Task:Mapping openness
m (→Ongoing: fix link)
 
(27 intermediate revisions not shown)
Line 1: Line 1:
-
{| style="background-color:#f4f09c; border: 1px silver solid; padding: 10px; text-align: center;"
+
{{100Days agenda}}
-
| This article is continued discussion from the [http://maemo.org/news/announcements/view/maemo-brainstorm.html maemo.org brainstorm], please see the [[100Days|100 Days agenda]] for more.
+
-
|}
+
-
Openness is a significant part of what makes maemo so strong, putting together a plan for addressing closed-source components, particularly those directly controlled by Nokia (e.g. low-level stuff like mce and dsme, and user-space stuff like tablet-browser and the task/statusbar applets), would be both a good way to work towards making things that (the community believes, and that Nokia will be convinced of ;)) should be open open and, more generally, addressing the community's concerns over openness in general, particularly the "Why?" of it.
+
==Objectives==
-
:''Perhaps ''Map openness'' would be a more accurate description, specially for the 100 Days. Nokia has not the goal of shipping a 100% open source platform. Open source is the recommended approach, but closed source is used when it offers a differentiator, an advantage over competitors. But it is good to get a common understanding on why Nokia is shipping component X as closed source, and answer when possible to requests about opensourcing something.--[[User:qgil|qgil]] 06:46, 2 June 2008 (UTC)''
+
* Clarify the open source strategy of Nokia in Maemo.
-
::''No, I don't disagree. The community's end-goal here is greater openness (I don't think anybody but the strongest outliers is really dead-set on 100% open, though), and the first step towards achieving that goal is greater (and more specific) communication on the subject, thus, the mapping. So the title could be a bit misleading from the agenda perspective, but openness is definitely the goal here. —[[User:generalantilles|generalantilles]] 16:09, 2 June 2008 (UTC)''
+
* Identify the licenses of the packages that make Maemo.
 +
* Provide the reasons of closed source packages to be closed.
 +
* Define a process to request the opening of a package.
 +
* Document the maemo.org maintenance and development processes.
-
== The plan ==
+
==Tasks==
-
* Identify all components (a module name isn't enough). Be like GNOME's release set list.
+
Help is welcome in all of them.
-
* Identify all closed components in the OS at each layer:
+
 
-
** Initfs/direct hardware access
+
===Completed===
-
** Firmware used by kernel modules (Wifi, Bluetooth)
+
* Document explaining the open source positioning and strategy of Nokia in Maemo. - Quim
-
** Low-level system daemons (mce, dsme)
+
* Introduce [[Maemo package source status|license and open/closed status]] to the [[Task:Components_and_packages|list of packages]] - Soumya?
-
** User-space applications (tablet-browser, applets)
+
 
-
* For each package:
+
===Ongoing===
-
** Outline purpose in a dedicated wiki page.
+
 
-
** Describe the closed-source rationale.
+
* [[Task:Document maemo.org processes|Documenting in maemo.org the web development process]] (see [[Maemo.org team/Updating maemo.org sites|updating maemo.org sites]]  - Dave
-
*** ''Will need some form of mediawiki template for such pages --[[User:jaffa|jaffa]] 22:26, 29 May 2008 (UTC)''
+
* [[Why the closed packages|Explanation of the reasons why the closed source packages are closed]] - Quim
-
* Document the process for working towards opening the component, or its specification.
+
* Describe the [[Task:Maemo contributions|Maemo contributions]] to complement http://opensource.nokia.com - Quim
-
* Ensuring any new closed packages get a wiki page containing their rationale.
+
 
-
:''Yes, we can do or at least start something along these lines in the 100 Days. What about getting into details about this plan in a page apart, to keeop the main page clean?  (same would apply to the rest of actions taken) Let's also see to the potential starting points i.e. [http://maemo.org/development/documentation/how-tos/4-x/maemo_architecture.html the maemo architecture] and the [http://tablets-dev.nokia.com/4.0.1/4.0_vs_4.0.1_content_comparison.html list of packages].--[[User:qgil|qgil]] 06:46, 2 June 2008 (UTC)''
+
===Backlog===
 +
Currently in the [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g maemo.org backlog]:
 +
* Define maemo.org policies for things like editbugs, getting @maemo.org email addresses, and if it doesn't exist, getting svn access - Dave
 +
* [https://bugs.maemo.org/show_bug.cgi?id=1584 Bug 1584] - provide system management software under free software licenses - Quim
 +
* Process to [[Source petition for example package|request a closed source package to be open]] - volunteers needed.
 +
* Review the [http://maemo.org/legal/contribution_guidelines/ Maemo contribution guidelines] - Quim

Latest revision as of 10:31, 13 July 2010

Image:Ambox_notice.png
 This article is continued discussion from the maemo.org brainstorm
Please see the 100 Days agenda for more.


Contents

[edit] Objectives

  • Clarify the open source strategy of Nokia in Maemo.
  • Identify the licenses of the packages that make Maemo.
  • Provide the reasons of closed source packages to be closed.
  • Define a process to request the opening of a package.
  • Document the maemo.org maintenance and development processes.

[edit] Tasks

Help is welcome in all of them.

[edit] Completed

[edit] Ongoing

[edit] Backlog

Currently in the maemo.org backlog:

Retrieved from "http://wiki.maemo.org/Task:Mapping_openness"