Requesting SVN write access - Revision history

⚠️Landa at 16:14, 11 June 2014

2014-06-11T16:14:30Z

← Older revision		Revision as of 16:14, 11 June 2014
Line 1:		Line 1:
	~~=== Procedure to request SVN write access ===~~		{{MovedToTrac\|PSC/RequestingSVNWriteAccess}}

	~~We distinguish between:~~
	* Write access to the Main GRASS-SVN repository
	* Write access to the GRASS-Addons-SVN repository

	~~Please see this page for details: http://trac.osgeo.org/grass~~/~~wiki/HowToContribute~~

	~~[[Category: PSC]]~~
	~~[[Category:Development]]~~

Neteler: clarification

2012-05-30T12:32:17Z

clarification

← Older revision		Revision as of 12:32, 30 May 2012
Line 1:		Line 1:
	=== Procedure to request SVN write access ===		=== Procedure to request SVN write access ===

	~~See~~ http://trac.osgeo.org/grass/wiki/HowToContribute		We distinguish between:
			* Write access to the Main GRASS-SVN repository
			* Write access to the GRASS-Addons-SVN repository

			Please see this page for details: http://trac.osgeo.org/grass/wiki/HowToContribute

	[[Category: PSC]]		[[Category: PSC]]
	[[Category:Development]]		[[Category:Development]]

Neteler: moved to http://trac.osgeo.org/grass/wiki/HowToContribute

2008-03-26T15:00:40Z

moved to http://trac.osgeo.org/grass/wiki/HowToContribute

@@ Line 1: / Line 1: @@
 === Procedure to request SVN write access ===
-The [[PSC|GRASS Project Steering Commitee]] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]).
+See http://trac.osgeo.org/grass/wiki/HowToContribute
 [[Category: PSC]]
 [[Category:Development]]

Neteler: updated to new rules (this page should go into trac)

2008-02-06T08:46:37Z

updated to new rules (this page should go into trac)

← Older revision		Revision as of 08:46, 6 February 2008
Line 1:		Line 1:
	=== Procedure to request ~~CVS~~ write access ===		=== Procedure to request SVN write access ===

	The [[PSC\|GRASS Project Steering Commitee]] is responsible for granting ~~CVS~~ write access to contributors (as defined in [http://~~mpa~~.~~itc~~.it/~~markus~~/~~grass63progman~~/rfc/rfc1_psc.html RFC1]).		The [[PSC\|GRASS Project Steering Commitee]] is responsible for granting SVN write access to contributors (as defined in [http://download.osgeo.org/grass/grass6_progman/rfc/rfc1_psc.html RFC1]).

	* The requestor has to '''read and ~~accept~~''' the document [http://~~mpa~~.~~itc~~.it/~~markus~~/~~grass63progman~~/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).		* The requestor has to '''read and abide by''' the document [http://download.osgeo.org/grass/grass6_progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).

	* The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires [http://~~grass~~.~~itc~~.it/mailman/listinfo/grass-psc subscription] to the mailing list.		* The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires [http://lists.osgeo.org/mailman/listinfo/grass-psc subscription] to the mailing list.

	=== Setting up ~~CVS~~ write access ===		=== Setting up SVN write access ===

	Once ~~CVS~~ access is granted, the requestor ~~should follow the [~~http://~~freegis~~.org//~~grass~~/~~howto_grass-sshcvs~~.en.~~html GRASS~~-~~CVS-ssh instructions] to get the write access enabled~~. The ~~public SSH key should be sent to Bernhard Reiter (email address at page bottom of the GRASS-CVS-ssh instructions, in copy to the~~ GRASS-PSC chair (currently Markus Neteler).		Once SVN access is granted, the requestor needs to obtain an "osgeo_id" at http://www.osgeo.org/osgeo_userid
			If s/he already have an "osgeo_id" but forgot it, it can be searched at http://www.osgeo.org/cgi-bin/ldap_web_search.py
			The GRASS-PSC chair (currently Markus Neteler) and other developers can add this "osgeo_id" to the OSGeo LDAP authentication system.

	Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).		Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).
Line 15:		Line 17:
	=== Then what? ===		=== Then what? ===

	Happy hacking :) The requestor should subscribe to the [http://~~grass~~.~~itc~~.it/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-~~CVS~~ commit differences for real-time code review.		Happy hacking :) The requestor should subscribe to the [http://lists.osgeo.org/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-SVN commit differences for real-time code review.

	[[Category: PSC]]		[[Category: PSC]]
	[[Category:Development]]		[[Category:Development]]

Neteler: Requesting CVS write access moved to Requesting SVN write access: new repo

2008-02-06T08:41:42Z

Requesting CVS write access moved to Requesting SVN write access: new repo

← Older revision		Revision as of 08:41, 6 February 2008
(No difference)

Neteler: Category:Development

2007-07-05T14:10:42Z

Category:Development

← Older revision		Revision as of 14:10, 5 July 2007
Line 18:		Line 18:

	[[Category: PSC]]		[[Category: PSC]]
			[[Category:Development]]

Neteler: grass-commit

2007-06-23T12:17:31Z

grass-commit

← Older revision		Revision as of 12:17, 23 June 2007
Line 12:		Line 12:

	Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).		Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).

			=== Then what? ===

			Happy hacking :) The requestor should subscribe to the [http://grass.itc.it/mailman/listinfo/grass-commit grass-commit] mailing list which distributes GRASS-CVS commit differences for real-time code review.

	[[Category: PSC]]		[[Category: PSC]]

Neteler: extended

2007-06-02T19:39:17Z

extended

← Older revision		Revision as of 19:39, 2 June 2007
Line 9:		Line 9:
	=== Setting up CVS write access ===		=== Setting up CVS write access ===

	Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled.		Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled. The public SSH key should be sent to Bernhard Reiter (email address at page bottom of the GRASS-CVS-ssh instructions, in copy to the GRASS-PSC chair (currently Markus Neteler).

	Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).		Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).

	[[Category: PSC]]		[[Category: PSC]]

