Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Kinda strange that none of this involves site-dev@ which was the genesis of the original site. Sent from my iPhone > On Mar 13, 2015, at 3:44 AM, Daniel Gruno wrote: > > > If someone other than me could apply those patches, that'd sure be swell. > This is (the future) projects.apache.org, not humbedooh.apache.org :( > > > As for keeping the old site around for a while, I suppose that's an option, > just don't expect infra to maintain it if it keels over ;) > With regards, > Daniel. > >> On 2015-03-13 08:40, Hervé BOUTEMY wrote: >> ping? >> >> Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : >>> Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : On 03/06/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) I'm going to call this a "yes" vote overall, with a few nits >>> +1 >>> >>> one more thing: when we switch projects-new to projects, it would be useful >>> to have old projects switched to projects-old, since there are still parts >>> that are useful or to be integrated to the new site (see Feeds, DOAP Files >>> and Documentation sections) >>> that have been addressed. >>> -1 I sent patches but they were not applied >>> Thank you all for your thoughts. Thanks, Daniel, for your work on this. And with all the folks that have said they'll get checkouts and hack on it, we should have much wonderment real soon. >>> Can I get commit access (without being PMC member)? >>> >>> I'd like to add an "about" folder equivalent to >>> https://projects.apache.org/references.html, and with a reference to >>> http://people.apache.org/committers-by-project.html#comdev >>> >>> Notice: shouldn't comdev be added to projects-new as 6th "special >>> committee"? >>> >>> Regards, >>> >>> Hervé >>> --Rich >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le vendredi 13 mars 2015 08:44:05 Daniel Gruno a écrit : > > If someone other than me could apply those patches, that'd sure be swell. > This is (the future) projects.apache.org, not humbedooh.apache.org :( > +1 that's why I proposed to even join (and not only stay outside) > > As for keeping the old site around for a while, I suppose that's an > option, just don't expect infra to maintain it if it keels over ;) how is it related to infra? I supposed projects-new was like projects, ie a comdev site, with comdev community? if that's not the casae, I understand now that the change from projects to projects-new is also a switch from infra responsibility to comdev = an organisational change, not only technical Perhaps the organisational part wasn't expected. Regards, Hervé > With regards, > Daniel. > > On 2015-03-13 08:40, Hervé BOUTEMY wrote: > > ping? > > > > Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : > >> Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > >>> On 03/06/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) > >>> > >>> I'm going to call this a "yes" vote overall, with a few nits > >> > >> +1 > >> > >> one more thing: when we switch projects-new to projects, it would be > >> useful > >> to have old projects switched to projects-old, since there are still > >> parts > >> that are useful or to be integrated to the new site (see Feeds, DOAP > >> Files > >> and Documentation sections) > >> > >>> that have been addressed. > >> > >> -1 I sent patches but they were not applied > >> > >>> Thank you all for your thoughts. Thanks, Daniel, for > >>> your work on this. And with all the folks that have said they'll get > >>> checkouts and hack on it, we should have much wonderment real soon. > >> > >> Can I get commit access (without being PMC member)? > >> > >> I'd like to add an "about" folder equivalent to > >> https://projects.apache.org/references.html, and with a reference to > >> http://people.apache.org/committers-by-project.html#comdev > >> > >> Notice: shouldn't comdev be added to projects-new as 6th "special > >> committee"? > >> > >> Regards, > >> > >> Hervé > >> > >>> --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
If someone other than me could apply those patches, that'd sure be swell. This is (the future) projects.apache.org, not humbedooh.apache.org :( As for keeping the old site around for a while, I suppose that's an option, just don't expect infra to maintain it if it keels over ;) With regards, Daniel. On 2015-03-13 08:40, Hervé BOUTEMY wrote: ping? Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : On 03/06/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) I'm going to call this a "yes" vote overall, with a few nits +1 one more thing: when we switch projects-new to projects, it would be useful to have old projects switched to projects-old, since there are still parts that are useful or to be integrated to the new site (see Feeds, DOAP Files and Documentation sections) that have been addressed. -1 I sent patches but they were not applied Thank you all for your thoughts. Thanks, Daniel, for your work on this. And with all the folks that have said they'll get checkouts and hack on it, we should have much wonderment real soon. Can I get commit access (without being PMC member)? I'd like to add an "about" folder equivalent to https://projects.apache.org/references.html, and with a reference to http://people.apache.org/committers-by-project.html#comdev Notice: shouldn't comdev be added to projects-new as 6th "special committee"? Regards, Hervé --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
ping? Le mercredi 11 mars 2015 08:49:23 Hervé BOUTEMY a écrit : > Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > > On 03/06/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) > > > > I'm going to call this a "yes" vote overall, with a few nits > > +1 > > one more thing: when we switch projects-new to projects, it would be useful > to have old projects switched to projects-old, since there are still parts > that are useful or to be integrated to the new site (see Feeds, DOAP Files > and Documentation sections) > > > that have been addressed. > > -1 I sent patches but they were not applied > > > Thank you all for your thoughts. Thanks, Daniel, for > > your work on this. And with all the folks that have said they'll get > > checkouts and hack on it, we should have much wonderment real soon. > > Can I get commit access (without being PMC member)? > > I'd like to add an "about" folder equivalent to > https://projects.apache.org/references.html, and with a reference to > http://people.apache.org/committers-by-project.html#comdev > > Notice: shouldn't comdev be added to projects-new as 6th "special > committee"? > > Regards, > > Hervé > > > --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le mardi 10 mars 2015 13:32:26 Rich Bowen a écrit : > On 03/06/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) > > I'm going to call this a "yes" vote overall, with a few nits +1 one more thing: when we switch projects-new to projects, it would be useful to have old projects switched to projects-old, since there are still parts that are useful or to be integrated to the new site (see Feeds, DOAP Files and Documentation sections) > that have been addressed. -1 I sent patches but they were not applied > Thank you all for your thoughts. Thanks, Daniel, for > your work on this. And with all the folks that have said they'll get > checkouts and hack on it, we should have much wonderment real soon. Can I get commit access (without being PMC member)? I'd like to add an "about" folder equivalent to https://projects.apache.org/references.html, and with a reference to http://people.apache.org/committers-by-project.html#comdev Notice: shouldn't comdev be added to projects-new as 6th "special committee"? Regards, Hervé > > --Rich
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 03/06/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) I'm going to call this a "yes" vote overall, with a few nits that have been addressed. Thank you all for your thoughts. Thanks, Daniel, for your work on this. And with all the folks that have said they'll get checkouts and hack on it, we should have much wonderment real soon. --Rich -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
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 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 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: [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 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 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: [VOTE] Replace projects.apache.org with projects-new.apache.org
Le dimanche 8 mars 2015 13:13:32 Daniel Gruno a écrit : > > 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. only the edit has such effect, and on some data, not on the site itself I'm sure using CMS would help make this site a normal site > Furthermore, I'm not sure the CMS would work for > non-tlp sites...I've never tried that :) Maven has Doxia site which is a sub-site, non-TLP > and it would still be > restricted to comdev in any case. yes, comdev is a TLP like any other: should use CMS, since once again the site should not only have calculated graphics: it should have plain text too, with editorial content > > >>> - 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/proj > > ects/ ? > > 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. ok, svnpubsub and svn commit list: really classical > > >>> - 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 ;) ok, I'll try tonight with some really simple changes before trying more complex work Regards, Hervé
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: [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
El vie., 6 de marzo de 2015 a las 23:40, Daniel Gruno () escribió: > > > On 2015-03-06 23:39, Christopher wrote: > > On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru > (...) > >> Similarly, are we still using DOAP files? I could imagine that there > >> are others who were also referring to individual DOAPs or to the > >> projects.a.o/feeds content. > >> > >> These may not be widely used features, but if we're nuking them we > >> should be explicit about that and provide some notice about them being > >> gone. > >> > >> > > +1; it'd be nice to know that we don't have to update them anymore, if > > that's the case. > You don't, you update everything through the site ( currently at > https://projects-new.apache.org/edit ). > > Is there a reasonable audit trail of changes? Before now, the svn log of the DOAP files was effectively an audit trail. Does the project-new system provide something reasonably similar? Regards Santiago > With regards, > Daniel. > >
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: [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
+1 Antoine On Mar 6, 2015, at 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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 03/06/2015 06:08 PM, Shane Curcuru wrote: This is really cool stuff, but I want to make sure that our 160++ projects actually understand what's going on (and will take the responsibility to keep their own info updated here), and that various outsiders who come to the site to find our projects get the information they need. we've told them several times. I recognize that's not the same as "projects actually understand". -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
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 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: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-07 05:20, Pei Chen wrote: This is pretty cool. Just curious- are the *.json automagically updated via a script of some sort? eg https://projects-new.apache.org/json/foundation/people.json We were thinking of reusing the data to pull that and populate our own people.html page dynamically via jQuery. Yeah, that's all updated automatically these days. With regards, Daniel. On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: +1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org Minor design nit: the content boxes should either be centered or do a better job of auto filling the available horizontal space. Otherwise, it looks spiffy, despite being fairly tiny on my monitor. Would also like to see the releases page sort by date by default, and show more than 10 entries. This is not a reason to block the switch though. +0.9 in current state, +1 once my comments are addressed. On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: I'd like for us to go ahead and replace projects.apache.org with projects-new.apache.org. -0, do we need all these js/css/cookies from google(apis)? I never had to disable noscript for anything than a.o on a.o until then, whitelisting *.gg.c annoys me a bit...
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Thanks for your work, much more better now! :-) # web: http://www.jgeppert.com twitter: http://twitter.com/jogep 2015-03-07 5:20 GMT+01:00 Pei Chen : > This is pretty cool. > Just curious- are the *.json automagically updated via a script of some > sort? > eg https://projects-new.apache.org/json/foundation/people.json > We were thinking of reusing the data to pull that and populate our own > people.html page dynamically via jQuery. > > > On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < > chris.a.mattm...@jpl.nasa.gov> wrote: > > > +1 please do so :) > > > > ++ > > Chris Mattmann, Ph.D. > > Chief Architect > > Instrument Software and Science Data Systems Section (398) > > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > > Office: 168-519, Mailstop: 168-527 > > Email: chris.a.mattm...@nasa.gov > > WWW: http://sunset.usc.edu/~mattmann/ > > ++ > > Adjunct Associate Professor, Computer Science Department > > University of Southern California, Los Angeles, CA 90089 USA > > ++ > > > > > > > > > > > > > > -Original Message----- > > From: Mike Drob > > Reply-To: "dev@community.apache.org" > > Date: Friday, March 6, 2015 at 12:50 PM > > To: "dev@community.apache.org" > > Subject: Re: [VOTE] Replace projects.apache.org with > > projects-new.apache.org > > > > >Minor design nit: the content boxes should either be centered or do a > > >better job of auto filling the available horizontal space. Otherwise, it > > >looks spiffy, despite being fairly tiny on my monitor. > > > > > >Would also like to see the releases page sort by date by default, and > show > > >more than 10 entries. This is not a reason to block the switch though. > > > > > >+0.9 in current state, +1 once my comments are addressed. > > > > > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic > wrote: > > > > > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > > >> > I'd like for us to go ahead and replace projects.apache.org with > > >> > projects-new.apache.org. > > >> > > >> -0, do we need all these js/css/cookies from google(apis)? > > >> I never had to disable noscript for anything than a.o on a.o until > > >> then, whitelisting *.gg.c annoys me a bit... > > >> > > > > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
This is pretty cool. Just curious- are the *.json automagically updated via a script of some sort? eg https://projects-new.apache.org/json/foundation/people.json We were thinking of reusing the data to pull that and populate our own people.html page dynamically via jQuery. On Fri, Mar 6, 2015 at 10:43 PM, Mattmann, Chris A (3980) < chris.a.mattm...@jpl.nasa.gov> wrote: > +1 please do so :) > > ++ > Chris Mattmann, Ph.D. > Chief Architect > Instrument Software and Science Data Systems Section (398) > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 168-519, Mailstop: 168-527 > Email: chris.a.mattm...@nasa.gov > WWW: http://sunset.usc.edu/~mattmann/ > ++ > Adjunct Associate Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++ > > > > > > > -Original Message- > From: Mike Drob > Reply-To: "dev@community.apache.org" > Date: Friday, March 6, 2015 at 12:50 PM > To: "dev@community.apache.org" > Subject: Re: [VOTE] Replace projects.apache.org with > projects-new.apache.org > > >Minor design nit: the content boxes should either be centered or do a > >better job of auto filling the available horizontal space. Otherwise, it > >looks spiffy, despite being fairly tiny on my monitor. > > > >Would also like to see the releases page sort by date by default, and show > >more than 10 entries. This is not a reason to block the switch though. > > > >+0.9 in current state, +1 once my comments are addressed. > > > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > > > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > >> > I'd like for us to go ahead and replace projects.apache.org with > >> > projects-new.apache.org. > >> > >> -0, do we need all these js/css/cookies from google(apis)? > >> I never had to disable noscript for anything than a.o on a.o until > >> then, whitelisting *.gg.c annoys me a bit... > >> > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
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 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: [VOTE] Replace projects.apache.org with projects-new.apache.org
LGTM, but don't forget to update the www.apache.org homepageto base it on the new stuff instead of the DOAP files. On Friday, March 6, 2015 10:47 PM, "Mattmann, Chris A (3980)" wrote: +1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org >Minor design nit: the content boxes should either be centered or do a >better job of auto filling the available horizontal space. Otherwise, it >looks spiffy, despite being fairly tiny on my monitor. > >Would also like to see the releases page sort by date by default, and show >more than 10 entries. This is not a reason to block the switch though. > >+0.9 in current state, +1 once my comments are addressed. > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: >> > I'd like for us to go ahead and replace projects.apache.org with >> > projects-new.apache.org. >> >> -0, do we need all these js/css/cookies from google(apis)? >> I never had to disable noscript for anything than a.o on a.o until >> then, whitelisting *.gg.c annoys me a bit... >>
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 please do so :) ++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Mike Drob Reply-To: "dev@community.apache.org" Date: Friday, March 6, 2015 at 12:50 PM To: "dev@community.apache.org" Subject: Re: [VOTE] Replace projects.apache.org with projects-new.apache.org >Minor design nit: the content boxes should either be centered or do a >better job of auto filling the available horizontal space. Otherwise, it >looks spiffy, despite being fairly tiny on my monitor. > >Would also like to see the releases page sort by date by default, and show >more than 10 entries. This is not a reason to block the switch though. > >+0.9 in current state, +1 once my comments are addressed. > >On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > >> On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: >> > I'd like for us to go ahead and replace projects.apache.org with >> > projects-new.apache.org. >> >> -0, do we need all these js/css/cookies from google(apis)? >> I never had to disable noscript for anything than a.o on a.o until >> then, whitelisting *.gg.c annoys me a bit... >>
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 3/6/15 5:40 PM, Daniel Gruno wrote: > > > On 2015-03-06 23:39, Christopher wrote: >> On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru >> wrote: >> >>> Question: is there any plan to redirect old URLs? >>> >>> The old projects.a.o certainly is clunky, but there may well be a few >>> people who have linked to various parts of the site. >>> >>> Similarly, are we still using DOAP files? I could imagine that there >>> are others who were also referring to individual DOAPs or to the >>> projects.a.o/feeds content. >>> >>> These may not be widely used features, but if we're nuking them we >>> should be explicit about that and provide some notice about them being >>> gone. >>> >>> >> +1; it'd be nice to know that we don't have to update them anymore, if >> that's the case. > You don't, you update everything through the site ( currently at > https://projects-new.apache.org/edit ). Ah, so this means DOAP files are essentially deprecated, correct? Have we documented how PMCs are supposed to update their project's details, and communicated to pmcs@ the expectation that they must now keep this stuff updated instead of the DOAP files? This is really cool stuff, but I want to make sure that our 160++ projects actually understand what's going on (and will take the responsibility to keep their own info updated here), and that various outsiders who come to the site to find our projects get the information they need. - Shane > > With regards, > Daniel. >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On 2015-03-06 23:39, Christopher wrote: On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru wrote: Question: is there any plan to redirect old URLs? The old projects.a.o certainly is clunky, but there may well be a few people who have linked to various parts of the site. Similarly, are we still using DOAP files? I could imagine that there are others who were also referring to individual DOAPs or to the projects.a.o/feeds content. These may not be widely used features, but if we're nuking them we should be explicit about that and provide some notice about them being gone. +1; it'd be nice to know that we don't have to update them anymore, if that's the case. You don't, you update everything through the site ( currently at https://projects-new.apache.org/edit ). With regards, Daniel.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 5:35 PM, Shane Curcuru wrote: > Question: is there any plan to redirect old URLs? > > The old projects.a.o certainly is clunky, but there may well be a few > people who have linked to various parts of the site. > > Similarly, are we still using DOAP files? I could imagine that there > are others who were also referring to individual DOAPs or to the > projects.a.o/feeds content. > > These may not be widely used features, but if we're nuking them we > should be explicit about that and provide some notice about them being > gone. > > +1; it'd be nice to know that we don't have to update them anymore, if that's the case.
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Question: is there any plan to redirect old URLs? The old projects.a.o certainly is clunky, but there may well be a few people who have linked to various parts of the site. Similarly, are we still using DOAP files? I could imagine that there are others who were also referring to individual DOAPs or to the projects.a.o/feeds content. These may not be widely used features, but if we're nuking them we should be explicit about that and provide some notice about them being gone. - Shane P.S. There's some perspective for you on the Releases tab... 5306 software product releases (and those are just ones that the scripts can detect). On 3/6/15 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: [VOTE] Replace projects.apache.org with projects-new.apache.org
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: [VOTE] Replace projects.apache.org with projects-new.apache.org
Just happened to notice that the new website's header seems to be truncated on mobile. I use Chrome on Android.. http://imgur.com/8gZfu0i On 6 Mar 2015 16:53, "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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Minor design nit: the content boxes should either be centered or do a better job of auto filling the available horizontal space. Otherwise, it looks spiffy, despite being fairly tiny on my monitor. Would also like to see the releases page sort by date by default, and show more than 10 entries. This is not a reason to block the switch though. +0.9 in current state, +1 once my comments are addressed. On Fri, Mar 6, 2015 at 2:29 PM, Yann Ylavic wrote: > On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > > I'd like for us to go ahead and replace projects.apache.org with > > projects-new.apache.org. > > -0, do we need all these js/css/cookies from google(apis)? > I never had to disable noscript for anything than a.o on a.o until > then, whitelisting *.gg.c annoys me a bit... >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org. -0, do we need all these js/css/cookies from google(apis)? I never had to disable noscript for anything than a.o on a.o until then, whitelisting *.gg.c annoys me a bit...
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
On Fri, Mar 6, 2015 at 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) -0, index on new site took in excess of 20 seconds to load for me in chrome. About 10 seconds trying again in firefox. 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)
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 6 Mar 2015 17:53, "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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 2015-03-06 17:52, 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: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1, with two comments: 1. the projects page on the new site has a link to "Contributors", which is broken. 2. there's some information linked on the old site about DOAP files and RSS/Atom feeds, which do not exist (or are not obvious) on the new site. -- Christopher L Tubbs II http://gravatar.com/ctubbsii On Fri, Mar 6, 2015 at 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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/ >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Jacques Le 06/03/2015 17:52, 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 Fri, Mar 6, 2015 at 5:52 PM, Rich Bowen wrote: > I'd like for us to go ahead and replace projects.apache.org with > projects-new.apache.org +1 -Bertrand
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
Yes please! > On Mar 6, 2015, at 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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 06/03/15 17:52, 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 -- Sergio Fernández Partner Technology Manager Redlink GmbH m: +43 660 2747 925 e: sergio.fernan...@redlink.co w: http://redlink.co
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Hadrian On 03/06/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: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 On 6 March 2015 at 17:57, Daniel Gruno wrote: > +1 but clearly biased ;-) > > > On 2015-03-06 17:54, Ross Gardler (MS OPEN TECH) wrote: > >> +1 >> >> Microsoft Open Technologies, Inc. >> A subsidiary of Microsoft Corporation >> >> -Original Message- >> From: Rich Bowen [mailto:rbo...@redhat.com] >> Sent: Friday, March 6, 2015 8:53 AM >> To: dev >> Subject: [VOTE] Replace projects.apache.org with projects-new.apache.org >> >> 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 >> >> -- >> Rich Bowen - rbo...@redhat.com >> OpenStack Community Liaison >> http://rdoproject.org/ >> > >
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+ 1. Suresh > On Mar 6, 2015, at 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 > > -- > Rich Bowen - rbo...@redhat.com > OpenStack Community Liaison > http://rdoproject.org/
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
One of your mentors or the champion will have to do the edits for now. We can always relax this to include committers, but for incubator that would equal universal commit bit on this as well. But I think that is not for this thread :) With regards, Daniel. On 2015-03-06 18:14, Stian Soiland-Reyes wrote: +1 - looks great! ..Apologies if this was explained before I joined this list - How does this work for podlings? For the old site I was able to make a DOAP file, but on the Apache Taverna entry on projects-new I am unable to edit it as I am not in the Incubator PMC. Can we still maintain the old doap file? Those instructions are on http://projects.apache.org/doap.html and perhaps would need to be moved over in some form. On 6 March 2015 at 16:57, Daniel Gruno wrote: +1 but clearly biased ;-) On 2015-03-06 17:54, Ross Gardler (MS OPEN TECH) wrote: +1 Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: Rich Bowen [mailto:rbo...@redhat.com] Sent: Friday, March 6, 2015 8:53 AM To: dev Subject: [VOTE] Replace projects.apache.org with projects-new.apache.org 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 -- Rich Bowen - rbo...@redhat.com OpenStack Community Liaison http://rdoproject.org/
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 - looks great! ..Apologies if this was explained before I joined this list - How does this work for podlings? For the old site I was able to make a DOAP file, but on the Apache Taverna entry on projects-new I am unable to edit it as I am not in the Incubator PMC. Can we still maintain the old doap file? Those instructions are on http://projects.apache.org/doap.html and perhaps would need to be moved over in some form. On 6 March 2015 at 16:57, Daniel Gruno wrote: > +1 but clearly biased ;-) > > > On 2015-03-06 17:54, Ross Gardler (MS OPEN TECH) wrote: >> >> +1 >> >> Microsoft Open Technologies, Inc. >> A subsidiary of Microsoft Corporation >> >> -Original Message- >> From: Rich Bowen [mailto:rbo...@redhat.com] >> Sent: Friday, March 6, 2015 8:53 AM >> To: dev >> Subject: [VOTE] Replace projects.apache.org with projects-new.apache.org >> >> 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 >> >> -- >> Rich Bowen - rbo...@redhat.com >> OpenStack Community Liaison >> http://rdoproject.org/ > > -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/-0001-9842-9718
Re: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 but clearly biased ;-) On 2015-03-06 17:54, Ross Gardler (MS OPEN TECH) wrote: +1 Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: Rich Bowen [mailto:rbo...@redhat.com] Sent: Friday, March 6, 2015 8:53 AM To: dev Subject: [VOTE] Replace projects.apache.org with projects-new.apache.org 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 -- Rich Bowen - rbo...@redhat.com OpenStack Community Liaison http://rdoproject.org/
RE: [VOTE] Replace projects.apache.org with projects-new.apache.org
+1 Microsoft Open Technologies, Inc. A subsidiary of Microsoft Corporation -Original Message- From: Rich Bowen [mailto:rbo...@redhat.com] Sent: Friday, March 6, 2015 8:53 AM To: dev Subject: [VOTE] Replace projects.apache.org with projects-new.apache.org 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 -- Rich Bowen - rbo...@redhat.com OpenStack Community Liaison http://rdoproject.org/
[VOTE] Replace projects.apache.org with projects-new.apache.org
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 -- Rich Bowen - rbo...@redhat.com OpenStack Community Liaison http://rdoproject.org/
