On Mon, Nov 7, 2016 at 2:51 PM, Matthew Jordan <[email protected]> wrote:
> > > On Mon, Nov 7, 2016 at 5:00 AM, Dan Jenkins <[email protected]> > wrote: > >> >> On Fri, Nov 4, 2016 at 2:07 PM, Matt Fredrickson <[email protected]> >> 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
