On Tue, Mar 8, 2016 at 7:36 AM, John D. Ament <johndam...@apache.org> wrote: > On Tue, Mar 8, 2016 at 7:30 AM Sam Ruby <ru...@intertwingly.net> wrote: > >> On Tue, Mar 8, 2016 at 7:14 AM, John D. Ament <johndam...@apache.org> >> wrote: >> > Hi, >> > >> > So, I'm following up on the podling reminder emails. I know I was >> looking >> > at this a long time ago, but decided I needed to learn a bit about ruby >> > (the language) before trying my hands at coming up with a replacement >> > script. >> > >> > So I was wondering, if I do get a script created would whimsy be able to >> > run it on a monthly basis in favor of the marvin script? >> >> I'll give two answers, short term and long term. >> >> --- >> >> Short term, what would be most helpful to start is a detailed >> description of the current (manual) process, complete with examples or >> templates of the emails that are sent out. With that in place, I (or >> others) can code up something that you can initially run on your own >> machine. I trust that you will find that tweaking a running program >> where you can see the outputs instantly to be a less daunting task >> than writing an entirely new program in a language that you are not >> familiar with. Once it is working, it can be hooked up to either run >> as a cron job or as needed, with a a push of a button. >> >> To see an example of the latter, enable your javascript console in >> your browser, go to >> https://whimsy.apache.org/board/agenda/2016-03-16/missing, click on >> one of the buttons at the bottom, then click on Dry Run. >> >> --- >> >> Longer term, I feel that the current board agenda treatment of the >> incubator items to be suboptimal - it displays them as a single >> report. Splitting them into separate pages that can be navigated >> through would be a good start. If there were separate pages per >> incubator item, then people could use those pages to submit reports, >> and features like mentor signoff and enabling comments and discussions >> on individual reports would be a possibility. >> >> Should there be interest in this longer term vision, that might >> influence how the short term step was implemented. >> > > I think we'll need to look long and hard at what the IPMC's report is vs > what is all of the podling reports. It may be a better use of time to > allow the IPMC to flag podling reports and make comments over the board, > just because of chain of authority.
I'm not being paid to do this, so don't worry too much about my time :-) Imagine what could be placed at https://whimsy.apache.org/incubator/reports. What should the ACLs be? What actions do people do today via "svn update; use favorite editor; svn commit" where a push of a button might be easier? Imagine not only mass mailings, but a button on every podling report that will make it easy for you to email just that podling. And with a dropdown on that page that lets you navigate quickly to prior reports. These are but a few things that board members have access to. Things that might make the job of those that actively participate in the incubator easier. All without interfering with those that prefer to update the files in subversion or elsewhere directly. > This would be an interim solution where a simple script could be run to > generate the email. A template would follow what Marvin (the person) > usually sends out > > http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201512.mbox/%3C20151230220215.0C02B189F5%40minotaur.apache.org%3E A template is just one part of the process. Deciding which podlings need to be reminded, and where to send those reminders is also important. In particular, what are the exceptions. This very mailing list is an exception, where the name does not match the PMC for ASF infrastructure implementation reasons. > John - Sam Ruby
