Duties of the PMC members

[dims]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Folks,

So, am trying to follow up on some threads i started in other lists. Do we have already have a list of duties of PMC
members?

Here's my totally non-authoratative take on it. Comments please

#1: Timely and accurate reports based on the rotation schedule in the foundation svn module
#2: Create and maintain a charter that governs the PMC/project(s)
#3: Take decisions affecting progress and health of the projects(s), ensure smooth functioning and create a conducive
work atmosphere for everyone in the community.
#4: Focus efforts more on community building rather than on code.
#5: Ensure all community members (not just PMC members) participate in decision-making processes (ex: limit IRC usage,
ban private lists for dev related decisions)
#6: Work with Infrastructure to meet day-to-day requirements of community members.
#7: Interact with other PMC's/Projects to learn best practices, reuse code, increase synergy, avoid duplication of effort.
#8: Work with the board for refining policies and practices to better serve the needs of the community.
#9: Work hard to add new individuals to the community, provide mentoring and enable them to join the PMC.
10: Keep strict watch on legal issues w.r.t copyrights, patents and licenses. Work proactively with our legal resources
to avoid problems to folks who use our projects.
#11: Be active and be a hands on contributor whether it is commits or JIRA's or answering questions on user or dev
mailing list.


For the PMC Chair, there are 2 more items:
#1: Consolidate and send report to the board
#2: Grant karma for svn for new committers.

thanks,
dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)

iD8DBQFIH25BgNg6eWEDv1kRAlyKAJ9ypoEC4kx+LwIBtVEIoOPa4dIEswCggX0Q
S0xugpsFl3iJ6/sTTWKckuI=
=dV+m
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Andrus Adamchik]

Hi Dims,

This looks good, so let me comment specifically on things that IMO  
need clarification.

On May 5, 2008, at 11:29 PM, Davanum Srinivas wrote:
> #2: Create and maintain a charter that governs the PMC/project(s)

That's probably obsolete. I recall seeing some TLP's having a charter,  
but I don't think that's an ongoing practice. All projects are part of  
a single org (ASF) after all.

> #4: Focus efforts more on community building rather than on code.

[...]

> #11: Be active and be a hands on contributor whether it is commits  
> or JIRA's or answering questions on user or dev
> mailing list.


"Community comes before code" maybe a general ASF philosophy, but  
relative time and prioritization of code vs. "community building" is  
up to an individual to decide. Some people may code like crazy and  
never show up on a mailing list except for an occasional release vote;  
others may spend time on the lists, interacting with the users and  
fellow developers and never commit anything. Either activity is not a  
duty.

Andrus

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jean T. Anderson]

Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Folks,
>
> So, am trying to follow up on some threads i started in other lists.
> Do we have already have a list of duties of PMC
> members?
>
http://www.apache.org/dev/pmc.html

also, lots of resource links are listed here:

http://www.apache.org/dev/#pmc

</snip>
> For the PMC Chair, there are 2 more items:
> #1: Consolidate and send report to the board
> #2: Grant karma for svn for new committers.
>
also see:

http://www.apache.org/dev/pmc.html#chair

cheers,

 -jean

> thanks,
> dims
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIH25BgNg6eWEDv1kRAlyKAJ9ypoEC4kx+LwIBtVEIoOPa4dIEswCggX0Q
> S0xugpsFl3iJ6/sTTWKckuI=
> =dV+m
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@...
> For additional commands, e-mail: general-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[dims]

Jean,

My problem was "proper management of an Apache project." What does it
entail? What should an individual PMC member do? that's what i am try
to enumerate here.

-- dims

On Mon, May 5, 2008 at 5:10 PM, Jean T. Anderson <jta@...> wrote:

> Davanum Srinivas wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Folks,
> >
> > So, am trying to follow up on some threads i started in other lists. Do we
> have already have a list of duties of PMC
> > members?
> >
> >
>  http://www.apache.org/dev/pmc.html
>
>  also, lots of resource links are listed here:
>
>  http://www.apache.org/dev/#pmc
>
>  </snip>
>
>
> > For the PMC Chair, there are 2 more items:
> > #1: Consolidate and send report to the board
> > #2: Grant karma for svn for new committers.
> >
> >
>  also see:
>
>  http://www.apache.org/dev/pmc.html#chair
>
>  cheers,
>
>  -jean
>
>
> >
> > thanks,
> > dims
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.5 (Cygwin)
> >
> > iD8DBQFIH25BgNg6eWEDv1kRAlyKAJ9ypoEC4kx+LwIBtVEIoOPa4dIEswCggX0Q
> > S0xugpsFl3iJ6/sTTWKckuI=
> > =dV+m
> > -----END PGP SIGNATURE-----
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@...
> > For additional commands, e-mail: general-help@...
> >
> >
>
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: general-unsubscribe@...
>  For additional commands, e-mail: general-help@...
>
>

--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Jean T. Anderson]

Davanum Srinivas wrote:
> Jean,
>
> My problem was "proper management of an Apache project." What does it
> entail? What should an individual PMC member do? that's what i am try
> to enumerate here.
>
>  

sure, that's fine, but you specifically asked "Do we have already have a
list of duties of PMC members?", and your post didn't reference any of
the existing documentation,  so I provided urls for them. In particular,
http://www.apache.org/dev/pmc.html lists some duties for the pmc as a
whole, and it also lists duties of the pmc chair.

Those lists might be incomplete -- it'd be good to improve the existing
docs.

at any rate, I responded to that specific question.

  -jean

