Le vendredi 26 juin 2015 17:46:55 sebb a écrit : > On 26 June 2015 at 07:12, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > that's why I want to switch projects to projects-old and projects-new to > > projects: be able to work on extracting documentation from projects-old > > and > > updating it to match the new location > > That will break the existing links. > > If you want do the switch ahead of fixing the documentation, then one > way to do it is to ensure that projects-old is set up to point to the > current projects.a.o. > > Then change projects-new to link to projects-old instead of projects - > that should be trivial to do. > > Then projects-new can replace projects.a.o. > > Documentation can then be migrated to the new code in the old URL. yes, of course, these are the exact steps: I just summarised
> > > I proposed http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > > as > > the new location of DOAP files lists (both PMC and projects) but got no > > answer > Did not see that. > > That will break projects-old, so -1 until projects-old has been > retired unless you can find a way to keep projects-old working with > the new location. the idea is to let old data in the old location and not update it any more: this won't break anything, just make projects-old less accurate over time that's not an issue IMHO, since we expect to migrate the doc and shutdown projects-old after that, in a few monthes notice that I think the cron job that updates projects-old should be switched off to avoid issues > > AFAIK it's not necessary to move the location. ? previously, you told having projects-new depending on projects-old was an issue and you were right! and IMHO, it's an issue just because data in projects-old is hard to find for someone not expert in the whole system I'll start to add comments in projects-old data to point to projects-new to start the transition then we'll have to agree on when to really switch (and find who can do it) Regards, Hervé > > > if we're ok with that new location, the next step is to stop modifying > > equivalent files in > > http://svn.apache.org/viewvc/infrastructure/site-tools/trunk/projects/ > > (or even remove them) but point to the new location > > > > Of course, if ok with the new location, we can immediately add > > committees.xml and projects.xml pointers to > > https://projects-new.apache.org/about.html IMHO the simple file names and > > location in about.html would make things very clear before diggin into > > more details on DOAP format and conventions (which could be in the Wiki > > for ease of editing) > > > > > > can we agree: > > 1. on the new data location and content: > > http://svn.apache.org/viewvc/comdev/projects.apache.org/data/ > > No, see above. > > > 2. on the switch then update of everything to match the new location (and > > stop updating projects-old) > > Not entirely, see above. > > > Regards, > > > > Hervé > > > > Le jeudi 25 juin 2015 09:17:32 vous avez écrit : > >> On 25 June 2015 at 06:53, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > >> > Sebb, > >> > > >> > as main maintainer of current http://projects.apache.org/ (AFAIK), are > >> > you > >> > ok with switching the url to the new service and renaming current > >> > service > >> > to projects-old (to let use time to continue content migration withotu > >> > loosing anything)? Do you see any show stopper? > >> > >> The main item missing from projects-new is documentation - it > >> currently points to projects. > >> It's not immediately obvious how to provide data for the site. > >> I think the main page needs to provide more of an overview. > >> > >> I think the first step needs to be to improve the projects-new > >> documentation so it does not rely on the current project pages. > >> > >> Also I notice that it seems p-new relies on parsing > >> http://people.apache.org/committer-index.html > >> which in turn parses other data sources. > >> > >> That needs to be fixed. > >> > >> > Of course, I'm interested in your help to maintain the new projects > >> > site: > >> > don't hesitate to comment on or change the code. > >> > > >> > Regards, > >> > > >> > Hervé > >> > > >> > Le dimanche 21 juin 2015 17:16:07 jan i a écrit : > >> >> +1 switch as soon as possible, and then continue working on the data > >> >> end. > >> >> > >> >> rgds > >> >> jan i > >> >> > >> >> On Sunday, June 21, 2015, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > >> >> > Le dimanche 21 juin 2015 15:54:29 jan i a écrit : > >> >> > > On 21 June 2015 at 15:48, Daniel Gruno <humbed...@apache.org > >> >> > > >> >> > <javascript:;>> wrote: > >> >> > > > On 2015-06-21 02:45, Hervé BOUTEMY wrote: > >> >> > > >> for me, the new site is ready: there is of course room for > >> >> > > >> >> > improvements, > >> >> > > >> >> > > >> but > >> >> > > >> it is stable and maintainable, waiting for contributions > >> >> > > >> > >> >> > > >> notice: I changed the wording to stop using "TLP", but use > >> >> > > >> "Committee" > >> >> > > >> instead, since TLP cause issues when trying to describe each > >> >> > > >> projects > >> >> > > >> (the > >> >> > > >> software) as TLP or sub-projects > >> >> > > >> > >> >> > > >> > >> >> > > >> when doing the switch, we'll need to rename current site as > >> >> > > >> projects- > >> >> > > >> old.apache.org: there is some content to migrate (DOAP, > >> >> > > >> >> > documentation) > >> >> > > >> >> > > >> associated to communication with projects on the changes that > >> >> > > >> has > >> >> > > >> to > >> >> > > >> >> > be > >> >> > > >> >> > > >> decoupled from public vizualisation. I'll continue working on > >> >> > > >> it. > >> >> > > >> > >> >> > > >> There one choice to do: continue serving the pages from current > >> >> > > >> VM > >> >> > > >> or > >> >> > > >> serve > >> >> > > >> through standard resilient httpds. The VM is useful for cron > >> >> > > >> jobs, > >> >> > > >> >> > but is > >> >> > > >> >> > > >> not > >> >> > > >> absolutely necessary for serving content since I removed online > >> >> > > >> >> > content > >> >> > > >> >> > > >> editing that caused the VM requirement for content serving > >> >> > > >> AFAIK. > >> >> > > >> >> > Using > >> >> > > >> >> > > >> standard httpd will avoid SPOF or eventual load issue. > >> >> > > > > >> >> > > > What do you mean by 'standard httpd'? It already uses...standard > >> >> > > > httpd > >> >> > > >> >> > for > >> >> > > >> >> > > > serving the site. > >> >> > > > The cron jobs are needed for updating various statistics and > >> >> > > > data > >> >> > > > on > >> >> > > >> >> > the > >> >> > > >> >> > > > site, they can't just be shut off - they also power > >> >> > > >> >> > reporter.apache.org. > >> >> > > >> >> > > Maybe I misunderstood something, I understood that we are using > >> >> > > httpd, > >> >> > > >> >> > but > >> >> > > >> >> > > in our own vm. In my opinion it would be nicer to use the www.a.o > >> >> > > httpd > >> >> > > (sorry > >> >> > > vms have been changing lately so I am not sure where it runs), > >> >> > > since > >> >> > > that > >> >> > > would put httpd maintenance on infra instead of comdev. > >> >> > > >> >> > +1 > >> >> > that was what I mean by "standard httpd" (ie not the binary but the > >> >> > machines > >> >> > where it runs) > >> >> > > >> >> > > > I think the site is ready for a more prominent role, but I find > >> >> > > > this > >> >> > > > discussion confusing, and I find it somewhat sad that we're > >> >> > > > gonna > >> >> > > > stick > >> >> > > > with something as arcane as DOAP. > >> >> > > > >> >> > > +100 !! > >> >> > > > >> >> > > DOAP == Dead On Arrival Permanently :-) JSON == Jump Simply On New > >> >> > > (but I know I am only 1 voice). > >> >> > > >> >> > step by step, please: this will avoid confusion between independant > >> >> > topics > >> >> > > >> >> > switching without disturbing current conventions/knowledge is > >> >> > something > >> >> > that > >> >> > already takes a long time and energy: I know it because I put a lot > >> >> > of > >> >> > energy > >> >> > on it for a few monthes now! > >> >> > > >> >> > We started a discussion on this source format topic during april, > >> >> > and > >> >> > AFAIK > >> >> > nobody worked on it. > >> >> > > >> >> > What I'd like now is to switch: we can discuss later on what we want > >> >> > to > >> >> > change > >> >> > (and communication to every comittees this requires). > >> >> > With the new site, we'll be able to change formats if we want, the > >> >> > only > >> >> > requirement is to have json files for the visualization > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > Regards, > >> >> > > >> >> > Hervé > >> >> > > >> >> > > rgds > >> >> > > jan i. > >> >> > > > >> >> > > > With regards, > >> >> > > > Daniel. > >> >> > > > > >> >> > > >> but definitely, the site is ready for the switch > >> >> > > >> > >> >> > > >> Regards, > >> >> > > >> > >> >> > > >> Hervé > >> >> > > >> > >> >> > > >> Le vendredi 19 juin 2015 20:55:52 Sally Khudairi a écrit : > >> >> > > >>> Hello Uli and the Apache ComDev team --I hope this message > >> >> > > >>> finds > >> >> > > >>> you > >> >> > > >>> well. > >> >> > > >>> Per below, I'm interested in promoting the new Projects page. > >> >> > > >>> Can you please let me know if/when we're ready to do so? > >> >> > > >>> Thanks so much, > >> >> > > >>> Sally > >> >> > > >>> > >> >> > > >>> ----- Forwarded Message ----- > >> >> > > >>> > >> >> > > >>> From: David Nalley <da...@gnsa.us <javascript:;>> > >> >> > > >>> > >> >> > > >>> To: Sally Khudairi <sallykhuda...@yahoo.com <javascript:;>> > >> >> > > >>> > >> >> > > >>> Cc: Daniel Gruno <humbed...@apache.org <javascript:;>>; ASF > >> >> > > >> >> > Infrastructure > >> >> > > >> >> > > >>> <infrastruct...@apache.org <javascript:;>> Sent: Friday, June > >> >> > > >>> 19, > >> >> > > >> >> > 2015 11:50 AM > >> >> > > >> >> > > >>> Subject: Re: Is https://projects-new.apache.org/ ready for > >> >> > > >>> prime > >> >> > > >> >> > time? > >> >> > > >> >> > > >>> Hi Sally: > >> >> > > >>> > >> >> > > >>> projects-new.apache.org is a ComDev managed resource, not an > >> >> > > >>> infrastructure managed resource. I think the PMC has had a > >> >> > > >>> discussion > >> >> > > >>> or two about when to migrate projects-new to projects.a.o > >> >> > > >>> > >> >> > > >>> --David > >> >> > > >>> > >> >> > > >>> > >> >> > > >>> > >> >> > > >>> On Fri, Jun 19, 2015 at 11:30 AM, Sally Khudairi > >> >> > > >>> > >> >> > > >>> <sallykhuda...@yahoo.com <javascript:;>> wrote: > >> >> > > >>>> Hello Daniel and David --I hope you are both well. > >> >> > > >>>> > >> >> > > >>>> > >> >> > > >>>> I was wondering if the new Projects page at > >> >> > > >>>> > >> >> > > >>>> https://projects-new.apache.org/ > >> >> > > >>>> > >> >> > > >>>> was ready to be publicly deployed/announced/promoted. > >> >> > > >>>> > >> >> > > >>>> There's so much great information there and it's an > >> >> > > >>>> incredible > >> >> > > >> >> > resource > >> >> > > >> >> > > >>>> (I > >> >> > > >>>> use it every week for the News Round-ups and we relied on it > >> >> > > >>>> for > >> >> > > >>>> the > >> >> > > >>>> Annual Report), if there's no reason why it should still be > >> >> > > >>>> in > >> >> > > >> >> > stealth > >> >> > > >> >> > > >>>> mode, I'd like to shout out about it from the rooftops. > >> >> > > >>>> > >> >> > > >>>> Just let me know if we're good to go and if there are any > >> >> > > >>>> disclaimers/caveats we should be aware of. > >> >> > > >>>> > >> >> > > >>>> Warm thanks, > >> >> > > >>>> Sally > >> >> > > >>>> > >> >> > > >>>> > >> >> > > >>>> = = = = = > >> >> > > >>>> vox +1 617 921 8656 > >> >> > > >>>> off2 +1 646 583 3362 > >> >> > > >>>> skype sallykhudairi
