Re: Apache Brochure/Tri-Fold?
Roman, You might need to align this with the need to update the English version and have it approved by Press and Media first. SK says it is too out of date for distribution. Then the English version needs to be translated to the Russian version, etc. Not sure if the Russian version is out of date though. Regards, kAM On 3/22/2019 10:57 PM, Roman Shaposhnik wrote: > I can help getting the fixes committed -- replied on the JIRA and > assigned to myself to help Dmitriy get his fixes in > > On Fri, Mar 22, 2019 at 10:47 AM Dmitriy Pavlov wrote: >> Thanks for this idea, for me it will be also easier to keep track. >> >> Issue: https://issues.apache.org/jira/browse/COMDEV-315 >> >> Could you please assign me to contributor role, so I can assign this issue >> to me? >> >> пт, 22 мар. 2019 г. в 20:42, sebb : >> >>> On Fri, 22 Mar 2019 at 15:50, Dmitriy Pavlov wrote: It's a pity. Also, I can prepare .xfc files and send it to a ComDev committer via email. Who can commit it later? >>> Better to create a JIRA COMDEV issue and attach it there please. >>> >>> https://issues.apache.org/jira/browse/COMDEV >>> >>> That would make it easier to keep track of progress, and allow others >>> to help/comment. >>> >>> @comdev: Maybe ask Infra to create a (read-only) GitHub mirror of the >>> SVN repo so non-committers can create PRs etc? >>> пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: >> Hi Roman, >> >> I've tried to update it using GIMP, and it seems I can fix it. It >>> refers > to >> "Standard" font. If I set Arial it looks ok. >> >> Can I commit changes later using general Apache Committer >>> credentials or >> should I be committer in the ComDev? > One must be a ComDev committer to commit there. > >> пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik >>> : >>> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru >> wrote: Kevin A. McGrail wrote on 3/21/19 8:57 PM: > Anyone know where the source for this is at so I can print some >>> for > the > roadshow? Last updated 2017, but it is a trifold brochure layout: https://svn.apache.org/repos/asf/comdev/marketing/brochure/ >>> As a side note, the Russian translation has a very messed up font > kerning. >>> Would be great to fix it. >>> >>> Thanks, >>> Roman. >>> >>> >>> - >>> 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 > > >>> - >>> 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 > -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Brochure/Tri-Fold?
I can help getting the fixes committed -- replied on the JIRA and assigned to myself to help Dmitriy get his fixes in On Fri, Mar 22, 2019 at 10:47 AM Dmitriy Pavlov wrote: > > Thanks for this idea, for me it will be also easier to keep track. > > Issue: https://issues.apache.org/jira/browse/COMDEV-315 > > Could you please assign me to contributor role, so I can assign this issue > to me? > > пт, 22 мар. 2019 г. в 20:42, sebb : > > > On Fri, 22 Mar 2019 at 15:50, Dmitriy Pavlov wrote: > > > > > > It's a pity. Also, I can prepare .xfc files and send it to a ComDev > > > committer via email. Who can commit it later? > > > > Better to create a JIRA COMDEV issue and attach it there please. > > > > https://issues.apache.org/jira/browse/COMDEV > > > > That would make it easier to keep track of progress, and allow others > > to help/comment. > > > > @comdev: Maybe ask Infra to create a (read-only) GitHub mirror of the > > SVN repo so non-committers can create PRs etc? > > > > > пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > > > > > > > > > > > > > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > > > > > Hi Roman, > > > > > > > > > > I've tried to update it using GIMP, and it seems I can fix it. It > > refers > > > > to > > > > > "Standard" font. If I set Arial it looks ok. > > > > > > > > > > Can I commit changes later using general Apache Committer > > credentials or > > > > > should I be committer in the ComDev? > > > > > > > > One must be a ComDev committer to commit there. > > > > > > > > > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik > >: > > > > > > > > > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > > > > > > >> wrote: > > > > >>> > > > > >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: > > > > Anyone know where the source for this is at so I can print some > > for > > > > the > > > > roadshow? > > > > >>> > > > > >>> Last updated 2017, but it is a trifold brochure layout: > > > > >>> > > > > >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > > > > >> > > > > >> As a side note, the Russian translation has a very messed up font > > > > kerning. > > > > >> Would be great to fix it. > > > > >> > > > > >> Thanks, > > > > >> Roman. > > > > >> > > > > >> > > - > > > > >> 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 > > > > > > > > > > > > - > > 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
[jira] [Commented] (COMDEV-315) Fix Russian translation for Apache Brochure
[ https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799511#comment-16799511 ] Roman Shaposhnik commented on COMDEV-315: - Hey [~dpavlov] if you could attach fixed xcf and pdf files to this JIRA I can commit those > Fix Russian translation for Apache Brochure > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Roman Shaposhnik >Priority: Major > > The Russian translation has a very messed up font kerning. > Related discussion: > https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Assigned] (COMDEV-315) Fix Russian translation for Apache Brochure
[ https://issues.apache.org/jira/browse/COMDEV-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roman Shaposhnik reassigned COMDEV-315: --- Assignee: Roman Shaposhnik > Fix Russian translation for Apache Brochure > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug >Reporter: Dmitriy Pavlov >Assignee: Roman Shaposhnik >Priority: Major > > The Russian translation has a very messed up font kerning. > Related discussion: > https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: 回复：Re: Establishing an Events PMC?
To follow up Ted's proposal I think it would be a really good idea for some folks to look at models for scaling like the Arduino model Ted links to. The organizer of DevOps Days is a day job colleague, I'm sure she would be happy to chat with someone about what has worked and what has not. I wonder if Ted would be willing to interview a few people like this and write up the findings for us? Ross From: Ross Gardler Sent: Friday, March 22, 2019 7:05 PM To: Rich Bowen; dev@community.apache.org; tedl...@yahoo.com Subject: Re: 回复：Re: Establishing an Events PMC? Yes, you can absolutely count on me to help in any way possible. I'd love to be a part of closing the loop on what we started all those years ago. I've been much less active recently it would be an honor to help you kick of the next stage. Ross From: Liu Ted Sent: Friday, March 22, 2019 6:54 PM To: dev@community.apache.org; Rich Bowen; dev@community.apache.org Subject: 回复：Re: Establishing an Events PMC? Hi Rich, A big +1. To scale out, we may also refer to how Arduino Day operates 659 events in 106 countries on March 16 2019. I helped out and participated Arduino Day 2019 - Beijing. Please see more details in https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fday.arduino.cc%2Fdata=02%7C01%7C%7C774ee88b43b7452088d908d6af341152%7C84df9e7fe9f640afb435%7C1%7C0%7C636889035491353769sdata=vSPVxDZhPDZK0zhBc9CGNhQh85PsQDSzRH%2BddK19NlU%3Dreserved=0 Best regards, Ted Liu, ASF Member, Sponsor Ambassador, Incubator PMC Member 2019 年 3 月 23 日周六 1:00，Rich Bowen 写道： On 3/22/19 12:59 PM, Kevin A. McGrail wrote: > I like the idea especially the roadshow first to establish a beachhead. I > would add that a collocated event might be ok in some circumstances too as > a first landing. Yes, I just added collocated as a category in the document I'm working on. Thanks for that reminder. > On Fri, Mar 22, 2019, 11:28 Rich Bowen >> Several years ago, due to many reasons (let's call it "dysfunction" for >> now) ConCom - the Conferences Committee - was disbanded by the Board, >> and replaced with a single individual - myself - designated as VP >> Conferences. This was largely due to break the gridlock of dealing with >> 30 people, with 50 opinions, for every single time-sensitive decision >> around events. >> >> So far, so good. >> >> As we are faced with a sudden explosive expansion in our official stable >> of events, we are building ad-hoc processes for managing these. >> >> Again, so far, so good. Having dedicated per-event leads is working >> remarkably well in 2019. >> >> I have ... concerns ... going into 2020. With pushes to add events in >> Brazil, China, South Korea, Japan, India, and who knows where else, I am >> concerned that this is going to get away from us again. And it's not so >> much about control, as about having early failures in new markets and >> harming our chances for the future. >> >> I would like, for example, to have policies around how we expand into >> new regions. Like, say, that you can't do an "ApacheCon" in a new region >> before doing a "Roadshow" there to scout it out, so to speak. I don't >> want to squish enthusiasm. I also don't want to suddenly be expected to >> fund, promote, and organize 8 conference with a machine designed to run >> two. >> >> I digress. >> >> I would like to propose the following. >> >> 1) That we (primarily, myself, Ross, and any former members of ConCom >> who are able to participate) clearly document why ConCom failed, and was >> disbanded. To do this in a dispassionate non-fault-finding way. >> >> 2) That we document how the new Events organization will be managed, >> explicitly documenting ways that we will avoid the failings of ConCom. >> >> 3) That we establish a new Events PMC, documenting how it will related >> to both Marketing and ComDev (since there will always be overlap in >> those two places). >> >> Ross, is this something that you can help me with over the coming 6 >> months or so? >> >> -- >> Rich Bowen - rbo...@rcbowen.com >> https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frcbowen.com%2Fdata=02%7C01%7C%7C774ee88b43b7452088d908d6af341152%7C84df9e7fe9f640afb435%7C1%7C0%7C636889035491353769sdata=KwNlcCPd77Zbg%2FygYwgge%2B3M%2BMZDMuonjhzlNaTlG60%3Dreserved=0 >> @rbowen >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> > -- Rich Bowen - rbo...@rcbowen.com https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frcbowen.com%2Fdata=02%7C01%7C%7C774ee88b43b7452088d908d6af341152%7C84df9e7fe9f640afb435%7C1%7C0%7C636889035491353769sdata=KwNlcCPd77Zbg%2FygYwgge%2B3M%2BMZDMuonjhzlNaTlG60%3Dreserved=0 @rbowen
Re: 回复：Re: Establishing an Events PMC?
Yes, you can absolutely count on me to help in any way possible. I'd love to be a part of closing the loop on what we started all those years ago. I've been much less active recently it would be an honor to help you kick of the next stage. Ross From: Liu Ted Sent: Friday, March 22, 2019 6:54 PM To: dev@community.apache.org; Rich Bowen; dev@community.apache.org Subject: 回复：Re: Establishing an Events PMC? Hi Rich, A big +1. To scale out, we may also refer to how Arduino Day operates 659 events in 106 countries on March 16 2019. I helped out and participated Arduino Day 2019 - Beijing. Please see more details in https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fday.arduino.cc%2Fdata=02%7C01%7C%7C586ed0cd64754d8cf99508d6af328e09%7C84df9e7fe9f640afb435%7C1%7C0%7C63688902899250sdata=hANvCxFPhYvJVAD%2FHg%2BfW3tWAMbRQ5TQ1M82CNkTIHM%3Dreserved=0 Best regards, Ted Liu, ASF Member, Sponsor Ambassador, Incubator PMC Member 2019 年 3 月 23 日周六 1:00，Rich Bowen 写道： On 3/22/19 12:59 PM, Kevin A. McGrail wrote: > I like the idea especially the roadshow first to establish a beachhead. I > would add that a collocated event might be ok in some circumstances too as > a first landing. Yes, I just added collocated as a category in the document I'm working on. Thanks for that reminder. > On Fri, Mar 22, 2019, 11:28 Rich Bowen >> Several years ago, due to many reasons (let's call it "dysfunction" for >> now) ConCom - the Conferences Committee - was disbanded by the Board, >> and replaced with a single individual - myself - designated as VP >> Conferences. This was largely due to break the gridlock of dealing with >> 30 people, with 50 opinions, for every single time-sensitive decision >> around events. >> >> So far, so good. >> >> As we are faced with a sudden explosive expansion in our official stable >> of events, we are building ad-hoc processes for managing these. >> >> Again, so far, so good. Having dedicated per-event leads is working >> remarkably well in 2019. >> >> I have ... concerns ... going into 2020. With pushes to add events in >> Brazil, China, South Korea, Japan, India, and who knows where else, I am >> concerned that this is going to get away from us again. And it's not so >> much about control, as about having early failures in new markets and >> harming our chances for the future. >> >> I would like, for example, to have policies around how we expand into >> new regions. Like, say, that you can't do an "ApacheCon" in a new region >> before doing a "Roadshow" there to scout it out, so to speak. I don't >> want to squish enthusiasm. I also don't want to suddenly be expected to >> fund, promote, and organize 8 conference with a machine designed to run >> two. >> >> I digress. >> >> I would like to propose the following. >> >> 1) That we (primarily, myself, Ross, and any former members of ConCom >> who are able to participate) clearly document why ConCom failed, and was >> disbanded. To do this in a dispassionate non-fault-finding way. >> >> 2) That we document how the new Events organization will be managed, >> explicitly documenting ways that we will avoid the failings of ConCom. >> >> 3) That we establish a new Events PMC, documenting how it will related >> to both Marketing and ComDev (since there will always be overlap in >> those two places). >> >> Ross, is this something that you can help me with over the coming 6 >> months or so? >> >> -- >> Rich Bowen - rbo...@rcbowen.com >> https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frcbowen.com%2Fdata=02%7C01%7C%7C586ed0cd64754d8cf99508d6af328e09%7C84df9e7fe9f640afb435%7C1%7C0%7C63688902899250sdata=syaOCGLE4KYjBKwYz3429kqiY4JJv%2FdLNSs%2BGiWlGCc%3Dreserved=0 >> @rbowen >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> > -- Rich Bowen - rbo...@rcbowen.com https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frcbowen.com%2Fdata=02%7C01%7C%7C586ed0cd64754d8cf99508d6af328e09%7C84df9e7fe9f640afb435%7C1%7C0%7C63688902899250sdata=syaOCGLE4KYjBKwYz3429kqiY4JJv%2FdLNSs%2BGiWlGCc%3Dreserved=0 @rbowen - 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: Establishing an Events PMC?
Hi Rich, A big +1. To scale out, we may also refer to how Arduino Day operates 659 events in 106 countries on March 16 2019. I helped out and participated Arduino Day 2019 - Beijing. Please see more details in https://day.arduino.cc/ Best regards, Ted Liu, ASF Member, Sponsor Ambassador, Incubator PMC Member 2019 年 3 月 23 日周六 1:00，Rich Bowen 写道： On 3/22/19 12:59 PM, Kevin A. McGrail wrote: > I like the idea especially the roadshow first to establish a beachhead. I > would add that a collocated event might be ok in some circumstances too as > a first landing. Yes, I just added collocated as a category in the document I'm working on. Thanks for that reminder. > On Fri, Mar 22, 2019, 11:28 Rich Bowen >> Several years ago, due to many reasons (let's call it "dysfunction" for >> now) ConCom - the Conferences Committee - was disbanded by the Board, >> and replaced with a single individual - myself - designated as VP >> Conferences. This was largely due to break the gridlock of dealing with >> 30 people, with 50 opinions, for every single time-sensitive decision >> around events. >> >> So far, so good. >> >> As we are faced with a sudden explosive expansion in our official stable >> of events, we are building ad-hoc processes for managing these. >> >> Again, so far, so good. Having dedicated per-event leads is working >> remarkably well in 2019. >> >> I have ... concerns ... going into 2020. With pushes to add events in >> Brazil, China, South Korea, Japan, India, and who knows where else, I am >> concerned that this is going to get away from us again. And it's not so >> much about control, as about having early failures in new markets and >> harming our chances for the future. >> >> I would like, for example, to have policies around how we expand into >> new regions. Like, say, that you can't do an "ApacheCon" in a new region >> before doing a "Roadshow" there to scout it out, so to speak. I don't >> want to squish enthusiasm. I also don't want to suddenly be expected to >> fund, promote, and organize 8 conference with a machine designed to run >> two. >> >> I digress. >> >> I would like to propose the following. >> >> 1) That we (primarily, myself, Ross, and any former members of ConCom >> who are able to participate) clearly document why ConCom failed, and was >> disbanded. To do this in a dispassionate non-fault-finding way. >> >> 2) That we document how the new Events organization will be managed, >> explicitly documenting ways that we will avoid the failings of ConCom. >> >> 3) That we establish a new Events PMC, documenting how it will related >> to both Marketing and ComDev (since there will always be overlap in >> those two places). >> >> Ross, is this something that you can help me with over the coming 6 >> months or so? >> >> -- >> 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 >> >> > -- 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"
Striving for an ideal is good. Doing away with it entirely feels like giving up on it and admitting defeat. Dinesh > On Mar 22, 2019, at 4:24 PM, Naomi Slater wrote: > > I suspect the answer is not to replace the word but to do away with it > entirely > >> On Fri 22. Mar 2019 at 21:28, Roman Shaposhnik wrote: >> >>> On Fri, Mar 22, 2019 at 9:59 AM Rich Bowen wrote: On 3/22/19 3:03 AM, Roman Shaposhnik wrote: It would be very important to come up with a replacement that is as effective as what we're trying to replace. Frankly, I don't know a single candidate. >>> >>> As discussed elsewhere in the thread, simply coming up with a new word, >>> while potentially helpful in starting conversations, doesn't really >>> address the underlying problem. And each new word (do-ocracy is one that >>> has been proposed, for example) comes with its own set of concerns and >>> baggage. >> >> FWIW: the only word I can 100% embrace as a wholesale replacement >> of meritocracy is do-ocracy. >> >>> We have had the "what other word can we use" conversation at least once >>> on this mailing list, and at least one on members, in the last 2 years. >>> Neither conversation resulted in anything actionable. >> >> That's basically my point. >> >> Thanks, >> Roman. >> >> - >> 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 3/22/2019 7:28 PM, Roman Shaposhnik wrote: > On Fri, Mar 22, 2019 at 4:25 PM Naomi Slater wrote: >> I suspect the answer is not to replace the word but to do away with it >> entirely > I still would like to have a succinct handle to reference the ethos of ASF. >From my experience, there are words that are landmines in open source: free and meritocracy happen to be such words without question. Switching meritocracy to do-ocracy might be a good way to handle it and I know that's what other orgs like LF have done. However, we are straddling the middle of having both principles of duopolies like JFDI and elections with the necessary hierarchy for fiscal / corporate oversight. That means the definition of do-ocracy doesn't fit. I usually do mention the issues like a meritocracy often morphs into a dictatorship and that people can amass too much merit that it's viewed as harmful. I see that when I mention my $0.02 sometimes and it's taken with more weight than I intend. So like Roman, I've been search for a word or a succinct handle to refer to it. I don't have an answer but agree that do-ocracy and meritocracy don't work well. I usually say all the things we aren't in my Yet Another The Apache Way talk (TATAW per Daniel Ruggeri). I think I'll start saying we aren't a meritocracy OR a do-ocracy/duopoly either but it's the closest thing I know of. I don't like the idea of NOT saying what we are so do you have suggestion of what word you think fits? Regards, KAM - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On Fri, Mar 22, 2019 at 4:25 PM Naomi Slater wrote: > > I suspect the answer is not to replace the word but to do away with it > entirely I still would like to have a succinct handle to reference the ethos of ASF. Thanks, Roman. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
I suspect the answer is not to replace the word but to do away with it entirely On Fri 22. Mar 2019 at 21:28, Roman Shaposhnik wrote: > On Fri, Mar 22, 2019 at 9:59 AM Rich Bowen wrote: > > On 3/22/19 3:03 AM, Roman Shaposhnik wrote: > > > It would be very important to come up with a replacement that is > > > as effective as what we're trying to replace. Frankly, I don't know > > > a single candidate. > > > > As discussed elsewhere in the thread, simply coming up with a new word, > > while potentially helpful in starting conversations, doesn't really > > address the underlying problem. And each new word (do-ocracy is one that > > has been proposed, for example) comes with its own set of concerns and > > baggage. > > FWIW: the only word I can 100% embrace as a wholesale replacement > of meritocracy is do-ocracy. > > > We have had the "what other word can we use" conversation at least once > > on this mailing list, and at least one on members, in the last 2 years. > > Neither conversation resulted in anything actionable. > > That's basically my point. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Apache Brochure/Tri-Fold?
OK, I will ramp down on that unless someone else has time to get it into shape for me to run 50 copies or something at Fedex/Kinkos on Sunday. Regards, KAM On 3/22/2019 5:11 PM, Sally Khudairi wrote: > Kevin, that document hasn't been updated in quite a long time. > > Whomever from ComDev that needs it works with me to bring it up to current > messaging and stats. > > Please do not print it in its current state for Monday. > > Regards, > Sally > > - - - > Vice President Marketing & Publicity > Vice President Sponsor Relations > The Apache Software Foundation > > Tel +1 617 921 8656 | s...@apache.org > > On Thu, Mar 21, 2019, at 20:57, Kevin A. McGrail wrote: >> Anyone know where the source for this is at so I can print some for the >> roadshow? >> >> Regards, >> >> KAM >> >> -- >> Kevin A. McGrail >> Member, Apache Software Foundation >> Chair Emeritus Apache SpamAssassin Project >> https://www.linkedin.com/in/kmcgrail - 703.798.0171 >> >> -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171 - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Brochure/Tri-Fold?
Kevin, that document hasn't been updated in quite a long time. Whomever from ComDev that needs it works with me to bring it up to current messaging and stats. Please do not print it in its current state for Monday. Regards, Sally - - - Vice President Marketing & Publicity Vice President Sponsor Relations The Apache Software Foundation Tel +1 617 921 8656 | s...@apache.org On Thu, Mar 21, 2019, at 20:57, Kevin A. McGrail wrote: > Anyone know where the source for this is at so I can print some for the > roadshow? > > Regards, > > KAM > > -- > Kevin A. McGrail > Member, Apache Software Foundation > Chair Emeritus Apache SpamAssassin Project > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
[jira] [Commented] (COMDEV-307) GSoC - Allura - responsive web pages
[ https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799334#comment-16799334 ] Dave Brondsema commented on COMDEV-307: --- Hi [~dilshandilip] I'd recommend first installing Allura and getting it running so you can be familiar with it. Then you could try experimenting with a simple page template and see how it works. Join our dev mailing list at [https://lists.apache.org/list.html?d...@allura.apache.org] to ask any questions. It'd be good to do some initial small work with Allura (see the contributing section of the docs). > GSoC - Allura - responsive web pages > > > Key: COMDEV-307 > URL: https://issues.apache.org/jira/browse/COMDEV-307 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: css, gsoc2019, html, javascript, sass, ux > > Allura's web frontend should be responsive. Initial prototyping work has > begun using the Foundation framework: > [https://foundation.zurb.com/sites/docs/] More initial work needs to be done > to develop a reliable pattern, and then convert existing templates to use > Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an > intuitive way for all screen sizes. Interactivity via JS may need to be > updated as well. Some more details are here > [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On Fri, Mar 22, 2019 at 9:59 AM Rich Bowen wrote: > On 3/22/19 3:03 AM, Roman Shaposhnik wrote: > > It would be very important to come up with a replacement that is > > as effective as what we're trying to replace. Frankly, I don't know > > a single candidate. > > As discussed elsewhere in the thread, simply coming up with a new word, > while potentially helpful in starting conversations, doesn't really > address the underlying problem. And each new word (do-ocracy is one that > has been proposed, for example) comes with its own set of concerns and > baggage. FWIW: the only word I can 100% embrace as a wholesale replacement of meritocracy is do-ocracy. > We have had the "what other word can we use" conversation at least once > on this mailing list, and at least one on members, in the last 2 years. > Neither conversation resulted in anything actionable. That's basically my point. Thanks, Roman. - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Brochure/Tri-Fold?
On Fri, 22 Mar 2019 at 17:47, Dmitriy Pavlov wrote: > > Thanks for this idea, for me it will be also easier to keep track. > > Issue: https://issues.apache.org/jira/browse/COMDEV-315 > > Could you please assign me to contributor role, so I can assign this issue > to me? AFAIK issues are normally assigned to the committer doing the work. When a committer starts, they assign it to themselves so others know someone is handling it. > пт, 22 мар. 2019 г. в 20:42, sebb : > > > On Fri, 22 Mar 2019 at 15:50, Dmitriy Pavlov wrote: > > > > > > It's a pity. Also, I can prepare .xfc files and send it to a ComDev > > > committer via email. Who can commit it later? > > > > Better to create a JIRA COMDEV issue and attach it there please. > > > > https://issues.apache.org/jira/browse/COMDEV > > > > That would make it easier to keep track of progress, and allow others > > to help/comment. > > > > @comdev: Maybe ask Infra to create a (read-only) GitHub mirror of the > > SVN repo so non-committers can create PRs etc? > > > > > пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > > > > > > > > > > > > > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > > > > > Hi Roman, > > > > > > > > > > I've tried to update it using GIMP, and it seems I can fix it. It > > refers > > > > to > > > > > "Standard" font. If I set Arial it looks ok. > > > > > > > > > > Can I commit changes later using general Apache Committer > > credentials or > > > > > should I be committer in the ComDev? > > > > > > > > One must be a ComDev committer to commit there. > > > > > > > > > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik > >: > > > > > > > > > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > > > > > > >> wrote: > > > > >>> > > > > >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: > > > > Anyone know where the source for this is at so I can print some > > for > > > > the > > > > roadshow? > > > > >>> > > > > >>> Last updated 2017, but it is a trifold brochure layout: > > > > >>> > > > > >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > > > > >> > > > > >> As a side note, the Russian translation has a very messed up font > > > > kerning. > > > > >> Would be great to fix it. > > > > >> > > > > >> Thanks, > > > > >> Roman. > > > > >> > > > > >> > > - > > > > >> 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 > > > > > > > > > > > > - > > 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"
Hi Naomi, Thanks for (re)starting this discussion. I’ve come to agree that there are serious problems with the word “meritocracy”. Everyone and every culture brings their own ever evolving definition. I brought up the Incubator because mentoring new podlings currently includes teaching that the ASF is a meritocracy and often pushing these projects into actually having discussions about which contributors should be invited to be committers and/or PPMC members. They each achieve their own “bar” for this. Some are “higher" and some “lower”. The ones that set a higher bar may be projects that will never grow enough to be sustainable and diverse enough to withstand the natural attrition of the “volunteers” that are currently driving the project. To me the “non-expiring merit” that should be identified by an Apache Project Community is those who show that they “care" and willingly, regularly make even small contributions to the community. This can be as “insignificant” (to those who set a high bar) as answering user questions with regularity. I don’t know if there is a single word for it, but I think we should be looking for those who willingly contribute in an Open, Sharing, Diverse, Inclusive, and Sustainable way. In many projects there have been moments when a Meritorious, High Energy, Driving person has become poisonous to that community and has needed to be driven away. This is never a fun process. A sustainable community that recognizes small contributions and grows volunteers can survive this. If not then the project is headed to the Attic or will be forked. I agree with Rich that having this discussion with membership will encounter a fair amount of pushback (and filibustering in the 19th century sense of the word) Regards, Dave > On Mar 22, 2019, at 10:06 AM, Naomi Slater wrote: > > agreed re "do-ocracy" > > 1) like Patricia points out, like "meritocracy", it presupposes our past > and future ability implement such a system > > 2) even if we *have* been successful at implementing such a system, is that > really enough for us, from an ideological perspective? are we not concerned > with who *isn't* contributing, and why? what we can do about it, etc, etc > > this is why I think it's important to separate this into to components: (a) > a statement about what we want to achieve that explicitly acknowledges the > potential for bias and discrimination, and (b) practical > information/guidance that helps us work towards that > > On Fri, 22 Mar 2019 at 17:59, Rich Bowen wrote: > >> >> >> On 3/22/19 3:03 AM, Roman Shaposhnik wrote: >>> It would be very important to come up with a replacement that is >>> as effective as what we're trying to replace. Frankly, I don't know >>> a single candidate. >> >> As discussed elsewhere in the thread, simply coming up with a new word, >> while potentially helpful in starting conversations, doesn't really >> address the underlying problem. And each new word (do-ocracy is one that >> has been proposed, for example) comes with its own set of concerns and >> baggage. >> >> We have had the "what other word can we use" conversation at least once >> on this mailing list, and at least one on members, in the last 2 years. >> Neither conversation resulted in anything actionable. >> >> -- >> 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 >> >> - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Brochure/Tri-Fold?
Thanks for this idea, for me it will be also easier to keep track. Issue: https://issues.apache.org/jira/browse/COMDEV-315 Could you please assign me to contributor role, so I can assign this issue to me? пт, 22 мар. 2019 г. в 20:42, sebb : > On Fri, 22 Mar 2019 at 15:50, Dmitriy Pavlov wrote: > > > > It's a pity. Also, I can prepare .xfc files and send it to a ComDev > > committer via email. Who can commit it later? > > Better to create a JIRA COMDEV issue and attach it there please. > > https://issues.apache.org/jira/browse/COMDEV > > That would make it easier to keep track of progress, and allow others > to help/comment. > > @comdev: Maybe ask Infra to create a (read-only) GitHub mirror of the > SVN repo so non-committers can create PRs etc? > > > пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > > > > > > > > > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > > > > Hi Roman, > > > > > > > > I've tried to update it using GIMP, and it seems I can fix it. It > refers > > > to > > > > "Standard" font. If I set Arial it looks ok. > > > > > > > > Can I commit changes later using general Apache Committer > credentials or > > > > should I be committer in the ComDev? > > > > > > One must be a ComDev committer to commit there. > > > > > > > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik >: > > > > > > > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > > > > >> wrote: > > > >>> > > > >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: > > > Anyone know where the source for this is at so I can print some > for > > > the > > > roadshow? > > > >>> > > > >>> Last updated 2017, but it is a trifold brochure layout: > > > >>> > > > >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > > > >> > > > >> As a side note, the Russian translation has a very messed up font > > > kerning. > > > >> Would be great to fix it. > > > >> > > > >> Thanks, > > > >> Roman. > > > >> > > > >> > - > > > >> 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 > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
[jira] [Created] (COMDEV-315) Fix Russian translation for Apache Brochure
Dmitriy Pavlov created COMDEV-315: - Summary: Fix Russian translation for Apache Brochure Key: COMDEV-315 URL: https://issues.apache.org/jira/browse/COMDEV-315 Project: Community Development Issue Type: Bug Reporter: Dmitriy Pavlov The Russian translation has a very messed up font kerning. Related discussion: https://lists.apache.org/thread.html/c926035ccb50282b9769770c8276c8c1f172ee6c68b32b37d6381cf7@%3Cdev.community.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Apache Brochure/Tri-Fold?
On Fri, 22 Mar 2019 at 15:50, Dmitriy Pavlov wrote: > > It's a pity. Also, I can prepare .xfc files and send it to a ComDev > committer via email. Who can commit it later? Better to create a JIRA COMDEV issue and attach it there please. https://issues.apache.org/jira/browse/COMDEV That would make it easier to keep track of progress, and allow others to help/comment. @comdev: Maybe ask Infra to create a (read-only) GitHub mirror of the SVN repo so non-committers can create PRs etc? > пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > > > > > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > > > Hi Roman, > > > > > > I've tried to update it using GIMP, and it seems I can fix it. It refers > > to > > > "Standard" font. If I set Arial it looks ok. > > > > > > Can I commit changes later using general Apache Committer credentials or > > > should I be committer in the ComDev? > > > > One must be a ComDev committer to commit there. > > > > > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik : > > > > > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > > >> wrote: > > >>> > > >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: > > Anyone know where the source for this is at so I can print some for > > the > > roadshow? > > >>> > > >>> Last updated 2017, but it is a trifold brochure layout: > > >>> > > >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > > >> > > >> As a side note, the Russian translation has a very messed up font > > kerning. > > >> Would be great to fix it. > > >> > > >> Thanks, > > >> Roman. > > >> > > >> - > > >> 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 > > > > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Help with task: Ensure all Apache TLPs have Wikipedia pages
I would like to help out with the task listed at /task.html?0b349bee
Re: on "meritocracy"
agreed re "do-ocracy" 1) like Patricia points out, like "meritocracy", it presupposes our past and future ability implement such a system 2) even if we *have* been successful at implementing such a system, is that really enough for us, from an ideological perspective? are we not concerned with who *isn't* contributing, and why? what we can do about it, etc, etc this is why I think it's important to separate this into to components: (a) a statement about what we want to achieve that explicitly acknowledges the potential for bias and discrimination, and (b) practical information/guidance that helps us work towards that On Fri, 22 Mar 2019 at 17:59, Rich Bowen wrote: > > > On 3/22/19 3:03 AM, Roman Shaposhnik wrote: > > It would be very important to come up with a replacement that is > > as effective as what we're trying to replace. Frankly, I don't know > > a single candidate. > > As discussed elsewhere in the thread, simply coming up with a new word, > while potentially helpful in starting conversations, doesn't really > address the underlying problem. And each new word (do-ocracy is one that > has been proposed, for example) comes with its own set of concerns and > baggage. > > We have had the "what other word can we use" conversation at least once > on this mailing list, and at least one on members, in the last 2 years. > Neither conversation resulted in anything actionable. > > -- > 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: Who "manages" the RedBubble account?
On 19/03/2019 23:49, Shane Curcuru wrote: > Related question: do we have a canonical URL to send people to the > Redbubble store? In particular are we intending to list it anywhere on > our website(s)? I suggest: https://www.redbubble.com/people/comdev/portfolio?asc=u as that groups products by project. Mark > I would imagine it should be under the www.a.o/support apache link, as > well as somewhere on the community.a.o site. > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Establishing an Events PMC?
On 3/22/19 12:59 PM, Kevin A. McGrail wrote: > I like the idea especially the roadshow first to establish a beachhead. I > would add that a collocated event might be ok in some circumstances too as > a first landing. Yes, I just added collocated as a category in the document I'm working on. Thanks for that reminder. > On Fri, Mar 22, 2019, 11:28 Rich Bowen >> Several years ago, due to many reasons (let's call it "dysfunction" for >> now) ConCom - the Conferences Committee - was disbanded by the Board, >> and replaced with a single individual - myself - designated as VP >> Conferences. This was largely due to break the gridlock of dealing with >> 30 people, with 50 opinions, for every single time-sensitive decision >> around events. >> >> So far, so good. >> >> As we are faced with a sudden explosive expansion in our official stable >> of events, we are building ad-hoc processes for managing these. >> >> Again, so far, so good. Having dedicated per-event leads is working >> remarkably well in 2019. >> >> I have ... concerns ... going into 2020. With pushes to add events in >> Brazil, China, South Korea, Japan, India, and who knows where else, I am >> concerned that this is going to get away from us again. And it's not so >> much about control, as about having early failures in new markets and >> harming our chances for the future. >> >> I would like, for example, to have policies around how we expand into >> new regions. Like, say, that you can't do an "ApacheCon" in a new region >> before doing a "Roadshow" there to scout it out, so to speak. I don't >> want to squish enthusiasm. I also don't want to suddenly be expected to >> fund, promote, and organize 8 conference with a machine designed to run >> two. >> >> I digress. >> >> I would like to propose the following. >> >> 1) That we (primarily, myself, Ross, and any former members of ConCom >> who are able to participate) clearly document why ConCom failed, and was >> disbanded. To do this in a dispassionate non-fault-finding way. >> >> 2) That we document how the new Events organization will be managed, >> explicitly documenting ways that we will avoid the failings of ConCom. >> >> 3) That we establish a new Events PMC, documenting how it will related >> to both Marketing and ComDev (since there will always be overlap in >> those two places). >> >> Ross, is this something that you can help me with over the coming 6 >> months or so? >> >> -- >> 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 >> >> > -- 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"
On 3/22/19 3:03 AM, Roman Shaposhnik wrote: > It would be very important to come up with a replacement that is > as effective as what we're trying to replace. Frankly, I don't know > a single candidate. As discussed elsewhere in the thread, simply coming up with a new word, while potentially helpful in starting conversations, doesn't really address the underlying problem. And each new word (do-ocracy is one that has been proposed, for example) comes with its own set of concerns and baggage. We have had the "what other word can we use" conversation at least once on this mailing list, and at least one on members, in the last 2 years. Neither conversation resulted in anything actionable. -- 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: Establishing an Events PMC?
I like the idea especially the roadshow first to establish a beachhead. I would add that a collocated event might be ok in some circumstances too as a first landing. On Fri, Mar 22, 2019, 11:28 Rich Bowen Several years ago, due to many reasons (let's call it "dysfunction" for > now) ConCom - the Conferences Committee - was disbanded by the Board, > and replaced with a single individual - myself - designated as VP > Conferences. This was largely due to break the gridlock of dealing with > 30 people, with 50 opinions, for every single time-sensitive decision > around events. > > So far, so good. > > As we are faced with a sudden explosive expansion in our official stable > of events, we are building ad-hoc processes for managing these. > > Again, so far, so good. Having dedicated per-event leads is working > remarkably well in 2019. > > I have ... concerns ... going into 2020. With pushes to add events in > Brazil, China, South Korea, Japan, India, and who knows where else, I am > concerned that this is going to get away from us again. And it's not so > much about control, as about having early failures in new markets and > harming our chances for the future. > > I would like, for example, to have policies around how we expand into > new regions. Like, say, that you can't do an "ApacheCon" in a new region > before doing a "Roadshow" there to scout it out, so to speak. I don't > want to squish enthusiasm. I also don't want to suddenly be expected to > fund, promote, and organize 8 conference with a machine designed to run > two. > > I digress. > > I would like to propose the following. > > 1) That we (primarily, myself, Ross, and any former members of ConCom > who are able to participate) clearly document why ConCom failed, and was > disbanded. To do this in a dispassionate non-fault-finding way. > > 2) That we document how the new Events organization will be managed, > explicitly documenting ways that we will avoid the failings of ConCom. > > 3) That we establish a new Events PMC, documenting how it will related > to both Marketing and ComDev (since there will always be overlap in > those two places). > > Ross, is this something that you can help me with over the coming 6 > months or so? > > -- > 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"
On 3/22/19 12:49 PM, Dave Fisher wrote: > Hi Rich, > > I’m not sure if you included the Incubator in your analysis. We have mentions > of meritoc on six pages along with references to foundation pages and links. > > The pages are: > > guides/proposal.html > guides/graduation.html > guides/community.html > guides/ppmc.html > index.html > policy/incubation.html I didn't, as that's not content that I've ever touched, so I don't have a checkout of that. > > Please provide guidance on changes to the Incubator. Yeah, that guidance is definitely something we should come up with. But I don't think that's going to be something that we can just issue an edict on without broader discussion - a broader discussion which will probably involve the membership, and much vitriol. Not looking forward to that. But my initial guidance, at least coming out of this thread, would be edits that reflect s/is a meritocracy/strives towards meritocratic ideals/ or something like that. >> On Mar 22, 2019, at 8:29 AM, Rich Bowen wrote: >> >> >> >> On 3/22/19 10:55 AM, Naomi Slater wrote many good and helpful things. >> >> Narrowing it down to the "action items": >> >>> there are two issues here: >>> >>> (1) improving our external communication in a way that communicates our >>> desire to build an inclusive, respectful, safe, and equitable organization >> >> This is something that we can do immediately, in small incremental >> patches, as we find that content. I have, as mentioned, taken a first >> (incomplete!) step to do this on community.apache.org >> >> I realized this morning that one of those changes may have stepped on >> Bertrand's toes, since he was the primary driver behind the Maturity >> Model prose, which is used in more than just this one place. We (I?) >> need to connect with Bertrand to ensure that the change doesn't get >> reverted in future iterations of that content. >> >> Meanwhile, anyone here can start looking through the 150 (ish?) places >> on www.apache.org where the term meritocra(cy|tic) is used, and >> determine whether it's valuable to enhance how that is phrased. >> >>> (2) actually changing the way that we operate to better work towards those >>> goals >>> >>> doing (2) is where we will continue to be met with resistance. with people >>> who are upset, offended, or irritated by the work we're trying to do, the >>> things we're saying, and the changes we're trying to make >> >> To which we should, as the Community Development PMC, push back and >> insist that we're working towards the development of the community, as >> per our charter, and that the changes are NOT about what was done in the >> past, or a slight against who did it, but that they are intended to >> welcome the next generation of our community, and build a strong tomorrow. >> >> Whatever we have done wrong in the past, I feel like it's really >> important to focus on the future. I mean, it's *useful*, as Naomi has >> said, to understand the past, I don't know about y'all, but all I have >> time for is the future. >> >> As was illustrated brilliantly when Sharan did the community survey a >> couple of years ago, the people who complained that it was a waste of >> time did not, in the long run, have any right to tell us not to waste >> our time in that way. And good came from it. >> >> The "small incremental changes" model applies. >> >> -- >> 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 >> > > > - > 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"
Hi Rich, I’m not sure if you included the Incubator in your analysis. We have mentions of meritoc on six pages along with references to foundation pages and links. The pages are: guides/proposal.html guides/graduation.html guides/community.html guides/ppmc.html index.html policy/incubation.html Please provide guidance on changes to the Incubator. Regards, Dave > On Mar 22, 2019, at 8:29 AM, Rich Bowen wrote: > > > > On 3/22/19 10:55 AM, Naomi Slater wrote many good and helpful things. > > Narrowing it down to the "action items": > >> there are two issues here: >> >> (1) improving our external communication in a way that communicates our >> desire to build an inclusive, respectful, safe, and equitable organization > > This is something that we can do immediately, in small incremental > patches, as we find that content. I have, as mentioned, taken a first > (incomplete!) step to do this on community.apache.org > > I realized this morning that one of those changes may have stepped on > Bertrand's toes, since he was the primary driver behind the Maturity > Model prose, which is used in more than just this one place. We (I?) > need to connect with Bertrand to ensure that the change doesn't get > reverted in future iterations of that content. > > Meanwhile, anyone here can start looking through the 150 (ish?) places > on www.apache.org where the term meritocra(cy|tic) is used, and > determine whether it's valuable to enhance how that is phrased. > >> (2) actually changing the way that we operate to better work towards those >> goals >> >> doing (2) is where we will continue to be met with resistance. with people >> who are upset, offended, or irritated by the work we're trying to do, the >> things we're saying, and the changes we're trying to make > > To which we should, as the Community Development PMC, push back and > insist that we're working towards the development of the community, as > per our charter, and that the changes are NOT about what was done in the > past, or a slight against who did it, but that they are intended to > welcome the next generation of our community, and build a strong tomorrow. > > Whatever we have done wrong in the past, I feel like it's really > important to focus on the future. I mean, it's *useful*, as Naomi has > said, to understand the past, I don't know about y'all, but all I have > time for is the future. > > As was illustrated brilliantly when Sharan did the community survey a > couple of years ago, the people who complained that it was a waste of > time did not, in the long run, have any right to tell us not to waste > our time in that way. And good came from it. > > The "small incremental changes" model applies. > > -- > 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 > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
On 3/22/19, 12:04 AM, "Roman Shaposhnik" wrote: It would be very important to come up with a replacement that is as effective as what we're trying to replace. Frankly, I don't know a single candidate. Does anyone? Do-ocracy - I think we've used this word before to describe the ASF. Seems to have definitions in the Urban Dictionary. Action-ocracy - This might be a new word and thus we can define it to be what we want it to be. HTH, -Alex
Re: Apache Brochure/Tri-Fold?
It's a pity. Also, I can prepare .xfc files and send it to a ComDev committer via email. Who can commit it later? пт, 22 мар. 2019 г. в 18:34, Rich Bowen : > > > On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > > Hi Roman, > > > > I've tried to update it using GIMP, and it seems I can fix it. It refers > to > > "Standard" font. If I set Arial it looks ok. > > > > Can I commit changes later using general Apache Committer credentials or > > should I be committer in the ComDev? > > One must be a ComDev committer to commit there. > > > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik : > > > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > >> wrote: > >>> > >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: > Anyone know where the source for this is at so I can print some for > the > roadshow? > >>> > >>> Last updated 2017, but it is a trifold brochure layout: > >>> > >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > >> > >> As a side note, the Russian translation has a very messed up font > kerning. > >> Would be great to fix it. > >> > >> Thanks, > >> Roman. > >> > >> - > >> 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"
On 3/22/19 10:55 AM, Naomi Slater wrote many good and helpful things. Narrowing it down to the "action items": > there are two issues here: > > (1) improving our external communication in a way that communicates our > desire to build an inclusive, respectful, safe, and equitable organization This is something that we can do immediately, in small incremental patches, as we find that content. I have, as mentioned, taken a first (incomplete!) step to do this on community.apache.org I realized this morning that one of those changes may have stepped on Bertrand's toes, since he was the primary driver behind the Maturity Model prose, which is used in more than just this one place. We (I?) need to connect with Bertrand to ensure that the change doesn't get reverted in future iterations of that content. Meanwhile, anyone here can start looking through the 150 (ish?) places on www.apache.org where the term meritocra(cy|tic) is used, and determine whether it's valuable to enhance how that is phrased. > (2) actually changing the way that we operate to better work towards those > goals > > doing (2) is where we will continue to be met with resistance. with people > who are upset, offended, or irritated by the work we're trying to do, the > things we're saying, and the changes we're trying to make To which we should, as the Community Development PMC, push back and insist that we're working towards the development of the community, as per our charter, and that the changes are NOT about what was done in the past, or a slight against who did it, but that they are intended to welcome the next generation of our community, and build a strong tomorrow. Whatever we have done wrong in the past, I feel like it's really important to focus on the future. I mean, it's *useful*, as Naomi has said, to understand the past, I don't know about y'all, but all I have time for is the future. As was illustrated brilliantly when Sharan did the community survey a couple of years ago, the people who complained that it was a waste of time did not, in the long run, have any right to tell us not to waste our time in that way. And good came from it. The "small incremental changes" model applies. -- 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: Apache Brochure/Tri-Fold?
On 3/22/19 11:24 AM, Dmitriy Pavlov wrote: > Hi Roman, > > I've tried to update it using GIMP, and it seems I can fix it. It refers to > "Standard" font. If I set Arial it looks ok. > > Can I commit changes later using general Apache Committer credentials or > should I be committer in the ComDev? One must be a ComDev committer to commit there. > пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik : > >> On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru >> wrote: >>> >>> Kevin A. McGrail wrote on 3/21/19 8:57 PM: Anyone know where the source for this is at so I can print some for the roadshow? >>> >>> Last updated 2017, but it is a trifold brochure layout: >>> >>> https://svn.apache.org/repos/asf/comdev/marketing/brochure/ >> >> As a side note, the Russian translation has a very messed up font kerning. >> Would be great to fix it. >> >> Thanks, >> Roman. >> >> - >> 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
Establishing an Events PMC?
Several years ago, due to many reasons (let's call it "dysfunction" for now) ConCom - the Conferences Committee - was disbanded by the Board, and replaced with a single individual - myself - designated as VP Conferences. This was largely due to break the gridlock of dealing with 30 people, with 50 opinions, for every single time-sensitive decision around events. So far, so good. As we are faced with a sudden explosive expansion in our official stable of events, we are building ad-hoc processes for managing these. Again, so far, so good. Having dedicated per-event leads is working remarkably well in 2019. I have ... concerns ... going into 2020. With pushes to add events in Brazil, China, South Korea, Japan, India, and who knows where else, I am concerned that this is going to get away from us again. And it's not so much about control, as about having early failures in new markets and harming our chances for the future. I would like, for example, to have policies around how we expand into new regions. Like, say, that you can't do an "ApacheCon" in a new region before doing a "Roadshow" there to scout it out, so to speak. I don't want to squish enthusiasm. I also don't want to suddenly be expected to fund, promote, and organize 8 conference with a machine designed to run two. I digress. I would like to propose the following. 1) That we (primarily, myself, Ross, and any former members of ConCom who are able to participate) clearly document why ConCom failed, and was disbanded. To do this in a dispassionate non-fault-finding way. 2) That we document how the new Events organization will be managed, explicitly documenting ways that we will avoid the failings of ConCom. 3) That we establish a new Events PMC, documenting how it will related to both Marketing and ComDev (since there will always be overlap in those two places). Ross, is this something that you can help me with over the coming 6 months or so? -- 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: Apache Brochure/Tri-Fold?
Hi Roman, I've tried to update it using GIMP, and it seems I can fix it. It refers to "Standard" font. If I set Arial it looks ok. Can I commit changes later using general Apache Committer credentials or should I be committer in the ComDev? Sincerely Dmitriy Pavlov пт, 22 мар. 2019 г. в 05:21, Roman Shaposhnik : > On Thu, Mar 21, 2019 at 6:23 PM Shane Curcuru > wrote: > > > > Kevin A. McGrail wrote on 3/21/19 8:57 PM: > > > Anyone know where the source for this is at so I can print some for the > > > roadshow? > > > > Last updated 2017, but it is a trifold brochure layout: > > > > https://svn.apache.org/repos/asf/comdev/marketing/brochure/ > > As a side note, the Russian translation has a very messed up font kerning. > Would be great to fix it. > > Thanks, > Roman. > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
sorry for the double post... I just noticed, from the blog post I linked, that GitHub replaced their "meritocracy" slogan with: "In collaboration we trust." I like that! On Fri, 22 Mar 2019 at 15:55, Naomi Slater wrote: > "Word origins are just that - origins. What matters is the current > meaning, not where they originated. You can play that kind of game with > lots of English words, many of which have absurd origin stories." > > but it's not just a word origin. that was my point. the moral issues the > satirical novel moralizes about are directly applicable to us and our > implementation of "meritocracy". that's what makes it ironic! > > "What's relevant is now." > > but even if we look past that and just look at what the word means *now*, > we still have an issue with the way it makes us look. organizations using > the word "meritocracy" was a red flag for the sorts of people our > organization sorely lacks all the way back in 2014 > > cf. https://readwrite.com/2014/01/24/github-meritocracy-rug/ > > and that public perception has only worsened since. the fact it's now > showing up in FastCompany is what prompted me to start this thread > > "Crafting our message for the small number of horrible people seems less > effective" > > I'm not saying we should do that. > > there are two issues here: > > (1) improving our external communication in a way that communicates our > desire to build an inclusive, respectful, safe, and equitable organization > (2) actually changing the way that we operate to better work towards those > goals > > doing (2) is where we will continue to be met with resistance. with people > who are upset, offended, or irritated by the work we're trying to do, the > things we're saying, and the changes we're trying to make > > I'm not saying that everyone at Apache is a "pompous blow-hard". I'm > saying that I, personally, have experienced enough here (from a vocal > minority) to know that this won't be easy work > > "And these > discussions in Apache-land are pretty consistently LESS hostile than in > other communities I'm part of." > > that's true. I left Debian permanently for this reason. but it's still > bad. and it's still enough that I have known multiple people who care about > this stuff withdraw for their own emotional, psychological, and in some > cases physical health > > Roman wrote: > > "Plus I'm still not sure what's being proposed as a replacement." > > well, I suggested one approach in one of my previous emails. but I > actually don't think this is likely to be too much of an issue. I expect > that it is perfectly possible to talk about how people's contributions > ought to be recognized without mentioning "meritocracy" (as Rich hints wrt > the blog post). lots and lots of other open source projects and > organizations manage it perfectly well. we could start by looking at how > they do it > > I would focus on trying to communicate two things: > > (1) we want to build an organization that recognizes individual > contributions (with status, responsibility, and power) in a way that is > inclusive of skillset, backgrounds, cultures, race, gender, sexuality, etc, > etc > > (2) the technical details, i.e. how this happens. we already do this! our > bylaws, project bylaws, etc. but we could improve it with practical > tools/techniques/principals that can help us with inclusion, unconscious > bias, and so on > > > On Fri, 22 Mar 2019 at 15:45, Patricia Shanahan wrote: > >> On 3/22/2019 6:56 AM, Shawn McKinney wrote: >> > >> >> On Mar 22, 2019, at 2:03 AM, Roman Shaposhnik >> wrote: >> >> >> >> It would be very important to come up with a replacement that is >> >> as effective as what we're trying to replace. Frankly, I don't know >> >> a single candidate. >> >> >> >> Does anyone? >> > >> > Here are some, can’t say they carry the same level of clarity or weight. >> > >> > excellence, merit-based / merited, self-determination, deserving / >> deservingness, worthiness / being worthy of, getting one's due, be entitled >> / qualified to >> >> I suspect, without research data to back it up, that anything that >> implies that those with decision making power got there primarily >> through their own merit/deserts/worth etc. would have the same harmful >> effects as a claim to be a meritocracy. I prefer the direction that >> presents meritocracy as something towards which we can strive, but that >> has not been achieved and may never be fully achieved. Luck and having >> the right parents will go on being important. >> >> Patricia >> >> --- >> This email has been checked for viruses by AVG. >> https://www.avg.com >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >>
Re: on "meritocracy"
"Word origins are just that - origins. What matters is the current meaning, not where they originated. You can play that kind of game with lots of English words, many of which have absurd origin stories." but it's not just a word origin. that was my point. the moral issues the satirical novel moralizes about are directly applicable to us and our implementation of "meritocracy". that's what makes it ironic! "What's relevant is now." but even if we look past that and just look at what the word means *now*, we still have an issue with the way it makes us look. organizations using the word "meritocracy" was a red flag for the sorts of people our organization sorely lacks all the way back in 2014 cf. https://readwrite.com/2014/01/24/github-meritocracy-rug/ and that public perception has only worsened since. the fact it's now showing up in FastCompany is what prompted me to start this thread "Crafting our message for the small number of horrible people seems less effective" I'm not saying we should do that. there are two issues here: (1) improving our external communication in a way that communicates our desire to build an inclusive, respectful, safe, and equitable organization (2) actually changing the way that we operate to better work towards those goals doing (2) is where we will continue to be met with resistance. with people who are upset, offended, or irritated by the work we're trying to do, the things we're saying, and the changes we're trying to make I'm not saying that everyone at Apache is a "pompous blow-hard". I'm saying that I, personally, have experienced enough here (from a vocal minority) to know that this won't be easy work "And these discussions in Apache-land are pretty consistently LESS hostile than in other communities I'm part of." that's true. I left Debian permanently for this reason. but it's still bad. and it's still enough that I have known multiple people who care about this stuff withdraw for their own emotional, psychological, and in some cases physical health Roman wrote: "Plus I'm still not sure what's being proposed as a replacement." well, I suggested one approach in one of my previous emails. but I actually don't think this is likely to be too much of an issue. I expect that it is perfectly possible to talk about how people's contributions ought to be recognized without mentioning "meritocracy" (as Rich hints wrt the blog post). lots and lots of other open source projects and organizations manage it perfectly well. we could start by looking at how they do it I would focus on trying to communicate two things: (1) we want to build an organization that recognizes individual contributions (with status, responsibility, and power) in a way that is inclusive of skillset, backgrounds, cultures, race, gender, sexuality, etc, etc (2) the technical details, i.e. how this happens. we already do this! our bylaws, project bylaws, etc. but we could improve it with practical tools/techniques/principals that can help us with inclusion, unconscious bias, and so on On Fri, 22 Mar 2019 at 15:45, Patricia Shanahan wrote: > On 3/22/2019 6:56 AM, Shawn McKinney wrote: > > > >> On Mar 22, 2019, at 2:03 AM, Roman Shaposhnik > wrote: > >> > >> It would be very important to come up with a replacement that is > >> as effective as what we're trying to replace. Frankly, I don't know > >> a single candidate. > >> > >> Does anyone? > > > > Here are some, can’t say they carry the same level of clarity or weight. > > > > excellence, merit-based / merited, self-determination, deserving / > deservingness, worthiness / being worthy of, getting one's due, be entitled > / qualified to > > I suspect, without research data to back it up, that anything that > implies that those with decision making power got there primarily > through their own merit/deserts/worth etc. would have the same harmful > effects as a claim to be a meritocracy. I prefer the direction that > presents meritocracy as something towards which we can strive, but that > has not been achieved and may never be fully achieved. Luck and having > the right parents will go on being important. > > Patricia > > --- > This email has been checked for viruses by AVG. > https://www.avg.com > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: on "meritocracy"
On 3/22/2019 6:56 AM, Shawn McKinney wrote: On Mar 22, 2019, at 2:03 AM, Roman Shaposhnik wrote: It would be very important to come up with a replacement that is as effective as what we're trying to replace. Frankly, I don't know a single candidate. Does anyone? Here are some, can’t say they carry the same level of clarity or weight. excellence, merit-based / merited, self-determination, deserving / deservingness, worthiness / being worthy of, getting one's due, be entitled / qualified to I suspect, without research data to back it up, that anything that implies that those with decision making power got there primarily through their own merit/deserts/worth etc. would have the same harmful effects as a claim to be a meritocracy. I prefer the direction that presents meritocracy as something towards which we can strive, but that has not been achieved and may never be fully achieved. Luck and having the right parents will go on being important. Patricia --- This email has been checked for viruses by AVG. https://www.avg.com - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
> On Mar 22, 2019, at 2:03 AM, Roman Shaposhnik wrote: > > It would be very important to come up with a replacement that is > as effective as what we're trying to replace. Frankly, I don't know > a single candidate. > > Does anyone? Here are some, can’t say they carry the same level of clarity or weight. excellence, merit-based / merited, self-determination, deserving / deservingness, worthiness / being worthy of, getting one's due, be entitled / qualified to —Shawn - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: on "meritocracy"
FYI, as you may have seen, I've made the following change in a couple of places. I think it only goes part-way to solving the problem, but it replaces "is" with "strives to be" in every place on community.apache.org where this term occurs. We can, of course, do more, but I didn't want to be random with it. I'd like to come to an agreement as to what change, exactly, we wish to make. This also ties in to the recent blog post - https://blogs.apache.org/foundation/entry/the-apache-way-to-sustainable - which, as you may note, doesn't use the term even once. Anyways, I think we can, and should, start looking through the list of 150 on www.apache.org and seeing what changes should be made there. [rbowen@sasha:content/apache-way]$ svn diff (03-21 14:27) Index: apache-project-maturity-model.mdtext === --- apache-project-maturity-model.mdtext(revision 1856006) +++ apache-project-maturity-model.mdtext(working copy) @@ -179,7 +179,7 @@ CO40 -The community is meritocratic and over time aims to give more rights and +The community strives to be meritocratic and over time aims to give more rights and responsibilities to contributors who add value to the project. On 3/21/19 2:26 PM, Rich Bowen wrote: > A few more hits on 'meritoc' since we use "meritocratic" some places. > > > On 3/21/19 1:53 PM, Rich Bowen wrote: >> FWIW: >> >> [rbowen@sasha:comdev/site]$ grep -ri meritocracy | wc -l >> 4 >> >> So, that one's easy ... >> >> >> [rbowen@sasha:apache/www-site]$ grep -ri meritocracy ./ | wc -l >> 150 >> >> Somewhat more challenging, and would require considerable cooperation >> from Sally to ensure that we are in line with approved messaging. > -- 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
[jira] [Commented] (COMDEV-307) GSoC - Allura - responsive web pages
[ https://issues.apache.org/jira/browse/COMDEV-307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16799011#comment-16799011 ] Dilshan Dilip commented on COMDEV-307: -- Hello Dave, My name is Dilshan Dilip Udara, Second year undergraduate at university of Jaffna, Srilanka. I would like to do this project as GSoc 2019.Please help me to proceed. My GitHub Link is [https://github.com/DilshanDilipudara] > GSoC - Allura - responsive web pages > > > Key: COMDEV-307 > URL: https://issues.apache.org/jira/browse/COMDEV-307 > Project: Community Development > Issue Type: Improvement > Components: GSoC/Mentoring ideas >Reporter: Dave Brondsema >Priority: Major > Labels: css, gsoc2019, html, javascript, sass, ux > > Allura's web frontend should be responsive. Initial prototyping work has > begun using the Foundation framework: > [https://foundation.zurb.com/sites/docs/] More initial work needs to be done > to develop a reliable pattern, and then convert existing templates to use > Foundation HTML markup and CSS (SCSS, actually) to layout the pages in an > intuitive way for all screen sizes. Interactivity via JS may need to be > updated as well. Some more details are here > [https://lists.apache.org/thread.html/f441cef1d288410be5b6c6fc521d62d350ba92df5b4c0e84ea734d5d@%3Cdev.allura.apache.org%3E] > https://allura.apache.org/ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - 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 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
Re: Google Season of Docs 2019
Hi Aizhamal Thanks very much for the offer of help. I'll put something together and perhaps you can help me with a review. Thanks Sharan On 2019/03/19 18:11:02, 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
Help with task: Ensure all Apache TLPs have Wikipedia pages
I would like to help out with the task listed at /task.html?0b349bee
Re: Google Season of Docs 2019
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
Re: on "meritocracy"
On Thu, Mar 21, 2019 at 10:53 AM Rich Bowen wrote: > On 3/21/19 1:15 PM, Naomi Slater wrote: > > > > I feel like this is a good opportunity to bring up (as I have brought up > > before) the fact that "meritocracy" was invented for the purposes of a > > satirical *dystopian* novel. > > Well, maybe. I kind of find that entire line of conversation to be just > an amusing sidebar, and not really relevant. But, then, this is a > favorite topic of debate with my linguist brother - the descriptive vs > prescriptive nature of definitions. :) > > Word origins are just that - origins. What matters is the current > meaning, not where they originated. You can play that kind of game with > lots of English words, many of which have absurd origin stories. > > I have a similar reaction to people who try to justify current > political policies by referencing the historical origin of their > opponent's political party. > > What's relevant is now. > > Many, many words that we rely on daily have contradictory origin > stories. "Awful" and "Terrible" are instructive examples. > > > I *think* that on this particular mailing list, you're preaching to the > > choir. And that choir is notably much more diverse than the ASF at > > large. The challenge is spreading this story to the larger congregation. > > Particularly when certain vocal members of that congregation speak very > > loudly against those efforts as being wasteful of time and volunteer > > effort. > > > > > > but in your first email, re people getting offended, you said: > > > > "I understand that these people exist, but citing them as representative > > seems weird." > > Specifically, there, I'm talking about Stuart Varney, who is a nasty, > horrible person, and isn't representative of anyone here at the > Foundation, even the most horrible nasty person here. > > Crafting our message for the small number of horrible people seems less > effective than crafting it for the large number of > well-intentioned-but-passive people, well-intentioned-but-unaware > people, and well-intentioned-but-unaffected-due-to-their-privilege people. > > I firmly believe that most of the people here at the Foundation > genuinely want to do the right thing. That we haven't done the right > thing is not, for the most part, due to a malicious intention to do the > wrong thing. I try, really hard, to assume good intent when crafting > messages. If we assume everyone is Stuart Varney, we'll end up with > messaging that will offend everyone and inform nobody. > > > my experience attempting to bring this sort of thing "to the > > congregation" (i.e., members@) in the past is *the primary reason* I > > burnt out and took hiatus for as long as I did. it was extremely > > exhausting. being challenged by multiple people on every little point. > > being drawn into long, circular, unproductive, and hostile arguments. > > having to manage other people's emotions/outrage/flames > > > > traumatizing too, to be honest > > > > it is ironic (and bitterly unfair) that this sort of work often has to > > be done by the people who have a material stake in what is being > > dismissed and who are already exhausted/traumatized from all the times > > they've had these sorts of conflicts before > > Yes, agreed. Also ironic is how some of us who desperately want to help > are often unable to do so, because, as a white, middle aged, bearded, > financially successful man, I'm a large part of the problem, and so my > voice doesn't carry nearly the weight of yours. > > > I don't know what to do, to be honest. I don't have the emotional or > > psychological health required to butt heads on members@ anymore > > I am willing to take on that fight, whenever and however I can. I often > feel that I'm trying to mop up the sea with a paper towel. And these > discussions in Apache-land are pretty consistently LESS hostile than in > other communities I'm part of. > > > perhaps a good first step would be to update the material the ComDev > > project is responsible for? phase out the word "meritocracy" (and maybe > > add a note that acknowledges this change and gives a rationale). reframe > > our values and approach as per my last email. from there, we could move > > on to http://theapacheway.com/ (if Shane is up for it) and then the > > Apache website proper, Incubator, etc. let it percolate through > > +1 to phasing out the word. -0 to providing a rationale for doing so, as > it would seem to be a distraction, and picking a fight. Rather, finding > the right/best phrasing, and moving to it, without necessarily drawing > attention to the change, seems like a way to avoid pointless pushback > from our Usual Suspects that tend to poop on any attempt to balance our > community diversity. > > FWIW: > > [rbowen@sasha:comdev/site]$ grep -ri meritocracy | wc -l > 4 > > So, that one's easy ... > > > [rbowen@sasha:apache/www-site]$ grep -ri meritocracy ./ | wc -l > 150 > > Somewhat more challenging, and would
