Re: Markdown issue
Hi, @Ioan: that was exactly what I was trying to avoid, it feels a bit cumbersome to type the whole link instead something like [text][1](.whatevercssclass) or similar @Shane: yep, had checked also that link, unfortunately, Special attribute blocks can be used only with headers fenced code blocks. and I was looking to arbitrarily style a given link (btw, the preview pane doesn't like fenced blocks, or is it just me?) seems I'll stick with inline html, I was puzzled to see that it doesn't seem to be an easy way to put custom styles via markdown :-? anyway, thanks for the insights br, juan pablo On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org wrote: See if this helps: http://michelf.ca/projects/**php-markdown/extra/#spe-attrhttp://michelf.ca/projects/php-markdown/extra/#spe-attr Which is linked from: http://www.apache.org/dev/**cmsref.html#markdownhttp://www.apache.org/dev/cmsref.html#markdown - Shane On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote: Hi all, probably is a dumb issue and I'm missing something obvious, but so far, I haven't been able to solve it: Is there an easy way to tell a markdown link to use a specific css class? I'd like to render links pointing outside the incubator site with an external css class. I know I can write the html equivalent, but that feels unnatural, so I'd better avoid that option. I've been poking at a few site's sources, but haven't had any luck yet.. thx in advance! br, juan pablo --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org
Re: Ripple, Streams, Onami, HDT need to fix your metadata
Thanks David, fixed it for Onami and Ripple before a minute. On Tue, Mar 5, 2013 at 8:15 AM, David Crossley cross...@apache.org wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.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, 20 March 2013, 10:30: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 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/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple, Streams, Onami, HDT need to fix your metadata
I've removed the monthly schedule for Streams too. Not sure how about updating the site though, can't find instruction how to trigger that, if even needed? Thanks, Ate On 03/05/2013 08:15 AM, David Crossley wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.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, 20 March 2013, 10:30: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 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/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple, Streams, Onami, HDT need to fix your metadata
Ate Douma wrote: I've removed the monthly schedule for Streams too. Not sure how about updating the site though, can't find instruction how to trigger that, if even needed? After making source changes, then i just go to https://cms.apache.org/incubator/publish to publish the generated changes when they are ready. I did that now. The next time that someone runs Clutch (there are notes on that page) then it will pull together any pending metadata changes. -David On 03/05/2013 08:15 AM, David Crossley wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.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, 20 March 2013, 10:30: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 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/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple, Streams, Onami, HDT need to fix your metadata
On 03/05/2013 01:47 PM, David Crossley wrote: Ate Douma wrote: I've removed the monthly schedule for Streams too. Not sure how about updating the site though, can't find instruction how to trigger that, if even needed? After making source changes, then i just go to https://cms.apache.org/incubator/publish to publish the generated changes when they are ready. I did that now. Thanks! The next time that someone runs Clutch (there are notes on that page) then it will pull together any pending metadata changes. Ah, I now see those build notes on the Clutch page itself, noted for next time. I was looking for something in the README.txt in the source tree. -David On 03/05/2013 08:15 AM, David Crossley wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.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, 20 March 2013, 10:30: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 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/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail:
[VOTE] Accept Curator into the Incubator
Discussion has settled down so I am calling a VOTE for acceptance of Curator into the Apache Incubator. The vote will close at on Friday, March 8, 2013. [ ] +1 Accept Curator into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Curator into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/incubator/CuratorProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Jordan Zimmerman === PROPOSAL === Curator - ZooKeeper client wrapper and rich ZooKeeper framework Abstract Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. Proposal Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. It consists of three components that build on each other. Curator Client is a replacement for the bundled ZooKeeper class that takes care of some low-level housekeeping and provides some useful utilities. Curator Framework is a high-level API that greatly simplifies using ZooKeeper. It adds many features that build on ZooKeeper and handles the complexity of managing connections to the ZooKeeper cluster and retrying operations. Curator Recipes consists of implementations of some of the common ZooKeeper recipes. Additionally, Curator Test is included which includes utilities to help with unit testing ZooKeeper-based applications. Background Curator was initially developed by Netflix to make writing ZooKeeper-based applications easier and more reliable. Curator was open-sourced by Netflix on GitHub as an Apache 2.0 licensed project in July 2011. During this time Curator has been formally released many times and has gained widespread adoption. Rationale New users of ZooKeeper are surprised to learn that a significant amount of connection management must be done manually. For example, when the ZooKeeper client connects to the ensemble it must negotiate a new session, etc. This takes some time. If you use a ZooKeeper client API before the connection process has completed, ZooKeeper will throw an exception. These types of exceptions are referred to as recoverable errors. Curator automatically handles connection management, greatly simplifying client code. Instead of directly using the ZooKeeper APIs you use Curator APIs that internally check for connection completion and wrap each ZooKeeper API in a retry loop. Curator uses a retry mechanism to handle recoverable errors and automatically retry operations. The method of retry is customizable. Curator comes bundled with several implementations (ExponentialBackoffRetry, etc.) or custom implementations can be written. The ZooKeeper documentation describes many possible uses for ZooKeeper calling each a recipe. While the distribution comes bundled with a few implementations of these recipes, most ZooKeeper users will need to manually implement one or more of the recipes. Implementing a ZooKeeper recipe is not trivial. Besides the connection handling issues, there are numerous edge cases that are not well documented that must be considered. For example, many recipes require that an ephemeral-sequential node be created. New users of ZooKeeper will not know that there is an edge case in ephemeral-sequential node creation that requires you to put a special marker in the node’s name so that you can search for the created node if an I/O failure occurs. This is but one of many edge cases that are not well documented but are handled by Curator. Current Status Meritocracy Curator was initially developed by Jordan Zimmerman in 2011 at Netflix. Developers external to Netflix provided feedback, suggested features and fixes and implemented extensions of Curator. Netflix's engineering team has since maintained the project and has been dedicated towards its improvement. Contributors to Curator include developers from multiple organizations around the world. Curator will be a meritocracy as it enters the Incubator and beyond. Community Curator is currently used by a number of organizations all over the world. Curator has an active and growing user and developer community with active participation in the http://groups.google.com/group/curator-users mailing list and at its GitHub home: https://github.com/Netflix/curator. Since open sourcing the project, there have been fifteen individuals from various organizations who have contributed code. Core Developers The core developers for Curator are: • Jordan Zimmerman • Jay Zarfoss Jordan has contributed towards Apache ZooKeeper and both Jordan and Jay are familiar with Apache principles and philosophy for community driven software development. Alignment Curator is a natural complement for
Re: [VOTE] Accept Curator into the Incubator
+1 binding. Cheers, Chris On 3/5/13 10:21 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Discussion has settled down so I am calling a VOTE for acceptance of Curator into the Apache Incubator. The vote will close at on Friday, March 8, 2013. [ ] +1 Accept Curator into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Curator into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/incubator/CuratorProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Jordan Zimmerman === PROPOSAL === Curator - ZooKeeper client wrapper and rich ZooKeeper framework Abstract Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. Proposal Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. It consists of three components that build on each other. Curator Client is a replacement for the bundled ZooKeeper class that takes care of some low-level housekeeping and provides some useful utilities. Curator Framework is a high-level API that greatly simplifies using ZooKeeper. It adds many features that build on ZooKeeper and handles the complexity of managing connections to the ZooKeeper cluster and retrying operations. Curator Recipes consists of implementations of some of the common ZooKeeper recipes. Additionally, Curator Test is included which includes utilities to help with unit testing ZooKeeper-based applications. Background Curator was initially developed by Netflix to make writing ZooKeeper-based applications easier and more reliable. Curator was open-sourced by Netflix on GitHub as an Apache 2.0 licensed project in July 2011. During this time Curator has been formally released many times and has gained widespread adoption. Rationale New users of ZooKeeper are surprised to learn that a significant amount of connection management must be done manually. For example, when the ZooKeeper client connects to the ensemble it must negotiate a new session, etc. This takes some time. If you use a ZooKeeper client API before the connection process has completed, ZooKeeper will throw an exception. These types of exceptions are referred to as recoverable errors. Curator automatically handles connection management, greatly simplifying client code. Instead of directly using the ZooKeeper APIs you use Curator APIs that internally check for connection completion and wrap each ZooKeeper API in a retry loop. Curator uses a retry mechanism to handle recoverable errors and automatically retry operations. The method of retry is customizable. Curator comes bundled with several implementations (ExponentialBackoffRetry, etc.) or custom implementations can be written. The ZooKeeper documentation describes many possible uses for ZooKeeper calling each a recipe. While the distribution comes bundled with a few implementations of these recipes, most ZooKeeper users will need to manually implement one or more of the recipes. Implementing a ZooKeeper recipe is not trivial. Besides the connection handling issues, there are numerous edge cases that are not well documented that must be considered. For example, many recipes require that an ephemeral-sequential node be created. New users of ZooKeeper will not know that there is an edge case in ephemeral-sequential node creation that requires you to put a special marker in the node¹s name so that you can search for the created node if an I/O failure occurs. This is but one of many edge cases that are not well documented but are handled by Curator. Current Status Meritocracy Curator was initially developed by Jordan Zimmerman in 2011 at Netflix. Developers external to Netflix provided feedback, suggested features and fixes and implemented extensions of Curator. Netflix's engineering team has since maintained the project and has been dedicated towards its improvement. Contributors to Curator include developers from multiple organizations around the world. Curator will be a meritocracy as it enters the Incubator and beyond. Community Curator is currently used by a number of organizations all over the world. Curator has an active and growing user and developer community with active participation in the http://groups.google.com/group/curator-users mailing list and at its GitHub home: https://github.com/Netflix/curator. Since open sourcing the project, there have been fifteen individuals from various organizations who have contributed code. Core Developers The core developers for Curator are: € Jordan Zimmerman € Jay Zarfoss Jordan has contributed towards Apache ZooKeeper and both Jordan and Jay are familiar with Apache principles and philosophy for community driven software development.
Re: [VOTE] Accept Curator into the Incubator
On Tue, Mar 5, 2013 at 10:21 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Discussion has settled down so I am calling a VOTE for acceptance of Curator into the Apache Incubator. The vote will close at on Friday, March 8, 2013. [ ] +1 Accept Curator into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Curator into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/incubator/CuratorProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Jordan Zimmerman === PROPOSAL === Curator - ZooKeeper client wrapper and rich ZooKeeper framework Abstract Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. Proposal Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. It consists of three components that build on each other. Curator Client is a replacement for the bundled ZooKeeper class that takes care of some low-level housekeeping and provides some useful utilities. Curator Framework is a high-level API that greatly simplifies using ZooKeeper. It adds many features that build on ZooKeeper and handles the complexity of managing connections to the ZooKeeper cluster and retrying operations. Curator Recipes consists of implementations of some of the common ZooKeeper recipes. Additionally, Curator Test is included which includes utilities to help with unit testing ZooKeeper-based applications. Background Curator was initially developed by Netflix to make writing ZooKeeper-based applications easier and more reliable. Curator was open-sourced by Netflix on GitHub as an Apache 2.0 licensed project in July 2011. During this time Curator has been formally released many times and has gained widespread adoption. Rationale New users of ZooKeeper are surprised to learn that a significant amount of connection management must be done manually. For example, when the ZooKeeper client connects to the ensemble it must negotiate a new session, etc. This takes some time. If you use a ZooKeeper client API before the connection process has completed, ZooKeeper will throw an exception. These types of exceptions are referred to as recoverable errors. Curator automatically handles connection management, greatly simplifying client code. Instead of directly using the ZooKeeper APIs you use Curator APIs that internally check for connection completion and wrap each ZooKeeper API in a retry loop. Curator uses a retry mechanism to handle recoverable errors and automatically retry operations. The method of retry is customizable. Curator comes bundled with several implementations (ExponentialBackoffRetry, etc.) or custom implementations can be written. The ZooKeeper documentation describes many possible uses for ZooKeeper calling each a recipe. While the distribution comes bundled with a few implementations of these recipes, most ZooKeeper users will need to manually implement one or more of the recipes. Implementing a ZooKeeper recipe is not trivial. Besides the connection handling issues, there are numerous edge cases that are not well documented that must be considered. For example, many recipes require that an ephemeral-sequential node be created. New users of ZooKeeper will not know that there is an edge case in ephemeral-sequential node creation that requires you to put a special marker in the node’s name so that you can search for the created node if an I/O failure occurs. This is but one of many edge cases that are not well documented but are handled by Curator. Current Status Meritocracy Curator was initially developed by Jordan Zimmerman in 2011 at Netflix. Developers external to Netflix provided feedback, suggested features and fixes and implemented extensions of Curator. Netflix's engineering team has since maintained the project and has been dedicated towards its improvement. Contributors to Curator include developers from multiple organizations around the world. Curator will be a meritocracy as it enters the Incubator and beyond. Community Curator is currently used by a number of organizations all over the world. Curator has an active and growing user and developer community with active participation in the http://groups.google.com/group/curator-users mailing list and at its GitHub home: https://github.com/Netflix/curator. Since open sourcing the project, there have been fifteen individuals from various organizations who have contributed code. Core Developers The core developers for Curator are: • Jordan Zimmerman • Jay Zarfoss Jordan has contributed towards Apache ZooKeeper
Re: Markdown issue
IF I understand you correctly you might be able to simply tackle the
issue using the right CSS selector to apply styles for external links.
If links pointing inside the site use URLs not starting with http you
might want to do something like the following to match external links:
a[href^=http://;] { color: red; }
hth,
Manos
On 03/05/2013 10:18 AM, Juan Pablo Santos Rodríguez wrote:
Hi,
@Ioan: that was exactly what I was trying to avoid, it feels a bit
cumbersome to type the whole link instead something like
[text][1](.whatevercssclass) or similar
@Shane: yep, had checked also that link, unfortunately, Special attribute
blocks can be used only with headers fenced code blocks. and I was looking
to arbitrarily style a given link (btw, the preview pane doesn't like
fenced blocks, or is it just me?)
seems I'll stick with inline html, I was puzzled to see that it doesn't
seem to be an easy way to put custom styles via markdown :-?
anyway, thanks for the insights
br,
juan pablo
On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org wrote:
See if this helps:
http://michelf.ca/projects/**php-markdown/extra/#spe-attrhttp://michelf.ca/projects/php-markdown/extra/#spe-attr
Which is linked from:
http://www.apache.org/dev/**cmsref.html#markdownhttp://www.apache.org/dev/cmsref.html#markdown
- Shane
On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote:
Hi all,
probably is a dumb issue and I'm missing something obvious, but so far, I
haven't been able to solve it:
Is there an easy way to tell a markdown link to use a specific css class?
I'd like to render links pointing outside the incubator site with an
external css class. I know I can write the html equivalent, but that
feels unnatural, so I'd better avoid that option. I've been poking at a
few
site's sources, but haven't had any luck yet..
thx in advance!
br,
juan pablo
--**--**-
To unsubscribe, e-mail:
general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-help@incubator.apache.**orggeneral-h...@incubator.apache.org
--
Manos Batsis, Chief Technologist
___
_/ /_ (_)_ __
/ __ `/ __ \/ / ___/ ___// __ `/ ___/
/ /_/ / /_/ / (__ |__ )/ /_/ / /
\__,_/_.___/_//(_)__, /_/
//
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Markdown issue
In the custom extension we use there is code that lets you select a CSS
classname by adding {.classname} to the end of the text area.
Sent from my iPhone
On Mar 5, 2013, at 1:48 PM, Emmanouil Batsis (Manos) ma...@abiss.gr wrote:
IF I understand you correctly you might be able to simply tackle the issue
using the right CSS selector to apply styles for external links.
If links pointing inside the site use URLs not starting with http you might
want to do something like the following to match external links:
a[href^=http://;] { color: red; }
hth,
Manos
On 03/05/2013 10:18 AM, Juan Pablo Santos Rodríguez wrote:
Hi,
@Ioan: that was exactly what I was trying to avoid, it feels a bit
cumbersome to type the whole link instead something like
[text][1](.whatevercssclass) or similar
@Shane: yep, had checked also that link, unfortunately, Special attribute
blocks can be used only with headers fenced code blocks. and I was looking
to arbitrarily style a given link (btw, the preview pane doesn't like
fenced blocks, or is it just me?)
seems I'll stick with inline html, I was puzzled to see that it doesn't
seem to be an easy way to put custom styles via markdown :-?
anyway, thanks for the insights
br,
juan pablo
On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org wrote:
See if this helps:
http://michelf.ca/projects/**php-markdown/extra/#spe-attrhttp://michelf.ca/projects/php-markdown/extra/#spe-attr
Which is linked from:
http://www.apache.org/dev/**cmsref.html#markdownhttp://www.apache.org/dev/cmsref.html#markdown
- Shane
On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote:
Hi all,
probably is a dumb issue and I'm missing something obvious, but so far, I
haven't been able to solve it:
Is there an easy way to tell a markdown link to use a specific css class?
I'd like to render links pointing outside the incubator site with an
external css class. I know I can write the html equivalent, but that
feels unnatural, so I'd better avoid that option. I've been poking at a
few
site's sources, but haven't had any luck yet..
thx in advance!
br,
juan pablo
--**--**-
To unsubscribe, e-mail:
general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-help@incubator.apache.**orggeneral-h...@incubator.apache.org
--
Manos Batsis, Chief Technologist
___
_/ /_ (_)_ __
/ __ `/ __ \/ / ___/ ___// __ `/ ___/
/ /_/ / /_/ / (__ |__ )/ /_/ / /
\__,_/_.___/_//(_)__, /_/
//
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Permission to edit incubator wiki
Hi, Can someone grant me permissions to edit the incubator wiki? My wiki id is MatthieuMorel Thanks! Matthieu - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Permission to edit incubator wiki
On Tue, Mar 5, 2013 at 10:58 AM, Matthieu Morel mmo...@apache.org wrote: Can someone grant me permissions to edit the incubator wiki? My wiki id is MatthieuMorel Done. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE] Graduate cTAKES from Incubator
This is to open a VOTE to graduate Apache cTAKES podling from the Apache Incubator. Apache cTAKES entered the Incubator in June of 2012. We have made significant progress with the project since moving over to Apache. We currently have over 18 committers listed on our status page at [1] including over 10 which accepted after the podling was formed. A VOTE was also held on the ctakes-dev group with 12 +1 results for graduation [4]. During incubation, cTAKES has : * Produced 1 Release * Added over 10 new Committer/PPMC members and shows constant community activities * Cleared IP on code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that [2] * Established Apache cTAKES is a suitable name [3] * The community of Apache cTAKES is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. Please cast your votes: [ ] +1 Graduate Apache cTAKES podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache cTAKES podling [ ] -1 Reject graduation of Apache cTAKES podling from Apache Incubator because ... We'll run the vote for at least 72 hours. [1] http://people.apache.org/committers-by-project.html#ctakes [2] https://issues.apache.org/jira/browse/CTAKES#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-24 [4] http://markmail.org/search/+list:org.apache.incubator.ctakes-dev#query:%20list%3Aorg.apache.incubator.ctakes-dev+page:1+mid:y5lxfqrp2tgzbuwq+state:results Resolution: --- X. Establish the Apache cTAKES Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the processing of natural language text from the electronic medical record. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache cTAKES Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache cTAKES Project be and hereby is responsible for the creation and maintenance of software related to the processing of natural language text from the electronic medical record; and be it further RESOLVED, that the office of Vice President, Apache cTAKES 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 cTAKES Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache cTAKES 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 cTAKES Project: Andy McMurry and...@apache.org Britt Fitch brittfi...@apache.org Chen Lin c...@apache.org Chris Mattmann mattm...@apache.org Ding Cheng Li leonlee...@apache.org Dmitriy Dligach dlig...@apache.org Grant Ingersoll gsing...@apache.org Guergana K. Savova gsav...@apache.org Hongfang Liu liuhongf...@apache.org James J Masanz james-mas...@apache.org Jörn Kottmann jo...@apache.org Kim Ebert Matt Coarr mattco...@apache.org Karthik Sarma ksa...@apache.org Pei J Chen chen...@apache.org Scott Russell Halgrim shalg...@apache.org Sean Finan seanfi...@apache.org Sean Patrick Murphy spmurph...@apache.org Siddhartha Jonnalagadda siddhar...@apache.org Stephen Wu s...@apache.org Steven Bethard stevenbeth...@apache.org Sunghwan Sohn ss...@apache.org Tim Miller tm...@apache.org Troy C. Bleeker blee...@apache.org Vinod C Kaggal vkag...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pei J Chen be appointed to the office of Vice President, Apache cTAKES, 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 cTAKES 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 cTAKES Project; and be it further RESOLVED, that the Apache cTAKES Project be and hereby is tasked with the migration and rationalization of the Apache Incubator cTAKES podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator cTAKES 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: Markdown issue
Hi!
@Manos: that's great! didn't thought of that, but it absolutely solves the
problem
@Joseph: that looks interesting too, could you provide a link to that
extension?
thx a lot for the tips pointers
cheers,
juan pablo
On Tue, Mar 5, 2013 at 7:56 PM, Joseph Schaefer joe_schae...@yahoo.comwrote:
In the custom extension we use there is code that lets you select a CSS
classname by adding {.classname} to the end of the text area.
Sent from my iPhone
On Mar 5, 2013, at 1:48 PM, Emmanouil Batsis (Manos) ma...@abiss.gr
wrote:
IF I understand you correctly you might be able to simply tackle the
issue using the right CSS selector to apply styles for external links.
If links pointing inside the site use URLs not starting with http you
might want to do something like the following to match external links:
a[href^=http://;] { color: red; }
hth,
Manos
On 03/05/2013 10:18 AM, Juan Pablo Santos Rodríguez wrote:
Hi,
@Ioan: that was exactly what I was trying to avoid, it feels a bit
cumbersome to type the whole link instead something like
[text][1](.whatevercssclass) or similar
@Shane: yep, had checked also that link, unfortunately, Special
attribute
blocks can be used only with headers fenced code blocks. and I was
looking
to arbitrarily style a given link (btw, the preview pane doesn't like
fenced blocks, or is it just me?)
seems I'll stick with inline html, I was puzzled to see that it doesn't
seem to be an easy way to put custom styles via markdown :-?
anyway, thanks for the insights
br,
juan pablo
On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org
wrote:
See if this helps:
http://michelf.ca/projects/**php-markdown/extra/#spe-attr
http://michelf.ca/projects/php-markdown/extra/#spe-attr
Which is linked from:
http://www.apache.org/dev/**cmsref.html#markdown
http://www.apache.org/dev/cmsref.html#markdown
- Shane
On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote:
Hi all,
probably is a dumb issue and I'm missing something obvious, but so
far, I
haven't been able to solve it:
Is there an easy way to tell a markdown link to use a specific css
class?
I'd like to render links pointing outside the incubator site with an
external css class. I know I can write the html equivalent, but that
feels unnatural, so I'd better avoid that option. I've been poking at
a
few
site's sources, but haven't had any luck yet..
thx in advance!
br,
juan pablo
--**--**-
To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org
general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.**org
general-h...@incubator.apache.org
--
Manos Batsis, Chief Technologist
___
_/ /_ (_)_ __
/ __ `/ __ \/ / ___/ ___// __ `/ ___/
/ /_/ / /_/ / (__ |__ )/ /_/ / /
\__,_/_.___/_//(_)__, /_/
//
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Curator into the Incubator
+1 (non binding). On Wed, Mar 6, 2013 at 2:21 AM, Jordan Zimmerman jor...@jordanzimmerman.com wrote: Discussion has settled down so I am calling a VOTE for acceptance of Curator into the Apache Incubator. The vote will close at on Friday, March 8, 2013. [ ] +1 Accept Curator into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Curator into the incubator because... Full proposal is pasted below and the corresponding wiki is http://wiki.apache.org/incubator/CuratorProposal Only VOTEs from Incubator PMC members are binding, but all are welcome to express their thoughts. Sincerely, Jordan Zimmerman === PROPOSAL === Curator - ZooKeeper client wrapper and rich ZooKeeper framework Abstract Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. Proposal Curator is a set of Java libraries that make using Apache ZooKeeper much easier. While ZooKeeper comes bundled with a Java client, using the client is non-trivial and error prone. It consists of three components that build on each other. Curator Client is a replacement for the bundled ZooKeeper class that takes care of some low-level housekeeping and provides some useful utilities. Curator Framework is a high-level API that greatly simplifies using ZooKeeper. It adds many features that build on ZooKeeper and handles the complexity of managing connections to the ZooKeeper cluster and retrying operations. Curator Recipes consists of implementations of some of the common ZooKeeper recipes. Additionally, Curator Test is included which includes utilities to help with unit testing ZooKeeper-based applications. Background Curator was initially developed by Netflix to make writing ZooKeeper-based applications easier and more reliable. Curator was open-sourced by Netflix on GitHub as an Apache 2.0 licensed project in July 2011. During this time Curator has been formally released many times and has gained widespread adoption. Rationale New users of ZooKeeper are surprised to learn that a significant amount of connection management must be done manually. For example, when the ZooKeeper client connects to the ensemble it must negotiate a new session, etc. This takes some time. If you use a ZooKeeper client API before the connection process has completed, ZooKeeper will throw an exception. These types of exceptions are referred to as recoverable errors. Curator automatically handles connection management, greatly simplifying client code. Instead of directly using the ZooKeeper APIs you use Curator APIs that internally check for connection completion and wrap each ZooKeeper API in a retry loop. Curator uses a retry mechanism to handle recoverable errors and automatically retry operations. The method of retry is customizable. Curator comes bundled with several implementations (ExponentialBackoffRetry, etc.) or custom implementations can be written. The ZooKeeper documentation describes many possible uses for ZooKeeper calling each a recipe. While the distribution comes bundled with a few implementations of these recipes, most ZooKeeper users will need to manually implement one or more of the recipes. Implementing a ZooKeeper recipe is not trivial. Besides the connection handling issues, there are numerous edge cases that are not well documented that must be considered. For example, many recipes require that an ephemeral-sequential node be created. New users of ZooKeeper will not know that there is an edge case in ephemeral-sequential node creation that requires you to put a special marker in the node’s name so that you can search for the created node if an I/O failure occurs. This is but one of many edge cases that are not well documented but are handled by Curator. Current Status Meritocracy Curator was initially developed by Jordan Zimmerman in 2011 at Netflix. Developers external to Netflix provided feedback, suggested features and fixes and implemented extensions of Curator. Netflix's engineering team has since maintained the project and has been dedicated towards its improvement. Contributors to Curator include developers from multiple organizations around the world. Curator will be a meritocracy as it enters the Incubator and beyond. Community Curator is currently used by a number of organizations all over the world. Curator has an active and growing user and developer community with active participation in the http://groups.google.com/group/curator-users mailing list and at its GitHub home: https://github.com/Netflix/curator. Since open sourcing the project, there have been fifteen individuals from various organizations who have contributed code. Core Developers The core developers for Curator are: • Jordan Zimmerman • Jay Zarfoss Jordan has contributed towards Apache ZooKeeper and both Jordan and Jay are
Re: Markdown issue
See http://www.apache.org/dev/cmsref#markdown in particular the elementid
plugin.
Sent from my iPhone
On Mar 5, 2013, at 4:54 PM, Juan Pablo Santos Rodríguez
juanpablo.san...@gmail.com wrote:
Hi!
@Manos: that's great! didn't thought of that, but it absolutely solves the
problem
@Joseph: that looks interesting too, could you provide a link to that
extension?
thx a lot for the tips pointers
cheers,
juan pablo
On Tue, Mar 5, 2013 at 7:56 PM, Joseph Schaefer joe_schae...@yahoo.comwrote:
In the custom extension we use there is code that lets you select a CSS
classname by adding {.classname} to the end of the text area.
Sent from my iPhone
On Mar 5, 2013, at 1:48 PM, Emmanouil Batsis (Manos) ma...@abiss.gr
wrote:
IF I understand you correctly you might be able to simply tackle the
issue using the right CSS selector to apply styles for external links.
If links pointing inside the site use URLs not starting with http you
might want to do something like the following to match external links:
a[href^=http://;] { color: red; }
hth,
Manos
On 03/05/2013 10:18 AM, Juan Pablo Santos Rodríguez wrote:
Hi,
@Ioan: that was exactly what I was trying to avoid, it feels a bit
cumbersome to type the whole link instead something like
[text][1](.whatevercssclass) or similar
@Shane: yep, had checked also that link, unfortunately, Special
attribute
blocks can be used only with headers fenced code blocks. and I was
looking
to arbitrarily style a given link (btw, the preview pane doesn't like
fenced blocks, or is it just me?)
seems I'll stick with inline html, I was puzzled to see that it doesn't
seem to be an easy way to put custom styles via markdown :-?
anyway, thanks for the insights
br,
juan pablo
On Tue, Mar 5, 2013 at 3:30 AM, Shane Curcuru a...@shanecurcuru.org
wrote:
See if this helps:
http://michelf.ca/projects/**php-markdown/extra/#spe-attr
http://michelf.ca/projects/php-markdown/extra/#spe-attr
Which is linked from:
http://www.apache.org/dev/**cmsref.html#markdown
http://www.apache.org/dev/cmsref.html#markdown
- Shane
On 3/4/2013 6:46 PM, Juan Pablo Santos Rodríguez wrote:
Hi all,
probably is a dumb issue and I'm missing something obvious, but so
far, I
haven't been able to solve it:
Is there an easy way to tell a markdown link to use a specific css
class?
I'd like to render links pointing outside the incubator site with an
external css class. I know I can write the html equivalent, but that
feels unnatural, so I'd better avoid that option. I've been poking at
a
few
site's sources, but haven't had any luck yet..
thx in advance!
br,
juan pablo
--**--**-
To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.org
general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.**org
general-h...@incubator.apache.org
--
Manos Batsis, Chief Technologist
___
_/ /_ (_)_ __
/ __ `/ __ \/ / ___/ ___// __ `/ ___/
/ /_/ / /_/ / (__ |__ )/ /_/ / /
\__,_/_.___/_//(_)__, /_/
//
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate cTAKES from Incubator
+1 binding. Great job great community great project. Cheers, Chris On 3/5/13 12:54 PM, Chen, Pei pei.c...@childrens.harvard.edu wrote: This is to open a VOTE to graduate Apache cTAKES podling from the Apache Incubator. Apache cTAKES entered the Incubator in June of 2012. We have made significant progress with the project since moving over to Apache. We currently have over 18 committers listed on our status page at [1] including over 10 which accepted after the podling was formed. A VOTE was also held on the ctakes-dev group with 12 +1 results for graduation [4]. During incubation, cTAKES has : * Produced 1 Release * Added over 10 new Committer/PPMC members and shows constant community activities * Cleared IP on code * Developed Roadmap(s) for the next major and minor releases in a community process and started working on that [2] * Established Apache cTAKES is a suitable name [3] * The community of Apache cTAKES is active, healthy, and growing and has demonstrated the ability to self-govern using accepted Apache practices. Please cast your votes: [ ] +1 Graduate Apache cTAKES podling from Apache Incubator [ ] +0 Indifferent to the graduation status of Apache cTAKES podling [ ] -1 Reject graduation of Apache cTAKES podling from Apache Incubator because ... We'll run the vote for at least 72 hours. [1] http://people.apache.org/committers-by-project.html#ctakes [2] https://issues.apache.org/jira/browse/CTAKES#selectedTab=com.atlassian.jir a.plugin.system.project%3Aroadmap-panel [3] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-24 [4] http://markmail.org/search/+list:org.apache.incubator.ctakes-dev#query:%20 list%3Aorg.apache.incubator.ctakes-dev+page:1+mid:y5lxfqrp2tgzbuwq+state:r esults Resolution: --- X. Establish the Apache cTAKES Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to the processing of natural language text from the electronic medical record. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache cTAKES Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache cTAKES Project be and hereby is responsible for the creation and maintenance of software related to the processing of natural language text from the electronic medical record; and be it further RESOLVED, that the office of Vice President, Apache cTAKES 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 cTAKES Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache cTAKES 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 cTAKES Project: Andy McMurry and...@apache.org Britt Fitch brittfi...@apache.org Chen Lin c...@apache.org Chris Mattmann mattm...@apache.org Ding Cheng Li leonlee...@apache.org Dmitriy Dligach dlig...@apache.org Grant Ingersoll gsing...@apache.org Guergana K. Savova gsav...@apache.org Hongfang Liu liuhongf...@apache.org James J Masanz james-mas...@apache.org Jörn Kottmann jo...@apache.org Kim Ebert Matt Coarr mattco...@apache.org Karthik Sarma ksa...@apache.org Pei J Chen chen...@apache.org Scott Russell Halgrim shalg...@apache.org Sean Finan seanfi...@apache.org Sean Patrick Murphy spmurph...@apache.org Siddhartha Jonnalagadda siddhar...@apache.org Stephen Wu s...@apache.org Steven Bethard stevenbeth...@apache.org Sunghwan Sohn ss...@apache.org Tim Miller tm...@apache.org Troy C. Bleeker blee...@apache.org Vinod C Kaggal vkag...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Pei J Chen be appointed to the office of Vice President, Apache cTAKES, 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 cTAKES 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 cTAKES Project; and be it further RESOLVED, that the Apache cTAKES Project be and hereby is tasked with the migration and rationalization of the Apache Incubator cTAKES podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator cTAKES podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands,
Re: [VOTE] Release Apache Mesos 0.10.0-incubating (RC4)
Hi Ben, Chris, +1 (binding) from me as well. Great job guys. -Andrew. output FYI: andrew@pluto ~/mesos $ uname -a Linux pluto 3.0.0-16-generic #29-Ubuntu SMP Tue Feb 14 12:48:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux andrew@pluto ~/mesos $ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-incubating.tar.gz ... andrew@pluto ~/mesos $ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-incubating.tar.gz.md5 ... andrew@pluto ~/mesos $ wget http://people.apache.org/~benh/mesos-0.10.0-incubating-RC4/mesos-0.10.0-incubating.tar.gz.asc ... andrew@pluto ~/mesos $ md5sum mesos-0.10.0-incubating.tar.gz 6aa70e04902d4f27d30f74a142206dd4 mesos-0.10.0-incubating.tar.gz andrew@pluto ~/mesos $ wget http://svn.apache.org/repos/asf/incubator/mesos/dist/KEYS ... andrew@pluto ~/mesos $ gpg --import KEYS gpg: keyring `/home/andrew/.gnupg/secring.gpg' created gpg: /home/andrew/.gnupg/trustdb.gpg: trustdb created gpg: key F6FB762C: public key Benjamin Hindman b...@apache.org imported gpg: key 1B207A4D: public key Andy Konwinski (CODE SIGNING KEY) and...@apache.org imported gpg: Total number processed: 2 gpg: imported: 2 (RSA: 2) andrew@pluto ~/mesos $ gpg --verify mesos-0.10.0-incubating.tar.gz.asc gpg: Signature made Thu 07 Feb 2013 10:22:30 PM PST using RSA key ID F6FB762C gpg: Good signature from Benjamin Hindman b...@apache.org gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4BF2 061E 7300 3185 CA06 E30F F99D 6AD0 F6FB 762C andrew@pluto ~/mesos $ tar xzvf mesos-0.10.0-incubating.tar.gz ... andrew@pluto ~/mesos $ cd mesos-0.10.0/ andrew@pluto ~/mesos/mesos-0.10.0 $ ./configure --disable-java ... andrew@pluto ~/mesos/mesos-0.10.0 $ make ... [lots of output suppressed] ... creating build/bdist.linux-x86_64 creating build/bdist.linux-x86_64/egg copying build/lib.linux-x86_64-2.7/mesos.py - build/bdist.linux-x86_64/egg copying build/lib.linux-x86_64-2.7/mesos_pb2.py - build/bdist.linux-x86_64/egg copying build/lib.linux-x86_64-2.7/_mesos.so - build/bdist.linux-x86_64/egg byte-compiling build/bdist.linux-x86_64/egg/mesos.py to mesos.pyc byte-compiling build/bdist.linux-x86_64/egg/mesos_pb2.py to mesos_pb2.pyc creating stub loader for _mesos.so byte-compiling build/bdist.linux-x86_64/egg/_mesos.py to _mesos.pyc creating build/bdist.linux-x86_64/egg/EGG-INFO copying src/mesos.egg-info/PKG-INFO - build/bdist.linux-x86_64/egg/EGG-INFO copying src/mesos.egg-info/SOURCES.txt - build/bdist.linux-x86_64/egg/EGG-INFO copying src/mesos.egg-info/dependency_links.txt - build/bdist.linux-x86_64/egg/EGG-INFO copying src/mesos.egg-info/top_level.txt - build/bdist.linux-x86_64/egg/EGG-INFO writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt zip_safe flag not set; analyzing archive contents... creating dist creating 'dist/mesos-0.10.0-py2.7-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it removing 'build/bdist.linux-x86_64/egg' (and everything under it) make[2]: Leaving directory `/home/andrew/mesos/mesos-0.10.0/src' make[1]: Leaving directory `/home/andrew/mesos/mesos-0.10.0/src' Making all in ec2 make[1]: Entering directory `/home/andrew/mesos/mesos-0.10.0/ec2' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/andrew/mesos/mesos-0.10.0/ec2' Making all in hadoop make[1]: Entering directory `/home/andrew/mesos/mesos-0.10.0/hadoop' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/andrew/mesos/mesos-0.10.0/hadoop' On 03/04/2013 09:29 PM, Mattmann, Chris A (388J) wrote: Great. We just need 1 more IPMC +1 here. Anyone willing to contribute a review of Mesos 0.10.0-incubating RC4? Cheers, Chris On 3/4/13 9:57 AM, Benjamin Hindman b...@eecs.berkeley.edu wrote: Yes, my vote is a +1. On Sat, Mar 2, 2013 at 4:40 PM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Ben, just FYI on this, is your VOTE +1? The current tally I have is: +1 Chris Mattmann* * - IPMC We need probably a couple VOTEs from the Mesos community here (PPMC members), can you poke Vinod, as well as anyone else that has time to build and test and review the RC? IPMC folks -- a review and a couple more binding VOTEs would really help out Mesos here. Can folks try it out and VOTE? Thank you. Cheers, Chris Vote Wrangler Mattmann On 2/7/13 10:32 PM, Benjamin Hindman b...@berkeley.edu wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.10.0. This will be the second incubator release for Mesos in Apache. -- --- Changes since last release candidate: * Updated configure.ac to work better on OS X 10.8. * Added missing license (the only blocker on the previous candidate).
