When can we expect the packages license change?

[Sven Versteegen]

Is there a timeframe for the change? It was more then a year ago since this was approved and I really think it's time to do this.

[Andrew Eddie]

+1

Can we just decide how to do this and just do it please. It's only a couple dozen PR's. 

My vote, since this has dragged on for far, far too long is just bump the minor version on all the packages and relicense.

Regards,

Andrew Eddie

[Sven Versteegen]

My vote, since this has dragged on for far, far too long is just bump the minor version on all the packages and relicense.

+1

Should we also do PRs against the 2.0-dev branches or just master branch?
I just did a PR to the authentication package to both branches, since the LICENSE file there is already LGPL, but I'm not on my Laptop and don't have git on it and using the webfrontend is a pita...

[Michael Babker]

The original intent was to do the license change with the 2.0 package releases and this was reaffirmed with the roadmap post earlier this year.  I'd personally suggest it stays that way unless someone with more decision power than me mandates otherwise.

--
Framework source code: https://github.com/joomla-framework
Visit http://developer.joomla.org for more information about developing with Joomla!
---
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-frame...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-framework.

[Sven Versteegen]

The original intent was to do the license change with the 2.0 package releases and this was reaffirmed with the roadmap post earlier this year.

Ok, so we do the PRs to the 2.0-dev branch then...

Since that roadmap is nearly 5 month old, is there a list of things that need to be done to get v2 out, because waiting another year for this to happen isn't really an option I would say.

@Michael What is with the packages in your "Keep or Dump" post, that thread drifted completely away from your initial post, I would vote to deprecate them all (including the ones you marked as questionable), but like Andrew wrote they should get a relicense too.

[Michael Babker]

For the social packages, if we're going to bump the license and do another major release, I would suggest that they be brought up-to-date with their parent APIs as needed and not just tag and bag it.  My concern with keeping them is a lack of maintenance since they were merged; they've received very little attention in the time since then and I'm not sure if they all work with their corresponding APIs still (or if they are lacking features, etc.).  For the ones I flagged as questionable you could argue one way or another that they're either feature incomplete or don't really fit the Joomla structure (like the Data package, well intended and I can see potential uses for it, but it's just unused in the core software and has next to no use in the PHP community (https://packagist.org/packages/joomla/data/stats)).

On Wed, Jul 1, 2015 at 11:45 AM, Sven Versteegen <redey...@gmail.com> wrote:

The original intent was to do the license change with the 2.0 package releases and this was reaffirmed with the roadmap post earlier this year.

Ok, so we do the PRs to the 2.0-dev branch then...

Since that roadmap is nearly 5 month old, is there a list of things that need to be done to get v2 out, because waiting another year for this to happen isn't really an option I would say.

@Michael What is with the packages in your "Keep or Dump" post, that thread drifted completely away from your initial post, I would vote to deprecate them all (including the ones you marked as questionable), but like Andrew wrote they should get a relicense too.

On Wednesday, 1 July 2015 17:04:50 UTC+2, Michael Babker wrote:

The original intent was to do the license change with the 2.0 package releases and this was reaffirmed with the roadmap post earlier this year.  I'd personally suggest it stays that way unless someone with more decision power than me mandates otherwise.

--