Re: Why should D be a president's committee?

[Ross Gardler]

As I understand the current D committee proposal it does not impact current 
CoC setup.

If you feel it should/should not then maybe you can provide your thoughts in 
the form of feedback to Myrle's initial question here. If you don't have an 
opinion yet maybe consider asking the proposed VP D and the volunteers on the 
diversity list for their thoughts.

Ross


From: Dave Fisher 
Sent: Wednesday, May 1, 2019 8:23 AM
To: dev@community.apache.org
Subject: Re: Why should D be a president's committee?

Hi Ross,

Forgive me if this opens up the subject more than needed, but I have a question.

How do you view this new Diversity & Inclusion committee with respect to the 
code of conduct and 
https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.apache.org%2Ffoundation%2Fpolicies%2Fconduct%23reporting-guidelinesdata=02%7C01%7C%7C72419fb14e8c4659a9ec08d6ce4915f6%7C84df9e7fe9f640afb435%7C1%7C0%7C636923210621821512sdata=QlG6eMuv0Yp9bMB0vDSIwg%2BI3VstBHLEoXfKLj5bhVQ%3Dreserved=0
 where a list of contacts are provided.

Is the new D committee meant to be separate from reporting/“enforcement” or 
not? Your arguments around legal situations involving law enforcement 
potentially implies a mixing of policy evaluation and enforcement.

Regards,
Dave

> On May 1, 2019, at 7:31 AM, Ross Gardler  wrote:
>
> Good points so far.  One that I believe has been missed...
>
> Board committees have 9 bosses. PMCs have potentially many more. Presidents 
> committees have 1.
>
> In other words, a Presidents committee can get things done more quickly in 
> difficult or controversial spaces, especially in things that do not present a 
> binary correct/incorrect set of choices.
>
> As noted by others there is significant oversight from the board via monthly 
> reports. Plenty of opportunity for course correction as result. Any objection 
> by any one of the nine is dealt with by President, allowing the committee to 
> get on with their work within the boundaries agreed with the president.
>
> This requires a level of trust in the President, and their delegates.
>
> Ross
>
> Get Outlook for 
> Android
>
> 
> From: Shane Curcuru 
> Sent: Wednesday, May 1, 2019 6:23:34 AM
> To: dev@community.apache.org
> Subject: Re: Why should D be a president's committee?
>
> The most important question is: where do the people who are currently
> most active doing the real work of the survey and organizing
> informational materials on diversity@ want to do that work?  Ensuring
> they have a productive space and framework to work is the first thing to
> solve.   That said...
>
> Myrle Krantz wrote on 5/1/19 7:06 AM:
> ...snip...
>> * Make it a sub-committee of ComDev.
>
> This is nothing more than a page on community.a.o and the diversity@
> mailing list.  We already effectively have that.  The only difference
> would be having a formal page on the website that lists who's there,
> essentially copying what we've done in the mailing list.
>
> In terms of powers, none in particular.  Membership changes by the PMC
> voting in new PMC members (or allowing committers to participate, etc.)
> Reports would be part of the quarterly ComDev report.
>
>> * Make it a president's committee.
>
> The proposal is to also name a VP of that committee as well.  The VP is
> an officer, and can perform duties for the ASF within the scope of
> whatever charter the board originally creates the VP officer with.
>
> Historically, we've had the board create *new VP roles* with a title and
> description, and appoint the first person to that role.  For President's
> committees and other VPs reporting to the President, we've had the
> President thereafter simply make new appointments to existing roles
> directly (always reported in board reports).
>
> President's committees can be changed by the President at any point, or
> by the VP in charge if specifically authorized to do so.  Also, since
> President's committees are mostly about operations, we have examples of
> officers like this having regular annual budgets and signing authority.
>
> They cannot release software (publicly).  They could have a separate
> website and mailing lists.  President's committees report monthly.
>
>> * Make it it's own PMC.
>
> This requires a normal board resolution, and would act like any other
> PMC, especially in terms of managing PMC or committer membership.  We've
> done straight-to-PMC before (i.e. not going through Incubation), it just
> needs the scope description of the PMC and the list of VP and members.
>
> They could release software and all the usual PMC things, and they
> report to the board quarterly.
>
> 
>
> Elsethread, 

