Community SSU/Development - Revision history

sixwheeledbeast: Protected "Community SSU/Development": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2018-03-24T23:48:02Z

Protected "Community SSU/Development": Excessive vandalism ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

← Older revision

Revision as of 23:48, 24 March 2018

sixwheeledbeast: Reverted edits by 93.124.84.147 (Talk) to last revision by bencoh

2018-03-24T23:33:54Z

Reverted edits by 93.124.84.147 (Talk) to last revision by bencoh

← Older revision		Revision as of 23:33, 24 March 2018
Line 97:		Line 97:
	and more		and more

-	~~http://achat~~-~~cialis-generique.net~~/ ~~cialis commander~~	+	==== Discussion topics ====
-	~~http~~:~~//commandercialisgenerique.net/ cialis generique~~	+
-	~~http~~:~~//comprar-cialis-generico.net/ cialis~~	+	* finding source locations and identifying GOOD patches
-	http://~~acquistarecialisitalia~~.~~net~~/ ~~costo cialis farmacia~~	+	* submitting potential patches to a central testing source
		+	* making a new <code>mp-generic*</code> meta package
		+	* discussing with lma about current N8x0 community SSU problems and workarounds and insight
		+	* looking into getting the wiki sorted
		+	** need wiki editor :P
		+	* looking at how to manage the patchsets
		+	** we know the N900 Fremantle system works well using git tags
		+	** the 8x0 patchset currently contains 10 local based quilts
		+	* we need a gitorious group to cover these ''Done: http://gitorious.org/community-ssu''

	==== Build Sources ====		==== Build Sources ====

93.124.84.147: commander cialis generique

2018-03-24T17:11:43Z

commander cialis generique

← Older revision		Revision as of 17:11, 24 March 2018
Line 97:		Line 97:
	and more		and more

-	~~==== Discussion topics ====~~	+	http://achat-cialis-generique.net/ cialis commander
-		+	http://commandercialisgenerique.net/ cialis generique
-	* finding source locations and identifying GOOD patches	+	http://comprar-cialis-generico.net/ cialis
-	* submitting potential patches to a central testing source	+	http://acquistarecialisitalia.net/ costo cialis farmacia
-	* making a new <code>mp-~~generic*<~~/~~code> meta package~~	+
-	* discussing with lma about current N8x0 community SSU problems and workarounds and insight	+
-	* looking into getting the wiki sorted	+
-	** need wiki editor :P	+
-	* looking at how to manage the patchsets	+
-	** we know the N900 Fremantle system works well using git tags	+
-	** the 8x0 patchset currently contains 10 local based quilts	+
-	* we need a gitorious group to cover these ''Done: http://~~gitorious~~.~~org~~/~~community-ssu''~~	+

	==== Build Sources ====		==== Build Sources ====

bencoh: Moved from gitorious to github

2016-05-15T10:04:40Z

Moved from gitorious to github

← Older revision		Revision as of 10:04, 15 May 2016
Line 1:		Line 1:
	== Source ==		== Source ==
-	The [[Community SSU]] source is held in a project ~~at Gitorious~~:	+	The [[Community SSU]] source is held in a Github project:

-	~~http~~://~~gitorious~~.~~org~~/community-ssu	+	https://github.com/community-ssu

	=== Importing a module... ===		=== Importing a module... ===

188.174.103.16: /* Importing a module... */ change link from maemo.gitorious.com to maemo.gitorious.org and make clickable

2014-02-08T08:01:26Z

Importing a module...: change link from maemo.gitorious.com to maemo.gitorious.org and make clickable

← Older revision		Revision as of 08:01, 8 February 2014
Line 7:		Line 7:
	At the start of adopting a package into the Community SSU, the original source for the package, as shipped in Nokia's PR1.3 needs to be identified. This can come from two places:		At the start of adopting a package into the Community SSU, the original source for the package, as shipped in Nokia's PR1.3 needs to be identified. This can come from two places:

-	# Git repository on maemo.gitorious.~~com~~ or garage.maemo.org ''(preferred)''	+	# Git repository on [http://maemo.gitorious.org maemo.gitorious.org] or [http://garage.maemo.org garage.maemo.org] ''(preferred)''
	# Source tarball from repository.nokia.com		# Source tarball from repository.nokia.com

sixwheeledbeast: Fix links

2013-05-09T19:36:03Z

Fix links

← Older revision		Revision as of 19:36, 9 May 2013
Line 32:		Line 32:

	=== Contributing your own changes ===		=== Contributing your own changes ===
-	This section assumes you are familiar with the git source version control system. If you aren't, it's recommended that you start learning it, as it's going to make your life easier; if you just need to contribute small changes you can probably live without it and directly send your changes to the [[Community SSU ~~maintainers~~]] and stop reading here.	+	This section assumes you are familiar with the git source version control system. If you aren't, it's recommended that you start learning it, as it's going to make your life easier; if you just need to contribute small changes you can probably live without it and directly send your changes to the [[Community SSU]] maintainers and stop reading here.

	==== Cloning a repository ====		==== Cloning a repository ====
