Re: projects-new.apache.org
I had a look at Forrest doap file[1]: it's not a doap file, it's a feed containing a doap entry you should IMHO simplify it to match a simple doap file, like [2], for example Regards, Hervé [1] http://forrest.apache.org/doap.xml [2] http://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf Le lundi 13 avril 2015 04:58:05 Hervé BOUTEMY a écrit : > if you run parserdf.py, you'll see that forrest is one of the few rdf that > makes the script choke: > > Error when reading None's doap file http://forrest.apache.org/doap.xml: > > Traceback (most recent call last): > File "rdfparse.py", line 59, in > if pjson['homepage']: > KeyError: 'homepage' > > > > I still didn't have time to investigate this one, and report (did it for > lucy and uima: opened Jira issues on each project) > > Regards, > > Hervé > > Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > > Apache Forrest is also missing from projects-new.a.o > > but was one of the early adopters at projects.a.o > > > > I cannot determine why. Would someone else please try. > > > > -David > > > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > > I finally found time to investigate: > > > > > > this is because ofbiz is not in pmcs reference list [1] used by the site > > > to > > > create pmcs.json [2] > > > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > > > Regards, > > > > > > Hervé > > > > > > > > > [1] > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > s > > > /data_files/ > > > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > > > [3] > > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/project > > > s > > > /data_files/aareadme.txt > > > > > > [4] http://projects.apache.org/create.html#submit > > > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > > overview. > > > > > > > > Best regards, > > > > > > > > Pierre Smits
Re: projects-new.apache.org
if you run parserdf.py, you'll see that forrest is one of the few rdf that makes the script choke: Error when reading None's doap file http://forrest.apache.org/doap.xml: Traceback (most recent call last): File "rdfparse.py", line 59, in if pjson['homepage']: KeyError: 'homepage' I still didn't have time to investigate this one, and report (did it for lucy and uima: opened Jira issues on each project) Regards, Hervé Le lundi 13 avril 2015 12:32:49 David Crossley a écrit : > Apache Forrest is also missing from projects-new.a.o > but was one of the early adopters at projects.a.o > > I cannot determine why. Would someone else please try. > > -David > > On Sun, Apr 12, 2015 at 07:27:18PM +0200, Hervé BOUTEMY wrote: > > I finally found time to investigate: > > > > this is because ofbiz is not in pmcs reference list [1] used by the site > > to > > create pmcs.json [2] > > > > it seems one step was missed during OFBiz TLP creation [3] > > > > As PMC Chair and/or member, you should be able to fix it [4] > > > > Once done, just tell and I'll regenerate the pmcs.json file > > > > Regards, > > > > Hervé > > > > > > [1] > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects > > /data_files/ > > > > [2] https://projects-new.apache.org/json/foundation/pmcs.json > > > > [3] > > https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects > > /data_files/aareadme.txt > > > > [4] http://projects.apache.org/create.html#submit > > > > Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > > > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' > > > overview. > > > > > > Best regards, > > > > > > Pierre Smits
Re: projects-new.apache.org
I finally found time to investigate: this is because ofbiz is not in pmcs reference list [1] used by the site to create pmcs.json [2] it seems one step was missed during OFBiz TLP creation [3] As PMC Chair and/or member, you should be able to fix it [4] Once done, just tell and I'll regenerate the pmcs.json file Regards, Hervé [1] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/ [2] https://projects-new.apache.org/json/foundation/pmcs.json [3] https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/data_files/aareadme.txt [4] http://projects.apache.org/create.html#submit Le lundi 30 mars 2015 08:54:46 Pierre Smits a écrit : > Hi. I don't see Apache OFBiz when looking at the 'Projects by PMC' overview. > > Best regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Mon, Mar 30, 2015 at 8:23 AM, Hervé BOUTEMY > > wrote: > > Now that every committer has commit privs, I continued my improvements > > (about > > Attic, whimsy, categories) and added an About page: > > https://projects-new.apache.org/about.html > > > > It is pretty basic at the moment, but tells important things to > > contribute. > > The format is quite simple, but since it's handwritten html... > > > > Now what remains to do before we can switch projects.a.o to projects-new > > content? > > I made a list of "TbD" in the About page listing content that exists in > > previous site that should be somthing like imported IMHO > > > > WDYT? > > > > > > Notice that the Comdev PMC does not have any DOAP file, then no page to > > describe its structure. Same applies to special comittees (Infrastructure, > > Travel Assistance, Security Team, Legal Affairs and Brand Management). > > Don't > > you think we should list these PMCs like any other? > > > > Regards, > > > > Hervé
disabling edit feature in https://projects-new.apache.org/
Hi, I'm working on https://projects-new.apache.org/ , trying to figure out the whole information flow for informations about our projects: I like this new site, but IMHO we can't switch until we're clear on that. And it seems the edit feature currently cause inconsistencies since it edits site's svn simplified json content, instead of DOAP which is AFAIK the current project description standard [1] There are only few projects that used the feature, then it's not too late to fix the issue before it gets worse and people are lost. IMHO, adding a link to this DOAP page in projects-new's about page would do the job = explain people how to add their project (perhaps some additionnal instructions are required, I'm not sure) WDYT? Regards, Hervé [1] http://projects.apache.org/doap.html
DOAP format question
Hi, I'm working on http://projects-new.apache.org/ , which makes me dig into ASF DOAP conventions And I found something that I think is a bug: on http://projects.apache.org/docs/pmc.html , half of the page explains about asfext:PMC in uppercase, while the other half is about asfext:pmc in lowercase AFAIK, everybody is using asfext:pmc, in lowercase Can you confirm that it is in lowercase? Then fix the page, that is causing a little bit of confusion? Thanks in advance, Hervé
projects-new.apache.org
Now that every committer has commit privs, I continued my improvements (about Attic, whimsy, categories) and added an About page: https://projects-new.apache.org/about.html It is pretty basic at the moment, but tells important things to contribute. The format is quite simple, but since it's handwritten html... Now what remains to do before we can switch projects.a.o to projects-new content? I made a list of "TbD" in the About page listing content that exists in previous site that should be somthing like imported IMHO WDYT? Notice that the Comdev PMC does not have any DOAP file, then no page to describe its structure. Same applies to special comittees (Infrastructure, Travel Assistance, Security Team, Legal Affairs and Brand Management). Don't you think we should list these PMCs like any other? Regards, Hervé
Re: first little patch for projects-new.apache.org
Le jeudi 19 mars 2015 12:20:08 Rich Bowen a écrit : > Thanks, Herve. I've applied all of your patches. Sorry for the long > delay. Thanks so much for helping out. thank you Rich I'll wait for the permission opening to continue improvements (I already know a few little steps to do) then, before switching, we'll need to discuss about: - project's DOAP future - previous site with site-dev@ Regards, Hervé > > On 03/08/2015 12:56 PM, Hervé BOUTEMY wrote: > > avoid copy paste for TLP vs sub-project icon and put the icon on the > > left to have full alignment
Re: commit rights to ComDev non-community.a.o site resources
+1 (non-binding) Regards, Hervé Le dimanche 15 mars 2015 22:24:34 Ulrich Stärk a écrit : > Heh. > > When I put that sentence in the board report we didn't have projects-new > yet. > > I don't see a reason why we shouldn't open up those two (or even all of > /comdev) for all committers as long as changes are first discussed on our > lists. > > What do others think? > > Cheers, > > Uli > > On 2015-03-14 16:38, Hervé BOUTEMY wrote: > > Hi, > > > > I lately gave patches for projects-new that were not applied: it seems > > there is a problem to determine who should do it (to avoid projects-new > > to be a single-man affair). > > > > Then I made some investigations: in the last board report for ComDev [1], > > I > > think I found the cause: > > "Since artifacts produced by ComDev are usually documentation on our > > website which is writable for all Apache committers, we usually do not > > add committers to the ComDev project." > > > > Then should projects(-new).apache.org become writeable for all Apache > > committers too? Same for reporter.apache.org? > > > > Regards, > > > > Hervé > > > > [1] https://whimsy.apache.org/board/minutes/Community_Development.html
commit rights to ComDev non-community.a.o site resources
Hi, I lately gave patches for projects-new that were not applied: it seems there is a problem to determine who should do it (to avoid projects-new to be a single-man affair). Then I made some investigations: in the last board report for ComDev [1], I think I found the cause: "Since artifacts produced by ComDev are usually documentation on our website which is writable for all Apache committers, we usually do not add committers to the ComDev project." Then should projects(-new).apache.org become writeable for all Apache committers too? Same for reporter.apache.org? Regards, Hervé [1] https://whimsy.apache.org/board/minutes/Community_Development.html
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
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: 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é
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 ""
+} else {
+ return ""
+}
+}
+
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 = "" + projects[project].name + "";
- if (isTLP(projects[project].name)) {
- li.innerHTML += ""
- } else {
- li.innerHTML += ""
- }
+ li.innerHTML = projectIcon(projects[project].name) + "" + projects[project].name + "";
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 = "" + projects[i].name + "";
- if (isTLP(projects[i].name)) {
-cli.innerHTML += ""
- } else {
-cli.innerHTML += ""
- }
+ cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + "";
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 = "" + projects[i].name + "";
- if (isTLP(projects[i].name)) {
-cli.innerHTML += ""
- } else {
-cli.innerHTML += ""
- }
+ cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + "";
cul.appendChild(cli)
}
}
@@ -662,12 +655,7 @@
xdate = committees[projects[i].name]
if (xdate == date) {
var cli = document.createElement('li');
- cli.innerHTML = "" + projects[i].name + "";
- if (isTLP(projects[i].name)) {
- cli.innerHTML += ""
- } else {
- cli.innerHTML += ""
- }
+ cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + "";
cul.appendChild(cli)
}
}
@@ -712,12 +700,7 @@
var cli = document.createElement('li');
cli.innerHTML = "" + projects[i].name + ": " + len + " committers";
if (unixgroups[i+'-pmc']) {
- cli.innerHTML += ", " + unixgroups[i+'-pmc'].length + " PMC members";
- if (isTLP(projects[i].name)) {
-cli.innerHTML += ""
- } else {
-cli.innerHTML += ""
- }
+ 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 = "" + projects[i].name + "";
- if (isTLP(projects[i].name)) {
- cli.innerHTML += ""
- } else {
- cli.innerHTML += ""
- }
+ cli.innerHTML = projectIcon(projects[i].name) + "" + projects[i].name + "";
cul.appendChild(cli)
}
}
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
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:/
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 @@ - Copyright© 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0 + Copyright© 2015, the Apache Software Foundation. Licensed under the http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version 2.0 For inquiries, contact dev@community.apache.org. Index: index.html === --- index.html (révision 1665047) +++ index.html (copie de travail) @@ -40,7 +40,7 @@ - Copyright© 2015, the Apache Software Foundation. Licensed under the Apache License v/2.0 + Copyright© 2015, the Apache Software Foundation. Licensed under the http://www.apache.org/licenses/LICENSE-2.0";>Apache License, Version 2.0 For inquiries, contact dev@community.apache.org.
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
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
+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: First draft of slides for ApacheCon
Le dimanche 17 février 2013 06:55:21 Benson Margulies a écrit : > On Sun, Feb 17, 2013 at 6:37 AM, Hervé BOUTEMY wrote: > > slide 5: french typo > > "chacun à son goût" (I suppose...) > > Actually, that's an intentional bad joke. Note the word 'capricious' > in the previous line. ok, my english wasn't subtle enough :) notice "á" vs "à": if "goat" vs "goût" is intentional, I suppose "á" vs "à" isn't yes, for a french guy like me, "á" is a typo, or a word for bizarre people having strange accents (I don't know from which country exactly, but for sure not french-speaking), where "à" is perfectly normal Regards, Hervé > > > all over the slides: there are trigrams used (BDfL, PMC, IPMC, PPMC, CCLA, > > SGA, CTR, RTC, TLP, AL): should add plain-text explanations first time > > each one is used, at least in comments > > > > Regards, > > > > Hervé > > > > Le samedi 16 février 2013 13:54:52 Benson Margulies a écrit : > >> https://docs.google.com/presentation/d/1XSqXy9rz-RDcE-P2cK7dEmyjGGHvK8--m > >> R4k _E-qAL4/edit?usp=sharing > >> > >> I've made my first pass at the slides for the talk I'm giving on the > >> incubator in Portland. > >> > >> If anyone is really allergic to Google Docs, I can export it and put > >> it somewhere otherwise accessible.
Re: First draft of slides for ApacheCon
slide 5: french typo "chacun à son goût" (I suppose...) all over the slides: there are trigrams used (BDfL, PMC, IPMC, PPMC, CCLA, SGA, CTR, RTC, TLP, AL): should add plain-text explanations first time each one is used, at least in comments Regards, Hervé Le samedi 16 février 2013 13:54:52 Benson Margulies a écrit : > https://docs.google.com/presentation/d/1XSqXy9rz-RDcE-P2cK7dEmyjGGHvK8--mR4k > _E-qAL4/edit?usp=sharing > > I've made my first pass at the slides for the talk I'm giving on the > incubator in Portland. > > If anyone is really allergic to Google Docs, I can export it and put > it somewhere otherwise accessible.
