[asterisk-dev] Proposed Working Group Guidelines

Wed Nov 16 08:39:21 CST 2016

On Thu, Nov 10, 2016 at 10:27 AM, Sebastian <scgm11 at gmail.com> wrote:
> Hi!
>
> I’m up to help on the working groups.
>
> 1) About the work there not being reflected as patches to the source code I
> think the Matt idea of involving an Asterisk developer will make this easier
> to validate the ideas and not work in something that is not going to be on
> asterisk, so the time spent working is not in vain.
>
> 2) ok
>
> 3) About mailing listst and wiki I’m agree with Dan, is hard to follow up.
> (I know this is a no go but Github would really be veary easy or even
> Bitbucket that has Bitbucket pipelines to execute builds and test with CI
> with PRs and code review)
>
> What do you think about using gitter? or slack? the gitter could be added to
> the github mirror to be easy to get there ?

I'm so old school, I prefer mailing lists usually, but I understand
the desire that a lot of people want newer tools.  My perspective is
that people can use whatever collaboration tools they'd like to use,
as long they're publicly available for others to lurk on and they're
linked to on the working group's wiki page.

> 4) Meeting at the same hour weekly I see that hard to do it for everyone,
> for people in different timezones or even working commitments, maybe a more
> relaxed way of doing it?

Not sure - it seems like it helps to have a regular meeting to drive
the work, but I suppose we could make that working group dependent of
how that occurs.

> 9) about the process to contribute maybe do it as it is now with gerrit
> reviews? and maybe access to the wiki to contribute on documentation too.

I'm gonna say maybe that should be working group dependent.  I think
some groups will probably have code focus, and others probably are
going to produce documents/documentation instead.

Matthew Fredrickson

> El mié., 9 de nov. de 2016 a la(s) 14:03, Matt Fredrickson
> <creslin at digium.com> escribió:
>>
>> I can add that to the list!
>>
>> Matthew Fredrickson
>>
>> On Tue, Nov 8, 2016 at 2:40 AM, Dan Jenkins <dan.jenkins88 at gmail.com>
>> wrote:
>> >
>> >
>> > On Mon, Nov 7, 2016 at 2:51 PM, Matthew Jordan <mjordan at digium.com>
>> > wrote:
>> >>
>> >>
>> >>
>> >> On Mon, Nov 7, 2016 at 5:00 AM, Dan Jenkins <dan.jenkins88 at gmail.com>
>> >> wrote:
>> >>>
>> >>>
>> >>> On Fri, Nov 4, 2016 at 2:07 PM, Matt Fredrickson <creslin at digium.com>
>> >>> wrote:
>> >>>>
>> >>>> Hey All,
>> >>>>
>> >>>> I've been thinking a lot about how working groups might work within
>> >>>> the context of the Asterisk project.  Here are a few guidelines that
>> >>>> I
>> >>>> have come up with governing working groups.  Some of these guidelines
>> >>>> come from the Node project, as they have a lot of pre-existing
>> >>>> material on doing this.  I deliberately avoided comprehensively
>> >>>> importing their structure and guidelines, but pulled from some of
>> >>>> their more essential core principles.
>> >>>>
>> >>>> 1. There is no explicit or implicit commitment that a working group’s
>> >>>> output will actually be turned into code/patches by Digium or anybody
>> >>>> else outside of the working group.
>> >>>>
>> >>>> 2. Some working group topics might include: documentation, feature
>> >>>> request list, benchmarking, debug-ability, bug tracker triaging and
>> >>>> replication, migration efforts from SIP to PJSIP (and more?)
>> >>>>
>> >>>> 3. They need somewhere to “work” - so a section of the asterisk.org
>> >>>> wiki and probably a mailing list.  This can be a work item for me to
>> >>>> get taken care of.
>> >>>>
>> >>>> 4. Need a regular (weekly?) meeting time and “place” (an Asterisk
>> >>>> conference call, IRC, a google hangout, etc).
>> >>>>
>> >>>> 5. Need a charter of some sort - a charter would be a clearly defined
>> >>>> mission statement determining the subject matter of the group’s
>> >>>> efforts.
>> >>>>
>> >>>> 6. Need at least three initial members (pulled from node.js
>> >>>> guidelines)
>> >>>>
>> >>>> 7. Need to follow a consensus seeking process for any decisions
>> >>>> (https://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
>> >>>>
>> >>>> 8. Membership cannot be changed (added or removed) without unanimous
>> >>>> consensus of the members of the group (pulled from node.js
>> >>>> guidelines)
>> >>>>
>> >>>> 9. In order to create one, talk to me and I can see about getting
>> >>>> infrastructure (mailing list, wiki, git access) setup.
>> >>>>
>> >>>> Let me know if you have any thoughts, questions, or qualms with the
>> >>>> above guidelines.  I'll wiki-fy the results of any discussion here.
>> >>>>
>> >>>> --
>> >>>> Matthew Fredrickson
>> >>>> Digium, Inc. | Engineering Manager
>> >>>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> >>>>
>> >>>> --
>> >>>> _____________________________________________________________________
>> >>>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> >>>>
>> >>>> asterisk-dev mailing list
>> >>>> To UNSUBSCRIBE or update options visit:
>> >>>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>> >>>
>> >>>
>> >>>
>> >>> Hi Matt,
>> >>>
>> >>> Firstly, thanks for compiling all of this.
>> >>>
>> >>> Some comments around having the discussions etc.
>> >>>
>> >>> Please, no more mailing lists. Please? I'd rather not use the wiki for
>> >>> working groups - the wiki doesn't encourage conversation; instead its
>> >>> a
>> >>> place to go to document something and maybe write some comments on it
>> >>> - its
>> >>> really not the best place to have a conversation - I guess this is
>> >>> where the
>> >>> mailing lists come in but I'd love to get away from mailing lists - we
>> >>> have
>> >>> discourse now for example which is a MUCH better environment to have
>> >>> these
>> >>> conversations. I'd personally like to just replicate the node.js
>> >>> environment
>> >>> on github, with github issues and labels etc but its been made clear
>> >>> that
>> >>> isn't really an option unfortunately.
>> >>>
>> >>> There was talk of needing at least one core contributor (doesn't need
>> >>> to
>> >>> be a digium employee in my mind) to be one of the 3 initial members -
>> >>> is
>> >>> this still true?
>> >>>
>> >>
>> >> I mentioned that I thought it would be a good idea to have an Asterisk
>> >> Developer involved in any working group, simply as they can help to
>> >> validate
>> >> the feasibility of an idea. Whether or not that should be a requirement
>> >> is
>> >> up for debate.
>> >>
>> >> --
>> >> Matthew Jordan
>> >> Digium, Inc. | CTO
>> >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> >> Check us out at: http://digium.com & http://asterisk.org
>> >>
>> >> --
>> >> _____________________________________________________________________
>> >> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> >>
>> >> asterisk-dev mailing list
>> >> To UNSUBSCRIBE or update options visit:
>> >>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>> >
>> >
>> > Matt J - I like the idea personally - it was just missing from the list
>> > Matt
>> > F made :)
>> >
>> > --
>> > _____________________________________________________________________
>> > -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>> >
>> > asterisk-dev mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >    http://lists.digium.com/mailman/listinfo/asterisk-dev
>>
>>
>>
>> --
>> Matthew Fredrickson
>> Digium, Inc. | Engineering Manager
>> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>>
>> --
>> _____________________________________________________________________
>> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>>
>> asterisk-dev mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev

-- 
Matthew Fredrickson
Digium, Inc. | Engineering Manager
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA