Re: New graduation jiras
On Thu, Nov 29, 2012 at 4:08 PM, Daniel Shahaf d...@daniel.shahaf.name wrote: ...Some caveats not documented there are: - The PMC chair is still responsible for using modify_unix_group... I've fixed the not documented bit by adding that info to http://www.apache.org/dev/infra-contact#requesting-graduation - hope that works for you. -Bertrand - 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 non-binding Andy Seaborne: 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
Re: Retirement decision making
On Fri, Nov 30, 2012 at 4:18 AM, Alan Cabrera l...@toolazydogs.com wrote: Hence my idea to do away with the rule of thumb and stick to at least one responsible PMC member How will that work? IIUC your idea, the resulting PMC cannot get 3 PMC votes so it cannot operate. I don't want to burden the board with more Xalan-like project saving exercices if it can be avoided, that case was driven by historic evolution of the project, graduating projects that are headed in that direction doesn't make sense to me. People come and go, so to be realistic I'd say you need at least five active PMC members at graduation time, so as to get three votes when needed, with some spares. Mentors staying on board can of course count in those five. -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 30 November 2012 00:52, Benson Margulies bimargul...@gmail.com 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. +1 (where reasonably regular habit of contributing code should be reasonably regular habit of contributing in some way - that is only being active in PMC duties would be fine, need not be active committer, as long as it is responsible activity (i.e. voting from an informed position) Ross 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 -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Re: Formats of SHA/MD5 checksums
Henk P. Penning wrote on Fri, Nov 30, 2012 at 10:08:33 +0100:
The reason given I ended up writing a Perl script doesn't
make sense ; .md5 files come in many forms but the algorithm
to verify is the same for all of them (there are no 'variations.') :
verify (checksum md5, .md5-file fff) :
-- tmp = lowercase cat fff
-- md5 = lowercase cat md5
-- squeeze non-hex ([^a-f0-9]) out of tmp (and md5)
md5(1) on FreeBSD produces the literal text MD5 as part of its output.
md5sum(1) on Linux prints the filename as part of its output. The
filename usually contains a hex digit (such as the a in tar or d
in hadoop).
Therefore just stripping non-hex-digits won't work with the standard md5
computation tools on those two platforms.
-- match md5 ~ tmp
HPP
_
Henk P. Penning, ICT-beta R Uithof WISK-412 _/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Budapestlaan 6, 3584CD Utrecht, NLF +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
On Fri, Nov 30, 2012 at 4:27 AM, Ross Gardler rgard...@opendirective.comwrote: On 30 November 2012 00:52, Benson Margulies bimargul...@gmail.com 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. +1 (where reasonably regular habit of contributing code should be reasonably regular habit of contributing in some way - that is only being active in PMC duties would be fine, need not be active committer, as long as it is responsible activity (i.e. voting from an informed position) Yes. Particularly for more mature code-bases, I'd put a lot of weight on whether people are around to answer user questions -- quite possibly, explaining the system helps attract new users more than tinkering with it does. --Ari -- Ari Rabkin asrab...@gmail.com Princeton Computer Science Department
Re: Retirement decision making
On Nov 30, 2012, at 12:56 AM, Bertrand Delacretaz wrote: On Fri, Nov 30, 2012 at 4:18 AM, Alan Cabrera l...@toolazydogs.com wrote: Hence my idea to do away with the rule of thumb and stick to at least one responsible PMC member How will that work? IIUC your idea, the resulting PMC cannot get 3 PMC votes so it cannot operate. I don't want to burden the board with more Xalan-like project saving exercices if it can be avoided, that case was driven by historic evolution of the project, graduating projects that are headed in that direction doesn't make sense to me. People come and go, so to be realistic I'd say you need at least five active PMC members at graduation time, so as to get three votes when needed, with some spares. Mentors staying on board can of course count in those five. Ok, I think I get it. Maybe that could be a requirement, if the mentors think that the podling is not diverse and vibrant yet, then they must stay on as active PMC members until such time that they believe that the TLP has achieved it; kind of a put your money where your mouth is thing. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Retirement decision making
On Fri, Nov 30, 2012 at 4:49 PM, Alan Cabrera l...@toolazydogs.com wrote: On Nov 30, 2012, at 12:56 AM, Bertrand Delacretaz wrote: ...I'd say you need at least five active PMC members at graduation time... ...Maybe that could be a requirement, if the mentors think that the podling is not diverse and vibrant yet, then they must stay on as active PMC members until such time that they believe that the TLP has achieved it; kind of a put your money where your mouth is thing Works for me. -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 Fri, Nov 30, 2012 at 10:56 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Fri, Nov 30, 2012 at 4:49 PM, Alan Cabrera l...@toolazydogs.com wrote: On Nov 30, 2012, at 12:56 AM, Bertrand Delacretaz wrote: ...I'd say you need at least five active PMC members at graduation time... ...Maybe that could be a requirement, if the mentors think that the podling is not diverse and vibrant yet, then they must stay on as active PMC members until such time that they believe that the TLP has achieved it; kind of a put your money where your mouth is thing It's arguable that one or two of my PMC memberships fall under this provision. I'd merely adjust that the word 'vibrant' means nothing specific to me, it's not a criteria I've ever thought about, and my willingness to become the long-term mentor of these folks outside the incubator is, in my mind, mostly a matter of compensating for small numbers and lack of ASF prior experience. Aside from being an extra release voter, I'm there to pay some attention and help with issues that come up when they (finally) absorb some new people. Works for me. -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
+1 on active PMC duties would be fine to ensure continuation of the project. regards, Eric On Fri, Nov 30, 2012 at 1:27 AM, Ross Gardler rgard...@opendirective.comwrote: On 30 November 2012 00:52, Benson Margulies bimargul...@gmail.com 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. +1 (where reasonably regular habit of contributing code should be reasonably regular habit of contributing in some way - that is only being active in PMC duties would be fine, need not be active committer, as long as it is responsible activity (i.e. voting from an informed position) Ross 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 -- Ross Gardler (@rgardler) Programme Leader (Open Development) OpenDirective http://opendirective.com
Invoke silent consensus rule for podling releases (was: [VOTE] Release Apache Bloodhound 0.3 (incubating))
It's quite frustrating that people find time to write hundreds of mails about points of procedure, but can't take time to review a release tarball from a podling. Activity on Bloodhound is picking up, and the project wants to release every couple weeks; yet the 0.2 vote thread sat in general@ for longer than that. It's worse for these mails to go unanswered than if the release had been vetoed. I hereby propose we extend the silent consensus rule to podling release votes. -- Brane On 26.11.2012 16:59, Joachim Dreimann wrote: Hi, I would like to request the beginning of the vote for the third release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/owksv6lbcs6zq7th The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/tags/0.3-incubating/ (r1412891) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/273 https://issues.apache.org/bloodhound/ticket/274 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.3 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe - 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
Jake Farrell wrote on Thu, Nov 29, 2012 at 22:02:16 -0500: That page is part of the Apache CMS and ASF members can edit that page by using the following http://www.apache.org/dev/cms.html#usage. Non ASF members can create a ticket within jira under the infra project and attach a patch for the changes they would like to make. Actually, if there's consensus, any ASF member can edit the page directly (but not publish the change). The repo and file you are looking for is https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/dev/release-signing.mdtext -Jake Roman Shaposhnik mailto:r...@apache.org November 29, 2012 9:05 PM +infra Ping! I would really like this annoyance to be resolved one way or the other. Could somebody more experienced with Apache web properties answer the question? Question: how do we go about discouraging it then? Do we need a vote to modify the content of: http://www.apache.org/dev/release-signing#md5 Or even more basic question -- where's the source for that webpage? Thanks, Roman. On Sun, Nov 25, 2012 at 9:29 PM, Roman Shaposhnikr...@apache.org wrote: On Tue, Nov 20, 2012 at 3:50 PM, sebbseb...@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: Formats of SHA/MD5 checksums
Daniel Shahaf wrote on Sat, Dec 01, 2012 at 07:25:54 +0200: Jake Farrell wrote on Thu, Nov 29, 2012 at 22:02:16 -0500: That page is part of the Apache CMS and ASF members can edit that page by using the following http://www.apache.org/dev/cms.html#usage. Non ASF members can create a ticket within jira under the infra project and attach a patch for the changes they would like to make. Actually, if there's consensus, any ASF member can edit the page directly (but not publish the change). s/member/committer/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release celix-0.0.1-incubating
On Thu, Nov 8, 2012 at 11:27 AM, Roman Shaposhnik r...@apache.org wrote: ||| Hi all, ||| ||| I would like to start the vote for the first release of Celix! ||| The last few months we have been working on this release. ||| Most of the time went into cleaning up sources, getting the required ||| files into the correct place etc. ||| ||| The source release file and signatures can be found on: ||| https://dist.apache.org/repos/dist/dev/incubator/celix/celix-0.0.1-incubating/ ||| ||| Before voting please review the section, ||| What are the ASF requirements on approving a release?, at ||| http://www.apache.org/dev/release.html#approving-a-release ||| ||| Since this is the first release made by Celix, please do an extensive check, ||| to verify all is correct. If all checks out and looks good, I will call the ||| vote on ||| the general list. ||| ||| Please vote to approve this release: ||| ||| [ ] +1 Approve the release ||| [ ] -1 Disapprove the release (please provide specific comments) -1 (binding) based on the RAT check: my cursory run of RAT (http://creadur.apache.org/rat/apache-rat/index.html) uncovered 61 Unknown Licenses. My concerns have been taken care of for this release. +1 (binding) 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
On Fri, Nov 30, 2012 at 1:08 AM, Henk P. Penning penn...@uu.nl wrote: I am +1 on suggesting (on that page) a 'normal' form for the content of a .md5 file. I'll take a crack at it now that I know where the source is ;-) I am definitedly -1 on removing the gpg line above, or suggesting that only one form of .md5 files is allowed. Why? The output it generates is not really similar to anything else and can be confusing. Is there a platform where GPG can be the only tool capable of generating MD5/SHA? 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
On Thu, Nov 29, 2012 at 11:49 PM, Mark Thomas ma...@apache.org wrote: Releases and new committers are pretty much the only time I'd expect to see votes in an Apache community. Understood. My question was specifically about the process used by ASF to manage its top level web pages. Now I know. Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Invoke silent consensus rule for podling releases (was: [VOTE] Release Apache Bloodhound 0.3 (incubating))
On Fri, Nov 30, 2012 at 9:08 PM, Branko Čibej br...@apache.org wrote: It's quite frustrating that people find time to write hundreds of mails about points of procedure, but can't take time to review a release tarball from a podling. Activity on Bloodhound is picking up, and the project wants to release every couple weeks; yet the 0.2 vote thread sat in general@ for longer than that. It's worse for these mails to go unanswered than if the release had been vetoed. I hereby propose we extend the silent consensus rule to podling release votes. -- Brane -1 for extending the silent consensus rule to podling release votes. BTW, have you got any IPMC binding votes from your mentors ? -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
Re: [VOTE] Release Apache Bloodhound 0.3 (incubating)
On Mon, Nov 26, 2012 at 7:59 AM, Joachim Dreimann joachim.dreim...@wandisco.com wrote: Hi, I would like to request the beginning of the vote for the third release of Apache Bloodhound in the incubator following the successful vote by the Bloodhound PPMC. The result of the vote is summarised here: http://markmail.org/thread/owksv6lbcs6zq7th The artefacts for the release including the source distribution and KEYS can be found here: https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ The release itself is created from: https://svn.apache.org/repos/asf/incubator/bloodhound/tags/0.3-incubating/ (r1412891) Issues identified to be fixed for the next release are listed here: https://issues.apache.org/bloodhound/ticket/273 https://issues.apache.org/bloodhound/ticket/274 The vote will be open for at least 72 hours. [ ] +1 Release this package as Apache Bloodhound 0.3 [ ] +0 Don't care [ ] -1 Do not release this package (please explain) Cheers, Joe -- Joe Dreimann UX Designer | WANdisco http://www.wandisco.com/ License and notice seems fine and couple of the issues found during the vote on the dev list dosen't seem blocking. +1 binding.
