<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1"><font face="Helvetica, Arial, sans-serif">That's
what I wanted to hear. :D<br>
<br>
/Howard<br>
<br>
</font></font>
<div class="moz-cite-prefix">On 11/07/2012 10:40,
<a class="moz-txt-link-abbreviated" href="mailto:twilight312@gmail.com">twilight312@gmail.com</a> wrote:<br>
</div>
<blockquote cite="mid:1341999654.6822.5.camel@BloodRose" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="generator" content="Osso Notes">
<title></title>
<p>We don't have any jurisdiction over Mer, Jolla, and similar
efforts (fortunately). Bylaws doesn't exclude collaboration - or
even merging, if approriate - with such projects, but base goal
is continuation of support for user of Maemo flavors (incl.
Harmattan).
<br>
<br>
/Estel
<br>
<br>
On śro 11 lip 2012 05:25:10 CEST, S. Howard <<a
moz-do-not-send="true" href="mailto:howards@gmx.co.uk">howards@gmx.co.uk</a>>
wrote:
<br>
<br>
> This will also apply to MeeGo/JollaMobile efforts?
<br>
> <br>
> Howard.
<br>
> <br>
> On 10/07/2012 17:06, robert bauer wrote:
<br>
> <br>
> > Hello,
<br>
> > <br>
> > In order to continue the community at <a
moz-do-not-send="true" 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
<br>
> > generally <a moz-do-not-send="true"
href="http://talk.maemo.org/showthread.php?t=84933.%A0">http://talk.maemo.org/showthread.php?t=84933. </a>;
The attached
<br>
> > bylaws are proposed for discussion. Please note that
this is
<br>
> > primarily a legal document and this is not the
appropriate place to
<br>
> > discuss many of the issues associated with the actual
migration of
<br>
> > the community. <br>
> > <br>
> > The first thing you may notice is the name. Because
Maemo is
<br>
> > trademarked by Nokia and we don't want to experience
problems, or even
<br>
> > delay, while the issue is worked out, we have decided
to suggest
<br>
> > Hildon Foundation as the name. There is also a
recognition that Maemo
<br>
> > may be regarded as having commercially tarnished by
Nokia's negligence
<br>
> > of the software, and so it might be good to use a
different name in
<br>
> > any event. Either one of the domain names <a
moz-do-not-send="true" href="http://www.maemocommunity.org">www.maemocommunity.org</a>
and
<br>
> > <a moz-do-not-send="true"
href="http://www.hildonfoundation.org">www.hildonfoundation.org</a>
have been registered and will be available
<br>
> > for the community if we 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
<br>
> > be regarded as any implication at all that Qt,
Harmattan, CSSU,
<br>
> > Cordia, kp, or any other specific software related to
Maemo will not
<br>
> > be supported by 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"
<br>
> > nature of the maemo community to the extent
practical. But this is
<br>
> > not meant to be predetermined and alternative
structures may be
<br>
> > proposed and adopted. It is also unknown whether a
voting mechanism
<br>
> > opf the current maemo infrastructure will continue to
be available.
<br>
> > The composition of the initial Board also needs to be
carefully
<br>
> > determined and this is surrounded by brackets.
<br>
> > <br>
> > The finances and budgets will be worked out once the
entity is in
<br>
> > place 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
<br>
> > is suggested because it has more lax requirements than
Delaware and
<br>
> > better suited for smaller organizations. Europe is
also available and
<br>
> > so the jurisdiction is surrounded by brackets. The
main
<br>
> > considerations are speed and start-up costs.
<br>
> > <br>
> > Council discussed a prior draft of the bylaws at its
July 6 meeting
<br>
> > and 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
<br>
> > mail - please raise it and discuss it as you wish.
<br>
> > <br>
> > Rob (SD69)
<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > <br>
> > _______________________________________________
<br>
> > maemo-community mailing list
<br>
> > <a moz-do-not-send="true"
href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a>
<br>
> > <a moz-do-not-send="true"
href="https://lists.maemo.org/mailman/listinfo/maemo-community">https://lists.maemo.org/mailman/listinfo/maemo-community</a>
<br>
> <br>
> <br>
> <br>
<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
maemo-community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:maemo-community@maemo.org">maemo-community@maemo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.maemo.org/mailman/listinfo/maemo-community">https://lists.maemo.org/mailman/listinfo/maemo-community</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>