<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.sugarlabs.org/index.php?action=history&amp;feed=atom&amp;title=Oversight_Board%2FProject_Motion</id>
	<title>Oversight Board/Project Motion - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.sugarlabs.org/index.php?action=history&amp;feed=atom&amp;title=Oversight_Board%2FProject_Motion"/>
	<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Oversight_Board/Project_Motion&amp;action=history"/>
	<updated>2026-05-03T11:21:14Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.0</generator>
	<entry>
		<id>https://wiki.sugarlabs.org/index.php?title=Oversight_Board/Project_Motion&amp;diff=60211&amp;oldid=prev</id>
		<title>Walter: Created page with &quot;== MOTION ==  First, the short version:  1. If your project helps SL, is all freely licensed, and has a wiki page  with certain info on it, you can apply for project status by em...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.sugarlabs.org/index.php?title=Oversight_Board/Project_Motion&amp;diff=60211&amp;oldid=prev"/>
		<updated>2010-12-14T01:47:47Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;== MOTION ==  First, the short version:  1. If your project helps SL, is all freely licensed, and has a wiki page  with certain info on it, you can apply for project status by em...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== MOTION ==&lt;br /&gt;
&lt;br /&gt;
First, the short version:&lt;br /&gt;
&lt;br /&gt;
1. If your project helps SL, is all freely licensed, and has a wiki page &lt;br /&gt;
with certain info on it, you can apply for project status by emailing &lt;br /&gt;
slobs/iaep your wiki page URL and saying &amp;quot;here&amp;#039;s our project page, &lt;br /&gt;
please raise a motion to make us a project.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
2. If SLOBs passes the motion (4 votes of +1), you are a project. This &lt;br /&gt;
gets you a sidebar listing, do-it-yourself infrastructure access, and &lt;br /&gt;
permission to call yourselves a SL project. (In addition, projects can&lt;br /&gt;
work with Sugar Labs on fund raising.)&lt;br /&gt;
&lt;br /&gt;
3. Projects are obligated to update their project page and email that &lt;br /&gt;
project page URL to the list during the last month of each Sugar release &lt;br /&gt;
cycle. That&amp;#039;s it.&lt;br /&gt;
&lt;br /&gt;
4. If a project doesn&amp;#039;t do this (SLOBs will check), its project status &lt;br /&gt;
is revoked, and it loses the sidebar listing and the ability to call &lt;br /&gt;
itself a SL project. Projects who have their status revoked may reapply, &lt;br /&gt;
see (1).&lt;br /&gt;
&lt;br /&gt;
Now, the fine print:&lt;br /&gt;
&lt;br /&gt;
Being a SL project means you get (1) listed in the sidebar, (2) full use &lt;br /&gt;
of SL infrastructure&amp;#039;s resources (though projects must do the &lt;br /&gt;
administrative work themselves, they&amp;#039;ll get machine access) if the &lt;br /&gt;
project isn&amp;#039;t already using them, and (3) permission to refer to &lt;br /&gt;
yourselves as a SL project (you can request TM usage separately).&lt;br /&gt;
&lt;br /&gt;
Being a SL project does NOT mean that (1) SL teams are obligated to &lt;br /&gt;
fulfil all your requests, or that (2) SLOBs or SL teams can tell you &lt;br /&gt;
what to do, or that (3) anyone else will step up and make your project &lt;br /&gt;
happen - people working on a project still need to step up and drive and &lt;br /&gt;
do all the work.&lt;br /&gt;
&lt;br /&gt;
The only thing SLOBs can do is remove &amp;quot;SL Project&amp;quot; status, which (1) &lt;br /&gt;
removes a project from the sidebar and (2) the project not being able to &lt;br /&gt;
refer to itself as a &amp;quot;SL project&amp;quot; any more. (Infrastructure privileges &lt;br /&gt;
shouldn&amp;#039;t be removed except in cases of gross misconduct.)&lt;br /&gt;
&lt;br /&gt;
SL projects must:&lt;br /&gt;
* work towards the mission of SL in some way, &lt;br /&gt;
http://wiki.sugarlabs.org/go/Sugar_Labs#Mission&lt;br /&gt;
* contain only code and content released under approved licenses, &lt;br /&gt;
http://wiki.sugarlabs.org/go/Trademark#Approved_licenses&lt;br /&gt;
&lt;br /&gt;
To request status as a SL project, create a project wiki page that &lt;br /&gt;
contains (at minimum) the following information, and submit it to SLOBs &lt;br /&gt;
as an agenda item (&amp;quot;here is our project wiki page, can we be a project?&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
(these are directly from the version of &lt;br /&gt;
http://wiki.sugarlabs.org/go/Sugar_Labs/Project_Guidelines as of this &lt;br /&gt;
writing)&lt;br /&gt;
&lt;br /&gt;
* Who the new project would serve and who will lead the project&lt;br /&gt;
* What the goals and scope of the new project would be&lt;br /&gt;
* When the project can be considered a success&lt;br /&gt;
* Where the project will lead and where it will fit into Sugar Labs&lt;br /&gt;
* Why the idea warrants the creation of a new project within Sugar Labs&lt;br /&gt;
* How the project will benefit Sugar Labs and the Sugar ecosystem&lt;br /&gt;
* The number of active contributors&lt;br /&gt;
* The state of the project compared to its goals&lt;br /&gt;
* Documentation of how the project is working for the community&lt;br /&gt;
* The current method of governing the project&lt;br /&gt;
* A schedule and plan to achieve remaining goals and milestones&lt;br /&gt;
&lt;br /&gt;
This then becomes a motion that needs 4 SLOBs +1s to pass, just like any &lt;br /&gt;
other motion.&lt;br /&gt;
&lt;br /&gt;
The only obligation of a project is to submit a status report, in the &lt;br /&gt;
form of emailing iaep a link to an updated project wiki page with &lt;br /&gt;
up-to-date answers to all the same above questions, during the last &lt;br /&gt;
month of each sugar release cycle. One week after each Sugar release &lt;br /&gt;
cycle, SLOBs will check which projects have fulfilled that obligation, &lt;br /&gt;
renew the project status of all projects that have, and revoke project &lt;br /&gt;
status of all projects that haven&amp;#039;t. Projects that haven&amp;#039;t can simply &lt;br /&gt;
reapply.&lt;/div&gt;</summary>
		<author><name>Walter</name></author>
	</entry>
</feed>