Re: Source code dumps via JIRA?
Hi All, For OODT, we think we want to import the prior history of the project into the podling via a Subversion dump file. However, in: http://incubator.apache.org/guides/mentor.html#initial-import-code-dump it says: --- In either case, the code to be imported should be attached to a JIRA and then imported. It is recommended that the previous version control system is tagged so that the imported version is precisely known. A public record MUST be made of the code imported. If the import is not attached to JIRA then it MUST be committed to version control. --- I can understand the rationale for having a public record, but I'm not seeing the reasoning for JIRA. Can someone please shed some light on this? Is this really reflective of actual best practices? As a counter-example, I'd believe providing a URL to the dump (or uploading it to people.a.o) and providing a SHA checksum via email (PGP-signed?) would be sufficient for our purposes. -- justin My (non-binding) +1 to this. Cheers, Chris - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[ANNOUNCE] Apache Tuscany SCA Java 1.6 released
The Apache Tuscany team are pleased to announce the 1.6 release of the Java SCA project. Apache Tuscany provides a runtime environment based on the Service Component Architecture (SCA). SCA is a set of specifications aimed at simplifying SOA application development. These specifications are being standardized by OASIS as part of the Open Composite Services Architecture (Open CSA). This 1.6 release adds various improvements over the previous releases and includes numerous bug fixes and enhancements, see the RELEASE_NOTES and CHANGES file for details, and to download the distributions please go to: http://tuscany.apache.org/sca-java-releases.html To find out more about OASIS Open CSA go to: http://www.oasis-opencsa.org Apache Tuscany welcomes your help. Any contribution, including code, testing, contributions to the documentation, or bug reporting is always appreciated. For more information on how to get involved in Apache Tuscany visit the website at: http://tuscany.apache.org Thank you for your interest in Apache Tuscany! -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Source code dumps via JIRA?
On Mon, Feb 8, 2010 at 9:47 PM, Paul Querna p...@querna.org wrote: For most projects they just put a URL in the jira, and Joe just imports it. So, is this just a failure of the documentation to reflect what is actually done? If so, I'm happy to update the documentation. -- justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Source code dumps via JIRA?
On Tue, Feb 9, 2010 at 3:48 PM, Justin Erenkrantz jus...@erenkrantz.com wrote: On Mon, Feb 8, 2010 at 9:47 PM, Paul Querna p...@querna.org wrote: For most projects they just put a URL in the jira, and Joe just imports it. So, is this just a failure of the documentation to reflect what is actually done? more a case of best practice evolving, i think If so, I'm happy to update the documentation. cool - robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Source code dumps via JIRA?
On Tue, Feb 9, 2010 at 5:22 AM, Justin Erenkrantz jus...@erenkrantz.com wrote: For OODT, we think we want to import the prior history of the project into the podling via a Subversion dump file. However, in: http://incubator.apache.org/guides/mentor.html#initial-import-code-dump it says: --- In either case, the code to be imported should be attached to a JIRA and then imported. It is recommended that the previous version control system is tagged so that the imported version is precisely known. A public record MUST be made of the code imported. If the import is not attached to JIRA then it MUST be committed to version control. --- I can understand the rationale for having a public record, but I'm not seeing the reasoning for JIRA. Can someone please shed some light on this? Is this really reflective of actual best practices? that part of the document's a draft - just a starting point. most of it is just collected practice, not necessarily best. someone needs to pick it up and drive it through a review process so that best practice can emerge. one way of doing the review would be to pick sections like this an throw it open for comments and improvements before you try to apply the guidelines. or just patch it as you go - robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [Vote] Release Kato M1-incubating - please vote!
On Sun, Feb 7, 2010 at 4:36 AM, Matt Hogstrom m...@hogstrom.org wrote: I downloaded one of the tar balls and did some spot checking for licenses and verified pgp sigs. +1 +1 well done - robert - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE RESULTS] was: [Vote] Release Kato M1-incubating
The vote is now closed. The vote results are: +1 votes: 4 (Ant Elder, Matt Hogstrom, Robert Burrell Donkin, Mark Hindess) 0 votes: 0 -1 votes: 0 The vote therefore passes. Many thanks to those who voted. Regards, Stuart Stuart Monteith wrote: The Kato community has voted to release Kato M1-incubating. We now request the Incubator PMC for a vote. The proposed release artifacts are located at: http://people.apache.org/~monteith/kato/apache-kato-M1-incubating-RC3/ There are packages for the Java binaries with documentation, source and native libaries for Linux and Windows x86. Each package is available in tar.gz and zip form, expect for the native packages. asc, md5 and sha1 (SHA512) files are generated for each. rat*.txt files have been generated for each of the packages contents. The mapping is: apache-kat-M1-incubating-bin.(tar.gz|zip) - rat-bin.txt apache-kat-M1-incubating-src.(tar.gz|zip) - rat-src.txt apache-kat-M1-incubating-native-bin-linux-i386.tar.gz - rat-bin-linux.txt apache-kat-M1-incubating-native-bin-windows-i386.zip - rat-bin-windows.txt Please review the artifacts and cast your vote by Thursday 4th February. Thanks in advance, Stuart Monteith -- Stuart Monteith http://blog.stoo.me.uk/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] Commented: (INCUBATOR-106) MetaCarta Lucene Connector Framework code grant
[ https://issues.apache.org/jira/browse/INCUBATOR-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12831613#action_12831613 ] Karl Wright commented on INCUBATOR-106: --- Here are the complete dependencies (other than the third-party client libraries, that are local to individual connectors): - Sun dependency (standard jsp tag library jars and tlds: jstl.jar, standard.jar, sql.tld, c.tld, fmt.tld, x.tld, and servlet.jar) - Apache dependency, unexceptional (commons-fileupload, commons-collections, commons-codec, commons-logging, log4j, axis, castor) - Apache dependency, requiring upstream modifications in order to build properly (commons-httpclient, xerces2-java) - LGPL dependency, possibly requiring upstream modifications in order to run properly (jcifs) - LGPL dependency, not requiring upstream modifications in order to run properly (postgres jdbc driver, jtds) - BSD jar dependency (Bitstream pool driver, jdbcpool-0.99.jar) - Third party proprietary jars (not enumerated here) - Dependencies which will be immediately removed (metacarta-license.jar) MetaCarta Lucene Connector Framework code grant --- Key: INCUBATOR-106 URL: https://issues.apache.org/jira/browse/INCUBATOR-106 Project: Incubator Issue Type: New Feature Reporter: Karl Wright Assignee: Grant Ingersoll Attachments: apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, apache-lcf-software-grant.tar.gz, build.xml kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ dpkg --list | grep coreutils ii coreutils 6.10-6 The GNU core utilities kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ md5sum apache-lcf-software-grant.tar.gz 1e429efbc2359a18912948411e09a76f apache-lcf-software-grant.tar.gz kwri...@kuskokwim:~/export-area/apache-lcf-software-grant$ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Request PMC Karma for IP Process
I'm following the checklist at: http://incubator.apache.org/ip-clearance/ip-clearance-template.html for clearing a submission of the Nexus Indexer code to the Maven Project. 1)IP Clearance processing must be executed either by an Officer or a Member of the ASF. If you are not an Officer or a Member, please contact your project chair who will find an appropriate volunteer. Incubator karma is also required. Please request karma from the incubator pmc if you do not have it. So I hereby request incubator pmc karma. Thanks, Brian Fox Apache Maven PMC Chair - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
IP Clearance question
Question on Step 3: A software grant must be provided to the ASF. This grant can either be done by the ASF Corporate CLA (via Schedule B) or the traditional License Agreement. Acceptable methods of sending the grant to the ASF includes: snail-mail to the ASF office and/or ASF officer FAXing to the ASF office and/or an ASF officer Emailing the scanned document to secret...@apache.org and legal-arch...@apache.org. Sonatype already has a CCLA on file and all the active committers are already Maven Committers. Do we need to file any additional paper work or is this step covered? --Brian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance Question
So as I understand it, the old copyright can exist in the NOTICES file and that's ok in conjunction with the standard Apache license headers copyright? On Tue, Feb 2, 2010 at 2:10 PM, Robert Burrell Donkin robertburrelldon...@gmail.com wrote: On Mon, Feb 1, 2010 at 11:47 PM, Niclas Hedhman nic...@hedhman.org wrote: I think this will be promoted now, after the recent license header issues in another podling... +1 once i have a minute, i planned to drawing up additional policy - robert - 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: Checking status of transfer rights ?
On Mon, Feb 8, 2010 at 8:49 AM, Leif Hedstrom zw...@apache.org wrote: Hi, sorry if this is not the right channel for this question, but, I'd like to find out if ASF has received any paperworks from Yahoo!, showing that we've transfered the rights for Traffic Server code to ASF. If not, is there a form that they need to fill out and submit? There hasn't been a CCLA, but all of traffic servers commits have been covered by iCLAs of the comitters, so no, Yahoo does not need to do anything else. Also, I know we still need to transfer some TM over to ASF as well, but that is still being worked on. I'd assume transfer of these remaining TMs (most have expired already, including the one in the US) is a prerequisite for doing an official Apache Traffic Server release? I honestly don't think we should block doing a release on this, if Yahoo sues us over the TM, well... heh, it just doesn't make sense. Thanks, Paul - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request PMC Karma for IP Process
Noel will usually process this within a few days, but if you need someone to commit something in the mean time feel free to ping me. On 10/02/2010, at 8:47 AM, Brian Fox wrote: I'm following the checklist at: http://incubator.apache.org/ip-clearance/ip-clearance-template.html for clearing a submission of the Nexus Indexer code to the Maven Project. 1)IP Clearance processing must be executed either by an Officer or a Member of the ASF. If you are not an Officer or a Member, please contact your project chair who will find an appropriate volunteer. Incubator karma is also required. Please request karma from the incubator pmc if you do not have it. So I hereby request incubator pmc karma. Thanks, Brian Fox Apache Maven PMC Chair - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance question
On 10/02/2010, at 8:49 AM, Brian Fox wrote: Question on Step 3: A software grant must be provided to the ASF. This grant can either be done by the ASF Corporate CLA (via Schedule B) or the traditional License Agreement. Acceptable methods of sending the grant to the ASF includes: snail-mail to the ASF office and/or ASF officer FAXing to the ASF office and/or an ASF officer Emailing the scanned document to secret...@apache.org and legal-arch...@apache.org. Sonatype already has a CCLA on file and all the active committers are already Maven Committers. Do we need to file any additional paper work or is this step covered? I think you'd either need to amend the CCLA to fill out schedule B, or submit a software grant. While a contributor can probably commit it under section 7 of the CLA with the org's permission, given the size of it and that it's a contribution from multiple people at once, I think the grant is more appropriate. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
