Re: Feathercast scheduling
Dear Com.Devs, I would be happy to say a couple of words about Apache Ignite. I've requested permissions to add myself to the list. Thank you. Sincerely, Dmitriy Pavlov ср, 1 апр. 2020 г. в 19:49, Rich Bowen : > I should clarify - I'll do a second scheduling once I've cleared the queue. > There will be other opportunities. > > Shosholoza, > Rich > > > On Wed, Apr 1, 2020, 12:03 Rich Bowen wrote: > > > I'm not sure who Gian is, who wishes to speak for Druid. Thanks for your > > willingness. However, the times listed in that document are the only > > times that I have available. Please don't add extra times to the list, > > since I won't be available then. > > > > Thanks. > > --Rich > > > > On 3/31/20 12:51 PM, Rich Bowen wrote: > > > Hi, friends, > > > > > > I'm hoping to reboot Feathercast (yeah, I know, I've said this before) > > > next week, around the original theme of "Yeah, but what does it *DO*?" > > > that we used to do in the old days. > > > > > > To that end, I have a list of all of the projects (as of today, > > > anyways!) here: > > > > > > https://docs.google.com/spreadsheets/d/1jXP89WzTDiOS2QaSeKGyz6M_z71HI0lYOzVFnnZ-EAo/edit?usp=sharing > > > > > > > > > And I have a boilerplate script, here: > > > > > > https://docs.google.com/document/d/1FZzloEiCf2qxm9Q4Ipq6i-2mkykdKfvuNaqOpRf901w/edit?usp=sharing > > > > > > > > > What I'd like, short term, is a couple of "friendly" projects that I > can > > > get started with. Perhaps people who are excited about their project, > > > are used to being interviews, and can get us off on a good start. > > > > > > If you are interested in volunteering for this, please let me know, and > > > we'll schedule something. > > > > > > Thanks! > > > > > > > -- > > Rich Bowen - rbo...@rcbowen.com > > http://rcbowen.com/ > > @rbowen > > >
Re: Please add Apache Ignite Logo to RedBubble
Hi, Thank you, Mark! I'll order something since it looks very nice. Sincerely, Dmitriy Pavlov пт, 16 авг. 2019 г. в 19:32, Mark Thomas : > On 14/08/2019 17:06, Dmitriy Pavlov wrote: > > Hi Mark, > > > > would it be a good idea to reuse #LoveApache version of Apache Ignite > > sticker > > > > http://www.apache.org/logos/loveapache/ignite.png > > > > and make it available for order at RedBubble? > > > https://www.redbubble.com/people/comdev/works/40623105-apache-ignite-love-apache?asc=u > > Enjoy (I particularly like the clock). > > Mark > > > > > > Sincerely, > > Dmitriy Pavlov > > > > вс, 11 авг. 2019 г. в 01:12, Dmitriy Pavlov : > > > >> Hi Mark, Thank you! > >> > >> сб, 10 авг. 2019 г. в 23:43, Mark Thomas : > >> > >>> On 08/08/2019 22:33, Dmitriy Pavlov wrote: > >>>> Dear Community Developers, > >>>> > >>>> Could you please add Apache Ignite Logo to RedBubble? > >>>> > >>>> Logo http://apache.org/logos/#ignite > >>> > >>> > https://www.redbubble.com/people/comdev/works/40515447-apache-ignite?asc=u > >>> > >>> Mark > >>> > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
ASF slack for Apache Ignite - non English communication
Dear Community Developers, Please share your vision about the following idea: Russian Native speakers from the Apache Ignite community will create an additional Slack channel #ignite-ru and will communicate using Russian there. A number of committers are Russian and not all of them are fluent in English. I would make everything possible to keep our principle working: 'If it didn't happen on a list it didn't happen', but since contributors work for different companies, we need to use different messengers (skype, slack, Rocket, Telegram, WhatsApp). And the language barrier is also a problem for some folks to express some of their ideas. I have an idea to move some peer-2-peer messaging to ASF slack channel ignite-ru and make it simpler to connect outside the list without the necessity to translate to English, and replace private communication with the channel for everyone. What do you think? Sincerely, Dmitriy Pavlov
Re: Please add Apache Ignite Logo to RedBubble
Hi Mark, would it be a good idea to reuse #LoveApache version of Apache Ignite sticker http://www.apache.org/logos/loveapache/ignite.png and make it available for order at RedBubble? Sincerely, Dmitriy Pavlov вс, 11 авг. 2019 г. в 01:12, Dmitriy Pavlov : > Hi Mark, Thank you! > > сб, 10 авг. 2019 г. в 23:43, Mark Thomas : > >> On 08/08/2019 22:33, Dmitriy Pavlov wrote: >> > Dear Community Developers, >> > >> > Could you please add Apache Ignite Logo to RedBubble? >> > >> > Logo http://apache.org/logos/#ignite >> >> https://www.redbubble.com/people/comdev/works/40515447-apache-ignite?asc=u >> >> Mark >> >
Re: #LoveApache Project Stickers
Hi Sharan, I like an auto-generated version of a sticker for Apache Ignite, could you please add it to the order? http://www.apache.org/logos/loveapache/ignite.png Sincerely, Dmitriy Pavlov ср, 14 авг. 2019 г. в 17:27, Adina Crainiceanu : > Hi Sharan,. > Could we add Daniel's version of #LoveApache for Rya to the order? > http://www.apache.org/logos/loveapache/rya.png > > Thanks, > Adina > > On Tue, Aug 13, 2019 at 5:02 PM Aizhamal Nurmamat kyzy > wrote: > > > Hey Sharan, > > > > Could we use Daniel's version of the logo for Airflow stickers > > http://www.apache.org/logos/loveapache/airflow.png? The one I shared > > is pixelated, Daniel's is much better. Sorry for causing so many > troubles.. > > :( > > > > On Tue, Aug 13, 2019 at 1:49 PM Sharan Foga wrote: > > > > > Hi Aizhamal > > > > > > Yes, those work. I have added them to the order. > > > > > > Thanks > > > Sharan > > > > > > On 2019/08/13 20:42:11, Aizhamal Nurmamat kyzy > > > > > wrote: > > > > Ah, not attachments are allowed. How about this > > > > > > > > > > https://drive.google.com/drive/folders/1r7aw8eKmbkBo41IE_PR_--MB-U6bwW8L?usp=sharing > > > > ? > > > > > > > > > > > > > > > > > > > > On Tue, Aug 13, 2019 at 1:34 PM Aizhamal Nurmamat kyzy < > > > aizha...@google.com> > > > > wrote: > > > > > > > > > Hi Sharan, > > > > > > > > > > How about these graphics for #LoveApache stickers? LMK if they work > > :) > > > > > > > > > > > > > > > On Tue, Aug 13, 2019 at 1:19 PM Daniel Gruno > > > > wrote: > > > > > > > > > >> On 8/13/19 10:15 PM, Sharan Foga wrote: > > > > >> > Hi Daniel > > > > >> > > > > > >> > Absolutely brilliant! I can pick up the beam and airflow ones > > that I > > > > >> need from there. > > > > >> > > > > >> Airflow's logo has some serious padding on it that poses a > problem. > > > > >> Those should ideally be cut form the original svg first.. > > > > >> > > > > >> > > > > > >> > Anyone else that wants them then please let me know. > > > > >> > > > > > >> > Thanks > > > > >> > Sharan > > > > >> > > > > > >> > On 2019/08/13 20:02:24, Daniel Gruno > > wrote: > > > > >> >> On 8/13/19 9:45 PM, Sharan Foga wrote: > > > > >> >>> Hi All > > > > >> >>> > > > > >> >>> If you would like some #LoveApache versions of your project > > > stickers > > > > >> available at the ASF booth for Apachecon then please make sure > that > > > you > > > > >> create the graphic based on the instructions below > > > > >> >>> > > > > >> >>> https://www.apache.org/foundation/press/kit/#loveapache > > > > >> >>> > > > > >> >>> and then send me the graphic so I can use it for the sticker > > > order. > > > > >> >> > > > > >> >> There's an auto-generator that runs and spits out images at: > > > > >> >> http://www.apache.org/logos/loveapache/ > > > > >> >> > > > > >> >> it uses the same defaults as the Powered-By generator, that > > is...if > > > > >> >> there is an original called $project-pb.svg, it will use that > > one, > > > > >> >> otherwise it will find the most round/square logo and use that. > > > > >> >> > > > > >> >> it's currently running round one, images slowly coming up... > > > > >> >> they're not the best fit for all projects, but it works for > some > > :) > > > > >> >> > > > > >> >>> > > > > >> >>> Thanks > > > > >> >>> Sharan > > > > >> >>> > > > > >> >>> > > > - > > > > >> >>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > >> >>> For additional commands, e-mail: > dev-h...@community.apache.org > > > > >> >>> > > > > >> >> > > > > >> >> > > > > >> >> > > > - > > > > >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > >> >> For additional commands, e-mail: dev-h...@community.apache.org > > > > >> >> > > > > >> >> > > > > >> > > > > > >> > > > > - > > > > >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > >> > For additional commands, e-mail: dev-h...@community.apache.org > > > > >> > > > > > >> > > > > >> > > > > >> > > - > > > > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > >> For additional commands, e-mail: dev-h...@community.apache.org > > > > >> > > > > >> > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > -- > Dr. Adina Crainiceanu > Associate Professor > Computer Science Department > United States Naval Academy > 410-293-6822 > ad...@usna.edu > http://www.usna.edu/Users/cs/adina/ >
Re: REMINDER: Project Stickers for Apachecon NA or EU
Hi Sharan, Can I ask you to include Apache Ignite stickers to the order? http://apache.org/logos/#ignite Talks related to Apache Ignite will be both at Apache Con NA (Denis Magda) and Apache Con EU (Alexey Zinoviev). Also, I participate in Apache Training (incubating) http://apache.org/logos/?#training This polding related talks will be held at least at Apache Con EU. So could you please add it, as well? Should I start 2 separate threads at Com.Dev list? Or is it enough to reply in this email? Sincerely, Dmitriy Pavlov вт, 13 авг. 2019 г. в 20:12, Sharan Foga : > Hi All > > We still have a little time to put together a second order for stickers > for the ASF booth for Las Vegas and Berlin. I already have a couple of > projects on the second order so if you would like us to have some of your > project stickers too then please let me know and I will include it. > > This includes incubating projects too so if you have never seen or had any > stickers available for your project then this is the time to request some! > > Thanks > Sharan > > On 2019/08/07 19:51:25, Sharan Foga wrote: > > Hi Everyone > > > > This is a reminder that I am putting the main sticker order together now > with the plan to get the order in progress by the weekend. So if you are > coming to Apachecon NA or EU and would like to see some of your project > stickers there then please let me know. And remember this covers podlings > too. > > > > Please check to see if your project is already on the Sticker list at > > https://cwiki.apache.org/confluence/display/COMDEV/ApacheCon+NA+2019 > > > > and if not, then please either add it to the list on the wiki or respond > to this thread with the name of your project and I will add it. > > > > Thanks > > Sharan > > > > - > > 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: Please add Apache Ignite Logo to RedBubble
Hi Mark, Thank you! сб, 10 авг. 2019 г. в 23:43, Mark Thomas : > On 08/08/2019 22:33, Dmitriy Pavlov wrote: > > Dear Community Developers, > > > > Could you please add Apache Ignite Logo to RedBubble? > > > > Logo http://apache.org/logos/#ignite > > https://www.redbubble.com/people/comdev/works/40515447-apache-ignite?asc=u > > Mark >
Please add Apache Ignite Logo to RedBubble
Dear Community Developers, Could you please add Apache Ignite Logo to RedBubble? Logo http://apache.org/logos/#ignite Sincerely, Dmitriy Pavlov
[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=16903343#comment-16903343 ] Dmitriy Pavlov commented on COMDEV-315: --- [~sebb], yes, and discussion was stopped since marketing was going to update statistics first. I'm not sure issue can be completed now. > Fix Russian translation for Apache Brochure > --- > > Key: COMDEV-315 > URL: https://issues.apache.org/jira/browse/COMDEV-315 > Project: Community Development > Issue Type: Bug > Components: Comdev > 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.14#76016) - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: Focused effort on Apache Way education
> For the purposes of *THIS* discussion, I think that that's a bit of a sidetrack. Sure. Jim, Despite the fact that I do not fully understand the problem, I am ready to volunteer to prepare materials. I don't care if it will be a part of Apache Training or Apache Com.Dev or slightly another thing. I just like this topic, which why a year ago I've started asking about it here. I know about the excellent slides done by Shane http://shaneslides.com/apachecon/TheApacheWay-ApacheConNA2018.html#2 I also like the idea of explaining not only principles but all principles' impact. Ideal material for education would explain why ASF can't drop each component of the Apache Way. Sincerely, Dmitriy Pavlov вт, 16 июл. 2019 г. в 22:46, Rich Bowen : > > > On 7/16/19 2:29 PM, Dmitriy Pavlov wrote: > > Hi Jim, > > > > Could you mention events you're referring to? > > For the purposes of *THIS* discussion, I think that that's a bit of a > sidetrack. > > Suffice it to say that clearer understanding of the *WHY* around the > principles of the Apache Way is necessary, in order that the *WHAT* > doesn't get perceived as meaningless, arbitrary, or dispensible. > > > > > > In Apache Training (incubating) Justin started to develop content related > > to the Incubator > > > https://github.com/apache/incubator-training/tree/master/content/ApacheWay > , > > so we can consider developing a standalone session related to the Apache > > Way principles. But to understand if training will be helpful I would > like > > to know the entire story. > > > > You can share it with me directly if you want. > > > > Sincerely > > Dmitriy Pavlov > > > > вт, 16 июл. 2019 г. в 20:52, Jim Jagielski : > > > >> I think that the events of the last several months have clearly shown a > >> lack of awareness, knowledge and (and some level) appreciation > (adherence) > >> to The Apache Way. It would be useful, I think, if this was a focused > >> effort w/i the foundation. > >> > >> Of course, there is a lot of overlap between ComDev and this effort, and > >> so the questions are how best to address this. Maybe some sort of > sub-cmmt > >> under ComDev? Or spinning this out ala D (but as a PMC to avoid the > >> problems that cmmt encountered and to engender trust and > collaboration)? Or > >> basically focus on it w/i ComDev with the structure "as is"... I think > >> having one person "tasked" with herding the cats and coordinating the > >> effort would be useful (and I volunteer to do so), no matter what > structure > >> we decide. > >> > >> Thoughts? Ideas? > >> - > >> 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: Focused effort on Apache Way education
Hi Jim, Could you mention events you're referring to? In Apache Training (incubating) Justin started to develop content related to the Incubator https://github.com/apache/incubator-training/tree/master/content/ApacheWay , so we can consider developing a standalone session related to the Apache Way principles. But to understand if training will be helpful I would like to know the entire story. You can share it with me directly if you want. Sincerely Dmitriy Pavlov вт, 16 июл. 2019 г. в 20:52, Jim Jagielski : > I think that the events of the last several months have clearly shown a > lack of awareness, knowledge and (and some level) appreciation (adherence) > to The Apache Way. It would be useful, I think, if this was a focused > effort w/i the foundation. > > Of course, there is a lot of overlap between ComDev and this effort, and > so the questions are how best to address this. Maybe some sort of sub-cmmt > under ComDev? Or spinning this out ala D (but as a PMC to avoid the > problems that cmmt encountered and to engender trust and collaboration)? Or > basically focus on it w/i ComDev with the structure "as is"... I think > having one person "tasked" with herding the cats and coordinating the > effort would be useful (and I volunteer to do so), no matter what structure > we decide. > > Thoughts? Ideas? > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: [Proposal] Apache Local Community - meetups
Hi Shane, This list looks outdated. README about how to update the list gives 404. Can any Apache Project committer update it? If so, I could update this page from time to time: - Once I've shared Apache Ignite meetup link - and I saw one request to update this list at com.dev list recently. Sincerely, Dmitriy Pavlov сб, 29 июн. 2019 г. в 20:33, Swapnil M Mane : > Awesome, thanks so much Shane for sharing this information. > > Best Regards, > Swapnil M Mane > > > > On Sat, Jun 29, 2019 at 7:36 PM Shane Curcuru > wrote: > > > Peter Hunsberger wrote on 2019-6-27 8:51AM EDT: > > > Around here we get a lot of local development focused groups on > > > Meetup.com... > > > > Note that the ASF's VP of Conferences has a page that will list Meetups > > and similar events that are run by Apache projects: > > > > https://events.apache.org/event/meetups.html > > > > That's another great way to help other people find out about any local > > Apache project meetings/talks that you organize. Note that Rich (VP > > Conferences) also travels to many conferences, so please be patient when > > asking for updates to that page (or, help volunteer on maintenance!) > > > > -- > > > > - Shane > > Documenter Of Useful Things > > The Apache Software Foundation > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >
Re: [Proposal] Apache Local Community - how to list yourself
Hi All, I appreciate this action started. My experience related to FOAF files: I didn't know about local mentors and FOAF until I visited community development web site. I've tried to add, but that time it didn't work, so I gave up. +1 for asking people at Apache Con and +1 for sending some announce to committers@ to remind people about existence. I definitely going to try one more time. In my local area (Russia, Saint-Petersburg, and Moscow) I guess we don't have too many committers, so I'm not absolutely sure that monthly meetups could be possible. FOAF for Saint-Petersburg shows 2 committers. Time to time I speak about How Open Source works and about The Apache Way in local meetups and conferences, for example here we have ~ 900 people: https://www.meetup.com/Moscow-Apache-Ignite-Meetup/ But usually, only 30-60 came in person to meet up (users+committers+PMC). I saw other meetups related to Apache Cassandra. I definitely would be happy to come to Apache related event and could help to organize some in Russia. Sincerely, Dmitriy Pavlov чт, 27 июн. 2019 г. в 17:16, Swapnil M Mane : > Glad to hear from you Shane, thanks so much for your comments :) > > I also feel the same, we need some more publicity for this. > We can share these details on committ...@apache.org list (so in case if > any > committer is unaware of it, they will get to know). > > Apart from this, I also feel we can smooth the process of registering in > Committers map, here are some initial thoughts. I am not sure about the > feasibility of these items for us. > > -- At the time of onboarding new committer in ASF, we can ask do they want > to register themselves in committer map, if yes, we can get required > details (lat/long, etc) from them and generate and commit FOAF file by > ourselves. So no action will be required by the Committer. > > -- The current process involved two steps > 1. Create a FOAF file [1]. > 2. Commit the FOAF file to committers SVN repo. > Can we simplify this process, we can create a simple form with details like > the first name, last name, lat/long, etc (all the details we asked in the > form available here [1]). > As the Committer submit this form, automatically behind the scene FOAF file > will be created and committed to SVN repo. > We can make sure this form is accessible to only committers. > > [1] https://home.apache.org/foaf/foafamatic.html > > Best Regards, > Swapnil M Mane > > > On Thu, Jun 27, 2019 at 6:20 PM Shane Curcuru > wrote: > > > Great ideas all! > > > > Swapnil M Mane wrote on 2019-6-27 8:34AM EDT: > > ...snip... > > > The nearby Apache people can be found here [1], and Apache Committers > map > > > [2] can also help, but I think, it is not up to date. > > > > > > Hope these details will help you, I am excited to work together :) > > > > > > [1] http://community.zones.apache.org/ > > > [2] http://community.zones.apache.org/map.html > > > > The Committers map definitely works, however it relies on individual > > committers voluntarily listing a location for themselves - the ASF does > > not otherwise give out private data about committers. It also hasn't > > been well-publicised recently, so I think a lot of committers don't even > > know about it. Ideas on 1) how to improve it and 2) how to get other > > committers in your project(s) to think about listing themselves are > > appreciated. > > > > To list yourself on the map, put a location in a FOAF file and point to > > it from the committers SVN repo: > > > > https://home.apache.org/foaf/index.html > > > > If anyone has improvements to the ComDev website or the Phone > > Book/home.apache.org, you can see the website sources to patch: > > > > http://community.apache.org/about/#about-this-website > > > > -- > > > > - Shane > > ComDev PMC > > The Apache Software Foundation > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > >
Re: help with Wikipedia task
Hi Trevor, I've added permission to edit. Please check. Sincerely Dmitriy Pavlov ср, 5 июн. 2019 г. в 00:07, Trevor Grant : > I don't have write permissions on that doc, but the mahout description is > painfully out of date as well. > > > On Tue, Jun 4, 2019 at 2:52 PM Dmitriy Pavlov wrote: > > > Hi Bob, > > > > You can contribute any page/update to the page from following Google doc: > > > > > https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit#gid=0 > > > > For projects with row/cell is a red means page does not exist or needed > > information is missing. > > > > Also, it may be a good idea to contact project PMCs/Dev.list if the > project > > does not have a Wikipedia page. In case we start a discussion about page > > contribution with PMC we can add a link to list thread to this document > (to > > avoid duplicated discussions). > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 4 июн. 2019 г. в 20:51, Bob Marley : > > > > > I missed this response when it arrived into the inbox. I am genuinely > > > interested in helping here if you are interested:) > > > > > > Thanks > > > Marcin > > > > > > Ps. It's easier to use that as a nickname but I can see that it can be > > > confusing hah :) > > > > > > > > > On Thu, 18 Apr 2019, 14:57 Rich Bowen, wrote: > > > > > > > Bob Marley? Really? > > > > > > > > I'm increasingly coming to believe that everything coming through on > > the > > > > "help wanted" thing is spam, and it may be time to shut it down. > > > > Discouraging, given our high hopes going in. > > > > > > > > On 4/16/19 3:49 PM, Bob Marley wrote: > > > > > Hi, > > > > > > > > > > I could help with the task: > > > > > > > > > > > > > > > > > > > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > > > > Task #0b349bee: Ensure all Apache TLPs have Wikipedia pages > > > > > > > > > > What would be the first step? > > > > > > > > > > Thanks! > > > > > > > > > > > > > -- > > > > Rich Bowen - rbo...@rcbowen.com > > > > http://rcbowen.com/ > > > > @rbowen > > > > > > > > > >
Re: help with Wikipedia task
Hi Bob, You can contribute any page/update to the page from following Google doc: https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit#gid=0 For projects with row/cell is a red means page does not exist or needed information is missing. Also, it may be a good idea to contact project PMCs/Dev.list if the project does not have a Wikipedia page. In case we start a discussion about page contribution with PMC we can add a link to list thread to this document (to avoid duplicated discussions). Sincerely, Dmitriy Pavlov вт, 4 июн. 2019 г. в 20:51, Bob Marley : > I missed this response when it arrived into the inbox. I am genuinely > interested in helping here if you are interested:) > > Thanks > Marcin > > Ps. It's easier to use that as a nickname but I can see that it can be > confusing hah :) > > > On Thu, 18 Apr 2019, 14:57 Rich Bowen, wrote: > > > Bob Marley? Really? > > > > I'm increasingly coming to believe that everything coming through on the > > "help wanted" thing is spam, and it may be time to shut it down. > > Discouraging, given our high hopes going in. > > > > On 4/16/19 3:49 PM, Bob Marley wrote: > > > Hi, > > > > > > I could help with the task: > > > > > > > > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > > Task #0b349bee: Ensure all Apache TLPs have Wikipedia pages > > > > > > What would be the first step? > > > > > > Thanks! > > > > > > > -- > > Rich Bowen - rbo...@rcbowen.com > > http://rcbowen.com/ > > @rbowen > > >
Russia, Saint-Petersburg, Apache Ignite Meetup
Hi Community Developers, In St. Petersburg, Apache Ignite meetup to be held soon: https://www.meetup.com/St-Petersburg-Apache-Ignite-Meetup/events/262004665/ GridGain (commercial company) organizes this meetup. However, for the first time, none of the speakers are GridGain employees. I believe this case is special because it is a step towards a healthy/diverse community around the project. Could you please share information about the event in the social media networks/share with your colleagues? Sincerely, Dmitriy Pavlov
Re: Any chance we can update HelpWanted?
Hi Sally, According to feedback from folks here, we can't edit existing tasks, but any Apache committer can mark any task as done and create a new one. I'm aware of only one task from Com.Dev project - it is an update of Wikipedia pages. Sincerely, Dmitriy Pavlov пт, 26 апр. 2019 г. в 06:13, Sally Khudairi : > Hello ComDev-ers! I hope everyone is doing well. > > I was preparing a promotion for HelpWanted https://helpwanted.apache.org/ > but noticed that some of the entries are rather old, dating back to > February 2016. > > Is there any way this page can be updated a bit more regularly? > > If this is a worthwhile/used service, I'll see if we can also make it look > a little more "current" as well. > > Kind thanks in advance, > Sally > > - - - > Vice President Marketing & Publicity > Vice President Sponsor Relations > The Apache Software Foundation > > Tel +1 617 921 8656 | s...@apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
Hi Pierre, Thank you for bringing here this idea. >From the one side, anybody can grant access if he/she has to write access. If you could help to collect this information, you can share Google login and I will add. >From the other side, not all of us can have google accounts, so it may be reasonable to keep it editable/suggestable. For now, I've added comment permission for everyone who has a link. If we agree to set write permissions, I can change to write. Sincerely, Dmitriy Pavlov чт, 25 апр. 2019 г. в 16:23, Pierre Smits : > Hi Swapnil, > > The google doc is read-only by default. If you want to have it updated > fast and frequently by various parties, you may consider opening it up more > (write access to all/anybody). Otherwise we keep having this chicken-egg > situation. > > Best regards, > > Pierre Smits > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) > since 2008* > Apache Steve <https://steve.apache.org>, committer > > > On Wed, Apr 24, 2019 at 8:11 AM Swapnil M Mane > wrote: > > > Hi Corey, > > > > Thank you for your interest in the help task. > > Please follow these steps to help us in this task. > > > > We have created a Google sheet [1] (edit access to are provided you) > > containing the list of all Apache's top level projects. > > Please check, is the Wikipedia page exist for that particular project, if > > yes put the link of page else put the appropriate comment and mark row as > > red. > > > > Some things to remember: > > 1.) The sheet also contain Attic and Incubating projects, please ignore > > them. Our focus is Apache's top level projects. > > 2.) Some projects that are managed by the same PMC, e.g. Apache Anakia > does > > not have a separate page, > > but it is mentioned in https://en.wikipedia.org/wiki/Apache_Velocity. So > > for these cases, same Wikipedia page will be used. > > > > If you any queries, please free to contact Dmitriy (dpav...@apache.org) > or > > me (swapnilmm...@apache.org). > > > > [1] > > > > > https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit?usp=sharing > > > > - Thanks & Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Mon, Apr 22, 2019 at 7:13 PM Corey Duvall-kenyon < > > dufflebagriche...@gmail.com> wrote: > > > > > I would like to help out with the task listed at /task.html?0b349bee > > > > > >
Re: Blog Post 'How To Become Committer' - feedback needed
Sorry for 2nd email, By re-post, I meant not a citation of this blog, but re-use of the text of the blog. Of course, we can remove mentioning of employment. If it is possible to whom I could contact to prepare a post? ср, 24 апр. 2019 г. в 11:28, Dmitriy Pavlov : > Hi Community Developers, > > Recently we've translated a blog post based on my recent talk on Apache > Ignite meetup/Moscow: > > https://www.gridgain.com/resources/blog/how-become-open-source-committer-and-why-youd-want > > > I would appreciate if someone from more experienced Apache fellows can > provide some comments to this post (actually, this one is based on previous > feedback from Shane C.). > > Would it be possible to re-post this blog in 'success at Apache' series? > > Sincerely, > Dmitriy Pavlov > > > > >
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
I'm going to, but I can't promise the exact date. It is in my todo-list ср, 24 апр. 2019 г. в 12:56, Rich Bowen : > At the risk of being overly bureaucratic, who is going to do this? Cause if > "someone should" chances are no-one will. > > On Wed, Apr 24, 2019, 12:35 AM Swapnil M Mane > wrote: > > > +1 Rich and Dmitriy > > > > > > - Best Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Wed, Apr 24, 2019 at 3:07 AM Dmitriy Pavlov > wrote: > > > > > +1, I agree we can remove this too generic ticket because possible > > > contributor may not know what exactly needs to be done. > > > > > > I'd better create a couple of specific tasks to be done for > > > contributing/updating a particular project description. > > > > > > вт, 23 апр. 2019 г. в 17:58, Rich Bowen : > > > > > > > There is not currently a way to edit these HelpWanted tickets. > Perhaps > > > > since the project is well underway, we could just delete the ticket? > > > > > > > > On 4/23/19 7:49 AM, Swapnil M Mane wrote: > > > > > Nice, thanks Dmitriy. > > > > > > > > > > On Tue, Apr 23, 2019 at 4:37 PM Dmitriy Pavlov > > > > > wrote: > > > > > > > > > >> It works fine, thanks, > > > > >> > > > > >> I've started to fill this doc. For now, I will skip projects that > > are > > > > >> managed by the same PMC. E.g. Apache Anakia does not have a > separate > > > > page, > > > > >> but it is mentioned in > > https://en.wikipedia.org/wiki/Apache_Velocity > > > > >> > > > > >> > > > > > +1 > > > > > > > > > > > > > > >> I will also skip attic and incubator projects. Unfortunately, I > can > > > not > > > > >> > > > > > > > > > > +1 > > > > > > > > > > > > > > >> edit this ticket so we need somehow share this list of project & > > > > wikipedia > > > > >> page correspondence sheet. > > > > >> > > > > >> > > > > > Agree, we should find way to add this sheet information in the > > ticket. > > > > > May be we can take help from Nick (creator of the ticket) or infra. > > > > > > > > > > > > > > >> Sincerely, > > > > >> Dmitriy Pavlov > > > > >> > > > > >> вт, 23 апр. 2019 г. в 10:39, Swapnil M Mane < > > swapnilmm...@apache.org > > > >: > > > > >> > > > > >>> Great Dmitriy, thoughts travels :-) > > > > >>> I have granted you the access, kindly check. > > > > >>> > > > > >>> > > > > >>> - Best Regards, > > > > >>> Swapnil M Mane, > > > > >>> ofbiz.apache.org > > > > >>> > > > > >>> > > > > >>> > > > > >>> On Tue, Apr 23, 2019 at 1:01 PM Dmitriy Pavlov < > dpav...@apache.org > > > > > > > >> wrote: > > > > >>> > > > > >>>> Hi Swapnil M Mane, > > > > >>>> > > > > >>>> I was thinking about absolutely the same approach. I've > requested > > > edit > > > > >>>> access, could you please grant it? > > > > >>>> > > > > >>>> Sincerely, > > > > >>>> Dmitriy Pavlov > > > > >>>> > > > > >>>> вт, 23 апр. 2019 г. в 09:08, Swapnil M Mane < > > > swapnilmm...@apache.org > > > > >: > > > > >>>> > > > > >>>>> Hello Rich and team, > > > > >>>>> > > > > >>>>> As we see, various people are willing to help for this task of > > > > >> ensuring > > > > >>>> all > > > > >>>>> Apache TLPs have Wikipedia pages [1]. > > > > >>>>> I see, some of the TLPs are having there Wikipedia page in > draft > > > > >> status > > > > >>>>> (might be some projects don't even have the page). > > > > >>>>> So, here the approach
Blog Post 'How To Become Committer' - feedback needed
Hi Community Developers, Recently we've translated a blog post based on my recent talk on Apache Ignite meetup/Moscow: https://www.gridgain.com/resources/blog/how-become-open-source-committer-and-why-youd-want I would appreciate if someone from more experienced Apache fellows can provide some comments to this post (actually, this one is based on previous feedback from Shane C.). Would it be possible to re-post this blog in 'success at Apache' series? Sincerely, Dmitriy Pavlov
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
+1, I agree we can remove this too generic ticket because possible contributor may not know what exactly needs to be done. I'd better create a couple of specific tasks to be done for contributing/updating a particular project description. вт, 23 апр. 2019 г. в 17:58, Rich Bowen : > There is not currently a way to edit these HelpWanted tickets. Perhaps > since the project is well underway, we could just delete the ticket? > > On 4/23/19 7:49 AM, Swapnil M Mane wrote: > > Nice, thanks Dmitriy. > > > > On Tue, Apr 23, 2019 at 4:37 PM Dmitriy Pavlov > wrote: > > > >> It works fine, thanks, > >> > >> I've started to fill this doc. For now, I will skip projects that are > >> managed by the same PMC. E.g. Apache Anakia does not have a separate > page, > >> but it is mentioned in https://en.wikipedia.org/wiki/Apache_Velocity > >> > >> > > +1 > > > > > >> I will also skip attic and incubator projects. Unfortunately, I can not > >> > > > > +1 > > > > > >> edit this ticket so we need somehow share this list of project & > wikipedia > >> page correspondence sheet. > >> > >> > > Agree, we should find way to add this sheet information in the ticket. > > May be we can take help from Nick (creator of the ticket) or infra. > > > > > >> Sincerely, > >> Dmitriy Pavlov > >> > >> вт, 23 апр. 2019 г. в 10:39, Swapnil M Mane : > >> > >>> Great Dmitriy, thoughts travels :-) > >>> I have granted you the access, kindly check. > >>> > >>> > >>> - Best Regards, > >>> Swapnil M Mane, > >>> ofbiz.apache.org > >>> > >>> > >>> > >>> On Tue, Apr 23, 2019 at 1:01 PM Dmitriy Pavlov > >> wrote: > >>> > >>>> Hi Swapnil M Mane, > >>>> > >>>> I was thinking about absolutely the same approach. I've requested edit > >>>> access, could you please grant it? > >>>> > >>>> Sincerely, > >>>> Dmitriy Pavlov > >>>> > >>>> вт, 23 апр. 2019 г. в 09:08, Swapnil M Mane >: > >>>> > >>>>> Hello Rich and team, > >>>>> > >>>>> As we see, various people are willing to help for this task of > >> ensuring > >>>> all > >>>>> Apache TLPs have Wikipedia pages [1]. > >>>>> I see, some of the TLPs are having there Wikipedia page in draft > >> status > >>>>> (might be some projects don't even have the page). > >>>>> So, here the approach we can follow to complete this task. > >>>>> > >>>>> I have created a Google sheet [2] containing the list of all Apache's > >>> top > >>>>> level projects. > >>>>> All those contributors who are willing to help us, we can share this > >>>> sheet > >>>>> with them with *edit* permission. > >>>>> Then they simply have to check, is the Wikipedia page for project > >>> exist, > >>>> if > >>>>> yes put the link of page else put the appropriate comment and mark > >> row > >>> as > >>>>> red. > >>>>> The sheet contain Attic and Incubating project, we can ignore them. > >>>>> > >>>>> After this we can contact the respective project community (who don't > >>>> have > >>>>> Wikipedia page) to work on Wikipedia page of project. > >>>>> > >>>>> Please let me know if your thoughts on this. > >>>>> > >>>>> [1] > >>>>> > >>>>> > >>>> > >>> > >> > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > >>>>> [2] > >>>>> > >>>>> > >>>> > >>> > >> > https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit?usp=sharing > >>>>> > >>>>> P.S. Looping in Nick, since I see the task is created by him. > >>>>> > >>>>> > >>>>> - Best Regards, > >>>>> Swapnil M Mane, > >>>>> ofbiz.apache.org > >>>>> > >>>>> > >>>>> > >>>>> On Mon
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
It works fine, thanks, I've started to fill this doc. For now, I will skip projects that are managed by the same PMC. E.g. Apache Anakia does not have a separate page, but it is mentioned in https://en.wikipedia.org/wiki/Apache_Velocity I will also skip attic and incubator projects. Unfortunately, I can not edit this ticket so we need somehow share this list of project & wikipedia page correspondence sheet. Sincerely, Dmitriy Pavlov вт, 23 апр. 2019 г. в 10:39, Swapnil M Mane : > Great Dmitriy, thoughts travels :-) > I have granted you the access, kindly check. > > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Tue, Apr 23, 2019 at 1:01 PM Dmitriy Pavlov wrote: > > > Hi Swapnil M Mane, > > > > I was thinking about absolutely the same approach. I've requested edit > > access, could you please grant it? > > > > Sincerely, > > Dmitriy Pavlov > > > > вт, 23 апр. 2019 г. в 09:08, Swapnil M Mane : > > > > > Hello Rich and team, > > > > > > As we see, various people are willing to help for this task of ensuring > > all > > > Apache TLPs have Wikipedia pages [1]. > > > I see, some of the TLPs are having there Wikipedia page in draft status > > > (might be some projects don't even have the page). > > > So, here the approach we can follow to complete this task. > > > > > > I have created a Google sheet [2] containing the list of all Apache's > top > > > level projects. > > > All those contributors who are willing to help us, we can share this > > sheet > > > with them with *edit* permission. > > > Then they simply have to check, is the Wikipedia page for project > exist, > > if > > > yes put the link of page else put the appropriate comment and mark row > as > > > red. > > > The sheet contain Attic and Incubating project, we can ignore them. > > > > > > After this we can contact the respective project community (who don't > > have > > > Wikipedia page) to work on Wikipedia page of project. > > > > > > Please let me know if your thoughts on this. > > > > > > [1] > > > > > > > > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > > [2] > > > > > > > > > https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit?usp=sharing > > > > > > P.S. Looping in Nick, since I see the task is created by him. > > > > > > > > > - Best Regards, > > > Swapnil M Mane, > > > ofbiz.apache.org > > > > > > > > > > > > On Mon, Feb 18, 2019 at 11:10 PM Dmitriy Pavlov > > > wrote: > > > > > > > Sorry, I've misread the initial email. I'll double check if there is > a > > > > missing project in Wikipedia. > > > > > > > > Sincerely, > > > > Dmitriy Pavlov > > > > > > > > пн, 18 февр. 2019 г. в 20:32, Dmitriy Pavlov : > > > > > > > > > Hi Rich, > > > > > > > > > > The task is still in the list of help-wanted service here > > > > > > > > > > > > > > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > > > > > > > > > Should I mark it as done? > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > пн, 18 февр. 2019 г. в 17:05, Rich Bowen : > > > > > > > > > >> Has anyone verified where we are on this task, recently? I think > we > > > may > > > > >> already have done this, and, if so, we really should drop this > task > > > from > > > > >> the list. Can someone take a moment to verify where we stand on > > this? > > > > >> Perhaps even one of the people who has said they want to help with > > the > > > > >> task? > > > > >> > > > > >> Meanwhile, NONE of the people who have volunteered to help with > this > > > > >> have so much as responded to my followup emails to them. Has > anyone > > > else > > > > >> had any followup from any of the volunteers? > > > > >> > > > > >> --Rich > > > > >> > > > > >> On 2/16/19 2:50 AM, S M wrote: > > > > >> > I would like to help out with the task listed at > > /task.html?0b349bee > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> > تم الإرسال من جهاز Samsung > > > > >> > > > > > >> > > > > > >> > > > > - > > > > >> > 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: Help with task: Ensure all Apache TLPs have Wikipedia pages
Hi Swapnil M Mane, I was thinking about absolutely the same approach. I've requested edit access, could you please grant it? Sincerely, Dmitriy Pavlov вт, 23 апр. 2019 г. в 09:08, Swapnil M Mane : > Hello Rich and team, > > As we see, various people are willing to help for this task of ensuring all > Apache TLPs have Wikipedia pages [1]. > I see, some of the TLPs are having there Wikipedia page in draft status > (might be some projects don't even have the page). > So, here the approach we can follow to complete this task. > > I have created a Google sheet [2] containing the list of all Apache's top > level projects. > All those contributors who are willing to help us, we can share this sheet > with them with *edit* permission. > Then they simply have to check, is the Wikipedia page for project exist, if > yes put the link of page else put the appropriate comment and mark row as > red. > The sheet contain Attic and Incubating project, we can ignore them. > > After this we can contact the respective project community (who don't have > Wikipedia page) to work on Wikipedia page of project. > > Please let me know if your thoughts on this. > > [1] > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > [2] > > https://docs.google.com/spreadsheets/d/1pBjiBB4ROB7QrIIFMLSbDUMyPjmDCf9xHI1rZnCVKd8/edit?usp=sharing > > P.S. Looping in Nick, since I see the task is created by him. > > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Mon, Feb 18, 2019 at 11:10 PM Dmitriy Pavlov > wrote: > > > Sorry, I've misread the initial email. I'll double check if there is a > > missing project in Wikipedia. > > > > Sincerely, > > Dmitriy Pavlov > > > > пн, 18 февр. 2019 г. в 20:32, Dmitriy Pavlov : > > > > > Hi Rich, > > > > > > The task is still in the list of help-wanted service here > > > > > > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > > > > > Should I mark it as done? > > > > > > Sincerely, > > > Dmitriy Pavlov > > > > > > пн, 18 февр. 2019 г. в 17:05, Rich Bowen : > > > > > >> Has anyone verified where we are on this task, recently? I think we > may > > >> already have done this, and, if so, we really should drop this task > from > > >> the list. Can someone take a moment to verify where we stand on this? > > >> Perhaps even one of the people who has said they want to help with the > > >> task? > > >> > > >> Meanwhile, NONE of the people who have volunteered to help with this > > >> have so much as responded to my followup emails to them. Has anyone > else > > >> had any followup from any of the volunteers? > > >> > > >> --Rich > > >> > > >> On 2/16/19 2:50 AM, S M wrote: > > >> > I would like to help out with the task listed at /task.html?0b349bee > > >> > > > >> > > > >> > > > >> > > > >> > تم الإرسال من جهاز Samsung > > >> > > > >> > > > >> > > - > > >> > 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: [Discuss] Attributing contributions to commercial vendors investing in projects
> Some employers actually employ people from the community to work on Open Source projects. Sorry for wordy email, but this topic is something I really care about and I assume some (employed) contributors don't understand it. I'm employed, and I use both my work and free time to contribute. But I contribute as an individual, I represent my own view when I participate in PMC discussion because I do believe in hats concept when I communicate with others I wear the hat of a community member: committer and PMC. This allows all fellows to feel free, then they have a disagreement. If we have a disagreement we, as a community, can build a consensus to find out the best possible decision. I think it is a key thing that allowed a number of ASF projects to become leading projects in their area. I also think companies can benefit from donating part of their code to open-source because a community can bring vision and ideas on how to make things better. Mentioning companies is possible somewhere in the project committers list. But it is not a good practice to stress it in emails signatures/use corporate email address/or pay too much attention to an employer on website. This can make others feel that if you employed by company A, you may have more power/influence in the community - it is not the case in the ASF. I think the responsibility of every project PMC is to avoid it. As for mentioning personal profile, probably it is not prohibited to add a link to the linked-in profile in the website field in Apache Directory. Some communities add a reference to contributors' profile in the list of committers. But still, it is always made in the context of the individual, not any kind of company contribution. чт, 18 апр. 2019 г. в 00:16, Jim Jagielski : > The ASF is an entity which is focused on the individual contributor... all > "merit" obtained is obtained by the *contributor* and not their companies. > There are some exceptions, such as the code donation of a large chunk of > code: that can be, and is, "attributed" to a company. But in general, the > focus is on the *contributor*. This is because we want to create a healthy, > viable pool of volunteer contributors no matter WHO signs their paychecks, > and projects which are truly independent upon any single company or set of > companies. We have seen how this can end, and it is not pretty. > > There are plenty of ways that companies can get attribution by the ASF, > but the normal day-to-day contributions are not it. > > > On Apr 17, 2019, at 2:27 PM, Griselda Cuevas > wrote: > > > > Hi ComDev, > > > > What are your opinions/best practices on attributing contributions to > > commercial vendors who support an Apache project. I recently had a few > > discussions with folks in OSS and they convinced me on this being a good > > idea because it has a two-fold purpose: > > > > > > 1. > > > > It brings clarity to project roadmap and dependencies. > > Knowing what companies are investing in a given area, allows users & > > contributors know who to contact to move their own contributions > faster and > > gives companies the ability to accept user suggestions. > > But the roadmap of a project is NOT set nor determined by a company. Nor > even by the ASF. It is set by the project community, with guidance and > stewardship of the PMC. Users and contributors just need to know to contact > the ASF, not investigate what companies are "involved". Any user > suggestions and feedback should be directed to the ASF and the project and > NOT to any companies. This is very important: the ASF cannot in any way be > beneficial or partial to any company. The ASF and our projects are, AND > MUST BE, fiercely independent. > > > > > > > > 1. > > > > Gives recognition to the companies (or individuals) who are investing > in > > Airflow. > > This in the long term adds value to the project brand itself as it’s > > easy to demonstrate who is using/contributing to the project. > > Again, this is a project task, not a company one. > > > > > > > So my question is: Have you seen this done in a project? If yes, how they > > do it? Would you support this? > > > > I want to clarify that I understand that Open Source is about the > > individuals and not the companies, however I also see the need for > > transparency for the sake of project agility. > > > Well, APACHE is all about individuals... It is what separates us quite > markedly from other FOSS organizations and foundations. Linux Foundation, > for example, is perfectly OK with fuzzing the line between community and > companies and even, at times, weighing the scales in favor of companies > when needed. The ASF never has, never does, and never will. Because we are, > quite frankly, ALL about the individual. To truly understand the ASF, one > MUST grok this. > > > > > Thanks > > > > G > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For
Re: [Discuss] Attributing contributions to commercial vendors investing in projects
Hi, I saw a few examples of how corporate employer's emails had a negative influence on the community health and good ideas were rejected. So (in any kind) stating that Apache Project X roadmap can be driven by company Y (or companies Y and Z) it a dangerous thing. Volunteers will never join the community if everything is decided outside community and nothing they can change here. Eventually, it becomes a fake, non-diverse community, but not real community-driven open source project development. I would not recommend the usage of a project or joining the community if you feel that things go this way. Sincerely, Dmitriy Pavlov ср, 17 апр. 2019 г. в 22:17, Shane Curcuru : > Rich Bowen wrote on 4/17/19 3:08 PM: > > By policy and long-standing tradition, no. Companies do not participate > > in projects. Individuals participate in projects. > > > > It's possible I misunderstand the question, but this is something we > > have always discouraged. > I think it's a bigger question than that, but in general I'd also be > cautious. More particularly, any new suggested practices for PMCs > should be reviewed against existing documentation: > > https://community.apache.org/projectIndependence > https://www.apache.org/foundation/marks/linking > > The big question is: how, specifically, would this be displayed on > project websites (the projects that opt to do so, obviously)? I can > imagine some ways to recognize corporations, but Rich has a hugely > important point above: only individuals are recognized as committers, > PMC members, or ASF Members - never companies. > > So while the corporate linking guidelines above show ways PMCs can > choose to recognize corporations who help their work by donating > servers/CI/whatever, we still expect all the core work on our projects > to be done with individuals using their Apache committer affiliation - > and not their corporate affiliation. > > Having some more specific examples of what this might look like would > probably help discussing the issue as well. > > > > > > > On 4/17/19 2:27 PM, Griselda Cuevas wrote: > >> Hi ComDev, > >> > >> What are your opinions/best practices on attributing contributions to > >> commercial vendors who support an Apache project. I recently had a few > >> discussions with folks in OSS and they convinced me on this being a good > >> idea because it has a two-fold purpose: > >> > >> > >> 1. > >> > >> It brings clarity to project roadmap and dependencies. > >> Knowing what companies are investing in a given area, allows users & > >> contributors know who to contact to move their own contributions > >> faster and > >> gives companies the ability to accept user suggestions. > >> > >> > >> > >> 1. > >> > >> Gives recognition to the companies (or individuals) who are > >> investing in > >> Airflow. > >> This in the long term adds value to the project brand itself as it’s > >> easy to demonstrate who is using/contributing to the project. > >> > >> > >> So my question is: Have you seen this done in a project? If yes, how > they > >> do it? Would you support this? > >> > >> I want to clarify that I understand that Open Source is about the > >> individuals and not the companies, however I also see the need for > >> transparency for the sake of project agility. > >> > >> Thanks > >> > >> G > >> > > > > > -- > > - Shane > ComDev PMC > The Apache Software Foundation > > - > 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?
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: 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: Apache Maturity Model Consensus Building contradicts Incubator rules?
Hi Chirs, I agree some disagreements exist. Practically I suppose adding (or removing) people to(or from) committer and (P)PMC status is a very sensitive thing, so there should be an opportunity of veto. While process changes and releases can't be vetoed, adding committers or PMCs should be consensus only. If it is the Majority approval it is always easy for some commercial company to take full control of any project. In this case, some individual PMC has almost no influence on PMC members/Committers. All people from a company will generate as much +1's as needed to elect new PMCs/Committers, even if this one true volunteer will vote -1. Sincerely, Dmitriy Pavlov ср, 20 мар. 2019 г. в 15:43, Christofer Dutz : > Hi all, > > I’m currently working on finishing some things in preparation of > graduation … one thing we were requested to address, is to do an assessment > of the Apache Maturity Model for our project. > > Within this, there’s a rule: > CS40 - In Apache projects, vetoes are only valid for code commits and are > justified by a technical explanation, as per the Apache voting rules > defined in CS30. > > This sort of contradicts the rules for incubating projects specified by > the Incubator, which says: > https://wiki.apache.org/incubator/DefaultProjectGuidelines > > - Consensus Approval< > https://www.apache.org/foundation/glossary.html#ConsensusApproval> – > Consensus approval requires 3 binding< > https://www.apache.org/foundation/voting.html#binding-votes> +1 votes and > no -1 votes (vetoes<https://www.apache.org/foundation/glossary.html#Veto > >). > > So for Consensus Approval there are Vetoes and code changes apply for Lazy > Consensus. If there are actually vetoes for code changes, I can imagine > that quite some projects would stall instantly. > > > The incubator guidelines state for adding (or removing) people to(or from) > committer and PPMC status, these guidelines claim them being Consensus > Approval, which allows vetoes. > > Would be cool if this could be streamlined to be more aligned. Right now I > claim that the PLC4X project simply fails CS40 as this contradicts the > incubator rules. > > Chris >
Re: Help with task: Ensure all Apache TLPs have Wikipedia pages
Sorry, I've misread the initial email. I'll double check if there is a missing project in Wikipedia. Sincerely, Dmitriy Pavlov пн, 18 февр. 2019 г. в 20:32, Dmitriy Pavlov : > Hi Rich, > > The task is still in the list of help-wanted service here > https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 > > Should I mark it as done? > > Sincerely, > Dmitriy Pavlov > > пн, 18 февр. 2019 г. в 17:05, Rich Bowen : > >> Has anyone verified where we are on this task, recently? I think we may >> already have done this, and, if so, we really should drop this task from >> the list. Can someone take a moment to verify where we stand on this? >> Perhaps even one of the people who has said they want to help with the >> task? >> >> Meanwhile, NONE of the people who have volunteered to help with this >> have so much as responded to my followup emails to them. Has anyone else >> had any followup from any of the volunteers? >> >> --Rich >> >> On 2/16/19 2:50 AM, S M wrote: >> > I would like to help out with the task listed at /task.html?0b349bee >> > >> > >> > >> > >> > تم الإرسال من جهاز Samsung >> > >> > >> > - >> > 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: Help with task: Ensure all Apache TLPs have Wikipedia pages
Hi Rich, The task is still in the list of help-wanted service here https://helpwanted.apache.org/task.html?0b349bee48c7e47a20fb29222b8217fa61b11d31 Should I mark it as done? Sincerely, Dmitriy Pavlov пн, 18 февр. 2019 г. в 17:05, Rich Bowen : > Has anyone verified where we are on this task, recently? I think we may > already have done this, and, if so, we really should drop this task from > the list. Can someone take a moment to verify where we stand on this? > Perhaps even one of the people who has said they want to help with the > task? > > Meanwhile, NONE of the people who have volunteered to help with this > have so much as responded to my followup emails to them. Has anyone else > had any followup from any of the volunteers? > > --Rich > > On 2/16/19 2:50 AM, S M wrote: > > I would like to help out with the task listed at /task.html?0b349bee > > > > > > > > > > تم الإرسال من جهاز Samsung > > > > > > - > > 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: The Apache Way and good developers don’t like to communicate
Hi Craig, Ignite dev list is now quite busy-list. GitHub comments are not forwarded (for the main repository, it is only forwarded for an additional GitBox repository, and probably we need to disable it as well or create notifications list). Forwarding comments may create additional pressure to contributors because they need to filter out emails from contributions which are not interesting. Some Ignite developers use the list to find a reviewer, and reviewers reply to dev list/to JIRA about results. The reviewer mentions where to find comments. Community Developers, thank you for all your replies. I've forwarded the reference to this thread and to 'large code drops' thread to Ignite dev list. I'm sure it will help the participants to understand why it is an important thing to share their ideas/plans/results using the list. Sincerely, Dmitriy Pavlov пт, 2 нояб. 2018 г. в 18:31, Craig Russell : > +1 to what Myrle says. > > I especially like the idea of engaging the submitter to discuss a pull > request. Even if it's to say "Thanks for this. It looks perfect as is". But > often, there will be a bit of back and forth. > > One potential problem is the work flow using the github tools, which can > have the effect of dialog "off-list" between the submitter and the other > devs. I don't know how to solve this issue except for one of the other devs > to initiate contact via the dev list in addition to the issue tools. > > Are the github tools for the project configured to copy the dev list on > every interaction on a pull request? > > Craig > > > On Nov 2, 2018, at 8:23 AM, Myrle Krantz wrote: > > > > If anyone on the PMC is uncomfortable with making someone a committer > > because of their uncommunicativeness, I'd be inclined to give it a little > > more time. A "no" now, doesn't mean a "no" forever. Maybe ask that > person > > a few questions about their PR's on the list and see if they can be > > encouraged to engage? Maybe let the PMC member who's advocating for a > > particular contributor be the one to take point on that effort? > > > > Greets, > > Myrle > > > > Craig L Russell > Secretary, Apache Software Foundation > c...@apache.org <mailto:c...@apache.org> http://db.apache.org/jdo < > http://db.apache.org/jdo> >
Re: The Apache Way and good developers don’t like to communicate
Dear ASF Fellows, I strongly appreciate all your replies. I believe there is no just one correct answer. Which is why I need opinions of folks from other projects. Myrle, Apache Ignite has 26 PMC members and 38 committers, so PMCs is a subset of committers set. About collaboration: I guess these contributors were communicating with someone of community within a company they work for, in person/or, probably, Skype. So maybe the code was good. And they became effective code contributors without valuable communication on lists and without contributing to the community. Chris, About the subject: it is translated version of the argument I hear about contributors, who are not often present on dev/user list. So if a person does not like to communicate, let's say, afraid of society/publicity, can he or she be a committer in Apache? Sincerely, Dmitriy Pavlov пт, 2 нояб. 2018 г. в 14:31, Myrle Krantz : > Hi Dmitriy, > > Is Ignite a PMC = committer community or a PMC ⊂ committer community? > > You may have different requirements for communication level depending on > which of these your community is. But I don't believe it is possible to > write very good code without being willing to talk with others about it. > > Still, different communities have different "bars". And I've come to be > convinced by Greg Stein, that a lower committer bar is better for > attracting contributions. People might feel more comfortable communicating > once they've been given the committer bit? > > Regards, > Myrle > > On Fri, Nov 2, 2018 at 9:53 AM Dmitriy Pavlov > wrote: > > > Dear ASF Fellows, > > > > I am PMC member of Apache Ignite, but I joined PMC relatively recently. I > > need help from you again in regarding the Apache Way. > > > > Question is related to comittership for community members, > > > > - who are not visible on dev/user list, have a couple of threads they > > participated > > > > - but contributed a significant feature or many fixes. > > > > Usually, such contributors work for a commercial company with sufficient > > product expertise, so they probably collaborate with experts, but outside > > space of Apache. > > > > > > Several guides and policies > > > > https://www.apache.org/foundation/how-it-works.html#meritocracy > > > > http://community.apache.org/newcommitter.html > > > > and others say that PMC member needs to evaluate communication and > > cooperative work with peers, ability to be a mentor, behavior in > > disagreement. > > > > > > Communication is required by Apache Ignite guide > > > > > https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance > > > > Simultaneously > > https://community.apache.org/contributors/#contributing-a-project-copdoc > > > > contains a mention someone who contributed sufficiently to ‘ANY’ area may > > become a committer. So why can't we count code only contribution without > > contribution to community/project? > > > > There are several cases when I may disagree with other PMC members. > > > > I insist candidate should communicate in ASF space because A) > > community-first and motto: B) “If it didn’t happen on the mailing list it > > didn’t happen.” For such cases then contributors collaborate outside > Apache > > space we can still accept a contribution, still appreciate contributor’s > > effort and say thank you; but not promote as a committer. But I may > > over-estimate the role of collaboration in the ASF. I may be too strict > in > > understanding ASF principles. > > > > But PMCs who suggest such comittership candidates may counter-argument > > > > - those cool developers don't like to communicate (they may be a little > bit > > uncomfortable with public communications/tries to avoid spam/any other > > reasons they have). > > > > - If he or she will communicate often, then he or she will never have > time > > to write a code. > > > > So what do you think? Is it required to communicate with the rest of the > > community publicly more than a couple of times to become a committer? > > > > Sincerely, > > > > Dmitriy Pavlov > > >
The Apache Way and good developers don’t like to communicate
Dear ASF Fellows, I am PMC member of Apache Ignite, but I joined PMC relatively recently. I need help from you again in regarding the Apache Way. Question is related to comittership for community members, - who are not visible on dev/user list, have a couple of threads they participated - but contributed a significant feature or many fixes. Usually, such contributors work for a commercial company with sufficient product expertise, so they probably collaborate with experts, but outside space of Apache. Several guides and policies https://www.apache.org/foundation/how-it-works.html#meritocracy http://community.apache.org/newcommitter.html and others say that PMC member needs to evaluate communication and cooperative work with peers, ability to be a mentor, behavior in disagreement. Communication is required by Apache Ignite guide https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance Simultaneously https://community.apache.org/contributors/#contributing-a-project-copdoc contains a mention someone who contributed sufficiently to ‘ANY’ area may become a committer. So why can't we count code only contribution without contribution to community/project? There are several cases when I may disagree with other PMC members. I insist candidate should communicate in ASF space because A) community-first and motto: B) “If it didn’t happen on the mailing list it didn’t happen.” For such cases then contributors collaborate outside Apache space we can still accept a contribution, still appreciate contributor’s effort and say thank you; but not promote as a committer. But I may over-estimate the role of collaboration in the ASF. I may be too strict in understanding ASF principles. But PMCs who suggest such comittership candidates may counter-argument - those cool developers don't like to communicate (they may be a little bit uncomfortable with public communications/tries to avoid spam/any other reasons they have). - If he or she will communicate often, then he or she will never have time to write a code. So what do you think? Is it required to communicate with the rest of the community publicly more than a couple of times to become a committer? Sincerely, Dmitriy Pavlov
Re: Blog post about Apache Ignite Community structure
Hi Shane, Thank you for finding time to review. It seems I still able to edit the original post, so I will try to include your proposals. BTW escalation guide is great, and I'll definitely share it with Apache Ignite developers. Sincerely, Dmitriy Pavlov пн, 8 окт. 2018 г. в 21:27, Shane Curcuru : > Dmitriy Pavlov wrote on 10/8/18 11:46 AM: > > Dear Community Developers, > > > > I want to share with new my blog post "Introduction to the Apache® > Ignite™ > > community structure." > > > > > https://www.gridgain.com/resources/blog/introduction-apacher-ignitetm-community-structure > > There I explain the roles, rules, and benefits of participating in > Apache > > communities. > > Hey, that's a pretty good overview, and you've brought in a lot of > different concepts of the Apache Way into the article - nice. > > > Is it reasonable to develop this post somehow and (re)publish on Apache > > blogging engine? If not, what kind of blogs may be interesting to other > > Apache members? > > Every Apache project can request a blogs.a.o for their project: > > http://www.apache.org/dev/project-blogs > > > Because I want to develop my background related to understanding the > Apache > > Way, I heartily appreciate comments and feedback. > > Minor corrections: > > s/APACHE FOUNDATION/APACHE SOFTWARE FOUNDATION/ > > Projects "graduate" from the incubator to become TLPs. > > Consider updating the Developer/Contributor paragraph to note that > projects value non-code contributions too, from writers, editors, > testers, etc. > > Consider pointing to the lists.a.o mail archive, which might be > friendlier for people who complain about mailing lists: > > https://lists.apache.org/list.html?dev@community.apache.org > > > -- > > - Shane > Director & Member > The Apache Software Foundation > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Blog post about Apache Ignite Community structure
Dear Community Developers, I want to share with new my blog post "Introduction to the Apache® Ignite™ community structure." https://www.gridgain.com/resources/blog/introduction-apacher-ignitetm-community-structure There I explain the roles, rules, and benefits of participating in Apache communities. Is it reasonable to develop this post somehow and (re)publish on Apache blogging engine? If not, what kind of blogs may be interesting to other Apache members? Because I want to develop my background related to understanding the Apache Way, I heartily appreciate comments and feedback. Sincerely, Dmitriy Pavlov
Re: Idea feedback request: Project mailing list specifically for upstream users
Hi Alex, I'm sure you know your project specific better, and probably separate list is the best/only solution. I don't see any problems if the community agrees about it and a new list is well documented. But uniformity of mailing lists between Apache projects helps a lot to contribute to different projects. You always know where to write. If you will to contribute to the project - you can write to a dev. If you just use it - to a user. I would like to propose to use user list with some mark in emails. Then some filtered view can be prepared for emails related to upstream. I hope it helps. Sincerely, Dmitriy Pavlov ср, 26 сент. 2018 г. в 1:05, Alexandre Rafalovitch : > In my mind, there are three differentiation: > 1) The Solr Users mailing list traffic is quite large and diverse. So, > it can be both overwhelming (for everybody) and hard to notice > messages that are possibly of much higher impact than others. An > upstream framework that is suddenly broken or wants to adopt a new > feature has a larger impact on overall user experience, then one > person's individual journey through Solr features and its current > limitations. So, there is a multiplier effect of attention if handled > right. > 2) The upstream implementer's questions are usually a mix of > super-technical details and potentially not complete understanding of > Solr. So, they could benefit - in my mind - of having space of their > own being more technical an/or in-depth than Users list and less > Solr-tuned than Dev list. > 3) The other people on such list would be other implementers with > similar questions (e.g. new schema configuration API specifics) and so > they could benefit from each other's questions in the way people on > the Solr Users mailing list do much less frequently. > > I hope this clarifies my reasoning. >Alex. > > On 25 September 2018 at 17:49, Luciano Resende > wrote: > > On Tue, Sep 25, 2018 at 5:30 PM Alexandre Rafalovitch > > wrote: > >> > >> Hi, > >> > >> I have an idea that I would love to get feedback on to see if it makes > >> sense, feasible, has been tried, is currently being done by somebody, > >> etc. > >> > ... > >> Would it make sense to have a mailing list where committers of > >> upstream projects could ask questions related to their implementation > >> of API, interface, feature dependency, etc? The list would need to be > >> backed by a couple of primary project committers (preferably with a > >> wide rather than deep feature knowledge) that can explain new > >> features, translate the jargon, help troubleshoot the failures, etc. > >> > > > > > > > Wouldn't these type of questions also be beneficial for general users? > > > > I see your scenario more like advanced users versus regular users, but > > I also see regular users becoming advanced users at some point (but > > probably in a smaller percentage). > > > > -- > > Luciano Resende > > http://twitter.com/lresende1975 > > http://lresende.blogspot.com/ > > > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: Contribute to Apache Software Foundation
Hi Raghav, Unfortunately, I don't know much about GSOC. But you can select any project you like. Projects sorted by language can be found here: https://projects.apache.org/projects.html?language and by topic here: https://projects.apache.org/projects.html?category That might help you to narrow down the options. Once you select a project you interested to contribute to, you can contact with contributors (developers) there. If you need help getting introduced to the project community, please don't hesitate to ask. Usually, a project has a guide on how to contribute and provides a list of easy tickets to start with. Probably I will be able to help with guiding you in that project. Welcome aboard! Sincerely, Dmitriy Pavlov сб, 22 сент. 2018 г. в 20:36, Raghvendra Gupta : > Hi, > I am Raghvendra Gupta, a final year undergrad student at SGSITS Indore. I > am new to open source world and interested in contributing to the Apache > Software Foundation. > > Having an interest in distributed and cloud computing domain, I am aiming > for GSOC 2019. I am flexible with the choice of programming language. > Please guide me through my very first contribution in ASF. > > > Thank You > Regards, > Raghvendra Gupta > Final Year Undergrad - SGSITS Indore >
Re: .Need Someone to Help Me to Contribute
Hi Jack, As the Apache Software Foundation principles and values include 'comfortable technical discussion', I think, every Apache project should be welcoming and friendly to newcomers. I guess some incubating projects may need volunteers more than top-level projects, but I just guessing here. If you will need any assistance in the project's process, I will do my absolute best to help. Sincerely, Dmitriy Pavlov пт, 21 сент. 2018 г. в 23:29, Awasum Yannick : > Hello Jack, > > Welcome to the Apache Software Foundation. > > There is a large number of Apache Open Source projects written in Java and > also more than a dozen written in C: > https://projects.apache.org/projects.html?language > > Go though the list, visit the websites of the projects which use your > language(s) of choice, then pick anyone which interests you and subscribe > to the developers mailing list and introduce yourself. People are going to > point in the right direction on how to get started with the specific > project. > > This list is for general Apache Community Development. Mostly non-technical > stuff, event planning, culture and others. > > I hope this helps. > > Thanks. > Awasum Yannick > > > On Fri, Sep 21, 2018 at 7:12 PM Jack Tsai > wrote: > > > Dear Sir/Madam, > > > > I am good at java programming and know a little about C programming. I > am a > > freshman to open source development. Please can someone help me to get > > started or let me know if there is the project which is friendly or be > > easier for the newcomers. > > > > Best regards, > > jack870131 > > >
Re: help me to contribute
One more thing, once you select a project you interested to contribute to, you can let me know, and I will also subscribe to their mailing list too. So if you will need any assistance in the project's process, I will do my absolute best to help. пт, 21 сент. 2018 г. в 20:07, Dmitriy Pavlov : > Hi, > > you can find some project written in Java and contact with contributors > (developers) there. > > Usually, a project has a guide on how to contribute and provides a list of > easy tickets to start with. > > Sincerely, > Dmitriy Pavlov > > пт, 21 сент. 2018 г. в 19:46, sheetal bharadwaj < > sheetal.bhashaka...@gmail.com>: > >> I am good at java, have a little knowledge of c. I am very new to open >> source development. Please help me get started >> -- >> sheetal b.bharadwaj >> >
Re: help me to contribute
Hi, you can find some project written in Java and contact with contributors (developers) there. Usually, a project has a guide on how to contribute and provides a list of easy tickets to start with. Sincerely, Dmitriy Pavlov пт, 21 сент. 2018 г. в 19:46, sheetal bharadwaj < sheetal.bhashaka...@gmail.com>: > I am good at java, have a little knowledge of c. I am very new to open > source development. Please help me get started > -- > sheetal b.bharadwaj >
Re: YATAWP
Hi Daniel, Slides are great! Good luck with the presentation. 2 month ago I presented a similar speech at Moscow Apache Ignite meetup. Then I have created an overview of `how ASF works`. As I could see from comments and questions, this topic is not well-known by developers. I think it needs to be covered every time when we have a chance to. Sincerely, Dmitriy Pavlov ср, 22 авг. 2018 г. в 0:10, Kevin A. McGrail : > If you want to share more detailed speaker notes for 12-15, that might > help. Doesn't have to be prose but an outline. > > -- > Kevin A. McGrail > VP Fundraising, Apache Software Foundation > Chair Emeritus Apache SpamAssassin Project > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171> > > On Tue, Aug 21, 2018 at 4:57 PM, Daniel Ruggeri > wrote: > > > Hi, Jim; > >Is it about The Apache Way or an overview of the ASF? Answer: "Yes!" > > > >As mentioned to KAM in my previous reply, the meat you are looking for > > (and where I will spend most attention to detail) is in slides 12-15 > > talking about some of those tenets. > > > >At the same time, my recent booth duty at OSCON reminded me that a lot > > of folks still think "Apache" == "that webserver I installed once" and > had > > no idea about the other projects and *all the stuff* the foundation > > does/is, so I wanted to work that in, too. > > > > -- > > Daniel Ruggeri > > > > > > > > On 2018-08-21 15:11, Jim Jagielski wrote: > > > >> Thanks! > >> > >> There seems very little meat on the actual Apache Way and it's more an > >> overview of the ASF and our projects. Is that the intent? > >> > >> On Aug 21, 2018, at 2:24 PM, Daniel Ruggeri > wrote: > >>> > >>> ... stands for "Yet Another The Apache Way Presentation" :-) > >>> > >>> I just wanted to share this for additional eyes and feedback. This is a > >>> much-needed modernization of an older The Apache Way presentation I put > >>> together circa '15. > >>> http://people.apache.org/~druggeri/presentations/TheApacheWay.pdf > >>> > >>> I plan to give this talk next week at OSSummit, assuming no glaringly > >>> bad mistakes were made: > >>> https://ossna18.sched.com/event/FAPH/the-apache-way-daniel- > >>> ruggeri-mastercard > >>> > >>> As always, feedback/patches welcome. > >>> > >>> -- > >>> Daniel Ruggeri > >>> > >>> - > >>> 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: Link share: well done etiquette FAQ
Hi Daniel, Thank you for sharing this. I've found some things what I do wrong :) Sincerely, Dmitriy Pavlov пт, 3 авг. 2018 г. в 16:18, Daniel Ruggeri : > Hi, all; >During my random and incoherent stumblings around the Internet I came > across a really great FAQ for discussion etiquette and figured I would > share: > https://discourse.pi-hole.net/faq > > I really don't have a call to action by sharing it, as I'm not trying to > say that there's something wrong with the comdev-created guide... just that > I thought this was a pretty good one, too :-) > -- > Daniel Ruggeri
Re: Assigning tickets to someone else in community
Dear Mentors, Thank you so much for your comments on this topic. I feel in completely the same way. I will continue to learn the Apache Way, and I hope I would be able to help to other communities. Sincerely, Dmitriy Pavlov вт, 31 июл. 2018 г. в 20:09, Rafael Weingärtner : > In CloudStack (we use Github workflow now) only members can assign PRs and > issues to users. Therefore, when an issue or PR is created it does not have > an assignee. Then, when a contributor starts working on it, the community > members (committer or PMC) will assign this contributor to the issue/PR. > The member will also set the proper tags and milestone to the issue/PR. > > I think in an open source community where everything is distributed, > asynchronous and volunteer work we should leave the issues open to anyone > until someone volunteers to work on it. Otherwise, we might face the risk > of assigning issues to people, and they (the issues) never get resolved > (for numerous reason that we do not need to get into details here). > > I also find issues without assignee more welcoming to contributors. I mean, > if some issue has already an assignee I would think twice before starting > to work on it; moreover, I would only reach the person if I really need the > issue to be resolved, otherwise I would wait. On the other hand, if the > issue has no assignee and I am interested to work on it, I start right > away. > > > To answer your questions: > > > can he or she assign it directly to maintainer? > > > I would rather open an issue/ticket and reach people in the mailing list; > not asking for people to solve something for you, but rather discussing and > trying to create a solution together with the community. Assigning things > to people seems the role of a project manager that has some sort of power > over the managed team. Speaking from experience I do not take it nicely > when someone that uses the project I am a volunteer at (which I might now > know ) “assigns work” to me. > > > Or contributor should always assign ticket to him or herself? > > > Leave tickets/issues open to people. Only assign them (tickets/issues) when > someone has already started working on it (do you see the shift on workflow > here? ). Then, you are not ordering, you are simply filling out some meta > information regarding the person that has taken upon an issue. > > Is this regulated/recommended by the Apache policies? > > Not that I know of. > > > > On Tue, Jul 31, 2018 at 1:31 PM, Alexei Fedotov > wrote: > > > IMHO good practice is that community is unaware of your company > > policies. There is no gain in enforcing internal policies to external > > community members. > > > > Adapt. ) > > -- > > Carry a towel > > http://dataved.ru/ > > +7 916 562 8095 <+7%20916%20562-80-95> > > > > [1] Join Alexei Fedotov @linkedin, http://ru.linkedin.com/in/dataved/ > > [2] Join Alexei Fedotov @facebook, http://www.facebook.com/openmeetings > > [3] Start using Apache Openmeetings today, > http://openmeetings.apache.org/ > > > > > > On Tue, Jul 31, 2018 at 7:06 PM, Dmitriy Pavlov > > wrote: > > > Dear Mentors, > > > > > > I have a question that I have not yet found an answer to. Can community > > > members assign tasks to other contributor in JIRA. I mean the case that > > > someone wants a particular contributor to do a task, can he or she > assign > > > it directly to maintainer? > > > > > > Or contributor should always assign ticket to him or herself? > > > > > > Is this regulated/recommended by the Apache policies? Or it is given to > > the > > > community to decide. > > > > > > Thank you in advance. > > > > > > Sincerely, > > > Dmitry Pavlov > > > > > > P.S. Discussion recently occurred at Apache Ignite community dev. List > > > http://apache-ignite-developers.2346864.n4.nabble. > > com/Fwd-jira-Assigned-IGNITE-9113-Allocate-memory-for-a- > > data-region-when-first-cache-assigned-to-this-red-td33172.html > > > > > > And I always believed that it is always necessary that only community > > > member can assign ticket to him or herself. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > -- > Rafael Weingärtner >
Assigning tickets to someone else in community
Dear Mentors, I have a question that I have not yet found an answer to. Can community members assign tasks to other contributor in JIRA. I mean the case that someone wants a particular contributor to do a task, can he or she assign it directly to maintainer? Or contributor should always assign ticket to him or herself? Is this regulated/recommended by the Apache policies? Or it is given to the community to decide. Thank you in advance. Sincerely, Dmitry Pavlov P.S. Discussion recently occurred at Apache Ignite community dev. List http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-jira-Assigned-IGNITE-9113-Allocate-memory-for-a-data-region-when-first-cache-assigned-to-this-red-td33172.html And I always believed that it is always necessary that only community member can assign ticket to him or herself.
