On Sun, Mar 08, 2015 at 06:08PM, David Nalley wrote: > On Sun, Mar 8, 2015 at 5:55 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > > On Sun, Mar 8, 2015 at 2:45 PM, Ross Gardler (MS OPEN TECH) > > <ross.gard...@microsoft.com> wrote: > >> Who said we allow it for engineers? My position is the same for any > >> community member no matter what they do. > > > > It is all over LI and resumes. Here's a good example: > > https://www.linkedin.com/profile/view?id=759319 > > "Developer at Apache Maven" > > > > But he is an Apache Maven developer. (and committer, and PMC member). > That's very different than hiring someone off the street with a $bigco > job title of Maven Developer with no standing in the community.
That's actually a great differentiator between the categories. Let me rephrase: - it is acceptable to use "Developer of/at Apache Foo" for a committer/PMC of Foo - it is NOT suitable to say "Apache Bar Developer" if is tasked with maintenance and advancements of a private fork/version of Apache Bar at Z-Enterprise - one can say "Apache Foo Community Technologist/Manager" if Foo's PMC assigned such a title to a certain member of the community to deal with conferences, preparation of PR materials, being a liaison with other OSS and commercial projects. - however, a title can NOT say "Apache Foo Community Manager" while assigned and paid by the owners of Z-Enterprise to read through Apache Foo mail-lists and rebuke if someone make a slightly negative remark about his/her employer. I think Roman's question boils down to the latter. from ASF stand-point, what would be an acceptable title for a person who's responsibility is to help with meetups, blogs, and similar things related to Apache Foo project yet getting paid for it by Z-Enterprise? And honestly I don't have a good answer for this. Perhaps the following might help... What about titles for people who, say, responsible for how a company integrates itself with an open-source projects: setting up contribution policies, guiding the company's legal and marketing to make sure they are aware of proper use and best practices adopted in the open source community, etc. etc. That's easy, I believe ;) It could be pretty much whatever blows your hair back: - Open Source Evangelist (it has been mentioned elsewhere, that it doesn't received well in Europe) - Director of Open Source Communities - and so on... Say, my own title is "VP, Open Source Development" which doesn't infringe on any Apache (or other foundations) projects I might be associated with. Or I might not be involved and yet would have to work with those communities for whatever reason. Cos
