While I appreciate the carefully separated data architecture of the projects.a.o RDF/DOAP/website, it seems overly complicated and has very few active maintainers. In particular, it's not clear to most users why we have the PMC RDF files completely separate from all other data sources - nor does it appear anyone actively maintains them.
Pro Tip: if you have no idea what that is, don't worry about it! 8-) ---- Given the growth of active developers on Whimsy, and the centralization of more easily maintained stable data feeds in public/*.json there, does anyone have interest in simplifying the projects.a.o data structure? In particular, even writing up a "Which data comes from where, is processed by what, and is then relied upon by whom" would be a huge improvement, since projects.a.o and whimsy.a.o seem to each process data from the other site (even I'm confused by that). Without getting into major work, it seems the PMC RDF files can be obsoleted easily by having Whimsy do this work. The only relevant data there is the charter, which has this comment: !-- This should be taken from the PMC board resolution --> It seems simple for Whimsy to store a single JSON of all TLPs and their charters by directly sucking it out of passed board resolutions as part of the finalization of a board agenda after the meeting. Is there any interest in reducing cruft in projects.a.o, or at least better documenting the data flow between websites here? This message is /Rich Bowen Approved/. -- - Shane https://www.apache.org/foundation/marks/resources --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
