I think it would be worth considering setting up a central store for DOAPs. This was suggested in the past, but was rejected, I think mainly because PMCs were expecting to have to make regular updates to DOAPs, e.g. when releases are made, so wanted to keep them with the code.
It's a pain keeping the releases section of DOAPs up to date (even if they are local to code). Now that there is an automated releases listing, I wonder whether there is any point keeping the info in the DOAP as well? The rest of the fields in a DOAP rarely change, so it matters less if the DOAP is stored in a different repo from the code to which it relates. If DOAPs were moved to a shared GitHub repo, I think it would be much easier for maintenance purposes. Some issues such as fixing an incorrect repo URL or download page link could be dealt with by anyone with suitable karma. Just a thought. Sebb --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