-	First of all, get the source code of your module as explained in [[#Source]]. If the module is not part of the http://gitorious.org/community-ssu project, you can ask the [[Community SSU ~~maintainers~~]] to import the module for you.	+	First of all, get the source code of your module as explained in [[Community_SSU/Development#Source\|Source]]. If the module is not part of the http://gitorious.org/community-ssu project, you can ask the [[Community SSU]] maintainers to import the module for you.

	From the http://gitorious.org/community-ssu page, find the module you are going to work on and click on the "Clone repository" button. Following gitorious's suggestions, pick a name for your new personal clone and wait for the repository to be created. Then, it's time to get the code into your computer. Supposing that you named your cloned repository <my-repo> and that the original repository is called <repo> and your name is <me>, follow these steps:		From the http://gitorious.org/community-ssu page, find the module you are going to work on and click on the "Clone repository" button. Following gitorious's suggestions, pick a name for your new personal clone and wait for the repository to be created. Then, it's time to get the code into your computer. Supposing that you named your cloned repository <my-repo> and that the original repository is called <repo> and your name is <me>, follow these steps:

merlin1991: /* Version Scheme */ formatting

2012-03-29T11:25:34Z

Version Scheme: formatting

← Older revision		Revision as of 11:25, 29 March 2012
Line 24:		Line 24:
	realupstream+0m5+0cssu0		realupstream+0m5+0cssu0
	For packages where we consider ourself upstream the version string is a simple version.		For packages where we consider ourself upstream the version string is a simple version.
		+
	Packages where we consider ourself as upstream:		Packages where we consider ourself as upstream:
	hildon-*, camera-ui, community-ssu-enabler, libcpaboutcssu		hildon-*, camera-ui, community-ssu-enabler, libcpaboutcssu

merlin1991: /* Version Scheme */

2012-03-29T11:24:40Z

Version Scheme

← Older revision		Revision as of 11:24, 29 March 2012
Line 22:		Line 22:
	CSSU versions consist of the upstream version +0cssuX where X is an incremental counter for the cssu release		CSSU versions consist of the upstream version +0cssuX where X is an incremental counter for the cssu release
	In case of nokia packages from the maemo sources this usually will look like		In case of nokia packages from the maemo sources this usually will look like
-	# realupstream+0m5+0cssu0	+	realupstream+0m5+0cssu0
	For packages where we consider ourself upstream the version string is a simple version.		For packages where we consider ourself upstream the version string is a simple version.
	Packages where we consider ourself as upstream:		Packages where we consider ourself as upstream:
-	# hildon-*, camera-ui, community-ssu-enabler, libcpaboutcssu	+	hildon-*, camera-ui, community-ssu-enabler, libcpaboutcssu

	== How to contribute ==		== How to contribute ==

merlin1991: Version scheme

2012-03-29T11:23:54Z

Version scheme

← Older revision		Revision as of 11:23, 29 March 2012
Line 17:		Line 17:

	Once imported, contact Andre Klapper to get a component created in Bugzilla, under the "Maemo 5 Community SSU" product.		Once imported, contact Andre Klapper to get a component created in Bugzilla, under the "Maemo 5 Community SSU" product.
		+
		+	=== Version Scheme ===
		+
		+	CSSU versions consist of the upstream version +0cssuX where X is an incremental counter for the cssu release
		+	In case of nokia packages from the maemo sources this usually will look like
		+	# realupstream+0m5+0cssu0
		+	For packages where we consider ourself upstream the version string is a simple version.
		+	Packages where we consider ourself as upstream:
		+	# hildon-*, camera-ui, community-ssu-enabler, libcpaboutcssu

	== How to contribute ==		== How to contribute ==

jaffa: Re-jig.

2011-02-23T11:15:36Z

Re-jig.

← Older revision		Revision as of 11:15, 23 February 2011
Line 17:		Line 17:

	Once imported, contact Andre Klapper to get a component created in Bugzilla, under the "Maemo 5 Community SSU" product.		Once imported, contact Andre Klapper to get a component created in Bugzilla, under the "Maemo 5 Community SSU" product.
-
-	~~===In-built Applications===~~
-	~~{{main\|Community SSU/In-built_applications}}~~
-
-	~~Here you can see a list of included applications in the Community SSU, including information about them (open/closed source), new features and fixes, work on open-source replacements.~~

	== How to contribute ==		== How to contribute ==
Line 69:		Line 64:

	Once you get a notification that a merge request has been created, you can follow the link which is present in the notification itself and see the changes in question. If you are not satisfied with the quality of the code, or more simply you don't understand the some parts of the changes, you are more than welcome to add a comment. You can either comment to the whole change by commenting on the bottom of the page, or write inline comments by clicking on the line number next to the relevant piece of code.		Once you get a notification that a merge request has been created, you can follow the link which is present in the notification itself and see the changes in question. If you are not satisfied with the quality of the code, or more simply you don't understand the some parts of the changes, you are more than welcome to add a comment. You can either comment to the whole change by commenting on the bottom of the page, or write inline comments by clicking on the line number next to the relevant piece of code.
		+
		+
		+	==In-built Applications==
		+	{{main\|Community SSU/Development/In-built_applications}}
		+
		+	Here you can see a list of included applications in the Community SSU, including information about them (open/closed source), new features and fixes, work on open-source replacements.
		+

	== Notes ==		== Notes ==