Mystery unlocked. Committees != Projects
Looks like https://projects.apache.org/json/foundation/committees.json contains the information that I'm looking for. Now, it would still seem that the information on the 'projects by date' page is somewhat misleading, but this is up to the projects to correct in their doap files. Now, we just need to find a way to encourage them to do that. --Rich On 12/13/2016 02:44 PM, Rich Bowen wrote: > Making a note of this here in case someone knows why this is, and can > save me some time digging. Also, because I'm confusing myself. > > There are (sometimes) several different dates floating around on > projects.apache.org regarding project creation date. > > That is, the dates listed on > https://projects.apache.org/committees.html?date and those listed in > the JSON version are (sometimes) not the same. > > That is, let's take Stanbol: > > https://projects.apache.org/committees.html?date says 2012-09 > > https://projects.apache.org/committee.html?stanbol says 2012-09 > > The JSON at https://projects.apache.org/json/foundation/projects.json > says: "created": "2010-12-09" > > The actual board minutes for this project says 19 SEP 2012 (ie 2012-09) > > And the doap.rdf file for the project says <created>2010-12-09</created> > > So, the doap file is wrong, and projects.apache.org is inconsistent. > > This is irritating because I'm trying to write a script that consumes > the JSON and spits out tweets, but of course it's giving me incorrect > results. > > It also implies that people are using a DOAP-generation tool, and then > not checking the output for actual correctness. Or ... something. I'm > not sure. > > Any insight would be welcomed here. Also welcomed would be someone > writing a script that 1) checked whether projects' DOAP files are > correct and 2) bugged projects to fix their wrong DOAP files. > > -- Rich Bowen - rbo...@rcbowen.com - @rbowen http://apachecon.com/ - @apachecon
signature.asc
Description: OpenPGP digital signature
