Re: Correct process for signing keys?
Hi Andrew, here are some basic docs: http://www.apache.org/dev/release-signing.html http://www.apache.org/dev/openpgp.html#update I could not find information on your specific question. At log4php we were curious recently about the same and decided to go with this: http://www.apache.org/dist/logging/log4php/KEYS But we made sure it would match this: https://people.apache.org/keys/group/logging-pmc.asc Basically my understanding is the one from people would be fine alone. There is some danger people would take the KEYS file from a mirror which is to my knowledge not possible from people. My 2 cents- hopefully somebody with more knowledge on that matter (infra) can add a note. Cheers On Thu, May 30, 2013 at 10:44 PM, Andrew Phillips andr...@apache.orgwrote: Hi all Apologies in advance if this is not the correct audience for this question: what is the correct process now for publishing signing keys for releases? jclouds currently has a KEYS file [1]; there is another (different) file containing keys in the groups list [2] on people.apache, and most individual committers *also* have their personal keys automatically retrieved via people.apache (e.g. [3]). In an email thread on this topic Brian (McCallister) indicated that: Upon investigation, if release signing keys are published via https://people.apache.org/**keys/ https://people.apache.org/keys/ then we don't need a KEYS file and should remove it. -Brian In that case, I'd be grateful if you could give some guidance on what the validity of the other approaches (KEYS file published somewhere or group KEYS file) is, and what we should do with those files, if anything. Thanks! Andrew [1] http://www.apache.org/dist/**incubator/jclouds/KEYShttp://www.apache.org/dist/incubator/jclouds/KEYS [2] https://people.apache.org/**keys/group/jclouds.aschttps://people.apache.org/keys/group/jclouds.asc [3] https://people.apache.org/**keys/committer/andrewp.aschttps://people.apache.org/keys/committer/andrewp.asc --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de
[jira] [Updated] (PODLINGNAMESEARCH-33) Establish whether Apache JSPWiki is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Juan Pablo Santos Rodríguez updated PODLINGNAMESEARCH-33: - Description: We have to do some investigations to ensure that Apache JSPWiki is a suitable name for a TLP. Here are some resources related to this issue: http://incubator.apache.org/guides/names.html http://www.apache.org/foundation/marks/ Apache JSPWiki is a Java-based WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A similar search was perfomed 4 years ago, so this issue is mostly an update on that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547 was: We have to do some investigations to ensure that Apache JSPWiki is a suitable name for a TLP. Here are some resources related to this issue: http://incubator.apache.org/guides/names.html http://www.apache.org/foundation/marks/ A similar search was perfomed 4 years ago, so this issue is mostly an update on that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547 added project description to the JIRA issue (as done in other PODLINGNAMESEARCH issues) Also, it has been a few days without any other comments, are we ok with Apache JSPWiki? What are the next steps? Establish whether Apache JSPWiki is a suitable name -- Key: PODLINGNAMESEARCH-33 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-33 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Juan Pablo Santos Rodríguez We have to do some investigations to ensure that Apache JSPWiki is a suitable name for a TLP. Here are some resources related to this issue: http://incubator.apache.org/guides/names.html http://www.apache.org/foundation/marks/ Apache JSPWiki is a Java-based WikiWiki engine, feature-rich and built around standard J2EE components (Java, servlets, JSP). A similar search was perfomed 4 years ago, so this issue is mostly an update on that JIRA. cfr with: https://issues.apache.org/jira/browse/JSPWIKI-547 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
RE: Correct process for signing keys?
@Christian The other advantage of the people list is that it is automatically updated from the federation of PGP key servers so it reflects the latest web of trust and also, I presume, any revocation. In some cases, PMC wide is a bit too generous though. I think the release manager's Apache ID is better, using https://people.apache.org/keys/id.asc. This is probably more confidence-inspiring that the web of trust itself for those who do not participate in Apache projects and don't know who those folks who've counter-signed the certificate happen to be. In that case, the lock to an ASF committer is valuable. (It is unfortunate that committers and especially release managers are often not visible by their id@apache.org, thus providing even more confidence in the connection for observers.) - Dennis PS: I notice I just did the thing I'm complaining about. But I don't think orcmid@ a.o is subscribed to this list [;). -Original Message- From: Christian Grobmeier [mailto:grobme...@gmail.com] Sent: Sunday, June 2, 2013 01:24 AM To: general@incubator.apache.org Subject: Re: Correct process for signing keys? Hi Andrew, here are some basic docs: http://www.apache.org/dev/release-signing.html http://www.apache.org/dev/openpgp.html#update I could not find information on your specific question. At log4php we were curious recently about the same and decided to go with this: http://www.apache.org/dist/logging/log4php/KEYS But we made sure it would match this: https://people.apache.org/keys/group/logging-pmc.asc Basically my understanding is the one from people would be fine alone. There is some danger people would take the KEYS file from a mirror which is to my knowledge not possible from people. My 2 cents- hopefully somebody with more knowledge on that matter (infra) can add a note. Cheers On Thu, May 30, 2013 at 10:44 PM, Andrew Phillips andr...@apache.orgwrote: Hi all Apologies in advance if this is not the correct audience for this question: what is the correct process now for publishing signing keys for releases? jclouds currently has a KEYS file [1]; there is another (different) file containing keys in the groups list [2] on people.apache, and most individual committers *also* have their personal keys automatically retrieved via people.apache (e.g. [3]). In an email thread on this topic Brian (McCallister) indicated that: Upon investigation, if release signing keys are published via https://people.apache.org/**keys/ https://people.apache.org/keys/ then we don't need a KEYS file and should remove it. -Brian In that case, I'd be grateful if you could give some guidance on what the validity of the other approaches (KEYS file published somewhere or group KEYS file) is, and what we should do with those files, if anything. Thanks! Andrew [1] http://www.apache.org/dist/**incubator/jclouds/KEYShttp://www.apache.org/dist/incubator/jclouds/KEYS [2] https://people.apache.org/**keys/group/jclouds.aschttps://people.apache.org/keys/group/jclouds.asc [3] https://people.apache.org/**keys/committer/andrewp.aschttps://people.apache.org/keys/committer/andrewp.asc --**--**- To unsubscribe, e-mail: general-unsubscribe@incubator.**apache.orggeneral-unsubscr...@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.**orggeneral-h...@incubator.apache.org -- http://www.grobmeier.de https://www.timeandbill.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] MetaModel for the Apache Incubator
Thank you Matt. I have updated the proposal to reflect the change of Champion for MetaModel proposal. Thanks, - Henry On Fri, May 31, 2013 at 5:44 PM, Matt Franklin m.ben.frank...@gmail.comwrote: Now that Henry is a member, I would like this proposal to reflect that he has really been the primary champion, not me. I am looking forward to staying on as a mentor, but Henry has been the driving force in getting MetaModel organized and proposed. I am more than willing to champion this project and help keep it going, but Henry's passion for its success is hard to match. On Fri, May 31, 2013 at 4:35 PM, Henry Saputra henry.sapu...@gmail.com wrote: Added Noah Slater (nslater at apache dot org) as mentor and initial committer to the proposal. - Henry On Tue, May 28, 2013 at 11:20 AM, Henry Saputra henry.sapu...@gmail.com wrote: Dear ASF members, We would like to propose MetaModel for the incubator. Matt Franklin will be the Champion for this project and the proposal draft is available at: https://wiki.apache.org/incubator/MetaModelProposal Looking forward to all of your suggestions and feedback. Thanks, Henry Saputra - = MetaModel – uniform data access across datastores = Proposal for Apache Incubator == Abstract == MetaModel is a data access framework, providing a common interface for exploration and querying of different types of datastores. == Proposal == MetaModel provides a uniform meta-model for exploring and querying the structure of datastores, covering but not limited to relational databases, various data file formats, NoSQL databases, Salesforce.com, SugarCRM and more. The scope of the project is to stay domain-agnostic, so the meta-model will be concerned with schemas, tables, columns, rows, relationships etc. On top of this meta-model a rich querying API is provided which resembles SQL, but built using compiler-checked Java language constructs. For datastores that do not have a native SQL-compatible query engine, the MetaModel project also includes an abstract Java-based query engine implementation which individual datastore-modules can adapt to fit the concrete datastore. === Background === The MetaModel project was initially developed by eobject.dk to service the DataCleaner application (http://datacleaner.org). The main requirement was to perform data querying and modification operations on a wide range of quite different datastores. Furthermore a programmatic query model was needed in order to allow different components to influence the query plan. In 2009, Human Inference acquired the eobjects projects including MetaModel. Since then MetaModel has been put to extensive use in the Human Inference products. The open source nature of the project was reinforced, leading to a significant growth in the community. MetaModel has successfully been used in a number of other open source projects as well as mission critical commercial software from Human Inference. Currently MetaModel is hosted at http://metamodel.eobjects.org. === Rationale === Different types of datastores have different characteristics, which always lead to the interfaces for these being different from one another. Standards like JDBC and the SQL language attempt to standardize data access, but for some datastore types like flat files, spreadsheets, NoSQL databases and more, such standards are not even implementable. Specialization in interfaces obviously has merit for optimized usage, but for integration tools, batch applications and or generic data modification tools, this myriad of specialized interfaces is a big pain. Furthermore, being able to query every datastore with a basic set of SQL-like features can be a great productivity boost for a wide range of applications. === Initial goals === MetaModel is already a stable project, so initial goals are more oriented towards an adaption to the Apache ecosystem than about functional changes. We are constantly adding more datastore types to the portfolio, but the core modules have not had drastic changes for some time. Our focus will be on making ties with other Apache projects (such as POI, Gora, HBase and CouchDB) and potentially renaming the ‘MetaModel’ project to something more rememberable. This includes comply with Apache Software Foundation license for third party dependencies. == Current status == === Meritocracy === We intend to do everything we can to encourage a meritocracy in the development of MetaModel. Currently most important development and design decisions have been made at Human Inference, but with an open window for anyone to participate on mailing lists and
[RESULT] [VOTE] Release Apache Mesos 0.11.0-incubating (RC3)
The vote to release mesos-0.11.0-incubating has passed with 3 IPMC binding +1s and 5 non-binding +1s: IPMC binding votes: Chris Mattmann BrianMcCallister Ant Elder Non-binding votes: Vinod Kone Brenden Matthews Yan Xu Ben Hindman Jean-Sebastien Delfino Thank you! On Sat, Jun 1, 2013 at 8:01 PM, Mattmann, Chris A (398J) chris.a.mattm...@jpl.nasa.gov wrote: Thanks Brian! Vinod, since Brian is a member of the IPMC, I believe we now have enough VOTEs to send a [RESULT]. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: Brian McCallister bri...@skife.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Saturday, June 1, 2013 5:01 PM To: mesos-...@incubator.apache.org mesos-...@incubator.apache.org Cc: general@incubator.apache.org general@incubator.apache.org Subject: Re: [VOTE] Release Apache Mesos 0.11.0-incubating (RC3) +1 On Tue, May 28, 2013 at 2:24 PM, Vinod Kone vinodk...@gmail.com wrote: Please vote on releasing the following candidate as Apache Mesos (incubating) version 0.11.0. This will be the third incubator release for Mesos in Apache . The candidate for Mesos 0.11.0-incubating release is available at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz The tag to be voted on: https://git-wip-us.apache.org/repos/asf?p=incubator-mesos.git;a=tag;h=dbc aa0d348a88188c17a8b06b57306832a7a5885 The MD5 checksum of the tarball can be found at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz.md5 The signature of the tarball can be found at: http://people.apache.org/~vinodkone/mesos-0.11.0-incubating-RC3/mesos-0.1 1.0-incubating.tar.gz.asc PGP key used to sign the release: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x2B1D89DA5C6E508C Please vote on releasing this package as Apache Mesos 0.11.0-incubating! The vote is open until Friday, May 31st at 18:30 UTC and passes if a majority of at least 3 +1 IPMC votes are cast. [ ] +1 Release this package as Apache Mesos 0.11.0-incubating [ ] -1 Do not release this package because ... To learn more about Apache Mesos, please see http://incubator.apache.org/mesos.
RE: Correct process for signing keys?
Hi Christian, Dennis Thanks for your responses and the links provided. By the sounds of it we're all roughly in the same position: aware of the different options and not 100% certain which is the current correct one, or if indeed all options are equally valid. Unfortunately, the docs also do seem to clearly identify which, if any, of the options is preferred. @IPMC: would it be correct to infer that, at the present, time, a group or project KEYS file is fine but simply ensuring the release managers' keys are available from people.apache would be sufficient or, indeed, preferable? Thanks! ap -- Andrew Phillips jclouds - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Correct process for signing keys?
I think that the RM _must_ have a key, that the key must be part of a KEYS file in svn/git, and that it _should_ be uploaded into their Apache account, and it is more better if it is signed into the GWOT (global web of trust). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Correct process for signing keys?
Well, I've got the first three, and will bug coworkers in the GWOT to sign my key next week. =) A. On Sun, Jun 2, 2013 at 2:13 PM, Benson Margulies bimargul...@gmail.comwrote: I think that the RM _must_ have a key, that the key must be part of a KEYS file in svn/git, and that it _should_ be uploaded into their Apache account, and it is more better if it is signed into the GWOT (global web of trust). - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On 2 June 2013 17:21, a...@apache.org wrote: Author: adc Date: Sun Jun 2 16:21:24 2013 New Revision: 1488735 URL: http://svn.apache.org/r1488735 Log: First few utility functions/classes Also include LinkedIn notice Added: incubator/public/trunk/tools/src/asf/utils/ incubator/public/trunk/tools/src/asf/utils/__init__.py incubator/public/trunk/tools/src/asf/utils/config.py incubator/public/trunk/tools/src/asf/utils/file.py incubator/public/trunk/tools/tests/test_config.py Modified: incubator/public/trunk/tools/NOTICE.txt incubator/public/trunk/tools/requirements.txt incubator/public/trunk/tools/setup.py Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities== +== Version 2.0.0, in this case for the ASF Incubator tools== == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote: Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities== +== Version 2.0.0, in this case for the ASF Incubator tools== == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! Would this suffice: begin This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. endj Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote: Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities== +== Version 2.0.0, in this case for the ASF Incubator tools== == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! Would this suffice: begin This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. endj IMO, no. It's not a standard NOTICE file - the ASF header is missing. Anyway, does the LinkedIn license REQUIRE attribution in a NOTICE file? Regards, Alan - 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] Apache Ambari 1.2.3-incubating RC1
+1 From: Jitendra Pandey Sent: 6/2/2013 5:18 PM To: ambari-...@incubator.apache.org Cc: general Subject: Re: [VOTE] Apache Ambari 1.2.3-incubating RC1 +1 On Wed, May 29, 2013 at 10:34 PM, Siddharth Wagle swa...@hortonworks.comwrote: +1 for the release. On Wed, May 29, 2013 at 7:09 PM, Yusaku Sako yus...@hortonworks.com wrote: Hi all, ambari-1.2.3-incubating-rc1 release candidate is now available. Here's a summary of Ambari 1.2.3 features: * Improved stability * Ability to update core-site.xml properties post-install * Ability to add and remove custom configuration properties * New Heatmaps (Host CPU WIO %, HBase RegionServer Reads/Writes/Regions/QueueSize/MemstoreSize) * Ability to add host components on existing hosts * Filter hosts by host health status * Mixed OS support * init.d scripts * Support for Oracle Enterprise Linux 5 and 6 I have successfully deployed a 5-node cluster on RHEL 6.3 using the instructions available at: http://incubator.apache.org/ambari/1.2.3/installing-hadoop-using-ambari/content/index.html SVN source tag: https://svn.apache.org/repos/asf/incubator/ambari/tags/release-1.2.3-rc1 Staging site: http://people.apache.org/~yusaku/ambari-1.2.3-incubating-rc1 PGP release keys (signed using 3ABE18B3) http://pgp.mit.edu:11371/pks/lookup?op=vindexsearch=0x4C3AA2723ABE18B3 One can look into the issues fixed in this release at: https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMBARI%20AND%20fixVersion%20%3D%20%221.2.3%22%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my vote to start: +1 (binding) Yusaku -- http://hortonworks.com/download/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 5:29 PM, sebb seb...@gmail.com wrote: On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote: Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities== +== Version 2.0.0, in this case for the ASF Incubator tools== == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! Would this suffice: begin This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. endj IMO, no. It's not a standard NOTICE file - the ASF header is missing. Can you point to a canonical example for me to emulate? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 10:09 PM, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 5:29 PM, sebb seb...@gmail.com wrote: On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote: Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities== +== Version 2.0.0, in this case for the ASF Incubator tools== == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! Would this suffice: begin This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. endj IMO, no. It's not a standard NOTICE file - the ASF header is missing. Can you point to a canonical example for me to emulate? How about the following: http://www.apache.org/legal/src-headers.html#notice and http://www.apache.org/dev/licensing-howto.html --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 7:45 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Jun 2, 2013, at 10:09 PM, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 5:29 PM, sebb seb...@gmail.com wrote: On 3 June 2013 00:37, Alan Cabrera l...@toolazydogs.com wrote: On Jun 2, 2013, at 4:01 PM, sebb seb...@gmail.com wrote: Modified: incubator/public/trunk/tools/NOTICE.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/tools/NOTICE.txt?rev=1488735r1=1488734r2=1488735view=diff == --- incubator/public/trunk/tools/NOTICE.txt (original) +++ incubator/public/trunk/tools/NOTICE.txt Sun Jun 2 16:21:24 2013 @@ -1,5 +1,21 @@ = == NOTICE file corresponding to section 4(d) of the Apache License, == -== Version 1.0.0, in this case for the LiveTribe Utilities == +== Version 2.0.0, in this case for the ASF Incubator tools == == distribution. == = + +This distribution contains code from the LinkedIn Corporation: + + Copyright (c) 2013 LinkedIn Corp. All rights reserved. + + Licensed under the Apache License, Version 2.0 (the License); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an AS IS BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. That does not look like a standard NOTICE file. The part between === should not be present, and the AL 2.0 should not be there either. Is the notice entry even required by the Linked In license? Remember that NOTICE files are like poems - they are only correct when nothing more can be removed! Would this suffice: begin This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. endj IMO, no. It's not a standard NOTICE file - the ASF header is missing. Can you point to a canonical example for me to emulate? How about the following: http://www.apache.org/legal/src-headers.html#notice and http://www.apache.org/dev/licensing-howto.html Apache Incubator tools Copyright 2013 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. Licensed under the Apache License, Version 2.0 WDYT? Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 11:08 PM, Alan Cabrera l...@toolazydogs.com wrote: Apache Incubator tools Copyright 2013 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. Licensed under the Apache License, Version 2.0 WDYT? There is still Sebb's outstanding question: Anyway, does the LinkedIn license REQUIRE attribution in a NOTICE file? --kevan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Jun 2, 2013, at 8:51 PM, Kevan Miller kevan.mil...@gmail.com wrote: On Jun 2, 2013, at 11:08 PM, Alan Cabrera l...@toolazydogs.com wrote: Apache Incubator tools Copyright 2013 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. Licensed under the Apache License, Version 2.0 WDYT? There is still Sebb's outstanding question: Anyway, does the LinkedIn license REQUIRE attribution in a NOTICE file? I was asked to provide attribution. The NOTICE file seemed to be a reasonable plea to put it. Regards, Alan - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1488735 - in /incubator/public/trunk/tools: NOTICE.txt requirements.txt setup.py src/asf/utils/ src/asf/utils/__init__.py src/asf/utils/config.py src/asf/utils/file.py tests/test_conf
On Sun, Jun 2, 2013 at 11:08 PM, Alan Cabrera l...@toolazydogs.com wrote: ... Apache Incubator tools Copyright 2013 The Apache Software Foundation This product includes software developed at The Apache Software Foundation (http://www.apache.org/). This distribution contains code from the LinkedIn Corporation: Copyright (c) 2013 LinkedIn Corp. All rights reserved. Licensed under the Apache License, Version 2.0 WDYT? Looks good. And given that the LinkedIn stuff is under ALv2, then 4(d) comes into play, requesting attribution. It is Right and Proper that they get a couple lines in our NOTICE file. Note that we may even need to incorporate portions of *their* NOTICE file. (I don't know the extent of inclusion/derivation, but ALv2 4(d) is pretty straight-forward) Cheers, -g - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
