Discourse - next steps / actions

[lzap]

Although I prefer to only migrate users list, if we decide to migrate both I would actually like to see foreman-announce to be migrated as well. We previously had issues sending plugin announcements into this low-volume list, it's a chance to change this and split it into announce-core and announce-plugins or something like that. I assume there would be an easy way of subscribing to those tags via RSS or email.

LZ

···

On Thu, Nov 23, 2017 at 5:31 PM, Greg Sutcliffe <greg@emeraldreverie.org> wrote:

Hi all,

I'll try to keep this brief, at least by my standards :)

Firstly, I think it's clear that the discussion is leaning towards
implementing Discourse for at least one, and possibly both, of the
mailing lists. Many people have contributed - I'd like to thank them all
for keeping this from descending into a flamewar :)

We do need to give the users list a little longer for feedback (it's
only been a week), but I think here we can start to talk about the
migration planning.

Since we all (or most?) need to start getting used to Discourse, I've
written up a draft migration plan there:

Migration Plan

This is all very much theoretical, and open to suggestion/contribution! Once we’re happy with it I will post it to the dev list, but it’s much easier to incorporate suggestions here first. I have wiki’d this post, so edit as needed, or put suggestions in the replies and I will include them. I will structure this as a timeline, I think that makes the most sense. I’m going for about 3 weeks notice, but that’s open to debate too. T minus ? - consultation Consultation phase, where we are right now…

I've just updated it to reflect the latest discussions. No doubt I have
missed something though, so I've made it into a wiki post - feel free to
edit with suggestions.

There are two things I'd like to get input from people on:

# Moderators

I need a small team of moderators to deal with running the forum. I
don't expect it to take up much time, but it is important that more
people than just me know how things work. 3-4 people (including me) is
probably enough to start with.

So, volunteers needed! Don't make me start picking on people :)

# Choice of lists to migrate

As above, we have to decide if we migrate both lists or just one. I see
significant benefits on having everyone on the same platform (top 2 -
the @groups feature is very useful for discussions, and the
discoverability of dev discussions for users helps them to get involved
and grow our dev community). However, I know others are more cautious
than I.

Again, since we'll all likely be using Discourse in some capacity, I've
gone ahead and created a poll on Discourse for us. Please do leave your
feedback! Votes by email-response (here or on Discourse) are of course
acceptable for those allergic to UIs, I will add them in ;)

[poll] Which lists should migrate to Discourse?

As per the post to the dev-list, a move to Discourse of some kind is looking very likely. However, we need to decide what should be migrated to Discourse in this pass. Since Discourse is going to be a feature in our lives, let’s use the tools it brings . Here’s a poll: poll If you need another option for some reason, just let me know.

I've not covered foreman-announce - we use this so infrequently, and
posting rights are heavily restricted, so I think we can decide what to
do with it later.

Hang in there, we're getting to the fun bit! :)
Greg

--
You received this message because you are subscribed to the Google Groups "foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Later,
  Lukas @lzap Zapletal