> -- dims
>
> On Mon, May 5, 2008 at 5:10 PM, Jean T. Anderson <jta@...> wrote:
>  
>> Davanum Srinivas wrote:
>>
>>    
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Folks,
>>>
>>> So, am trying to follow up on some threads i started in other lists. Do we
>>>      
>> have already have a list of duties of PMC
>>    
>>> members?
>>>
>>>
>>>      
>>  http://www.apache.org/dev/pmc.html
>>
>>  also, lots of resource links are listed here:
>>
>>  http://www.apache.org/dev/#pmc
>>
>>  </snip>
>>
>>
>>    
>>> For the PMC Chair, there are 2 more items:
>>> #1: Consolidate and send report to the board
>>> #2: Grant karma for svn for new committers.
>>>
>>>
>>>      
>>  also see:
>>
>>  http://www.apache.org/dev/pmc.html#chair
>>
>>  cheers,
>>
>>  -jean
>>
>>
>>    
>>> thanks,
>>> dims
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.5 (Cygwin)
>>>
>>> iD8DBQFIH25BgNg6eWEDv1kRAlyKAJ9ypoEC4kx+LwIBtVEIoOPa4dIEswCggX0Q
>>> S0xugpsFl3iJ6/sTTWKckuI=
>>> =dV+m
>>> -----END PGP SIGNATURE-----
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@...
>>> For additional commands, e-mail: general-help@...
>>>
>>>
>>>      
>>
>>  ---------------------------------------------------------------------
>>  To unsubscribe, e-mail: general-unsubscribe@...
>>  For additional commands, e-mail: general-help@...
>>
>>
>>    
>
>
>
>  

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Roland Weber]

Andrus Adamchik wrote:

> Hi Dims,
>
> This looks good, so let me comment specifically on things that IMO need
> clarification.
>
> On May 5, 2008, at 11:29 PM, Davanum Srinivas wrote:
>> #2: Create and maintain a charter that governs the PMC/project(s)
>
> That's probably obsolete. I recall seeing some TLP's having a charter,
> but I don't think that's an ongoing practice. All projects are part of a
> single org (ASF) after all.

I believe that "bylaws" are required. At least the creation of
bylaws is mentioned in the TLP resolutions I have read last year.
While all projects are part of the ASF, they still have different
ways to handle code review, release preparation, project plans,
and so on.
A "charter" serves to define the scope of a project, but I've
seen projects that just use their TLP resolution to that end.
Of course I've also seen both terms being used interchangeably :-)

cheers,
   Roland


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Andrus Adamchik]

On May 6, 2008, at 7:42 PM, Roland Weber wrote:

> I believe that "bylaws" are required. At least the creation of
> bylaws is mentioned in the TLP resolutions I have read last year.

I think that's obsolete. Cayenne graduated 1.5 years ago and has no  
bylaws.

> Of course I've also seen both terms being used interchangeably :-)

My email was an example of that :-)

Andrus


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[robert burrell donkin-2]

On Tue, May 6, 2008 at 5:42 PM, Roland Weber <ossfwot@...> wrote:

> Andrus Adamchik wrote:
>
> > Hi Dims,
> >
> > This looks good, so let me comment specifically on things that IMO need
> clarification.
> >
> > On May 5, 2008, at 11:29 PM, Davanum Srinivas wrote:
> >
> > > #2: Create and maintain a charter that governs the PMC/project(s)
> > >
> >
> > That's probably obsolete. I recall seeing some TLP's having a charter, but
> I don't think that's an ongoing practice. All projects are part of a single
> org (ASF) after all.
> >
>
>  I believe that "bylaws" are required. At least the creation of
>  bylaws is mentioned in the TLP resolutions I have read last year.
>  While all projects are part of the ASF, they still have different
>  ways to handle code review, release preparation, project plans,
>  and so on.
>  A "charter" serves to define the scope of a project, but I've
>  seen projects that just use their TLP resolution to that end.
>  Of course I've also seen both terms being used interchangeably :-)

i think http://www.apache.org/foundation/bylaws.html are the bylaws referred to

- robert

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...

[Henri Yandell]

On Tue, May 6, 2008 at 10:35 AM, Robert Burrell Donkin
<robertburrelldonkin@...> wrote:

> On Tue, May 6, 2008 at 5:42 PM, Roland Weber <ossfwot@...> wrote:
>  > Andrus Adamchik wrote:
>  >
>  > > Hi Dims,
>  > >
>  > > This looks good, so let me comment specifically on things that IMO need
>  > clarification.
>  > >
>  > > On May 5, 2008, at 11:29 PM, Davanum Srinivas wrote:
>  > >
>  > > > #2: Create and maintain a charter that governs the PMC/project(s)
>  > > >
>  > >
>  > > That's probably obsolete. I recall seeing some TLP's having a charter, but
>  > I don't think that's an ongoing practice. All projects are part of a single
>  > org (ASF) after all.
>  > >
>  >
>  >  I believe that "bylaws" are required. At least the creation of
>  >  bylaws is mentioned in the TLP resolutions I have read last year.
>  >  While all projects are part of the ASF, they still have different
>  >  ways to handle code review, release preparation, project plans,
>  >  and so on.
>  >  A "charter" serves to define the scope of a project, but I've
>  >  seen projects that just use their TLP resolution to that end.
>  >  Of course I've also seen both terms being used interchangeably :-)
>
>  i think http://www.apache.org/foundation/bylaws.html are the bylaws referred to

We covered this in the last board meeting. Someone [Greg? Jim? I
forget who] has an action item to discuss on board@.

If I recall, it's that said bylaws can be a pointer to obey the
general ASF bylaws. There is no need for any self imposed bureaucracy
on the PMCs part; not unless they want it.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@...
For additional commands, e-mail: general-help@...