Originally Posted by CommunityCouncil

Meeting held 2015-12-01 on FreeNode, channel #maemo-meeting (logs)

Attending: Peter Leinchen (peterleinchen), Halit Bal (HtheB), Gido Griese (Win7Mac), Jussi Ohenoja (juiceme)

Partial: Bernardo Reino (reinob)

Absent:

Summary of topics (ordered by discussion):

• Discussing handling of ex-members accounts
• Automatic calculation of election results
• Finalizing the rules for the coding competition

(Topic Discussing handling of ex-members accounts):

• Discussion about ex-users that still receive maermo mails; It seems that in some cases even when an user removes his account or requests removal from techstaff something might still remain active; for example mail bouncer might send something, or election machine might still dig up the mail account when automailing to members.
• At least one case was solved by Techstaff; it was found out that the user still was listed as a project admin in a mailing list of one of his old projects.

(Topic Automatic calculation of election results):

• The Council discussed the state of the Maemo voting system, what are the pros and cons of it.
• The only problem currently is that the automatic calculation of the votes does not work, and it requires that the resulting list of votes is run manually through OpenSTV after the election closes and results are posted to the voting page.
• Juiceme was not absolutely sure that it had ever worked correctly and had to check it from Woody; the answer is that it did work correctly sometime in the past.
• Possibly a system update has at some point of time changed paths that the calculation script uses, hence breaking it.
• HtheB raised again the point that we have 2 different user-base systems, "TMO users" != "Maemo users" which is a major disadvantage. Only people with Maemo account are allowed to vote on community matters, and there probably are many TMO users who do not even know that...
• User base harmonization has been discussed before and it is very difficult to do and possibly disastrous. However there are reasons why it should be done. If the pressure to do it is strong enough we need to do something about it, so it should be studied further.
• What should be done, is to try to get everybody on TMO to join MO. Maybe mass-posting or automatic notice message on TMO.

(Topic Finalizing the rules for the coding competition):

• It has been decided that the competition categories are based on devices rather than types-of-apps.
• Prize devices need to be collected by asking donations on TMO.
• Categorizing the prizes; it needs to be ensured that "right devices match the right developers", so that the winners get what they need and deserve.
• It needs to be decided how the competition entries are reviewed and tested as suitable. Who will be in the group that does it.
• There was discussion on whether to allow closed-source entries; it is more difficult to review those and make sure there are no hiddem malicious features. However if the competition is restricted to FOSS only, it might alienate some developers. It was decided that we want to aim open/portable SW anyway, so competition entries need to be FOSS. Github can be used for source code inspection, and binaries could be uploaded to maemo.org repositories. Other than Maemo binaries (harmattan/SFOS) could be uploaded to openrepos (need to be checked if possible).
• It could be a good idea to recruit people from other communities (like TJC) to test submissions and possibly to join TMO and attend the competition too

Action Items:

• old items:
  • Looking into automatic calculation of election results ...
  • Discuss spam handling with techstaff.
• new items:
  • Finalize the coding competition rules.
  • Post to TMO announcing the competition and requesting for donations.
  • Discuss competition entries storing with OpenRepos people.

Link: Original article.

Originally Posted by nieldk

What I miss here, is the topic of who collects/ships the rewards for the competition.