> ---------- Forwarded message ---------- > From: "Marvin Humphrey" <mar...@rectangular.com> > Date: Feb 10, 2014 3:49 PM > Subject: Re: Tool to generate disclaimer, NOTICE, etc. files > To: "general@incubator.apache.org" <general@incubator.apache.org> > Cc: > > On Sat, Feb 8, 2014 at 8:49 AM, Alan Cabrera <l...@toolazydogs.com> wrote: > > Do you think it would be helpful if we had a tool that generated these > > files? It could work like a command line wizard that prompts the person for > > licensing information and then generates a valid disclaimer, notice, etc. > > files. > > > > If this is a good idea, what files should we generate? Currently, all I can > > think of is disclaimer and notice. > >
chiming in here (without much context so it may not be what you are looking for), but in cloudstack we have a CHANGES file with list of bugs fixed. While we can argue if this is needed or not, I created a quick script to pull jira information from a filter: https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs-rn.git;a=blob_plain;f=utils/jira.py;hb=refs/heads/master it then automatically populates our doc: http://apache-cloudstack-release-notes.readthedocs.org/en/latest/about.html#issues-fixed-in-4-3-0 > > Maybe it could add the info into the project's DOAP file. If we worked out > > the kinks then we could create sbt/gradle/mvn plugins to read the DOAP file > > and insert these files into the correct places in the distributions. Apache > > RAT could also use this info as well. > > > > WDYT? > > I concur with sebb on the extreme challenges of auto-generating NOTICE -- > which is a shame because I'd really love it if the Incubator could benefit > when you're inspired to write tooling. > > One thing I think we could use is a tool which parses mbox archives in > people.apache.org:/home/apmail/ and generates statistics: > > * Total emails sent per list (a measure of activity) > * Unique addresses participating (a measure of diversity) > * Emails sent by Mentors (a measure of Mentor engagement) > I have been doing this for CloudStack, I download all mbox files at the end of the month, parse and stick in mongodb. I than run couple queries. You can see examples at: http://sebgoa.blogspot.ch/2013/05/update-on-apache-cloudstack-community.html The code is a bit of a mess so I did not put it on github. however I did put asf-mail-spider: https://github.com/runseb/asf-mail-spider It crawls the apache mail archive site and collects the names of all the asf making lists, then goes into each one of them and extracts the number of messages each month. Then plots a very messy graph. You could easily focus on the incubator projects and plot that same graph that would give you "Total emails sent per list". > We expend a lot of volunteer energy on shepherding each month, and I think > such an automated tool could help to free up some of that energy for other > tasks. There are two main functions for shepherding: > > 1. Alert the IPMC to podlings which have gone adrift. > 2. Provide an outsider view. > > (I'd add a #3: being exposed to new communities benefits the shepherd, but > that varies by individual.) > > I think that purpose #1 could largely be accomplished using email stats. > > I don't know if this is something you'd feel motivated to work on, but I > thought it was worth mentioning because your original proposal would save time > and energy and so would this. > > Marvin Humphrey > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
