Re: Process, policy and best practice

2013-04-03 Thread Rich Bowen
On Apr 1, 2013, at 6:28 PM, Benson Margulies wrote: As I see it, the primary attraction here is that we could end up with *one* coherent body of documentation on policies and procedures, available to project new and old. For whatever it's worth, I'd like to participate in such an effort in

Process, policy and best practice

2013-04-01 Thread Ross Gardler
ComDev PMC, I proposed, during budget discussions, that the ComDev PMC should consider budgeting to accelerate the documentation goals of this PMC. Since then the IPMC has been discussing the idea of handing off the documentation parts of their responsibilities to ComDev. This is just a

Re: Process, policy and best practice

2013-04-01 Thread Luciano Resende
On Mon, Apr 1, 2013 at 2:58 AM, Ross Gardler rgard...@opendirective.comwrote: ComDev PMC, I proposed, during budget discussions, that the ComDev PMC should consider budgeting to accelerate the documentation goals of this PMC. Since then the IPMC has been discussing the idea of handing off

Re: Process, policy and best practice

2013-04-01 Thread Ross Gardler
Sent from a mobile device, please excuse mistakes and brevity On 1 Apr 2013 18:28, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Apr 1, 2013 at 2:58 AM, Ross Gardler rgard...@opendirective.com wrote: ComDev PMC, I proposed, during budget discussions, that the ComDev PMC should

Re: Process, policy and best practice

2013-04-01 Thread Luciano Resende
On Mon, Apr 1, 2013 at 10:32 AM, Ross Gardler rgard...@opendirective.comwrote: Sent from a mobile device, please excuse mistakes and brevity On 1 Apr 2013 18:28, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Apr 1, 2013 at 2:58 AM, Ross Gardler rgard...@opendirective.com wrote:

Re: Process, policy and best practice

2013-04-01 Thread Noah Slater
ComDev could work to attract volunteers. I am sure there are more than a few people on the Incubator dev@ list at the moment who might consider moving over here to work on process and policy documentation... On 1 April 2013 19:19, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Apr 1, 2013

Re: Process, policy and best practice

2013-04-01 Thread Martijn Dashorst
Because 150+ people tasked with oversight, documentation of processes and procedures of podlings, TLPs and themselves, discussing different views of the past, present and future might not be able to agree to anything, but a small team tasked with just documenting process might get the job done

Re: Process, policy and best practice

2013-04-01 Thread Ross Gardler
On 1 April 2013 22:20, Shane Curcuru a...@shanecurcuru.org wrote: On 4/1/2013 2:19 PM, Luciano Resende wrote: On Mon, Apr 1, 2013 at 10:32 AM, Ross Gardler rgard...@opendirective.com **wrote: On 1 Apr 2013 18:28, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Apr 1, 2013 at 2:58

Re: Process, policy and best practice

2013-04-01 Thread Benson Margulies
As I see it, the primary attraction here is that we could end up with *one* coherent body of documentation on policies and procedures, available to project new and old. - To unsubscribe, e-mail:

Re: Process, policy and best practice

2013-04-01 Thread Marvin Humphrey
On Mon, Apr 1, 2013 at 3:22 PM, Ross Gardler rgard...@opendirective.com wrote: The role of ComDev would not be to define policy, only to document and curate it. As Greg said when this first came up over a year ago - most of the actual writing is done. There is no single source of policy for

Re: Process, policy and best practice

2013-04-01 Thread Shane Curcuru
On 4/1/2013 6:28 PM, Benson Margulies wrote: As I see it, the primary attraction here is that we could end up with *one* coherent body of documentation on policies and procedures, available to project new and old. Oh, drat. I was really starting to get excited about this project - having one

Re: Process, policy and best practice

2013-04-01 Thread Luciano Resende
On Mon, Apr 1, 2013 at 5:56 PM, Shane Curcuru a...@shanecurcuru.org wrote: On 4/1/2013 6:28 PM, Benson Margulies wrote: As I see it, the primary attraction here is that we could end up with *one* coherent body of documentation on policies and procedures, available to project new and old.