Re: Amber CLA status [Was: Old projects with incomplete copyright diligence]
Sounds like you should sign off on the first item in the Copyright section of http://incubator.apache.org/projects/amber.html as n/a. No code was relicensed to the ASF when Amber was created. Instead it was a fork of Uni of Newcastle code and that copyright remains on the code. Hen On Mon, Aug 20, 2012 at 1:00 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, thanks for taking care of this. IANAL but technically yes I think that the OAuth 2.0 part of Amber can be considered as a fork. Before to perform the first release we followed what has been suggested in LEGAL-134. Did we miss something? Should we do something more or we can assume this legal issue is over? Thanks and regards Antonio On Aug 12, 2012, at 8:28 PM, Henri Yandell wrote: Hi Antonio, This is about making sure that all software being contributed to Apache is covered by CLAs (continuous contribution) or the software license grant (single contribution). Legally it would also be fine to fork software under a Category A license, though it's frowned upon (ie: the status checkbox doesn't offer it as an option). By the look of LEGAL-134, it sounds like Amber started as a fork of University of Newcastle code? Hen On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, Amber wise we tracked this in [0]. Now I am not sure if we can also tick the box. Regards Antonio [0] https://issues.apache.org/jira/browse/LEGAL-134 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote: The following projects haven't signed off on the copyright checklist item: 2009-02-09 kato 2009-02-13 stonehenge 2009-05-13 socialsite 2010-05-19 amber 2010-09-05 nuvem 2010-11-12 kitty 2010-11-24 stanbol 2011-06-13 openofficeorg Said checklist item is: Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. How long do we host software without explicitly stating we have these rights? Personally I think 1 year is more than enough, even for OpenOffice. Note that this list comes from https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Amber CLA status [Was: Old projects with incomplete copyright diligence]
Thanks a lot for your effort Henri, we will do as you suggested. Do you thing we are missing anything else legally wise? Regards Antonio On Aug 23, 2012, at 9:18 AM, Henri Yandell wrote: Sounds like you should sign off on the first item in the Copyright section of http://incubator.apache.org/projects/amber.html as n/a. No code was relicensed to the ASF when Amber was created. Instead it was a fork of Uni of Newcastle code and that copyright remains on the code. Hen On Mon, Aug 20, 2012 at 1:00 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, thanks for taking care of this. IANAL but technically yes I think that the OAuth 2.0 part of Amber can be considered as a fork. Before to perform the first release we followed what has been suggested in LEGAL-134. Did we miss something? Should we do something more or we can assume this legal issue is over? Thanks and regards Antonio On Aug 12, 2012, at 8:28 PM, Henri Yandell wrote: Hi Antonio, This is about making sure that all software being contributed to Apache is covered by CLAs (continuous contribution) or the software license grant (single contribution). Legally it would also be fine to fork software under a Category A license, though it's frowned upon (ie: the status checkbox doesn't offer it as an option). By the look of LEGAL-134, it sounds like Amber started as a fork of University of Newcastle code? Hen On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, Amber wise we tracked this in [0]. Now I am not sure if we can also tick the box. Regards Antonio [0] https://issues.apache.org/jira/browse/LEGAL-134 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote: The following projects haven't signed off on the copyright checklist item: 2009-02-09 kato 2009-02-13 stonehenge 2009-05-13 socialsite 2010-05-19 amber 2010-09-05 nuvem 2010-11-12 kitty 2010-11-24 stanbol 2011-06-13 openofficeorg Said checklist item is: Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. How long do we host software without explicitly stating we have these rights? Personally I think 1 year is more than enough, even for OpenOffice. Note that this list comes from https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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: Amber CLA status [Was: Old projects with incomplete copyright diligence]
There are other legal items on that page that you should review and decide if you can check off. If you're releasing, then I would expect that page to have no unfinished tasks. Hen On Thu, Aug 23, 2012 at 12:32 AM, Antonio Sanso asa...@adobe.com wrote: Thanks a lot for your effort Henri, we will do as you suggested. Do you thing we are missing anything else legally wise? Regards Antonio On Aug 23, 2012, at 9:18 AM, Henri Yandell wrote: Sounds like you should sign off on the first item in the Copyright section of http://incubator.apache.org/projects/amber.html as n/a. No code was relicensed to the ASF when Amber was created. Instead it was a fork of Uni of Newcastle code and that copyright remains on the code. Hen On Mon, Aug 20, 2012 at 1:00 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, thanks for taking care of this. IANAL but technically yes I think that the OAuth 2.0 part of Amber can be considered as a fork. Before to perform the first release we followed what has been suggested in LEGAL-134. Did we miss something? Should we do something more or we can assume this legal issue is over? Thanks and regards Antonio On Aug 12, 2012, at 8:28 PM, Henri Yandell wrote: Hi Antonio, This is about making sure that all software being contributed to Apache is covered by CLAs (continuous contribution) or the software license grant (single contribution). Legally it would also be fine to fork software under a Category A license, though it's frowned upon (ie: the status checkbox doesn't offer it as an option). By the look of LEGAL-134, it sounds like Amber started as a fork of University of Newcastle code? Hen On Fri, Jul 13, 2012 at 7:39 AM, Antonio Sanso asa...@adobe.com wrote: Hi Henri, Amber wise we tracked this in [0]. Now I am not sure if we can also tick the box. Regards Antonio [0] https://issues.apache.org/jira/browse/LEGAL-134 On Jul 8, 2012, at 4:22 AM, Henri Yandell wrote: The following projects haven't signed off on the copyright checklist item: 2009-02-09 kato 2009-02-13 stonehenge 2009-05-13 socialsite 2010-05-19 amber 2010-09-05 nuvem 2010-11-12 kitty 2010-11-24 stanbol 2011-06-13 openofficeorg Said checklist item is: Check and make sure that the papers that transfer rights to the ASF been received. It is only necessary to transfer rights for the package, the core code, and any new code produced by the project. How long do we host software without explicitly stating we have these rights? Personally I think 1 year is more than enough, even for OpenOffice. Note that this list comes from https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects Hen - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name
Scott Wilson created PODLINGNAMESEARCH-13: - Summary: Establish whether Apache Wookie is a suitable name Key: PODLINGNAMESEARCH-13 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Scott Wilson We have to do some investigations to ensure that Apache Wookie 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/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Updated] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Wilson updated PODLINGNAMESEARCH-13: -- Evidence Of Registration: I conducted a US Trademark Search, this shows no results for Wookie: http://www.trademarkia.com/trademarks-search.aspx?tn=wookiefs=01/01/1960fe=08/02/2012pri=009gs=cn=st=1 Establish whether Apache Wookie is a suitable name Key: PODLINGNAMESEARCH-13 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Scott Wilson We have to do some investigations to ensure that Apache Wookie 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/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440198#comment-13440198 ] Scott Wilson commented on PODLINGNAMESEARCH-13: --- A Google search for Wookie Software shows Apache Wookie as the top 3 results; the 4th result is a reference in a course description to Wookie as a software simulator for Windows that can simulate the function of a real 68HC11 microcontroller (http://www.ele.uri.edu/courses/ele205/Lab03.pdf). Further searches show references in a few other electronics course descriptions, as recently as 2009. Much further into the results is a reference to WookieChat - and IRC client for the AmigaOS: http://wookiechat.amigarevolution.com/wookiechat/ There are also some references to a radio-related application on some forums, e.g.: 2100-WOOKIE-LAB- Field Programmer for the MOBIUS Radio-Series (Sky Walker) 2100 portables and mobiles radio with 5/6 Tone signalizing. v.R2.01beta SDVN4274A. Is dus Wookie lab software, is een Beta en daarom is hij niet volledig 100% betrouwbaar. Dat uit zich in het soms niet kunnen benaderen van de tuningmodus. Wookie wil bij het opslaan van je codeplug nog wel eens alle kanalen op eenzelfde frequentie zetten. Soms kun je met een nieuwe installatie wel in de tuningmodus komen. Maar de beste oplossing om dit uit te laten voeren door iemand met kennis van zaken (en die gebruikt de Ms-Dos RSS versie!). http://www.scannerforum.nl/index.php?topic=6418.0 Establish whether Apache Wookie is a suitable name Key: PODLINGNAMESEARCH-13 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Scott Wilson We have to do some investigations to ensure that Apache Wookie 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/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440203#comment-13440203 ] Scott Wilson commented on PODLINGNAMESEARCH-13: --- A search on Github for Wookie yields 14 repositories: - 7 of these are plugins for Apache Wookie, or ports of the Apache Wookie W3C library jar to other platforms/languages - alto/wookie is a Rails plugin for exporting stats; last updated 3 years ago - CaioMatias/Wookie is a Flash project framework - BookieWookie is a link-sharing plugin for Rails; last updated 3 years ago - wookie-translator is an english-to-wookie translator (probably a misspelling of Wookiee from Star Wars) - wookie-cab- is an empty project - wookie-cam is an empty project - fernandoafb/wookie is an empty project Establish whether Apache Wookie is a suitable name Key: PODLINGNAMESEARCH-13 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Scott Wilson We have to do some investigations to ensure that Apache Wookie 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/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Commented] (PODLINGNAMESEARCH-13) Establish whether Apache Wookie is a suitable name
[ https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440206#comment-13440206 ] Scott Wilson commented on PODLINGNAMESEARCH-13: --- A search on Sourceforge for Wookie yields 1 project: http://wookilang.sourceforge.net/; This is the Wooki Language Interpreter project (wookilang) This project was registered on SourceForge.net on Apr 17, 2011, and is described by the project team as follows: It is a language and interpreter aiming to test data structures, with debugging tools. Establish whether Apache Wookie is a suitable name Key: PODLINGNAMESEARCH-13 URL: https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-13 Project: Podling Suitable Names Search Issue Type: Suitable Name Search Reporter: Scott Wilson We have to do some investigations to ensure that Apache Wookie 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/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
A request/suggestion for shepherds: be firm about IP clearance
After my recent adventure sorting out Kato's IP clearance, I have an intention as a shepherd, and I'd like to suggest that others pick it up, as well. If a podling has not filled in the IP clearance field on their status page, ask them what's going on, and ask them to report the status in their report. If IP clearance is done but the status field is not checked, insist that they go edit that page, *right now*, and insert the necessary data. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Created] (INCUBATOR-125) How-to guide for Assembling LICENSE and NOTICE
Marvin Humphrey created INCUBATOR-125: - Summary: How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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: [VOTE] Apache DeltaSpike 0.3-incubating
+1!
-David
On Aug 20, 2012, at 6:47 AM, Mark Struberg wrote:
Hi Folks!
The deltaspike-0.3-incubating vote has internally passed with lots of +1.
We have 2 IPMC +1 so far and like to ask for a tough review from fellow IPMCs.
[+1] all fine, ship it
[+0] I don't care but smells fine
[-1] stop it, this stuff contains a blocker ${insertreason}
The VOTE is open for 72h.
txs and LieGrue,
strub
- Forwarded Message -
From: Mark Struberg strub...@yahoo.de
To: deltaspike-...@incubator.apache.org
deltaspike-...@incubator.apache.org
Cc:
Sent: Monday, August 20, 2012 3:43 PM
Subject: Re: [VOTE] [RESULT] Apache DeltaSpike 0.3-incubating
T ime to tally the vote.
+1: Mark Struberg (IPMC), Shane Bryzak, Gerhard Petracek (IPMC), Mehdi
Heidarzadeh (nonbinding), Lincoln Baxter, Romain Manni-Buccau, Thomas Herzog
(nonbinding), Cody Lerum, Arne Limburg, Charles Moulliard, Jason Porter, Ken
Finnigan, Christian Kaltepoth, Antoine Sabot-Durand
no -1 and no 0.
I'll forward the vote mail for a rewiew to general@incubator.
LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: deltaspike deltaspike-...@incubator.apache.org
Cc:
Sent: Wednesday, August 15, 2012 11:56 AM
Subject: [VOTE] Apache DeltaSpike 0.3-incubating
Hi!
I like to call a VOTE on the Apache DeltaSpike 0.3-incubating release.
The Maven staging repository:
https://repository.apache.org/content/repositories/orgapachedeltaspike-010/
The source release package:
https://repository.apache.org/content/repositories/orgapachedeltaspike-010/org/apache/deltaspike/deltaspike-project/0.3-incubating/
I've pushed the GIT release branch to my github account:
https://github.com/struberg/incubator-deltaspike/tree/deltaspike-0.3-incubating
(The branch will be pushed and merged to master after the VOTE passed.)
The TAG can be found here:
https://github.com/struberg/incubator-deltaspike/tree/deltaspike-project-0.3-incubating
Please note:
This VOTE is majority approval with a minimum of three +1votes
of
PPMC members.
The VOTE is open for 72 hours.
[+1] all fine, ship it
[+0] I don't care but smells fine
[-1] stop it, this stuff contains a blocker ${insertreason}
LieGrue,
strub
-
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] [RESULT] Apache DeltaSpike 0.3-incubating
The VOTE has passed with the following IPMC +1:
David Blevins, Matze Wessendorf, Mark Struberg, Gerhard Petracek
No -1 nor 0.
I'll go on with the release process.
txs and LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: general@incubator.apache.org general@incubator.apache.org
Cc:
Sent: Monday, August 20, 2012 3:47 PM
Subject: [VOTE] Apache DeltaSpike 0.3-incubating
Hi Folks!
The deltaspike-0.3-incubating vote has internally passed with lots of +1.
We have 2 IPMC +1 so far and like to ask for a tough review from fellow IPMCs.
[+1] all fine, ship it
[+0] I don't care but smells fine
[-1] stop it, this stuff contains a blocker ${insertreason}
The VOTE is open for 72h.
txs and LieGrue,
strub
- Forwarded Message -
From: Mark Struberg strub...@yahoo.de
To: deltaspike-...@incubator.apache.org
deltaspike-...@incubator.apache.org
Cc:
Sent: Monday, August 20, 2012 3:43 PM
Subject: Re: [VOTE] [RESULT] Apache DeltaSpike 0.3-incubating
T ime to tally the vote.
+1: Mark Struberg (IPMC), Shane Bryzak, Gerhard Petracek (IPMC), Mehdi
Heidarzadeh (nonbinding), Lincoln Baxter, Romain Manni-Buccau, Thomas
Herzog
(nonbinding), Cody Lerum, Arne Limburg, Charles Moulliard, Jason Porter,
Ken
Finnigan, Christian Kaltepoth, Antoine Sabot-Durand
no -1 and no 0.
I'll forward the vote mail for a rewiew to general@incubator.
LieGrue,
strub
- Original Message -
From: Mark Struberg strub...@yahoo.de
To: deltaspike deltaspike-...@incubator.apache.org
Cc:
Sent: Wednesday, August 15, 2012 11:56 AM
Subject: [VOTE] Apache DeltaSpike 0.3-incubating
Hi!
I like to call a VOTE on the Apache DeltaSpike 0.3-incubating release.
The Maven staging repository:
https://repository.apache.org/content/repositories/orgapachedeltaspike-010/
The source release package:
https://repository.apache.org/content/repositories/orgapachedeltaspike-010/org/apache/deltaspike/deltaspike-project/0.3-incubating/
I've pushed the GIT release branch to my github account:
https://github.com/struberg/incubator-deltaspike/tree/deltaspike-0.3-incubating
(The branch will be pushed and merged to master after the VOTE
passed.)
The TAG can be found here:
https://github.com/struberg/incubator-deltaspike/tree/deltaspike-project-0.3-incubating
Please note:
This VOTE is majority approval with a minimum of three
+1votes
of
PPMC members.
The VOTE is open for 72 hours.
[+1] all fine, ship it
[+0] I don't care but smells fine
[-1] stop it, this stuff contains a blocker ${insertreason}
LieGrue,
strub
-
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
[jira] [Updated] (INCUBATOR-125) How-to guide for Assembling LICENSE and NOTICE
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Humphrey updated INCUBATOR-125: -- Attachment: licensing_howto.mdtext How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey Attachments: licensing_howto.mdtext While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Commented] (INCUBATOR-125) How-to guide for Assembling LICENSE and NOTICE
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440563#comment-13440563 ] Sebb commented on INCUBATOR-125: Very useful. compiled package = binary package would be clearer. I don't think it's advisable to incorporate the list of license types; just link to where the official list is found. How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey Attachments: licensing_howto.mdtext While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[jira] [Commented] (INCUBATOR-125) How-to guide for Assembling LICENSE and NOTICE
[ https://issues.apache.org/jira/browse/INCUBATOR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440619#comment-13440619 ] Marvin Humphrey commented on INCUBATOR-125: --- Hi, Sebb, Thanks for the review! compiled package = binary package would be clearer. +1, sounds good. I don't think it's advisable to incorporate the list of license types; just link to where the official list is found. That list and the list of license types from the ASF legal FAQ are not the same. While most (?) licenses in category A do not include required third party notices that may have to go into NOTICE, there are at least 3 exceptions: ALv1.0, ALv1.1, ALv2. The reason that the ALv2 is broken out is because it must be treated differently from BSD, MIT, etc, what with its NOTICE file. ALv1.1 will require an additional special section because of its advertising clause. It's possible that other licenses in category A also have special requirements. There's a TODO item in the draft document to perform that research (presumably via legal-discuss) before the page goes live. In my view, it's essential to do this work in advance so that PMCs don't wind up poring over the text of licenses trying to figure out whether something needs to go into NOTICE or whatever. That's what leads to people deciding that the copyright notice in a BSD license has to go into NOTICE -- because that sure sounds like a required third party notice, right? (see LEGAL-59.) How-to guide for Assembling LICENSE and NOTICE Key: INCUBATOR-125 URL: https://issues.apache.org/jira/browse/INCUBATOR-125 Project: Incubator Issue Type: Improvement Components: site Reporter: Marvin Humphrey Attachments: licensing_howto.mdtext While the ASF provides reference documentation for LICENSE and NOTICE, confusion persists and existing versions vary widely in quality. To address these problems, we should augment the reference documentation with a how-to guide which provides formulaic instructions for assembling LICENSE and NOTICE under common conditions. One key feature of this how-to should be a mapping of approved licenses to what they require as far as NOTICE. This mapping will help PMCs determine when the licensing information of a dependency contains a required third party notice which must be added to NOTICE. There are at least four possible locations where this how-to might live: * www.apache.org/dev/licensing_howto.html -- probably the best location, considering the intended audience. * www.apache.org/legal/licensing_howto.html -- if legal wants it. * incubator.apache.org/guides/licensing_howto.html -- probably not ideal, because the information applies to TLPs as well as podlings and we have a problem with duplication. * Somewhere on community.apache.org -- in theory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa 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
[RESULT][VOTE] Graduate Oozie podling from Apache Incubator
The VOTE by Apache Incubator to graduate Oozie podling has passed. Tally of binding votes is as follows: 5 +1 votes Chris Mattmann Arvind Prabhakar Chris Douglas Alan Gates Bertrand Delacretaz 0 +0 votes 0 -1 votes The VOTE threads for this can be found at [1]. I will proceed by sending the proposal to the board. [1] http://s.apache.org/Gs0 http://s.apache.org/UJp Thanks and regards, Alejandro Abdelnur - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
