Hi Daniel,
You are mingling several different ideas here, so let me try to separate
them to keep this discussion productive:
1) Should tools not ready for production live under a (sub-) domain
separate from fsfe.org?
2) How do we switch teams over?
3) Is Discourse a suitable replacement for
On 08/02/18 17:51, Florian Snow wrote:
> Hi Daniel,
>
>
> Daniel Pocock writes:
>> How does using a domain with the word "test" in it somewhere create more
>> work?
>
> At some point, a service is at least supposed to go into production, so
> at that point, configuration
Hi Daniel,
Daniel Pocock writes:
> How does using a domain with the word "test" in it somewhere create more
> work?
At some point, a service is at least supposed to go into production, so
at that point, configuration files need to change, DNS records need to
change, and
Hi Max,
while I agree with you in general, I see a small problem here:
On Thu, 08 Feb 2018 12:02:02 +0100 Max Mehl wrote:
>
> Discourse could work similarly. It has been set up by a group of
> volunteers and we gave them a free hand. Later it might serve as a
> communication platform for a
On 08/02/18 11:02, Max Mehl wrote:
> # Daniel Pocock [2018-02-08 11:00 +0100]:
>> There is a distinction between people volunteering to maintain a service
>> and the association choosing to rely on a service.
>>
>> This is particularly important in cases where two services do something
>> similar
# Daniel Pocock [2018-02-08 11:00 +0100]:
There is a distinction between people volunteering to maintain a service
and the association choosing to rely on a service.
This is particularly important in cases where two services do something
similar (e.g. Discourse acts as an alternative to the
On 08/02/18 08:27, Max Mehl wrote:
> # hellekin [2018-02-01 11:05 +0100]:
>> On Thu, Feb 01, 2018 at 07:26:42AM +0100, Florian Snow wrote:
>>>
>>> This may have been mentioned before, but there is a Discourse instance
>>> at community.fsfe.org.
>>
>> Hmmm, no there is not, only a broken page.