Re: ASF Application for Google Season of Docs 2019
That's great Dinesh. Thanks Sharan On 2019/04/03 05:35:25, Dinesh Joshi wrote: > I have reached out to them seeking clarification. Will let you all know when > I hear back. > > Dinesh > > > On Apr 2, 2019, at 10:33 PM, Sharan Foga wrote: > > > > Hi Aizhamal > > > > The rules are that a maximum of 2 technical writers will be allocated per > > organisation - and we are asking for the maximum. This is a Google > > constraint not ours. And even though we have asked for 2, if accepted there > > is also the possibility that we get allocated only 1. > > > > My thought is that unlike GSoC where there are lots of students wanting to > > apply and participate, there is only a limited number of technical writers > > available so to ensure accepted organisations get at least one writer - it > > is being limited. > > > > Thanks > > Sharan > > > > On 2019/04/02 21:57:20, Aizhamal Nurmamat kyzy > > wrote: > >> Hi Sharan, > >> > >> We plan to prepare ideas list for at least 2 Apache projects, in particular > >> for Airflow, Beam and possibly Spark. I am sure there are other projects > >> that would like to participate, therefore I’m wondering whether 2 tech > >> writers will be enough? Can we ask for more? > >> > >> I’m happy to chat further to figure out what’s the best course of action. > >> > >> Thanks, > >> Aizhamal > >> > >> > >> On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: > >> > >>> Hi All > >>> > >>> As mentioned the applications for the Google Season of Docs opened today > >>> and I'm working my way through it on behalf of the ASF. > >>> > >>> If accepted, we will be allocated either one or two techical writers. > >>> Google will also pay the ASF a stipend of $500 per technical writer > >>> mentored (which I hope can go directly to fundraising :-) > >>> > >>> Each project that wants to participate must provide two mentors for each > >>> documentation project. > >>> > >>> As part of the application process there are a few things that we need to > >>> setup. > >>> > >>> 1. Season of Docs Page and List of Project Ideas > >>> We need to create a public webpage about Season of Docs that contains the > >>> list of project ideas for documentation. I have created a page on the > >>> ComDev wiki https://s.apache.org/w4CH with a table for projects to > >>> record their ideas. > >>> > >>> 2. Alternative administrator. > >>> I’ve set myself up as the primary admin and Maxim as the alternative admin > >>> (Maxim, I need to confirm your contact email and you will also need to > >>> register as the alternative admin and I will email you the link offline) > >>> > >>> 3. Mentors > >>> All mentors from the projects interested in participating must register > >>> individually at the following link : https://forms.gle/a1x26WQGzURLerv66. > >>> > >>> 4. Application Form: Documentation / Technnial Writer Collaboration > >>> There is a section to fill in about experience with documentation and any > >>> previous collaboration with technical writers. I know a few projects have > >>> used various tools for documentation - but not sure about any technical > >>> writing collaboration (so if you know of any then please let me know) > >>> > >>> 5. Application Form: GSoC > >>> There is a section to complete at our participation in GSoC.I think I have > >>> the details from our application this year so can follow up with Maxim or > >>> Uli about it > >>> > >>> This is all I have at the moment and we have until the 23rd April 2019 to > >>> finalise all the application details. Ideally I want to have it done well > >>> before then :-) > >>> > >>> Please pass on this information within your various projects and as with > >>> GSoC - I'll see how we can get this information out to all our project > >>> mailing lists. > >>> > >>> Thanks > >>> Sharan > >>> > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >>> For additional commands, e-mail: dev-h...@community.apache.org > >>> > >>> -- > >> > >> *Aizhamal Nurmamat kyzy* > >> > >> Open Source Program Manager > >> > >> 646-355-9740 Mobile > >> > >> 601 North 34th Street, Seattle, WA 98103 > >> > > > > - > > 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 > > - 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
I have reached out to them seeking clarification. Will let you all know when I hear back. Dinesh > On Apr 2, 2019, at 10:33 PM, Sharan Foga wrote: > > Hi Aizhamal > > The rules are that a maximum of 2 technical writers will be allocated per > organisation - and we are asking for the maximum. This is a Google constraint > not ours. And even though we have asked for 2, if accepted there is also the > possibility that we get allocated only 1. > > My thought is that unlike GSoC where there are lots of students wanting to > apply and participate, there is only a limited number of technical writers > available so to ensure accepted organisations get at least one writer - it is > being limited. > > Thanks > Sharan > > On 2019/04/02 21:57:20, Aizhamal Nurmamat kyzy > wrote: >> Hi Sharan, >> >> We plan to prepare ideas list for at least 2 Apache projects, in particular >> for Airflow, Beam and possibly Spark. I am sure there are other projects >> that would like to participate, therefore I’m wondering whether 2 tech >> writers will be enough? Can we ask for more? >> >> I’m happy to chat further to figure out what’s the best course of action. >> >> Thanks, >> Aizhamal >> >> >> On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: >> >>> Hi All >>> >>> As mentioned the applications for the Google Season of Docs opened today >>> and I'm working my way through it on behalf of the ASF. >>> >>> If accepted, we will be allocated either one or two techical writers. >>> Google will also pay the ASF a stipend of $500 per technical writer >>> mentored (which I hope can go directly to fundraising :-) >>> >>> Each project that wants to participate must provide two mentors for each >>> documentation project. >>> >>> As part of the application process there are a few things that we need to >>> setup. >>> >>> 1. Season of Docs Page and List of Project Ideas >>> We need to create a public webpage about Season of Docs that contains the >>> list of project ideas for documentation. I have created a page on the >>> ComDev wiki https://s.apache.org/w4CH with a table for projects to >>> record their ideas. >>> >>> 2. Alternative administrator. >>> I’ve set myself up as the primary admin and Maxim as the alternative admin >>> (Maxim, I need to confirm your contact email and you will also need to >>> register as the alternative admin and I will email you the link offline) >>> >>> 3. Mentors >>> All mentors from the projects interested in participating must register >>> individually at the following link : https://forms.gle/a1x26WQGzURLerv66. >>> >>> 4. Application Form: Documentation / Technnial Writer Collaboration >>> There is a section to fill in about experience with documentation and any >>> previous collaboration with technical writers. I know a few projects have >>> used various tools for documentation - but not sure about any technical >>> writing collaboration (so if you know of any then please let me know) >>> >>> 5. Application Form: GSoC >>> There is a section to complete at our participation in GSoC.I think I have >>> the details from our application this year so can follow up with Maxim or >>> Uli about it >>> >>> This is all I have at the moment and we have until the 23rd April 2019 to >>> finalise all the application details. Ideally I want to have it done well >>> before then :-) >>> >>> Please pass on this information within your various projects and as with >>> GSoC - I'll see how we can get this information out to all our project >>> mailing lists. >>> >>> Thanks >>> Sharan >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >>> -- >> >> *Aizhamal Nurmamat kyzy* >> >> Open Source Program Manager >> >> 646-355-9740 Mobile >> >> 601 North 34th Street, Seattle, WA 98103 >> > > - > 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
Hi Aizhamal The rules are that a maximum of 2 technical writers will be allocated per organisation - and we are asking for the maximum. This is a Google constraint not ours. And even though we have asked for 2, if accepted there is also the possibility that we get allocated only 1. My thought is that unlike GSoC where there are lots of students wanting to apply and participate, there is only a limited number of technical writers available so to ensure accepted organisations get at least one writer - it is being limited. Thanks Sharan On 2019/04/02 21:57:20, Aizhamal Nurmamat kyzy wrote: > Hi Sharan, > > We plan to prepare ideas list for at least 2 Apache projects, in particular > for Airflow, Beam and possibly Spark. I am sure there are other projects > that would like to participate, therefore I’m wondering whether 2 tech > writers will be enough? Can we ask for more? > > I’m happy to chat further to figure out what’s the best course of action. > > Thanks, > Aizhamal > > > On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: > > > Hi All > > > > As mentioned the applications for the Google Season of Docs opened today > > and I'm working my way through it on behalf of the ASF. > > > > If accepted, we will be allocated either one or two techical writers. > > Google will also pay the ASF a stipend of $500 per technical writer > > mentored (which I hope can go directly to fundraising :-) > > > > Each project that wants to participate must provide two mentors for each > > documentation project. > > > > As part of the application process there are a few things that we need to > > setup. > > > > 1. Season of Docs Page and List of Project Ideas > > We need to create a public webpage about Season of Docs that contains the > > list of project ideas for documentation. I have created a page on the > > ComDev wiki https://s.apache.org/w4CH with a table for projects to > > record their ideas. > > > > 2. Alternative administrator. > > I’ve set myself up as the primary admin and Maxim as the alternative admin > > (Maxim, I need to confirm your contact email and you will also need to > > register as the alternative admin and I will email you the link offline) > > > > 3. Mentors > > All mentors from the projects interested in participating must register > > individually at the following link : https://forms.gle/a1x26WQGzURLerv66. > > > > 4. Application Form: Documentation / Technnial Writer Collaboration > > There is a section to fill in about experience with documentation and any > > previous collaboration with technical writers. I know a few projects have > > used various tools for documentation - but not sure about any technical > > writing collaboration (so if you know of any then please let me know) > > > > 5. Application Form: GSoC > > There is a section to complete at our participation in GSoC.I think I have > > the details from our application this year so can follow up with Maxim or > > Uli about it > > > > This is all I have at the moment and we have until the 23rd April 2019 to > > finalise all the application details. Ideally I want to have it done well > > before then :-) > > > > Please pass on this information within your various projects and as with > > GSoC - I'll see how we can get this information out to all our project > > mailing lists. > > > > Thanks > > Sharan > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > -- > > *Aizhamal Nurmamat kyzy* > > Open Source Program Manager > > 646-355-9740 Mobile > > 601 North 34th Street, Seattle, WA 98103 > - 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
On 2019/04/03 04:47:24, Maxim Solodovnik wrote: > Hello Dinesh, > > According to > https://developers.google.com/season-of-docs/terms/program-rules > 1.13 "*Organization*" means the open source organization that registers for > the Program as an organization. > > I believe this is the ASF > > Sharan could you clarify? > Yes - this is my understanding as well. Also parts of the application make reference to GSoC and it is the ASF as an organisation that registers for GSoC even though many projects participate in it. Thanks Sharan > On Wed, 3 Apr 2019 at 11:44, Dinesh Joshi > wrote: > > > I am slightly confused here. I believe each ASF project that wishes to > > participate can qualify as an organization. If the whole of ASF were to be > > enrolled as an organization, that would limit the ASF to 1 technical > > writer. Can someone please clarify what the rules are? > > > > Dinesh > > > > > On Apr 2, 2019, at 8:31 PM, Maxim Solodovnik > > wrote: > > > > > > If I'm not mistaken rules are: > > > one tech writer - 2 mentors > > > > > > So I doubt all proposals will be covered > > > We have to wisely choose best proposals, and hopefully next year we will > > > get more tech writers > > > > > > On Wed, 3 Apr 2019 at 04:57, Aizhamal Nurmamat kyzy > > > wrote: > > > > > >> Hi Sharan, > > >> > > >> We plan to prepare ideas list for at least 2 Apache projects, in > > particular > > >> for Airflow, Beam and possibly Spark. I am sure there are other projects > > >> that would like to participate, therefore I’m wondering whether 2 tech > > >> writers will be enough? Can we ask for more? > > >> > > >> I’m happy to chat further to figure out what’s the best course of > > action. > > >> > > >> Thanks, > > >> Aizhamal > > >> > > >> > > >> On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: > > >> > > >>> Hi All > > >>> > > >>> As mentioned the applications for the Google Season of Docs opened > > today > > >>> and I'm working my way through it on behalf of the ASF. > > >>> > > >>> If accepted, we will be allocated either one or two techical writers. > > >>> Google will also pay the ASF a stipend of $500 per technical writer > > >>> mentored (which I hope can go directly to fundraising :-) > > >>> > > >>> Each project that wants to participate must provide two mentors for > > each > > >>> documentation project. > > >>> > > >>> As part of the application process there are a few things that we need > > to > > >>> setup. > > >>> > > >>> 1. Season of Docs Page and List of Project Ideas > > >>> We need to create a public webpage about Season of Docs that contains > > the > > >>> list of project ideas for documentation. I have created a page on the > > >>> ComDev wiki https://s.apache.org/w4CH with a table for projects to > > >>> record their ideas. > > >>> > > >>> 2. Alternative administrator. > > >>> I’ve set myself up as the primary admin and Maxim as the alternative > > >> admin > > >>> (Maxim, I need to confirm your contact email and you will also need to > > >>> register as the alternative admin and I will email you the link > > offline) > > >>> > > >>> 3. Mentors > > >>> All mentors from the projects interested in participating must register > > >>> individually at the following link : > > https://forms.gle/a1x26WQGzURLerv66 > > >> . > > >>> > > >>> 4. Application Form: Documentation / Technnial Writer Collaboration > > >>> There is a section to fill in about experience with documentation and > > any > > >>> previous collaboration with technical writers. I know a few projects > > have > > >>> used various tools for documentation - but not sure about any technical > > >>> writing collaboration (so if you know of any then please let me know) > > >>> > > >>> 5. Application Form: GSoC > > >>> There is a section to complete at our participation in GSoC.I think I > > >> have > > >>> the details from our application this year so can follow up with Maxim > > or > > >>> Uli about it > > >>> > > >>> This is all I have at the moment and we have until the 23rd April 2019 > > to > > >>> finalise all the application details. Ideally I want to have it done > > well > > >>> before then :-) > > >>> > > >>> Please pass on this information within your various projects and as > > with > > >>> GSoC - I'll see how we can get this information out to all our project > > >>> mailing lists. > > >>> > > >>> Thanks > > >>> Sharan > > >>> > > >>> > > >>> > > >>> - > > >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > >>> For additional commands, e-mail: dev-h...@community.apache.org > > >>> > > >>> -- > > >> > > >> *Aizhamal Nurmamat kyzy* > > >> > > >> Open Source Program Manager > > >> > > >> 646-355-9740 Mobile > > >> > > >> 601 North 34th Street, Seattle, WA 98103 > > >> > > > > > > > > > -- > > > WBR > > > Maxim aka solomax > > > > > > - > > To unsubscribe, e-mail:
Fwd: Request for Interview Participants
I've seen a couple of threads about this sort of unsolicited email. Is there an easy "what to do" doc my colleagues or I could follow? I am especially perturbed because this went to u...@beam.apache.org. Kenn -- Forwarded message - From: Amber Horvath Date: Sun, Mar 31, 2019 at 4:49 PM Subject: Request for Interview Participants To: To Whom it May Concern, Hi, my name is Amber Horvath and I’m a first year graduate student in Carnegie Mellon University’s Human Computer Interaction Institute. I’m studying the perceived usability of Apache Beam as part of a larger study of API usability. I’m interested in possibly recruiting some users of Apache Beam through this mailing list to partake in an interview on your usage of Apache Beam. The interview will cover questions relating to your mental model of Apache Beam, how you have used Apache Beam, what functionalities of the API you use most frequently and least frequently, and how you integrate Apache Beam into your larger data stack. The interview would be recorded and you would be compensated for $10 an hour, with the interview not taking any longer than 2 hours. Thank you for your time and please let me know if you are interested or would like more information! Amber Horvath
Re: ASF Application for Google Season of Docs 2019
I am slightly confused here. I believe each ASF project that wishes to participate can qualify as an organization. If the whole of ASF were to be enrolled as an organization, that would limit the ASF to 1 technical writer. Can someone please clarify what the rules are? Dinesh > On Apr 2, 2019, at 8:31 PM, Maxim Solodovnik wrote: > > If I'm not mistaken rules are: > one tech writer - 2 mentors > > So I doubt all proposals will be covered > We have to wisely choose best proposals, and hopefully next year we will > get more tech writers > > On Wed, 3 Apr 2019 at 04:57, Aizhamal Nurmamat kyzy > wrote: > >> Hi Sharan, >> >> We plan to prepare ideas list for at least 2 Apache projects, in particular >> for Airflow, Beam and possibly Spark. I am sure there are other projects >> that would like to participate, therefore I’m wondering whether 2 tech >> writers will be enough? Can we ask for more? >> >> I’m happy to chat further to figure out what’s the best course of action. >> >> Thanks, >> Aizhamal >> >> >> On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: >> >>> Hi All >>> >>> As mentioned the applications for the Google Season of Docs opened today >>> and I'm working my way through it on behalf of the ASF. >>> >>> If accepted, we will be allocated either one or two techical writers. >>> Google will also pay the ASF a stipend of $500 per technical writer >>> mentored (which I hope can go directly to fundraising :-) >>> >>> Each project that wants to participate must provide two mentors for each >>> documentation project. >>> >>> As part of the application process there are a few things that we need to >>> setup. >>> >>> 1. Season of Docs Page and List of Project Ideas >>> We need to create a public webpage about Season of Docs that contains the >>> list of project ideas for documentation. I have created a page on the >>> ComDev wiki https://s.apache.org/w4CH with a table for projects to >>> record their ideas. >>> >>> 2. Alternative administrator. >>> I’ve set myself up as the primary admin and Maxim as the alternative >> admin >>> (Maxim, I need to confirm your contact email and you will also need to >>> register as the alternative admin and I will email you the link offline) >>> >>> 3. Mentors >>> All mentors from the projects interested in participating must register >>> individually at the following link : https://forms.gle/a1x26WQGzURLerv66 >> . >>> >>> 4. Application Form: Documentation / Technnial Writer Collaboration >>> There is a section to fill in about experience with documentation and any >>> previous collaboration with technical writers. I know a few projects have >>> used various tools for documentation - but not sure about any technical >>> writing collaboration (so if you know of any then please let me know) >>> >>> 5. Application Form: GSoC >>> There is a section to complete at our participation in GSoC.I think I >> have >>> the details from our application this year so can follow up with Maxim or >>> Uli about it >>> >>> This is all I have at the moment and we have until the 23rd April 2019 to >>> finalise all the application details. Ideally I want to have it done well >>> before then :-) >>> >>> Please pass on this information within your various projects and as with >>> GSoC - I'll see how we can get this information out to all our project >>> mailing lists. >>> >>> Thanks >>> Sharan >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >>> For additional commands, e-mail: dev-h...@community.apache.org >>> >>> -- >> >> *Aizhamal Nurmamat kyzy* >> >> Open Source Program Manager >> >> 646-355-9740 Mobile >> >> 601 North 34th Street, Seattle, WA 98103 >> > > > -- > WBR > Maxim aka solomax - 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
If I'm not mistaken rules are: one tech writer - 2 mentors So I doubt all proposals will be covered We have to wisely choose best proposals, and hopefully next year we will get more tech writers On Wed, 3 Apr 2019 at 04:57, Aizhamal Nurmamat kyzy wrote: > Hi Sharan, > > We plan to prepare ideas list for at least 2 Apache projects, in particular > for Airflow, Beam and possibly Spark. I am sure there are other projects > that would like to participate, therefore I’m wondering whether 2 tech > writers will be enough? Can we ask for more? > > I’m happy to chat further to figure out what’s the best course of action. > > Thanks, > Aizhamal > > > On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: > > > Hi All > > > > As mentioned the applications for the Google Season of Docs opened today > > and I'm working my way through it on behalf of the ASF. > > > > If accepted, we will be allocated either one or two techical writers. > > Google will also pay the ASF a stipend of $500 per technical writer > > mentored (which I hope can go directly to fundraising :-) > > > > Each project that wants to participate must provide two mentors for each > > documentation project. > > > > As part of the application process there are a few things that we need to > > setup. > > > > 1. Season of Docs Page and List of Project Ideas > > We need to create a public webpage about Season of Docs that contains the > > list of project ideas for documentation. I have created a page on the > > ComDev wiki https://s.apache.org/w4CH with a table for projects to > > record their ideas. > > > > 2. Alternative administrator. > > I’ve set myself up as the primary admin and Maxim as the alternative > admin > > (Maxim, I need to confirm your contact email and you will also need to > > register as the alternative admin and I will email you the link offline) > > > > 3. Mentors > > All mentors from the projects interested in participating must register > > individually at the following link : https://forms.gle/a1x26WQGzURLerv66 > . > > > > 4. Application Form: Documentation / Technnial Writer Collaboration > > There is a section to fill in about experience with documentation and any > > previous collaboration with technical writers. I know a few projects have > > used various tools for documentation - but not sure about any technical > > writing collaboration (so if you know of any then please let me know) > > > > 5. Application Form: GSoC > > There is a section to complete at our participation in GSoC.I think I > have > > the details from our application this year so can follow up with Maxim or > > Uli about it > > > > This is all I have at the moment and we have until the 23rd April 2019 to > > finalise all the application details. Ideally I want to have it done well > > before then :-) > > > > Please pass on this information within your various projects and as with > > GSoC - I'll see how we can get this information out to all our project > > mailing lists. > > > > Thanks > > Sharan > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > -- > > *Aizhamal Nurmamat kyzy* > > Open Source Program Manager > > 646-355-9740 Mobile > > 601 North 34th Street, Seattle, WA 98103 > -- WBR Maxim aka solomax
Re: {Action by April 5] Vote on best time for the D committee discussion call
On Tue, Apr 2, 2019 at 7:44 PM Griselda Cuevas wrote: > To the point of no calls... > > How does the board meet and make decisions? That's a very fair question. The board practice is to assemble all of the reports, suggested motions etc days and sometimes weeks before the synchronous meeting. That meeting is recorded with minutes for dissemination for everyone who isn't attending. Less the redacted bits, these are approved a month or two later and published openly for the record. We can all ready 20 years of them here; http://apache.org/foundation/board/calendar.html There is almost nothing presented to the board that wasn't already before them and the membership for some significant time in advance, so the inclusiveness aspect is satisfied. Now, as an operating board, these aren't truly "public" discussions, only officers and members, who number over 700, have any visibility into some early discussion. But many matters which are brought to the board's attention arise from discussions which are public on various -dev and discuss lists, and corresponding votes on committee internal discussion lists. Ultimately and to an outgoing AU board participant's frustration, the meetings are synchronous and set comfortably in a US timezone. But this is mostly a side-effect of US corporate governance, there was no "accepted" framework for async electronic meetings at the time the foundation was created. Effectively, the board isn't going to pop any surprise on the membership, because their agenda was laid out days and often months in advance on the mailing lists, votes had been taken by project committees, and comments on business before them are already received.
Re: {Action by April 5] Vote on best time for the D committee discussion call
To the point of no calls... How does the board meet and make decisions? On Tue, Apr 2, 2019, 5:43 PM Griselda Cuevas wrote: > Sam suggested a call, so that's why I initiated. > > > I think a call will help work out quickly a document we can socialize in > the mailing list. > > > > On Tue, Apr 2, 2019, 1:27 PM Jim Jagielski wrote: > >> Can I recommend instead of a call, using the newly created >> mailing list... In general, Apache tries to avoid the use of >> sync communication medium except when absolutely required. >> >> I think that esp for such a topic as D, starting the effort off >> using a method that inherently disenfranchises people may >> not be the wisest 1st step :) >> >> Cheers! >> >> > On Apr 2, 2019, at 3:53 PM, Griselda Cuevas >> wrote: >> > >> > Hi everyone, >> > >> > Following up the original thread that sparked the creation of a >> Diversity & >> > Inclusion committee in the ASF [1], I'm coordinating a call/videocall to >> > discuss the proposal details to the board. >> > >> > *Action by April 5th, 2019 @ midnight PST* >> > If you're interested in being part of the committee and shaping the >> request >> > to the board, add your availability in this Doodle*: >> > https://doodle.com/poll/52cce5zh77avryri >> > >> > *If you don't know how to use Doodle, read this: >> > https://help.doodle.com/hc/en-us/articles/360012150073 >> > >> > [1] >> > >> https://lists.apache.org/thread.html/5b88a314fd28ec3753fd9aa57fdf815fe9f7a64c5f60fb00e2d25bcf@%3Cdev.community.apache.org%3E >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: {Action by April 5] Vote on best time for the D committee discussion call
Sam suggested a call, so that's why I initiated. I think a call will help work out quickly a document we can socialize in the mailing list. On Tue, Apr 2, 2019, 1:27 PM Jim Jagielski wrote: > Can I recommend instead of a call, using the newly created > mailing list... In general, Apache tries to avoid the use of > sync communication medium except when absolutely required. > > I think that esp for such a topic as D, starting the effort off > using a method that inherently disenfranchises people may > not be the wisest 1st step :) > > Cheers! > > > On Apr 2, 2019, at 3:53 PM, Griselda Cuevas > wrote: > > > > Hi everyone, > > > > Following up the original thread that sparked the creation of a > Diversity & > > Inclusion committee in the ASF [1], I'm coordinating a call/videocall to > > discuss the proposal details to the board. > > > > *Action by April 5th, 2019 @ midnight PST* > > If you're interested in being part of the committee and shaping the > request > > to the board, add your availability in this Doodle*: > > https://doodle.com/poll/52cce5zh77avryri > > > > *If you don't know how to use Doodle, read this: > > https://help.doodle.com/hc/en-us/articles/360012150073 > > > > [1] > > > https://lists.apache.org/thread.html/5b88a314fd28ec3753fd9aa57fdf815fe9f7a64c5f60fb00e2d25bcf@%3Cdev.community.apache.org%3E > > > - > 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
Hi Sharan, We plan to prepare ideas list for at least 2 Apache projects, in particular for Airflow, Beam and possibly Spark. I am sure there are other projects that would like to participate, therefore I’m wondering whether 2 tech writers will be enough? Can we ask for more? I’m happy to chat further to figure out what’s the best course of action. Thanks, Aizhamal On Tue, Apr 2, 2019 at 14:03 Sharan Foga wrote: > Hi All > > As mentioned the applications for the Google Season of Docs opened today > and I'm working my way through it on behalf of the ASF. > > If accepted, we will be allocated either one or two techical writers. > Google will also pay the ASF a stipend of $500 per technical writer > mentored (which I hope can go directly to fundraising :-) > > Each project that wants to participate must provide two mentors for each > documentation project. > > As part of the application process there are a few things that we need to > setup. > > 1. Season of Docs Page and List of Project Ideas > We need to create a public webpage about Season of Docs that contains the > list of project ideas for documentation. I have created a page on the > ComDev wiki https://s.apache.org/w4CH with a table for projects to > record their ideas. > > 2. Alternative administrator. > I’ve set myself up as the primary admin and Maxim as the alternative admin > (Maxim, I need to confirm your contact email and you will also need to > register as the alternative admin and I will email you the link offline) > > 3. Mentors > All mentors from the projects interested in participating must register > individually at the following link : https://forms.gle/a1x26WQGzURLerv66. > > 4. Application Form: Documentation / Technnial Writer Collaboration > There is a section to fill in about experience with documentation and any > previous collaboration with technical writers. I know a few projects have > used various tools for documentation - but not sure about any technical > writing collaboration (so if you know of any then please let me know) > > 5. Application Form: GSoC > There is a section to complete at our participation in GSoC.I think I have > the details from our application this year so can follow up with Maxim or > Uli about it > > This is all I have at the moment and we have until the 23rd April 2019 to > finalise all the application details. Ideally I want to have it done well > before then :-) > > Please pass on this information within your various projects and as with > GSoC - I'll see how we can get this information out to all our project > mailing lists. > > Thanks > Sharan > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > > -- *Aizhamal Nurmamat kyzy* Open Source Program Manager 646-355-9740 Mobile 601 North 34th Street, Seattle, WA 98103
ASF Application for Google Season of Docs 2019
Hi All As mentioned the applications for the Google Season of Docs opened today and I'm working my way through it on behalf of the ASF. If accepted, we will be allocated either one or two techical writers. Google will also pay the ASF a stipend of $500 per technical writer mentored (which I hope can go directly to fundraising :-) Each project that wants to participate must provide two mentors for each documentation project. As part of the application process there are a few things that we need to setup. 1. Season of Docs Page and List of Project Ideas We need to create a public webpage about Season of Docs that contains the list of project ideas for documentation. I have created a page on the ComDev wiki https://s.apache.org/w4CH with a table for projects to record their ideas. 2. Alternative administrator. I’ve set myself up as the primary admin and Maxim as the alternative admin (Maxim, I need to confirm your contact email and you will also need to register as the alternative admin and I will email you the link offline) 3. Mentors All mentors from the projects interested in participating must register individually at the following link : https://forms.gle/a1x26WQGzURLerv66. 4. Application Form: Documentation / Technnial Writer Collaboration There is a section to fill in about experience with documentation and any previous collaboration with technical writers. I know a few projects have used various tools for documentation - but not sure about any technical writing collaboration (so if you know of any then please let me know) 5. Application Form: GSoC There is a section to complete at our participation in GSoC.I think I have the details from our application this year so can follow up with Maxim or Uli about it This is all I have at the moment and we have until the 23rd April 2019 to finalise all the application details. Ideally I want to have it done well before then :-) Please pass on this information within your various projects and as with GSoC - I'll see how we can get this information out to all our project mailing lists. Thanks Sharan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: {Action by April 5] Vote on best time for the D committee discussion call
Can I recommend instead of a call, using the newly created mailing list... In general, Apache tries to avoid the use of sync communication medium except when absolutely required. I think that esp for such a topic as D, starting the effort off using a method that inherently disenfranchises people may not be the wisest 1st step :) Cheers! > On Apr 2, 2019, at 3:53 PM, Griselda Cuevas wrote: > > Hi everyone, > > Following up the original thread that sparked the creation of a Diversity & > Inclusion committee in the ASF [1], I'm coordinating a call/videocall to > discuss the proposal details to the board. > > *Action by April 5th, 2019 @ midnight PST* > If you're interested in being part of the committee and shaping the request > to the board, add your availability in this Doodle*: > https://doodle.com/poll/52cce5zh77avryri > > *If you don't know how to use Doodle, read this: > https://help.doodle.com/hc/en-us/articles/360012150073 > > [1] > https://lists.apache.org/thread.html/5b88a314fd28ec3753fd9aa57fdf815fe9f7a64c5f60fb00e2d25bcf@%3Cdev.community.apache.org%3E - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Google Season of Docs 2019
Hi Trevor The mentors will need to register separately. I will start a new thread and share the required links. Thanks Sharan On 2019/04/02 19:37:48, Trevor Grant wrote: > We have another volunteer to mentor on Apache SDAP-Incubating > > On Tue, Apr 2, 2019 at 12:44 PM dinesh.jo...@yahoo.com.INVALID > wrote: > > > They're taking applications now. > > Dinesh > > > > On Saturday, March 30, 2019, 9:08:50 AM PDT, > > wrote: > > > > Excellent and thanks Maxim! :-) > > > > Thanks > > Sharan > > > > On 30. 03. 19 16:45, Maxim Solodovnik wrote: > > > Hello Sharah > > > > > > I can help :) > > > > > > On Sat, Mar 30, 2019, 22:33 Sharan Foga wrote: > > > > > >> Hi Kenn > > >> > > >> No not yet - applications open on 2nd April and close on 23rd April. > > Will > > >> aim to get a draft together this weekend. > > >> > > >> We also need to have two organisation administrators for GSoD so I am > > >> still looking for another volunteer to help out with that. > > >> > > >> Thanks > > >> Sharan > > >> > > >> On 2019/03/29 23:21:16, Kenneth Knowles wrote: > > >>> Is this taken care of? Did ASF apply? Is there anything more that I > > could > > >>> help with at all? I would also be happy to review anything. > > >>> > > >>> Kenn > > >>> > > >>> On Fri, Mar 22, 2019 at 3:14 AM Sharan Foga wrote: > > >>> > > Hi Dinesh > > > > It's great to hear that the Apache Cassandra community is keen to be > > involved with this. I confirm that I will put an application on behalf > > >> of > > the ASF. > > > > Thanks > > Sharan > > > > On 2019/03/22 07:24:20, Dinesh Joshi > > wrote: > > > Hi all, > > > > > > I am coordinating the GSoD effort in the Apache Cassandra community. > > >> We > > already have a few volunteers willing to help mentor the tech writer. > > >> Who > > can confirm whether ASF is applying as an organization? We will not > > >> apply > > separately. > > > Thanks, > > > > > > Dinesh > > > > > >> On Mar 19, 2019, at 11:11 AM, Aizhamal Nurmamat kyzy > > wrote: > > >> Hi Sharan, > > >> > > >> I'm happy to help with the ASF's application for SoD, if you need > > >> any > > >> support there. > > >> > > >> Thanks, > > >> Aizhamal > > >> > > >> On Mon, Mar 18, 2019 at 3:25 PM Sharan Foga > > >> wrote: > > >>> Hi > > >>> > > >>> ComDev currently manages the ASF applications for GSoC so it might > > make > > >>> sense for us to centralise the application for this too. > > >>> > > >>> We would need 2 people to manage the ASF organisation application > > >> as a > > >>> mentor organisation as well as administer the projects and > > >> mentors. > > >>> If selected then each project participating would need to > > >> guarantee at > > >>> least 2 mentors to work with the technical writer. We currently > > collect > > >>> the GSoC ideas via a JIra so perhaps that could be adapted for > > >> GSoD > > too, > > >>> The timeline is tight - I think 2nd April is when applications > > >> open. > > It > > >>> already sounds like the level of interest is high so we need to > > >> act > > quickly > > >>> if we want to participate. > > >>> > > >>> Thanks > > >>> Sharan > > >>> > > >>> On 2019/03/12 18:14:54, Dave Fisher > > >> wrote: > > Hi - > > > > Looks pretty cool. > > > > Cc: to Apache Community Development. > > > > Regards, > > Dave > > > > Sent from my iPhone > > > > > On Mar 12, 2019, at 9:22 AM, Huxing Zhang > > wrote: > > > Hi, > > > > > > Google Season of Docs 2019[1] seems to be an interesting > > >> project, > > > which bring open source project and technical writer communities > > > together, just Like Google summer of code. > > > > > > I think the Dubbo can benefit from the project, especially the > > English > > > version of documentation could be improved. > > > > > > How do you think? > > > > > > [1] https://developers.google.com/season-of-docs/docs/timeline > > > > > > -- > > > Best Regards！ > > > Huxing > > > > > > >> - > > 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: Google Season of Docs 2019
Hi Dinesh I've started on the ASF application and will start a new thread as there are some things that need to be setup. Thanks Sharan On 2019/04/02 17:44:31, "dinesh.jo...@yahoo.com.INVALID" wrote: > They're taking applications now. > Dinesh > > On Saturday, March 30, 2019, 9:08:50 AM PDT, wrote: > > Excellent and thanks Maxim! :-) > > Thanks > Sharan > > On 30. 03. 19 16:45, Maxim Solodovnik wrote: > > Hello Sharah > > > > I can help :) > > > > On Sat, Mar 30, 2019, 22:33 Sharan Foga wrote: > > > >> Hi Kenn > >> > >> No not yet - applications open on 2nd April and close on 23rd April. Will > >> aim to get a draft together this weekend. > >> > >> We also need to have two organisation administrators for GSoD so I am > >> still looking for another volunteer to help out with that. > >> > >> Thanks > >> Sharan > >> > >> On 2019/03/29 23:21:16, Kenneth Knowles wrote: > >>> Is this taken care of? Did ASF apply? Is there anything more that I could > >>> help with at all? I would also be happy to review anything. > >>> > >>> Kenn > >>> > >>> On Fri, Mar 22, 2019 at 3:14 AM Sharan Foga wrote: > >>> > Hi Dinesh > > It's great to hear that the Apache Cassandra community is keen to be > involved with this. I confirm that I will put an application on behalf > >> of > the ASF. > > Thanks > Sharan > > On 2019/03/22 07:24:20, Dinesh Joshi > wrote: > > Hi all, > > > > I am coordinating the GSoD effort in the Apache Cassandra community. > >> We > already have a few volunteers willing to help mentor the tech writer. > >> Who > can confirm whether ASF is applying as an organization? We will not > >> apply > separately. > > Thanks, > > > > Dinesh > > > >> On Mar 19, 2019, at 11:11 AM, Aizhamal Nurmamat kyzy > wrote: > >> Hi Sharan, > >> > >> I'm happy to help with the ASF's application for SoD, if you need > >> any > >> support there. > >> > >> Thanks, > >> Aizhamal > >> > >> On Mon, Mar 18, 2019 at 3:25 PM Sharan Foga > >> wrote: > >>> Hi > >>> > >>> ComDev currently manages the ASF applications for GSoC so it might > make > >>> sense for us to centralise the application for this too. > >>> > >>> We would need 2 people to manage the ASF organisation application > >> as a > >>> mentor organisation as well as administer the projects and > >> mentors. > >>> If selected then each project participating would need to > >> guarantee at > >>> least 2 mentors to work with the technical writer. We currently > collect > >>> the GSoC ideas via a JIra so perhaps that could be adapted for > >> GSoD > too, > >>> The timeline is tight - I think 2nd April is when applications > >> open. > It > >>> already sounds like the level of interest is high so we need to > >> act > quickly > >>> if we want to participate. > >>> > >>> Thanks > >>> Sharan > >>> > >>> On 2019/03/12 18:14:54, Dave Fisher > >> wrote: > Hi - > > Looks pretty cool. > > Cc: to Apache Community Development. > > Regards, > Dave > > Sent from my iPhone > > > On Mar 12, 2019, at 9:22 AM, Huxing Zhang > wrote: > > Hi, > > > > Google Season of Docs 2019[1] seems to be an interesting > >> project, > > which bring open source project and technical writer communities > > together, just Like Google summer of code. > > > > I think the Dubbo can benefit from the project, especially the > English > > version of documentation could be improved. > > > > How do you think? > > > > [1] https://developers.google.com/season-of-docs/docs/timeline > > > > -- > > Best Regards！ > > Huxing > > > >> - > 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 > >>> > >>> > > > > - > > 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 > > > >>
{Action by April 5] Vote on best time for the D committee discussion call
Hi everyone, Following up the original thread that sparked the creation of a Diversity & Inclusion committee in the ASF [1], I'm coordinating a call/videocall to discuss the proposal details to the board. *Action by April 5th, 2019 @ midnight PST* If you're interested in being part of the committee and shaping the request to the board, add your availability in this Doodle*: https://doodle.com/poll/52cce5zh77avryri *If you don't know how to use Doodle, read this: https://help.doodle.com/hc/en-us/articles/360012150073 [1] https://lists.apache.org/thread.html/5b88a314fd28ec3753fd9aa57fdf815fe9f7a64c5f60fb00e2d25bcf@%3Cdev.community.apache.org%3E
Re: Google Season of Docs 2019
We have another volunteer to mentor on Apache SDAP-Incubating On Tue, Apr 2, 2019 at 12:44 PM dinesh.jo...@yahoo.com.INVALID wrote: > They're taking applications now. > Dinesh > > On Saturday, March 30, 2019, 9:08:50 AM PDT, > wrote: > > Excellent and thanks Maxim! :-) > > Thanks > Sharan > > On 30. 03. 19 16:45, Maxim Solodovnik wrote: > > Hello Sharah > > > > I can help :) > > > > On Sat, Mar 30, 2019, 22:33 Sharan Foga wrote: > > > >> Hi Kenn > >> > >> No not yet - applications open on 2nd April and close on 23rd April. > Will > >> aim to get a draft together this weekend. > >> > >> We also need to have two organisation administrators for GSoD so I am > >> still looking for another volunteer to help out with that. > >> > >> Thanks > >> Sharan > >> > >> On 2019/03/29 23:21:16, Kenneth Knowles wrote: > >>> Is this taken care of? Did ASF apply? Is there anything more that I > could > >>> help with at all? I would also be happy to review anything. > >>> > >>> Kenn > >>> > >>> On Fri, Mar 22, 2019 at 3:14 AM Sharan Foga wrote: > >>> > Hi Dinesh > > It's great to hear that the Apache Cassandra community is keen to be > involved with this. I confirm that I will put an application on behalf > >> of > the ASF. > > Thanks > Sharan > > On 2019/03/22 07:24:20, Dinesh Joshi > wrote: > > Hi all, > > > > I am coordinating the GSoD effort in the Apache Cassandra community. > >> We > already have a few volunteers willing to help mentor the tech writer. > >> Who > can confirm whether ASF is applying as an organization? We will not > >> apply > separately. > > Thanks, > > > > Dinesh > > > >> On Mar 19, 2019, at 11:11 AM, Aizhamal Nurmamat kyzy > wrote: > >> Hi Sharan, > >> > >> I'm happy to help with the ASF's application for SoD, if you need > >> any > >> support there. > >> > >> Thanks, > >> Aizhamal > >> > >> On Mon, Mar 18, 2019 at 3:25 PM Sharan Foga > >> wrote: > >>> Hi > >>> > >>> ComDev currently manages the ASF applications for GSoC so it might > make > >>> sense for us to centralise the application for this too. > >>> > >>> We would need 2 people to manage the ASF organisation application > >> as a > >>> mentor organisation as well as administer the projects and > >> mentors. > >>> If selected then each project participating would need to > >> guarantee at > >>> least 2 mentors to work with the technical writer. We currently > collect > >>> the GSoC ideas via a JIra so perhaps that could be adapted for > >> GSoD > too, > >>> The timeline is tight - I think 2nd April is when applications > >> open. > It > >>> already sounds like the level of interest is high so we need to > >> act > quickly > >>> if we want to participate. > >>> > >>> Thanks > >>> Sharan > >>> > >>> On 2019/03/12 18:14:54, Dave Fisher > >> wrote: > Hi - > > Looks pretty cool. > > Cc: to Apache Community Development. > > Regards, > Dave > > Sent from my iPhone > > > On Mar 12, 2019, at 9:22 AM, Huxing Zhang > wrote: > > Hi, > > > > Google Season of Docs 2019[1] seems to be an interesting > >> project, > > which bring open source project and technical writer communities > > together, just Like Google summer of code. > > > > I think the Dubbo can benefit from the project, especially the > English > > version of documentation could be improved. > > > > How do you think? > > > > [1] https://developers.google.com/season-of-docs/docs/timeline > > > > -- > > Best Regards！ > > Huxing > > > >> - > 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 > >>> > >>> > > > > - > > 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 > > > >> - > >> To unsubscribe, e-mail:
Re: on "meritocracy"
Craig, I was tempted to ask the same but in reverse re divers...@apache.org. I am wary of dropping the "inclusion" aspect. On Tue, 2 Apr 2019 at 19:48, Craig Russell wrote: > Before we get locked into this JIRA, could we consider changing its name > to DIVERSITY instead of DI ? > > Craig > > > On Apr 2, 2019, at 10:06 AM, Griselda Cuevas > wrote: > > > > @joan - I also get a Pony, I requested the Jira ;) > > > > On Tue, Apr 2, 2019, 10:03 AM Joan Touzet wrote: > > > >> > >> > >> > >> Daniel wrote: > >> > >>> Requested, and should be ready within an hour or two. > >> > >> Thank you! You get a pony! > >> > >> -Joan "JFDI" Touzet > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> For additional commands, e-mail: dev-h...@community.apache.org > >> > >> > > Craig Russell > Member, Apache Incubator PMC > apache@gmail.com > > > >
Re: on "meritocracy"
Outreachy is great and we should add that to a list of things to look into re our efforts, working with them, etc. I met Karen Sandler in person once and she is good people. On Tue, 2 Apr 2019 at 19:56, William A Rowe Jr wrote: > On Sun, Mar 31, 2019 at 2:59 PM Mark Thomas wrote: > > > I asked the D folks at $dayjob for some advice / suggestions and got > > back the following: > > > > 1. Mozilla have been doing some work in this area. It was suggested we > > reach out to them to get the benefit of their experience. Anyone have > > any contacts there? > > > If you are interested in parallel and active projects, the Women outreach > SIG > within the GNOME project is a really interesting and successful case study. > > I haven't tracked them in real-time, so I'm surprised/pleased by one > particular fruit of their efforts; https://en.wikipedia.org/wiki/Outreachy > which Mozilla too turns out to be a huge champion of. The history topic > on that page plus footnotes are useful starting points. >
Re: on "meritocracy"
On Sun, Mar 31, 2019 at 2:59 PM Mark Thomas wrote: > I asked the D folks at $dayjob for some advice / suggestions and got > back the following: > > 1. Mozilla have been doing some work in this area. It was suggested we > reach out to them to get the benefit of their experience. Anyone have > any contacts there? If you are interested in parallel and active projects, the Women outreach SIG within the GNOME project is a really interesting and successful case study. I haven't tracked them in real-time, so I'm surprised/pleased by one particular fruit of their efforts; https://en.wikipedia.org/wiki/Outreachy which Mozilla too turns out to be a huge champion of. The history topic on that page plus footnotes are useful starting points.
Re: D
iirc there were discussions about public lists and their suitability for the kind of changes and audiences involved, positive discrimination, outreach efforts, etc... > On Apr 2, 2019, at 1:21 PM, Griselda Cuevas wrote: > > Any highlights, take aways or tips on what to look for? > > On Tue, Apr 2, 2019, 9:09 AM Jim Jagielski wrote: > >> Not sure how many people were around back in the day, >> but it would be good to learn whatever can be learned >> from the women@ "experiment": >> >>https://lists.apache.org/list.html?wo...@apache.org >> >> Cheers! >> >> - >> 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: on "meritocracy"
Before we get locked into this JIRA, could we consider changing its name to DIVERSITY instead of DI ? Craig > On Apr 2, 2019, at 10:06 AM, Griselda Cuevas wrote: > > @joan - I also get a Pony, I requested the Jira ;) > > On Tue, Apr 2, 2019, 10:03 AM Joan Touzet wrote: > >> >> >> >> Daniel wrote: >> >>> Requested, and should be ready within an hour or two. >> >> Thank you! You get a pony! >> >> -Joan "JFDI" Touzet >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> Craig Russell Member, Apache Incubator PMC apache@gmail.com
Re: Google Season of Docs 2019
They're taking applications now. Dinesh On Saturday, March 30, 2019, 9:08:50 AM PDT, wrote: Excellent and thanks Maxim! :-) Thanks Sharan On 30. 03. 19 16:45, Maxim Solodovnik wrote: > Hello Sharah > > I can help :) > > On Sat, Mar 30, 2019, 22:33 Sharan Foga wrote: > >> Hi Kenn >> >> No not yet - applications open on 2nd April and close on 23rd April. Will >> aim to get a draft together this weekend. >> >> We also need to have two organisation administrators for GSoD so I am >> still looking for another volunteer to help out with that. >> >> Thanks >> Sharan >> >> On 2019/03/29 23:21:16, Kenneth Knowles wrote: >>> Is this taken care of? Did ASF apply? Is there anything more that I could >>> help with at all? I would also be happy to review anything. >>> >>> Kenn >>> >>> On Fri, Mar 22, 2019 at 3:14 AM Sharan Foga wrote: >>> Hi Dinesh It's great to hear that the Apache Cassandra community is keen to be involved with this. I confirm that I will put an application on behalf >> of the ASF. Thanks Sharan On 2019/03/22 07:24:20, Dinesh Joshi wrote: > Hi all, > > I am coordinating the GSoD effort in the Apache Cassandra community. >> We already have a few volunteers willing to help mentor the tech writer. >> Who can confirm whether ASF is applying as an organization? We will not >> apply separately. > Thanks, > > Dinesh > >> On Mar 19, 2019, at 11:11 AM, Aizhamal Nurmamat kyzy wrote: >> Hi Sharan, >> >> I'm happy to help with the ASF's application for SoD, if you need >> any >> support there. >> >> Thanks, >> Aizhamal >> >> On Mon, Mar 18, 2019 at 3:25 PM Sharan Foga >> wrote: >>> Hi >>> >>> ComDev currently manages the ASF applications for GSoC so it might make >>> sense for us to centralise the application for this too. >>> >>> We would need 2 people to manage the ASF organisation application >> as a >>> mentor organisation as well as administer the projects and >> mentors. >>> If selected then each project participating would need to >> guarantee at >>> least 2 mentors to work with the technical writer. We currently collect >>> the GSoC ideas via a JIra so perhaps that could be adapted for >> GSoD too, >>> The timeline is tight - I think 2nd April is when applications >> open. It >>> already sounds like the level of interest is high so we need to >> act quickly >>> if we want to participate. >>> >>> Thanks >>> Sharan >>> >>> On 2019/03/12 18:14:54, Dave Fisher >> wrote: Hi - Looks pretty cool. Cc: to Apache Community Development. Regards, Dave Sent from my iPhone > On Mar 12, 2019, at 9:22 AM, Huxing Zhang wrote: > Hi, > > Google Season of Docs 2019[1] seems to be an interesting >> project, > which bring open source project and technical writer communities > together, just Like Google summer of code. > > I think the Dubbo can benefit from the project, especially the English > version of documentation could be improved. > > How do you think? > > [1] https://developers.google.com/season-of-docs/docs/timeline > > -- > Best Regards！ > Huxing >> - 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 >>> >>> > > - > 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 >> - >> 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: D
Any highlights, take aways or tips on what to look for? On Tue, Apr 2, 2019, 9:09 AM Jim Jagielski wrote: > Not sure how many people were around back in the day, > but it would be good to learn whatever can be learned > from the women@ "experiment": > > https://lists.apache.org/list.html?wo...@apache.org > > Cheers! > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
I don't know why I missed Mark's email, it appeared in a different thread in my Gmail. I will take your suggestions Mark and embed them into a proposal in the new Jira board. Thank you!!! This is inspiring, motivating and amazing. On Sun, Mar 31, 2019, 12:59 PM Mark Thomas wrote: > I asked the D folks at $dayjob for some advice / suggestions and got > back the following: > > 1. Mozilla have been doing some work in this area. It was suggested we > reach out to them to get the benefit of their experience. Anyone have > any contacts there? > > 2. Mozilla joined https://womensleadership.stanford.edu/corporate as > part of their program. > > 3. Consider sending folks to relevant conferences e.g. > http://www.womentransformingtechnology.com/ > > 4. Creating a vision for inclusion > > 5. Various workshops (psychological safety, inclusion) and other > educational sessions > > 6. Hearing from leadership on these topics. > > 7. Making the content core not extra-curricular. > > > Trying to translate what some of this might look like at the ASF: > > I think a lot of this is already covered by what Griselda set out here: > > https://lists.apache.org/thread.html/a5e7e30fad3e89547db554cf64b10d33611d4401356590bddf94b918@%3Cdev.community.apache.org%3E > > I think I'm getting a little ahead of things but I wanted to add some > ideas of my own in terms of what some of the above could look like while > the ideas were fresh in my mind. > > 4. One for the board. > > 6/7. D could/should be part of our quarterly and annual reports. It > should appear on the board agenda and in the minutes. It should be in > State of the Feather talks at ApacheCon. This sounds like we need a VP > D to me. I think Sam's thinking was heading in this direction when he > mentioned setting up a President's committee. > > 5. Harder to do in an organisation as virtual as ours. We could/should > certainly try and do more of this at ApacheCon. I'm fairly sure that > there are geographical concentrations of committers. We should look at > putting on specific events for committers where we have concentrations > of committers. > > 3. I'm thinking TAC+. We fund folks to attend these external events. > > Mark > > > > On 29/03/2019 22:40, Justin Mclean wrote: > > Hi, > > > > Slightly off topic but relevant. One think we could do is look at other > foundations and communities and see what they have done that has worked for > them. I come across this interesting artifice this morning [1]. Note it > includes the steps that community took to build a diverse community, I’d > also note we’ve taken some of those steps (e.g. have a code of conduct) but > perhaps shows where we could do more. They have set up a Drupal Diversity & > Inclusion team [5] that spells out it values [2] and has among other > things guide on moderation, [3] and participation [4], Now the ASF is > different to Drupal and some of those tings may not fit but it would be > useful I think to at least consider them. > > > > Thanks, > > Justin > > > > 1. > https://angel.co/blog/drupals-angela-byron-on-building-a-diverse-community > > 2. > https://www.drupal.org/docs/8/modules/drupal-diversity-inclusion/statement-of-values > > 3. > https://www.drupal.org/docs/8/modules/drupal-diversity-inclusion/drupal-diversity-inclusion-participation-moderation-1 > > 4. > https://www.drupal.org/docs/8/modules/drupal-diversity-inclusion/participation-moderation-guidelines/participant-guidelines > > 5. https://www.drupal.org/project/diversity > > - > > 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: on "meritocracy"
Thank you! On Tue, Apr 2, 2019, 10:12 AM Daniel Gruno wrote: > https://lists.apache.org/list.html?divers...@apache.org > > > > On 02/04/2019 12.03, Joan Touzet wrote: > > > > > > > > Daniel wrote: > > > >> Requested, and should be ready within an hour or two. > > > > Thank you! You get a pony! > > > > -Joan "JFDI" Touzet > > > > - > > 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: on "meritocracy"
Griselda Cuevas wrote: > @joan - I also get a Pony, I requested the Jira ;) Of course you do! (Use a monospace font for best rendering...) ,--, _ ___/ /\| ;( )__, ) ; // '--; \ | ^^ -Joan "Caaan do!" Touzet - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
https://lists.apache.org/list.html?divers...@apache.org On 02/04/2019 12.03, Joan Touzet wrote: Daniel wrote: Requested, and should be ready within an hour or two. Thank you! You get a pony! -Joan "JFDI" Touzet - 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: on "meritocracy"
@Sam - let's arrange a date & time. I am on my phone (currently at FlinkForward), but when I get my laptop I'll send a Doodle in a new thread to schedule. Thanks all for chiming in and helping move this forward, all get ponies :) On Tue, Apr 2, 2019, 10:06 AM Griselda Cuevas wrote: > @joan - I also get a Pony, I requested the Jira ;) > > On Tue, Apr 2, 2019, 10:03 AM Joan Touzet wrote: > >> >> >> >> Daniel wrote: >> >> > Requested, and should be ready within an hour or two. >> >> Thank you! You get a pony! >> >> -Joan "JFDI" Touzet >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: on "meritocracy"
@joan - I also get a Pony, I requested the Jira ;) On Tue, Apr 2, 2019, 10:03 AM Joan Touzet wrote: > > > > Daniel wrote: > > > Requested, and should be ready within an hour or two. > > Thank you! You get a pony! > > -Joan "JFDI" Touzet > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
Daniel wrote: > Requested, and should be ready within an hour or two. Thank you! You get a pony! -Joan "JFDI" Touzet - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
Let's you and I find some time to chat, possibly with ross and others, and we can bring a proposal back to the list. On Tue, Apr 2, 2019, 12:44 PM Griselda Cuevas wrote: > +1 to divers...@apache.org > > I want to move forward on creating a president's committee. How do I do > that? > > On Tue, Apr 2, 2019, 9:36 AM Daniel Gruno wrote: > > > On 02/04/2019 11.34, Joan Touzet wrote: > > > Daniel said: > > >> On 02/04/2019 11.29, Daniel Gruno wrote: > > >>> On 02/04/2019 11.26, Joan Touzet wrote: > > Trying to cut through the bikeshedding: > > > > Daniel Gruno said: > > > I'd recommend a separate mailing list (to provide focus) and a > > > JIRA, > > > perhaps some place to put documents (either within the comdev svn > > > area, > > > or somewhere else if spun off), and then...just get to work :) > > > > This is what Griselda proposed as well (yes, and other things). > > > > Can we get these now (under ComDev) and move them later when the > > president's committee is approved? (And, if not, they can stay > > under > > ComDev)? > > >>> > > >>> Yes, we can request them right now (within 3 hours), we just need > > >>> to > > >>> pick a name for the list (gimme some suggestions!) - and probably > > >>> just > > >>> pick the same name for a sub dir of comdev's svn. the JIRA instance > > >>> is > > >>> already requested via a ticket. > > >> > > >> perhaps we should just make divers...@apache.org and get started > > >> there? > > >> the advantage being that it's not tied to a project, so whatever we > > >> end > > >> up with, it wouldn't affect the list. > > > > > > Well, we have the JIRA already: > > > > > > https://issues.apache.org/jira/projects/DI/summary > > > > > > divers...@apache.org works for me; if the president's committee > doesn't > > > get approved, would we have any pressure to move that to > > > diversity@community.a.o instead? > > > > No, not really :) there's plenty of precedence for keeping it. > > Assuming this would be a public list (feedback??), I can get it created > > ASAP. > > > > > > > > -Joan > > > > > > - > > > 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: on "meritocracy"
On 02/04/2019 11.37, Joan Touzet wrote: Daniel Gruno said: On 02/04/2019 11.34, Joan Touzet wrote: Daniel said: On 02/04/2019 11.29, Daniel Gruno wrote: On 02/04/2019 11.26, Joan Touzet wrote: Trying to cut through the bikeshedding: Daniel Gruno said: I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps some place to put documents (either within the comdev svn area, or somewhere else if spun off), and then...just get to work :) This is what Griselda proposed as well (yes, and other things). Can we get these now (under ComDev) and move them later when the president's committee is approved? (And, if not, they can stay under ComDev)? Yes, we can request them right now (within 3 hours), we just need to pick a name for the list (gimme some suggestions!) - and probably just pick the same name for a sub dir of comdev's svn. the JIRA instance is already requested via a ticket. perhaps we should just make divers...@apache.org and get started there? the advantage being that it's not tied to a project, so whatever we end up with, it wouldn't affect the list. Well, we have the JIRA already: https://issues.apache.org/jira/projects/DI/summary divers...@apache.org works for me; if the president's committee doesn't get approved, would we have any pressure to move that to diversity@community.a.o instead? No, not really :) there's plenty of precedence for keeping it. Assuming this would be a public list (feedback??), I can get it created ASAP. Public, but non-member posts get moderated. (I forget if this is the default.) Requested, and should be ready within an hour or two. -Joan - 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: on "meritocracy"
Daniel Gruno said: > On 02/04/2019 11.34, Joan Touzet wrote: > > Daniel said: > >> On 02/04/2019 11.29, Daniel Gruno wrote: > >>> On 02/04/2019 11.26, Joan Touzet wrote: > Trying to cut through the bikeshedding: > > Daniel Gruno said: > > I'd recommend a separate mailing list (to provide focus) and a > > JIRA, > > perhaps some place to put documents (either within the comdev > > svn > > area, > > or somewhere else if spun off), and then...just get to work :) > > This is what Griselda proposed as well (yes, and other things). > > Can we get these now (under ComDev) and move them later when the > president's committee is approved? (And, if not, they can stay > under > ComDev)? > >>> > >>> Yes, we can request them right now (within 3 hours), we just need > >>> to > >>> pick a name for the list (gimme some suggestions!) - and probably > >>> just > >>> pick the same name for a sub dir of comdev's svn. the JIRA > >>> instance > >>> is > >>> already requested via a ticket. > >> > >> perhaps we should just make divers...@apache.org and get started > >> there? > >> the advantage being that it's not tied to a project, so whatever > >> we > >> end > >> up with, it wouldn't affect the list. > > > > Well, we have the JIRA already: > > > > https://issues.apache.org/jira/projects/DI/summary > > > > divers...@apache.org works for me; if the president's committee > > doesn't > > get approved, would we have any pressure to move that to > > diversity@community.a.o instead? > > No, not really :) there's plenty of precedence for keeping it. > Assuming this would be a public list (feedback??), I can get it > created > ASAP. Public, but non-member posts get moderated. (I forget if this is the default.) -Joan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
+1 to divers...@apache.org I want to move forward on creating a president's committee. How do I do that? On Tue, Apr 2, 2019, 9:36 AM Daniel Gruno wrote: > On 02/04/2019 11.34, Joan Touzet wrote: > > Daniel said: > >> On 02/04/2019 11.29, Daniel Gruno wrote: > >>> On 02/04/2019 11.26, Joan Touzet wrote: > Trying to cut through the bikeshedding: > > Daniel Gruno said: > > I'd recommend a separate mailing list (to provide focus) and a > > JIRA, > > perhaps some place to put documents (either within the comdev svn > > area, > > or somewhere else if spun off), and then...just get to work :) > > This is what Griselda proposed as well (yes, and other things). > > Can we get these now (under ComDev) and move them later when the > president's committee is approved? (And, if not, they can stay > under > ComDev)? > >>> > >>> Yes, we can request them right now (within 3 hours), we just need > >>> to > >>> pick a name for the list (gimme some suggestions!) - and probably > >>> just > >>> pick the same name for a sub dir of comdev's svn. the JIRA instance > >>> is > >>> already requested via a ticket. > >> > >> perhaps we should just make divers...@apache.org and get started > >> there? > >> the advantage being that it's not tied to a project, so whatever we > >> end > >> up with, it wouldn't affect the list. > > > > Well, we have the JIRA already: > > > > https://issues.apache.org/jira/projects/DI/summary > > > > divers...@apache.org works for me; if the president's committee doesn't > > get approved, would we have any pressure to move that to > > diversity@community.a.o instead? > > No, not really :) there's plenty of precedence for keeping it. > Assuming this would be a public list (feedback??), I can get it created > ASAP. > > > > > -Joan > > > > - > > 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: on "meritocracy"
On 02/04/2019 11.34, Joan Touzet wrote: Daniel said: On 02/04/2019 11.29, Daniel Gruno wrote: On 02/04/2019 11.26, Joan Touzet wrote: Trying to cut through the bikeshedding: Daniel Gruno said: I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps some place to put documents (either within the comdev svn area, or somewhere else if spun off), and then...just get to work :) This is what Griselda proposed as well (yes, and other things). Can we get these now (under ComDev) and move them later when the president's committee is approved? (And, if not, they can stay under ComDev)? Yes, we can request them right now (within 3 hours), we just need to pick a name for the list (gimme some suggestions!) - and probably just pick the same name for a sub dir of comdev's svn. the JIRA instance is already requested via a ticket. perhaps we should just make divers...@apache.org and get started there? the advantage being that it's not tied to a project, so whatever we end up with, it wouldn't affect the list. Well, we have the JIRA already: https://issues.apache.org/jira/projects/DI/summary divers...@apache.org works for me; if the president's committee doesn't get approved, would we have any pressure to move that to diversity@community.a.o instead? No, not really :) there's plenty of precedence for keeping it. Assuming this would be a public list (feedback??), I can get it created ASAP. -Joan - 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: on "meritocracy"
Daniel said: > On 02/04/2019 11.29, Daniel Gruno wrote: > > On 02/04/2019 11.26, Joan Touzet wrote: > >> Trying to cut through the bikeshedding: > >> > >> Daniel Gruno said: > >>> I'd recommend a separate mailing list (to provide focus) and a > >>> JIRA, > >>> perhaps some place to put documents (either within the comdev svn > >>> area, > >>> or somewhere else if spun off), and then...just get to work :) > >> > >> This is what Griselda proposed as well (yes, and other things). > >> > >> Can we get these now (under ComDev) and move them later when the > >> president's committee is approved? (And, if not, they can stay > >> under > >> ComDev)? > > > > Yes, we can request them right now (within 3 hours), we just need > > to > > pick a name for the list (gimme some suggestions!) - and probably > > just > > pick the same name for a sub dir of comdev's svn. the JIRA instance > > is > > already requested via a ticket. > > perhaps we should just make divers...@apache.org and get started > there? > the advantage being that it's not tied to a project, so whatever we > end > up with, it wouldn't affect the list. Well, we have the JIRA already: https://issues.apache.org/jira/projects/DI/summary divers...@apache.org works for me; if the president's committee doesn't get approved, would we have any pressure to move that to diversity@community.a.o instead? -Joan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On 02/04/2019 11.29, Daniel Gruno wrote: On 02/04/2019 11.26, Joan Touzet wrote: Trying to cut through the bikeshedding: Daniel Gruno said: I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps some place to put documents (either within the comdev svn area, or somewhere else if spun off), and then...just get to work :) This is what Griselda proposed as well (yes, and other things). Can we get these now (under ComDev) and move them later when the president's committee is approved? (And, if not, they can stay under ComDev)? Yes, we can request them right now (within 3 hours), we just need to pick a name for the list (gimme some suggestions!) - and probably just pick the same name for a sub dir of comdev's svn. the JIRA instance is already requested via a ticket. perhaps we should just make divers...@apache.org and get started there? the advantage being that it's not tied to a project, so whatever we end up with, it wouldn't affect the list. I want to get started with reasonable, motivated discussion and not lose momentum while we wait a few weeks. I think this is the right approach. Let's get something started, and the whole org aspect and fine tuning can be applied at next board meeting or whenever :) -Joan - 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 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On Tue, Apr 2, 2019 at 5:39 PM Griselda Cuevas wrote: > ...this rationale still treats the effort to embrace the need for a > Diversity and Inclusion strategy as a proof of concept, expecting it will > die... FWIW that's not my angle. I was just trying to keep things simple, and small reversible steps are usually our favorite way of working: start small, demonstrate that things work and progress incrementally. But if those who will do the work have other opinions I will not stand in the way: another of our important principles is that whoever does the work gets to decide ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On 02/04/2019 11.26, Joan Touzet wrote: Trying to cut through the bikeshedding: Daniel Gruno said: I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps some place to put documents (either within the comdev svn area, or somewhere else if spun off), and then...just get to work :) This is what Griselda proposed as well (yes, and other things). Can we get these now (under ComDev) and move them later when the president's committee is approved? (And, if not, they can stay under ComDev)? Yes, we can request them right now (within 3 hours), we just need to pick a name for the list (gimme some suggestions!) - and probably just pick the same name for a sub dir of comdev's svn. the JIRA instance is already requested via a ticket. I want to get started with reasonable, motivated discussion and not lose momentum while we wait a few weeks. I think this is the right approach. Let's get something started, and the whole org aspect and fine tuning can be applied at next board meeting or whenever :) -Joan - 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: on "meritocracy"
> On Apr 2, 2019, at 12:11 PM, Daniel Gruno wrote: > > > The specific organizational structure does indeed seem like a moot topic. > What matters is that wherever this take place, the group is given *space and > freedom* to get some work done. I'd be fine with it being within ComDev, I'd > also be fine (but perhaps a bit confused) with it being a thing of its > own...but what it really just needs is a space to work within, and a > sufficient amount of isolation from bike-shedding. > > I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps > some place to put documents (either within the comdev svn area, or somewhere > else if spun off), and then...just get to work :) > My last post on this today: Agreed on the above. The rationale for keeping in ComDev is to avoid friction and possible "hey, shouldn't D be doing that?" and "Hey, this is part of ComDev", etc... keeping all under one roof prevents that whereas sep mailing list and Jira allow for the potential for focus to keep the effort going. As the lines become more clear on what are the diffs between ComDev's charter and what D is doing (if it comes to that), then that friction/overlap/confusion becomes moot.
Re: on "meritocracy"
Trying to cut through the bikeshedding: Daniel Gruno said: > I'd recommend a separate mailing list (to provide focus) and a JIRA, > perhaps some place to put documents (either within the comdev svn > area, > or somewhere else if spun off), and then...just get to work :) This is what Griselda proposed as well (yes, and other things). Can we get these now (under ComDev) and move them later when the president's committee is approved? (And, if not, they can stay under ComDev)? I want to get started with reasonable, motivated discussion and not lose momentum while we wait a few weeks. -Joan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
what I liked about Mark's proposal for a VP D is that it sets a very clear top-down message that the Board is taking this matter seriously and that ongoing monthly reports are something we are committing to I think that is diluted somewhat in both intent and impact if this is "relegated" to a provisional side-project under ComDev On Tue, 2 Apr 2019 at 18:11, Daniel Gruno wrote: > On 02/04/2019 10.57, Jim Jagielski wrote: > > I don't think anyone expects it to die, but rather that D be one of > > the core aspects of community development and not an effort, > > in and of itself. If it reaches critical mass and warrants being > > spun out (due to clear division of tasks between D and ComDev) > > then I think everyone would support that. > > > > IMO, spinning out does not guarantee that an effort will succeed and > > not die (we have loads of history to show that), nor does keeping > > it, for the time being, in ComDev mean that it will wither or die on > > the vine. > > The specific organizational structure does indeed seem like a moot > topic. What matters is that wherever this take place, the group is given > *space and freedom* to get some work done. I'd be fine with it being > within ComDev, I'd also be fine (but perhaps a bit confused) with it > being a thing of its own...but what it really just needs is a space to > work within, and a sufficient amount of isolation from bike-shedding. > > I'd recommend a separate mailing list (to provide focus) and a JIRA, > perhaps some place to put documents (either within the comdev svn area, > or somewhere else if spun off), and then...just get to work :) > > > > > Just my 2c > > > >> On Apr 2, 2019, at 11:38 AM, Griselda Cuevas > wrote: > >> > >> I agree with Sam that if we do not formalize this as a committee it will > >> die. > >> > >> I understand and acknowledge the reasons why this being part of ComDev > >> makes sense: simplicity and agility to get off the ground. > >> > >> However, this rationale still treats the effort to embrace the need for > a > >> Diversity and Inclusion strategy as a proof of concept, expecting it > will > >> die. I have committed to make this happen and the commitment includes > >> driving this through the bureocracy needed to make the group and efforts > >> part of the ASF DNA. > >> > >> If we do not do it now, it will just become what Naomi mentioned: yet > >> another try. > >> > >> I am happy to walk the walk and structure work and needs to make this > >> happen. > >> > >> I would suggest we still aim for the committee or at least define a > clear > >> goal to hit for it to graduate to that level. Right now the > >> success.measurement is unclear and vague. > >> > >> On Tue, Apr 2, 2019, 8:12 AM Bertrand Delacretaz < > bdelacre...@apache.org> > >> wrote: > >> > >>> On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby > wrote: > ...My feeling is that it will die here... > >>> > >>> IIUC what's been proposed so far is a new mailing list and issue > tracker. > >>> > >>> Both can very well be owned by comdev and that shouldn't limit > >>> progress in any way. > >>> > >>> It's just that the comdev PMC is responsible for oversight and > >>> reporting on those new initiatives, and it keeps things simple for > >>> now. > >>> > >>> -Bertrand > >>> > >>> - > >>> 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 > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
On 02/04/2019 10.57, Jim Jagielski wrote: I don't think anyone expects it to die, but rather that D be one of the core aspects of community development and not an effort, in and of itself. If it reaches critical mass and warrants being spun out (due to clear division of tasks between D and ComDev) then I think everyone would support that. IMO, spinning out does not guarantee that an effort will succeed and not die (we have loads of history to show that), nor does keeping it, for the time being, in ComDev mean that it will wither or die on the vine. The specific organizational structure does indeed seem like a moot topic. What matters is that wherever this take place, the group is given *space and freedom* to get some work done. I'd be fine with it being within ComDev, I'd also be fine (but perhaps a bit confused) with it being a thing of its own...but what it really just needs is a space to work within, and a sufficient amount of isolation from bike-shedding. I'd recommend a separate mailing list (to provide focus) and a JIRA, perhaps some place to put documents (either within the comdev svn area, or somewhere else if spun off), and then...just get to work :) Just my 2c On Apr 2, 2019, at 11:38 AM, Griselda Cuevas wrote: I agree with Sam that if we do not formalize this as a committee it will die. I understand and acknowledge the reasons why this being part of ComDev makes sense: simplicity and agility to get off the ground. However, this rationale still treats the effort to embrace the need for a Diversity and Inclusion strategy as a proof of concept, expecting it will die. I have committed to make this happen and the commitment includes driving this through the bureocracy needed to make the group and efforts part of the ASF DNA. If we do not do it now, it will just become what Naomi mentioned: yet another try. I am happy to walk the walk and structure work and needs to make this happen. I would suggest we still aim for the committee or at least define a clear goal to hit for it to graduate to that level. Right now the success.measurement is unclear and vague. On Tue, Apr 2, 2019, 8:12 AM Bertrand Delacretaz wrote: On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby wrote: ...My feeling is that it will die here... IIUC what's been proposed so far is a new mailing list and issue tracker. Both can very well be owned by comdev and that shouldn't limit progress in any way. It's just that the comdev PMC is responsible for oversight and reporting on those new initiatives, and it keeps things simple for now. -Bertrand - 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 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
D
Not sure how many people were around back in the day, but it would be good to learn whatever can be learned from the women@ "experiment": https://lists.apache.org/list.html?wo...@apache.org Cheers! - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
Ah. Ok. That's fair. I retract my comment. I was seeing going the full top-level committee thing as being a bureaucratic stumbling block, and not in this light. I have no strong preference one way or the other and merely wanted to remove obstacles. Your reasoning is compelling and right. Go for it. --Rich On 4/2/19 11:38 AM, Griselda Cuevas wrote: > I agree with Sam that if we do not formalize this as a committee it will > die. > > I understand and acknowledge the reasons why this being part of ComDev > makes sense: simplicity and agility to get off the ground. > > However, this rationale still treats the effort to embrace the need for a > Diversity and Inclusion strategy as a proof of concept, expecting it will > die. I have committed to make this happen and the commitment includes > driving this through the bureocracy needed to make the group and efforts > part of the ASF DNA. > > If we do not do it now, it will just become what Naomi mentioned: yet > another try. > > I am happy to walk the walk and structure work and needs to make this > happen. > > I would suggest we still aim for the committee or at least define a clear > goal to hit for it to graduate to that level. Right now the > success.measurement is unclear and vague. > > On Tue, Apr 2, 2019, 8:12 AM Bertrand Delacretaz > wrote: > >> On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby wrote: >>> ...My feeling is that it will die here... >> >> IIUC what's been proposed so far is a new mailing list and issue tracker. >> >> Both can very well be owned by comdev and that shouldn't limit >> progress in any way. >> >> It's just that the comdev PMC is responsible for oversight and >> reporting on those new initiatives, and it keeps things simple for >> now. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> > -- Rich Bowen - rbo...@rcbowen.com http://rcbowen.com/ @rbowen - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
I don't think anyone expects it to die, but rather that D be one of the core aspects of community development and not an effort, in and of itself. If it reaches critical mass and warrants being spun out (due to clear division of tasks between D and ComDev) then I think everyone would support that. IMO, spinning out does not guarantee that an effort will succeed and not die (we have loads of history to show that), nor does keeping it, for the time being, in ComDev mean that it will wither or die on the vine. Just my 2c > On Apr 2, 2019, at 11:38 AM, Griselda Cuevas wrote: > > I agree with Sam that if we do not formalize this as a committee it will > die. > > I understand and acknowledge the reasons why this being part of ComDev > makes sense: simplicity and agility to get off the ground. > > However, this rationale still treats the effort to embrace the need for a > Diversity and Inclusion strategy as a proof of concept, expecting it will > die. I have committed to make this happen and the commitment includes > driving this through the bureocracy needed to make the group and efforts > part of the ASF DNA. > > If we do not do it now, it will just become what Naomi mentioned: yet > another try. > > I am happy to walk the walk and structure work and needs to make this > happen. > > I would suggest we still aim for the committee or at least define a clear > goal to hit for it to graduate to that level. Right now the > success.measurement is unclear and vague. > > On Tue, Apr 2, 2019, 8:12 AM Bertrand Delacretaz > wrote: > >> On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby wrote: >>> ...My feeling is that it will die here... >> >> IIUC what's been proposed so far is a new mailing list and issue tracker. >> >> Both can very well be owned by comdev and that shouldn't limit >> progress in any way. >> >> It's just that the comdev PMC is responsible for oversight and >> reporting on those new initiatives, and it keeps things simple for >> now. >> >> -Bertrand >> >> - >> 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: on "meritocracy"
Top-post: Couldn’t this be made a President’s committee now and the board can chat about it elsewhere until the next board meeting in a few weeks? The board could even defer until there are Policy recommendations. (I’m not excited about reading yet another passionate Jim/Sam debate about which type of committee at this moment.) Regards, Dave > On Apr 2, 2019, at 8:46 AM, Patricia Shanahan wrote: > > On 4/2/2019 8:12 AM, Bertrand Delacretaz wrote: > ... >> It's just that the comdev PMC is responsible for oversight and >> reporting on those new initiatives, and it keeps things simple for >> now. > > That is exactly what troubles me about making the new initiative part of > ComDev. > > There seems to me to be a risk of going back to the "Do we have a problem? > Even if we have a problem do we really need to do anything about it?" stage > every time the group tries to do anything, including reporting progress to > the board, and requesting resources from the board. > > At best, comdev PMC oversight and reporting would be mostly harmless. They > would just pass through whatever the group would have sent directly to the > board, only costing time. At worst, it could make the current initiative go > the way of all previous diversity efforts, by discouraging and sapping the > energy of the initiative's leadership. > > The risk of anything other than direct access to the board seems too high. > > [I have not attempted to join the initiative only because I do not have any > expertise in the area of solutions. I have been a woman in computing, in > various ways, for over 50 years. I want the current initiative to have the > best possible chance of making a difference.] > > - > 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: on "meritocracy"
On 4/2/2019 8:12 AM, Bertrand Delacretaz wrote: ... It's just that the comdev PMC is responsible for oversight and reporting on those new initiatives, and it keeps things simple for now. That is exactly what troubles me about making the new initiative part of ComDev. There seems to me to be a risk of going back to the "Do we have a problem? Even if we have a problem do we really need to do anything about it?" stage every time the group tries to do anything, including reporting progress to the board, and requesting resources from the board. At best, comdev PMC oversight and reporting would be mostly harmless. They would just pass through whatever the group would have sent directly to the board, only costing time. At worst, it could make the current initiative go the way of all previous diversity efforts, by discouraging and sapping the energy of the initiative's leadership. The risk of anything other than direct access to the board seems too high. [I have not attempted to join the initiative only because I do not have any expertise in the area of solutions. I have been a woman in computing, in various ways, for over 50 years. I want the current initiative to have the best possible chance of making a difference.] - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
I agree with Sam that if we do not formalize this as a committee it will die. I understand and acknowledge the reasons why this being part of ComDev makes sense: simplicity and agility to get off the ground. However, this rationale still treats the effort to embrace the need for a Diversity and Inclusion strategy as a proof of concept, expecting it will die. I have committed to make this happen and the commitment includes driving this through the bureocracy needed to make the group and efforts part of the ASF DNA. If we do not do it now, it will just become what Naomi mentioned: yet another try. I am happy to walk the walk and structure work and needs to make this happen. I would suggest we still aim for the committee or at least define a clear goal to hit for it to graduate to that level. Right now the success.measurement is unclear and vague. On Tue, Apr 2, 2019, 8:12 AM Bertrand Delacretaz wrote: > On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby wrote: > > ...My feeling is that it will die here... > > IIUC what's been proposed so far is a new mailing list and issue tracker. > > Both can very well be owned by comdev and that shouldn't limit > progress in any way. > > It's just that the comdev PMC is responsible for oversight and > reporting on those new initiatives, and it keeps things simple for > now. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
On Tue, Apr 2, 2019 at 4:57 PM Sam Ruby wrote: > ...My feeling is that it will die here... IIUC what's been proposed so far is a new mailing list and issue tracker. Both can very well be owned by comdev and that shouldn't limit progress in any way. It's just that the comdev PMC is responsible for oversight and reporting on those new initiatives, and it keeps things simple for now. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On Tue, Apr 2, 2019 at 10:48 AM Bertrand Delacretaz wrote: > > On Tue, Apr 2, 2019 at 3:53 PM Rich Bowen wrote: > > ...In the spirit of small reversible steps, starting as a ComDev > > initiative, and then, if needed, graduating to its own entity later?... > > Good point, that's what I was trying to say, but better said ;-) My feeling is that it will die here, but I recognize that the burden of proof is on those that wish to propose that Diversity and Inclusion merits its own place in the organizational structure. - Sam Ruby - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On Tue, Apr 2, 2019 at 3:53 PM Rich Bowen wrote: > ...In the spirit of small reversible steps, starting as a ComDev > initiative, and then, if needed, graduating to its own entity later?... Good point, that's what I was trying to say, but better said ;-) -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
> On Apr 2, 2019, at 9:53 AM, Rich Bowen wrote: > > > > On 4/2/19 7:05 AM, Jim Jagielski wrote: >> Does it need to be its own entity? Why can't this be a task/effort under >> ComDev's control/charter? It certainly seems to fit under the >> concept of comdev and the people are already here... > > In the spirit of small reversible steps, starting as a ComDev > initiative, and then, if needed, graduating to its own entity later? > ++1
Re: on "meritocracy"
On 4/2/19 7:05 AM, Jim Jagielski wrote: > Does it need to be its own entity? Why can't this be a task/effort under > ComDev's control/charter? It certainly seems to fit under the > concept of comdev and the people are already here... In the spirit of small reversible steps, starting as a ComDev initiative, and then, if needed, graduating to its own entity later? It would be a shame to get wrapped up in administrivia at this point (ie, creating a board committee, and so on) and losing the momentum of JFDI that appears to be happening. > >> On Apr 1, 2019, at 6:31 PM, Griselda Cuevas wrote: >> >> Another update. >> >> I'm writing the note to operati...@apache.org to request the creation of an >> entity to support and govern diversity and inclusion work. I've added the >> name of everyone who volunteered here initially, with the caveat that I >> might have missed someone, so please follow up on the new thread when I >> send it, nothing intentional. >> >> I've also included a potential framework to work under. You can see it >> illustrated in this talk I gave at OSCON last year: >> https://docs.google.com/presentation/d/1FV_9geYGoclJeBb7Ld8Jy0Ze3ex8lTm77dZ6l31y8zo/edit#slide=id.g3e2640810d_1_6 >> >> I've also requested an initial quote from the firm we work on Research for >> OSS contributor documentation (Guidea). I've asked for pricing on a project >> that will deliver on this: >> - Identify factors preventing under represented groups to contribute/join >> Apache projects >> - Recommendations in how to foster diversity & inclusion based in findings >> - Help establishing a D committee >> >> I'll report back their quote. >> >> On Mon, 1 Apr 2019 at 14:15, Griselda Cuevas wrote: >> >>> >>> >>> >>> On Fri, 29 Mar 2019 at 17:38, Sam Ruby wrote: >>> On Fri, Mar 29, 2019 at 8:25 PM Griselda Cuevas wrote: > > Thanks everyone for the encouragement and recognition. > > I'm happy to work on the Jira board this weekend. Can I just start a new > one on my personal account and add people to it? or does someone need to > create it under an Apache account? - If the later, can someone create it > and give me admin access? No private JIRA. Needs to be ASF hosted. It is a simple request to the infra team, and yes, you can have admin access. >>> >>> Just filed a Jira against Infra requesting the board. >>> https://issues.apache.org/jira/browse/INFRA-18147 >>> >>> > I will then populate it with the initial structure and will seed it with > components and the deliverables I outlined. I will add the people who > indicated interest so they can select where they want to contribute. > > In terms of comm channels, can we also create a slack channel? Slack channels tend to disadvantage people who can't be available at a given time (either due to other commitments or time zones). We use it in infra for time sensitive coordination, but my sense is that the D work should be done in a more... dare I say it... inclusive manner using mailing lists and JIRA and the like. >>> >>> Agree. Let's start with the Jira & mailing list. Could you help with >>> creating the diversity & inclusion mailing list? >>> >>> > // I will comment on Kenn's point in a separate note, he outlined great > points for us to put into an overall D strategy > > Thanks everyone! And you deserve thanks for volunteering! - Sam Ruby > On Fri, 29 Mar 2019 at 16:51, Kenneth Knowles wrote: > >> I don't find this off-topic. I am grateful for this profile of Drupal, >> which I otherwise would not have been exposed to. Thanks Justin! >> >> I want to bring the main section headers and key items (curated by me) of >> the Drupal article on list for ease of reading and archival. Apologies for >> redundancy with the links that Justin shared. >> >> 1. Institute a community-wide code of conduct >>a. With a working group to escalate to for mediation >> >> 2. Elevate a diverse group of leaders >>a. have a D board to advance initiatives surrounding D >>b. and a D contribution team to help underrepresented people >> contribute to the Drupal codebase >>c. address D in values: "We believe that the Drupal project benefits >> from a diverse contribution pool, and we strive to foster a welcoming and >> inclusive culture everywhere Drupal exists—at events, online, and in our >> workplaces” >> >> 3. Make your project accessible to a diverse user base (hits home as I >> think a lot about how they user base becomes the contributor base) >> >> 4. How private companies can promote open source diversity >>a. for most engineers, open source work is a luxury, and one that is >> not afforded to underrepresented people >>b. companies—particularly ones that profit from open
Re: Apache Maturity Model Consensus Building contradicts Incubator rules?
Hi Chris,
On Wed, Mar 20, 2019 at 1:43 PM Christofer Dutz
wrote:
> ...CS40 - In Apache projects, vetoes are only valid for code commits and are
> justified
> by a technical explanation, as per the Apache voting rules defined in CS30
I wrote that bit as that was my understanding until very recently.
We had fairly long discussions (on members@ IIRC) last year about this
and my conclusions are:
a) vetoes do apply to code as per
https://www.apache.org/foundation/voting.html ("Votes on code
modifications") but that page clearly explains how they can happen,
with strong justifications.
b) vetoes are not recommended for other decisions, due to the
potential for blocking things (especially in small projects) but PMCs
are free to decide for themselves.
Joan linked to http://couchdb.apache.org/bylaws.html which is a great
way to clarify this *for a specific PMC* even though nowadays we
prefer such things to be named "community guidelines" instead of
bylaws.
CouchDB does accept vetoes only for technical decisions as per the
default ASF model, but as per "3.8. Decision Types" they require
stronger 2/3 majorities for some decisions.
That's the kind of things that projects can decide for themselves,
https://httpd.apache.org/dev/guidelines.html has another example. I
have added those links to
https://wiki.apache.org/incubator/DefaultProjectGuidelines
-Bertrand
-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
Hi Sam, On Tue, Apr 2, 2019 at 1:25 PM Sam Ruby wrote: > ...My recommendation at this time is that it becomes a committee,.. > There are early talks about this group having a budget and hiring a > vendor. The organizational structure chosen should be one that > enables that... Ok, let's wait for the result of those talks then, thanks for clarifying! -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
IMO, this sounds like a cmmt that will defining and implementing policy... which is a board prerogative. My pref would be, if this really does need to be outside of ComDev, it be a board cmmt > On Apr 2, 2019, at 7:25 AM, Sam Ruby wrote: > > On Tue, Apr 2, 2019 at 3:32 AM Bertrand Delacretaz > wrote: >> >> We've had problems in the past with lists becoming orphaned after some >> time because they didn't clearly belong to one of our PMCs. > > My recommendation at this time is that it becomes a committee, > complete with requirements to produce either monthly or quarterly > board reports. One such mechanism is that it becomes a PMC. Another > is that it becomes a president's committee. > > There are early talks about this group having a budget and hiring a > vendor. The organizational structure chosen should be one that > enables that. > > My initial thoughts are that this be modeled after Brand Management - > with each PMC ultimately being responsible for Diversity and > Inclusion; the board being the only policing agency, and with a > central group responsible for education, documentation, and perhaps a > select number of enumerated tasks. > > - Sam Ruby > > - > 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: on "meritocracy"
On Tue, Apr 2, 2019 at 3:32 AM Bertrand Delacretaz wrote: > > We've had problems in the past with lists becoming orphaned after some > time because they didn't clearly belong to one of our PMCs. My recommendation at this time is that it becomes a committee, complete with requirements to produce either monthly or quarterly board reports. One such mechanism is that it becomes a PMC. Another is that it becomes a president's committee. There are early talks about this group having a budget and hiring a vendor. The organizational structure chosen should be one that enables that. My initial thoughts are that this be modeled after Brand Management - with each PMC ultimately being responsible for Diversity and Inclusion; the board being the only policing agency, and with a central group responsible for education, documentation, and perhaps a select number of enumerated tasks. - Sam Ruby - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
Does it need to be its own entity? Why can't this be a task/effort under ComDev's control/charter? It certainly seems to fit under the concept of comdev and the people are already here... > On Apr 1, 2019, at 6:31 PM, Griselda Cuevas wrote: > > Another update. > > I'm writing the note to operati...@apache.org to request the creation of an > entity to support and govern diversity and inclusion work. I've added the > name of everyone who volunteered here initially, with the caveat that I > might have missed someone, so please follow up on the new thread when I > send it, nothing intentional. > > I've also included a potential framework to work under. You can see it > illustrated in this talk I gave at OSCON last year: > https://docs.google.com/presentation/d/1FV_9geYGoclJeBb7Ld8Jy0Ze3ex8lTm77dZ6l31y8zo/edit#slide=id.g3e2640810d_1_6 > > I've also requested an initial quote from the firm we work on Research for > OSS contributor documentation (Guidea). I've asked for pricing on a project > that will deliver on this: > - Identify factors preventing under represented groups to contribute/join > Apache projects > - Recommendations in how to foster diversity & inclusion based in findings > - Help establishing a D committee > > I'll report back their quote. > > On Mon, 1 Apr 2019 at 14:15, Griselda Cuevas wrote: > >> >> >> >> On Fri, 29 Mar 2019 at 17:38, Sam Ruby wrote: >> >>> On Fri, Mar 29, 2019 at 8:25 PM Griselda Cuevas >>> wrote: Thanks everyone for the encouragement and recognition. I'm happy to work on the Jira board this weekend. Can I just start a new one on my personal account and add people to it? or does someone need to create it under an Apache account? - If the later, can someone create it and give me admin access? >>> >>> No private JIRA. Needs to be ASF hosted. It is a simple request to >>> the infra team, and yes, you can have admin access. >>> >> >> Just filed a Jira against Infra requesting the board. >> https://issues.apache.org/jira/browse/INFRA-18147 >> >> I will then populate it with the initial structure and will seed it with components and the deliverables I outlined. I will add the people who indicated interest so they can select where they want to contribute. In terms of comm channels, can we also create a slack channel? >>> >>> Slack channels tend to disadvantage people who can't be available at a >>> given time (either due to other commitments or time zones). We use it >>> in infra for time sensitive coordination, but my sense is that the D >>> work should be done in a more... dare I say it... inclusive manner >>> using mailing lists and JIRA and the like. >>> >> >> Agree. Let's start with the Jira & mailing list. Could you help with >> creating the diversity & inclusion mailing list? >> >> // I will comment on Kenn's point in a separate note, he outlined great points for us to put into an overall D strategy Thanks everyone! >>> >>> And you deserve thanks for volunteering! >>> >>> - Sam Ruby >>> On Fri, 29 Mar 2019 at 16:51, Kenneth Knowles wrote: > I don't find this off-topic. I am grateful for this profile of Drupal, > which I otherwise would not have been exposed to. Thanks Justin! > > I want to bring the main section headers and key items (curated by >>> me) of > the Drupal article on list for ease of reading and archival. >>> Apologies for > redundancy with the links that Justin shared. > > 1. Institute a community-wide code of conduct >a. With a working group to escalate to for mediation > > 2. Elevate a diverse group of leaders >a. have a D board to advance initiatives surrounding D >b. and a D contribution team to help underrepresented people > contribute to the Drupal codebase >c. address D in values: "We believe that the Drupal project >>> benefits > from a diverse contribution pool, and we strive to foster a welcoming >>> and > inclusive culture everywhere Drupal exists—at events, online, and in >>> our > workplaces” > > 3. Make your project accessible to a diverse user base (hits home as I > think a lot about how they user base becomes the contributor base) > > 4. How private companies can promote open source diversity >a. for most engineers, open source work is a luxury, and one that >>> is > not afforded to underrepresented people >b. companies—particularly ones that profit from open source > technology—can solve this problem by giving employees time to >>> contribute to > the projects the company uses > > It sounds like the work Gris has been doing is like the work of the >>> Drupal > D board and also the Drupal D contribution team. > > Kenn > > On Fri, Mar 29, 2019 at 3:40 PM Justin Mclean < >>> jus...@classsoftware.com> > wrote: > >> Hi, >> >> Slightly
Re: on "meritocracy"
Hi, On Tue, Apr 2, 2019 at 12:13 AM Sam Ruby wrote: > ...What would you like for the name of the list? divers...@apache.org? > da...@pache.org? d...@apache.org? If you pick a name, you can request > this yourself... We've had problems in the past with lists becoming orphaned after some time because they didn't clearly belong to one of our PMCs. I suggest for the new list to be owned by the comdev PMC, to make things clear - it probably changes nothing right now but it ensures clear ownership and oversight going forward. I have similar thoughts about the new https://issues.apache.org/jira/projects/DI project by the way, having the comdev PMC "own" it from an administrative point of view would clarify things. If we agree to put these things under comdev ownership I suppose this just means listing those resources at https://community.apache.org/ and mentioning them in the next comdev Board report. -Bertrand - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
