Re: December reporting: All Mentors Please Sign Off and general note
Yes, true, but any invitation to communicate such difficulties is welcome IMO. Upayavira On Sun, Dec 2, 2012, at 02:37 AM, Tim Williams wrote: On Sat, Dec 1, 2012 at 12:54 PM, Benson Margulies bimargul...@gmail.com wrote: First of several reminders: For podlings reporting in December, we'd like *all* mentors to sign off on the reports. I hope to use this to get a clearer picture of where we have mentor weaknesses. General note: if you are a PPMC member or mentor, and you feel that your community is undersupplied with Mentor attention (e.g., you have trouble getting votes for releases), please start a thread here. The report is meant to communicate this sort of health info... --tim - 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
Re: [VOTE] Graduate OpenMeetings from Incubator
+1 Sent from my tablet On Dec 2, 2012 6:51 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: = Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache OpenMeetings PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [VOTE] Graduate OpenMeetings from Incubator
+1 On Dec 2, 2012 1:51 PM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: = Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache OpenMeetings PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: Incubator report reminders sent for Dec 2012
On Sat, Dec 01, 2012 at 07:20:35PM +0100, Christian Grobmeier wrote:
I miss Onami and Ripple from the reminders.
Helix and HDT are also missing; these four are all set up as
${podling}.incubator.apache.org - related?
But they are listed here:
http://incubator.apache.org/report-next-month.html#onami
What do I need to fix to get these reminders?
I just know the old wiki-styled process
On Sat, Dec 1, 2012 at 4:26 PM, Marvin no-re...@apache.org wrote:
The next board meeting is scheduled for Wed, 19 December 2012, 10:00:00 PST.
I have just sent reminder emails to the below addresses, requesting them
to supply board reports 2 weeks before the above date (Wed, Dec 5th).
Please recall that the Incubator report is due Wed, Dec 12th.
Allura Developers allura-...@incubator.apache.org
Bloodhound Developers bloodhound-...@incubator.apache.org
Blur Developers blur-...@incubator.apache.org
cTAKES Developers ctakes-...@incubator.apache.org
Drill Developersdrill-...@incubator.apache.org
Etch Developers etch-...@incubator.apache.org
Flex Developers flex-...@incubator.apache.org
Hadoop Development Tools Developers
general@incubator.apache.org
HCatalog Developers hcatalog-...@incubator.apache.org
Kalumet Developers kalumet-...@incubator.apache.org
Openmeetings Developers openmeetings-...@incubator.apache.org
S4 Developers s4-...@incubator.apache.org
Wave Developers wave-...@incubator.apache.org
-
To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
For additional commands, e-mail: private-h...@incubator.apache.org
--
http://www.grobmeier.de
https://www.timeandbill.de
-
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
Incubator PMC/Board report for Dec 2012 ([ppmc])
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 December 2012, 10:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Dec 5th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/December2012 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
On Fri, 30 Nov 2012, Roman Shaposhnik wrote: Date: Fri, 30 Nov 2012 03:05:15 +0100 From: Roman Shaposhnik r...@apache.org To: general@incubator.apache.org, infrastruct...@apache.org Subject: Re: Formats of SHA/MD5 checksums Sender: shaposh...@gmail.com On Sun, Nov 25, 2012 at 9:29 PM, Roman Shaposhnik r...@apache.org wrote: On Tue, Nov 20, 2012 at 3:50 PM, sebb seb...@gmail.com wrote: Personally, I find it difficult to verify the GPG generated checksums. Ditto. It's particularly awkward when the hash is wrapped over several lines. I ended up writing a Perl script to handle all the variations. If I'm not alone perhaps we should discourage the use of this format and modify the release FAQ page. +1 Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 I assume 'it' is md5 cheksum files generated with gpg --print-md MD5 [fileName] [fileName].md5 I am +1 on suggesting (on that page) a 'normal' form for the content of a .md5 file. I am definitedly -1 on removing the gpg line above, or suggesting that only one form of .md5 files is allowed. The reason given I ended up writing a Perl script doesn't make sense ; .md5 files come in many forms but the algorithm to verify is the same for all of them (there are no 'variations.') : verify (checksum md5, .md5-file fff) : -- tmp = lowercase cat fff -- md5 = lowercase cat md5 -- squeeze non-hex ([^a-f0-9]) out of tmp (and md5) -- match md5 ~ tmp HPP _ Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_ Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \ Budapestlaan 6, 3584CD Utrecht, NLF +31 30 253 4553 \_/ \_/ http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
Roman Shaposhnik r...@apache.org wrote: +infra Ping! I would really like this annoyance to be resolved one way or the other. Could somebody more experienced with Apache web properties answer the question? Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? No vote is required to change that web page. Those pages are infra owned but any member can change them. Since infra owns the page, it would be polite to suggest the alternative text on infrastructure@. Once that is agreed, any member can apply it. With my infra hat on, I have no objection to standardising on the md5sum format for MD5 checksums. A couple of side issues: Firstly, you removed far to much context when adding infra to the thread. I had to go digging through the archives to figure out what the problem was. Secondly, votes are not the way to drive change. Discussion is. The process is not: - see an issue - pick a solution - start a vote for implementing that solution - drive through the change but: - see an issue - discuss options to fix it - agree the way forward (consensus) - make the change Releases and new committers are pretty much the only time I'd expect to see votes in an Apache community. Mark - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
That page is part of the Apache CMS and ASF members can edit that page by using the following http://www.apache.org/dev/cms.html#usage. Non ASF members can create a ticket within jira under the infra project and attach a patch for the changes they would like to make. The repo and file you are looking for is https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/dev/release-signing.mdtext -Jake Roman Shaposhnik November 29, 2012 9:05 PM +infra Ping! I would really like this annoyance to be resolved one way or the other. Could somebody more experienced with Apache web properties answer the question? Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? Thanks, Roman. On Sun, Nov 25, 2012 at 9:29 PM, Roman Shaposhnik r...@apache.org wrote: On Tue, Nov 20, 2012 at 3:50 PM, sebb seb...@gmail.com wrote: Personally, I find it difficult to verify the GPG generated checksums. Ditto. It's particularly awkward when the hash is wrapped over several lines. I ended up writing a Perl script to handle all the variations. If I'm not alone perhaps we should discourage the use of this format and modify the release FAQ page. +1 Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? Thanks, Roman.
Re: Incubator report reminders sent for Dec 2012
On Sat, Dec 1, 2012 at 7:41 PM, Daniel Shahaf danie...@apache.org wrote:
On Sat, Dec 01, 2012 at 07:20:35PM +0100, Christian Grobmeier wrote:
I miss Onami and Ripple from the reminders.
Helix and HDT are also missing; these four are all set up as
${podling}.incubator.apache.org - related?
Yes, I think so too. Davids e-mail indicated something like that. I
have just looked at
http://svn.apache.org/viewvc?view=revisionrevision=1400367
but could not see anything of interested (for this case). But this is
related to my lack of python knowledge.
It seems some sorts of files like:
http://svn.apache.org/repos/asf/incubator/public/trunk/content/report_due_3.txt
are generated by clutch and then later used by Marvin (I really don't
know anything about this tool) to send out the reminders.
That said, HDT, Ripple, Onami and Helix all have a wrong recipient
address in this file. So my idea is that we need to find
out how Clutch extracts the recipient address of the podling and fix
either the source of it or the alogrithm in clutch.
But they are listed here:
http://incubator.apache.org/report-next-month.html#onami
What do I need to fix to get these reminders?
I just know the old wiki-styled process
On Sat, Dec 1, 2012 at 4:26 PM, Marvin no-re...@apache.org wrote:
The next board meeting is scheduled for Wed, 19 December 2012, 10:00:00
PST.
I have just sent reminder emails to the below addresses, requesting them
to supply board reports 2 weeks before the above date (Wed, Dec 5th).
Please recall that the Incubator report is due Wed, Dec 12th.
Allura Developers allura-...@incubator.apache.org
Bloodhound Developers bloodhound-...@incubator.apache.org
Blur Developers blur-...@incubator.apache.org
cTAKES Developers ctakes-...@incubator.apache.org
Drill Developersdrill-...@incubator.apache.org
Etch Developers etch-...@incubator.apache.org
Flex Developers flex-...@incubator.apache.org
Hadoop Development Tools Developers
general@incubator.apache.org
HCatalog Developers hcatalog-...@incubator.apache.org
Kalumet Developers kalumet-...@incubator.apache.org
Openmeetings Developers openmeetings-...@incubator.apache.org
S4 Developers s4-...@incubator.apache.org
Wave Developers wave-...@incubator.apache.org
-
To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org
For additional commands, e-mail: private-h...@incubator.apache.org
--
http://www.grobmeier.de
https://www.timeandbill.de
-
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
--
http://www.grobmeier.de
https://www.timeandbill.de
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate OpenMeetings from Incubator
+1 (mentor) On Sun, Dec 2, 2012 at 10:50 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: = Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache OpenMeetings PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate OpenMeetings from Incubator
+1 (IPMC) On Sun, Dec 2, 2012 at 7:50 AM, seba.wag...@gmail.com seba.wag...@gmail.com wrote: Dear Incubation members, During incubation, OpenMeetings has : * Produced 1 Release * Added 5 new Committer/PPMC members and shows constant community activities * Cleared IP on all code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that Given these accomplishments, I propose that we submit the following graduation resolution to the incubator PMC. We organized already a community vote: http://markmail.org/thread/wnxvkvukdqgdddpn The vote received: 1x +1 Yegor IPMC 5x +1 solomax, aaf, sebawagner, greenes PMC 1x +1 Irina Please VOTE over the next 72 hours on the resolution below: [ ] +1 Graduate OpenMeetings from the Incubator per the resolution below. [ ] +0 Don't care. [ ] -1 Don't graduate OpenMeetings from the Incubator because: = Charter here: https://cwiki.apache.org/confluence/display/OPENMEETINGS/Draft+Charter and copied below: X. Establish the Apache OpenMeetings Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to OpenMeetings Web-Conferencing tool. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache OpenMeetings Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is responsible for the creation and maintenance of software related to the OpenMeetings Web-Conferencing tool; and be it further RESOLVED, that the office of Vice President, Apache OpenMeetings be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache OpenMeetings Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache OpenMeetings Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache OpenMeetings Project: * Alexei Fedotova...@apache.org * Sebastian Wagner sebawag...@apache.org * Maxim Solodovnik solo...@apache.org * Oliver Becherer smoe...@apache.org * Rodion Volkovrc...@apache.org * Eugen Schwert eschw...@apache.org * German Grekhovggrek...@apache.org * Timur Tleukenov ti...@apache.org * Alvaro Bustos Ruiz al...@apache.org * George Kirkham gkirk...@apache.org * Stephen Cotthammegatroni...@apache.org * Sascha Xander sxan...@apache.org * Evgeny Rovinskyrovin...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sebastian Wagner be appointed to the office of Vice President, Apache OpenMeetings, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache OpenMeetings PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache OpenMeetings Project; and be it further RESOLVED, that the Apache OpenMeetings Project be and hereby is tasked with the migration and rationalization of the Apache Incubator OpenMeetings podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator OpenMeetings podling encumbered upon the Apache Incubator Project are hereafter discharged. -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator report reminders sent for Dec 2012
You supplied the critical information; it's supposed to all flow from the clutch, there are no other manually maintained files. On Sat, Dec 1, 2012 at 7:05 PM, David Crossley cross...@apache.org wrote: Benson Margulies wrote: Can you point to some maintenance instructions for all of this? Sorry i do not have time to find them right now, but it has been explained to this list on various occasions so should be in the archives. We do need to have better docs, so that we do not all forget, me included. The main data file is now content/podlings.xml Clutch parses that, gets other hints from each project status page, checks that the podling's mail lists are established and operating, then generates the report lists of dev addresses. http://incubator.apache.org/clutch.html#notes http://incubator.apache.org/clutch.html#data I think that i can see the glitch reported today. Recently the setup of new projects mail lists infra procedure changed. I immediately followed up an tweaked Clutch to handle that. However it seems that the writing of the report_due_[1-3].txt data files (which 'marvin' uses to send the reminders) is not quite right. Sorry no time to fix right now. See http://svn.apache.org/viewvc?view=revisionrevision=1400367 The reporting web page lists are also generated from content/podlings.xml each time that data file changes. The CMS triggers and its Ant build uses some XSL in the top level of the incubator SVN. Some other stuff that we need to make more obvious: http://incubator.apache.org/report-next-month.html http://incubator.apache.org/report-groups.txt -David On Sat, Dec 1, 2012 at 1:30 PM, Christian Grobmeier grobme...@gmail.com wrote: Hmm maybe it is this file? http://svn.apache.org/repos/asf/incubator/public/trunk/content/report_due_3.txt Onami which is listed there does have a wrong dev@ address. Not sure why Marvin didn't report it On Sat, Dec 1, 2012 at 7:26 PM, Benson Margulies bimargul...@gmail.com wrote: I'm embarassed to admit that I don't know either. http://incubator.apache.org/report-groups.txt looks right, what else needs to be done? On Sat, Dec 1, 2012 at 1:20 PM, Christian Grobmeier grobme...@gmail.com wrote: I miss Onami and Ripple from the reminders. But they are listed here: http://incubator.apache.org/report-next-month.html#onami What do I need to fix to get these reminders? I just know the old wiki-styled process On Sat, Dec 1, 2012 at 4:26 PM, Marvin no-re...@apache.org wrote: The next board meeting is scheduled for Wed, 19 December 2012, 10:00:00 PST. I have just sent reminder emails to the below addresses, requesting them to supply board reports 2 weeks before the above date (Wed, Dec 5th). Please recall that the Incubator report is due Wed, Dec 12th. Allura Developers allura-...@incubator.apache.org Bloodhound Developers bloodhound-...@incubator.apache.org Blur Developers blur-...@incubator.apache.org cTAKES Developers ctakes-...@incubator.apache.org Drill Developersdrill-...@incubator.apache.org Etch Developers etch-...@incubator.apache.org Flex Developers flex-...@incubator.apache.org Hadoop Development Tools Developers general@incubator.apache.org HCatalog Developers hcatalog-...@incubator.apache.org Kalumet Developers kalumet-...@incubator.apache.org Openmeetings Developers openmeetings-...@incubator.apache.org S4 Developers s4-...@incubator.apache.org Wave Developers wave-...@incubator.apache.org - To unsubscribe, e-mail: private-unsubscr...@incubator.apache.org For additional commands, e-mail: private-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - 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 -- http://www.grobmeier.de https://www.timeandbill.de - 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 - To unsubscribe, e-mail:
checking on the shepherd inventory (or, 3.14159 IPMC members ...)
http://wiki.apache.org/incubator/IncubatorShepherds is the official list of willing shepherds. I would be exceedingly grateful for additional volunteers here, and of course of someone needs to leave the list, please edit yourself out. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: checking on the shepherd inventory (or, 3.14159 IPMC members ...)
On Dec 2, 2012, at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: http://wiki.apache.org/incubator/IncubatorShepherds is the official list of willing shepherds. I would be exceedingly grateful for additional volunteers here, and of course of someone needs to leave the list, please edit yourself out. Hi Benson, I added my name to the wiki, I will be willing to help as needed. But if there is a choice, I prefer java based middleware, especially the big data, hadoop family of podlings. Suresh - 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
Re: checking on the shepherd inventory (or, 3.14159 IPMC members ...)
On Sun, Dec 2, 2012 at 11:28 AM, Suresh Marru sma...@apache.org wrote: On Dec 2, 2012, at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: http://wiki.apache.org/incubator/IncubatorShepherds is the official list of willing shepherds. I would be exceedingly grateful for additional volunteers here, and of course of someone needs to leave the list, please edit yourself out. Hi Benson, I added my name to the wiki, I will be willing to help as needed. But if there is a choice, I prefer java based middleware, especially the big data, hadoop family of podlings. Thank you very much Suresh, I have inventory in that area to point you at! Suresh - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: checking on the shepherd inventory (or, 3.14159 IPMC members ...)
Hi Benson, I liked that Jukka assigned me to random podlings as this exposes me to new ideas. Regards, Dave Sent from my iPhone On Dec 2, 2012, at 11:40 AM, Benson Margulies bimargul...@gmail.com wrote: On Sun, Dec 2, 2012 at 11:28 AM, Suresh Marru sma...@apache.org wrote: On Dec 2, 2012, at 10:28 AM, Benson Margulies bimargul...@gmail.com wrote: http://wiki.apache.org/incubator/IncubatorShepherds is the official list of willing shepherds. I would be exceedingly grateful for additional volunteers here, and of course of someone needs to leave the list, please edit yourself out. Hi Benson, I added my name to the wiki, I will be willing to help as needed. But if there is a choice, I prefer java based middleware, especially the big data, hadoop family of podlings. Thank you very much Suresh, I have inventory in that area to point you at! Suresh - 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 - 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
Re: Actively seeking for organic mentors
On Dec 2, 2012, at 8:46 AM, Benson Margulies wrote: By 'organic mentor', I mean a PPMC member who, while not an ASF member, has shown the necessary engagement and understanding to qualify as an IPMC member, and thus mentor and release voter. PPMC members who are also active in TLP communities are obvious candidates. We have, as well, inducted some people even if the PPMC is their first involvement at the ASF. I would ask all mentors, but especially mentors who are having trouble finding the time to be as engaged as they might like, to seek out and nominate PPMC members for membership in the IPMC. As a PMC, we will be want to much more than a rubber stamp, particularly in the second case. However, this is one of our best avenues to improve mentor coverage of projects In the next few months, I intend to send other messages focussed on podlings that have symptoms of mentor-deprivation, but I thought this might be a low-stress start. Great idea. May I suggest that this list of organic mentors be collected on private? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Actively seeking for organic mentors
On Sun, Dec 2, 2012 at 12:02 PM, Alan Cabrera l...@toolazydogs.com wrote: On Dec 2, 2012, at 8:46 AM, Benson Margulies wrote: By 'organic mentor', I mean a PPMC member who, while not an ASF member, has shown the necessary engagement and understanding to qualify as an IPMC member, and thus mentor and release voter. PPMC members who are also active in TLP communities are obvious candidates. We have, as well, inducted some people even if the PPMC is their first involvement at the ASF. I would ask all mentors, but especially mentors who are having trouble finding the time to be as engaged as they might like, to seek out and nominate PPMC members for membership in the IPMC. As a PMC, we will be want to much more than a rubber stamp, particularly in the second case. However, this is one of our best avenues to improve mentor coverage of projects In the next few months, I intend to send other messages focussed on podlings that have symptoms of mentor-deprivation, but I thought this might be a low-stress start. Great idea. May I suggest that this list of organic mentors be collected on private? Yes, nominations for IPMC membership belong, I believe, on private. I'm trying my best to be as public as possible, and than you for pointing out the little line in the sand here. Regards, Alan - 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
An idea for the clutch department
David, I'm thinking about how to make clutch.py grab a description from each project. I have two uses for this: first, if it were in the pkl output, I could make a generator for reporting templates that included the description. Second, if I were feeling silly, I could make it a popup div on the lines of the clutch table. It looks to me like the following xpath would yield the results I'm looking for: section[@id='Description']/p/text() Would you object to this idea? If not, off I go. ---benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: An idea for the clutch department
Sorry, I now see that there's a perfectly good description already being picked up. On Sun, Dec 2, 2012 at 2:35 PM, Benson Margulies bimargul...@gmail.com wrote: David, I'm thinking about how to make clutch.py grab a description from each project. I have two uses for this: first, if it were in the pkl output, I could make a generator for reporting templates that included the description. Second, if I were feeling silly, I could make it a popup div on the lines of the clutch table. It looks to me like the following xpath would yield the results I'm looking for: section[@id='Description']/p/text() Would you object to this idea? If not, off I go. ---benson - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Karma for incubator wiki
Could anybody please grant me write access to the incubator wiki, I need this to fill in the Etch report. My wiki id is MartinVeith. Thanks, Martin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
