Re: [IP CLEARANCE] Apache Maven - Mvndaemon

[Hervé BOUTEMY]

AFAIK, Guillaume fixed the issue as described in 
 https://issues.apache.org/jira/browse/LEGAL-586

Nothing blocks now, isn't it?

Do we consider the clearance ok as a conclusion, or should we restart a new 
thread?

Regards,

Hervé

Le jeudi 16 septembre 2021, 10:05:06 CET Olivier Lamy a écrit :
> FYI legal JIRA raise https://issues.apache.org/jira/browse/LEGAL-586
> cheers
> Olivier
> 
> On Tue, 7 Sept 2021 at 19:26, Justin Mclean 
> 
> wrote:
> > Hi,
> > 
> > > Can we replace the header with the following one instead:
> > https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/incl
> > ude/jni.h <
> > https://github.com/openjdk/jdk/blob/master/src/java.base/share/native/incl
> > ude/jni.h> 
> > > It is more clearly GPLv2 w/ CPE, so it should be allowed, as my
> > > understanding is that it is an exception to category X.
> > 
> > AFAIK it is not. It is listed as Category X here [1].
> > 
> > Form memory there might some cases where GPL + CPE might be OK as a
> > dependancy but it’s not OK in a release. Probably best to discuss on legal
> > discuss list or raise a legal JIRA.
> > 
> > Kind Regards,
> > Justin
> > 
> > 1. https://www.apache.org/legal/resolved.html#category-x





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT] [IP CLEARANCE] Aether, renamed to Maven Artifact Resolver

[Hervé Boutemy]

there were a few questions answered, and a good number of +1

this vote passes

thank you for your review and votes

Regards,

Hervé

Le mercredi 28 septembre 2016 17:25:01 Hervé Boutemy a écrit :
> Apache Maven received a code donation for Aether, that we renamed to Maven
> Artifact Resolver to fix a trademark issue:
> 
> http://incubator.apache.org/ip-clearance/maven-aether.html
> 
> The import plan is more detailed at http://maven.apache.org/aether.html
> 
> Please vote to approve this contribution. Lazy consensus applies. If no -1
> votes are cast within the next 72 hours, the vote passes.
> 
> Regards,
> 
> Hervé


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [IP CLEARANCE] Aether, renamed to Maven Artifact Resolver

[Hervé BOUTEMY]

ok, got it:
it's about dependencies 
https://github.com/eclipse/aether-ant/blob/master/src/main/resources/about.html
not about source code

not an issue

Regards,

Hervé

Le vendredi 30 septembre 2016 10:23:12 Justin Mclean a écrit :
> Hi,
> 
> > AFAIK, the incoming ant repo is covered by the Sonatype software grant:
> > what precise 3rd party code are you concerned about?
> 
> From a quick look there BSD and code copyright  copyright various other
> people [1]
> 
> Copyright (c) 2000 The Apache Software Foundation.  All rights
> Copyright (c) 2001-2003, ThoughtWorks, Inc.
> Copyright (c) 2002 Extreme! Lab, Indiana University. All rights reserved.
> Copyright (c) 2004, The Codehaus
> Copyright (c) 2004-2008 QOS.ch
> 
> However it may just be these licenses refer to stuff that’s been removed,
> but I'm not sure?
> 
> All look to be permissive but they would be need to not be part of the grant
> and keep their original license and headers (assuming they exist that is).
> 
> Thanks,
> Justin
> 
> 1.
> https://github.com/eclipse/aether-ant/tree/master/src/main/resources/about_
> files -
> 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: [IP CLEARANCE] Aether, renamed to Maven Artifact Resolver

[Hervé BOUTEMY]

honestly, there is not plan for Sisu currently: Sisu is less Maven centric 
(even if I don't have clear view of how it is used outside Maven , but an IoC 
component is quite generic)

but for sure, never say never

Regards,

Hervé

