Introducing the licensing change requests queue
 

I hereby declare the licensing change requests queue open, as proposed in this post:

http://wiki.maemo.org/Open_developme...hange_requests

Feel free to submit yours, follow procedure, and let's see where this leads :)

My hope is that it will lead to more constructive discussion and more openness of the Maemo OS. There are some existing proposals open already, that I will be evaluating over the next couple of days in order to prioritize them.

Re: Introducing the licensing change requests queue
 

Where existing license could be read?
Does it disallow use of these binaries on n900 in way other than official? or disallow distributing? or what?

How I hate all that licensing nonsense... :( :( :(

Re: Introducing the licensing change requests queue
 

General split is:

open source (you can find src in sdk, gitorious, etc), non-free, nokia-binaries (probably not free for anything but sdk usage or development). If you want to use anything not oss, you need to see if a solution can be worked out.

Re: Introducing the licensing change requests queue
 

Previously, people were told to make license change proposals in Brainstorm:
http://wiki.maemo.org/Open_developme...losed_packages
but it seems that the queue is already populated with those that were filed as bugs. It is nice that the legwork was done to include them, but the queue just opened, and the proposals filed as bugs are listed with preexisting votes. One has 52 votes and it must have taken awhile to accumulate that many votes.

I suggest that voting should be restarted or at least that preexisting votes should not be the dominant factor in determining which requests get put at the top of the queue.

And if a request is improper, will the requester be contacted to inform him or her of that so they know to correct the request?

Re: Introducing the licensing change requests queue
 

Yes, previous requests that were still open was included - I will be converting them to have proper request info and then we'll see. Some can probably be dismissed out of hand since existing discussion has indicated it won't happen. The important thing is getting requests in and getting a process going.

Regarding improper, yes, through bugzilla notification and ability to correct it.

Re: Introducing the licensing change requests queue
 

A small update: The current listing of the queue isn't doing my bidding very well. I'll be looking at how to present it better.

Re: Introducing the licensing change requests queue
 

OK, one thing now appears. The queue has changed in the last week. Is there a way to tell what happened? Did items get dropped? Did they get passed on? etc.

Re: Introducing the licensing change requests queue
 

Right. All this is available as information in bugzilla - people CC'ed on the bugs get told what happens when it does

3195 accidentially got marked ASSIGNED by me - I am waiting for GeneralAntilles to fill in the form as I can't be objective if I am making the forms myself

9138 (HildonFancyButton, new - going quite well IMHO), 4520 (old), 4560 (old) is being considered in an internal bug

1235 got marked WONTFIX, the media player opening bug:

"I have tried, but at this point the best is to resolve as WONTFIX.

The Fremantle Media Player won't be opened."

7811 WONTFIX, - Calendar:

"The Fremantle Calendar application won't be opened. Note that the Calendar
backend component in the platform is open source."

5549 (libosso-abook) is waiting for a statement on Quim on the progress of this one

7019 (getbootstate) got evaluated by me and now waits in line with a priority HIGH.

and the first success (FIXED) with a clear statement for CSSU:

9145 - Permission to modify and redistribute "OS2008 Feature upgrade" metapackages

All this info is available through the links on http://wiki.maemo.org/Open_developme...hange_requests

Re: Introducing the licensing change requests queue
 

Woot! Good news! Bug 9145:

Re: Introducing the licensing change requests queue
 

So the good news is that Nokia allow you to distribute something that you don't need their permissions in order to distribute.