Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Thanks for the info, Daniel. Updated. In terms of keeping project info updated, is this info along with all the release info, etc. being pulled from the project DOAP files? If not, do we still need to maintain them? Do I need to do anything additional for it to show up in the listing on https://projects-new.apache.org/projects.html or will something eventually kick in to add it to the index? https://projects-new.apache.org/project.html?tez seems to show my updates. thanks — Hitesh On Mar 7, 2015, at 2:12 AM, Daniel Gruno humbed...@apache.org wrote: Hi Hitesh, log onto https://projects-new.apache.org/edit/ and go to the bottom. Pick 'tez' as the PMC and nothing as the sub-project name, click the button and start typing :) That will create a tez.json file that the site will then use. With regards, Daniel. On 2015-03-07 04:56, Hitesh Shah wrote: Same question for Apache Tez. How do we need to fix the new website to show the Tez project? thanks — Hitesh On Mar 6, 2015, at 1:46 PM, Marshall Schor m...@schor.com wrote: I can see the Apache UIMA entry in the old page, but it's not listed on the new page. What needs fixing? -Marshall Schor On 3/6/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
On Sun, Mar 8, 2015 at 2:24 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: I'm -1 on using Apache Foo in a job title. It great confusion between the paid role and the community role. The community role is not attached to a paid role. It is connected to the individual. Like I said -- I consider it unfair if we allow it for engineers, but for community managers. And before we get all brand-conscious let me remind you guys that there's a significant premium being placed on 'Software Engineer, Apache FOO' when it comes to LinkedIN and resumes in general. I know, I know -- excessive fascination and all that, but lets be realistic. The fact that ppl. DO want that badge of honor is one of the major driving factors in growth of quite a few communities around ASF. I see no reason why individuals can't also use ASF titles where appropriate. Can you elaborate how? I see no problem with a product title that is associated with an Apache project in ways permitted by our trademark policy. I don't understand why you say what about things like Apache Cloudstack there is no product named Cloudstack. Exactly! So while I can be Databricks cloud community manager I can't be Cloudstack community manager according to your preference. So, for example, a title of technical/community evangelist Product Foo and a reference to Committer Apache Bar or similar is fine. True. But it has no way of fitting on a business card. Thanks, Roman.
Project base data change for project 'tez'
Hello,
The following new base data was set for tez by hitesh:
{
category: http://projects.apache.org/category/big-data;,
GitRepository: https://git-wip-us.apache.org/repos/asf/tez.git;,
bug-database: https://issues.apache.org/jira/browse/TEZ;,
description: ,
mailing-list: http://tez.apache.org/mail-lists.html;,
programming-language: Java,
file: tez,
pmc: tez,
shortdesc: Apache Tez is an effort to develop a generic application
framework which can be used to process arbitrarily complex directed-acyclic
graphs (DAGs) of data-processing tasks and also a re-usable set of
data-processing primitives which can be used by other projects.,
download-page: http://tez.apache.org/releases/;,
homepage: http://tez.apache.org/;,
SVNRepository: ,
name: Apache Tez
}
With regards,
projects.apache.org
Project base data change for project 'tez'
Hello,
The following new base data was set for tez by hitesh:
{
category: http://projects.apache.org/category/big-data;,
GitRepository: https://git-wip-us.apache.org/repos/asf/tez.git;,
bug-database: https://issues.apache.org/jira/browse/TEZ;,
description: ,
mailing-list: http://tez.apache.org/mail-lists.html;,
programming-language: Java,
file: tez,
pmc: tez,
shortdesc: Apache Tez is an effort to develop a generic application
framework which can be used to process arbitrarily complex directed-acyclic
graphs (DAGs) of data-processing tasks and also a re-usable set of
data-processing primitives which can be used by other projects.,
download-page: http://tez.apache.org/releases/;,
homepage: http://tez.apache.org/;,
SVNRepository: ,
name: Apache Tez
}
With regards,
projects.apache.org
Project base data change for project 'tez'
Hello,
The following new base data was set for tez by hitesh:
{
category: http://projects.apache.org/category/big-data;,
GitRepository: https://git-wip-us.apache.org/repos/asf/tez.git;,
bug-database: https://issues.apache.org/jira/browse/TEZ;,
description: ,
mailing-list: http://tez.apache.org/mail-lists.html;,
programming-language: Java,
file: tez,
pmc: tez,
shortdesc: Apache Tez is an effort to develop a generic application
framework which can be used to process arbitrarily complex directed-acyclic
graphs (DAGs) of data-processing tasks and also a re-usable set of
data-processing primitives which can be used by other projects.,
download-page: http://tez.apache.org/releases/;,
homepage: http://tez.apache.org/;,
SVNRepository: ,
name: Apache Tez
}
With regards,
projects.apache.org
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 19:33, Hitesh Shah wrote: Thanks for the info, Daniel. Updated. In terms of keeping project info updated, is this info along with all the release info, etc. being pulled from the project DOAP files? If not, do we still need to maintain them? No, if/when projects.apache.org gets replaced with the new system, you do not need to maintain doap files. As for the data update, I did see you push the save button a few times there ;). Your browser probably caches the json objects for N minutes, which is why you did not notice that the data had indeed been updated. Once we move this to a faster TLS terminator, we can look at updating JSON objects more often within browsers. With regards, Daniel Do I need to do anything additional for it to show up in the listing on https://projects-new.apache.org/projects.html or will something eventually kick in to add it to the index? https://projects-new.apache.org/project.html?tez seems to show my updates. thanks — Hitesh On Mar 7, 2015, at 2:12 AM, Daniel Gruno humbed...@apache.org wrote: Hi Hitesh, log onto https://projects-new.apache.org/edit/ and go to the bottom. Pick 'tez' as the PMC and nothing as the sub-project name, click the button and start typing :) That will create a tez.json file that the site will then use. With regards, Daniel. On 2015-03-07 04:56, Hitesh Shah wrote: Same question for Apache Tez. How do we need to fix the new website to show the Tez project? thanks — Hitesh On Mar 6, 2015, at 1:46 PM, Marshall Schor m...@schor.com wrote: I can see the Apache UIMA entry in the old page, but it's not listed on the new page. What needs fixing? -Marshall Schor On 3/6/2015 11:52 AM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
RE: What's the ideal job title for somebody who is payed to help ASF communities grow?
I'm -1 on using Apache Foo in a job title. It great confusion between the paid role and the community role. The community role is not attached to a paid role. It is connected to the individual. I see no reason why individuals can't also use ASF titles where appropriate. I see no problem with a product title that is associated with an Apache project in ways permitted by our trademark policy. I don't understand why you say what about things like Apache Cloudstack there is no product named Cloudstack. So, for example, a title of technical/community evangelist Product Foo and a reference to Committer Apache Bar or similar is fine. Ross Sent from my Windows Phone From: Roman Shaposhnikmailto:r...@apache.org Sent: 3/8/2015 2:09 PM To: ComDevmailto:dev@community.apache.org Subject: What's the ideal job title for somebody who is payed to help ASF communities grow? Hi! a recent thread with one of the PMCs pointed out an issue that I've long wanted to solicit feedback for: what is the ideal job title for somebody who is payed to help ASF communities grow? I have always thought that 'Technical/Community Evangelist, Apache FOO' would be appropriate, just like 'Software Engineer, Apache FOO' doesn't seem to be problematic. However it was pointed out, that when we're talking community as opposed engineering adding an Apache project name could be misleading and give an impression that the person somehow has a way to direct that community b/c of the job function. Question #1: what's the general consensus on 'Technical/Community Evangelist, Apache FOO' ? If we'd rather discourage its use, what are the alternatives? One that was suggested so far was to drop the 'Apache FOO'. This could work but seems unfair to the person who may be as bonafide a community evangelist as they come. Another idea was to use commercial product names where appropriate instead of Apache FOO. Thus instead of saying 'Technical/Community Evangelist, Apache FOO' it would say 'Technical/Community Evangelist, FOOPROD'. This could work for cases where project names != product names, but what about things like Apache CloudStack? Thanks, Roman.
RE: What's the ideal job title for somebody who is payed to help ASF communities grow?
Who said we allow it for engineers? My position is the same for any community member no matter what they do. Ross Sent from my Windows Phone From: Roman Shaposhnikmailto:ro...@shaposhnik.org Sent: 3/8/2015 2:39 PM To: ComDevmailto:dev@community.apache.org Subject: Re: What's the ideal job title for somebody who is payed to help ASF communities grow? On Sun, Mar 8, 2015 at 2:24 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: I'm -1 on using Apache Foo in a job title. It great confusion between the paid role and the community role. The community role is not attached to a paid role. It is connected to the individual. Like I said -- I consider it unfair if we allow it for engineers, but for community managers. And before we get all brand-conscious let me remind you guys that there's a significant premium being placed on 'Software Engineer, Apache FOO' when it comes to LinkedIN and resumes in general. I know, I know -- excessive fascination and all that, but lets be realistic. The fact that ppl. DO want that badge of honor is one of the major driving factors in growth of quite a few communities around ASF. I see no reason why individuals can't also use ASF titles where appropriate. Can you elaborate how? I see no problem with a product title that is associated with an Apache project in ways permitted by our trademark policy. I don't understand why you say what about things like Apache Cloudstack there is no product named Cloudstack. Exactly! So while I can be Databricks cloud community manager I can't be Cloudstack community manager according to your preference. So, for example, a title of technical/community evangelist Product Foo and a reference to Committer Apache Bar or similar is fine. True. But it has no way of fitting on a business card. Thanks, Roman.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+0.5 I really like the graphics and general idea: that's for sure the way to go! but before switching, there are some issues to fix, IMHO: - Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one) (copy/paste of another feedback that perfectly summarised a feeling I could not express better) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 11:12, Hervé BOUTEMY wrote: +0.5 I really like the graphics and general idea: that's for sure the way to go! but before switching, there are some issues to fix, IMHO: - Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one) (copy/paste of another feedback that perfectly summarised a feeling I could not express better) Heh, not really a technical argument ;-) But if people feel it's too dark, they are more than welcome to submit a patch for something lighter :) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) It's under the comdev banner, and as such, is available at https://svn.apache.org/repos/asf/comdev/projects.apache.org/ - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) All excellent points. If you check out the source, you can see that all doap files have been converted to JSON instead. As for CMS, I don't see any reason to use the CMS compared to just editing it in svn - it's 4-5 pages, each around 10 lines of html, not a 500+ page behemoth. - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? A delete feature would make sense, yes. As for what can be added, that's really up to the project, just as it was with the doap files. If you feel something in your project is a sub project in itself, you can add it. - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? DOAP will be replaced by the online editing. We haven't contacted projects about this yet, but on the other hand, I don't think we'd just change the DNS without letting folks know what we were doing. It's only been in testing so far. Once it was on the path to becoming something more official, surely projects would be included more. But it also requires people other than me to chip in - I only have so many hands and feet :) With regards, Daniel. Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
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
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
On Sun, Mar 8, 2015 at 3:08 PM, David Nalley da...@gnsa.us 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. How is it different if a person is considered a bonafide member of the community but his contributions are not code? Why that person can't have a similar title? Thanks, Roman.
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
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. --David
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
On Sun, Mar 8, 2015 at 3:42 PM, Ross Gardler (MS OPEN TECH)
ross.gard...@microsoft.com wrote:
Also note, a linked in profile or resume is about the individual. It's not an
official job title.
Then re-read my original reply.
Now we're just debating semantics. Seriously -- what do you think
'official job tile' is these days? It is whatever you and your boss agree
you can have on your public profile in such a way that it is beneficial
to the company and employee at the same time.
It most definitely NOT whatever that field happens to be in your corporate
HR database ('cuz in places like IBM it would be something like MTS VPS SPS
and who would want that to be on anything public?).
Thanks,
Roman.
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
Given what Joe said is exactly what I said I really object to this confrontational approach. To your specific question, if someone is speaking *for* a project then they can only do so with the permission of the project (being a PMC member or committer does not automatically bestow that authority). if someone is speaking for their employer (or anyone other than the project) then they can use any title the PMC has awarded them as long as it conforms to the ASF trademark rules. That's just a repeat of what I said in my first mail. Sent from Windows Mail From: Roman Shaposhnikmailto:ro...@shaposhnik.org Sent: ?Sunday?, ?March? ?8?, ?2015 ?5?:?33? ?PM To: ComDevmailto:dev@community.apache.org Last reply on this thread for today ;-) On Sun, Mar 8, 2015 at 4:09 PM, Joe Brockmeier j...@zonker.net wrote: On Sun, Mar 8, 2015, at 05:09 PM, Roman Shaposhnik wrote: As a title provided by a company, I would be against any title that incorporates the name of an Apache project. Red Hat, for instance, can employ (and grant the title) the Fedora Project Leader and Novell can employ the openSUSE Community Manager, but none of the companies are entitled to give a title related to any Apache project. Now I think we're really getting somewhere: it seems to be that some confusion (definitely mine at least) stems from the fact of of who can actually grant that title. The example of I gave with Brett -- clearly the ASF community was the one bestowing that title. Now, quite contrary to the semantics game that Ross was playing with 'what is an official title anyway?' -- I'd say that at that point it becomes one of Brett's official titles. Which means that even if there's a *corporate* announcement of him doing an event he can be billed as: Bret, Developer at Apache Maven Can we agree on that? Thanks, Roman.
RE: What's the ideal job title for somebody who is payed to help ASF communities grow?
Exactly Sent from my Windows Phone From: David Nalleymailto:da...@gnsa.us Sent: 3/8/2015 3:10 PM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: What's the ideal job title for somebody who is payed to help ASF communities grow? 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. --David
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
On Sun, Mar 8, 2015, at 05:09 PM, Roman Shaposhnik wrote: a recent thread with one of the PMCs pointed out an issue that I've long wanted to solicit feedback for: what is the ideal job title for somebody who is payed to help ASF communities grow? Just as a reference, I think my title when I was with Citrix was something like open source cloud evangelist. I kind of grew to dislike evangelist and suggested advocate instead. As a title provided by a company, I would be against any title that incorporates the name of an Apache project. Red Hat, for instance, can employ (and grant the title) the Fedora Project Leader and Novell can employ the openSUSE Community Manager, but none of the companies are entitled to give a title related to any Apache project. I'd probably suggest something around a product or more general technology title (e.g., open source big data advocate or CloudPlatform Community evangelist). I've yet to come up with a satisfying title that seems appropriate for what I do. Especially one that conveys what I do succinctly when people outside the immediate community ask me what my job is... Best, jzb -- Joe Brockmeier j...@zonker.net Twitter: @jzb http://www.dissociatedpress.net/
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
Last reply on this thread for today ;-) On Sun, Mar 8, 2015 at 4:09 PM, Joe Brockmeier j...@zonker.net wrote: On Sun, Mar 8, 2015, at 05:09 PM, Roman Shaposhnik wrote: As a title provided by a company, I would be against any title that incorporates the name of an Apache project. Red Hat, for instance, can employ (and grant the title) the Fedora Project Leader and Novell can employ the openSUSE Community Manager, but none of the companies are entitled to give a title related to any Apache project. Now I think we're really getting somewhere: it seems to be that some confusion (definitely mine at least) stems from the fact of of who can actually grant that title. The example of I gave with Brett -- clearly the ASF community was the one bestowing that title. Now, quite contrary to the semantics game that Ross was playing with 'what is an official title anyway?' -- I'd say that at that point it becomes one of Brett's official titles. Which means that even if there's a *corporate* announcement of him doing an event he can be billed as: Bret, Developer at Apache Maven Can we agree on that? Thanks, Roman.
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
Once again, the ASF makes no distinction between code and other contributions. Sent from Windows Mail From: Roman Shaposhnikmailto:ro...@shaposhnik.org Sent: ?Sunday?, ?March? ?8?, ?2015 ?5?:?21? ?PM To: ComDevmailto:dev@community.apache.org On Sun, Mar 8, 2015 at 3:08 PM, David Nalley da...@gnsa.us 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. How is it different if a person is considered a bonafide member of the community but his contributions are not code? Why that person can't have a similar title? Thanks, Roman.
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
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 Thanks, Roman. P.S. Now, the reason I'm picking on Brett is that he'd be the toughest to accuse of not grokking the Apache Way ;-)
RE: What's the ideal job title for somebody who is payed to help ASF communities grow?
Also note, a linked in profile or resume is about the individual. It's not an official job title. Then re-read my original reply. Sent from my Windows Phone From: David Nalleymailto:da...@gnsa.us Sent: 3/8/2015 3:10 PM To: dev@community.apache.orgmailto:dev@community.apache.org Subject: Re: What's the ideal job title for somebody who is payed to help ASF communities grow? 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. --David
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
Ideally and aspirationally, that is true. Practically speaking, definitely not true. On Sun, Mar 8, 2015 at 6:28 PM, Ross Gardler (MS OPEN TECH) ross.gard...@microsoft.com wrote: Once again, the ASF makes no distinction between code and other contributions. Sent from Windows Mail From: Roman Shaposhnikmailto:ro...@shaposhnik.org Sent: ?Sunday?, ?March? ?8?, ?2015 ?5?:?21? ?PM To: ComDevmailto:dev@community.apache.org On Sun, Mar 8, 2015 at 3:08 PM, David Nalley da...@gnsa.us 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. How is it different if a person is considered a bonafide member of the community but his contributions are not code? Why that person can't have a similar title? Thanks, Roman.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le dimanche 8 mars 2015 11:28:22 Daniel Gruno a écrit : - Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one) (copy/paste of another feedback that perfectly summarised a feeling I could not express better) Heh, not really a technical argument ;-) But if people feel it's too dark, they are more than welcome to submit a patch for something lighter :) yes, I'll try :) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) It's under the comdev banner, and as such, is available at https://svn.apache.org/repos/asf/comdev/projects.apache.org/ great, I'll have a look - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) All excellent points. If you check out the source, you can see that all doap files have been converted to JSON instead. you mean that projects should not update DOAP files any more but these json files? I really missed the info (and this means we should perhaps move maven- doap-plugin to the Attic...) As for CMS, I don't see any reason to use the CMS compared to just editing it in svn - it's 4-5 pages, each around 10 lines of html, not a 500+ page behemoth. CMS has staging, no? And perhaps the site is tiny because there is no easy editing: chicken and egg. IMHO, this new site has great graphics, but it really requires more than graphics. And the CMS could be part of the solution to do that. - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? A delete feature would make sense, yes. As for what can be added, that's really up to the project, just as it was with the doap files. If you feel something in your project is a sub project in itself, you can add it. IIUC, the online editing just updates https://svn.apache.org/repos/asf/comdev/projects.apache.org/site/json/projects/ ? Then editing these files is the way to track changes, or do what the online editing doesn't have any feature to do? - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? DOAP will be replaced by the online editing. We haven't contacted projects about this yet, but on the other hand, I don't think we'd just change the DNS without letting folks know what we were doing. It's only been in testing so far. Once it was on the path to becoming something more official, surely projects would be included more. what is great with DOAP is that there is a schema: is there something equivalent with json? But it also requires people other than me to chip in - I only have so many hands and feet :) now that we know where the source code is, I hope people will involve. How do we send patches? To you in person? Regards, Hervé With regards, Daniel. Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-08 12:47, Hervé BOUTEMY wrote: Le dimanche 8 mars 2015 11:28:22 Daniel Gruno a écrit : - Whereas the old pages were basic, the new ones have kind of an unusual dark theme to them and look unpolished (vs. just plain as the old one) (copy/paste of another feedback that perfectly summarised a feeling I could not express better) Heh, not really a technical argument ;-) But if people feel it's too dark, they are more than welcome to submit a patch for something lighter :) yes, I'll try :) - can we have a link to source? how can we submit patches? how can we test for ourselves improvement ideas before submitting patches? This is really a good start, but IMHO, if we don't have community involved in updates, this new site will loose a great opportunity to have contributors (unless it is a choice to avoid contributors) It's under the comdev banner, and as such, is available at https://svn.apache.org/repos/asf/comdev/projects.apache.org/ great, I'll have a look - why doesn't this use the CMS for some classical pages? Should not some parts of the old site be added to the new graphic content? While graphics and generated content are great, I think that some handwritten content would be useful (to explain where data come from, for example, or what happened to DOAP, or how to contribute...) All excellent points. If you check out the source, you can see that all doap files have been converted to JSON instead. you mean that projects should not update DOAP files any more but these json files? I really missed the info (and this means we should perhaps move maven- doap-plugin to the Attic...) As for CMS, I don't see any reason to use the CMS compared to just editing it in svn - it's 4-5 pages, each around 10 lines of html, not a 500+ page behemoth. CMS has staging, no? And perhaps the site is tiny because there is no easy editing: chicken and egg. IMHO, this new site has great graphics, but it really requires more than graphics. And the CMS could be part of the solution to do that. I'm not sure the CMS would add anything but trouble to this, as the site is tied to svn two-way; It reads data but also commits it back to SVN when changes occur. Furthermore, I'm not sure the CMS would work for non-tlp sites...I've never tried that :) and it would still be restricted to comdev in any case. - the idea of online editing is great, but not knowing what happens behind the scene, I fear to add sub-projects: what sub-projects should be added? can sub- projects be removed if the addition gives unexpected result? A delete feature would make sense, yes. As for what can be added, that's really up to the project, just as it was with the doap files. If you feel something in your project is a sub project in itself, you can add it. IIUC, the online editing just updates https://svn.apache.org/repos/asf/comdev/projects.apache.org/site/json/projects/ ? Then editing these files is the way to track changes, or do what the online editing doesn't have any feature to do? When you edit a project's JSON file, it triggers an email to this list, detailing what was edited. There is also (now) a job on the machine that updates it in SVN. The svn goes both ways; You can update something online and it will be committed to svn, or you can edit the json object in svn directly and it will be checked out on the machine. - what should we do with DOAP? Did I miss some explanations on private@ or dev@ ML from a project I'm working on? DOAP will be replaced by the online editing. We haven't contacted projects about this yet, but on the other hand, I don't think we'd just change the DNS without letting folks know what we were doing. It's only been in testing so far. Once it was on the path to becoming something more official, surely projects would be included more. what is great with DOAP is that there is a schema: is there something equivalent with json? But it also requires people other than me to chip in - I only have so many hands and feet :) now that we know where the source code is, I hope people will involve. How do we send patches? To you in person? No, you send them to this ML :) This is a comdev project, not a Humbedooh project ;) Regards, Hervé With regards, Daniel. Please take this feedback as constructive feedback: I really like the new site, just need some little improvements to get out of beta and make a public release :) Regards, Hervé Le vendredi 6 mars 2015 11:52:35 Rich Bowen a écrit : I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. It now has all the functionality that projects.a.o has, and much more, and there's no reason to have two sites up. If you object to moving forward with this, please say so. [ ] +1, do it [ ] +0, whatevs [ ] -1, No (and say why, so we can address the problem) --Rich
Re: What's the ideal job title for somebody who is payed to help ASF communities grow?
On Sun, Mar 8, 2015 at 5:31 PM, Roman Shaposhnik ro...@shaposhnik.org wrote: The example of I gave with Brett -- clearly the ASF community was the one bestowing that title. Now, quite contrary to the semantics game that Ross was playing with 'what is an official title anyway?' -- I'd say that at that point it becomes one of Brett's official titles. Which means that even if there's a *corporate* announcement of him doing an event he can be billed as: Bret, Developer at Apache Maven Can we agree on that? To clarify what I am about to agree with: Titles bestowed by the community can be used by the individuals to reference themselves Titles bestowed by companies should not include Apache trademarks I agree with this and I think it is the same as what Roman said. The only problem is that our projects rarely acknowledge really strong advocates. For a specific instance, Ellen Friedman (note personal connection with me) was made a committer by Mahout for community development efforts while Drill has not recognized even more extensive efforts on their part. Any developer putting in a tenth as much time as she does would have long ago been made a committer and PMC member. But that means that she can't claim any official Drill status while promoting Drill (because she doesn't have any). One consequence is that people doing this sort of work get mightily discouraged.
first little patch for projects-new.apache.org
Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, HervéIndex: datatables.html === --- datatables.html (révision 1665047) +++ datatables.html (copie de travail) @@ -52,7 +52,7 @@ /noscript /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div /body Index: index.html === --- index.html (révision 1665047) +++ index.html (copie de travail) @@ -40,7 +40,7 @@ /noscript /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div script type=text/javascript Index: project.html === --- project.html (révision 1665047) +++ project.html (copie de travail) @@ -45,7 +45,7 @@ /noscript /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div /body Index: projects.html === --- projects.html (révision 1665047) +++ projects.html (copie de travail) @@ -50,7 +50,7 @@ /noscript /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div /body Index: releases.html === --- releases.html (révision 1665047) +++ releases.html (copie de travail) @@ -42,7 +42,7 @@ /noscript /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div Index: timelines.html === --- timelines.html (révision 1665047) +++ timelines.html (copie de travail) @@ -30,7 +30,7 @@ h1Timelines/h1 /div div id=footer - Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0br/ + Copyrightcopy; 2015, the Apache Software Foundation. Licensed under the a href=http://www.apache.org/licenses/LICENSE-2.0;Apache License, Version 2.0/abr/ For inquiries, contact a href=mailto:dev@community.apache.orgdev@community.apache.org/a. /div script type=text/javascript
Re: first little patch for projects-new.apache.org
another one, with simple instructions to make local tests Regards, Hervé Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, Hervé Index: STRUCTURE.txt === --- STRUCTURE.txt (révision 1664978) +++ STRUCTURE.txt (copie de travail) @@ -4,20 +4,20 @@ - Contains scripts used for import and maintenance of foundation-wide data, such as committer IDs/names, project VPs, founding dates, reporting cycles etc. - + /site: - Contains the HTML, images and javascript needed to run the site - + /site/json: - Contains the JSON data storage - + /site/json/foundation: - Contains foundation-wide JSON data (committers, chairs, podling evolution etc) - + /site/projects: - Contains project-specific base data. - + Suggested cron setup: scripts/cronjobs/parsechairs.py - daily scripts/cronjobs/parsecomitters.py - daily/hourly (whatever we need/want) @@ -28,4 +28,8 @@ scripts/import/parsecommittees.py - requires committee-info.txt to be present scripts/import/addpmc.py - manual run whenever a new PMC is founded - \ No newline at end of file +Webserver required: +To test the site locally, a webserver is required or you'll get +Cross origin requests are only supported for HTTP errors. +An easy setup is: run python -m SimpleHTTPServer from site directory +to have site available at http://localhost:/
Re: first little patch for projects-new.apache.org
and a third one: just white background instead of black
Regards,
Hervé
Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit :
another one, with simple instructions to make local tests
Regards,
Hervé
Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit :
Hi,
As promise, here is a first little patch: this is simply to add a link to
our license, per our policy :)
Regards,
Hervé
Index: styles.css
===
--- styles.css (révision 1665047)
+++ styles.css (copie de travail)
@@ -105,7 +105,7 @@
}
body {
font: 15px/1.5 Helvetica, Arial, 'Liberation Sans', FreeSans, sans-serif;
-background-color: #666;
+background-color: #fff;
}
.leftbar {
@@ -194,7 +194,6 @@
}
#footer {
- color: #DDD;
font-style: italic;
font-size: small;
text-align: center;
Re: first little patch for projects-new.apache.org
next: avoid copy paste for TLP vs sub-project icon and put the icon on the
left to have full alignment
Regards,
Hervé
Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit :
and a third one: just white background instead of black
Regards,
Hervé
Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit :
another one, with simple instructions to make local tests
Regards,
Hervé
Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit :
Hi,
As promise, here is a first little patch: this is simply to add a link
to
our license, per our policy :)
Regards,
Hervé
Index: js/projects.js
===
--- js/projects.js (révision 1665047)
+++ js/projects.js (copie de travail)
@@ -475,6 +475,14 @@
return str.replace(/^([a-z])(.+)$/, function(c,a,b) { return a.toUpperCase() + b.toLowerCase() } );
}
+function projectIcon(name) {
+if (isTLP(name)) {
+ return img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
+} else {
+ return img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
+}
+}
+
function renderProjectsList(cat) {
var obj = document.getElementById('contents');
@@ -502,12 +510,7 @@
for (i in arr) {
project = arr[i]
var li = document.createElement('li');
- li.innerHTML = a href='/project.html? + project + ' + projects[project].name + /a;
- if (isTLP(projects[project].name)) {
- li.innerHTML += img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
- } else {
- li.innerHTML += img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
- }
+ li.innerHTML = projectIcon(projects[project].name) + a href='/project.html? + project + ' + projects[project].name + /a;
ul.appendChild(li)
}
obj.appendChild(ul);
@@ -551,12 +554,7 @@
for (x in a) {
if (a[x].toLowerCase() == lang.toLowerCase()) {
var cli = document.createElement('li');
- cli.innerHTML = a href='/project.html? + i + ' + projects[i].name + /a;
- if (isTLP(projects[i].name)) {
-cli.innerHTML += img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
- } else {
-cli.innerHTML += img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
- }
+ cli.innerHTML = projectIcon(projects[i].name) + a href='/project.html? + i + ' + projects[i].name + /a;
cul.appendChild(cli)
}
}
@@ -609,12 +607,7 @@
a[x] = a[x].replace(http://projects.apache.org/category/;, ).toLowerCase();
if (a[x] == lang) {
var cli = document.createElement('li');
- cli.innerHTML = a href='/project.html? + i + ' + projects[i].name + /a;
- if (isTLP(projects[i].name)) {
-cli.innerHTML += img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
- } else {
-cli.innerHTML += img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
- }
+ cli.innerHTML = projectIcon(projects[i].name) + a href='/project.html? + i + ' + projects[i].name + /a;
cul.appendChild(cli)
}
}
@@ -662,12 +655,7 @@
xdate = committees[projects[i].name]
if (xdate == date) {
var cli = document.createElement('li');
- cli.innerHTML = a href='/project.html? + i + ' + projects[i].name + /a;
- if (isTLP(projects[i].name)) {
- cli.innerHTML += img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
- } else {
- cli.innerHTML += img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
- }
+ cli.innerHTML = projectIcon(projects[i].name) + a href='/project.html? + i + ' + projects[i].name + /a;
cul.appendChild(cli)
}
}
@@ -712,12 +700,7 @@
var cli = document.createElement('li');
cli.innerHTML = a href='/project.html? + i + ' + projects[i].name + /a: + len + committers;
if (unixgroups[i+'-pmc']) {
- cli.innerHTML += , + unixgroups[i+'-pmc'].length + PMC members;
- if (isTLP(projects[i].name)) {
-cli.innerHTML += img src='/images/tlp.png' title='Top Level Project' style='vertical-align: middle; padding: 2px;'/
- } else {
-cli.innerHTML += img src='/images/sub.png' title='Sub-project' style='vertical-align: middle; padding: 2px;'/
- }
+ cli.innerHTML = projectIcon(projects[i].name) + cli.innerHTML + , + unixgroups[i+'-pmc'].length + PMC members;
}
ul.appendChild(cli)
}
@@ -771,12 +754,7 @@
xlpmc = projects[i].pmc
if (xlpmc == lpmc) {
var cli = document.createElement('li');
- cli.innerHTML = a href='/project.html? + i + ' + projects[i].name + /a;
- if (isTLP(projects[i].name)) {
-
Re: first little patch for projects-new.apache.org
IMHO, icons for incubating and Attic projects should be different than standard sub-project (no idea about rendering of such icons) Regards, Hervé Le dimanche 8 mars 2015 17:56:52 Hervé BOUTEMY a écrit : next: avoid copy paste for TLP vs sub-project icon and put the icon on the left to have full alignment Regards, Hervé Le dimanche 8 mars 2015 17:43:49 Hervé BOUTEMY a écrit : and a third one: just white background instead of black Regards, Hervé Le dimanche 8 mars 2015 17:29:56 Hervé BOUTEMY a écrit : another one, with simple instructions to make local tests Regards, Hervé Le dimanche 8 mars 2015 17:23:36 Hervé BOUTEMY a écrit : Hi, As promise, here is a first little patch: this is simply to add a link to our license, per our policy :) Regards, Hervé
