Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

According to their website the fee provides free updates for the same version. If they support past versions well there shouldn't be a compelling reason to upgrade.

Then again the latest 3.8 (tmo claims to be 3.8.2 in the footer) is 3.8.7, released just over 16 months ago according to wikipedia, which that doesn't look too good support-wise.

Agreed, both for philosophical and practical reasons.

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

there have been a number of brilliant inventions before the N900 or even Maemo.
not all as poorly managed, but still, eventually relegated to the care of (sweet) memories.
the N900 is one of a kind right now, but acting like it is the last thing humanity would ever have needed (when hardly anyone even knows about it) is somewhat over dramatizing.

what's really worrisome is that a member of Council could take (seriously?) part in such a discussion :(

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

i guess this topic will be discussed on next meeting ? When ?

Let me suggest to add a plan to backup the wiki and release a such archive ? are there some legal issues ?

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

For those not on the Community mailing list, a Draft Bylaws for "Maemo Non-Profit Entity" document has been posted. The accompanying email can be found here:
http://lists.maemo.org/pipermail/mae...ly/005552.html

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

Kate,

do you (or anyone else?) have access to the downloads volumes of the repositories?
TMO is cute & all, but... the community could survive without it or with a skinned down version (IRC and mailing-list)
the repositories are the meat of the matter, so to speak.

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

Don't know if this is the best place to put this but, could Jolla takeover Maemo.org from Nokia?

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

Absolutely not.

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

On a note sent to us by Quim Gil, he has confirmed that we could use maemo.org domain for future community site:

"Nokia is happy to transfer the maemo.org domain to an organization entitled to receive it. I just got the confirmation today. Now it’s up to you to decide who / when."

This is great news as it will ease the transition to self sustained infrastructure.

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

It's absolutely great news, then!

So, when we can expect referendum? I think such huge change require one.

One could say, that everyone is free to continue Maemo legacy without referendum - and that is true. Hoever, such person/group would never receive official Maemo "things", like maemo.org domain, forum database, etc. I feel, that it belongs to Community, so community (and Nokia, speaking through qgil, seems to agree) should be able to vote about agreeing to bylaws (as proposed by Council), and overall structure of foundation. After all, the latter is is going to receive things belonging to community (domain, databases, etc).

Especially, that there are few controversial things considering bylaws - like 1-year cadence of Board, and way of managing finances.

/Estel

Re: Migrating to Community-driven Infrastructure - Step 1: Inventory
 

I'm sharing the spreadsheet I'm using to keep track of applications ready for promotion, the status and whose developers I've contacted with.

As previously agreed, all applications with enough votes and free of suspicious issues that are unmaintained will be auto-promoted. However we will need someone to do the promotion and, as you already know, our maintenance muscle is right now almost non existent.

In order to start the migration to self sustained infrastructure process, the Council contacted with X-Fade a few weeks ago, trying to obtain some administrative rights over current infrastructure. This way we would be able to improve our current maintenance status and start gathering a working group for administration tasks.

He agreed to grant the administrative rights to the repository web interface to merlin1991, as a first step in the handover process. Now we are just waiting him to actually give merlin1991 that permission so he could start doing some maintenance tasks on Fremantle repositories.

Once we have at least one administrator we could start tasks like this one for promotion of packages.