On Mon, Jun 27, 2016 at 12:19 AM, John D. Ament <johndam...@apache.org> wrote: > On Sun, Jun 26, 2016 at 5:52 PM Sam Ruby <ru...@intertwingly.net> wrote: > >> On Sun, Jun 26, 2016 at 11:21 PM, John D. Ament <john.d.am...@gmail.com> >> wrote: >> > All, >> > >> > Over the past 2 months, mostly in the days leading up to sending the >> report >> > timeline emaisl, I've been putting together a simple script to generate >> the >> > podling report reminders. I used this as an opportunity to learn me some >> > python, and figure out how our mail servers work. I finally finished it, >> > except for maybe some minor tweaks to the date calculation. >> > >> > You can find the script here: >> > >> http://svn.apache.org/viewvc/incubator/public/trunk/report_reminders.py?view=markup&pathrev=1750261 >> > >> > My next steps are: >> > >> > 1. Add it to the report runbook, indicating when to send the reminders. >> > >> > 2. Try to get it incorporated into whimsy. >> >> /me waves :-) >> > > Hey! Its Sam Ruby! The guy who shares his name with the Ruby programming > language!
I'll note that my last name predates the language by a considerable margin. :-) >> Because whimsy-vm is within the ASF's infrastructure, there is no need >> for a user and password to send mail. There also shouldn't be a need >> to prompt for a month? > > Yes, I'm aware of the email issue. It took a while to figure out that this > was why I was getting blacklisted on email. It took me a while too to figure out why whimsy-vm3 (the current vm) couldn't send email either; but that's now sorted out. > about the month... not sure. We could assume that when we're between board > meetings, we are sending for the next month's report. Board meetings are typically, but not always, on the third Wednesday of the month. The current podling reporting schedule backs up based on this rule. Perhaps it might be better to define everything in terms of how many days or weeks before the board meeting actually is instead? >> If you wouldn't mind, what I would like to do is to integrate this >> with Whimsy's library (which means recoding in Ruby, a language very >> much like Python). What that would mean is that things like the email >> list override would be available to all of Whimsy's applications, and >> not be locked into this one. It also will make this script even >> smaller. > > From what I remember, we started on a process to build a podling library. > I lost track of where that was since it wasn't really in anywhere public. > Is it still in SVN somewhere or has it mosey'd over to git? Here's the definition of the class: https://github.com/apache/whimsy/blob/master/lib/whimsy/asf/podlings.rb This truly is a class in the same sense as you would find in Java and other languages; once you obtain a pointer to a Podling object, you can invoke methods against it. > Personally, I'd like to move the override logic in to podlings.xml. I have > no idea why CMDA's name doesn't match its mailing lists, but they may > retire soon, so not sure its worth chasing. The others are all older > podlings. It may be worth spending time converting them to new format. I've roughed in a method to return the name of the dev mailing list for a given podling: https://github.com/apache/whimsy/commit/0f9ea1fc2a13abc3a7e2f205543b47ccde7b6632 Should this data become available in podlings.xml, the method implementation can be changed without affecting the callers of this method. - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