Neteler: extended

2007-06-02T07:41:51Z

extended

← Older revision		Revision as of 07:41, 2 June 2007
Line 1:		Line 1:
	=== Procedure to request CVS write access ===		=== Procedure to request CVS write access ===

	The [[GRASS Project Steering Commitee~~\|PSC~~]] is responsible for granting CVS write access to contributors (as defined in [http://mpa.itc.it/markus/grass63progman/rfc/rfc1_psc.html RFC1]).		The [[PSC\|GRASS Project Steering Commitee]] is responsible for granting CVS write access to contributors (as defined in [http://mpa.itc.it/markus/grass63progman/rfc/rfc1_psc.html RFC1]).

	The requestor has to '''read and accept''' the document [http://mpa.itc.it/markus/grass63progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2). ~~Contributions have~~ to ~~follow~~ the [~~[Working with CVS\|code submission guidelines~~]~~] (see also SUBMITTING* files in~~ the ~~source code)~~.		* The requestor has to '''read and accept''' the document [http://mpa.itc.it/markus/grass63progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2).

			* The request has to be send to the GRASS-PSC mailing list, stating that RFC2 was read and accepted. This requires [http://grass.itc.it/mailman/listinfo/grass-psc subscription] to the mailing list.

	=== Setting up CVS write access ===		=== Setting up CVS write access ===
Line 9:		Line 11:
	Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled.		Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled.

			Contributions have to follow the [[Working with CVS\|code submission guidelines]] (see also SUBMITTING* files in the source code).

	[[Category: PSC]]		[[Category: PSC]]

Neteler: new document

2007-06-02T07:37:12Z

new document

New page

=== Procedure to request CVS write access ===

The [[GRASS Project Steering Commitee|PSC]] is responsible for granting CVS write access to contributors (as defined in [http://mpa.itc.it/markus/grass63progman/rfc/rfc1_psc.html RFC1]).

The requestor has to '''read and accept''' the document [http://mpa.itc.it/markus/grass63progman/rfc/rfc2_psc.html Legal aspects of code contributions] (RFC2). Contributions have to follow the [[Working with CVS|code submission guidelines]] (see also SUBMITTING* files in the source code).

=== Setting up CVS write access ===

Once CVS access is granted, the requestor should follow the [http://freegis.org//grass/howto_grass-sshcvs.en.html GRASS-CVS-ssh instructions] to get the write access enabled.

[[Category: PSC]]