[ANNOUNCE] Apache Marmotta 3.1.0-incubating released!
The Apache Marmotta team is pleased to announce the release of Apache Marmotta 3.1.0-incubating. http://marmotta.incubator.apache.org Apache Marmotta (incubator) is an Open Platform for Linked Data, that can be used, extended and deployed easily by organizations who want to publish Linked Data or build custom applications on Linked Data. It provides: * Read-Write Linked Data * RDF triple store with transactions, versioning and rule-base reasoning * SPARQL and LDPath query languages * Transparent Linked Data Caching * Integrated basic security mechanisms This release bring many improvements, among few new features. The full changelog is available at: http://s.apache.org/marmotta-3.1.0-changelog We invite you to join the development community. Further details at: http://marmotta.incubator.apache.org/development.html Sebastian, on behalf of the Marmotta development community, and with thanks to all the contributors. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Release Apache Marmotta 3.1.0-incubating
Dear all, thanks for your support! The 72 hours have now passed and we have 8 positive votes, of which 3 are binding and 5 are non-binding. We now have the required number of positive binding votes and will therefore proceed with the release. The remark by sebb has been added as an issue for the next release (MARMOTTA-327). Greetings, Sebastian 2013/10/2 Olivier Lamy ol...@apache.org +1 sources build fine. -- Olivier On Sep 30, 2013 8:17 PM, Sebastian Schaffert sschaff...@apache.org wrote: Dear all, After several months of work since the last incubating release (3.0.0-incubating) in April, we are now ready to release version 3.1.0-incubating. We fixed all the remaining issues that have been discussed in April (see thread [1]) plus many more technical issues. We have already held a vote that was open for more than 72 hours on the Apache Marmotta developer mailinglist [2]. The vote concluded [3] with 7 positive votes, of which 2 have been binding from IPMC members (Andy and Nandana) and the remaining 5 from the Apache Marmotta developers. I'd therefore like to ask the general incubator to check our release candidate. The release notes are available at the Jira Issue Tracker [4]. The vote form is included at the bottom of this mail. Greetings, Sebastian [1] http://apache.markmail.org/message/5tieelmeevi2j6xb [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr [3] http://apache.markmail.org/message/fvytzho2pnhasw2c [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12324026 === A candidate for the Marmotta 3.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/ The release candidate is based on the sources tagged with 3.1.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The release candidate consists of the following source distribution archives: - apache-marmotta-3.1.0- incubating-src.[zip|tar.gz] SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527 SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729 In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617 - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75 - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142 SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-092/ Please vote on releasing this package as Apache Marmotta 3.1.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 Marmotta PMC votes are cast. [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... === Release Notes - Marmotta - Version 3.1-incubating ** Sub-task * [MARMOTTA-216] - Implement JOIN improvements * [MARMOTTA-217] - Implement FILTER improvements * [MARMOTTA-218] - Integrate in marmotta-sparql ** Bug * [MARMOTTA-28] - Implement tests for core that take into account triple store changes * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently not working properly * [MARMOTTA-66] - Rework sesame-commons ResourceUtils * [MARMOTTA-143] - unable to import big files * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords * [MARMOTTA-155] - 3-char lang-tags are not accepted * [MARMOTTA-156] - Add Logback configuration to all tests to enable/disable debug logging * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains wrong comments * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in marmotta-webapp * [MARMOTTA-186] - LDPath parser fails on local names that contain '.' * [MARMOTTA-187] - ldpath extension for CM does not recognize local names with '.' or '-' * [MARMOTTA-191] - SPARQL graph results fails under some circunstances * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation * [MARMOTTA-204] - Update to Sesame 2.7.1 * [MARMOTTA-205] - Turtle-Exports do not contain any language tags * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE * [MARMOTTA
Re: [VOTE] Release Apache Marmotta 3.1.0-incubating
Hi sebb, the GIT hash of the release candidate is c66a4eb5743820c89fcf0446efab60a50965c6de . I will change the build process so it includes this hash in the vote e-mail. Greetings, Sebastian 2013/10/1 sebb seb...@gmail.com On 30 September 2013 11:17, Sebastian Schaffert sschaff...@apache.org wrote: Dear all, After several months of work since the last incubating release (3.0.0-incubating) in April, we are now ready to release version 3.1.0-incubating. We fixed all the remaining issues that have been discussed in April (see thread [1]) plus many more technical issues. We have already held a vote that was open for more than 72 hours on the Apache Marmotta developer mailinglist [2]. The vote concluded [3] with 7 positive votes, of which 2 have been binding from IPMC members (Andy and Nandana) and the remaining 5 from the Apache Marmotta developers. I'd therefore like to ask the general incubator to check our release candidate. The release notes are available at the Jira Issue Tracker [4]. The vote form is included at the bottom of this mail. Greetings, Sebastian [1] http://apache.markmail.org/message/5tieelmeevi2j6xb [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr [3] http://apache.markmail.org/message/fvytzho2pnhasw2c [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12324026 === A candidate for the Marmotta 3.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/ The release candidate is based on the sources tagged with 3.1.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git What is the hash of the tag please? Tags are not immutable, so should be included in the vote e-mail for the record. The release candidate consists of the following source distribution archives: - apache-marmotta-3.1.0- incubating-src.[zip|tar.gz] SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527 SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729 In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617 - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75 - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142 SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-092/ Please vote on releasing this package as Apache Marmotta 3.1.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 Marmotta PMC votes are cast. [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... === Release Notes - Marmotta - Version 3.1-incubating ** Sub-task * [MARMOTTA-216] - Implement JOIN improvements * [MARMOTTA-217] - Implement FILTER improvements * [MARMOTTA-218] - Integrate in marmotta-sparql ** Bug * [MARMOTTA-28] - Implement tests for core that take into account triple store changes * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently not working properly * [MARMOTTA-66] - Rework sesame-commons ResourceUtils * [MARMOTTA-143] - unable to import big files * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords * [MARMOTTA-155] - 3-char lang-tags are not accepted * [MARMOTTA-156] - Add Logback configuration to all tests to enable/disable debug logging * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains wrong comments * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in marmotta-webapp * [MARMOTTA-186] - LDPath parser fails on local names that contain '.' * [MARMOTTA-187] - ldpath extension for CM does not recognize local names with '.' or '-' * [MARMOTTA-191] - SPARQL graph results fails under some circunstances * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation * [MARMOTTA-204] - Update to Sesame 2.7.1 * [MARMOTTA-205] - Turtle-Exports do not contain any language tags * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE * [MARMOTTA-208] - Meta Put Webservice Deleting Tuples Incorrectly * [MARMOTTA-213
[VOTE] Release Apache Marmotta 3.1.0-incubating
Dear all, After several months of work since the last incubating release (3.0.0-incubating) in April, we are now ready to release version 3.1.0-incubating. We fixed all the remaining issues that have been discussed in April (see thread [1]) plus many more technical issues. We have already held a vote that was open for more than 72 hours on the Apache Marmotta developer mailinglist [2]. The vote concluded [3] with 7 positive votes, of which 2 have been binding from IPMC members (Andy and Nandana) and the remaining 5 from the Apache Marmotta developers. I'd therefore like to ask the general incubator to check our release candidate. The release notes are available at the Jira Issue Tracker [4]. The vote form is included at the bottom of this mail. Greetings, Sebastian [1] http://apache.markmail.org/message/5tieelmeevi2j6xb [2] http://apache.markmail.org/message/lk3hc3jutoaxp6dr [3] http://apache.markmail.org/message/fvytzho2pnhasw2c [4] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12324026 === A candidate for the Marmotta 3.1.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.1.0-incubating/ The release candidate is based on the sources tagged with 3.1.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The release candidate consists of the following source distribution archives: - apache-marmotta-3.1.0- incubating-src.[zip|tar.gz] SHA1 of ZIP: 763c39dc9d7eb1c7d8fad83742b08f44b6fa5527 SHA1 of TGZ: 0f7f3395f22aeeaa4a402f1b08048c84899d9729 In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.1.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: d7417a711a7f80eb29eb93ec75744a314fcf2edd SHA1 of TGZ: 4606fe743f607215dd4f3f39d8506852f529b617 - apache-marmotta-3.1.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 4f4db937e0064a4393039b6fb8277be166a971ab SHA1 of TGZ: 5d63f972df2306afec96aa1a8931c4d0dabb2f75 - apache-marmotta-3.1.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: e8e168a29e398cda9220a793958b825a906a3142 SHA1 of TGZ: 80d022d316e727b5f011069eec6dc9793b174838 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-092/ Please vote on releasing this package as Apache Marmotta 3.1.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 Marmotta PMC votes are cast. [ ] +1 Release this package as Apache Marmotta 3.1.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because... === Release Notes - Marmotta - Version 3.1-incubating ** Sub-task * [MARMOTTA-216] - Implement JOIN improvements * [MARMOTTA-217] - Implement FILTER improvements * [MARMOTTA-218] - Integrate in marmotta-sparql ** Bug * [MARMOTTA-28] - Implement tests for core that take into account triple store changes * [MARMOTTA-63] - Triplestore: garbage collector for nodes currently not working properly * [MARMOTTA-66] - Rework sesame-commons ResourceUtils * [MARMOTTA-143] - unable to import big files * [MARMOTTA-150] - BNodes are a dead end in the Linked Data Explorer * [MARMOTTA-154] - Youtube video provider doesn't fetch the keywords * [MARMOTTA-155] - 3-char lang-tags are not accepted * [MARMOTTA-156] - Add Logback configuration to all tests to enable/disable debug logging * [MARMOTTA-170] - file-store (meta) for ldcache-backend-file contains wrong comments * [MARMOTTA-171] - remove legacy subdirs from src/main/webapp in marmotta-webapp * [MARMOTTA-186] - LDPath parser fails on local names that contain '.' * [MARMOTTA-187] - ldpath extension for CM does not recognize local names with '.' or '-' * [MARMOTTA-191] - SPARQL graph results fails under some circunstances * [MARMOTTA-197] - ldpath is loosing brackets on re-serialisation * [MARMOTTA-204] - Update to Sesame 2.7.1 * [MARMOTTA-205] - Turtle-Exports do not contain any language tags * [MARMOTTA-206] - Strictly follow the standard formatting on the NOTICE * [MARMOTTA-208] - Meta Put Webservice Deleting Tuples Incorrectly * [MARMOTTA-213] - Address the issues on our NOTICE files * [MARMOTTA-214] - Memento timestamp does not use the right template * [MARMOTTA-221] - ldpath is loosing quotes for StringConstants on re-serialisation * [MARMOTTA-225] - Serializing ldpath field mappings with URIs as fieldname does not work correctly * [MARMOTTA-227] - Snorql uses different set of prefixes in the query evaluation than the showed at the user interface * [MARMOTTA-231] - Admin Interface: changing list values does not work * [MARMOTTA-232] - Reasoner does not add all justifications * [MARMOTTA-234] - Loading webjars resources doesn't work
[RESULT] [VOTE] Release Apache Marmotta 3.0.0-incubating (RC8)
Hi all, thanks for all the fruitful discussions around the legal issues we faced, and sorry that I could not really participate in the last week - too many conferences and meetings. I'd now like to summarize the vote (including the votes we had on the dev@marmotta... mailinglist): - 4 binding votes with +1 (mentors and ant elder) - 7 non-binding votes with +1 - 1 binding vote with not -1 from Marvin, so I count it as 0 ;-) Since the votes are all positive, we will now proceed with releasing RC8 as 3.0.0-incubating ;-) Greetings, Sebastian
Re: [VOTE] Release Apache Marmotta 3.0.0-incubating (RC8)
Hi sebb, there are different NOTICE files for the different distributions, because the binary distributions are rather framework applications that bundle a lot of third party libraries. - The NOTICE file for the source distribution contains the notices for the 3rd party source code and data files contained in the source distribution and excludes the dependencies. We had to include some 3rd party source code temporarily, because the libraries are not available via Maven or we needed to patch the code. The NOTICE files for the different binary distributions also contain the notices for the binary dependencies we are bundling, because users of course need to be aware of any licensing issues that might arise when using the binary distributions. Each binary distribution will therefore have a different NOTICE file. We had long discussions about the content of the NOTICE files. We followed as much as possible the guidelines on the ASF websites (which are sometimes a bit contradictory) and also the examples of several other well-known Apache projects that are of similar nature (e.g. Apache SOLR also has similar NOTICE files, likewise ODE and Geronimo). See e.g. the original discussion [1] and the refinements we did after the recommendations of our mentors [2]. [1] http://markmail.org/message/rrvpchj7jetn3yj7?q=list:org%2Eapache%2Emarmotta%2Edev+notice [2] http://markmail.org/message/tnxoyavqwykgrzhf?q=list:org%2Eapache%2Emarmotta%2Edev+notice In case you have suggestions for improvement, I am happy to accept any feedback you might have. Even after several weeks of digging through licenses and notices, I am still a software engineer and not a lawyer. In case of doubt, we therefore decided to stay on the safe side and rather add a notice than forget about it. I don't want any users with legal problems ... ;-) Greetings, Sebastian 2013/4/17 sebb seb...@gmail.com On 15 April 2013 14:40, Sebastian Schaffert sschaff...@apache.org wrote: Dear all, Apache Marmotta is an implementation of the Linked Data Platform and accompanying services. In the last months, we have migrated our old source code to the Apache infrastructure and tried to adapt the Apache policies in all parts of the project. In particular, we have fixed all remaining licensing issues and spent much time on developing the appropriate NOTICE and LICENSE files. We have executed 8 voting cycles on release candidates throughout the last weeks and we think we are now (finally) ready to really do the release. The vote on release candidate RC8 has been open for more than 72 hours on the developer mailinglist [1]. After closing the vote, we have the following voting results: - 2 binding votes (from the mentors Andy Seaborne and Nandana Mihindukulasooriya) - 6 non-binding votes (the remaining developers) I'd therefore like to ask now the general incubator to check our release candidate. Since this is our first release, please check thoroughly, I'd like to be sure we did not miss anything. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://markmail.org/message/uncutapltb3mopgy?q=list:org%2Eapache%2Emarmotta%2Edev [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12323952 Please find attached below the concrete details on the release and on the vote. Greetings, Sebastian === A candidate for the Marmotta 3.0.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.0.0-incubating/ The release candidate is based on the sources tagged with 3.0.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The NOTICE file in the source archive and Git tree looks rather big - are all of those really present in the source? Also the formatting of the header is non-standard. The release candidate consists of the following source distribution archives: - apache-marmotta-3.0.0-incubating-src.[zip|tar.gz] SHA1 of ZIP: ac0cc9aa641a37fea96adaf128e44b0d6a06cc8f SHA1 of TGZ: e176b0b7816e5c334a3d8dccb960cda0b64d4b4c In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.0.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: 4e5bf3e5c59e04bea3776d76c37990fa1efd6995 SHA1 of TGZ: a8736dd1700c7993762dea0446a23c2d314e03ec - apache-marmotta-3.0.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 3dab792c935bf0380c98fb2767ea75653df3b9b1 SHA1 of TGZ: 237040387801aa6538fd07e3c75265b06e3d4ce3 - apache-marmotta-3.0.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: 7784ee71b665782f1011a8d1333524c825b90c6d SHA1 of TGZ: 217e17709e6e84ffe755841ac69f850538e867f7 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-093/ Please vote
Re: [VOTE] Release Apache Marmotta 3.0.0-incubating (RC8)
Hi sebb, there are different NOTICE files for the different distributions, because the binary distributions are rather framework applications that bundle a lot of third party libraries. - The NOTICE file for the source distribution contains the notices for the 3rd party source code and data files contained in the source distribution and excludes the dependencies. We had to include some 3rd party source code temporarily, because the libraries are not available via Maven or we needed to patch the code. The NOTICE files for the different binary distributions also contain the notices for the binary dependencies we are bundling, because users of course need to be aware of any licensing issues that might arise when using the binary distributions. Each binary distribution will therefore have a different NOTICE file. We had long discussions about the content of the NOTICE files. We followed as much as possible the guidelines on the ASF websites (which are sometimes a bit contradictory) and also the examples of several other well-known Apache projects that are of similar nature (e.g. Apache SOLR also has similar NOTICE files, likewise ODE and Geronimo). See e.g. the original discussion [1] and the refinements we did after the recommendations of our mentors [2]. [1] http://markmail.org/message/rrvpchj7jetn3yj7?q=list:org%2Eapache%2Emarmotta%2Edev+notice [2] http://markmail.org/message/tnxoyavqwykgrzhf?q=list:org%2Eapache%2Emarmotta%2Edev+notice In case you have suggestions for improvement, I am happy to accept any feedback you might have. Even after several weeks of digging through licenses and notices, I am still a software engineer and not a lawyer. In case of doubt, we therefore decided to stay on the safe side and rather add a notice than forget about it. I don't want any users with legal problems ... ;-) Greetings, Sebastian 2013/4/17 sebb seb...@gmail.com On 15 April 2013 14:40, Sebastian Schaffert sschaff...@apache.org wrote: Dear all, Apache Marmotta is an implementation of the Linked Data Platform and accompanying services. In the last months, we have migrated our old source code to the Apache infrastructure and tried to adapt the Apache policies in all parts of the project. In particular, we have fixed all remaining licensing issues and spent much time on developing the appropriate NOTICE and LICENSE files. We have executed 8 voting cycles on release candidates throughout the last weeks and we think we are now (finally) ready to really do the release. The vote on release candidate RC8 has been open for more than 72 hours on the developer mailinglist [1]. After closing the vote, we have the following voting results: - 2 binding votes (from the mentors Andy Seaborne and Nandana Mihindukulasooriya) - 6 non-binding votes (the remaining developers) I'd therefore like to ask now the general incubator to check our release candidate. Since this is our first release, please check thoroughly, I'd like to be sure we did not miss anything. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://markmail.org/message/uncutapltb3mopgy?q=list:org%2Eapache%2Emarmotta%2Edev [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12323952 Please find attached below the concrete details on the release and on the vote. Greetings, Sebastian === A candidate for the Marmotta 3.0.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.0.0-incubating/ The release candidate is based on the sources tagged with 3.0.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The NOTICE file in the source archive and Git tree looks rather big - are all of those really present in the source? Also the formatting of the header is non-standard. The release candidate consists of the following source distribution archives: - apache-marmotta-3.0.0-incubating-src.[zip|tar.gz] SHA1 of ZIP: ac0cc9aa641a37fea96adaf128e44b0d6a06cc8f SHA1 of TGZ: e176b0b7816e5c334a3d8dccb960cda0b64d4b4c In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.0.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: 4e5bf3e5c59e04bea3776d76c37990fa1efd6995 SHA1 of TGZ: a8736dd1700c7993762dea0446a23c2d314e03ec - apache-marmotta-3.0.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 3dab792c935bf0380c98fb2767ea75653df3b9b1 SHA1 of TGZ: 237040387801aa6538fd07e3c75265b06e3d4ce3 - apache-marmotta-3.0.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: 7784ee71b665782f1011a8d1333524c825b90c6d SHA1 of TGZ: 217e17709e6e84ffe755841ac69f850538e867f7 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-093/ Please vote
Re: [VOTE] Release Apache Marmotta 3.0.0-incubating (RC8)
Hi Sebb, 2013/4/17 sebb seb...@gmail.com We had long discussions about the content of the NOTICE files. We followed as much as possible the guidelines on the ASF websites (which are sometimes a bit contradictory) Please can you advise where the contradictions are so they can be sorted out? Yes, sure. There are currently the following documents (at least the ones I am aware of) that are somehow related to LICENSE and NOTICE: 1. http://www.apache.org/dev/licensing-howto.html 2. http://www.apache.org/legal/3party.html 3. http://www.apache.org/legal/src-headers.html 4. http://incubator.apache.org/guides/releasemanagement.html#best-practice-license While similar in the most important issues, all four documents vary in some of the details. For example: - The section NOTICE file in [3] says that The NOTICE file may also include copyright notices moved from source files submitted to the ASF. The 3rd party Javascript files we include are submitted to the ASF, but they are often under MIT license and therefore category A in [2]. If I read the document correctly, category A only requires to include notices if a NOTICE file is contained in the product. According to [1], MIT and New BSD even can have a reduced entry in LICENSE. [4] says, however, that All the licenses on all the files to be included within a package should be included in the LICENSE document. - for dependencies of category B, [2] specifies that Although the source must not be included in Apache products, the NOTICE file, which is required to be included in each ASF distribution, must point to the source form of the included binary (more on that in the forthcoming Receiving and Releasing Contributions document)., a fact that is not mentioned in any of the other documents. - The labelling requirement source access in [2] requires that the NOTICE file contains pointers to the location of the source code for any 3rd party library that is bundled in a binary distribution (not only category B). [1] on the other hand does not mention this requirement and says that everything that is not legally necessary does not belong into NOTICE. - [1] says that NOTICE must only include notices not satisfied by licensing information embedded within the dependency subtree. [2] says Users of Apache products must be provided with all licensing terms applicable to any part of the product and must be given prominent notice as fourth guiding principle (emphasis on *prominent*, which for me means not somewhere in the dependency subtree) Maybe contradictory was too strong a word. But all the four documents are incomplete in the guidance they provide. What I found very helpful, though, are the 4 guiding principles mentioned in [2]. Also very helpful was looking at how other projects are doing it, in particular we looked at SOLR and Geronimo, as they are also web frameworks bundling many different libraries. For example, SOLR has a very extensive NOTICE file: http://svn.apache.org/repos/asf/lucene/dev/trunk/solr/NOTICE.txt For future podlings, what would be very helpful is to improve the document [1] as a single point of guidance that collects all the information from the other documents (if it is correct). In particular, best practices for different types of projects would also help a lot, especially to people who are not legal experts (like me). Because apparently, many of the top level projects (like SOLR) are not really best practices. What would also help is to give more understanding what a notice actually means. For example, if I understand correctly, the Apache License, when used by 3rd party libraries, always requires notice. How can I see whether other licenses also require this notice? As an example, consider the MIT license. It explicitly says The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.. Does this mean that a copyright notice must go into the NOTICE file (under guiding principle number 4 I would read it like yes)? If so, then there is a contradiction with [1]. and also the examples of several other well-known Apache projects that are of similar nature (e.g. Apache SOLR also has similar NOTICE files, likewise ODE and Geronimo). See e.g. the original discussion [1] and the refinements we did after the recommendations of our mentors [2]. From Marvin's recent post in another VOTE thread: The ASF now has documentation which describes a formulaic approach to creating LICENSE and NOTICE. If you follow the recipe, you should be OK. http://www.apache.org/dev/licensing-howto.html We followed this document very closely (I can almost recite it in my sleep). If the recipe was complete, yes :-) But recipes typically do not contain sentences like NOTICE is reserved for a certain subset of legally required notifications. :-P Thanks for checking, BTW. From your point of view, is the NOTICE and LICENSE we have for Marmotta too extensive? Where
[VOTE] Release Apache Marmotta 3.0.0-incubating (RC8)
Dear all, Apache Marmotta is an implementation of the Linked Data Platform and accompanying services. In the last months, we have migrated our old source code to the Apache infrastructure and tried to adapt the Apache policies in all parts of the project. In particular, we have fixed all remaining licensing issues and spent much time on developing the appropriate NOTICE and LICENSE files. We have executed 8 voting cycles on release candidates throughout the last weeks and we think we are now (finally) ready to really do the release. The vote on release candidate RC8 has been open for more than 72 hours on the developer mailinglist [1]. After closing the vote, we have the following voting results: - 2 binding votes (from the mentors Andy Seaborne and Nandana Mihindukulasooriya) - 6 non-binding votes (the remaining developers) I'd therefore like to ask now the general incubator to check our release candidate. Since this is our first release, please check thoroughly, I'd like to be sure we did not miss anything. The release notes (fixed issues) are available at the Jira Issue Tracker [2]. [1] http://markmail.org/message/uncutapltb3mopgy?q=list:org%2Eapache%2Emarmotta%2Edev [2] https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314321version=12323952 Please find attached below the concrete details on the release and on the vote. Greetings, Sebastian === A candidate for the Marmotta 3.0.0-incubating release is available at: https://dist.apache.org/repos/dist/dev/incubator/marmotta/3.0.0-incubating/ The release candidate is based on the sources tagged with 3.0.0-incubating in: https://git-wip-us.apache.org/repos/asf/incubator-marmotta.git The release candidate consists of the following source distribution archives: - apache-marmotta-3.0.0-incubating-src.[zip|tar.gz] SHA1 of ZIP: ac0cc9aa641a37fea96adaf128e44b0d6a06cc8f SHA1 of TGZ: e176b0b7816e5c334a3d8dccb960cda0b64d4b4c In addition, the following supplementary binary distributions are provided: - apache-marmotta-3.0.0-incubating-installer.[zip|tar.gz] SHA1 of ZIP: 4e5bf3e5c59e04bea3776d76c37990fa1efd6995 SHA1 of TGZ: a8736dd1700c7993762dea0446a23c2d314e03ec - apache-marmotta-3.0.0-incubating-ldpath.[zip|tar.gz] SHA1 of ZIP: 3dab792c935bf0380c98fb2767ea75653df3b9b1 SHA1 of TGZ: 237040387801aa6538fd07e3c75265b06e3d4ce3 - apache-marmotta-3.0.0-incubating-webapp.[zip|tar.gz] SHA1 of ZIP: 7784ee71b665782f1011a8d1333524c825b90c6d SHA1 of TGZ: 217e17709e6e84ffe755841ac69f850538e867f7 A staged Maven repository is available for review at: https://repository.apache.org/content/repositories/orgapachemarmotta-093/ Please vote on releasing this package as Apache Marmotta 3.0.0-incubating. The vote is open for the next 72 hours and passes if a majority of at least three +1 Marmotta PMC votes are cast. [ ] +1 Release this package as Apache Marmotta 3.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with the release [ ] -1 Do not release this package because...
Re: [PROPOSAL] Apache Linda
Hi Daniel, Am 19.11.2012 um 06:53 schrieb dsh: A few comments in regards to the proposal draft and linked data specifically: * maybe consider calling out that you are striving towards implementing the Linked Data Platform 1.0 W3C draft (at least that's how I understand the proposal) Yes, this is true. The reason why we are not calling this out too loudly is that the recommendation is still emerging and that it is by far not the only recommendation that needs to be taken into account for a Linked Data Platform. There is also RDF, SPARQL 1.1 (including the protocol), WebID and WebACL (still working groups, no recommendation so far) and some others that might be interesting in enterprise settings (like versioning and the memento protocol). But in the proposal we should maybe add pointers to all these recommendations. * will Linda (or whatever name you'll choose) cover data governance aspects too. right now to me it looks like the assumption is that data is already normalized where enterprise data usually isn't in real life. That's why you have ETL processes and data governance models. That actually contradicts one of Berners-Lee statements in the Ted talk. I wouldn't assume that enterprises won't open their data because they want to keep it secret I would rather assume that there's a huge leap step towards transforming legacy data into usable (whatever that means in practice) linked data. Maybe how to transform legacy data into open linked data is even research subject. So my question is: will Linda be focusing on such data governance aspects too (it looks like LMF covers that aspect at least a bit in a wiki article)? To some extent yes. At the very least we will provide documentation how to transform legacy data into linked data. One tool we are currently using is a modified version of Google Refine (see the screencast on the current LMF homepage). But we will not cover such scenarios in-depth, I would see this out of the scope of the project, and there are others doing this already, e.g. D3RQ, Pubby, etc. Linked Data needs not necessarily also be Open Data, the same technology can also be used inside enterprises for information integration. In enterprises, the platform will have to fulfill many more requirements, especially regarding access control. Greetings, Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Linda
Hi Paolo, You are right, the discussion on the list shows we should explain a bit more about the general idea. We will add a paragraph to the proposal and some more links to background material. ;-) Am 19.11.2012 um 00:45 schrieb Paolo Castagna: On 19/11/12 01:01, Benson Margulies wrote: Ted, I did read the whole thing, and I'd like to join you in drawing a curtain in front of the man. The proposers of this project didn't create the problem of the term 'linked data', and they can't fix it. As you suggest, all they can do is pick a TLP name that is neutral to positive in relation to it. Since they've already signed up for finding some other girl, boy, or dinosaur to take to the dance here, I think we can leave the question of the badness of the phrase 'linked data' behind. A small improvement to the proposal would be to add a definition to 'linked data', so that others can read the rest of the proposal knowing what 'linked data' means in that context. The proposal should also refers the reader to: - http://en.wikipedia.org/wiki/Linked_data - http://www.w3.org/DesignIssues/LinkedData - http://www.w3.org/wiki/LinkedData - http://linkeddata.org/ As you said, nothing can be done in relation to 'linked data'. Paolo --benson - 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 Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Linda
and which is used by other projects in roughly the same domain is problematic. I disagree. Well, you can't disagree that I was confused by your proposal. I don't think that you can disagree that a big part of the cause of the confusion was the use of the generic phrase linked data in a highly specific way. Take other terms that have succeeded easily: hyperlink web log = blog web page atomic clock Each of these is essentially a phrase, but one that did not have a prior common usage. The 4 principles are very clear and simple: 1. Use URIs as names for things 2. Use HTTP URIs so that people can look up those names. 3. When someone looks up a URI, provide useful information, using the standards (RDF*, SPARQL) 4. Include links to other URIs. so that they can discover more things. We could debate indefinitely on the using the standards ... part, but should we do it here? No. You can define things any way you like. That isn't the point. What's isn't clear to you from the four principles above? The clarity of the four principles isn't the point. The clarity of the phrase linked data without somewhat unusual foreknowledge and without the definition is the point. A phrase that has to have its definition schlepped around with the phrase is hardly very useful. You already know what a URI, HTTP URIs, links are. Isn't it? :-) Yes. But you are way out in the weeds here arguing a point that doesn't need to be made. Now, I could have sympathy with you if you point your finger at RDF and SPARQL, but, Ahh... but each of these has names that are clearly not something else. Thus, if I don't know about triples and such, I still can see that I *don't* know what these phrases are. With linked data, I don't have a clue that I don't know what you are talking about. ... and clear... and if you want you can always refer to the W3C Recommendations (those are your primary sources of information in this case). but how would a person know that is where these terms are defined? Especially when you are giving them a huge pointer toward blackboard systems with the name Linda? ...You should be aware, however, that with these defects, it seems very unlikely to me that Apache would be able to help with trademark and name conflict issues. That may not seem like a big deal now, but if your project really does get going and then somebody tries to take over your community with a nearly identically named product, it will definitely feel like a big deal. Take a look at what happens with Open Office all the time. Regarding the name, I have no better suggestion than dropping the 'n'? Linda -- Lida (but I have not done much research to see if that has problems or not). How about following the tradition established by the contraction of web log into blog? That would give web linked data = Blinda It is still a female name if you need the gender stereotyping of Linda. It seems to have non-English meanings, but certainly has no connotations in English. It also seems to have no prior technical usage. Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Marmotta (was: Apache Linda)
Hi all, we have had a brainstorming round and came up with the suggestion Apache Marmotta as a new name. We looked a bit and the name seems not to be taken yet, so there would probably no legal issues with the name. Why Marmotta? It is Italian for marmot, one of the predominant animals in the mountains around us. It also is very social (i.e. links) and digs deep tunnels (looks for data). It is more or less easy to pronounce (only contains a and o as vowels and no unpronouncible combinations). The animal itself has typically a very positive association (cute) and would also provide easy branding with images and logos. What do you think? Greetings, Sebastian Am 19.11.2012 um 09:01 schrieb Sebastian Schaffert: Hi Ted, I read all your mail ( :-) ) and I am sorry that this evolved into such a discussion. For me, Linked Data is as specific as Web, Stack or Heap, and I would claim it is like this for at least the rest of the Web community and possibly the database community as well. But regardless what we think about it, fact is the label has been established and the time to criticise it would have been 7 years ago. With other people, I'd like to say. I can fully understand your position though: coming from a logics background in CS, I had similar concerns with the name Semantic Web, because nothing is really Semantic about it. From a logics point of view, it is all about symbols, the semantics would require an interpretation. I realised that opposing the term doesn't really help, though, since the world around me still continued using it. ;-) So, let's go forward with the constructive part of the discussion. We will sit together in about 1 hour and I am sure we come up with a solution (one way or the other - if it remains Linda we will have good arguments for it). And thanks again for rising the legal issue - something we will take into the discussion. Greetings, Sebastian Am 18.11.2012 um 21:55 schrieb Ted Dunning: On Sun, Nov 18, 2012 at 1:45 AM, Paolo Castagna castagna.li...@gmail.comwrote: On 17/11/12 22:49, Ted Dunning wrote: Frankly, the phrase linked data is also so generic as to be essentially meaningless outside your community. There are many, many uses of this phrase in computer science that mean something completely different from what you guys seem to mean. Where else is the phrase linked data used with a different meaning? The problem is that the phrase is generic and can arise in general speech. Links and pointers are ubiquitous in computer parlance. Nothing in the phrase linked data constrains the meaning to *that* kind of link for *that* kind of data other than the usage in a relatively small community. What 'those guys' seem to mean is well described in the Linked Data Wikipedia page: http://en.wikipedia.org/wiki/**Linked_datahttp://en.wikipedia.org/wiki/Linked_data Please, notice there isn't a disambiguation page. :-) That is because the phrase is only used as a proper noun for one thing. But it is used commonly as a descriptive phrase. The comparable phrase red flowers doesn't need a disambiguation link in wikipedia either because the meaning is apparent as a compositional construct. The above wiki page seems pretty short and clear to me. But the phrase itself is so vanilla that searching on the web to find the meaning (to a native speaker, anyway) seems kind of pointless. My question was not what does linked data mean? because it seemed like I could come up with ten meanings for the term. The question was which of the many possible meanings are these people talking about?. Note that a web search wouldn't answer that question because the existence of a common usage does not imply that any given community is following that common usage pattern. Is there anything in your opinion which isn't clear and should be better explained? I think that you are missing the point. The problem is that the phrase itself doesn't have any signal that there is any nominative usage going on. If I were speaking German and used the English phrase, there would be a very strong signal, but we aren't doing that. As such, I think that most mentions of linked data should include some such signal. In a proposal aimed at people outside your community, in particular, you need something along the lines the phrase linked data is used here idiosyncratically to refer to If you assume that the reader knows what kind of link you mean between what kind of data, then the documents you produce will tend to be impenetrable. Assumptions like this are common within insular communities and commonly lead to misunderstandings like this. The phrase linked data is composed by two words and the common definition of 'linked' (in particular if referred to the Web) and 'data' applies here unchanged. If you think at the Web as is big 'library' of linked
Re: [PROPOSAL] Apache Linda
Dear all, first of all, thanks for the feedback so far... Am 17.11.2012 um 20:08 schrieb Andy Seaborne: You're right changing the name can be done later but the name tends to get embedded both in the system (e.g. URLs, JIRA project) and more importantly in people knowing about the community. Renaming for the community is hard and risky - I would say it is easier to sort it out as part of project initialization if you believe the name change is likely. I did a quick search and found 2 lindas: Linda Spaces (the blackboard system that, I guess, is triggering the comments here) and TCP Linda, a parallel execution environment (which may well be related to the blackboard linda). TCP Linda == http://www.gaussian.com/g_prod/linda.htm Linda spaces leads to JavaSpaces so is a known name in the Java world at least. There is a SourceForge project linda (but looks dormant) Andy I agree that Linda is a very generic name and as such there are already several projects out there with this name. On the other hand, we chose Linda as an acronym for Linked Data in order to increase recognizability especially in the domain we are targeting. For our community, we think it would be quite easy to identify Apache Linda with the Linked Data Platform and not with a blackboard system or a methodology for parallel execution. A more artificial name would probably have a harder time establishing a brand (but of course the project is good enough to manage ;-) ). In case the Incubator PMC still recommends to rename the project, I agree we should do it BEFORE starting up the project. We will discuss options for renaming on Monday (European Time) and come up with suggestions. Greetings, Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Apache Linda
Dear Ted, even though I agree that the term Linked Data is very generic, this is out of my influence, and it describes quite well what the topic is about. The term Linked Data has actually been proposed by Tim Berners-Lee: http://www.w3.org/DesignIssues/LinkedData.html and is used in the various standardisation efforts (like the W3C Linked Data Platform recommendation mentioned in the proposal). There is also a nice presentation from 2009 at TED: http://www.ted.com/talks/tim_berners_lee_on_the_next_web.html Linked Data is also already used by major enterprises like: - BBC: http://www.w3.org/2001/sw/sweo/public/UseCases/BBC/ - Volkswagen: http://semanticweb.com/volkswagen-das-auto-company-is-das-semantic-web-company_b23233 - German National Library: http://www.dnb.de/EN/Service/DigitaleDienste/LinkedData/linkeddata_node.html So my fear that 'nobody is likely to understand the phrase Linked Data' is very low for the future. If there have been other uses of the phrase in Computer Science before they are now marginalized (if you can trust a Google search for Linked Data). That said, we take your concern serious (especially the legal issue) and will discuss the issue on Monday. I am also grateful for the proposals that have already been done on the list. Greetings, Sebastian Am 17.11.2012 um 23:49 schrieb Ted Dunning: Frankly, the phrase linked data is also so generic as to be essentially meaningless outside your community. There are many, many uses of this phrase in computer science that mean something completely different from what you guys seem to mean. It took me quite a bit of reading to figure out what you were talking about. At the very least, you need to look at your supporting materials with a naive eye so that you can avoid the confusion that your name and terminology are likely to cause. Having a project name that memorializes a phrase that nobody is likely to understand without (lots of) supporting material and which is used by other projects in roughly the same domain is problematic. My feeling is that I would be -0 on the name meaning that I think that it isn't good, but I wouldn't stand in the way by vetoing it. You guys seem pretty attached to your terminology regardless of the merits and it doesn't seem a big enough issue to be worth causing friction over it. You should be aware, however, that with these defects, it seems very unlikely to me that Apache would be able to help with trademark and name conflict issues. That may not seem like a big deal now, but if your project really does get going and then somebody tries to take over your community with a nearly identically named product, it will definitely feel like a big deal. Take a look at what happens with Open Office all the time. On Sat, Nov 17, 2012 at 2:12 PM, Sebastian Schaffert sebastian.schaff...@salzburgresearch.at wrote: I agree that Linda is a very generic name and as such there are already several projects out there with this name. On the other hand, we chose Linda as an acronym for Linked Data in order to increase recognizability especially in the domain we are targeting. For our community, we think it would be quite easy to identify Apache Linda with the Linked Data Platform and not with a blackboard system or a methodology for parallel execution. A more artificial name would probably have a harder time establishing a brand (but of course the project is good enough to manage ;-) ). In case the Incubator PMC still recommends to rename the project, I agree we should do it BEFORE starting up the project. We will discuss options for renaming on Monday (European Time) and come up with suggestions. Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[PROPOSAL] Apache Linda
Dear all, we would like to propose a new project called Apache Linda as a Linked Data Platform implementation to the incubator. Andy Seaborne was so kind as to volunteer as a champion for the project. The proposal is available at http://wiki.apache.org/incubator/LindaProposal The goal of Apache Linda 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. Linda 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. Linda 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). We are looking forward to your feedback and suggestions on how to improve the proposal and idea! Sergio, Thomas, Jakob and Sebastian -- | Dr. Sebastian Schaffert sebastian.schaff...@salzburgresearch.at | Salzburg Research Forschungsgesellschaft http://www.salzburgresearch.at | Head of Knowledge and Media Technologies Group +43 662 2288 423 | Jakob-Haringer Strasse 5/II | A-5020 Salzburg signature.asc Description: Message signed with OpenPGP using GPGMail