Re: Request for Reviewers for Community Track at ApacheCon NA Las Vegas

[Shane Curcuru]

Sharan Foga wrote on 5/1/19 4:16 PM:
> Hi All
> 
> The CFP for ApacheCon NA, Las Vegas will be closing soon so I am looking for 
> some volunteers to help review and rate the Community track submissions. 
> 
> If you are interested in helping out then please follow the submit a talk 
> link to login to the CFP system for ApacheCon NA, Las Vegas and then click on 
> the link to request to become a reviewer. 
> 
> https://asf.jamhosted.net/cfp.html

I just signed up and can definitely help you review and swizzle the
schedule.

Sadly, I'm not able to attend Las Vegas personally - this will be the
first US/NA ApacheCon I've missed since I started attending in 2001.  I
haven't been to quite as many as Rich, but I'm within a handful of the
number he's done!

-- 

- Shane
  Still An Occasional Planner
  The Apache Software Foundation
  https://archive.apachecon.com/

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Request for Reviewers for Community Track at ApacheCon NA Las Vegas

[Sharan Foga]

Hi All

The CFP for ApacheCon NA, Las Vegas will be closing soon so I am looking for 
some volunteers to help review and rate the Community track submissions. 

If you are interested in helping out then please follow the submit a talk link 
to login to the CFP system for ApacheCon NA, Las Vegas and then click on the 
link to request to become a reviewer. 

https://asf.jamhosted.net/cfp.html

Thanks
Sharan


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: REMINDER: We need more Community Track submissions for ApacheCon NA and ApacheCon EU

[Sharan Foga]

Hi All

At this stage we are still lacking submissions for our Community tracks in both 
Las Vegas and Berlin. If we don't get enough submissions then we may need to 
think about giving up some of our allocated slots.

We need more submissions in all areas so if you are interested please don't 
leave it to the last moment as the deadline for the Las Vegas CFP is 2 only 
weeks away.

Thanks
Sharan

On 2019/04/14 17:51:00, Sharan Foga  wrote: 
> Hi All
> 
> A reminder that we have 3 days of Community track for ApacheCon NA and 2 days 
> of Community track for ApacheCon EU.
> 
> Both CFPs are open and we need more submissions if we are going to fill both 
> of these Community tracks with content. I’ve included links to both CFPs 
> below:
> 
> * ApacheCon NA CFP https://www.apachecon.com/acna19/cfp.html 
> * ApacheCon EU CFP https://aceu19.apachecon.com/call-presentations 
> 
> I’ve also put together a bit of a promo paragraph (see below) to help give 
> potential speakers an idea of what we are looking for. 
> 
> If you are attending both ApacheCon NA and EU, then you could submit the same 
> talk for both ;-)
> 
> Thanks
> Sharan
> 
> --
> Speak on the Community Track at ApacheCon
> 
> As our communities grow it becomes even more important to hear from people 
> within our communities. We want to hear your story, how and why did you 
> become involved with Apache? What does it mean to be a Committer, Member, 
> Officer or Director?
> 
> As part of our Apache Way section we are looking for different stories and 
> experiences around adopting it. What were the challenges and how were they 
> overcome?  For the uninitiated - how does governance, branding and licensing 
> work?
> 
> We also have a new Apache tools section and are looking specifically for 
> introductions / getting started sessions on any of the following; Apache 
> Kibble, Apache Whimsy, Apache Training (incubating) or Apache Ponymail.
> 
> How diverse and inclusive are our communities? And looking into the future 
> how are our communities evolving? 
> 
> Share your thoughts and  experiences
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: ASF Application for Google Season of Docs 2019 (take 2)

[Sharan Foga]

Hi All

An update on this. Unfortunately the ASF has not been selected as an 
organisation but Apache Airflow and Apache Cassandra have - so congrats to 
them. You can see the full list of accepted organisations here

