Re: Draft Board report for November
Rob Weir wrote: Also maybe something like, In anticipation of additional growth post-graduation, we are developing web pages to support new volunteers, especially in the localization and QA areas Thanks, included. Andrea
Draft Board report for November
In the first three months after graduation a project is supposed to report to the Board on a monthly basis. So our reports will be due in November 2012, in December 2012, and then on a quarterly basis (Jan-Apr-Jul-Oct). I started a first draft of this month's report (which is still using the podling format, since we graduated less than two weeks ago) at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Nov Feel free to edit it. It should cover September 2012 and October 2012. Regards, Andrea.
Re: Draft Board report for November
LGTM, thanks! Regards, Dave On Nov 3, 2012, at 1:14 AM, Andrea Pescetti wrote: In the first three months after graduation a project is supposed to report to the Board on a monthly basis. So our reports will be due in November 2012, in December 2012, and then on a quarterly basis (Jan-Apr-Jul-Oct). I started a first draft of this month's report (which is still using the podling format, since we graduated less than two weeks ago) at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Nov Feel free to edit it. It should cover September 2012 and October 2012. Regards, Andrea.
Re: Draft Board report for November
On Sat, Nov 3, 2012 at 1:14 AM, Andrea Pescetti pesce...@apache.org wrote: In the first three months after graduation a project is supposed to report to the Board on a monthly basis. So our reports will be due in November 2012, in December 2012, and then on a quarterly basis (Jan-Apr-Jul-Oct). I started a first draft of this month's report (which is still using the podling format, since we graduated less than two weeks ago) at https://cwiki.apache.org/**confluence/display/OOOUSERS/**2012+Novhttps://cwiki.apache.org/confluence/display/OOOUSERS/2012+Nov Feel free to edit it. It should cover September 2012 and October 2012. Regards, Andrea. Good that you put it on the wiki. When is the due date? -- MzK Anyone who considers protocol unimportant has never dealt with a cat. -- Robert Heinlein
Re: Draft Board report for November
Kay Schenk wrote: ... https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Nov Feel free to edit it. It should cover September 2012 and October 2012. Good that you put it on the wiki. When is the due date? I received no deadline, since officially we only report on Jan-Apr-Jul-Oct and November-December 2012 are two extra initial reports, so we won't receive reminders for those. However, I plan to send it at the end of next week, 9 November or so. This will be OK, since the report must not be reviewed by the Incubator any longer. Regards, Andrea.
Re: Draft Board report for November
On Sat, Nov 3, 2012 at 6:59 PM, Andrea Pescetti pesce...@apache.org wrote: Kay Schenk wrote: ... https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Nov Feel free to edit it. It should cover September 2012 and October 2012. Good that you put it on the wiki. When is the due date? I received no deadline, since officially we only report on Jan-Apr-Jul-Oct and November-December 2012 are two extra initial reports, so we won't receive reminders for those. However, I plan to send it at the end of next week, 9 November or so. This will be OK, since the report must not be reviewed by the Incubator any longer. Also maybe something like, In anticipation of additional growth post-graduation, we are developing web pages to support new volunteers, especially in the localization and QA areas -Rob Regards, Andrea.
Re: board report for Sept. 20, 2012
On 09/04/2012 09:04 PM, Dennis E. Hamilton wrote: Minor correction: The proposal is at http://wiki.apache.org/incubator/September2012 down the list of reports in their alphabetical order. - Dennis yes, thanks for the correction Dennis and for forging ahead with this Dave. -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Tuesday, September 04, 2012 20:50 To: ooo-dev@incubator.apache.org Cc: orc...@apache.org Subject: Re: board report for Sept. 20, 2012 Hi, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. The report has been moved to the incubator wiki. Please let us know if you think anything should be edited. Regards, Dave [ ... ] -- MzK We never sit anything out. We are cups, constantly and quietly being filled. The trick is, knowing how to tip ourselves over and let the beautiful stuff out. -- Ray Bradbury, Zen in the Art of Writing
Re: board report for Sept. 20, 2012
Sorry, when I'm a bit late with this. Not that it makes a real difference. But in the March and June report it was named OpenOffice (was OpenOffice.org). Now it's again OpenOffice.org. Furthermore, I don't like the formulation We expect to graduate in the next quarter. Maybe it's because I'm not a native speaker but for me it sounds like too much demanding. A sentence like We plan and work to fulfill graduation in the next quarter. fits much better. Of course, my 2 ct. Marcus Am 09/05/2012 11:01 PM, schrieb Kay Schenk: On 09/04/2012 09:04 PM, Dennis E. Hamilton wrote: Minor correction: The proposal is at http://wiki.apache.org/incubator/September2012 down the list of reports in their alphabetical order. - Dennis yes, thanks for the correction Dennis and for forging ahead with this Dave. -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Tuesday, September 04, 2012 20:50 To: ooo-dev@incubator.apache.org Cc: orc...@apache.org Subject: Re: board report for Sept. 20, 2012 Hi, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. The report has been moved to the incubator wiki. Please let us know if you think anything should be edited. Regards, Dave [ ... ]
Re: board report for Sept. 20, 2012
Hi, On Sep 5, 2012, at 2:29 PM, Marcus (OOo) wrote: Sorry, when I'm a bit late with this. Not too late. The mentors have not signed off and the IPMC takes at least a week to review. Not that it makes a real difference. But in the March and June report it was named OpenOffice (was OpenOffice.org). Now it's again OpenOffice.org. Done. Officially in the Incubator records we are OpenOffice.org, but podling name changes are not uncommon. Furthermore, I don't like the formulation We expect to graduate in the next quarter. Maybe it's because I'm not a native speaker but for me it sounds like too much demanding. A sentence like We plan and work to fulfill graduation in the next quarter. fits much better. I changed to We are working to fulfill graduation requirements in the next quarter. Of course, my 2 ct. Worth more than that. Regards, Dave Marcus Am 09/05/2012 11:01 PM, schrieb Kay Schenk: On 09/04/2012 09:04 PM, Dennis E. Hamilton wrote: Minor correction: The proposal is at http://wiki.apache.org/incubator/September2012 down the list of reports in their alphabetical order. - Dennis yes, thanks for the correction Dennis and for forging ahead with this Dave. -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Tuesday, September 04, 2012 20:50 To: ooo-dev@incubator.apache.org Cc: orc...@apache.org Subject: Re: board report for Sept. 20, 2012 Hi, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. The report has been moved to the incubator wiki. Please let us know if you think anything should be edited. Regards, Dave [ ... ]
Re: board report for Sept. 20, 2012
Hi, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. The report has been moved to the incubator wiki. Please let us know if you think anything should be edited. Regards, Dave Regards, Dave On Sep 3, 2012, at 7:07 PM, Dennis E. Hamilton wrote: Reviewing the June report I have this to offer for September: A. COMMUNITY DEVELOPMENT This says there were 13 new Committers/PPMC members and 2 committer/PPMC member resignations. I don't track resignations, and I think it is best to show the baseline (or resulting levels) of those changes. I am assuming that my June 5, 2012 Status was the basis for the numbers in the June 8 report to the IPMC and Board. Comparing that with the report from yesterday, I would say that There are now 110 committers with 72 of those on the PPMC. Relative to the last report, that is an increase of 15 committers and a decrease of 3 committers on the PPMC (following an audit to reconcile subscribers to the ooo-private mailing list). Now the numbers are grounded and the baseline here makes the derivation of details in a further report easy to substantiate. B. A DIFFERENT OVERSIGHT It is stunning that of all the matters that it might be thought the Board might need to be aware of (whether or not called to act on) the only one I've ever noticed is the June statement about leaks from the ooo-private list to outside agencies. Along with that June issue, there is our promise to provide an update in the next report (this one in September 2012) or at least indicate that an update was provided separately. The current draft simply removes any evidence that this issue was raised. I suggest that there needs to be accountability and closure on our part. I paid little attention to that issue. I would suggest that the single leak was identified and the matter has been closed to the satisfaction of the PPMC. - Dennis -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 18:16 To: dennis.hamil...@acm.org Cc: OOo-dev Apache Incubator Subject: Re: board report for Sept. 20, 2012 On Sep 3, 2012, at 5:24 PM, Dennis E. Hamilton wrote: Dave, I don't know what the baseline was for the last report, so I have no idea what the deltas are. Where is the previous report to the IPMC? http://wiki.apache.org/incubator/June2012 It was written June 8. Regards, Dave - Dennis PS: I may have provided that previous data, but it was a while ago [;). -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 16:12 To: ooo-dev@incubator.apache.org Cc: dennis.hamil...@acm.org Hamilton Subject: Re: board report for Sept. 20, 2012 On Sep 2, 2012, at 1:31 PM, Kay Schenk wrote: On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... I made a additional changes as well. I think that the report is overly long and we can lose the detail at the bottom. Dennis - would you confirm the PPMC change statement. Thanks, Dave The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report
RE: board report for Sept. 20, 2012
Minor correction: The proposal is at http://wiki.apache.org/incubator/September2012 down the list of reports in their alphabetical order. - Dennis -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Tuesday, September 04, 2012 20:50 To: ooo-dev@incubator.apache.org Cc: orc...@apache.org Subject: Re: board report for Sept. 20, 2012 Hi, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. The report has been moved to the incubator wiki. Please let us know if you think anything should be edited. Regards, Dave [ ... ]
Incubator PMC/Board report for Sep 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 September 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, Sep 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/September2012 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
Incubator PMC/Board report for Sep 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 September 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, Sep 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/September2012 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
RE: board report for Sept. 20, 2012
Dave, I don't know what the baseline was for the last report, so I have no idea what the deltas are. Where is the previous report to the IPMC? - Dennis PS: I may have provided that previous data, but it was a while ago [;). -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 16:12 To: ooo-dev@incubator.apache.org Cc: dennis.hamil...@acm.org Hamilton Subject: Re: board report for Sept. 20, 2012 On Sep 2, 2012, at 1:31 PM, Kay Schenk wrote: On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... I made a additional changes as well. I think that the report is overly long and we can lose the detail at the bottom. Dennis - would you confirm the PPMC change statement. Thanks, Dave The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Re: board report for Sept. 20, 2012
On Sep 3, 2012, at 5:24 PM, Dennis E. Hamilton wrote: Dave, I don't know what the baseline was for the last report, so I have no idea what the deltas are. Where is the previous report to the IPMC? http://wiki.apache.org/incubator/June2012 It was written June 8. Regards, Dave - Dennis PS: I may have provided that previous data, but it was a while ago [;). -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 16:12 To: ooo-dev@incubator.apache.org Cc: dennis.hamil...@acm.org Hamilton Subject: Re: board report for Sept. 20, 2012 On Sep 2, 2012, at 1:31 PM, Kay Schenk wrote: On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... I made a additional changes as well. I think that the report is overly long and we can lose the detail at the bottom. Dennis - would you confirm the PPMC change statement. Thanks, Dave The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
RE: board report for Sept. 20, 2012
Reviewing the June report I have this to offer for September: A. COMMUNITY DEVELOPMENT This says there were 13 new Committers/PPMC members and 2 committer/PPMC member resignations. I don't track resignations, and I think it is best to show the baseline (or resulting levels) of those changes. I am assuming that my June 5, 2012 Status was the basis for the numbers in the June 8 report to the IPMC and Board. Comparing that with the report from yesterday, I would say that There are now 110 committers with 72 of those on the PPMC. Relative to the last report, that is an increase of 15 committers and a decrease of 3 committers on the PPMC (following an audit to reconcile subscribers to the ooo-private mailing list). Now the numbers are grounded and the baseline here makes the derivation of details in a further report easy to substantiate. B. A DIFFERENT OVERSIGHT It is stunning that of all the matters that it might be thought the Board might need to be aware of (whether or not called to act on) the only one I've ever noticed is the June statement about leaks from the ooo-private list to outside agencies. Along with that June issue, there is our promise to provide an update in the next report (this one in September 2012) or at least indicate that an update was provided separately. The current draft simply removes any evidence that this issue was raised. I suggest that there needs to be accountability and closure on our part. I paid little attention to that issue. I would suggest that the single leak was identified and the matter has been closed to the satisfaction of the PPMC. - Dennis -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 18:16 To: dennis.hamil...@acm.org Cc: OOo-dev Apache Incubator Subject: Re: board report for Sept. 20, 2012 On Sep 3, 2012, at 5:24 PM, Dennis E. Hamilton wrote: Dave, I don't know what the baseline was for the last report, so I have no idea what the deltas are. Where is the previous report to the IPMC? http://wiki.apache.org/incubator/June2012 It was written June 8. Regards, Dave - Dennis PS: I may have provided that previous data, but it was a while ago [;). -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 16:12 To: ooo-dev@incubator.apache.org Cc: dennis.hamil...@acm.org Hamilton Subject: Re: board report for Sept. 20, 2012 On Sep 2, 2012, at 1:31 PM, Kay Schenk wrote: On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... I made a additional changes as well. I think that the report is overly long and we can lose the detail at the bottom. Dennis - would you confirm the PPMC change statement. Thanks, Dave The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write
Re: board report for Sept. 20, 2012
Hi Dennis, Thanks. I've essentially followed your suggestions. I hope that others will review the wiki at https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept before it is moved to http://wiki.apache.org/incubator/June2012 on Wednesday. Regards, Dave On Sep 3, 2012, at 7:07 PM, Dennis E. Hamilton wrote: Reviewing the June report I have this to offer for September: A. COMMUNITY DEVELOPMENT This says there were 13 new Committers/PPMC members and 2 committer/PPMC member resignations. I don't track resignations, and I think it is best to show the baseline (or resulting levels) of those changes. I am assuming that my June 5, 2012 Status was the basis for the numbers in the June 8 report to the IPMC and Board. Comparing that with the report from yesterday, I would say that There are now 110 committers with 72 of those on the PPMC. Relative to the last report, that is an increase of 15 committers and a decrease of 3 committers on the PPMC (following an audit to reconcile subscribers to the ooo-private mailing list). Now the numbers are grounded and the baseline here makes the derivation of details in a further report easy to substantiate. B. A DIFFERENT OVERSIGHT It is stunning that of all the matters that it might be thought the Board might need to be aware of (whether or not called to act on) the only one I've ever noticed is the June statement about leaks from the ooo-private list to outside agencies. Along with that June issue, there is our promise to provide an update in the next report (this one in September 2012) or at least indicate that an update was provided separately. The current draft simply removes any evidence that this issue was raised. I suggest that there needs to be accountability and closure on our part. I paid little attention to that issue. I would suggest that the single leak was identified and the matter has been closed to the satisfaction of the PPMC. - Dennis -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 18:16 To: dennis.hamil...@acm.org Cc: OOo-dev Apache Incubator Subject: Re: board report for Sept. 20, 2012 On Sep 3, 2012, at 5:24 PM, Dennis E. Hamilton wrote: Dave, I don't know what the baseline was for the last report, so I have no idea what the deltas are. Where is the previous report to the IPMC? http://wiki.apache.org/incubator/June2012 It was written June 8. Regards, Dave - Dennis PS: I may have provided that previous data, but it was a while ago [;). -Original Message- From: Dave Fisher [mailto:dave2w...@comcast.net] Sent: Monday, September 03, 2012 16:12 To: ooo-dev@incubator.apache.org Cc: dennis.hamil...@acm.org Hamilton Subject: Re: board report for Sept. 20, 2012 On Sep 2, 2012, at 1:31 PM, Kay Schenk wrote: On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... I made a additional changes as well. I think that the report is overly long and we can lose the detail at the bottom. Dennis - would you confirm the PPMC change statement. Thanks, Dave The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before
Re: board report for Sept. 20, 2012
On 09/01/2012 11:26 AM, Dave Fisher wrote: On Sep 1, 2012, at 9:50 AM, Kay Schenk wrote: On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The report page is ready at http://wiki.apache.org/incubator/September2012 Due on Wednesday Sept. 5. I copied the June report and made some changes to https://cwiki.apache.org/confluence/display/OOOUSERS/2012+Sept There is more to be done. Please feel free to edit. Regards, Dave Thanks for getting this started, Dave. I made a few more changes...some facts need review and, of course, we could always use more input... The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Re: board report for Sept. 20, 2012
On Aug 31, 2012, at 5:48 PM, Dave Fisher wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Actually the due date is September 5. Thanks Kay for starting the process. Regards, Dave The IPMC will review the report. We should be discussing our graduation plans. The report will go here: http://wiki.apache.org/incubator/September2012 when that page is created. With my IPMC hat, Dave On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Re: board report for Sept. 20, 2012
On Fri, Aug 31, 2012 at 5:48 PM, Dave Fisher dave2w...@comcast.net wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Oh my! You are SO right...here is the message from June... http://markmail.org/message/7td2rgws7gnkoxo5 so, this will need to be ready like Sept 6th! WOW! That is very soon. The IPMC will review the report. We should be discussing our graduation plans. absolutely! The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave Thank you for the rather critical correction! On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Re: board report for Sept. 20, 2012
On Sat, Sep 1, 2012 at 6:07 AM, Dave Fisher dave2w...@comcast.net wrote: On Aug 31, 2012, at 5:48 PM, Dave Fisher wrote: We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. Actually the due date is September 5. Thanks Kay for starting the process. Regards, Dave The IPMC will review the report. We should be discussing our graduation plans. The report will go here: http://wiki.apache.org/incubator/September2012when that page is created. With my IPMC hat, Dave On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Re: board report for Sept. 20, 2012
We are not a TLP the board report is to the IPMC and needs to be ready much, much sooner than two days before the board meeting. We need to have this ready by a date like September 12. The IPMC will review the report. We should be discussing our graduation plans. The report will go here: http://wiki.apache.org/incubator/September2012 when that page is created. With my IPMC hat, Dave On Aug 31, 2012, at 4:53 PM, Kay Schenk wrote: In June, we all worked together via e-mail on the Board report to incubator, and I think most of us agreed that worked pretty well. But, I thought we could find a better contribution mechanism rather than e-mail and editing my one person. We have another quarterly report that will be due Sept 20. I've put a new page (empty) on the Planning Wiki containing 2 child pages -- the June report and an empty Sept placeholder. Hopefully, we can use the June report as a template and collectively contribute to the Sept report before its due date of Sept 18 (two days before the Board meeting). Please contribute as you see fit. https://cwiki.apache.org/confluence/display/OOOUSERS/Board+Reports -- MzK A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects. -- Robert Heinlein, Time Enough For Love
Incubator PMC/Board report for Jun 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, 20 June 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, Jun 6th). 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/June2012 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
Re: *DRAFT FINAL* June board report
I'm a little concerned about this idea of AOO being somehow different from other Apache projects. Its not, its just software. In Apache projects everyone is equal. If someone earns merit they earn merit, it makes no difference how that merit is earned. The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad. Note we have a VP who has never written a line of code in their life. As far as I'm aware they have never written a translation string or any documentation. Despite this there was no need to create a new class of community member to bring them into the ASF. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. Ross Sent from my mobile device, please forgive errors and brevity. On Jun 7, 2012 11:30 PM, Kay Schenk kay.sch...@gmail.com wrote: On Thu, Jun 7, 2012 at 9:40 AM, Rob Weir robw...@apache.org wrote: On Thu, Jun 7, 2012 at 6:59 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. The contributor role at Apache already handles this. A contributor can already register in Bugzilla, post patches, register in the wiki, contribute documentation, etc. What a contributor cannot do is directly modify the product code in SVN. So they are in RTC mode with respect to product code, including translations. I think the disconnect here is we only have an anonymous method for contributors to add translations to Pootle. I can see the justification for requiring non-committers to submit translations as patches in BZ or via suggestions in Pootle. But the anonymous part of this is completely wrong, both from community and from legal standpoint. For example, those who
Re: *DRAFT FINAL* June board report
On 08.06.2012 08:58, Ross Gardler wrote: [...] If someone earns merit they earn merit, it makes no difference how that merit is earned. I totally agree and that is exactly why I am concerned about the fast-tracking of committership for procedural reasons and not for merit. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. In JIRA or Bugzilla one doesn't have to be a committer to attach a patch but one has to be logged in. If there were a similar role in https://cwiki.apache.org/INFRA/translate-pootle-service-auth-levels.html there would be no problem. Herbert
Re: *DRAFT FINAL* June board report
On 6/8/12 8:58 AM, Ross Gardler wrote: I'm a little concerned about this idea of AOO being somehow different from other Apache projects. Its not, its just software. In Apache projects everyone is equal. If someone earns merit they earn merit, it makes no difference how that merit is earned. The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad. Note we have a VP who has never written a line of code in their life. As far as I'm aware they have never written a translation string or any documentation. Despite this there was no need to create a new class of community member to bring them into the ASF. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. I agree and Rob pointed already out that we have something like that (what I have proposed) already. In case of Pootle contributions we simply need an open user registration to solve the unknown issue i some way. Pootle allow us to define default rights for users and when we define that translation can be seen or compared with patches it sounds like a good step forward. My idea was mainly that we think about some formalization of this special user registration. Independent of registering for bugzilla, the wiki or Pootle, the user have to agree to contribute everything under ALv2. Sorry for the confusion Juergen Ross Sent from my mobile device, please forgive errors and brevity. On Jun 7, 2012 11:30 PM, Kay Schenk kay.sch...@gmail.com wrote: On Thu, Jun 7, 2012 at 9:40 AM, Rob Weir robw...@apache.org wrote: On Thu, Jun 7, 2012 at 6:59 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. The contributor role at Apache already handles this. A contributor can already register in Bugzilla, post patches, register in the wiki, contribute
Re: *DRAFT FINAL* June board report
Hi Ross, *, On Fri, Jun 08, 2012 at 07:58:25AM +0100, Ross Gardler wrote: I'm a little concerned about this idea of AOO being somehow different from other Apache projects. I agree. Its not, its just software. In Apache projects everyone is equal. If someone earns merit they earn merit, it makes no difference how that merit is earned. The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad. Note we have a VP who has never written a line of code in their life. As far as I'm aware they have never written a translation string or any documentation. Despite this there was no need to create a new class of community member to bring them into the ASF. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. IMHO the issue is not in the Apache Way of doing things, but in how the Pootle server works (or was set up). The most clear example is the CMS: you can make modifications and send a patch from within the CMS without being a committer: http://www.apache.org/dev/cmsref.html#non-committer You log-in as anonymous user, but when mailing the diff you can identify yourself. Something similar could be implemented in pootle. Regards -- Ariel Constenla-Haile La Plata, Argentina pgp9h7Ti6ovYM.pgp Description: PGP signature
Re: *DRAFT FINAL* June board report
On 6/8/12 1:55 PM, Ariel Constenla-Haile wrote: Hi Ross, *, On Fri, Jun 08, 2012 at 07:58:25AM +0100, Ross Gardler wrote: I'm a little concerned about this idea of AOO being somehow different from other Apache projects. I agree. Its not, its just software. In Apache projects everyone is equal. If someone earns merit they earn merit, it makes no difference how that merit is earned. The issue here should not be a different class of contributor it should be how to facilitate a different type of contribution and thus bootstrap their involvement in the project. Please don't create an artificial layer of hierarchy in order to do that. Hierarchy in an open development project is bad. Note we have a VP who has never written a line of code in their life. As far as I'm aware they have never written a translation string or any documentation. Despite this there was no need to create a new class of community member to bring them into the ASF. I propose the problem is in the workflow not in the structure of ASF projects. If that is the case then we need to examine why non-committer translators are unable to contribute efficiently. Find out why our default policies say they need to be committees and address that issue. For example, are contributions to Pootle any different to patches sent via JIR# from an IP point of view? If not then there is no need for an ICLA but there is a need for an audit trail. IMHO the issue is not in the Apache Way of doing things, but in how the Pootle server works (or was set up). The most clear example is the CMS: you can make modifications and send a patch from within the CMS without being a committer: http://www.apache.org/dev/cmsref.html#non-committer You log-in as anonymous user, but when mailing the diff you can identify yourself. Something similar could be implemented in pootle. I would say Pootle has everything that is needed. We would only need a mechanism to allow user registration as non committer, as possible for bugzilla or the wiki. More fine grained rights can we define and set per project in Pootle. This way way we can make sure that in case of AOO registered users can make suggestions. Other projects can handle it differently. The patch mechanism here is to make suggestions as a known person. Juergen Regards
Re: *DRAFT FINAL* June board report
On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. Thanks for highlighting it. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: *DRAFT FINAL* June board report
On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. Juergen
Re: *DRAFT FINAL* June board report
On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Juergen
Re: *DRAFT FINAL* June board report
On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: *DRAFT FINAL* June board report
On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. The difference between contributors and committers would be that only committers get the @apache.org email address. I think that a such lightweight user could be useful and the license question of their contributions would be clear form the beginning. Juergen
Re: *DRAFT FINAL* June board report
On Thu, Jun 7, 2012 at 3:59 AM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. You are a wise guy, Juergen! I also agree that a more refined contributor vs committer category is needed for cases just like this. And in this project, we may have quite a few! The difference between contributors and committers would be that only committers get the @apache.org email address. I think that a such lightweight user could be useful and the license question of their contributions would be clear form the beginning. I would also like to add a distinction such as this which would grant certain rights to contributors as you describe above but without svn access -- and thus also the lack of @apache.org. It's been a *while* since I had anything to do with the innards of LDAP and groups, but I feel confident these kinds of access distinctions can be handled this way. Especially with Pootle, as more folks are interested in this aspect, preventing them from directly accessing services is non-optimal to say the very least. thanks for bringing this up. Juergen -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT FINAL* June board report
On Thu, Jun 7, 2012 at 6:59 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. The contributor role at Apache already handles this. A contributor can already register in Bugzilla, post patches, register in the wiki, contribute documentation, etc. What a contributor cannot do is directly modify the product code in SVN. So they are in RTC mode with respect to product code, including translations. I think the disconnect here is we only have an anonymous method for contributors to add translations to Pootle. I can see the justification for requiring non-committers to submit translations as patches in BZ or via suggestions in Pootle. But the anonymous part of this is completely wrong, both from community and from legal standpoint. For example, those who contribute to Pootle, anonymously, see their contributions marked as being from nobody in the UI: https://translate.apache.org/projects/OOo_34/ Isn't that rather insulting? It also makes it very difficult for the PMC to do their job, since we cannot effectively track top contributors and nominate them for committership of the work is all by nobody. From legal perspective, we're failing to track where our contributions are coming from. We're losing the provenance of the translations by not associating translation contributions with a user ID/email address. -Rob The difference between contributors and committers would be that only committers get the @apache.org email address. I think that a such lightweight user could be useful and the license question of their contributions would be clear form the beginning. Juergen
Re: *DRAFT FINAL* June board report
On Thu, Jun 7, 2012 at 9:40 AM, Rob Weir robw...@apache.org wrote: On Thu, Jun 7, 2012 at 6:59 AM, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 12:10 PM, Ross Gardler wrote: On 7 June 2012 11:02, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:54 AM, Ross Gardler wrote: On 7 June 2012 10:47, Jürgen Schmidt jogischm...@googlemail.com wrote: On 6/7/12 11:28 AM, Ross Gardler wrote: On 7 June 2012 05:50, Herbert Duerr h...@apache.org wrote: ... I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. No, need, that's not a board level issue. It's up to the project to define its own expectations of committers. it's a very bad limitation. I would prefer a user management which allows registration (by email verification) of new users and where new users agree to contribute under the Apache license. Maybe combined with an iCLA but not necessarily require to be committer. But I am not sure if something like that would be possible at all. Otherwise we have to deal with the current approach and hope that we can reach volunteers to accept this approach and work together with them on a fast-track. I agree that the limitation suboptimal. I suggest someone take this up with legal-discuss@ If legal@ feel able to approve a more relaxed approach to iCLAs for access to Pootle then infra@ can be asked to find a technical solution. I agree and thanks to remind me that I should take the appropriate action to address things like that ;-) Careful with the I - madness lies that way ;-) This is the perfect opportunity for someone lurking here to make an early and potentially very significant contribution. Shepherding these kinds of actions takes time away from those embedded in the coding. It's a good way to earn merit while you figure out where to contribute to the project. If someone like that is reading but not sure how to proceed I'm sure others will help guide you. I agree but the idea is not really new and nothing happened so far ;-) Thinking more about it I would like to discuss a new term Apache contributor where users can register for an user account by accepting that all their contributions are under ALv2. The verification can be by email verification and the iCLA can be required as well (details have to be defined). With such accounts people would get access to more pubic wikis (like our user wiki), tools like Pootle, bugzilla etc. The contributor role at Apache already handles this. A contributor can already register in Bugzilla, post patches, register in the wiki, contribute documentation, etc. What a contributor cannot do is directly modify the product code in SVN. So they are in RTC mode with respect to product code, including translations. I think the disconnect here is we only have an anonymous method for contributors to add translations to Pootle. I can see the justification for requiring non-committers to submit translations as patches in BZ or via suggestions in Pootle. But the anonymous part of this is completely wrong, both from community and from legal standpoint. For example, those who contribute to Pootle, anonymously, see their contributions marked as being from nobody in the UI: https://translate.apache.org/projects/OOo_34/ Isn't that rather insulting? yes, it is...I thought Juergen was suggesting that some special submission access if you will be granted to the Pootle server. What I see here are some non-standard submissions in the Apache sense emerging in OpenOffice. I was alluding to this in a post I made the other day, but didn't specify anything. Using the Pootle server is a perfect example of such a case. We need to take this to its own thread sometime soon I think -- maybe after graduation? -- and see what can be done. I can't imagine that some new methods can't be enacted. It also makes it very difficult for the PMC to do their job, since we cannot effectively track top contributors and nominate them for committership of the work is all by nobody. From legal perspective, we're failing to track where our contributions are coming from. yes, I brought this up as well...it's a concern. We're losing the provenance of the translations by not associating translation contributions with a user ID/email address. No argument here... -Rob The difference between contributors and committers would be that only committers get the @apache.org email address. I think that a such lightweight user could be useful and the license question of their contributions would be clear form the beginning. Juergen --
Re: *DRAFT* June board report...please help
Kay Schenk wrote: - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Six plus source: Windows, Mac, Linux 32-bit RPM, Linux 32-bit DEB, Linux 64-bit RPM, Linux 64-bit DEB. Regards, Andrea.
Re: *DRAFT* June board report...please help
On 06/05/2012 11:35 PM, Andrea Pescetti wrote: Kay Schenk wrote: - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Six plus source: Windows, Mac, Linux 32-bit RPM, Linux 32-bit DEB, Linux 64-bit RPM, Linux 64-bit DEB. Thanks Andrea -- apparently my eyes are failing me! :( Regards, Andrea. -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT* June board report...please help
On 06/05/2012 05:34 PM, Ross Gardler wrote: On 6 June 2012 01:20, Kay Schenkkay.sch...@gmail.com wrote: On Tue, Jun 5, 2012 at 5:06 PM, Ross Gardlerrgard...@opendirective.comwrote: On 6 June 2012 00:14, Kay Schenkkay.sch...@gmail.com wrote: OK, here is the latest revision--and guess what, after some digging, I found the SPI deal is done! YAY! Hold up... http://permalink.gmane.org/gmane.comp.apache.incubator.ooo.devel/16846 Sorry to disappoint. The cheque mentioned in that post was cancelled due to the change in chair of Fundraising and further questions being asked here in the ASF. See http://article.gmane.org/gmane.comp.apache.incubator.ooo.devel/16845/match=schultheiss Unfortunately my note about further questions overlapped with the cheque notification otherwise I would have kept my mouth shut and returned the money if approval had not been given. Sometimes email and a rotating planet work against us... Ross Ross...this coupled with your earlier comment... There is certainly improvement but still the SPI issue is not resolved, calling that out explicitly makes me thing the PPMC is unaware of activity on this issue. This is falling between the cracks, partly because a change in VP fundraising resulted in a further delay after the issue seemed to be resolved on the SPI side. However, the item was raised at the last board meeting and everything should now be cleared up. I have it on my todo list to close this off, but that would not be the PPMC being self-managing and nobody here has asked me what needs to be done still (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). OK, in my mind, the PPMC *was* self-managing in addressing this initially, and the post I referenced. So, I will need to modify this comment in some way that makes sense. a confusing set of events... http://comments.gmane.org/gmane.comp.apache.incubator.ooo.devel/16759 Ross Ross -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT* June board report...please help
On 06/05/2012 05:26 PM, Rob Weir wrote: On Tue, Jun 5, 2012 at 4:34 PM, Kay Schenkkay.sch...@gmail.com wrote: OK, here's a draft -- Dennis is working on getting me actual people numbers later today, so what I have here in terms of new committers is just a (bad) guess. And, duh -- we only report in March, June, September, December, so what I have here in terms of what we've been doing since March is probably way, way off... Please update as you see fit! I now have an incubator wiki account so I will happily post when we're done == proposed June AOO report == *Project Name and Brief Description* OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations have supported 110 languages worldwide. * Most Important Items To Address Toward Graduation * 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work oncommunity readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community It seems odd to have a list that large and say that we're about to start a graduation vote. OK, I don't get your meaning here... My impression was we're really only working on #1, and Andre and Pedro seem to have those under control. #2 and #3 are ongoing activities, before and after graduation, for us and any other Apache project. we had #3 in the March report, so I just left it. I put in #2, because this is a point in the preparing for graduation document, and goes to how well we operate as a group. The reason I included it was twofold: to give communication style/interoperability more attention by us; and to make sure the incubator board knows we think this is important. But I don't think we have any graduation blocking issues there. no...it's just a awareness list. We have started preliminary discussion concerning graduation, and are putting renewed emphasis on the above items as we would like to propose graduation within the next month. * Issues for IPMC or ASF Board Awareness * - None * Community Development Progress * - Since our last report we have voted in 5 (?) new Committers/PPMC members. - Since our last report, one committer/PPMC member has resigned - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of our latest release 3.4. This decision was arrived after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are putting more effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaiing now abandoned former native-language project web sites. I'd word that as, 'We are increasing our global reach by recruiting volunteers to help update and maintain the large set of legacy native language home pages ok -- will do * Project Development Progress * - We released Apache OpenOffice 3.4 on May 8, 2012. Over three million downloads in the first month. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline We would like to publicly acknowledge the efforts of our mentors, the Apache infrastructure team, and the wonderful folks at SourceForge in making this release a success! - We are currently working on an alternate repository for category-B code to comply with graduation requirements - Prepartion was made in May for importing IBM Symphony changes into the OpenOffice repository Maybe first say an SGA was received from IBM for IBM Lotus Symphony, and now are preparing to import... ok... This should be complete by the time of the June board meeting. - Work is continuing on making translation processes easier for volunteers. Currently, only committers can access the Pootel server. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - need and update on this one and the mailing list
Re: *DRAFT* June board report...please help
On 06/05/2012 08:36 PM, Kevin Grignon wrote: KG01 - See comments inline. Kay, thanks for putting this information together. On Wed, Jun 6, 2012 at 8:26 AM, Rob Weirrobw...@apache.org wrote: On Tue, Jun 5, 2012 at 4:34 PM, Kay Schenkkay.sch...@gmail.com wrote: OK, here's a draft -- Dennis is working on getting me actual people numbers later today, so what I have here in terms of new committers is just a (bad) guess. And, duh -- we only report in March, June, September, December, so what I have here in terms of what we've been doing since March is probably way, way off... Please update as you see fit! I now have an incubator wiki account so I will happily post when we're done == proposed June AOO report == *Project Name and Brief Description* OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations have supported 110 languages worldwide. * Most Important Items To Address Toward Graduation * 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community It seems odd to have a list that large and say that we're about to start a graduation vote. My impression was we're really only working on #1, and Andre and Pedro seem to have those under control. #2 and #3 are ongoing activities, before and after graduation, for us and any other Apache project. But I don't think we have any graduation blocking issues there. We have started preliminary discussion concerning graduation, and are putting renewed emphasis on the above items as we would like to propose graduation within the next month. * Issues for IPMC or ASF Board Awareness * - None * Community Development Progress * - Since our last report we have voted in 5 (?) new Committers/PPMC members. - Since our last report, one committer/PPMC member has resigned - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of our latest release 3.4. This decision was arrived after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are putting more effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaiing now abandoned former native-language project web sites. KG01 - Re 3. Increase size and diversity of the active development community, perhaps we could acknowledge that we are working to re-invigorate the user experience design effort. Software is for people, and we should show that we are working hard to understand who is user our product, why and for what, and how we will work to deliver the best experience possible to support our users. We don't just make code software, we design great products that align with our client's view of success - that is a design activity. My feedback here is too wordy, please include anything that acknowledges effort in user research and design of our products would be great. you got it! I'll include something on this! I'd word that as, 'We are increasing our global reach by recruiting volunteers to help update and maintain the large set of legacy native language home pages * Project Development Progress * - We released Apache OpenOffice 3.4 on May 8, 2012. Over three million downloads in the first month. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline We would like to publicly acknowledge the efforts of our mentors, the Apache infrastructure team, and the wonderful folks at SourceForge in making this release a success! - We are currently working on an alternate repository for category-B code to comply with graduation requirements - Prepartion was made in May for importing IBM Symphony changes into the OpenOffice repository Maybe first say an SGA was received from IBM for IBM Lotus Symphony, and now are preparing to import... This should be complete by the time
*DRAFT FINAL* June board report
OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular with users but registration seems to have stabilized. The ooo-users list also is quite active. As Apache OpenOffice is a client product, we continue to investigate ways to direct users to appropriate support venues. - The developer list, ooo-dev, now has 409 subscribers and is very active with post averaging about 100 per day -- MzK Everything will be all
Re: *DRAFT* June board report...please help
Yes, I agree the funding thing is confusing. It is a situation that the ASF is not set up to manage, and one that probably won't happen again. That being said, someone in the PPMC needs to own these things. I'm aware of their status, so it is possible, but it would seem nobody else is tracking each step as things gradually move forwards. Of course, we are all volunteers here, I'm not blaming anyone just highlighting some of the problems a volunteer organisation needs to address. Ross Sent from my mobile device, please forgive errors and brevity. On Jun 6, 2012 6:16 PM, Kay Schenk kay.sch...@gmail.com wrote: On 06/05/2012 11:35 PM, Andrea Pescetti wrote: Kay Schenk wrote: - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Six plus source: Windows, Mac, Linux 32-bit RPM, Linux 32-bit DEB, Linux 64-bit RPM, Linux 64-bit DEB. Thanks Andrea -- apparently my eyes are failing me! :( Regards, Andrea. -- --**--** MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT FINAL* June board report
Sorry I'm late, here are 2 points maybe worth adding: - Spam has been completely eradicated from community English forum with new counter measures (new users moderation and new moderators). - A new root admin (imacat) has been promoted and is now taking the job to insure smooth running and consistency with infra requirements. Hagar Le mer. 06 juin 2012 20:13:14 CEST, Kay Schenk kay.sch...@gmail.com a écrit : OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular
Re: *DRAFT FINAL* June board report
Hagar -- SUPER! and thanks On Wed, Jun 6, 2012 at 12:37 PM, Hagar Delest hagar.del...@laposte.netwrote: Sorry I'm late, here are 2 points maybe worth adding: - Spam has been completely eradicated from community English forum with new counter measures (new users moderation and new moderators). - A new root admin (imacat) has been promoted and is now taking the job to insure smooth running and consistency with infra requirements. Hagar Le mer. 06 juin 2012 20:13:14 CEST, Kay Schenk kay.sch...@gmail.com a écrit : OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later ==**==**= Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/**projects/openofficeorg.mirror/** files/stats/timelinehttp://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service
Re: *DRAFT* June board report...please help
On Wed, Jun 6, 2012 at 11:36 AM, Ross Gardler rgard...@opendirective.comwrote: Yes, I agree the funding thing is confusing. It is a situation that the ASF is not set up to manage, and one that probably won't happen again. That being said, someone in the PPMC needs to own these things. I'm aware of their status, so it is possible, but it would seem nobody else is tracking each step as things gradually move forwards. Of course, we are all volunteers here, I'm not blaming anyone just highlighting some of the problems a volunteer organisation needs to address. Ross got it! I'll look at the postings again...obviously some mis-communication or expected communication (to the PPMC) that never came. Sent from my mobile device, please forgive errors and brevity. On Jun 6, 2012 6:16 PM, Kay Schenk kay.sch...@gmail.com wrote: On 06/05/2012 11:35 PM, Andrea Pescetti wrote: Kay Schenk wrote: - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Six plus source: Windows, Mac, Linux 32-bit RPM, Linux 32-bit DEB, Linux 64-bit RPM, Linux 64-bit DEB. Thanks Andrea -- apparently my eyes are failing me! :( Regards, Andrea. -- --**--** MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT FINAL* June board report
Am 06/06/2012 08:13 PM, schrieb Kay Schenk: OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular with users but registration seems to have stabilized. The ooo-users list also is quite active. As Apache OpenOffice is a client product, we continue to investigate ways to direct users to appropriate support venues. - The developer list, ooo-dev, now has 409 subscribers and is very active with post averaging about 100 per day Thanks a lot for volunteering to create the report and taking care of all the details and fine points. Marcus
Re: *DRAFT FINAL* June board report
Am 06/06/2012 09:37 PM, schrieb Hagar Delest: Sorry I'm late, here are 2 points maybe worth adding: - Spam has been completely eradicated from community English forum with new counter measures (new users moderation and new moderators). - A new root admin (imacat) has been promoted and is now taking the job to insure smooth running and consistency with infra requirements. Yes, IMHO an important detail. Marcus Le mer. 06 juin 2012 20:13:14 CEST, Kay Schenk kay.sch...@gmail.com a écrit : OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular with users but registration seems to have stabilized. The ooo-users list also is quite active. As Apache OpenOffice is a client product, we
Re: *DRAFT FINAL* June board report
On Jun 6, 2012, at 1:19 PM, Marcus (OOo) wrote: Am 06/06/2012 08:13 PM, schrieb Kay Schenk: OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular with users but registration seems to have stabilized. The ooo-users list also is quite active. As Apache OpenOffice is a client product, we continue to investigate ways to direct users to appropriate support venues. - The developer list, ooo-dev, now has 409 subscribers and is very active with post averaging about 100 per day Thanks a lot for volunteering to create the report and taking care of all the details and fine
needs mentor signoff: Re: *DRAFT FINAL* June board report
On Wed, Jun 6, 2012 at 1:49 PM, Dave Fisher dave2w...@comcast.net wrote: On Jun 6, 2012, at 1:19 PM, Marcus (OOo) wrote: Am 06/06/2012 08:13 PM, schrieb Kay Schenk: OK -- I hope this is the final. Rob -- I did see what you meant on the grad issues so I changed this a bit...and my spell checker was not functioning before so hopefully better now. Thanks for all the feedback. back later...again, formatting will be corrected later = Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness especially with regard to organization and communication style. We have started preliminary discussion concerning graduation as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 13 new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to initiate transfer of SPI funds formerly earmarked for OpenOffice.org to the ASF. However, due to changes in the ASF Fundraising chair, this transfer has been postponed. Followup with ASF Fundraising is needed to complete this transaction. These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consultation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accommodate and track these requests is becoming an important concern. - We are increasing our global reach by recruiting volunteers to help update and maintain the large set of native language home pages - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Six different client platform install versions in 15 languages Source tarballs in English Software development kit packaging for 5 platforms Language packs for 15 languages Over 3 million downloads the first month. A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirements - An SGA was received from IBM for IBM Lotus Symphony. We are now preparing to import IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - We are putting renewed effort into the user experience. Apache OpenOffice is an end-user product, the best quality product and best experience for end users is one of our primary goals. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - Community support forums remain popular with users but registration seems to have stabilized. The ooo-users list also is quite active. As Apache OpenOffice is a client product, we continue to investigate ways to direct users to appropriate support venues. - The developer list, ooo-dev, now has 409
Re: *DRAFT FINAL* June board report
On 06/06/2012 08:13 PM, Kay Schenk wrote: OK -- I hope this is the final. Very good, thank you very much for working on it. Issues for IPMC or ASF Board Awareness I think we maybe should add one more topic here: Working with pootle currently requires committership, which results in translators having having to be fast-tracked when they show up on the mailing list. The board needs to decide if this short-circuiting of the process is desirable or not and what the alternatives are. Herbert
Re: Incubator PMC/Board report for Jun 2012 ([ppmc])
On 6/5/12 1:14 AM, Kay Schenk wrote: Top posting-- Folks, I will note that we apparently didn't submit a report for May -- I guess we were all too busy with the release. So...this is due this coming Wed, June 6th. I will help if I can. We could at least mention that we're starting the discussion on graduation. And, get them caught up on our new committers and PPMC members. we had a first release, worth to mention ;-) Juergen On Sun, Jun 3, 2012 at 6:11 PM, Marvin no-re...@apache.org wrote: 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, 20 June 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, Jun 6th). 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/June2012 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
Re: Incubator PMC/Board report for Jun 2012 ([ppmc])
On Tue, Jun 5, 2012 at 1:03 AM, Jürgen Schmidt jogischm...@googlemail.comwrote: On 6/5/12 1:14 AM, Kay Schenk wrote: Top posting-- Folks, I will note that we apparently didn't submit a report for May -- I guess we were all too busy with the release. So...this is due this coming Wed, June 6th. I will help if I can. We could at least mention that we're starting the discussion on graduation. And, get them caught up on our new committers and PPMC members. we had a first release, worth to mention ;-) Juergen ya think! ;) yes, definitely :) On Sun, Jun 3, 2012 at 6:11 PM, Marvin no-re...@apache.org wrote: 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, 20 June 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, Jun 6th). 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/June2012 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 -- MzK So let it rock, let it roll Let the bible belt come and save my soul Hold on to sixteen as long as you can Changes come around real soon make us woman and men. -- Jack and Diane, John Mellencamp
*DRAFT* June board report...please help
OK, here's a draft -- Dennis is working on getting me actual people numbers later today, so what I have here in terms of new committers is just a (bad) guess. And, duh -- we only report in March, June, September, December, so what I have here in terms of what we've been doing since March is probably way, way off... Please update as you see fit! I now have an incubator wiki account so I will happily post when we're done == proposed June AOO report == *Project Name and Brief Description* OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations have supported 110 languages worldwide. * Most Important Items To Address Toward Graduation * 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community We have started preliminary discussion concerning graduation, and are putting renewed emphasis on the above items as we would like to propose graduation within the next month. * Issues for IPMC or ASF Board Awareness * - None * Community Development Progress * - Since our last report we have voted in 5 (?) new Committers/PPMC members. - Since our last report, one committer/PPMC member has resigned - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of our latest release 3.4. This decision was arrived after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are putting more effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaiing now abandoned former native-language project web sites. * Project Development Progress * - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline We would like to publicly acknowledge the efforts of our mentors, the Apache infrastructure team, and the wonderful folks at SourceForge in making this release a success! - We are currently working on an alternate repository for category-B code to comply with graduation requirements - Prepartion was made in May for importing IBM Symphony changes into the OpenOffice repository This should be complete by the time of the June board meeting. - Work is continuing on making translation processes easier for volunteers. Currently, only committers can access the Pootel server. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - need and update on this one and the mailing list numbers!!: Community support forums remain popular with users, hitting a new concurrency record (296) -- MzK So let it rock, let it roll Let the bible belt come and save my soul Hold on to sixteen as long as you can Changes come around real soon make us woman and men. -- Jack and Diane, John Mellencamp
Re: *DRAFT* June board report...please help
On 5 June 2012 21:34, Kay Schenk kay.sch...@gmail.com wrote: * Issues for IPMC or ASF Board Awareness * - None What about the possibility of leaks and the damage this might do to the community? You may have omitted it because you feel it is being handled OK and that there is nothing really to report at this stage. If that is the case then I would say that. The goal here is to give a heads up to the IPMC/Board that there is a serious issue and that it is being dealt with internally. If it is not resolved to the communities satisfaction and escalation is the first the IPMC/Board hear of this that will be considered bad form. You may also have omitted it because you are aware the IPMC and Board are already informed. This is true, but the board report is an opportunity for those who are not satisfied with progress to raise further issues and, if they so wish, escalate. I therefore try and include all items that cause significant tension. Furthermore, it is not uncommon for the board to ask a PMC chair to provide more information if something like this is not included in a report (a board member will often scan lists during review). They don't want to have to do detective work but if it looks like an issue is being ignored they will seek clarification. Note, the board reports are public so be sparing with details. The IPMC/Board has access to the private archives if they want details. From my last update to this list I think you could say: Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). There is certainly improvement but still the SPI issue is not resolved, calling that out explicitly makes me thing the PPMC is unaware of activity on this issue. This is falling between the cracks, partly because a change in VP fundraising resulted in a further delay after the issue seemed to be resolved on the SPI side. However, the item was raised at the last board meeting and everything should now be cleared up. I have it on my todo list to close this off, but that would not be the PPMC being self-managing and nobody here has asked me what needs to be done still (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). You probably also want to mention that the PPMC is starting to plan for graduation. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: *DRAFT* June board report...please help
On Tue, Jun 5, 2012 at 6:22 PM, Ross Gardler rgard...@opendirective.com wrote: (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). Suggestion: specify what the funds would be used for. I see prior mention of planning for an event. If so, that would be ideal, as that would increase the chance of the request being approved. - Sam Ruby
Re: *DRAFT* June board report...please help
On Tue, Jun 5, 2012 at 3:22 PM, Ross Gardler rgard...@opendirective.comwrote: On 5 June 2012 21:34, Kay Schenk kay.sch...@gmail.com wrote: * Issues for IPMC or ASF Board Awareness * - None What about the possibility of leaks and the damage this might do to the community? You may have omitted it because you feel it is being handled OK and that there is nothing really to report at this stage. If that is the case then I would say that. The goal here is to give a heads up to the IPMC/Board that there is a serious issue and that it is being dealt with internally. If it is not resolved to the communities satisfaction and escalation is the first the IPMC/Board hear of this that will be considered bad form. You may also have omitted it because you are aware the IPMC and Board are already informed. This was my assumption but I don't know that for sure. I will be happy to include the leak business. This is true, but the board report is an opportunity for those who are not satisfied with progress to raise further issues and, if they so wish, escalate. I therefore try and include all items that cause significant tension. Furthermore, it is not uncommon for the board to ask a PMC chair to provide more information if something like this is not included in a report (a board member will often scan lists during review). They don't want to have to do detective work but if it looks like an issue is being ignored they will seek clarification. Note, the board reports are public so be sparing with details. yes, I know this... The IPMC/Board has access to the private archives if they want details. From my last update to this list I think you could say: Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. I will include your wording on this. Thank you. - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). There is certainly improvement but still the SPI issue is not resolved, calling that out explicitly makes me thing the PPMC is unaware of activity on this issue. This is falling between the cracks, partly because a change in VP fundraising resulted in a further delay after the issue seemed to be resolved on the SPI side. However, the item was raised at the last board meeting and everything should now be cleared up. I have it on my todo list to close this off, but that would not be the PPMC being self-managing and nobody here has asked me what needs to be done still (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). You probably also want to mention that the PPMC is starting to plan for graduation. Well I did mention that we were in the discussion stage on this, but I can be more explicit. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com Thanks for your comments, Ross. Much appreciated. -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT* June board report...please help
On Tue, Jun 5, 2012 at 3:33 PM, Sam Ruby ru...@intertwingly.net wrote: On Tue, Jun 5, 2012 at 6:22 PM, Ross Gardler rgard...@opendirective.com wrote: (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). Suggestion: specify what the funds would be used for. I see prior mention of planning for an event. If so, that would be ideal, as that would increase the chance of the request being approved. - Sam Ruby OK, thanks. -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT* June board report...please help
On Jun 5, 2012, at 4:14 PM, Kay Schenk wrote: On Tue, Jun 5, 2012 at 3:33 PM, Sam Ruby ru...@intertwingly.net wrote: On Tue, Jun 5, 2012 at 6:22 PM, Ross Gardler rgard...@opendirective.com wrote: (if someone could pick this up I'd be grateful, just mail fundrais...@apache.org and ask if we are clear to have SPI transfer funds). Suggestion: specify what the funds would be used for. I see prior mention of planning for an event. If so, that would be ideal, as that would increase the chance of the request being approved. - Sam Ruby OK, thanks. With these suggested changes - well done Kay! Regards, Dave -- MzK Everything will be all right in the end... if it's not all right then it's not the end. -- Sonny, The Best Exotic Marigold Hotel
Re: *DRAFT* June board report...please help
On 6 June 2012 00:14, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Jun 5, 2012 at 3:22 PM, Ross Gardler rgard...@opendirective.comwrote: ... You probably also want to mention that the PPMC is starting to plan for graduation. Well I did mention that we were in the discussion stage on this, but I can be more explicit. I missed it, not sure if that was my rush to give you feedback or whether it needs to be more explicit - your call on that one. Oh, and I forgot to say thank you for picking this up. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: *DRAFT* June board report...please help
On Tue, Jun 5, 2012 at 5:06 PM, Ross Gardler rgard...@opendirective.comwrote: On 6 June 2012 00:14, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Jun 5, 2012 at 3:22 PM, Ross Gardler rgard...@opendirective.com wrote: ... You probably also want to mention that the PPMC is starting to plan for graduation. Well I did mention that we were in the discussion stage on this, but I can be more explicit. I missed it, not sure if that was my rush to give you feedback or whether it needs to be more explicit - your call on that one. Well we are still basically in the discussion stage at this point. So, I think this is sufficient. Oh, and I forgot to say thank you for picking this up. Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com OK, here is the latest revision--and guess what, after some digging, I found the SPI deal is done! YAY! and Dave, thank you...we have been REALLY busy since March! centuries in AOO time! I should get some actual numbers re committers from Dennis soonish. The formatting is a mess here but it should come out better for the wiki post. = June Board Report Project Name and Brief Description: OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations support have supported 110 languages worldwide. Most Important Items To Address Toward Graduation: 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community We have started preliminary discussion concerning graduation, and are putting renewed emphasis on these items as we would like to propose graduation within the next month. Issues for IPMC or ASF Board Awareness - Leaks from ooo-private to outside agencies Possible leaks of information from the ooo-private email list are being investigated. Our first objective is to first establish if and how leaks occurred. Once full details are available we will be working to address the issue directly. No action is currently required from the board and an update will be provided, at the latest, in our next report. Community Development/Outreach Progress - Since our last report we have voted in 7 (?) new Committers/PPMC members. - Since our last report, 2 committer/PPMC members have resigned - We have improved to act more as a self organized project to address and solve project related topics (e.g. forum moderation) - We were able to successfully transfer SPI funds formerly earmarked for OpenOffice.org to the ASF. See permalink: http://permalink.gmane.org/gmane.comp.apache.incubator.ooo.devel/16846 These funds, as previously discussed, will primarily be used for developer travel when needed. - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of latest release 3.4. This event was accomplished after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are more putting effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaing now abandoned former native-language project web sites. - Established various social programming accounts for additional outreach: Twitter, Google+, Facebook - Setup two additional native language mailing lists Project Development Progress - Pootle services for the project were established and used. Translation services will be ongoing as new contributors for this service join. - We released Apache OpenOffice 3.4 on May 8, 2012. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline - We are currently working on an alternate repository for category-B code to comply with graduation requirement - Prepartion was made for importing IBM Symphony chages into the OpenOffice repository This should be complete by the time of the June board meeting. - Testing and implementation of old update service for OpenOffice has been accomplished. This service
Re: *DRAFT* June board report...please help
On Tue, Jun 5, 2012 at 4:34 PM, Kay Schenk kay.sch...@gmail.com wrote: OK, here's a draft -- Dennis is working on getting me actual people numbers later today, so what I have here in terms of new committers is just a (bad) guess. And, duh -- we only report in March, June, September, December, so what I have here in terms of what we've been doing since March is probably way, way off... Please update as you see fit! I now have an incubator wiki account so I will happily post when we're done == proposed June AOO report == *Project Name and Brief Description* OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations have supported 110 languages worldwide. * Most Important Items To Address Toward Graduation * 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community It seems odd to have a list that large and say that we're about to start a graduation vote. My impression was we're really only working on #1, and Andre and Pedro seem to have those under control. #2 and #3 are ongoing activities, before and after graduation, for us and any other Apache project. But I don't think we have any graduation blocking issues there. We have started preliminary discussion concerning graduation, and are putting renewed emphasis on the above items as we would like to propose graduation within the next month. * Issues for IPMC or ASF Board Awareness * - None * Community Development Progress * - Since our last report we have voted in 5 (?) new Committers/PPMC members. - Since our last report, one committer/PPMC member has resigned - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of our latest release 3.4. This decision was arrived after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are putting more effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaiing now abandoned former native-language project web sites. I'd word that as, 'We are increasing our global reach by recruiting volunteers to help update and maintain the large set of legacy native language home pages * Project Development Progress * - We released Apache OpenOffice 3.4 on May 8, 2012. Over three million downloads in the first month. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline We would like to publicly acknowledge the efforts of our mentors, the Apache infrastructure team, and the wonderful folks at SourceForge in making this release a success! - We are currently working on an alternate repository for category-B code to comply with graduation requirements - Prepartion was made in May for importing IBM Symphony changes into the OpenOffice repository Maybe first say an SGA was received from IBM for IBM Lotus Symphony, and now are preparing to import... This should be complete by the time of the June board meeting. - Work is continuing on making translation processes easier for volunteers. Currently, only committers can access the Pootel server. - Testing and implementation of old update service for OpenOffice has been accomplished. This service is for older OpenOffice clients to identify updates and, optionally, install an update if available. - need and update on this one and the mailing list numbers!!: For ooo-dev we have 409 subscribers ! Community support forums remain popular with users, hitting a new concurrency record (296) Very good report. I see you have some other suggestions as well. Once those are included, and maybe a run through a spell checker, it should be ready to go. Thanks for volunteering to draft this! -Rob -- MzK So let it rock, let it roll Let the
Re: *DRAFT* June board report...please help
On 6 June 2012 01:20, Kay Schenk kay.sch...@gmail.com wrote: On Tue, Jun 5, 2012 at 5:06 PM, Ross Gardler rgard...@opendirective.comwrote: On 6 June 2012 00:14, Kay Schenk kay.sch...@gmail.com wrote: OK, here is the latest revision--and guess what, after some digging, I found the SPI deal is done! YAY! Hold up... http://permalink.gmane.org/gmane.comp.apache.incubator.ooo.devel/16846 Sorry to disappoint. The cheque mentioned in that post was cancelled due to the change in chair of Fundraising and further questions being asked here in the ASF. See http://article.gmane.org/gmane.comp.apache.incubator.ooo.devel/16845/match=schultheiss Unfortunately my note about further questions overlapped with the cheque notification otherwise I would have kept my mouth shut and returned the money if approval had not been given. Sometimes email and a rotating planet work against us... Ross Ross Ross
Re: *DRAFT* June board report...please help
KG01 - See comments inline. Kay, thanks for putting this information together. On Wed, Jun 6, 2012 at 8:26 AM, Rob Weir robw...@apache.org wrote: On Tue, Jun 5, 2012 at 4:34 PM, Kay Schenk kay.sch...@gmail.com wrote: OK, here's a draft -- Dennis is working on getting me actual people numbers later today, so what I have here in terms of new committers is just a (bad) guess. And, duh -- we only report in March, June, September, December, so what I have here in terms of what we've been doing since March is probably way, way off... Please update as you see fit! I now have an incubator wiki account so I will happily post when we're done == proposed June AOO report == *Project Name and Brief Description* OpenOffice (was OpenOffice.org) * OpenOffice entered incubation 2011-06-13 OpenOffice is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice is released on multiple platforms. Its localizations have supported 110 languages worldwide. * Most Important Items To Address Toward Graduation * 1. Review of distributed articles to ensure compliance with ASF policy 2. Given the size and scope of OpenOffice, continue work on community readiness espeically with refgard to organization and communication style. 3. Increase size and diversity of the active development community It seems odd to have a list that large and say that we're about to start a graduation vote. My impression was we're really only working on #1, and Andre and Pedro seem to have those under control. #2 and #3 are ongoing activities, before and after graduation, for us and any other Apache project. But I don't think we have any graduation blocking issues there. We have started preliminary discussion concerning graduation, and are putting renewed emphasis on the above items as we would like to propose graduation within the next month. * Issues for IPMC or ASF Board Awareness * - None * Community Development Progress * - Since our last report we have voted in 5 (?) new Committers/PPMC members. - Since our last report, one committer/PPMC member has resigned - We have improved to act more as a self organized project to address and solve project related topics (eg. budget transfer from SPI, forum moderation). - We accepted an offer from SourceForge to host our older 3.3 version and provide client installs of our latest release 3.4. This decision was arrived after much discussion among members and consulation with mentors. - Due to heightened interest, we are putting more resources (services, volunteers) into translation efforts - We are putting more effort into addressing trademark and third-party distributin requests. Ongoing emphasis as to how to accomodate and track these requests is becoming an important concern. - We are putting renewed emphasis on recruitment to assist with maintaiing now abandoned former native-language project web sites. KG01 - Re 3. Increase size and diversity of the active development community, perhaps we could acknowledge that we are working to re-invigorate the user experience design effort. Software is for people, and we should show that we are working hard to understand who is user our product, why and for what, and how we will work to deliver the best experience possible to support our users. We don't just make code software, we design great products that align with our client's view of success - that is a design activity. My feedback here is too wordy, please include anything that acknowledges effort in user research and design of our products would be great. I'd word that as, 'We are increasing our global reach by recruiting volunteers to help update and maintain the large set of legacy native language home pages * Project Development Progress * - We released Apache OpenOffice 3.4 on May 8, 2012. Over three million downloads in the first month. This release included: Five different client platform install versions in 15 languages Source tarbalss in Engligh Software development kit packaging for 5 platforms Language packs for 15 languages A summary of downloads for the installs can be found at: http://sourceforge.net/projects/openofficeorg.mirror/files/stats/timeline We would like to publicly acknowledge the efforts of our mentors, the Apache infrastructure team, and the wonderful folks at SourceForge in making this release a success! - We are currently working on an alternate repository for category-B code to comply with graduation requirements - Prepartion was made in May for importing IBM Symphony changes into the OpenOffice repository Maybe first say an SGA was received from IBM for IBM Lotus Symphony, and now are preparing to import... This should be complete by
Re: Incubator PMC/Board report for Jun 2012 ([ppmc])
Top posting-- Folks, I will note that we apparently didn't submit a report for May -- I guess we were all too busy with the release. So...this is due this coming Wed, June 6th. I will help if I can. We could at least mention that we're starting the discussion on graduation. And, get them caught up on our new committers and PPMC members. On Sun, Jun 3, 2012 at 6:11 PM, Marvin no-re...@apache.org wrote: 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, 20 June 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, Jun 6th). 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/June2012 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 -- MzK So let it rock, let it roll Let the bible belt come and save my soul Hold on to sixteen as long as you can Changes come around real soon make us woman and men. -- Jack and Diane, John Mellencamp
Incubator PMC/Board report for Jun 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, 20 June 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, Jun 6th). 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/June2012 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
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
On 03/05/2012 10:53 PM, Rob Weir wrote: On Mon, Mar 5, 2012 at 10:24 PM, Carl Marcumcmar...@apache.org wrote: On 03/05/2012 05:13 PM, Ross Gardler wrote: Thanks - signed off. On 5 March 2012 22:10, Rob Weirrobw...@apache.orgwrote: On Mon, Mar 5, 2012 at 5:01 PM, RGB ESrgb.m...@gmail.comwrote: 2012/3/5 Rob Weirrobw...@apache.org: I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Hagar added new data some days ago: http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874 Great. Thanks. I added a link to that in the report. -Rob I thought I would update the project status page with the March board report. The openofficeorg.xml used to be in incubator/site-author/projects/, now I only see sitemap.xml there. I do see it in incubator/content/ I checked http://incubator.apache.org/guides/website.html but didn't see anything different. Are the build and check-in instructions the same otherwise? Our instructions under PPMC FAQs) need to be updated. There was a thread on this on the Incubator general list just recently. Essentially the Incubator website has been CMS-enabled. So you should be able to edit the XML file using the CMS bookmarklet and publish it directly: https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/openofficeorg.xml So just like editing our podling website. I have not tried this myself. Let us know how it works. -Rob Best regards, Carl Status page now updated with a link to the March 2012 report. The bookmarklet worked well. Best regards, Carl
Incubator PMC/Board report for Mar 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, 21 March 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, Mar 7th). 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/March2012 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
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
On Mon, Mar 5, 2012 at 10:33 AM, Marvin no-re...@apache.org wrote: 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, 21 March 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, Mar 7th). Quick reminder: Our quarterly report is due to the IPMC on Wed. I just reviewed and it looked fine. I made a few small changes/additions. I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Otherwise, I think we're ready for mentor sign off. -Rob 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/March2012 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
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
2012/3/5 Rob Weir robw...@apache.org: I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Hagar added new data some days ago: http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
Thanks - signed off. On 5 March 2012 22:10, Rob Weir robw...@apache.org wrote: On Mon, Mar 5, 2012 at 5:01 PM, RGB ES rgb.m...@gmail.com wrote: 2012/3/5 Rob Weir robw...@apache.org: I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Hagar added new data some days ago: http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874 Great. Thanks. I added a link to that in the report. -Rob -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
On 03/05/2012 05:13 PM, Ross Gardler wrote: Thanks - signed off. On 5 March 2012 22:10, Rob Weirrobw...@apache.org wrote: On Mon, Mar 5, 2012 at 5:01 PM, RGB ESrgb.m...@gmail.com wrote: 2012/3/5 Rob Weirrobw...@apache.org: I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Hagar added new data some days ago: http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874 Great. Thanks. I added a link to that in the report. -Rob I thought I would update the project status page with the March board report. The openofficeorg.xml used to be in incubator/site-author/projects/, now I only see sitemap.xml there. I do see it in incubator/content/ I checked http://incubator.apache.org/guides/website.html but didn't see anything different. Are the build and check-in instructions the same otherwise? Best regards, Carl
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
On Mon, Mar 5, 2012 at 10:24 PM, Carl Marcum cmar...@apache.org wrote: On 03/05/2012 05:13 PM, Ross Gardler wrote: Thanks - signed off. On 5 March 2012 22:10, Rob Weirrobw...@apache.org wrote: On Mon, Mar 5, 2012 at 5:01 PM, RGB ESrgb.m...@gmail.com wrote: 2012/3/5 Rob Weirrobw...@apache.org: I'd love to include a line or two from the Community Forums, if there are any new stats on subscribers, questions answered, etc. Hagar added new data some days ago: http://user.services.openoffice.org/en/forum/viewtopic.php?p=222874#p222874 Great. Thanks. I added a link to that in the report. -Rob I thought I would update the project status page with the March board report. The openofficeorg.xml used to be in incubator/site-author/projects/, now I only see sitemap.xml there. I do see it in incubator/content/ I checked http://incubator.apache.org/guides/website.html but didn't see anything different. Are the build and check-in instructions the same otherwise? Our instructions under PPMC FAQs) need to be updated. There was a thread on this on the Incubator general list just recently. Essentially the Incubator website has been CMS-enabled. So you should be able to edit the XML file using the CMS bookmarklet and publish it directly: https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/openofficeorg.xml So just like editing our podling website. I have not tried this myself. Let us know how it works. -Rob Best regards, Carl
Incubator PMC/Board report for Mar 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, 21 March 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, Mar 7th). 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/March2012 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
Re: Incubator PMC/Board report for Mar 2012 ([ppmc])
On 2/23/12 2:13 PM, Marvin wrote: 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, 21 March 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, Mar 7th). 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 it's time for our next report. I've posted a draft to the wiki. Please review and make edits as needed. I probably missed important things. Especially numbers ;-) http://wiki.apache.org/incubator/March2012 Thanks, Juergen 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/March2012 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
Incubator PMC/Board report for Mar 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, 21 March 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, Mar 7th). 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/March2012 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
Incubator PMC/Board report for Dec 2011 ([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, 21 December 2011, 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 7th). 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/December2011 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
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
On 12/12/2011 01:28 PM, Rob Weir wrote: On Mon, Dec 12, 2011 at 1:05 PM, Marvinno-re...@apache.org wrote: 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. Automation seems a bit off. Our report for December has already been posted and signed off on. -Rob I'll update the status page. Best regards, Carl
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
The Status page is updated to include the December report. Carl
Incubator PMC/Board report for Dec 2011 ([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, 21 December 2011, 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 7th). 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/December2011 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
Re: Incubator PMC/Board report for Dec 2011 ([ppmc])
On Thu, Dec 1, 2011 at 7:55 AM, Marvin no-re...@apache.org wrote: 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, 21 December 2011, 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 7th). 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. Our report is due in a couple of days. I've posted a draft to the wiki. Please review and make edits as needed. It has been a busy and productive quarter. I probably missed some things. http://wiki.apache.org/incubator/December2011 Thanks, -Rob 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/December2011 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
Incubator PMC/Board report for Dec 2011 ([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, 21 December 2011, 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 7th). 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/December2011 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
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
Graham Lauder wrote on Mon, Oct 03, 2011 at 07:02:17 +1300: On Sunday, October 02, 2011 05:16:15 AM Dennis E. Hamilton wrote: These announcements to a list are interesting, because it is not clear who will take the initiative to see that this happens. Last month, I waited too long before declaring what I would be doing and then doing it. This month, I won't be tardy. I am declaring that I shall not be preparing the quarterly podling report for October. - Dennis I'll have time this month to deal with this. It is a marketing task in any case. Reporting to the board isn't about marketing, it is about the board's oversight over the foundation it is the board of. I don't think you wuold include community friction issues in marketing materials, but a PMC chair must report them to the board if they exist. I will respectively disagree. Marketing is about communication. Marketing is not simply external facing, especially in an opensource project. Any good marketing team should and will identify challenges and weaknesses. Highlighting and communicating those to the appropriate stakeholders it's just part of the job as is gathering that information. Community friction issues are one of those challenges that is often present in an opensource project, so it is definitely something that should be communicated. The board is the stakeholder that this needs to be communicated to. Marketing is not simply about pr, spin and glossy pamphlets. Cheers GL
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
On 1 October 2011 17:16, Dennis E. Hamilton dennis.hamil...@acm.org wrote: These announcements to a list are interesting, because it is not clear who will take the initiative to see that this happens. Once the project graduates it is the responsibility of the PMC chair to ensure that reports are submitted. While in the incubator it is the responsibility of your mentors to ensure it is done. In both cases it is the respinsbility of the community as a whole to produce the report. Thank you, once again, for making sure people see it and act on it. Ross
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
Marketing is not simply about pr +1
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
On Mon, Oct 3, 2011 at 7:34 AM, Graham Lauder yori...@openoffice.org wrote: Marketing is not simply about pr, spin and glossy pamphlets. But I like glossy pamphlets. They add color to my cubicle. How about status/progress regarding IP resolution, as that's a graduation requirement? Don
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
Graham Lauder wrote on Mon, Oct 03, 2011 at 07:02:17 +1300: On Sunday, October 02, 2011 05:16:15 AM Dennis E. Hamilton wrote: These announcements to a list are interesting, because it is not clear who will take the initiative to see that this happens. Last month, I waited too long before declaring what I would be doing and then doing it. This month, I won't be tardy. I am declaring that I shall not be preparing the quarterly podling report for October. - Dennis I'll have time this month to deal with this. It is a marketing task in any case. Reporting to the board isn't about marketing, it is about the board's oversight over the foundation it is the board of. I don't think you wuold include community friction issues in marketing materials, but a PMC chair must report them to the board if they exist.
Re: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
On 10/02/2011 11:02 AM, Graham Lauder wrote: On Sunday, October 02, 2011 05:16:15 AM Dennis E. Hamilton wrote: These announcements to a list are interesting, because it is not clear who will take the initiative to see that this happens. Last month, I waited too long before declaring what I would be doing and then doing it. This month, I won't be tardy. I am declaring that I shall not be preparing the quarterly podling report for October. - Dennis I'll have time this month to deal with this. It is a marketing task in any case. If anyone thinks that there are significant milestones or challenges for the project that should be highlighted then please feel free to point them out. Not being a coder and given that most activity right now is on the coding side, there is a good chance I'll miss stuff, so pile it on. Cheers GL What a good sport you are, Graham. I would point out the challenges we're having with finding a new architecture for the OpenOffice wiki and, most importantly, the user forums. As far as I know, we do not have a clear migration on either of these. If I think of anything else, I'll pass it along. -Original Message- From: no-re...@apache.org [mailto:no-re...@apache.org] Sent: Saturday, October 01, 2011 07:00 To: ooo-dev@incubator.apache.org Subject: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org) Dear OpenOffice.org Developers, 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 October 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. 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 one week 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/October2011 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 Graham Lauder, OpenOffice.org MarCon (Marketing Contact) NZ http://marketing.openoffice.org/contacts.html -- MzK There is no such thing as coincidence. -- Leroy Jethro Gibbs, Rule #39
Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
Dear OpenOffice.org Developers, 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 October 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. 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 one week 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/October2011 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
RE: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org)
These announcements to a list are interesting, because it is not clear who will take the initiative to see that this happens. Last month, I waited too long before declaring what I would be doing and then doing it. This month, I won't be tardy. I am declaring that I shall not be preparing the quarterly podling report for October. - Dennis -Original Message- From: no-re...@apache.org [mailto:no-re...@apache.org] Sent: Saturday, October 01, 2011 07:00 To: ooo-dev@incubator.apache.org Subject: Incubator PMC/Board report for October 2011 (ooo-dev@incubator.apache.org) Dear OpenOffice.org Developers, 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 October 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. 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 one week 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/October2011 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
Re: [MENTORS] Need Review/Sign-Off of PMC/Board Report
Done, thanks for the reminder. Good report, btw Christian On Thu, Sep 15, 2011 at 6:50 AM, Dennis E. Hamilton orc...@apache.org wrote: Ahem, There are no sign-offs on the OpenOffice.org Podling Board Report http://wiki.apache.org/incubator/September2011. - Dennis -- http://www.grobmeier.de
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
I have updated the draft report: 1) Added mention of the trademark permission request we reviewed and approved 2) Added mention of the difficulties we had this month with bulldozing when the discussions became heated. (I think that is relevant, and we should acknowledge the problem as well as steps taken to address it,) 3) Removed the unnecessary editorializing. Revised version is below. -Rob * OpenOffice.org entered incubation 2011-06-13. OpenOffice.org is an open-source, office-document productivity suite providing six productivity applications based around the OpenDocument Format (ODF). OpenOffice.org is released on multiple platforms. Its localizations support 110 languages worldwide. * Most important to address 1) Migration of the legacy OpenOffice.org website's content and services to Apache infrastructure, including defect tracking, wiki, forums, mailing lists, and cross-service registration using customized software not already supported by Apache projects and infrastructure. Successful negotiation of governance migration of user-supported services brought under incubation. Resolution of copyright, license and notice for content miugrated from legacy OpenOffice.org website. 2) Completion of the IP-review portions of the incubation checklist, which will require getting an amended SGA from Oracle to cover additional source files; scrubbing of incompatible notices from SGA-licensed code and resolving provenance of other existing materials being migrated. 3) A Successful Podling Release * Issues for IPMC or ASF Board Awareness None. * Community development progress As of 2011-09-12 there are 72 committers, with 55 on the PPMC, up from 71 and 52 at last report. Eleven initial committers have failed to submit iCLAs and are out of communication. Discussion is underway with the operators of the existing OpenOffice.org user-support forums for migration of the forums into the project, with adjustment of governance to provide appropriate PPMC oversight. We have created a ooo-users.i.a.o mailing list. A Japanese-language ooo-general-ja.i.a.o is also starting. We have reviewed a request for permission to use the OpenOffice.org trademark by a German book publisher, and sent our approval recommendation to Apache Branding. A Building OpenOffice.org for Linux hackfest was announced on the project blog and carried out over the Internet in the first full week of September. Although discussions on the list are currently calm, we have had cases this month of bulldozing and other undesired behavior when the discussions become heated. The project mentors have worked diligently to coach project members on the dangers of such behavior. * Project development progress The OpenOffice.org trademarks have been transferred to Apache. The OpenOffice.org domain-name registrations are being transferred to Apache. The legacy OpenOffice.org Issue Tracking Bugzilla has been moth-balled as read-only and an Apache Bugzilla established for continuation of Issue Tracking under the podling. The main source code base has been transferred to Apache SVN and is being actively tested and modified. Merging of additional work spaces from OpenOffice.org, and preservation of versioning history is being pursued. The current effort is focused on successful build of a counterpart of the last complete build at OpenOffice.org. Test configurations of the OpenOffice.org forum system and the OpenOffice.org Wiki have been brought up on Apache infrastructure fixtures. Cutover of the forum system is anticipated as part of the OpenOffice.org migration. Detailed planning continues on public wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
Dennis E. Hamilton wrote on Wed, Sep 14, 2011 at 08:29:05 -0700: Rob, 1. Considering that the Bulldozing term and thread were on ooo-private, it will be weird to have that reported here as status of a group that was not privy to it. (The IPMC and mentors already know, of course.) I recommend that the mention be removed. A community accomplishment would be the increase in civility on the ooo-dev list, perhaps. If this is to remain, do you have a more affirmative statement than that mentoring was required? Positive outcome strikes me as the accomplishment. It's possible to report an issue privately --- ie, to have it known to the PMC and the board (and for podlings also the PPMC), but not publish it in the public minutes. That's normally used for reporting issues of the sort that would be discussed on private@ rather than on dev@. I have no opinion on whether this mechanism should be invoked in this instance.
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
On Wed, Sep 14, 2011 at 11:29 AM, Dennis E. Hamilton dennis.hamil...@acm.org wrote: Rob, 1. Considering that the Bulldozing term and thread were on ooo-private, it will be weird to have that reported here as status of a group that was not privy to it. (The IPMC and mentors already know, of course.) I recommend that the mention be removed. A community accomplishment would be the increase in civility on the ooo-dev list, perhaps. If this is to remain, do you have a more affirmative statement than that mentoring was required? Positive outcome strikes me as the accomplishment. I think this was an issue of concern to the community and it was discussed on the ooo-dev as well as on ooo-private. If there are other preferred ways of describing it, then edits are welcome. But I think the term bulldozing is accurate and well-understood at Apache. 2. I also forgot an issue, and that is our failure to deal with the (usage of) encryption software now public in the code base. That does strike me as an issue that the Board might want to be aware of. It might be worth giving a one line summary and a link to each of the several issues you or other project members have raised on legal-discuss. 3. Issues were listed in the August report, under that heading. It might be good to have accounted for them. I have no idea what to say about the organizational one, but perhaps to report that the oversight responsibilities of the PPMC as delegated by the ASF were clarified and are being applied. Maybe this could go under community? 4. In particular, discussions with documentation authors were mentioned in the previous report and discussions as to licensing were identified as an issue. If you have a rewording for the outcome (rather than removing the topic completely from the status), I think that would be a good idea. I think that is subsumed with migration and IP review of source code, website and other content, highlighted as one of the top three things we need to do. That is also related to an unresolved legal-discuss question on the CC license. - Dennis -Original Message- From: Rob Weir [mailto:robw...@apache.org] Sent: Wednesday, September 14, 2011 05:18 To: ooo-dev@incubator.apache.org Subject: Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) I have updated the draft report: 1) Added mention of the trademark permission request we reviewed and approved 2) Added mention of the difficulties we had this month with bulldozing when the discussions became heated. (I think that is relevant, and we should acknowledge the problem as well as steps taken to address it,) 3) Removed the unnecessary editorializing. Revised version is below. -Rob * OpenOffice.org entered incubation 2011-06-13. [ ... ] * Community development progress [ ... ] Although discussions on the list are currently calm, we have had cases this month of bulldozing and other undesired behavior when the discussions become heated. The project mentors have worked diligently to coach project members on the dangers of such behavior. * Project development progress [ ... ]
[MENTORS] Need Review/Sign-Off of PMC/Board Report
Ahem, There are no sign-offs on the OpenOffice.org Podling Board Report http://wiki.apache.org/incubator/September2011. - Dennis
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
On Tue, Sep 13, 2011 at 12:31 PM, Dennis E. Hamilton orc...@apache.org wrote: The current committers are not equipped to fully resource the migration of OpenOffice.org sites and services under Apache OOo incubation. Preservation of the Wiki is in doubt because of resource and support limitations. Cutover of mailing-list and registration/forwarding systems is not resourced at all. The ability to make anticipatory modifications of OpenOffice.org in preparation for staging is also limited, with volunteer support and administration of the live system possibly eroding. How is resource defined in this? Don
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
On 9/13/11, Donald Whytock dwhyt...@gmail.com wrote: On Tue, Sep 13, 2011 at 12:31 PM, Dennis E. Hamilton orc...@apache.org wrote: The current committers are not equipped to fully resource the migration of OpenOffice.org sites and services under Apache OOo incubation. Preservation of the Wiki is in doubt because of resource and support limitations. Cutover of mailing-list and registration/forwarding systems is not resourced at all. The ability to make anticipatory modifications of OpenOffice.org in preparation for staging is also limited, with volunteer support and administration of the live system possibly eroding. How is resource defined in this? Don IMO the server might be shutdown without notice as well as php support on Apache infrastructure is not well embraced. -- Alexandro Colorado OpenOffice.org Español http://es.openoffice.org
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
is anticipated as part of the OpenOffice.org migration. Other services may languish for lack of podling resources. Detailed planning continues on public wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/ -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Tuesday, September 13, 2011 07:33 To: ooo-dev@incubator.apache.org Subject: RE: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) I've started pulling together a skeleton by reviewing the July/August reports and accomplishments since. When I have something on the wiki at http://wiki.apache.org/incubator/September2011 I will put an update on the list and request review. - Dennis -Original Message- From: no-re...@apache.org [mailto:no-re...@apache.org] Sent: Thursday, September 01, 2011 07:00 To: ooo-dev@incubator.apache.org Subject: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) Dear OpenOffice.org Developers, 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, 21 September 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. 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 one week 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/September2011 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
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
I'd like to suggest this be more detailed, so it's clear where the problems are. That way it's easier to determine what ASF can provide that isn't provided already. The current committers are not equipped to fully resource the migration of OpenOffice.org sites and services under Apache OOo incubation. Does current committers refer to people working on the Oracle site, or the current pool of committers in the podling? Does resource mean supply time, gain access, provide equipment, have skill? Preservation of the Wiki is in doubt because of resource and support limitations. Is this preservation of the wiki in its current form because the Oracle servers are going away? Preservation of the wiki data because it's not being done in a timely manner? Cutover of mailing-list and registration/forwarding systems is not resourced at all. Resourced as in people designated/volunteering to do it, no comparable Apache facility, no plan, no access? The ability to make anticipatory modifications of OpenOffice.org in preparation for staging is also limited, with volunteer support and administration of the live system possibly eroding. Specific problems with access, skill level, available people, timetable? Am I overestimating what has to be in a podling report? Don
Re: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org)
actively tested and modified. Merging of additional work spaces from OpenOffice.org, and preservation of versioning history is being pursued. The current effort is focused on successful build of a counterpart of the last complete build at OpenOffice.org. Test configurations of the OpenOffice.org forum system and the OpenOffice.org Wiki have been brought up on Apache infrastructure fixtures. Cutover of the forum system is anticipated as part of the OpenOffice.org migration. Other services may languish for lack of podling resources. Detailed planning continues on public wiki: https://cwiki.apache.org/confluence/display/OOOUSERS/ -Original Message- From: Dennis E. Hamilton [mailto:dennis.hamil...@acm.org] Sent: Tuesday, September 13, 2011 07:33 To: ooo-dev@incubator.apache.org Subject: RE: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) I've started pulling together a skeleton by reviewing the July/August reports and accomplishments since. When I have something on the wiki at http://wiki.apache.org/incubator/September2011 I will put an update on the list and request review. - Dennis -Original Message- From: no-re...@apache.org [mailto:no-re...@apache.org] Sent: Thursday, September 01, 2011 07:00 To: ooo-dev@incubator.apache.org Subject: Incubator PMC/Board report for September 2011 (ooo-dev@incubator.apache.org) Dear OpenOffice.org Developers, 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, 21 September 2011, 10 am Pacific. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted one week before the board meeting, to allow sufficient time for review. 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 one week 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/September2011 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
