[katello-devel] Improving our discussion process?

[Eric D Helms]

We've been down this road before, cause I know I have started it a few
times (which is to say I am all in favor if for nothing else the ability to
more easily throw in code snippets via gists and designs/screenshots
directly). I will lay out the previous reasons against this as I remember
and a few new ones just to make sure we would all be OK with them or have a
way to resolve them.

- Mailing list centralizes all development discussions and can be tracked
with just email
- People like threaded discussions

Questions:
- What would the devel mailing list be used for going forward (if not for
development discussions)?
- If we use a Github repo for tracking discussion and design issues, we now
have two places that occurs - Trello and Github - where do we draw the line?


- Eric

On Thu, Apr 18, 2013 at 8:23 AM, Petr Chalupa <pchalupa at redhat.com> wrote:

> It is as Jesus said. We could utilize Github-organization-team mentions so
> a developer would read only issues where he was mentioned. This should
> shrink the volume.
>
> On top of that it can be tagged to distinguish questions, proposals, etc.
> and monitor open/close state.
> Petr
> On 17.04.13 16:14, Jesus Rodriguez wrote:
>
>> From: "Miroslav Suchý" <msuchy at redhat.com>
>>> To: katello-devel at redhat.com
>>> Sent: Wednesday, April 17, 2013 9:37:48 AM
>>> Subject: Re: [katello-devel] Improving our discussion process?
>>>
>>> On 04/17/2013 01:25 PM, Petr Chalupa wrote:
>>>
>>>>
>>>> I think that our mailing list gets overwhelmed sometimes and discussions
>>>> tend to be long, hard to follow and sometimes without any resolution.
>>>>
>>>
>>> So you are saying there is a lot of emails for you.
>>>
>>>  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)
>>>>
>>>
>>> So you just move information from one form to another. But the amount of
>>> information (your primary problem) will be the same. How this change
>>> helps you then?
>>>
>>
>> I think his Petr's suggestions don't limit the amount of information but
>> it does segment it out so that the stuff he cares about is easier to
>> follow and the other stuff he can ignore (or deal with at a different
>> pace). But when it's all on the same list I agree it is quite hard to
>> follow. I mean I don't look at katello-devel very often (judging from
>> my 5500+ unread messages) but I will say this list gets A LOT of
>> traffic and I agree with Petr it is very hard to keep up with.
>>
>> jesus
>>
>>
> ______________________________**_________________
> katello-devel mailing list
> katello-devel at redhat.com
> https://www.redhat.com/**mailman/listinfo/katello-devel<https://www.redhat.com/mailman/listinfo/katello-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20130418/eb9d2507/attachment.htm>