https://developers.google.com/season-of-docs/docs/participants/

Thanks to everyone that helped prepare content for our application.

Thanks
Sharan

On 2019/04/24 05:43:14, Maxim Solodovnik  wrote: 
> AFAIK we should wait for slots and tech writers :)
> 
> On Wed, 24 Apr 2019 at 08:54, Huxing Zhang  wrote:
> 
> > Hi Maxim,
> >
> > Thanks for updating. I can see it on the wiki.
> > Anything else I need to do?
> >
> > On Wed, Apr 24, 2019 at 12:31 AM Maxim Solodovnik 
> > wrote:
> > >
> > > Done!
> > > sorry for delay
> > >
> > > On Tue, 23 Apr 2019 at 22:41, Maxim Solodovnik 
> > wrote:
> > >
> > > > Thanks I'm trying to add this info
> > > > unfortunately Confluence works extremely slow :(
> > > > Will let you know as soon as this will done, so you can check
> > > >
> > > > On Tue, 23 Apr 2019 at 20:26, Huxing Zhang  wrote:
> > > >
> > > >> Hi Maxim,
> > > >>
> > > >> On Tue, Apr 23, 2019 at 9:46 AM Maxim Solodovnik <
> > solomax...@gmail.com>
> > > >> wrote:
> > > >> >
> > > >> > For whatever reason I can't grant you permission, maybe my
> > > >> confluence-fu is
> > > >> > not enough :(
> > > >> > Can someone please help?
> > > >>
> > > >> Anyway, because the it is close to deadline, I will reply it here,
> > > >> could you please help to add it?
> > > >>
> > > >> ### Project 1
> > > >> Apache Project: Apache Dubbo (incubating)
> > > >> Documentation Project Name: Improve the doc for integrating Dubbo with
> > > >> service registry
> > > >> Description: Add documentation of how Dubbo work with registry center
> > > >> like etcd,
> > > >> consul, by following the zookeeper integration documentation
> > > >> Mentors: Huxing Zhang(hux...@apache.org), Jun Liu(liu...@apache.org)
> > > >> Link to the related materials:
> > > >> - Doc: http://dubbo.apache.org/en-us/docs/user/quick-start.html
> > > >> - Blog: http://dubbo.apache.org/en-us/blog/dubbo-zk.html
> > > >>
> > > >> ### Project2
> > > >> Apache Project: Apache Dubbo (incubating)
> > > >> Documentation Project Name: Improve documentation for Dubbo load
> > balancing
> > > >> Description: Add documentation of how to use various load balancing
> > > >> strategies,
> > > >> like Random, Consistent Hashing, etc.
> > > >> Mentors: Huxing Zhang(hux...@apache.org), Jun Liu(liu...@apache.org)
> > > >> Link to the related materials:
> > > >> - Doc: http://dubbo.apache.org/en-us/docs/user/demos/loadbalance.html
> > > >>
> > > >> If have to choose one project, please choose Project 1.
> > > >>
> > > >>
> > > >>
> > > >> >
> > > >> > On Tue, 23 Apr 2019 at 08:40, Huxing Zhang 
> > wrote:
> > > >> >
> > > >> > > Hi,
> > > >> > >
> > > >> > >
> > > >> > > On Mon, Apr 22, 2019 at 11:22 PM Maxim Solodovnik <
> > > >> solomax...@gmail.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > Hello,
> > > >> > > >
> > > >> > > > what is your confluence/apache id?
> > > >> > >
> > > >> > > I use my apache id (huxing) to login.
> > > >> > >
> > > >> > > >
> > > >> > > > On Mon, 22 Apr 2019 at 21:50, Huxing Zhang 
> > > >> wrote:
> > > >> > > >
> > > >> > > > > Hi All,
> > > >> > > > >
> > > >> > > > > I have contacted INFRA, they said that I need the karma
> > before I
> > > >> can
> > > >> > > > > edit this page.
> > > >> > > > > Could someone help to grant me the karma?
> > > >> > > > > Anything I need to do here?
> > > >> > > > >
> > > >> > > > > On Mon, Apr 22, 2019 at 4:28 PM Huxing Zhang <
> > hux...@apache.org>
> > > >> > > wrote:
> > > >> > > > > >
> > > >> > > > > > Hi,
> > > >> > > > > >
> > > >> > > > > > I am interesting in adding some ideas. However I cannot
> > access
> > > >> this
> > > >> > > > > > page with my Apache credentials. Any ideas how to fix this?
> > > >> > > > > >
> > > >> > > > > > On Sun, Apr 14, 2019 at 11:49 PM Sharan Foga <
> > sha...@apache.org
> > > >> >
> > > >> > > wrote:
> > > >> > > > > > >
> > > >> > > > > > > Hi All
> > > >> > > > > > >
> > > >> > > > > > > (Thanks very much Maxim for helping to reboot this!)
> > > >> > > > > > >
> > > >> > > > > > > If we are going to apply again then we need to have at
> > least
> > > >> one
> > > >> > > idea
> > > >> > > > > for a documentation project on our wiki page, so please
> > update it
> > > >> if
> > > >> > > you'd
> > > >> > > > > like to be a part of the ASF application. The deadline for our
> > > >> > > application
> > > >> > > > > is 23rd April 2019.
> > > >> > > > > > >
> > > >> > > > > > > Please don't forget there is a minimum requirement of 2
> > > >> mentors per
> > > >> > > > > documentation project and each mentor will also need to
> > register.
> > > >> > > > > > >
> > > >> > > > > > > Thanks
> > > >> > > > > > > Sharan
> > > >> > > > > > >
> > > >> > > > > > > On 2019/04/11 00:48:10, Maxim Solodovnik <
> > > >> solomax...@gmail.com>
> > > >> > > wrote:
> > > >> > 

Re: [ANNOUNCE] Welcome Gris Cuevas as new PMC member

[Sharan Foga]

Congratulations and welcome Gris!

Thanks
Sharan

On 2019/04/23 11:26:51, Myrle Krantz  wrote: 
> Hey all,
> 
> Please welcome Gris Cuevas as the newest member of the Community
> Development PMC.
> 
> Gris is helping out representing Apache at various conferences and helping
> to make our own conferences a success.  Gris has also offered to help us
> with Diversity & Inclusion work and has already made several constructive,
> concrete proposals.  She's helping us find the way forward through a
> particularly messy and difficult topic.
> 
> Thank you Gris, for accepting our invitation to continue your awesome work
> together with us!  I look forward to continuing to work together with you!
> 
> Best Regards,
> Myrle Krantz
> PMC Member, Apache Community Development
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [ANNOUNCE] Welcome Paul Berschick as Committer

[Sharan Foga]

Congratulations and welcome Paul!

Thanks
Sharan

On 2019/04/23 11:19:41, Myrle Krantz  wrote: 
> Hey all,
> 
> Please welcome Paul Berschick as a committer for community development.  He
> helped us put together the Apache Roadshow in Berlin last year, doing
> everything from booking the venue to organizing the video to  communicating
> with the printer to get the right colors on the Apache feather on the
> conference t-shirt.
> 
> This year he's helping us put together ApacheCon in Berliln.
> 
> Thank you for everything you've done Paul, and we look forward to
> continuing to work with you!
> 
> Best Regards,
> Myrle
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Why should D be a president's committee?

[Dave Fisher]

Hi Ross,

Forgive me if this opens up the subject more than needed, but I have a question.

How do you view this new Diversity & Inclusion committee with respect to the 
code of conduct and 
https://www.apache.org/foundation/policies/conduct#reporting-guidelines where a 
list of contacts are provided.

Is the new D committee meant to be separate from reporting/“enforcement” or 
not? Your arguments around legal situations involving law enforcement 
potentially implies a mixing of policy evaluation and enforcement.

Regards,
Dave

> On May 1, 2019, at 7:31 AM, Ross Gardler  wrote:
> 
> Good points so far.  One that I believe has been missed...
> 
> Board committees have 9 bosses. PMCs have potentially many more. Presidents 
> committees have 1.
> 
> In other words, a Presidents committee can get things done more quickly in 
> difficult or controversial spaces, especially in things that do not present a 
> binary correct/incorrect set of choices.
> 
> As noted by others there is significant oversight from the board via monthly 
> reports. Plenty of opportunity for course correction as result. Any objection 
> by any one of the nine is dealt with by President, allowing the committee to 
> get on with their work within the boundaries agreed with the president.
> 
> This requires a level of trust in the President, and their delegates.
> 
> Ross
> 
> Get Outlook for Android
> 
> 
> From: Shane Curcuru 
> Sent: Wednesday, May 1, 2019 6:23:34 AM
> To: dev@community.apache.org
> Subject: Re: Why should D be a president's committee?
> 
> The most important question is: where do the people who are currently
> most active doing the real work of the survey and organizing
> informational materials on diversity@ want to do that work?  Ensuring
> they have a productive space and framework to work is the first thing to
> solve.   That said...
> 
> Myrle Krantz wrote on 5/1/19 7:06 AM:
> ...snip...
>> * Make it a sub-committee of ComDev.
> 
> This is nothing more than a page on community.a.o and the diversity@
> mailing list.  We already effectively have that.  The only difference
> would be having a formal page on the website that lists who's there,
> essentially copying what we've done in the mailing list.
> 
> In terms of powers, none in particular.  Membership changes by the PMC
> voting in new PMC members (or allowing committers to participate, etc.)
> Reports would be part of the quarterly ComDev report.
> 
>> * Make it a president's committee.
> 
> The proposal is to also name a VP of that committee as well.  The VP is
> an officer, and can perform duties for the ASF within the scope of
> whatever charter the board originally creates the VP officer with.
> 
> Historically, we've had the board create *new VP roles* with a title and
> description, and appoint the first person to that role.  For President's
> committees and other VPs reporting to the President, we've had the
> President thereafter simply make new appointments to existing roles
> directly (always reported in board reports).
> 
> President's committees can be changed by the President at any point, or
> by the VP in charge if specifically authorized to do so.  Also, since
> President's committees are mostly about operations, we have examples of
> officers like this having regular annual budgets and signing authority.
> 
> They cannot release software (publicly).  They could have a separate
> website and mailing lists.  President's committees report monthly.
> 
>> * Make it it's own PMC.
> 
> This requires a normal board resolution, and would act like any other
> PMC, especially in terms of managing PMC or committer membership.  We've
> done straight-to-PMC before (i.e. not going through Incubation), it just
> needs the scope description of the PMC and the list of VP and members.
> 
> They could release software and all the usual PMC things, and they
> report to the board quarterly.
> 
> 
> 
> Elsethread, Mark also mentioned a board committee.  They have the powers
> of the board.  Changing board committees (normally) takes a board
> resolution, meaning it takes more time to add/remove people.  They
> report monthly to the board.
> 
> While President's committees have a broad scope of operations, often
> looking across the whole ASF, they do not have direct power to generally
> set policies across other projects.  Board committees, on the other
> hand, could directly enact and enforce policies across projects.
> 
> 
> 
> Personally, I'm +1 for a President's committee.  Right now, we need a
> place where people actively doing productive work can do so.
> President's committees provide plenty of oversight and monthly
> reporting.  A lot of the work will be gathering data and creating solid
> materials that projects or other officers can choose to use to help
> improve our communities, or doing their own direct outreach at
> conferences or the like.  Those are all things well suited to a
> 

Re: Why should D be a president's committee?

[Ross Gardler]

Good points so far.  One that I believe has been missed...

Board committees have 9 bosses. PMCs have potentially many more. Presidents 
committees have 1.

In other words, a Presidents committee can get things done more quickly in 
difficult or controversial spaces, especially in things that do not present a 
binary correct/incorrect set of choices.

As noted by others there is significant oversight from the board via monthly 
reports. Plenty of opportunity for course correction as result. Any objection 
by any one of the nine is dealt with by President, allowing the committee to 
get on with their work within the boundaries agreed with the president.

This requires a level of trust in the President, and their delegates.

Ross

Get Outlook for Android


From: Shane Curcuru 
Sent: Wednesday, May 1, 2019 6:23:34 AM
To: dev@community.apache.org
Subject: Re: Why should D be a president's committee?

The most important question is: where do the people who are currently
most active doing the real work of the survey and organizing
informational materials on diversity@ want to do that work?  Ensuring
they have a productive space and framework to work is the first thing to
solve.   That said...

Myrle Krantz wrote on 5/1/19 7:06 AM:
...snip...
> * Make it a sub-committee of ComDev.

This is nothing more than a page on community.a.o and the diversity@
mailing list.  We already effectively have that.  The only difference
would be having a formal page on the website that lists who's there,
essentially copying what we've done in the mailing list.

In terms of powers, none in particular.  Membership changes by the PMC
voting in new PMC members (or allowing committers to participate, etc.)
 Reports would be part of the quarterly ComDev report.

> * Make it a president's committee.

The proposal is to also name a VP of that committee as well.  The VP is
an officer, and can perform duties for the ASF within the scope of
whatever charter the board originally creates the VP officer with.

Historically, we've had the board create *new VP roles* with a title and
description, and appoint the first person to that role.  For President's
committees and other VPs reporting to the President, we've had the
President thereafter simply make new appointments to existing roles
directly (always reported in board reports).

President's committees can be changed by the President at any point, or
by the VP in charge if specifically authorized to do so.  Also, since
President's committees are mostly about operations, we have examples of
officers like this having regular annual budgets and signing authority.

They cannot release software (publicly).  They could have a separate
website and mailing lists.  President's committees report monthly.

> * Make it it's own PMC.

This requires a normal board resolution, and would act like any other
PMC, especially in terms of managing PMC or committer membership.  We've
done straight-to-PMC before (i.e. not going through Incubation), it just
needs the scope description of the PMC and the list of VP and members.

They could release software and all the usual PMC things, and they
report to the board quarterly.



Elsethread, Mark also mentioned a board committee.  They have the powers
of the board.  Changing board committees (normally) takes a board
resolution, meaning it takes more time to add/remove people.  They
report monthly to the board.

While President's committees have a broad scope of operations, often
looking across the whole ASF, they do not have direct power to generally
set policies across other projects.  Board committees, on the other
hand, could directly enact and enforce policies across projects.



Personally, I'm +1 for a President's committee.  Right now, we need a
place where people actively doing productive work can do so.
President's committees provide plenty of oversight and monthly
reporting.  A lot of the work will be gathering data and creating solid
materials that projects or other officers can choose to use to help
improve our communities, or doing their own direct outreach at
conferences or the like.  Those are all things well suited to a
President's committee with a named VP.


--

- Shane
  Director & Member
  The Apache Software Foundation

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Why should D be a president's committee?

[Shane Curcuru]

The most important question is: where do the people who are currently
most active doing the real work of the survey and organizing
informational materials on diversity@ want to do that work?  Ensuring
they have a productive space and framework to work is the first thing to
solve.   That said...

Myrle Krantz wrote on 5/1/19 7:06 AM:
...snip...
> * Make it a sub-committee of ComDev.

This is nothing more than a page on community.a.o and the diversity@
mailing list.  We already effectively have that.  The only difference
would be having a formal page on the website that lists who's there,
essentially copying what we've done in the mailing list.

In terms of powers, none in particular.  Membership changes by the PMC
voting in new PMC members (or allowing committers to participate, etc.)
 Reports would be part of the quarterly ComDev report.

> * Make it a president's committee.

The proposal is to also name a VP of that committee as well.  The VP is
an officer, and can perform duties for the ASF within the scope of
whatever charter the board originally creates the VP officer with.

Historically, we've had the board create *new VP roles* with a title and
description, and appoint the first person to that role.  For President's
committees and other VPs reporting to the President, we've had the
President thereafter simply make new appointments to existing roles
directly (always reported in board reports).

President's committees can be changed by the President at any point, or
by the VP in charge if specifically authorized to do so.  Also, since
President's committees are mostly about operations, we have examples of
officers like this having regular annual budgets and signing authority.

They cannot release software (publicly).  They could have a separate
website and mailing lists.  President's committees report monthly.

> * Make it it's own PMC.

This requires a normal board resolution, and would act like any other
PMC, especially in terms of managing PMC or committer membership.  We've
done straight-to-PMC before (i.e. not going through Incubation), it just
needs the scope description of the PMC and the list of VP and members.

They could release software and all the usual PMC things, and they
report to the board quarterly.



Elsethread, Mark also mentioned a board committee.  They have the powers
of the board.  Changing board committees (normally) takes a board
resolution, meaning it takes more time to add/remove people.  They
report monthly to the board.

While President's committees have a broad scope of operations, often
looking across the whole ASF, they do not have direct power to generally
set policies across other projects.  Board committees, on the other
hand, could directly enact and enforce policies across projects.



Personally, I'm +1 for a President's committee.  Right now, we need a
place where people actively doing productive work can do so.
President's committees provide plenty of oversight and monthly
reporting.  A lot of the work will be gathering data and creating solid
materials that projects or other officers can choose to use to help
improve our communities, or doing their own direct outreach at
conferences or the like.  Those are all things well suited to a
President's committee with a named VP.


-- 

- Shane
  Director & Member
  The Apache Software Foundation

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Why should D be a president's committee?

[Mark Thomas]

On 01/05/2019 12:06, Myrle Krantz wrote:
> When talking about formalizing our D effort, there have been essentially
> three options under discussion:
> 
> * Make it a sub-committee of ComDev.
> * Make it a president's committee.
> * Make it it's own PMC.
> 
> The current proposal is to make it a president's committee.
> 
> I'm not sure what the advantages and disadvantages of each approach is.
> I'd appreciate your thoughts.  What do the powers, freedoms, and
> responsibilities of a committee look in each of these alternatives?  What
> are the advantages and disadvantages with respect to our goals with D?

>From a "Demonstrating the ASF is taking D seriously" PoV I think D
needs to be on every board agenda. That means it needs to report the
board every month.

Of the options above, only a president's committee meets that criteria.

A board committee would also meet that criteria.

Broadly, responsibilities only vary by reporting process / frequency.

In terms of powers, I think any of the proposed structures above would
provide the necessary authority since part of forming the structure
would involve delegating powers.

A board committee has significantly more power. It can do *anything* the
board can do (it also requires that a board member is on the committee).
I don't think the additional authority is necessary but I do wonder if
reporting directly to the board (rather than through the president)
would enhance the "The ASF is taking D seriously" message.

Mark

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: Why should D be a president's committee?

[Jim Jagielski]

> On May 1, 2019, at 7:06 AM, Myrle Krantz  wrote:
> 
> 
> (Jim, this is an area you should be able to help us shine a light on, given
> your extensive experience at the ASF.  You are explicitly invited to
> participate.)

Thx for the invite but I know that any input I'd provide to be moot.

Cheers!

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Why should D be a president's committee?

[Myrle Krantz]

When talking about formalizing our D effort, there have been essentially
three options under discussion:

* Make it a sub-committee of ComDev.
* Make it a president's committee.
* Make it it's own PMC.

The current proposal is to make it a president's committee.

I'm not sure what the advantages and disadvantages of each approach is.
I'd appreciate your thoughts.  What do the powers, freedoms, and
responsibilities of a committee look in each of these alternatives?  What
are the advantages and disadvantages with respect to our goals with D?

Thanks,
Myrle

(Jim, this is an area you should be able to help us shine a light on, given
your extensive experience at the ASF.  You are explicitly invited to
participate.)

Re: Requesting the creation of a Diversity and Inclusion committee reporting to the President

[Bertrand Delacretaz]

On Tue, Apr 30, 2019 at 5:27 PM Ross Gardler
 wrote:
> ...Com Dev we intend to move the D responsibility to a separate Presidents 
> committee

I like the idea, big +1 to this.

I won't get into discussions about who's holier than others, though ;-)

-Bertrand

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org