<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="generator" content="Osso Notes">
<title></title></head>
<body>
<p>On wto 10 lip 2012 18:06:32 CEST, robert bauer <<a href="mailto:nybauer@gmail.com">nybauer@gmail.com</a>> wrote:
<br>
<br>> Hello,
<br>>
<br>> In order to continue the community at <a href="http://www.maemo.org">www.maemo.org</a> in the future, it
<br>> will be necessary to migrate much of the infrastructure and associated
<br>> elements to a new site and to establish a separate entity for that
<br>> purpose.  See generally <a href="http://talk.maemo.org/showthread.php?t=84933">http://talk.maemo.org/showthread.php?t=84933</a>.
<br>> The attached bylaws are proposed for discussion.  Please note that this
<br>> is primarily a legal document and this is not the appropriate place to
<br>> discuss many of the issues associated with the actual migration of the
<br>> community.
<br>>
<br>> The first thing you may notice is the name.  Because Maemo is trademarked
<br>> by Nokia and we don't want to experience problems, or even delay, while
<br>> the issue is worked out, we have decided to suggest Hildon Foundation as
<br>> the name.  There is also a recognition that Maemo may be regarded as
<br>> having commercially tarnished by Nokia's negligence of the software, and
<br>> so it might be good to use a different name in any event.  Either one of
<br>> the domain names <a href="http://www.maemocommunity.org">www.maemocommunity.org</a> and <a href="http://www.hildonfoundation.org">www.hildonfoundation.org</a>
<br>> have been registered and will be available for the community if we
<br>> choose to use them.
<br>>
<br>> Because this is a legal document, the discussion of the mission is
<br>> broadly stated in historical context so that the entity has much
<br>> flexibility. Although Maemo and Hildon are mentioned, this should not be
<br>> regarded as any implication at all that Qt, Harmattan, CSSU, Cordia, kp,
<br>> or any other specific software related to Maemo will not be supported by
<br>> the entity.
<br>>
<br>> The operations of the NPE allow it to cooperate with Nokia, Jolla, or
<br>> other commercial entity.  However, the entity is obligated to itself
<br>> permanently be an open source organization.
<br>>
<br>> Perhaps the section of most interest and discussion will be Membership
<br>> and Governance.  It is suggested that we keep the present "open" nature
<br>> of the maemo community to the extent practical.  But this is not meant
<br>> to be predetermined and alternative structures may be proposed and
<br>> adopted. It is also unknown whether a voting mechanism opf the current
<br>> maemo infrastructure will continue to be available.  The composition of
<br>> the initial Board also needs to be carefully determined and this is
<br>> surrounded by brackets.
<br>>
<br>> The finances and budgets will be worked out once the entity is in place
<br>> and can establish a bank account.
<br>>
<br>> The jurisdiction does not dictate the location of the servers or
<br>> repositories, or the nationality of the Board members.  Pennsylvania is
<br>> suggested because it has more lax requirements than Delaware and better
<br>> suited for smaller organizations.  Europe is also available and so the
<br>> jurisdiction is surrounded by brackets.  The main considerations are
<br>> speed and start-up costs.
<br>>
<br>> Council discussed a prior draft of the bylaws at its July 6 meeting and
<br>> you may refer to the logs for that discussion.  Please don't take
<br>> offense if an issue important to you has not been mentioned in this mail
<br>> - please raise it and discuss it as you wish.
<br>>
<br>> Rob (SD69)
<br>---
<br>
<br>One of the main issues is method and date of electing Board. While in document, a cadence of one year is suggestem, I'm pretty sure that - for transparent continuity - first election for board of directors, should be held at expected date for Council election (i.e. Council transparently migrates to Board).
<br>
<br>Personaly, I think that - for historical and practical reasons - we should keep Community Council name. Hoever, most foundations - like KDE - have Board of Directors. Such details are to be decided by Community.
<br>
<br>/Estel<br></p>
</body>
</html>