Open development - Revision history

joerg_rw: /* Community SSU */ github now. gitoriuos dead

2017-09-29T16:35:01Z

Community SSU: github now. gitoriuos dead

← Older revision		Revision as of 16:35, 29 September 2017
Line 82:		Line 82:
	=== Community SSU ===		=== Community SSU ===

-	The [[community SSU]] has [http://gitorious.org/community-ssu/ its own Gitorious project]. You can find all modifications to the Maemo open components (and sources of those), as well as replacement components and hacked bits, all there.	+	The [[community SSU]] has [http://gitorious.org/community-ssu/ its own Gitorious project] ([https://github.com/community-ssu now]). You can find all modifications to the Maemo open components (and sources of those), as well as replacement components and hacked bits, all there.

	[[Category:Community]]		[[Category:Community]]
	[[Category:Development]]		[[Category:Development]]

joerg_rw: /* Community SSU */

2011-11-29T01:04:42Z

Community SSU

← Older revision		Revision as of 01:04, 29 November 2011
Line 82:		Line 82:
	=== Community SSU ===		=== Community SSU ===

-	The [[community SSU]] has [http://gitorious.org/community-ssu/ its own Gitorious project]. You can find all modifications to the Maemo open components (and sources of those) there.	+	The [[community SSU]] has [http://gitorious.org/community-ssu/ its own Gitorious project]. You can find all modifications to the Maemo open components (and sources of those), as well as replacement components and hacked bits, all there.

	[[Category:Community]]		[[Category:Community]]
	[[Category:Development]]		[[Category:Development]]

thp: /* MeeGo */ Fix typo

2011-05-20T19:40:08Z

MeeGo: Fix typo

← Older revision		Revision as of 19:40, 20 May 2011
Line 37:		Line 37:

	* [http://mxr.meego.com/ Meego Cross-Reference]		* [http://mxr.meego.com/ Meego Cross-Reference]
-	* [http://meego.gitorious.org/ ~~MeeHo~~ on Gitorious] is where open development for Meego happens. For example, sources for the Meego Touch Framework are there. You can also find sources for some middleware components used in Maemo that have been partially opened in Meego, like [http://meego.gitorious.org/meego-middleware/mce MCE].	+	* [http://meego.gitorious.org/ MeeGo on Gitorious] is where open development for Meego happens. For example, sources for the Meego Touch Framework are there. You can also find sources for some middleware components used in Maemo that have been partially opened in Meego, like [http://meego.gitorious.org/meego-middleware/mce MCE].
	* [http://qt.gitorious.org/ Qt on Gitorious] Qt is an important part of the newer Maemo/Meego releases; you can find its source here.		* [http://qt.gitorious.org/ Qt on Gitorious] Qt is an important part of the newer Maemo/Meego releases; you can find its source here.

amigadave: move content from Sources

2011-03-08T12:04:35Z

move content from Sources

← Older revision		Revision as of 12:04, 8 March 2011
Line 1:		Line 1:
-	~~== The basics ==~~
-
	Maemo is developed as an open collaboration between Nokia and many generous volunteer programmers, designers, and users. Most of Maemo's components are open source, which gives users and developers the freedom and flexibility to contribute to and modify the platform's core development. Read the [http://maemo.nokia.com/maemo/maemo-software/ Introduction to open source] at maemo.nokia.com.		Maemo is developed as an open collaboration between Nokia and many generous volunteer programmers, designers, and users. Most of Maemo's components are open source, which gives users and developers the freedom and flexibility to contribute to and modify the platform's core development. Read the [http://maemo.nokia.com/maemo/maemo-software/ Introduction to open source] at maemo.nokia.com.

Line 7:		Line 5:
	== Open Source and open development strategy ==		== Open Source and open development strategy ==

-	* [~~http://wiki.maemo.org/~~Documentation/~~Maemo_5_Developer_Guide~~/Architecture/~~Top_Level_Architecture~~ Maemo 5 software architecture] indicating open/closed components.	+	* [[Documentation/Maemo 5 Developer Guide/Architecture/Top Level Architecture\|Maemo 5 software architecture]] indicating open/closed components.
	* [http://www.slideshare.net/qgil/how-maemo-approaches-open-source-presentation How Maemo approaches open source] explains the basics.		* [http://www.slideshare.net/qgil/how-maemo-approaches-open-source-presentation How Maemo approaches open source] explains the basics.
	* [http://www.slideshare.net/peterschneider/ari-jaaksi-o-s-i-m-world-2009 Taking open source forward] explains Maemo's willingness to collaborate in the platform while differentiating in the user experience.		* [http://www.slideshare.net/peterschneider/ari-jaaksi-o-s-i-m-world-2009 Taking open source forward] explains Maemo's willingness to collaborate in the platform while differentiating in the user experience.
Line 25:		Line 23:
	== In practice ==		== In practice ==

-	* If you want to get involved you need to find first the most recent source code available.	+	If you want to get involved you need to find first the most recent source code available:
-	** The source code of OSS components shipped in Maemo releases can be found at http://repository.maemo.org/pool/ e.g. [http://repository.maemo.org/pool/maemo5.0/free/ Maemo 5].	+	* The source code of OSS components shipped in Maemo releases can be found at http://repository.maemo.org/pool/ e.g. [http://repository.maemo.org/pool/maemo5.0/free/ Maemo 5].
-	** The current development of certain components can be found at http://maemo.gitorious.org . See the list of projects above for more details.	+	* The current development of certain components can be found at [http://maemo.gitorious.org Maemo on Gitorious]. See the list of projects above for more details.
-	* If you have patches for upstream components it is better to submit them directly upstream, unless they are indeed specific to Maemo.	+	** [http://gitorious.org/modest/ modest on gitorious] where open development for Modest (the stock N900 mail client) happened.
		+	* [http://mxr.maemo.org maemo.org Cross-Reference] contains searchable source dumps of the open packages of most Maemo releases. This website is incredibly useful; you can search for any given identifier (a name of a C function, for example) and it will find the declaration and all uses of that function for you.
		+
		+	If you have patches for upstream components it is better to submit them directly upstream, unless they are indeed specific to Maemo:
	* Check the [[Maemo contribution guidelines]] before contributing any code.		* Check the [[Maemo contribution guidelines]] before contributing any code.
-	* Patches with bugfixes are submitted through ~~http~~://bugs.maemo.org with the corresponding bug report.	+	* Patches with bugfixes are submitted through https://bugs.maemo.org with the corresponding bug report.
	* Contact the developers before working on major patches or new features!		* Contact the developers before working on major patches or new features!
		+
		+	=== MeeGo ===
		+
		+	* [http://mxr.meego.com/ Meego Cross-Reference]
		+	* [http://meego.gitorious.org/ MeeHo on Gitorious] is where open development for Meego happens. For example, sources for the Meego Touch Framework are there. You can also find sources for some middleware components used in Maemo that have been partially opened in Meego, like [http://meego.gitorious.org/meego-middleware/mce MCE].
		+	* [http://qt.gitorious.org/ Qt on Gitorious] Qt is an important part of the newer Maemo/Meego releases; you can find its source here.

	== Projects developed openly ==		== Projects developed openly ==
		+
	* Many components integrated in Maemo have Nokia developers or collaborators working directly upstream:		* Many components integrated in Maemo have Nokia developers or collaborators working directly upstream:
	** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]		** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]
Line 55:		Line 63:

	== Community projects developed openly ==		== Community projects developed openly ==
		+
	There are dozens of community projects developed openly. Learn more about them at (this should link to another page to keep this one around Nokia projects).		There are dozens of community projects developed openly. Learn more about them at (this should link to another page to keep this one around Nokia projects).
		+
		+	=== Extras ===
		+
		+	{{main\|Extras}}
		+
		+	The sources from all ''free'' packages in the extras and extras-devel repositories are available [http://repository.maemo.org/extras/pool/fremantle/free/source/ here].
		+
		+	On an [[Nokia N900\|N900]], or scratchbox, if you have [http://repository.maemo.org/#extras correctly added the extras-devel repository to sources.list], you can also get any packages source by writing the following on a shell:
		+
		+	apt-get source <packagename>
		+
		+	There are also some [http://vcs.maemo.org/git/ Garage projects using Git as version control system].
		+
		+	Some developers also use gitorious or github.
		+
		+	=== Community SSU ===
		+
		+	The [[community SSU]] has [http://gitorious.org/community-ssu/ its own Gitorious project]. You can find all modifications to the Maemo open components (and sources of those) there.

	[[Category:Community]]		[[Category:Community]]
	[[Category:Development]]		[[Category:Development]]

amigadave: /* Open Source and open development strategy */ add link

2010-05-20T08:15:59Z

Open Source and open development strategy: add link

← Older revision		Revision as of 08:15, 20 May 2010
Line 15:		Line 15:
	* [[Task:Components and packages]] contains statistics about packages open/closed in Maemo 4.1. A Maemo 5 update will come after the final release.		* [[Task:Components and packages]] contains statistics about packages open/closed in Maemo 4.1. A Maemo 5 update will come after the final release.
	* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.		* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.
		+	* [[What can we realistically expect]] lists some current hot topic discussions within the Maemo community
	* [[Task:Busybox]] describes the strategy for moving towards open development of Busybox.		* [[Task:Busybox]] describes the strategy for moving towards open development of Busybox.
	* [[Task:osso-xterm]] - opening the development of osso-xterm		* [[Task:osso-xterm]] - opening the development of osso-xterm

amigadave: /* Projects developed openly */ links

2010-05-04T12:31:49Z

Projects developed openly: links

← Older revision		Revision as of 12:31, 4 May 2010
Line 35:		Line 35:
	* Many components integrated in Maemo have Nokia developers or collaborators working directly upstream:		* Many components integrated in Maemo have Nokia developers or collaborators working directly upstream:
	** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]		** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]
-	** BlueZ	+	** [http://www.bluez.org/ BlueZ]
-	** GStreamer	+	** [http://gstreamer.freedesktop.org/ GStreamer]
-	** GTK+	+	** [http://www.gtk.org/ GTK+]
-	** Mozilla	+	** [http://www.mozilla.org/ Mozilla]
-	** Meta Tracker	+	** [http://projects.gnome.org/tracker/ Meta Tracker]
	** Ohm		** Ohm
-	** Telepathy	+	** [http://telepathy.freedesktop.org/wiki/ Telepathy]
-	** Upstart	+	** [http://upstart.ubuntu.com/ Upstart]
	** [http://connman.net/ ConnMan]		** [http://connman.net/ ConnMan]
	** [http://ofono.org/ oFono]		** [http://ofono.org/ oFono]
Line 49:		Line 49:
	** [https://garage.maemo.org/projects/busybox4maemo/ BusyBox]		** [https://garage.maemo.org/projects/busybox4maemo/ BusyBox]
	** [https://garage.maemo.org/projects/dsm/ dsme]		** [https://garage.maemo.org/projects/dsm/ dsme]
-	** osso-xterm	+	** [https://garage.maemo.org/projects/osso-xterm/ osso-xterm]
	* Developer tools:		* Developer tools:
	** [http://code.google.com/p/gst-dsp/ gst-dsp] aims to provide GStreamer elements to take advantage of those algorithms. The list includes video/image decoders and encoders. See also the [http://maemo.gitorious.org/maemo-multimedia/gst-dsp Maemo repository]		** [http://code.google.com/p/gst-dsp/ gst-dsp] aims to provide GStreamer elements to take advantage of those algorithms. The list includes video/image decoders and encoders. See also the [http://maemo.gitorious.org/maemo-multimedia/gst-dsp Maemo repository]

192.87.219.36: add gstreamer

2010-05-04T11:01:01Z

add gstreamer

← Older revision		Revision as of 11:01, 4 May 2010
Line 36:		Line 36:
	** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]		** [http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-omap-2.6.git;a=summary Linux kernel - OMAP list.]
	** BlueZ		** BlueZ
		+	** GStreamer
	** GTK+		** GTK+
	** Mozilla		** Mozilla

stskeeps at 14:55, 18 February 2010

2010-02-18T14:55:54Z

← Older revision		Revision as of 14:55, 18 February 2010
Line 12:		Line 12:
	* [[Open development/Upstream projects\|Upstream projects]] providing software integrated in Maemo releases.		* [[Open development/Upstream projects\|Upstream projects]] providing software integrated in Maemo releases.
	* [[Open development/Maemo contributions\|Maemo contributions]] is an attempt to list the most relevant contributions to OSS upstream projects.		* [[Open development/Maemo contributions\|Maemo contributions]] is an attempt to list the most relevant contributions to OSS upstream projects.
		+	* [[Open_development/Licensing_change_requests]] is the way to ask for licensing changes.
	* [[Task:Components and packages]] contains statistics about packages open/closed in Maemo 4.1. A Maemo 5 update will come after the final release.		* [[Task:Components and packages]] contains statistics about packages open/closed in Maemo 4.1. A Maemo 5 update will come after the final release.
	* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.		* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.

amigadave: Category:Community and Category:Development

2010-02-11T15:05:31Z

Category:Community and Category:Development

← Older revision		Revision as of 15:05, 11 February 2010
Line 53:		Line 53:
	== Community projects developed openly ==		== Community projects developed openly ==
	There are dozens of community projects developed openly. Learn more about them at (this should link to another page to keep this one around Nokia projects).		There are dozens of community projects developed openly. Learn more about them at (this should link to another page to keep this one around Nokia projects).
		+
		+	[[Category:Community]]
		+	[[Category:Development]]

dneary: /* Open Source and open development strategy */

2010-02-02T11:04:28Z

Open Source and open development strategy

← Older revision		Revision as of 11:04, 2 February 2010
Line 15:		Line 15:
	* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.		* [[Open development/Why the closed packages]] elaborates the reasons to have certain packages closed and addresses requests for opening components.
	* [[Task:Busybox]] describes the strategy for moving towards open development of Busybox.		* [[Task:Busybox]] describes the strategy for moving towards open development of Busybox.
		+	* [[Task:osso-xterm]] - opening the development of osso-xterm

	See also the [[Task:Maemo_roadmap/Fremantle\|Fremantle]] and [[Task:Maemo_roadmap/Harmattan\|Harmattan]] roadmaps.		See also the [[Task:Maemo_roadmap/Fremantle\|Fremantle]] and [[Task:Maemo_roadmap/Harmattan\|Harmattan]] roadmaps.