[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-community
Subject:    Re: Formal request to set up a KDE Discourse instance
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2021-03-08 8:55:12
Message-ID: CA+XidOF3xGf2GrDExeZpOoWwT2_pXXvfZ7fKzVud1twSNDW1hA () mail ! gmail ! com
[Download RAW message or body]

On Mon, Mar 8, 2021 at 2:55 AM Nate Graham <nate@kde.org> wrote:

> On 3/6/21 10:35 PM, Ben Cooksley wrote:
> > On Sun, Mar 7, 2021 at 3:51 AM Nate Graham <nate@kde.org
> > <mailto:nate@kde.org>> wrote:>
> >     Ben, can we get Discourse added to the Sysadmin task queue? Again, no
> >     pressure regarding schedule, but can we get it added there just for
> >     work-tracking purposes?
> >
> >
> > I've now added https://invent.kde.org/sysadmin/task-queue/-/issues/31
> > <https://invent.kde.org/sysadmin/task-queue/-/issues/31> for this.
>
> > In terms of scheduling it is currently behind [stuff]
>
>
> Thanks Ben! Much appreciated.
>
> I think doing GitLab stuff first makes sense in terms of usage of your
> time. On that subject, I notice that both Jonathan and Carl (CC'd) have
> offered to handle setting up the test Discourse instance, or assist with
> it. Perhaps we can do them in parallel, and accomplish a bit of Sysadmin
> onboarding too. :) What do you think?
>

We'll need to investigate the capacity and capability of our servers first
to choose one that can potentially handle this (which as noted earlier, is
substantially constrained by the demand of the Discourse developers to use
Docker).

In the meantime, it will be interesting to see how the discussion plays out
in the issue as there has been some interesting commentary already.


>
> Nate
>

Cheers,
Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Mon, Mar 8, 2021 at 2:55 AM Nate Graham &lt;<a \
href="mailto:nate@kde.org">nate@kde.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 3/6/21 10:35 PM, \
Ben Cooksley wrote:<br> &gt; On Sun, Mar 7, 2021 at 3:51 AM Nate Graham &lt;<a \
href="mailto:nate@kde.org" target="_blank">nate@kde.org</a> <br> &gt; &lt;mailto:<a \
href="mailto:nate@kde.org" target="_blank">nate@kde.org</a>&gt;&gt; wrote:&gt; <br> \
&gt;        Ben, can we get Discourse added to the Sysadmin task queue? Again, no<br> \
&gt;        pressure regarding schedule, but can we get it added there just for<br> \
&gt;        work-tracking purposes?<br> &gt; <br>
&gt; <br>
&gt; I&#39;ve now added <a \
href="https://invent.kde.org/sysadmin/task-queue/-/issues/31" rel="noreferrer" \
target="_blank">https://invent.kde.org/sysadmin/task-queue/-/issues/31</a> <br> &gt; \
&lt;<a href="https://invent.kde.org/sysadmin/task-queue/-/issues/31" rel="noreferrer" \
target="_blank">https://invent.kde.org/sysadmin/task-queue/-/issues/31</a>&gt; for \
this.<br> <br>
&gt; In terms of scheduling it is currently behind [stuff]<br>
<br>
<br>
Thanks Ben! Much appreciated.<br>
<br>
I think doing GitLab stuff first makes sense in terms of usage of your <br>
time. On that subject, I notice that both Jonathan and Carl (CC&#39;d) have <br>
offered to handle setting up the test Discourse instance, or assist with <br>
it. Perhaps we can do them in parallel, and accomplish a bit of Sysadmin <br>
onboarding too. :) What do you think?<br></blockquote><div><br></div><div>We&#39;ll \
need to investigate the capacity and capability of our servers first to choose one \
that can potentially handle this (which as noted earlier, is substantially \
constrained by the demand of the Discourse developers to use \
Docker).</div><div><br></div><div>In the meantime, it will be interesting to see how \
the discussion plays out in the issue as there has been some interesting commentary \
already.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px \
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
<br>
Nate<br></blockquote><div><br></div><div>Cheers,</div><div>Ben  </div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]