+1 for Tomaz! -Dan
On Tue, May 10, 2011 at 11:53 AM, Joe Miller <[email protected]> wrote: > +1 for Tomasz > > On Tue, May 10, 2011 at 11:24 AM, Schwartz, Philip Marc (LNG-BCT) < > [email protected]> wrote: > >> I would agree Tomasz would get my vote for chair if he is willing. >> >> Thank You, >> Philip Schwartz >> Software Engineering >> LexisNexis RS >> O - 561 999 4472 >> C - 954 290 4024 >> >> >> -----Original Message----- >> From: Joe Schaefer [mailto:[email protected]] >> Sent: Tuesday, May 10, 2011 2:20 PM >> To: [email protected] >> Subject: [libcloud] Re: push the graduation button >> >> So, the next step is to decide on a chair, >> who will go thru the incubator graduation checklist, >> deal with any outstanding issues, and put forth >> a resolution for the creation of a top-level >> project for libcloud. >> >> The chair is responsible for writing quarterly >> reports to the board on the project's status, >> and dealing with any changes in pmc/committer >> rosters. Other than that the position is that >> of a glorified secretary, not a project visionary. >> >> >> Any volunteers for the position? As a random >> observation Tomasz is not a bonehead and seems >> to not mind doing the drudgery of porting the >> website to the CMS, so he's certainly qualified. >> >> >> ----- Original Message ---- >> > From: Joe Schaefer <[email protected]> >> > To: [email protected] >> > Sent: Thu, April 14, 2011 1:01:01 PM >> > Subject: push the graduation button >> > >> > Well time has passed since the last time this >> > subject was broached, and new people have entered >> > the scene and are doing the bulk of the work. >> > I'd say this project is more than ready to graduate, >> > so let's discuss whatever needs ferreting out and >> > move forward to a vote soonish. >> > >> >> This message (including any attachments) contains confidential information >> intended for a specific individual and purpose, and is protected by law. If >> you are not the intended recipient, you should delete this message. Any >> disclosure, copying, or distribution of this message, or the taking of any >> action based on it, is strictly prohibited. >> >