Le mercredi 28 septembre 2016 17:38:59 Jochen Wiedmann a écrit :
> *Big* +1. Lets hope, that Sisu follows (sooner, or later). It feels
> *so* unnatural, to have this stuff at Eclipse.
> 
> On Wed, Sep 28, 2016 at 5:25 PM, Hervé Boutemy <hbout...@apache.org> wrote:
> > Apache Maven received a code donation for Aether, that we renamed to Maven
> > Artifact Resolver to fix a trademark issue:
> > 
> > http://incubator.apache.org/ip-clearance/maven-aether.html
> > 
> > The import plan is more detailed at http://maven.apache.org/aether.html
> > 
> > Please vote to approve this contribution. Lazy consensus applies. If no -1
> > votes are cast within the next 72 hours, the vote passes.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > -
> > 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: [IP CLEARANCE] Aether, renamed to Maven Artifact Resolver

[Hervé BOUTEMY]

yes, for sure, -1 until answered

AFAIK, the incoming ant repo is covered by the Sonatype software grant: what 
precise 3rd party code are you concerned about?

Regards,

Hervé

Le jeudi 29 septembre 2016 22:51:23 jus...@classsoftware.com a écrit :
> Hi,
> 
> Sorry but -1 (binding) until this is answered.
> 
> > I notice the ant repo contains other 3rd party code. I assume this is not
> > going to part of the software grant?
> Thanks,
> Justin
> -
> 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

[IP CLEARANCE] Aether, renamed to Maven Artifact Resolver

[Hervé Boutemy]

Apache Maven received a code donation for Aether, that we renamed to Maven 
Artifact Resolver to fix a trademark issue:

http://incubator.apache.org/ip-clearance/maven-aether.html

The import plan is more detailed at http://maven.apache.org/aether.html

Please vote to approve this contribution. Lazy consensus applies. If no -1
votes are cast within the next 72 hours, the vote passes.

Regards,

Hervé

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Retirement guide updates

[Hervé BOUTEMY]

