Re: [DISCUSSION] Retire Chukwa from incubation
Hi Alexei, Chukwa started before Flume and Kafka started. Flume community has flourish with Cloudera behind it. In my experience Flume has been more fluid, and Chukwa has been more solid. Chukwa can't swim in flume 1.2 branch because flume is becoming more like Chukwa. Unfortunately, most of Chukwa community don't get used to Flume syntax and centralized configuration via ZooKeeper. Kafka is a much younger project in comparison to Chukwa or Flume. I don't know much about scala but providing solid scalable Java API on scala seems like a project of it's own right that neither Kafka nor Chukwa community would be interested. Chris has done the research in Apache, and did not find any possible projects that would be a good fit to shelter Chukwa. regards, Eric On Wed, Nov 28, 2012 at 5:46 AM, Alexei Fedotov alexei.fedo...@gmail.comwrote: Let me rephrase the question. Could the actual reason behind Chukwa retirement be related to the fact, that there exist Flume and Kafka which gives users same opportunites to manage distributed systems? I better understand this before trying to spread the word about joinging Chukwa community. If this is the case, could it be that there are ways to mergre projects somehow, e.g. provide Chukwa API on the top of Flume or Kafka? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 6:23 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Hello guys, I want to understand Chukwa community building strategy better. Are there any insights why companies which use Hadoop (in Moscow those include Deutche Bank, Yandex, Rambler and Microsoft) do not crowd around or stay in line to get a chance to use Chukwa? -- With best regards / с наилучшими пожеланиями, Alexei Fedotov / Алексей Федотов, http://dataved.ru/ +7 916 562 8095 On Tue, Nov 27, 2012 at 3:55 PM, ant elder ant.el...@gmail.com wrote: On Tue, Nov 27, 2012 at 11:48 AM, Benson Margulies bimargul...@gmail.comwrote: One interesting point about consensus decision-making process is the need to define the starting point. The process assumes that there is a clear 'status quo', and that a consensus is required to change it. This may not always be the appropriate way to think about retiring a podling, but it's clearly the way we're thinking about this one. Does anyone else feel that this could have benefitted from a [DISCUSS] before the [VOTE]. At the bottom line, if there are new mentors to be fully responsible, I think it's reasonable to continue; however, I don't want to have exactly the same conversation in N months. Would the new mentors like to propose a time limit, and is the group willing to subscribe to the notion that, if after that time, the new mentors have the same report as the old mentors, we're at the end? Could we maybe include a time limit next month with the credible plan to give new mentors a little time to get up to speed with the project? ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
Hi all, Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 I am fine with a change of the format. But at the moment we (Celix) still have a pending release. Seeing that many other project use different formats, I personally don't see this as a show stopper for our current release.. Can we somehow reach a consensus that for a next release the format will be different? (ie the format used by md5sum). -- Met vriendelijke groet, Alexander Broekhuis
Re: Retirement decision making
On Wednesday, November 28, 2012, Greg Reddin wrote: ...What difference does it make to the ASF if a project is very small or very slow?... IMO, as long as there's three or more active PMC members who react when needed, and provide the quarterly board reports, a small/slow project is fine and there's no need to move it to the attic. -Bertrand
Re: Retirement decision making
On Thu, Nov 29, 2012 at 8:56 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Wednesday, November 28, 2012, Greg Reddin wrote: ...What difference does it make to the ASF if a project is very small or very slow?... IMO, as long as there's three or more active PMC members who react when needed, and provide the quarterly board reports, a small/slow project is fine and there's no need to move it to the attic. -Bertrand One of the issues with that is the interpretation of what active means. So we can look at poddlings which aren't very active and say it doesn't have three people committing regularly and therefore doesn't meet that requirement. However in reality there maybe three people who are at least watching and would step up and interact on votes etc when things require it. There are TLPs that operate like that. Is that enough for a poddling? I think the answer comes down to that trust issue, if its a bunch of ASF members we all know we're more lenient than if its a bunch of new comers none of us know. ...ant
Re: Retirement decision making
On 29 November 2012 08:56, Bertrand Delacretaz bdelacre...@apache.orgwrote: On Wednesday, November 28, 2012, Greg Reddin wrote: ...What difference does it make to the ASF if a project is very small or very slow?... IMO, as long as there's three or more active PMC members who react when needed, and provide the quarterly board reports, a small/slow project is fine and there's no need to move it to the attic. +1 - oversight is what matters. If the PMC is happy to continue as is then all is good. As previously stated my concern is whether the PMC is operating in a way in which the building and maintenance of a diverse community is possible. For example, when a new patch turns up are they reviewing and applying it and are they bringing in the new community member. Note that in this months reports the board were asked, by a TLP, for feedback on the dormant state they found themselves in, the PMC was reactive when necessary but not proactively developing the code or the community. The boards feedback was in line with Bertrands comment above - the PMC is providing sufficient oversight so no problem. In another case this month a TLP indicated one of their sub-projects was dormant to the extent that patches were not being reviewed. The board asked if there was a plan and the PMC responded with unity that it will be addressed. So no problem, the PMC is aware of the issue and is addressing it. Drawing this to its natural conclusion a podling should be graduated once it demonstrates an ability to operate as an Apache project without the need for binding IPMC votes on releases etc. A podling should be retired if there is insufficient interest from both the PPMC and the IPMC to move it towards this state (which brings me back to my original 3 stages of decision making about podling retirement). (Ant's email about trust overlapped with me typing this one, I think that is another side of the same coin and fully support his comments) Ross -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: [PROPOSAL] Apache Marmotta
On Monday, November 26, 2012, Andy Seaborne wrote: ...One of the mentors is not yet formally a member of IPMC so we're waiting until we have three formal mentors before calling the proposal vote IMO you can go forward with the vote and indicate that having Fabian as a mentor is pending final Incubator PMC membership approval as we did with Flex, see http://markmail.org/message/puo2rtrvby65lb3m -Bertrand
[VOTE] Accept Marmotta into the incubator
Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly * Move the existing LMF source from the current Google Code page to the Apache infrastructure * Remove LMF extensions that are not relevant for a core Linked Data platform (e.g. semantic search and content enhancement) * Define a
Re: [VOTE] Accept Marmotta into the incubator
+1 (binding) On 29 November 2012 11:28, Andy Seaborne a...@apache.org wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/**incubator/MarmottaProposalhttp://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly * Move the existing LMF source from the current Google Code page to the Apache
Re: [VOTE] Accept Marmotta into the incubator
+1 (unbinding since I am not yet an IPMC member) 2012/11/29 Ross Gardler rgard...@opendirective.com +1 (binding) On 29 November 2012 11:28, Andy Seaborne a...@apache.org wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/**incubator/MarmottaProposal http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and
Re: [VOTE] Accept Marmotta into the incubator
+1 binding Regards, Alan On Nov 29, 2012, at 3:28 AM, Andy Seaborne wrote: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
On Thu, Nov 29, 2012 at 12:28 PM, Andy Seaborne a...@apache.org wrote: ...Please cast your votes on whether to accept the Apache Marmotta proposal... +1 with a small caveat: ... = Nominated Mentors Fabian Christ (fchrist at apache dot org)... Fabian is not currently a member of the Incubator PMC, so him being a mentor is subject to being voted in and accepted by the board. We are working on this, and should be able to confirm that within 72 hours - just wanted to point out that formally he's not in yet. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
On Nov 29, 2012, at 1:14 AM, Ross Gardler wrote: On 29 November 2012 08:56, Bertrand Delacretaz bdelacre...@apache.orgwrote: On Wednesday, November 28, 2012, Greg Reddin wrote: ...What difference does it make to the ASF if a project is very small or very slow?... IMO, as long as there's three or more active PMC members who react when needed, and provide the quarterly board reports, a small/slow project is fine and there's no need to move it to the attic. +1 - oversight is what matters. If the PMC is happy to continue as is then all is good. As previously stated my concern is whether the PMC is operating in a way in which the building and maintenance of a diverse community is possible. For example, when a new patch turns up are they reviewing and applying it and are they bringing in the new community member. Note that in this months reports the board were asked, by a TLP, for feedback on the dormant state they found themselves in, the PMC was reactive when necessary but not proactively developing the code or the community. The boards feedback was in line with Bertrands comment above - the PMC is providing sufficient oversight so no problem. In another case this month a TLP indicated one of their sub-projects was dormant to the extent that patches were not being reviewed. The board asked if there was a plan and the PMC responded with unity that it will be addressed. So no problem, the PMC is aware of the issue and is addressing it. Drawing this to its natural conclusion a podling should be graduated once it demonstrates an ability to operate as an Apache project without the need for binding IPMC votes on releases etc. A podling should be retired if there is insufficient interest from both the PPMC and the IPMC to move it towards this state (which brings me back to my original 3 stages of decision making about podling retirement). Would you also add the three or more active PMC members requirement? What constitutes active? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
Hi, On Thu, Nov 29, 2012 at 12:28 PM, Andy Seaborne a...@apache.org wrote: Please cast your votes on whether to accept the Apache Marmotta proposal: +1 (binding) Best Regards, Nandana
Re: [VOTE] Accept Marmotta into the incubator
+1 binding Sent from my iPhone On Nov 29, 2012, at 6:28 AM, Andy Seaborne a...@apache.org wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
+1 On Thu, Nov 29, 2012 at 6:35 PM, Dave Fisher dave2w...@comcast.net wrote: +1 binding Sent from my iPhone On Nov 29, 2012, at 6:28 AM, Andy Seaborne a...@apache.org wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. - 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: Retirement decision making
On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
On Nov 29, 2012, at 6:53 AM, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. And so by extension we can apply this to podlings as well. So if the IP is vetted and we trust the PPMC members then the podling has met all the requirements for incubation? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
New graduation jiras
http://www.apache.org/dev/infra-contact#requesting-graduation outlines the jira tickets infra would like to see when a project requests resources migration at TLP graduation. The biggest change is that DNS/website/mailinglists are handled by 1 ticket. Some caveats not documented there are: - The PMC chair is still responsible for using modify_unix_group as appropriate --- we initialise the group membership on a best-guess basis, but the chair must check that it's accurate and add/rm people as needed. modify_committee however is initialised directly from the Board resolution (thanks mostarda@ for the parsing code). The under-the-hood is a new set of scripts that parse the board minutes and automate a few common parts of the graduation process. That's all --- I think everything else is documented on the link. Questions? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Marmotta into the incubator
+1 (binding) On Thu, Nov 29, 2012 at 6:39 AM, Alexei Fedotov alexei.fedo...@gmail.comwrote: +1 On Thu, Nov 29, 2012 at 6:35 PM, Dave Fisher dave2w...@comcast.net wrote: +1 binding Sent from my iPhone On Nov 29, 2012, at 6:28 AM, Andy Seaborne a...@apache.org wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. - 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 Marmotta into the incubator
+1 (binding). Cheers, Chris On Nov 29, 2012, at 3:28 AM, Andy Seaborne wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly * Move the existing LMF source from the current Google Code page to
Re: Retirement decision making
On 29 November 2012 14:59, Alan Cabrera l...@toolazydogs.com wrote: On Nov 29, 2012, at 6:53 AM, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. And so by extension we can apply this to podlings as well. So if the IP is vetted and we trust the PPMC members then the podling has met all the requirements for incubation? +1 -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: Retirement decision making
On Nov 29, 2012, at 7:45 AM, Ross Gardler wrote: On 29 November 2012 14:59, Alan Cabrera l...@toolazydogs.com wrote: On Nov 29, 2012, at 6:53 AM, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. And so by extension we can apply this to podlings as well. So if the IP is vetted and we trust the PPMC members then the podling has met all the requirements for incubation? +1 Well this dramatically changes what I though I was supposed to do. I thought I was doing my duty as a mentor when I scraped up my 9 pence and dragged Chukwa to the curb. http://www.youtube.com/watch?v=Sh8mNjeuyV4 By the criteria described above the podling is most likely good to go; in the good way not the bad way. It would probably be a good idea to add some kind of designation to the graduating podling officially informing it that in the estimation of the IPMC it has not yet obtained its vibrant and diverse requirements and that it will be required to submit a plan and track progress in its board reports. Maybe TLPs can be put on some kind of official probation, or some term less severe. The Attic can be the shepherds for TLPs in probation. The benefits are that the podlings no longer need to go through the sometimes arduous Incubator release cycle. They loose the stigma of being a podling. Strangers coming in understand that the TLP does not meet the ASF standard for diversity and vibrancy but the ASF still holds out great hope. Regards, Alan
Re: [VOTE] Accept Marmotta into the incubator
+1 (binding) Ralph On Nov 29, 2012, at 3:28 AM, Andy Seaborne wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly * Move the existing LMF source from the current Google Code page to the
Re: [VOTE] Accept Marmotta into the incubator
+1 (binding) On Thu, Nov 29, 2012 at 9:07 AM, Ralph Goers ralph.go...@dslextreme.comwrote: +1 (binding) Ralph On Nov 29, 2012, at 3:28 AM, Andy Seaborne wrote: Hi there, Following the discussion thread, here is the formal vote on the Marmotta proposal: Please cast your votes on whether to accept the Apache Marmotta proposal: [ ] +1 Accept Marmotta into the Apache Incubator [ ] +0 Indifferent to the acceptance of Marmotta [ ] -1 Do not accept the Marmotta proposal because ... The vote will be open until at least 23:59 Sunday 2nd December UTC (which is three full days from midnight tonight) Andy http://wiki.apache.org/incubator/MarmottaProposal --- == Abstract Marmotta is a Linked Data platform for industry-strength installations. == Proposal The goal of Apache Marmotta is to provide an open implementation of a Linked Data Platform that can be used, extended, and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. The phrase Linked Data is used here idiosyncratically to refer to a data integration paradigm across the Web. The term was coined by Tim Berners-Lee in 2006, and it is based on four very simple principles which basically describe recommended best practices for exposing, sharing, and connecting pieces of data, information, and knowledge on the Semantic Web using URIs and the RDF technology stack. Therefore Linked Data is about using the Web to connect related data that wasn't previously linked, or using the Web to lower the barriers to linking data currently linked using other methods. Marmotta will follow the core recommendations of the W3C on RDF, SPARQL and Linked Data publishing, particularly the emerging Linked Data Platform (LDP) recommendation. It will also offer extensions for frequently needed additional functionalities like Linked Data Querying, WebID, WebACL, Reasoning, and Versioning. Marmotta aims to cover both, Linked Open Data, as well as Enterprise Linked Data scenarios, providing facilities to deal with different data sources and requirements (small data/big data, open access/restricted access, etc). == Background The Semantic Web isn't just about putting data on the web. It is about making links, so that a person or machine can explore the web of data. Moreover, the Web has quickly evolved to a Read-Write paradigm, and Linked Data technologies too. And Marmotta will address this challenge and offer a common infrastructure for organizations working in this area. Marmotta comes as a continuation of the work in the Linked Media Framework (aka LMF) project. LMF is an easy-to-setup server application that bundles central Semantic Web technologies to offer some advanced services. The Linked Media Framework consists of LMF Core which provides a Read-Write Linked Data server, plus some modules that complement the server with other added added capabilities, such as, SPARQL 1.1, LDPath, LDCache, Reasoning, Versioning, etc. Besides, LMF also provides a Client Library, currently available in Java, PHP, and Javascript, as a convenient API abstraction around the LMF web services. Currently LMF integrates with other relevant tools (Apache Stanbol, Google Refine or Drupal) to cover a wider range of use cases and needs. == Rationale Linked Data technologies are now at a turning point from mostly research projects to industrial applications, and a lot of standardisation is currently in progress. Industrial applications require a reliable and scalable infrastructure that follows and helps defining a standard way of publishing and consuming Linked Data on the Web. The proposers have a strong background in building such applications and have invested considerable effort in the last years to building up an initial version of such a platform (the “Linked Media Framework” or “LMF”). Starting from this solid base, we strongly believe that Apache is the right environment to open the development of this project to a wider scope. Marmotta has the potential of being a reference implementation and Apache provides a better environment for a collaborative development effort. With its well-established governance model based on meritocracy and handling IP/legal issues, people from different organizations can more easily contribute to the project. This will help unify the efforts of people implementing the Linked Data Platform specification and other Semantic Web standards. In addition, it would considerably help organizations in adopting Linked Data technologies and would provide a solid base for further research activities in the community. == Initial Goals * Foster the use of Semantic Web Technologies in industry * Provide an open source and community-driven implementation of a Linked Data Platform and related Semantic Web standards, LDP 1.0 Draft and SPARQL 1.1 mainly *
Re: [VOTE] Accept Marmotta into the incubator
On 29 November 2012 21:28, Andy Seaborne a...@apache.org wrote: == Relationships with Other Apache Projects Although current RDF/SPARQL support in LMF is build on top of OpenRDF Sesame API, Marmotta is closely related to many Apache projects, such as Stanbol, Jena and Any23. See “Alignment” above. Hi Andy, Any23 is also based on the OpenRDF Sesame API, so it doesn't seem to fit in a list after Although. It may be easier to fit it in the list before saying Although. In addition, Stanbol can theoretically work with OpenRDF Sesame API through Clerezza, or through OWLAPI with my extensions that have not yet been accepted into the OWLAPI trunk. May be easier to avoid saying Although altogether. Good luck Marmotta team! Cheers, Peter - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
On 29/11/12 14:53, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. I think we need to be a bit careful about graduating a podling that is a minimum viable project. That's not say it shouldn't be done but if it's minimal, and looks ropey, then we're aren't doing us or them any favours if the project looks likely to get into problems quite soon. After all, graduation itself requires project resource. Andy -Bertrand - 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: Retirement decision making
Hard cases make bad law. The rough parameters of the recent 'small graduates' was that they had around 5 initial PMC members, and some detectable evidence that all of them were in the reasonably regular habit of contributing code, let alone voting for releases. If we insist on testing the absolute lower limit of viability, we're may bump into the absurd. On Thu, Nov 29, 2012 at 4:45 PM, Andy Seaborne a...@apache.org wrote: On 29/11/12 14:53, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. I think we need to be a bit careful about graduating a podling that is a minimum viable project. That's not say it shouldn't be done but if it's minimal, and looks ropey, then we're aren't doing us or them any favours if the project looks likely to get into problems quite soon. After all, graduation itself requires project resource. Andy -Bertrand - 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 Nuvem as a sub-project under Apache Tuscany
On Mon, Nov 19, 2012 at 9:41 PM, Luciano Resende luckbr1...@gmail.comwrote: Apache Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. It is currently composed of multiple cloud SCA components (Data, Queue, Chat), and supports multiple cloud platforms such as AWS, GAE, etc as well as standalone deployment. Nuvem was accepted for Incubation on June, 2010, and several of the active committers are already part of the Tuscany PMC. Nuvem was accepted for Incubation on June 2010, and is currently a small community, where the contributions are 100% done by volunteers in their own free time, which makes the level of activity low, compared to what is required for graduating it as a TLP. Having said that, Nuvem has a great synergy with Apache Tuscany, and after discussion between the two projects, we are seeking IPMC approval to allow graduation of Apache Nuvem as a sub-project under Apache Tuscany. Nuvem Graduation Vote thread *http://s.apache.org/nuvem-graduation* *http://s.apache.org/nuvem-graduation-result* Tuscany Graduation Vote thread *http://s.apache.org/tuscany-accept-nuvem* *http://s.apache.org/tuscany-accept-nuvem-result* Please cast your votes: [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache Tuscany, because ... +1 off course. -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
[RESULT][VOTE] Graduate Nuvem as a sub-project under Apache Tuscany
On Mon, Nov 19, 2012 at 9:41 PM, Luciano Resende luckbr1...@gmail.comwrote: Apache Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. It is currently composed of multiple cloud SCA components (Data, Queue, Chat), and supports multiple cloud platforms such as AWS, GAE, etc as well as standalone deployment. Nuvem was accepted for Incubation on June, 2010, and several of the active committers are already part of the Tuscany PMC. Nuvem was accepted for Incubation on June 2010, and is currently a small community, where the contributions are 100% done by volunteers in their own free time, which makes the level of activity low, compared to what is required for graduating it as a TLP. Having said that, Nuvem has a great synergy with Apache Tuscany, and after discussion between the two projects, we are seeking IPMC approval to allow graduation of Apache Nuvem as a sub-project under Apache Tuscany. Nuvem Graduation Vote thread *http://s.apache.org/nuvem-graduation* *http://s.apache.org/nuvem-graduation-result* Tuscany Graduation Vote thread *http://s.apache.org/tuscany-accept-nuvem* *http://s.apache.org/tuscany-accept-nuvem-result* Please cast your votes: [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache Tuscany, because ... Vote passed with 6 binding +1 from : Jukka Zitting Bertrand Delacretaz Matt Franklin Raymond Feng Alan Cagrega Senaka Fernando Luciano Resende And 3 non-binding +1 from : Jean-Sebastien Delfino Sagara Gunathunga And no -1 votes. Thanks -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: [VOTE] Graduate Apache Wink from Incubator
On Sun, Nov 25, 2012 at 3:49 PM, Luciano Resende luckbr1...@gmail.comwrote: The Apache Wink project entered incubator in May of 2009. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Wink community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Wink podling from Incubator [ ] +0 Indifferent to graduation status of Wink [ ] -1 Reject graduation of Wink podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/wink-graduation-vote [2] http://s.apache.org/wink-graduation-result [3] http://s.apache.org/wink-graduation-resolution Resolution: X.Establish the Apache Wink 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 enabling development and consumption of REST style web services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Wink Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Wink Project be and hereby is responsible for the creation and maintenance of a software project related to enabling development and consumption of REST style web services; and be it further RESOLVED, that the office of Vice President, Apache Wink 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 Wink Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Wink 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 Wink Project: * Bryant Luk (bluk) * Christopher James Blythe (cjblythe) * Dustin Amrhein (damrhei) * Davanum Srinivas (dims) * Eli Baram (elib) * Michael Elman (elman) * Jesse A. Ramos (jramos) * Kevan Lee Miller (kevan) * Luciano Resende (lresende) * Martin Snitkovsky (martins) * Nadav Fischer (nfischer) * Nicholas L. Gallardo (ngallardo) * Zhaohui Feng (rfeng) * Michael Rheinheimer (rott) * Tomer Shadi (tomershadi) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luciano Resende, be and hereby is appointed to the office of Vice President, Wink, 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 Wink Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Wink podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Wink podling encumbered upon the Apache Incubator PMC are hereafter discharged. Regards Off course, here is my +1 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
[RESULT][VOTE] Graduate Apache Wink from Incubator
On Sun, Nov 25, 2012 at 3:49 PM, Luciano Resende luckbr1...@gmail.comwrote: The Apache Wink project entered incubator in May of 2009. Since then it has grown the community in users, committers and PPMC members, made significant improvements to the project codebase and completed many releases following ASF policies and guidelines. The Apache Wink community has voted to proceed with graduation [1] and the result can be found at [2]. Discussion about the proposed resolution is also available at [3]. Please cast your votes: [ ] +1 Graduate Wink podling from Incubator [ ] +0 Indifferent to graduation status of Wink [ ] -1 Reject graduation of Wink podling from Incubator because ... Please find the proposed board resolution below. [1] http://s.apache.org/wink-graduation-vote [2] http://s.apache.org/wink-graduation-result [3] http://s.apache.org/wink-graduation-resolution Resolution: X.Establish the Apache Wink 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 enabling development and consumption of REST style web services. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the The Apache Wink Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that The Apache Wink Project be and hereby is responsible for the creation and maintenance of a software project related to enabling development and consumption of REST style web services; and be it further RESOLVED, that the office of Vice President, Apache Wink 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 Wink Project, and to have primary responsibility for management of the projects within the scope of responsibility of The Apache Wink 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 Wink Project: * Bryant Luk (bluk) * Christopher James Blythe (cjblythe) * Dustin Amrhein (damrhei) * Davanum Srinivas (dims) * Eli Baram (elib) * Michael Elman (elman) * Jesse A. Ramos (jramos) * Kevan Lee Miller (kevan) * Luciano Resende (lresende) * Martin Snitkovsky (martins) * Nadav Fischer (nfischer) * Nicholas L. Gallardo (ngallardo) * Zhaohui Feng (rfeng) * Michael Rheinheimer (rott) * Tomer Shadi (tomershadi) NOW, THEREFORE, BE IT FURTHER RESOLVED, that Luciano Resende, be and hereby is appointed to the office of Vice President, Wink, 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 Wink Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Wink podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Wink podling encumbered upon the Apache Incubator PMC are hereafter discharged. Vote passed with 8 binding +1 from : Alan Cabrera Davanum Srinivas Suresh Marru Raymond Feng Jukka Zitting Nandana Mihindukulasooriya Bertrand Delacretaz Luciano Resende And no -1. Thanks -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Sub-project graduation question
Just trying to clarify, based on [1] it seems that when a project is graduating into an existing TLP, once the IPMC vote is done, there is no need to seek Board approval and the hand-over and infrastructure tasks can start happening. Is that the correct understanding ? [1] http://incubator.apache.org/guides/graduation.html#subproject Thanks -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: [RESULT][VOTE] Graduate Nuvem as a sub-project under Apache Tuscany
On Thu, Nov 29, 2012 at 8:43 PM, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Nov 19, 2012 at 9:41 PM, Luciano Resende luckbr1...@gmail.comwrote: Apache Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. It is currently composed of multiple cloud SCA components (Data, Queue, Chat), and supports multiple cloud platforms such as AWS, GAE, etc as well as standalone deployment. Nuvem was accepted for Incubation on June, 2010, and several of the active committers are already part of the Tuscany PMC. Nuvem was accepted for Incubation on June 2010, and is currently a small community, where the contributions are 100% done by volunteers in their own free time, which makes the level of activity low, compared to what is required for graduating it as a TLP. Having said that, Nuvem has a great synergy with Apache Tuscany, and after discussion between the two projects, we are seeking IPMC approval to allow graduation of Apache Nuvem as a sub-project under Apache Tuscany. Nuvem Graduation Vote thread *http://s.apache.org/nuvem-graduation* *http://s.apache.org/nuvem-graduation-result* Tuscany Graduation Vote thread *http://s.apache.org/tuscany-accept-nuvem* *http://s.apache.org/tuscany-accept-nuvem-result* Please cast your votes: [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache Tuscany, because ... Vote passed with 6 binding +1 from : Jukka Zitting Bertrand Delacretaz Matt Franklin Raymond Feng Alan Cagrega Senaka Fernando Luciano Resende And 3 non-binding +1 from : Jean-Sebastien Delfino Sagara Gunathunga How do you get three votes from two people? Does one of them live in Chicago? And no -1 votes. Thanks -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT][VOTE] Graduate Nuvem as a sub-project under Apache Tuscany
On Thu, Nov 29, 2012 at 5:57 PM, Benson Margulies bimargul...@gmail.comwrote: On Thu, Nov 29, 2012 at 8:43 PM, Luciano Resende luckbr1...@gmail.com wrote: On Mon, Nov 19, 2012 at 9:41 PM, Luciano Resende luckbr1...@gmail.com wrote: Apache Nuvem will define an open application programming interface for common cloud application services, allowing applications to be easily ported across the most popular cloud platforms. It is currently composed of multiple cloud SCA components (Data, Queue, Chat), and supports multiple cloud platforms such as AWS, GAE, etc as well as standalone deployment. Nuvem was accepted for Incubation on June, 2010, and several of the active committers are already part of the Tuscany PMC. Nuvem was accepted for Incubation on June 2010, and is currently a small community, where the contributions are 100% done by volunteers in their own free time, which makes the level of activity low, compared to what is required for graduating it as a TLP. Having said that, Nuvem has a great synergy with Apache Tuscany, and after discussion between the two projects, we are seeking IPMC approval to allow graduation of Apache Nuvem as a sub-project under Apache Tuscany. Nuvem Graduation Vote thread *http://s.apache.org/nuvem-graduation* *http://s.apache.org/nuvem-graduation-result* Tuscany Graduation Vote thread *http://s.apache.org/tuscany-accept-nuvem* *http://s.apache.org/tuscany-accept-nuvem-result* Please cast your votes: [ ] +1 Graduate Nuvem as a sub-project under Apache Tuscany [ ] - 1 Nuvem is not ready to graduate as a sub-project under Apache Tuscany, because ... Vote passed with 6 binding +1 from : Jukka Zitting Bertrand Delacretaz Matt Franklin Raymond Feng Alan Cagrega Senaka Fernando Luciano Resende And 3 non-binding +1 from : Jean-Sebastien Delfino Sagara Gunathunga How do you get three votes from two people? Does one of them live in Chicago? Good catch, I actually didn't realize Senaka Fernando was part of IPMC until last minute, so the correct closing should be : Vote passed with 7 binding +1 from : Jukka Zitting Bertrand Delacretaz Matt Franklin Raymond Feng Alan Cagrega Senaka Fernando Luciano Resende And 2 non-binding +1 from : Jean-Sebastien Delfino Sagara Gunathunga -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: Sub-project graduation question
As per recent email, this is, formally, an act of the IPMC to certify that the IP is clear and the community good Apache citizens, followed by an act of the accepting project, and the board expects that the accepting project will report on the process promptly. I'm sure various will correct me if I've failed to explain. I think I should rewrite that section to reflect the change in the overall policy with regard to 'subprojects' in the Foundation, and to make it read more generally about a podling be absorbed into an existing TLP. On Thu, Nov 29, 2012 at 8:57 PM, Luciano Resende luckbr1...@gmail.com wrote: Just trying to clarify, based on [1] it seems that when a project is graduating into an existing TLP, once the IPMC vote is done, there is no need to seek Board approval and the hand-over and infrastructure tasks can start happening. Is that the correct understanding ? [1] http://incubator.apache.org/guides/graduation.html#subproject Thanks -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
On Thu, Nov 29, 2012 at 12:12 AM, Alexander Broekhuis a.broekh...@gmail.com wrote: I am fine with a change of the format. But at the moment we (Celix) still have a pending release. Seeing that many other project use different formats, I personally don't see this as a show stopper for our current release.. Can we somehow reach a consensus that for a next release the format will be different? (ie the format used by md5sum). I think that would be a fine choice. I'm fine with releasing it as is for now +1 (binding). That said -- I'd like to see the next release take into account the feedback that has been provided to the project so far. Nothing there is blocking, but not taking it into account would, in my opinion, make it more difficult to review and thus diminish the chances of getting enough eyeballs to look at it in time. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
+infra Ping! I would really like this annoyance to be resolved one way or the other. Could somebody more experienced with Apache web properties answer the question? Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? Thanks, Roman. On Sun, Nov 25, 2012 at 9:29 PM, Roman Shaposhnik r...@apache.org wrote: On Tue, Nov 20, 2012 at 3:50 PM, sebb seb...@gmail.com wrote: Personally, I find it difficult to verify the GPG generated checksums. Ditto. It's particularly awkward when the hash is wrapped over several lines. I ended up writing a Perl script to handle all the variations. If I'm not alone perhaps we should discourage the use of this format and modify the release FAQ page. +1 Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
Hence my idea to do away with the rule of thumb and stick to at least one responsible PMC member. What problem are we trying to avoid by having this activity/diversity boundary? Regards, Alan On Nov 29, 2012, at 4:52 PM, Benson Margulies wrote: Hard cases make bad law. The rough parameters of the recent 'small graduates' was that they had around 5 initial PMC members, and some detectable evidence that all of them were in the reasonably regular habit of contributing code, let alone voting for releases. If we insist on testing the absolute lower limit of viability, we're may bump into the absurd. On Thu, Nov 29, 2012 at 4:45 PM, Andy Seaborne a...@apache.org wrote: On 29/11/12 14:53, Bertrand Delacretaz wrote: On Thu, Nov 29, 2012 at 3:18 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Would you also add the three or more active PMC members requirement? What constitutes active?... IMO the bare minimum is being able to find three PMC members to vote on things when needed. Once a project gets below this limit it's in trouble and usually headed for the attic, but that's not the only possibility - see Resolution to reboot the Apache Xalan PMC at http://www.apache.org/foundation/records/minutes/2011/board_minutes_2011_07_20.txt for example. I think we need to be a bit careful about graduating a podling that is a minimum viable project. That's not say it shouldn't be done but if it's minimal, and looks ropey, then we're aren't doing us or them any favours if the project looks likely to get into problems quite soon. After all, graduation itself requires project resource. Andy -Bertrand - 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: Formats of SHA/MD5 checksums
On Nov 30, 2012, at 3:03 AM, Roman Shaposhnik r...@apache.org wrote: On Thu, Nov 29, 2012 at 12:12 AM, Alexander Broekhuis a.broekh...@gmail.com wrote: I am fine with a change of the format. But at the moment we (Celix) still have a pending release. Seeing that many other project use different formats, I personally don't see this as a show stopper for our current release.. Can we somehow reach a consensus that for a next release the format will be different? (ie the format used by md5sum). I think that would be a fine choice. I'm fine with releasing it as is for now +1 (binding). Thanks. That said -- I'd like to see the next release take into account the feedback that has been provided to the project so far. Nothing there is blocking, but not taking it into account would, in my opinion, make it more difficult to review and thus diminish the chances of getting enough eyeballs to look at it in time. +1 For a very first release attempt, I think the project did a good job, and it would definitely demonstrate getting the Apache way by taking all the suggestions and incorporating them in the next release. Yes, the incubator rules are not always written down well/correctly so releasing something will always trigger some amount of discussion. In that sense the incubator itself is also constantly improving. Greetings, Marcel - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Formats of SHA/MD5 checksums
Hi, I think that would be a fine choice. I'm fine with releasing it as is for now +1 (binding). Thanks! Could you post your vote to the formal release thread as well? That said -- I'd like to see the next release take into account the feedback that has been provided to the project so far. Nothing there is blocking, but not taking it into account would, in my opinion, make it more difficult to review and thus diminish the chances of getting enough eyeballs to look at it in time. Agreed. Most of the issues are already fixed in trunk. -- Met vriendelijke groet, Alexander Broekhuis
Re: Formats of SHA/MD5 checksums
Roman Shaposhnik wrote on Thu, Nov 29, 2012 at 18:05:15 -0800: +infra Ping! I would really like this annoyance to be resolved one way or the other. Could somebody more experienced with Apache web properties answer the question? Question: how do we go about discouraging it then? Do we need a vote Don't know. What's it ? to modify the content of: http://www.apache.org/dev/release-signing#md5 Ask your question in terms of release practices / policies, not in terms of web pages documenting them, please. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
