Community Council/Council election May 2012/Candidate declarations

m (Fixing communication between the community, Council, Nokia, and Nemein.)
(Reformat)
Line 30: Line 30:
''Here we come to another thing - despite common opinions, Council doesn't have any "special tools". Really. The only difference from regular users that we have, is '''community mandate''' to talk with Nokia at Community behalf, and respect'n'trust - or lack of - from Community, that helps (or not, in second case) to coordinate projects, find solutions, settle small argues etc."''
''Here we come to another thing - despite common opinions, Council doesn't have any "special tools". Really. The only difference from regular users that we have, is '''community mandate''' to talk with Nokia at Community behalf, and respect'n'trust - or lack of - from Community, that helps (or not, in second case) to coordinate projects, find solutions, settle small argues etc."''
-
 
-
---
 
'''Roadmap''' I would like Community to take:
'''Roadmap''' I would like Community to take:
-
 
+
'''1st priority'''
-
====1st priority====
+
Fix issues with infrastructure maintainership. I would like to hear '''Nokia''' position here - if cooperation between people maintaining infrastructure and Council is going to be so unsatisfying, is Nokia going to accept community will of changing infrastructure tech staff? IMO, problem of "hands tied" (Nokia paying bills, yet not demanding real work in return, Council not paying bills, so tech staff having Council in... '''*deep*''' respect, as history shows) is first hot potato to take care of.
Fix issues with infrastructure maintainership. I would like to hear '''Nokia''' position here - if cooperation between people maintaining infrastructure and Council is going to be so unsatisfying, is Nokia going to accept community will of changing infrastructure tech staff? IMO, problem of "hands tied" (Nokia paying bills, yet not demanding real work in return, Council not paying bills, so tech staff having Council in... '''*deep*''' respect, as history shows) is first hot potato to take care of.
-
====2nd priority====
+
'''2nd priority'''
Determining, if cooperation with Nokia (overall, including tech staff payed by Nokia) is to Community benefit or not, in long term. This is going to be open question, answered again and again, as time passes and situation change.
Determining, if cooperation with Nokia (overall, including tech staff payed by Nokia) is to Community benefit or not, in long term. This is going to be open question, answered again and again, as time passes and situation change.
 +
''Variant '''a''' - positive effects of cooperation with Nokia''
-
---
+
'''3.a'''
-
Variant '''a''' - positive effects of cooperation with Nokia
+
-
---
+
-
 
+
-
 
+
-
====3.a====
+
Keeping to make infrastructure better and better for developers, overcoming existing problems with infrastructure maintainer's help.
Keeping to make infrastructure better and better for developers, overcoming existing problems with infrastructure maintainer's help.
-
====4.a (same for both both Nokia-cooperation scenarios)====
+
'''4.a (same for both both Nokia-cooperation scenarios)'''
Clarification of confusing statement from '''Nokia''' about community governance. '''SD69''' was asking this via e-letters, quoting previous statements, and statements made my '''marias''' (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from '''Nokia''' up to date.
Clarification of confusing statement from '''Nokia''' about community governance. '''SD69''' was asking this via e-letters, quoting previous statements, and statements made my '''marias''' (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from '''Nokia''' up to date.
Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.
Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.
-
====5.a (same for both Nokia-cooperation scenarios)====
+
'''5.a (same for both Nokia-cooperation scenarios)'''
Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing '''own, independent device''' (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.
Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing '''own, independent device''' (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.
 +
''Variant '''b''' -  non-satisfying results of cooperation with Nokia''
-
---
+
'''3.b'''
-
Variant '''b''' -  non-satisfying results of cooperation with Nokia
+
-
---
+
-
 
+
-
 
+
-
====3.b====
+
Getting info about current resources used by '''Maemo ifnrastructure'''. Sounds trivial, yet, when '''SD69''' asked it, '''Nokia's representative''' wasn't able to give more precise answers than "I have no idea".
Getting info about current resources used by '''Maemo ifnrastructure'''. Sounds trivial, yet, when '''SD69''' asked it, '''Nokia's representative''' wasn't able to give more precise answers than "I have no idea".
-
====4.b (same for both both Nokia-cooperation scenarios)====
+
'''4.b (same for both both Nokia-cooperation scenarios)'''
Clarification of confusing statement from '''Nokia''' about community governance. '''SD69''' was asking this via e-letters, quoting previous statements, and statements made my '''marias''' (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from '''Nokia''' up to date.
Clarification of confusing statement from '''Nokia''' about community governance. '''SD69''' was asking this via e-letters, quoting previous statements, and statements made my '''marias''' (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from '''Nokia''' up to date.
Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.
Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.
-
====5.b====
+
'''5.b'''
Steady preparing infrastructure migration, solving issues of creating legal entity (foundation), dropping trademarks, etc. At the same time, negotiating with Nokia about lifetime of closed source binary repositories (PR's, and so goes on), and possibility to allow us redistributing it (still in closed way), when Nokia decide to shut down Fremantle repos.
Steady preparing infrastructure migration, solving issues of creating legal entity (foundation), dropping trademarks, etc. At the same time, negotiating with Nokia about lifetime of closed source binary repositories (PR's, and so goes on), and possibility to allow us redistributing it (still in closed way), when Nokia decide to shut down Fremantle repos.
-
====6.b (same for both Nokia-cooperation scenarios)====
+
'''6.b (same for both Nokia-cooperation scenarios)'''
Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing '''own, independent device''' (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.
Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing '''own, independent device''' (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.
-
 
-
---
 
I think I doesn't need to add, that variant '''"a"''' fit's my liking much more, but in my opinion, it's council responsibility to be prepared for both scenarios.
I think I doesn't need to add, that variant '''"a"''' fit's my liking much more, but in my opinion, it's council responsibility to be prepared for both scenarios.
Line 98: Line 85:
Nomination made on the [https://lists.maemo.org/mailman/listinfo/maemo-community/ maemo-community mailing list] at http://lists.maemo.org/pipermail/maemo-community/2012-April/005063.html
Nomination made on the [https://lists.maemo.org/mailman/listinfo/maemo-community/ maemo-community mailing list] at http://lists.maemo.org/pipermail/maemo-community/2012-April/005063.html
-
==== Statement on my priorities as a Council member ====
+
'''Statement on my priorities as a Council member'''
As an active Council member, my primary focus would be on communications and clarity, both in documenting/echoing what the community desires are to be sure we as Council understand issues in the community, and with infrastructure support (Nokia/Nemein).  My primary concern would be to see that Maemo.com continues and that the infrastructure we enjoy is both preserved and maintained in a way that promotes continued development and growth in all project spaces.
As an active Council member, my primary focus would be on communications and clarity, both in documenting/echoing what the community desires are to be sure we as Council understand issues in the community, and with infrastructure support (Nokia/Nemein).  My primary concern would be to see that Maemo.com continues and that the infrastructure we enjoy is both preserved and maintained in a way that promotes continued development and growth in all project spaces.
-
<span style="text-decoration: underline;">Replies to questions posed</span>
+
''Replies to questions posed''
-
 
+
'''Thoughts on integrating Harmattan / Meltemi'''
-
 
+
-
===== Thoughts on integrating Harmattan / Meltemi =====
+
Personally, I feel Harmattan users should be welcomed in the Maemo community, since in large part they can and often do identify as being part of the Maemo family.  The N9/N950 discussion areas show a good deal of activity, and for the most part many are already well integrated.  I would work toward finding a way to integrate the Harmattan community, and creating a stable home for that group here at Maemo.com.
Personally, I feel Harmattan users should be welcomed in the Maemo community, since in large part they can and often do identify as being part of the Maemo family.  The N9/N950 discussion areas show a good deal of activity, and for the most part many are already well integrated.  I would work toward finding a way to integrate the Harmattan community, and creating a stable home for that group here at Maemo.com.
Line 112: Line 97:
In short, I do foresee the possibility of other groups merging into the Maemo family over time, even those that may not have had a direct relational tie to Maemo. (OpenMoko for example, would be a reasonable fit.) But both communities would have to have a ''desire'' to be together in order for it to work, and subsequently to see support on my part for a merging.
In short, I do foresee the possibility of other groups merging into the Maemo family over time, even those that may not have had a direct relational tie to Maemo. (OpenMoko for example, would be a reasonable fit.) But both communities would have to have a ''desire'' to be together in order for it to work, and subsequently to see support on my part for a merging.
-
===== Fixing communication between the community, Council, Nokia, and Nemein. =====
+
'''Fixing communication between the community, Council, Nokia, and Nemein'''
While I do feel there's been a breakdown of communication over the past term or two, I'm not sure it's clear that any one party in particular was to blame.  The view I've had leads me to believe that there were several factors in the breakdown, which are reasonably fixed with the following steps (now that there seems to be a rather clear focus from all parties because of elections):
While I do feel there's been a breakdown of communication over the past term or two, I'm not sure it's clear that any one party in particular was to blame.  The view I've had leads me to believe that there were several factors in the breakdown, which are reasonably fixed with the following steps (now that there seems to be a rather clear focus from all parties because of elections):
Line 124: Line 109:
Finally, we need to get a solid commitment on level of effort from each group involved.  We need to revisit that regularly, get feedback on effort required for each item in the work queue for each group, and establish priorities on those items.  I don't think this needs to be a huge undertaking, but currently there's nothing in place to indicate what items are priority, and how much work is involved for any specific item to bring it to fruition.  I feel that working out those two key bits of information may save lots of effort and frustration on all sides over the next several cycles.
Finally, we need to get a solid commitment on level of effort from each group involved.  We need to revisit that regularly, get feedback on effort required for each item in the work queue for each group, and establish priorities on those items.  I don't think this needs to be a huge undertaking, but currently there's nothing in place to indicate what items are priority, and how much work is involved for any specific item to bring it to fruition.  I feel that working out those two key bits of information may save lots of effort and frustration on all sides over the next several cycles.
-
===== On lack of future hardware and Open mobility =====
+
'''On lack of future hardware and Open mobility'''
While I like the question as posed, I'm not clear that Council has the position or right to determine any of these paths for the community.  The community at large should be responsible for choosing this direction.  In some regards I see the answer to question one being reflective of this, since without new projects joining our family, there will be a fall-off over time.  While I'm excited that some other communities I follow (like OpenMoko) have taken steps to renew their momentum with community hardware projects, I'm not sure it's as feasible for the Council to chose of invoke that here without direct prompting by the community.  That said, I would be quite happy to see such efforts, and would be happy to facilitate both support and integration into the community at a social and technological level where feasible.
While I like the question as posed, I'm not clear that Council has the position or right to determine any of these paths for the community.  The community at large should be responsible for choosing this direction.  In some regards I see the answer to question one being reflective of this, since without new projects joining our family, there will be a fall-off over time.  While I'm excited that some other communities I follow (like OpenMoko) have taken steps to renew their momentum with community hardware projects, I'm not sure it's as feasible for the Council to chose of invoke that here without direct prompting by the community.  That said, I would be quite happy to see such efforts, and would be happy to facilitate both support and integration into the community at a social and technological level where feasible.
Line 133: Line 118:
'''1.''' What are your thoughts on integrating Harmattan and potentially even
'''1.''' What are your thoughts on integrating Harmattan and potentially even
-
Meltemi into the Maemo community and maemo.org? [http://lists.maemo.org/pipermail/maemo-community/2012-April/005055.html]
+
Meltemi/other-open-Qt+Linux Nokia/other manufacturer devices into the Maemo community and maemo.org? [http://lists.maemo.org/pipermail/maemo-community/2012-April/005055.html]
-
'''2.''' What are your thoughts on how communications should be conducted between Nokia, Nemein and the council; and the council and the community?
+
'''2.''' There is [http://talk.maemo.org/showthread.php?p=1187362#post1187362 a thread on TMO] highlighting some of the problems the current council has had. Do you agree with the assertions in that thread that there's been a breakdown in communication between Nokia, Nemein and the council; and the council and the community? If so, how do we fix it?[http://lists.maemo.org/pipermail/maemo-community/2012-April/005044.html]
'''3.'''
'''3.'''

Revision as of 15:03, 9 April 2012

Contents

Candidates for May 2012 Maemo Community Council elections

The following candidates intend to stand for election to the Maemo Community Council.

  1. Iván Gálvez Junquera / ivgalvez
  2. Piotr Jawidzyk / Estel
  3. Joseph Charpak / jcharpak
  4. Craig Woodward / woody14619


Candidate declarations

Iván Gálvez Junquera

Nomination made on the maemo-community mailing list at http://lists.maemo.org/pipermail/maemo-community/2012-April/005043.html

"I volunteer to the Concil for this next year. I'm pretty sure I won't have too much spare time but I can promise I won't leave without notice or move to any other platform in the years to come."


Piotr Jawidzyk

Nomination made on the maemo-community mailing list at http://lists.maemo.org/pipermail/maemo-community/2012-April/005019.html

"As for myself, I would like to try my best @ helping to organize infrastructure governed by community, without Nokia's roadblocks. Don't get me wrong - despite my personal opinion about our "Nokia friends", I don't plan to go into "war" with them. I realize, that "friendly divorce" is much better for both parties, and would like to negotiate best terms of it.

Here we come to another thing - despite common opinions, Council doesn't have any "special tools". Really. The only difference from regular users that we have, is community mandate to talk with Nokia at Community behalf, and respect'n'trust - or lack of - from Community, that helps (or not, in second case) to coordinate projects, find solutions, settle small argues etc."


Roadmap I would like Community to take:

1st priority Fix issues with infrastructure maintainership. I would like to hear Nokia position here - if cooperation between people maintaining infrastructure and Council is going to be so unsatisfying, is Nokia going to accept community will of changing infrastructure tech staff? IMO, problem of "hands tied" (Nokia paying bills, yet not demanding real work in return, Council not paying bills, so tech staff having Council in... *deep* respect, as history shows) is first hot potato to take care of.

2nd priority Determining, if cooperation with Nokia (overall, including tech staff payed by Nokia) is to Community benefit or not, in long term. This is going to be open question, answered again and again, as time passes and situation change.

Variant a - positive effects of cooperation with Nokia

3.a Keeping to make infrastructure better and better for developers, overcoming existing problems with infrastructure maintainer's help.

4.a (same for both both Nokia-cooperation scenarios) Clarification of confusing statement from Nokia about community governance. SD69 was asking this via e-letters, quoting previous statements, and statements made my marias (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from Nokia up to date.

Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.

5.a (same for both Nokia-cooperation scenarios) Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing own, independent device (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.

Variant b - non-satisfying results of cooperation with Nokia

3.b Getting info about current resources used by Maemo ifnrastructure. Sounds trivial, yet, when SD69 asked it, Nokia's representative wasn't able to give more precise answers than "I have no idea".

4.b (same for both both Nokia-cooperation scenarios) Clarification of confusing statement from Nokia about community governance. SD69 was asking this via e-letters, quoting previous statements, and statements made my marias (Nokia representative) during last meeting with Council - results were totally opposite. He haven't got any answer from Nokia up to date.

Overall, I think that passing maintainership to Community - like it happened with QT - is most profitable scenario to both parties. Would like to negotiate that with Nokia.

5.b Steady preparing infrastructure migration, solving issues of creating legal entity (foundation), dropping trademarks, etc. At the same time, negotiating with Nokia about lifetime of closed source binary repositories (PR's, and so goes on), and possibility to allow us redistributing it (still in closed way), when Nokia decide to shut down Fremantle repos.

6.b (same for both Nokia-cooperation scenarios) Working with other platform's teams - both hardware'ish and software'ish (Mer, Vivaldi, Spark, Raspberry Pi, to name a few) - to share their experiences and knowledge. Preparing plans for fund-raising and developing own, independent device (hardware), powered by OS of our choice. If desirable by Community, transforming Maemo Community to self-governed, independent entity (foundation). Last one would require a referendum, obviously.

I think I doesn't need to add, that variant "a" fit's my liking much more, but in my opinion, it's council responsibility to be prepared for both scenarios.


Joseph Charpak

Nomination made on the maemo-community mailing list at http://lists.maemo.org/pipermail/maemo-community/2012-April/005051.html

"I've been a maemo user from the N800 days, although I actually started with the 770 when it dropped in price due to the release of the N800.. I've been an avid follower of TMO since its ITT days. As a council member I would strive for more transparency in council actions. As a starting point I would ensure that announcements would be made weekly through the council blog, with a new post to the ask a council thread on TMO as well."


Craig Woodward

Nomination made on the maemo-community mailing list at http://lists.maemo.org/pipermail/maemo-community/2012-April/005063.html

Statement on my priorities as a Council member As an active Council member, my primary focus would be on communications and clarity, both in documenting/echoing what the community desires are to be sure we as Council understand issues in the community, and with infrastructure support (Nokia/Nemein). My primary concern would be to see that Maemo.com continues and that the infrastructure we enjoy is both preserved and maintained in a way that promotes continued development and growth in all project spaces.

Replies to questions posed Thoughts on integrating Harmattan / Meltemi

Personally, I feel Harmattan users should be welcomed in the Maemo community, since in large part they can and often do identify as being part of the Maemo family. The N9/N950 discussion areas show a good deal of activity, and for the most part many are already well integrated. I would work toward finding a way to integrate the Harmattan community, and creating a stable home for that group here at Maemo.com.

As for other projects (Meltemi and more), I would say that has to depend on the group and how they are perceived, both by the community here and within their own community (if any). Without knowing the structure and makeup of both core elements of the platform and/or it's target community, that question is impossible to answer.

In short, I do foresee the possibility of other groups merging into the Maemo family over time, even those that may not have had a direct relational tie to Maemo. (OpenMoko for example, would be a reasonable fit.) But both communities would have to have a desire to be together in order for it to work, and subsequently to see support on my part for a merging.

Fixing communication between the community, Council, Nokia, and Nemein

While I do feel there's been a breakdown of communication over the past term or two, I'm not sure it's clear that any one party in particular was to blame. The view I've had leads me to believe that there were several factors in the breakdown, which are reasonably fixed with the following steps (now that there seems to be a rather clear focus from all parties because of elections):

First, we need to verify and record the proper channel used to communicate between parties, ad preferably at least 2 back-up channels per contact. Be that e-mail, IRC, a bug-tack system, pager number, etc. Those should be documented somewhere accessible to all Council members and contact points at Nokia and Nemein.

Second, we need to have in place a standard location where Council will post all communications (or attempts at communicating) at least in summary. This should include not just meeting minutes but external communications as well, including summaries of issues raised by the community, and summaries of any communications or issues raised with or from Nokia/Nemein. This will facilitate transparency for all groups involved, and allow for a single place where all parties can verify they're on the same page.

Third, we need to re-establish some form of regularity to the communications between the groups. Be that a quick 10 minute meeting once a month, or a semi-weekly e-mail ping just to make sure everyone is still in the loop. On-demand contact is great, but I feel that having a formal schedule, even if only a few times a term, will help prevent a total dropping of the ball by any group involved. I'd rather have an issue sit in a bin for a week before someone sees it and picks it up than to see one request get answered in a day and a follow-up sit for 3 months for lack of a regular check-in.

Finally, we need to get a solid commitment on level of effort from each group involved. We need to revisit that regularly, get feedback on effort required for each item in the work queue for each group, and establish priorities on those items. I don't think this needs to be a huge undertaking, but currently there's nothing in place to indicate what items are priority, and how much work is involved for any specific item to bring it to fruition. I feel that working out those two key bits of information may save lots of effort and frustration on all sides over the next several cycles.

On lack of future hardware and Open mobility

While I like the question as posed, I'm not clear that Council has the position or right to determine any of these paths for the community. The community at large should be responsible for choosing this direction. In some regards I see the answer to question one being reflective of this, since without new projects joining our family, there will be a fall-off over time. While I'm excited that some other communities I follow (like OpenMoko) have taken steps to renew their momentum with community hardware projects, I'm not sure it's as feasible for the Council to chose of invoke that here without direct prompting by the community. That said, I would be quite happy to see such efforts, and would be happy to facilitate both support and integration into the community at a social and technological level where feasible.

Questions candidates might like to answer

The following questions have been asked of candidates, feel free to add to them.

1. What are your thoughts on integrating Harmattan and potentially even Meltemi/other-open-Qt+Linux Nokia/other manufacturer devices into the Maemo community and maemo.org? [1]

2. There is a thread on TMO highlighting some of the problems the current council has had. Do you agree with the assertions in that thread that there's been a breakdown in communication between Nokia, Nemein and the council; and the council and the community? If so, how do we fix it?[2]

3. Do You agree, that lack of devices (hardware) is one of major roadblocks for Open mobility we would like to have? If yes, which way should Council focus on supporting:

a) Cooperation with big companies (Nokia?), hoping that they'll finally release "device of our dreams" (or thing close to)?

b) Starting hard, demanding and somewhat costly (without guarantee of success) path of creating own device via donations, which - if succeed - may result in totally, or almost totally open device (way of Open Pandora, Raspberry Pi, etc)?