(sorry, I'm a little late in the discussion...)
no, DOAP was not retired

I tried to makes things simpler in the documentation:
https://projects.apache.org/about.html

Regards,

Hervé

Le dimanche 31 janvier 2016 22:00:18 John D. Ament a écrit :
> I believe doap was retired in the projects-new setup.
> 
> On Jan 31, 2016 20:31, "Marvin Humphrey"  wrote:
> > Greets,
> > 
> > I'm mostly done overhauling[1] the Incubator's Retirement Guide.
> > 
> > http://incubator.apache.org/guides/retirement
> > 
> > There are a couple items left.
> > 
> > First, is the DOAP file.
> > 
> > *   If it is to be updated, how so?  If we use
> > 
> > http://attic.apache.org/process.html#doap as a template, how should
> > 
> > it be
> > 
> > adapted?
> > 
> > *   When a podling retires, we zap its website and redirect to the podling
> > 
> > status page.  If the DOAP file lived on the podling website, it's
> > going
> > away, too.  What do we do about that?
> > 
> > For volunteers who are executing the steps to retirement, figuring out
> > what to
> > do about the DOAP file is a time sink.  If we can't come up with concrete
> > steps that someone who knows nearly nothing about DOAP files can execute,
> > I
> > propose to delete that task -- otherwise, it's not fair to the volunteer
> > handling the often-thankless work of retirement.
> > 
> > Second, there's a task to remove the podling mailing lists from the
> > incubation
> > status page.  I don't think this is important and if there are no
> > objections,
> > I propose to remove that task.
> > 
> > Marvin Humphrey
> > 
> > [1]
> > http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/retirem
> > ent.xml
> > 
> > 
> > 
> > 
> > r1727881 | marvin | 2016-01-31 17:24:47 -0800 (Sun, 31 Jan 2016) | 2
> > 
> > lines
> > 
> > Add task to delete retiring podling dist dir.
> > 
> > 
> > 
> > r1727880 | marvin | 2016-01-31 17:18:13 -0800 (Sun, 31 Jan 2016) | 5
> > 
> > lines
> > 
> > Modify conceptual explanation of retirement.
> > 
> > Add analogy comparing podling retirement against retiring a TLP to the
> > Attic, plus other wordsmithing.
> > 
> > 
> > 
> > r1727875 | marvin | 2016-01-31 16:14:27 -0800 (Sun, 31 Jan 2016) | 2
> > 
> > lines
> > 
> > Add retirement step "Disable ${podling} website".
> > 
> > 
> > 
> > r1727874 | marvin | 2016-01-31 16:05:55 -0800 (Sun, 31 Jan 2016) | 6
> > 
> > lines
> > 
> > Rework "steps to retirement".
> > 
> > Group like tasks together.  Use a combination of numbered and bullet
> > lists, plus improve formatting in other ways.  Adapt for "version
> > control" rather than "SVN", as well as other vocabulary changes.
> > 
> > 
> > 
> > r1723936 | marvin | 2016-01-10 08:04:09 -0800 (Sun, 10 Jan 2016) | 8
> > 
> > lines
> > 
> > Streamline explanation of decision to retire.
> > 
> > Move the explanation of the decision to retire into its own dedicated
> > section.  Simplify this explanation considerably.
> > 
> > As a side effect, the remaining text under "What is retirement"
> > becomes
> > more succinct.
> > 
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Retirement guide updates

[Hervé BOUTEMY]

dropping the DOAP file of a retired incubator project means removing the 
project from projects list [1]: it seems reasonable

there is one task to do: remove the entry from projects DOAP files list [2]

notice that this step has to be done only when a project has previously made 
the effort to create a DOAP file: incubator projects usually didn't take time 
to 
create one (perhaps because documentation has been hard to follow until now: I 
hope we'll make the process easier to understand in the future then have more 
incubator DOAP files...  )

Regards,

Hervé

[1] https://projects.apache.org/projects.html

[2] 
http://svn.apache.org/viewvc/comdev/projects.apache.org/data/projects.xml?view=markup

Le jeudi 4 février 2016 20:51:28 Marvin Humphrey a écrit :
> On Sun, Jan 31, 2016 at 7:00 PM, John D. Ament  
wrote:
> > I believe doap was retired in the projects-new setup.
> 
> Since there have been no objections, I've made the following change:
> 
> 
> r1728601 | marvin | 2016-02-04 20:45:47 -0800 (Thu, 04 Feb 2016) | 6 lines
> 
> Update steps to retirement.
> 
> *   Remove DOAP task.
> *   Remove task to delete mailing list links from status page.
> *   Make website disabling self-service and clarify.
> 
> At this point, the Retirement Guide should be up-to-date.  A volunteer who
> is reasonably familiar with the Incubator should be able to follow the
> steps in it without too much difficulty.
> 
> Marvin Humphrey


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Groovy Incubation proposal

[Hervé Boutemy]

Hi,

We're scheduling the Jira migration for Maven projects on the week-end of 
4/5/6 april.
If this schedule is fine for Groovy, I suppose it would be ok to add Groovy 
Jira project to the actual list [1]
Just tell, and I'll avoid to remove Groovy from the full dump we'll have 
during the migration.

Regards,

Hervé

Notice: please CC me if necessary, since I'm not subscribed to 
general@incubator

[1] https://issues.apache.org/jira/browse/INFRA-9116

Le lundi 16 mars 2015 09:53:00 Stephen Connolly a écrit :
 Arg! hit send too soon.
 
 You should really check in with Hervé to confirm that Groovy was in the
 export. I am 99% confident that your issues and comments are in the XML
 dump, but you really should check with Hervé to be certain.
 
 Also you may want to ask Mark Thomas what exactly is involved in preparing
 and doing such an import. Our own timelines for Maven's switch may not
 align with the Groovy incubation timelines... (mind you we are all at the
 grace of Ben for getting our timeline for the second export he committed to
 the Maven project)
 
 On 16 March 2015 at 09:49, Stephen Connolly stephen.alan.conno...@gmail.com
  wrote:
  
  
  
  On 16 March 2015 at 09:19, Cédric Champeau cedric.champ...@gmail.com
  
  wrote:
  Thanks Stephen, sounds like a good news. For us the attachments do not
  matter much, there are not so many. However, keeping track of comments is
  very important, because some issues have a lot of discussions.
  
  2015-03-16 10:08 GMT+01:00 Stephen Connolly 
  stephen.alan.conno...@gmail.com
  
   On 16 March 2015 at 08:55, Jochen Theodorou blackd...@gmx.org wrote:
Am 16.03.2015 09:25, schrieb Upayavira:
When Stephen Connolly says ”We @ Maven will have a full dump of the
Codehaus JIRA and we have a VM set
up to test migration…” isn’t he implying that the Groovy issues are
*included* in that? I.e. there’s not so much for you to worry about
here?

Even if Stephen gets a full dump, this does not mean we will get the
Groovy part out of it. Ben was so far telling us he cannot give it
out
   
   like
   
that, because of private and internal data in there. Instead he
   
   suggested a
   
json export (which most likely will not contain everything)
   
   Well we are getting the full XML dump because that's all you can get
   via
   the XML dump, but whether we get *all* attachments or only those for
  
  Maven
  
   is a different question.
   
So unless Stephy has this clear with his employee I stand on the
part,
that we don't have that.
   
   Clarification: Ben and I are co-workers.
   
bye Jochen

--
Jochen blackdrag Theodorou - Groovy Project Tech Lead
blog: http://blackdragsview.blogspot.com/
german groovy discussion newsgroup: de.comp.lang.misc
For Groovy programming sources visit http://groovy-lang.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: [DISCUSS] Groovy Incubation proposal

[Hervé Boutemy]

yes, I dropped every project we didn't want to import since some of them had 
special configuration that were causing issues

The first dump we used contained everything

Regards,

Hervé

Le lundi 16 mars 2015 10:03:37 Stephen Connolly a écrit :
 On 16 March 2015 at 09:58, Mark Thomas ma...@apache.org wrote:
  On 16/03/2015 09:53, Stephen Connolly wrote:
   Arg! hit send too soon.
   
   You should really check in with Hervé to confirm that Groovy was in the
   export. I am 99% confident that your issues and comments are in the XML
   dump, but you really should check with Hervé to be certain.
   
   Also you may want to ask Mark Thomas what exactly is involved in
   preparing and doing such an import. Our own timelines for Maven's switch
   may not align with the Groovy incubation timelines... (mind you we are
   all at the grace of Ben for getting our timeline for the second export
   he committed to the Maven project)
  
  The latest test export I have does not have any Groovy data in it.
 
 I believe that is because Hervé is stripping out on the VM to handle the
 version skew.
 
 IOW as I understand it, Hervé has a full dump. Imports into Codehaus
 version of JIRA, upgrades JIRA, removes all the non-maven stuff, does some
 mapping and does an export for you.
 
  Mark
  
   On 16 March 2015 at 09:49, Stephen Connolly
   stephen.alan.conno...@gmail.com
   
   mailto:stephen.alan.conno...@gmail.com wrote:
   On 16 March 2015 at 09:19, Cédric Champeau
   cedric.champ...@gmail.com mailto:cedric.champ...@gmail.com
  
  wrote:
   Thanks Stephen, sounds like a good news. For us the attachments
   do not
   matter much, there are not so many. However, keeping track of
   comments is
   very important, because some issues have a lot of discussions.
   
   2015-03-16 10:08 GMT+01:00 Stephen Connolly
   stephen.alan.conno...@gmail.com
   mailto:stephen.alan.conno...@gmail.com
   
On 16 March 2015 at 08:55, Jochen Theodorou blackd...@gmx.org
   
   mailto:blackd...@gmx.org wrote:
 Am 16.03.2015 09:25, schrieb Upayavira:
 When Stephen Connolly says ”We @ Maven will have a full
   
   dump of the
   
 Codehaus JIRA and we have a VM set
 up to test migration…” isn’t he implying that the Groovy
   
   issues are
   
 *included* in that? I.e. there’s not so much for you to
   
   worry about
   
 here?
 
 Even if Stephen gets a full dump, this does not mean we will
   
   get the
   
 Groovy part out of it. Ben was so far telling us he cannot
   
   give it out
   
like

 that, because of private and internal data in there. Instead
  
  he
  
suggested a

 json export (which most likely will not contain everything)

Well we are getting the full XML dump because that's all you
   
   can get via
   
the XML dump, but whether we get *all* attachments or only
   
   those for Maven
   
is a different question.

 So unless Stephy has this clear with his employee I stand on
   
   the part,
   
 that we don't have that.

Clarification: Ben and I are co-workers.

 bye Jochen
 
 --
 Jochen blackdrag Theodorou - Groovy Project Tech Lead
 blog: http://blackdragsview.blogspot.com/
 german groovy discussion newsgroup: de.comp.lang.misc
 For Groovy programming sources visit http://groovy-lang.org
   
   -
   
 To unsubscribe, e-mail:
   general-unsubscr...@incubator.apache.org
   mailto:general-unsubscr...@incubator.apache.org
   
 For additional commands, e-mail:
   general-h...@incubator.apache.org
   mailto:general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org