The main problem I have with JSON is that AFAIK it does not support comments.
On 18 April 2015 at 19:03, <herve.bout...@free.fr> wrote: > Yes, I have no problem with json vs xml: the question is more to define the > schema like doap did it, and write documentation for projects to know where > to publish what information > > editing current generated json just creates a new information source, without > any documentation > > My point is: afaik, the purpose of the site is to display info in newer ways, > then json generated from every existing piece of information is great, like > any other format that would better suit some other visualization > > But if we're creating any new source of information that competes with > existing one, this has to be done with great care on documentation, > explanation on how to migrate and so on > > of course the raw format is not an issue: no religion here on xml vs json vs > yaml vs ... > > Regards > > Hervé > > > ----- Mail d'origine ----- > De: jan i <j...@apache.org> > À: dev@community.apache.org > Envoyé: Sat, 18 Apr 2015 11:44:54 +0200 (CEST) > Objet: Re: Re : Re: Project Visualization Tool... > > On Saturday, April 18, 2015, <herve.bout...@free.fr> wrote: > >> It was told the new site would use native json, instead of doap >> But I'm not convinced at all, since Doap is an invaluable source of info, >> documented, and so on > > json is also a documented standard, that in general is more known, and I > believe has more tools supporting it. > > >> >> then imho it would be better to generate json from doap >> >> I disabled the json edit feature recently since it will cause problems > > which problems? > > with a defined json it is simple to generate the doap file. > > I highly recommend staying at json and using that as base for all our > central data. > > rgds > jan i > > > >> >> regards >> >> Hervé >> ----- Mail d'origine ----- >> De: Shane Curcuru <a...@shanecurcuru.org <javascript:;>> >> À: dev@community.apache.org <javascript:;> >> Envoyé: Sat, 18 Apr 2015 06:43:37 +0200 (CEST) >> Objet: Re: Project Visualization Tool... >> >> We had a great session, and a lot of energy, hopefully we can make some >> progress. One note: this needs to be a comdev PMC project, and we need >> to really plan the data part out if we want to be successful. >> >> Note that projects-new.a.o is the planned future replacement for >> projects.a.o - there are *significant* differences, so you need to look >> at the About page and the source repo. In particular, the new site uses >> it's own new JSON generated sources which (I think) will no longer use >> the DOAPs. >> >> In particular, Infra currently does *not* consider either the data >> gathering (i.e. populating the JSON behind the projects-new site) nor >> the visualizations (current or ones we want to build) as core supported >> services. So whatever we build needs to be maintained by this PMC to >> start with. >> >> Also, Link dump of useful related bits: ---------------- >> >> Old service, based on crappy cron jobs and DOAP files from projects: >> https://projects.apache.org/ >> >> New service, soon to be infra supported, relying on JSON data generated >> by infra on a regular schedule: >> https://projects-new.apache.org/ >> >> Useful PMC chair report helper, that surfaces a number of different >> statistics about your PMC(s), including mailing list stats, >> PMC/committer changes, some software releases, etc. etc. (Members have >> visibility to all PMCs): >> https://reporter.apache.org >> >> Rob Weir (AOO, Member) used to do some visualization stuff and might >> have code ideas: >> http://www.robweir.com/blog/2013/05/mapping-apache.html >> >> Ken Coar's old mailing list stats page: >> >> https://people.apache.org/~coar/mlists.html >> >> The AOO project wrote a mailing list visualizer for who talks to whom: >> https://blogs.apache.org/OOo/entry/visualizing_the_aoo_dev_list >> >> Some outside statistics FLOSSmole generated about Apache communities and >> lists: >> http://flossmole.org/category/tags/apache >> >> Random other interesting analytics: >> The Subversion project has the "contribulyzer" >> >> >> >> - Shane >> >> > > -- > Sent from My iPad, sorry for any misspellings. >
