Re: Fwd: Incubator PMC/Board report for Oct 2012 ([ppmc])
Hi Noah... This reminder is for collecting reports which is early enough as the reports are discussed at board meeting 3rd Wednesday from each month. Before reports were collected just one week before the board meeting and some of them were too late to submit there reports and hence the IPMC came up with the idea to collect it max. by the 1st Wednesday of the month. And I believe the reminders are even send more early than that I suppose this one is just a second/another reminder But thanks for being so keen to get things done on the right time :) On Thu, Oct 4, 2012 at 1:19 AM, Noah Slater nsla...@tumbolia.org wrote: I had seen the earlier reminder, but had not made a calendar event for it. So when the 24 hour reminder came in, along with a quick draft that was posted before I checked my email, I felt a little blindsided. Would be nice to have the final call reminder come in 72 hours before the deadline, as is customary in Apache. On Thu, Oct 4, 2012 at 12:15 AM, David Crossley cross...@apache.org wrote: Noah Slater wrote: Can we please adjust this system to send the notice out two days prior? As it stands, this notice gives the project a single day to prepare the board report. As it happens, I missed it, because I didn't check my mail yesterday. Which is annoying, because I had some comments on what was proposed. Can we adjust it so there is, at least, 72 hours notice? These are just reminders. The whole project should be aware of the reporting schedule, now and when TLP. Anyway here is the schedule stuff: http://incubator.apache.org/report-next-month.html http://incubator.apache.org/report-groups.txt These are generated from the main content/podlings.xml file. We should find a link in these archives about the SVN location of the tool that sends the reminders. Someone could adjust it. The code probably also needs some changes, to pick up next month's set of projects, because then firing before the new month. -David -- Forwarded message -- From: Marvin no-re...@apache.org Date: Tue, Oct 2, 2012 at 8:11 PM Subject: Incubator PMC/Board report for Oct 2012 ([ppmc]) To: cloudstack-...@incubator.apache.org 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, 17 October 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, Oct 3rd). 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/October2012 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 -- NS - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Incubator PMC/Board report for Oct 2012 ([ppmc])
Can we not run the cronjob ever day and have it wake up, do some date math, and then go back to sleep unless the moment is right. The moment being right defined as 72 hours before the deadline. On Thu, Oct 4, 2012 at 9:20 AM, Jukka Zitting jukka.zitt...@gmail.comwrote: Hi, On Thu, Oct 4, 2012 at 1:19 AM, Noah Slater nsla...@tumbolia.org wrote: I had seen the earlier reminder, but had not made a calendar event for it. So when the 24 hour reminder came in, along with a quick draft that was posted before I checked my email, I felt a little blindsided. Would be nice to have the final call reminder come in 72 hours before the deadline, as is customary in Apache. IIRC the main problem in making this happen is that the current cronjob is unable to send reminders already for the following month. Thus the reminders to podlings end up being sent only at the beginning of the month, sometimes just moments before the deadline. So far I've tried to remedy this by sending earlier reminders to general@, but of course not everyone is following that list. It would be great if someone could update our tooling to better handle the reminders. Perhaps the incubator.apache.org site build could even automatically generate per-project ical files for this? BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- NS
Re: Fwd: Incubator PMC/Board report for Oct 2012 ([ppmc])
Hi, On Thu, Oct 4, 2012 at 11:19 AM, Noah Slater nsla...@tumbolia.org wrote: Can we not run the cronjob ever day and have it wake up, do some date math, and then go back to sleep unless the moment is right. The moment being right defined as 72 hours before the deadline. We can, as soon as we have a patch. :-) Hopefully someone who knows the script better (where it's located, run, etc.) will fill in details on how one would go about writing such a patch. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
'Apache Mobile First' ?
Hi, just ran into this one: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ? I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
Ha! two minutes later - the tweet has been deleted :-D But it was linking to this page = http://www.apachemobilefilter.org/ -Matthias On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: Hi, just ran into this one: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ? I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache Thx, Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
Hi, On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ?... That project has been mentioned on the devicemap dev list, http://markmail.org/message/yfmu5h3n2tggy33n , but nothing more so far. ...I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache... I agree that the Apache Mobile Filter name might give the impression that that's an Apache project, but it's not, what that really is is a Mobile Filter for the Apache HTTP server. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate Isis podling from Apache Incubator
This is a call for vote to graduate the Isis podling from Apache Incubator. Isis entered the Incubator in Sept of 2010. Since then it has added one new committer, picked up a number of new contributors, and made two significant releases following the ASF policies and guidelines. The community of Isis, though small, is active, healthy and growing and has demonstrated the ability to self-govern using accepted Apache practices. The Isis community has voted to proceed with graduation [1] and the result can be found at [2]. Please cast your votes: [ ] +1 Graduate Isis podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Isis podling [ ] -1 Reject graduation of Isis podling from Apache Incubator because ... This vote will be open for at least 72 hours. Please find the proposed board resolution below. [1] http://s.apache.org/xt [2] http://s.apache.org/blt Regards, Dan Haywood Establish the Apache Isis Top-Level Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, to enable the creation of software using domain-driven design principles, and the realization of this through the naked objects architectural pattern, NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Isis Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Isis Project be and hereby is responsible for the creation and maintenance of software related to and inspired by the naked objects architectural pattern; and be it further RESOLVED, that the office of Vice President, Apache Isis be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Isis Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Isis Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Isis Project: Dan Haywood danhayw...@apache.org Robert Matthews rmatth...@apache.org Kevin Meyer ke...@apache.org Alexander Krasnukhin themalk...@apache.org Dave Slaughter dslaugh...@apache.org Jeroen van der Wal jcvander...@apache.org Mohammad Nour El-Din mn...@apache.org Mark Struberg strub...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dan Haywood be appointed to the office of Vice President, Apache Isis, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Isis PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Isis Project; and be it further RESOLVED, that the Apache Isis Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Isis podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Isis podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [DISCUSS] Apache Isis graduation - resolution (prior to recommendation vote)
Since there's been no further discussion on this, I'll start the vote. On 1 October 2012 20:50, Mark Struberg strub...@yahoo.de wrote: looks good to me. Status file is up2date as well. congratulations! +1 from me ;) LieGrue, strub - Original Message - From: Dan Haywood d...@haywood-associates.co.uk To: general@incubator.apache.org Cc: Sent: Monday, October 1, 2012 12:28 PM Subject: [DISCUSS] Apache Isis graduation - resolution (prior to recommendation vote) All, The Apache Isis podling has just had a community vote to graduate [1], which has succeeded [2]. This is in line with recent status reports to the Incubator board, [3], [4]. According to [5], the next step for us to follow is to ask for feedback on the resolution that we voted upon. For convenience, I've copied it to the end of this mail; it's also on our wiki [6] and in the vote [1]. If no objections are raised on this thread, then I'll follow up in a few days with a recommendation vote (again, as per [5]). For now, comments welcome. Many thanks Dan Haywood [1] http://markmail.org/thread/6qptoysy2tygoigi - vote, plus resolution [2] http://isis.markmail.org/thread/63zqlydeapmk3h64 - results [3] http://wiki.apache.org/incubator/September2012 [4] http://wiki.apache.org/incubator/June2012 [5] http://incubator.apache.org/guides/graduation.html#process [6] https://cwiki.apache.org/confluence/display/ISIS/GraduationResolution Establish the Apache Isis Top-Level Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, to enable the creation of software using domain-driven design principles, and the realization of this through the naked objects architectural pattern, NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Isis Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Isis Project be and hereby is responsible for the creation and maintenance of software related to and inspired by the naked objects architectural pattern; and be it further RESOLVED, that the office of Vice President, Apache Isis be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Isis Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Isis Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Isis Project: Dan Haywood danhayw...@apache.org Robert Matthews rmatth...@apache.org Kevin Meyer ke...@apache.org Alexander Krasnukhin themalk...@apache.org Dave Slaughter dslaugh...@apache.org Jeroen van der Wal jcvander...@apache.org Mohammad Nour El-Din mn...@apache.org Mark Struberg strub...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dan Haywood be appointed to the office of Vice President, Apache Isis, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Isis PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Isis Project; and be it further RESOLVED, that the Apache Isis Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Isis podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Isis podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: New challenges (Was: NOMINATIONS for Incubator PMC Chair)
+1 Benson is really good candidate! LieGrue, strub - Original Message - From: Dan Haywood d...@haywood-associates.co.uk To: general@incubator.apache.org Cc: Sent: Wednesday, October 3, 2012 10:09 AM Subject: Re: New challenges (Was: NOMINATIONS for Incubator PMC Chair) On 3 October 2012 07:47, Bertrand Delacretaz bdelacre...@apache.org wrote: Let's fix this: I nominate Benson Margulies as Incubator PMC chair. Benson's been actively involved in the Incubator for quite a while, has mentored several projects, and (despite longish emails sometimes IIRC ;-) has shown great ability to work in a non-confrontational way and help things go forward. I think he'd make a great Incubator PMC chair. +1 on that. Benson has been mentoring the podling I work on (Isis), and I've appreciated his no-nonsense guidance and support. Dan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
Apache Mobile Filter (or AMF) is the name of the project sine 2008, and is a filter of Apache so I don't know what is the problem Idel (owner of AMF) On 4 October 2012 14:36, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ?... That project has been mentioned on the devicemap dev list, http://markmail.org/message/yfmu5h3n2tggy33n , but nothing more so far. ...I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache... I agree that the Apache Mobile Filter name might give the impression that that's an Apache project, but it's not, what that really is is a Mobile Filter for the Apache HTTP server. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
On 4 October 2012 14:53, Idel Fuschini idel.fusch...@gmail.com wrote: Apache Mobile Filter (or AMF) is the name of the project sine 2008, and is a filter of Apache so I don't know what is the problem There is a potentially significant trademark problem (hence moving this to trademarks@): The following uses of ASF trademarks are probably infringing: Software service offerings that are for anything other than official ASF-distributed software. and You may not use ASF trademarks such as Apache or ApacheFoo or Foo in your own domain names if that use would be likely to confuse a relevant consumer about the source of software or services provided through your website http://www.apache.org/foundation/marks/ Ross Idel (owner of AMF) On 4 October 2012 14:36, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ?... That project has been mentioned on the devicemap dev list, http://markmail.org/message/yfmu5h3n2tggy33n , but nothing more so far. ...I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache... I agree that the Apache Mobile Filter name might give the impression that that's an Apache project, but it's not, what that really is is a Mobile Filter for the Apache HTTP server. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
So I need to change my domain name ? And this http://www.apache.com/ or myapache.org, or http://www.fortsillapache-nsn.gov/ or http://www.sancarlosapache.com/home.htm For me is a free project and I don't make money with this :-( and also my wiki the discription is: The module detects the mobile device and passes the WURFL capabilities on to the other web application as environment variables. It can also be used to resize images on the fly to adapt to the screen size of the mobile device. Idel On 4 October 2012 16:21, Ross Gardler rgard...@opendirective.com wrote: On 4 October 2012 14:53, Idel Fuschini idel.fusch...@gmail.com wrote: Apache Mobile Filter (or AMF) is the name of the project sine 2008, and is a filter of Apache so I don't know what is the problem There is a potentially significant trademark problem (hence moving this to trademarks@): The following uses of ASF trademarks are probably infringing: Software service offerings that are for anything other than official ASF-distributed software. and You may not use ASF trademarks such as Apache or ApacheFoo or Foo in your own domain names if that use would be likely to confuse a relevant consumer about the source of software or services provided through your website http://www.apache.org/foundation/marks/ Ross Idel (owner of AMF) On 4 October 2012 14:36, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ?... That project has been mentioned on the devicemap dev list, http://markmail.org/message/yfmu5h3n2tggy33n , but nothing more so far. ...I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache... I agree that the Apache Mobile Filter name might give the impression that that's an Apache project, but it's not, what that really is is a Mobile Filter for the Apache HTTP server. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: 'Apache Mobile First' ?
On 4 October 2012 15:48, Idel Fuschini idel.fusch...@gmail.com wrote: So I need to change my domain name ? Not necessarily. The ASF isn't in the business of shutting people down - that's kind of counter to everything we are all trying to achieve. All we want to do is remove confusion for end users. For this reason, you do need permission from our VP Trademarks to use our marks in ways that do not class as normative use. The right thing to do is to engage with the tradema...@apache.org list (I've again addressed that list in this reply). The people over there will work with you to ensure there is no confusion for end-users and thus ASF marks are not infringed. Shane (our VP Brand Management) is a nice guy, he'll be happy to work with you as opposed to against you :-) Ross And this http://www.apache.com/ or myapache.org, or http://www.fortsillapache-nsn.gov/ or http://www.sancarlosapache.com/home.htm For me is a free project and I don't make money with this :-( and also my wiki the discription is: The module detects the mobile device and passes the WURFL capabilities on to the other web application as environment variables. It can also be used to resize images on the fly to adapt to the screen size of the mobile device. Idel On 4 October 2012 16:21, Ross Gardler rgard...@opendirective.com wrote: On 4 October 2012 14:53, Idel Fuschini idel.fusch...@gmail.com wrote: Apache Mobile Filter (or AMF) is the name of the project sine 2008, and is a filter of Apache so I don't know what is the problem There is a potentially significant trademark problem (hence moving this to trademarks@): The following uses of ASF trademarks are probably infringing: Software service offerings that are for anything other than official ASF-distributed software. and You may not use ASF trademarks such as Apache or ApacheFoo or Foo in your own domain names if that use would be likely to confuse a relevant consumer about the source of software or services provided through your website http://www.apache.org/foundation/marks/ Ross Idel (owner of AMF) On 4 October 2012 14:36, Bertrand Delacretaz bdelacre...@apache.org wrote: Hi, On Thu, Oct 4, 2012 at 2:10 PM, Matthias Wessendorf mat...@apache.org wrote: https://twitter.com/smashingmag/status/253794604967669760 searching in my mail-account for 'apachemobilefilter' I do see it being mentioned with the DeviceMap proposal - but is that project _closely_ connected ?... That project has been mentioned on the devicemap dev list, http://markmail.org/message/yfmu5h3n2tggy33n , but nothing more so far. ...I think the following sentence is/was kinda confusing: Apache Mobile Filter is the easiest way to detect mobile devices. AMF is a suite of tools that allow access to a Device Repository (such as WURFL, DetectRight, 51Degrees or others) directly from Apache... I agree that the Apache Mobile Filter name might give the impression that that's an Apache project, but it's not, what that really is is a Mobile Filter for the Apache HTTP server. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] Helix for the Apache Incubator
Hi, I would like to propose Helix to be an Apache Incubator project. The proposal can be found here: http://wiki.apache.org/incubator/HelixProposal I have included the contexts of the proposal below. Thanks, Kishore G == Abstract == Helix is a cluster management system for managing partitioned and replicated resources in distributed data systems. == Proposal == Helix provides an abstraction that separates coordination and management tasks from functional tasks of a distributed system. The developer defines the system behavior via a state machine, the transitions between those states, and constraints on states and transitions that govern the system’s valid settings. Helix ensures the distributed system satisfies the state machine, controlling state changes as appropriate during common operational activities such as upgrades, component failures, bootstrapping, running maintenance tasks, and adding capacity. == Background == Helix was developed at LinkedIn to manage large clusters for several diverse applications, including a distributed, partitioned, replicated, highly available document store with a master-slave model, a search service with multiple replicas that are updated atomically and in near real-time, and a change data capture service for reliably transporting database changes to caches, other dependent databases and indexes. These services use Helix to reliably manage dozens of clusters in multiple data centers. These services meet stringent SLAs at large scale for mission-critical production applications such as search, social gestures, and profiles. Helix has proven to be flexible for a wide variety of system configurations and operational patterns, is easy to integrate, with pluggable interfaces enabling custom behavior. It depends on Apache Zookeeper for coordination and tracking of system state across the cluster, as well as providing fault tolerance. Helix is written in Java. It was developed internally at LinkedIn to meet our particular use cases, but will be useful to many organizations facing a similar need to manage large clusters. Therefore, we would like to share it the ASF and begin developing a community of developers and users within Apache. == Rationale == Many organizations can benefit from a generalized cluster management system such as Helix. While our distributed data systems use-cases for a very large website like LinkedIn has driven the design of Helix, its uses are varied and we expect many new use cases to emerge. == Current Status == === Meritocracy === Our intent with this incubator proposal is to start building a diverse developer community around Helix following the Apache meritocracy model. Since Helix was initially developed in late 2011, we have had fast adoption and contributions by multiple teams at LinkedIn. We plan to continue support for new contributors and work with those who contribute significantly to the project to make them committers. === Community === Helix is currently being used internally at LinkedIn and is in production in that company for customer-facing features. Recent public presentations of Helix and its goals garnered much interest from potential contributors. We hope to extend our contributor base significantly and invite all those who are interested in building large-scale distributed systems to participate. To further this goal, we use GitHub issue tracking and branching facilities. === Core Developers === Helix is currently being developed by three engineers at LinkedIn: Kishore Gopalakrishna, Shi Lu and Jason Zheng, and Adam Silberstein, an engineer at Trifacta. Kishore, the lead developer and architect, has experience within Apache as an S4 committer. Shi developed the partition to node mapping and rebalancing algorithm, cluster admin APIs, and the health check framework. Jason developed the cluster controller and most of the test framework. Adam developed the rich alerting framework that enables cluster-wide, “intelligent“ alerts. === Alignment === The ASF is the natural choice to host the Helix project as its goal of encouraging community-driven open-source projects fits with our vision for Helix. Many projects that can benefit from Helix will rely on Apache ZooKeeper for cluster state management, and can far more easily achieve their operational goals by using Helix. == Known Risks == === Orphaned Products === The core developers plan to work full time on the project. There is very little risk of Helix being abandoned as it is a critical part of LinkedIn's internal infrastructure and is in production use. === Inexperience with Open Source === Only one of the core developers has experience with open source development. Kishore has been actively involved with the ASF as a committer and lead developer of S4. === Homogeneous Developers === The current core developers are all from LinkedIn. However, we hope to establish a developer community that includes contributors from several corporations and we are actively
the report reminders script
Jukka Zitting wrote: Noah Slater wrote: Can we not run the cronjob ever day and have it wake up, do some date math, and then go back to sleep unless the moment is right. The moment being right defined as 72 hours before the deadline. We can, as soon as we have a patch. :-) Hopefully someone who knows the script better (where it's located, run, etc.) will fill in details on how one would go about writing such a patch. I do not know, but provided some hints earlier in this thread. Did some detective work today: The Incubator stuff was merged into the main 'marvin' reminder script in November 2011 and February 2012. See: https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_reminders/ It gets the lists of which podling is due each month, via the report_due_[1-3].txt files which are maintained by Clutch, using the data gathered from https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml See: http://incubator.apache.org/clutch.html#data -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
