[katello-devel] Improving our discussion process?

[Tom McKay]

----- Original Message -----
> From: "Petr Chalupa" <pchalupa at redhat.com>
> To: Katello-devel at redhat.com
> Sent: Wednesday, April 17, 2013 7:25:27 AM
> Subject: [katello-devel] Improving our discussion process?
> 
> Hi,
> 
> I think that our mailing list gets overwhelmed sometimes and discussions
> tend to be long, hard to follow and sometimes without any resolution.
> 
> Which got me thinking:
>   * move questions, proposals, any longish discussions, etc. (hereafter
> discussion) over to Github issues
>   * create separate project under Katello just for tracking the discussions
>   * to have person assigned to each discussion who will be responsible
> for resolving the discussion and updating the original description with
> the resolution
>   * it should clean up our mailing list to contain only important
> announcements, warnings, nightly status updates, etc.
>   * Github organization teams [1] could be utilized to address
> particular sub group of Katello developers. (Teams can be mentioned in
> comments e.g. @Katello/katello-devs) We could create teams for: all,
> ruby, js, ui, subscription, packaging, etc.
> 
> Other options could be:
>   * setup a Stack Overflow open-source clone for this (but I would like
> not to introduce system)
>   * create another mailing list (it would help only partially, it wold
> not track assigned persons nor open/close state)
> 
> What do you think?
> 
> Petr
> 
> [1] https://github.com/organizations/Katello/teams
> 

Adam had suggested forums a long while ago. I personally love that idea since it would become a reference itself over time. (I know the mail archives are almost equivalent to forums but they don't share the feeling of community.)

There are two email lists, one more announcement related and one for devel. Perhaps we should just increase the signal-to-noise ratio on the 'katello' list. For example, when a discussion comes to a resolution a summary email could be sent to 'katello'.

Or perhaps a wiki page is made for a topic, initially with just a link to an etherpad for discussion. Again, once a resolution is agreed upon the wiki gets filled in (and etherpad locked for posterity?).

Overall I would prefer to see us leverage what we use currently better.

Good topic, though!