![]() |
Re: Ask the Council!
Also, there seems to be a bit of confusion about who can access and who can fix the packages interface - http://maemo.org/packages . Again, you don't need to wait for a Council to help on that.
http://trac.midgard-project.org/brow...maemo.packages + find + fix + diff + patch... Old open development process applies. |
Re: Ask the Council!
Quote:
/Estel |
Re: Ask the Council!
Quote:
|
Re: Ask the Council!
Quote:
So I'd say the council's big thing for the near future is to keep itself relevant by communication, helping projects (not by writing code or fixing their bugs) and making sure that the community is a good place to be in whether one works on a small or big community project, is just an end-user or whatnot. These are things that anyone interested in the community's welfare can and should help with. This includes making sure that we don't end up in a situation like this anymore (QA and project problems). I'd argue that the current technical problems can be resolved before the next election. One doesn't need to be in the council to participate in the discussions and offer proposals to how to get things on the roll again. |
Re: Ask the Council!
Quote:
|
Re: Ask the Council!
Quote:
Sorry, I'm not buying that. Trying to arbitrary reduce Council from Community representatives to "walking telegrams" is just pushing Communtiy further into forking ideas. Unless I misunderstood what You're trying to say. In my opinion, state of Council being relevant or not depends totally on Community support for it. If Community will be willing to take path, that Council is supporting, yet don't have (legal) right in current state, Maemo Community will just fork itself, into organization with steering group or whatsnot. Similarly, Council can have upperpowa rights granted, yet, without Community accepting and following way the Council is doing job, there won't be any effect on Community. --- For me, referendum is great tool to have, that should be used in case of important and path-forming decisions. No one have right to tell Community "no, voting what you'll do isn't Your right". Of course, tools (like voting process) need someone to manage it, and who should do it if not Council? /Estel |
Re: Ask the Council!
fwiw I was trying to remind about the original purpose of the Council, not trying to deviate it out of somewhere.
In any case referendums only work after extensive discussions not leading to consensus in the first place. So the first question is: what power are you missing for the Council? |
Re: Ask the Council!
Quote:
Quote:
or is it? :confused: anyway, i think the problem here is less technical (promoting stable packages from -devel or even -testing to extras or fixing packages which are not) then organizational i.e. checking which packages are actually orphaned (in whichever way) and communicating with Niels (or any other person able to change ownership if owner is not available anymore) obviously, someone has to pick it up, but expecting individual developers to do that and getting anywhere is either disillusioned or complete naive :( |
Re: Ask the Council!
Quote:
did it ever occur to you that Maemo is not -- repeat not -- a free software, but a (pseudo-)commercial project of a company? they simply do not want to release it. if the community supports it, no matter how messy and disorganized it is, fine. otherwise... feel free to leave. i'm not telling you to leave, but NOKIA is not going to let go of Maemo. if you don't like this idea and would rather create a FOSS project, you will either have to start more or less from scratch or indeed cause a scission of the community along the line of what happened with Symbian... ppl are becoming unsure of the future and decide to leave it, no matter how good the latest iterations / efforts are |
Re: Ask the Council!
Quote:
http://talk.maemo.org/showpost.php?p...&postcount=784 For now, I'm not missing any power for Council - I'm rather trying to figure out, what exactly Council can do (or not) from "formal" point of view. I.E. who is entitled to create referendum, if not Council? After all, one of initial Council responsibilities, was to present Community ("azimuth") stance to Nokia, and to talk/negotiate about main Community concerns, that might be addressed by Nokia (often working in collaboration with Council or certain individualities). This may seems less relevant now - unfortunately - due to limited resources Nokia is wanting to invest in Maemo Community - no one blames You here, it's just a fact. Yet, to effectively use resources that we have - to Community best interest - it's important to have Council as true Community representatives, i.e. people that know about most important/potent projects going on in the community, issues found there, etc. This way, developers time isn't wasted and they can actually write the code, while having people that they trust speaking on their behalf about infrastructure, roadblocks etc. At least, this is how it looks from my point of view. So, "project Council" is ok, but with much higher doze of "representatives". Do not confuse with "politics" ;) /Estel |
| All times are GMT. The time now is 22:16. |
vBulletin® Version 3.8.8