Contributing - Revision history

Carignani at 12:56, 9 March 2020

2020-03-09T12:56:05Z

← Older revision		Revision as of 14:56, 9 March 2020
Line 4:		Line 4:

	The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.<blockquote>Important: please note that the document preparation is in progress. The preview is given to allow feedback and participation but needs to be refined before use in ETSI groups.</blockquote>For inquiries and suggestions, contact cti_support at etsi dot org.		The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.<blockquote>Important: please note that the document preparation is in progress. The preview is given to allow feedback and participation but needs to be refined before use in ETSI groups.</blockquote>For inquiries and suggestions, contact cti_support at etsi dot org.

			== How ETSI Groups use Forge in their processes ==
			{\| class="wikitable"
			!Group
			!Title
			!Reference
			!Link
			\|-
			\|3GPP
			\|Discussion papers
			\|
			\|[[ETSI Forge for 3GPP APIs]]
			\|-
			\|ISG NFV - TST WG
			\|ISG NFV, TST WG, Contribution and review process for Forge
			\|NFVTST(19)000269r3
			\|[https://docbox.etsi.org/ISG/NFV/TST/05-CONTRIBUTIONS/2019/NFVTST(19)000269r3_New_Procedure_for_TD_review_in_gitlab.pptx Download]
			\|-
			\|ISG NFV -TST WG
			\|ISG NFV
			\|NFVTST(20)000015r1
			\|[https://docbox.etsi.org/ISG/NFV/TST/05-CONTRIBUTIONS/2020//NFVTST(20)000015r1_Branching_and_tagging_strategy_for_Forge_repository.zip Download]
			\|}

	== Process documentation ==		== Process documentation ==

Carignani at 16:37, 13 January 2020

2020-01-13T16:37:06Z

← Older revision		Revision as of 18:37, 13 January 2020
Line 3:		Line 3:
	The goal is to enable ETSI TBs and ISGs to adopt best practices for management of code when dealing with formal and machine-readable languages in the specification process.		The goal is to enable ETSI TBs and ISGs to adopt best practices for management of code when dealing with formal and machine-readable languages in the specification process.

	The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.		The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.<blockquote>Important: please note that the document preparation is in progress. The preview is given to allow feedback and participation but needs to be refined before use in ETSI groups.</blockquote>For inquiries and suggestions, contact cti_support at etsi dot org.

	For inquiries and suggestions, contact cti_support at etsi dot org.

	== Process documentation ==		== Process documentation ==

Carignani at 15:51, 13 January 2020

2020-01-13T15:51:42Z

← Older revision		Revision as of 17:51, 13 January 2020
Line 9:		Line 9:
	== Process documentation ==		== Process documentation ==

	<big>Detailed documentation is maintained at</big><blockquote><big>https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation.</big></blockquote><u>Your contributions are welcome</u>!		<blockquote><big>[https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation/-/jobs/artifacts/master/raw/Forge-contribution-process.docx?job=doc Download the latest version in Docx version]</big></blockquote><big>Detailed documentation is maintained at</big><blockquote><big>https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation.</big></blockquote><u>Your contributions are welcome</u>!

	To provide feedback or proposing changes, log into Forge with your EOL account and click on '''Request access''' link.		To provide feedback or proposing changes, log into Forge with your EOL account and click on '''Request access''' link.
Line 16:		Line 16:

	== Overall process ==		== Overall process ==
	[[File:Forge-~~and~~-~~Portal~~-~~process~~.png\|center\|frameless\|~~455x455px~~]]		[[File:Forge-contrib-process-v1.png\|center\|frameless\|1023x1023px]]

Carignani at 07:12, 5 December 2019

2019-12-05T07:12:31Z

← Older revision		Revision as of 09:12, 5 December 2019
Line 9:		Line 9:
	== Process documentation ==		== Process documentation ==

	Detailed documentation is maintained at https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation.		<big>Detailed documentation is maintained at</big><blockquote><big>https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation.</big></blockquote><u>Your contributions are welcome</u>!

	~~Your contributions are welcome!~~ To provide feedback or proposing changes, log into Forge with your EOL account and click on '''Request access''' link.		To provide feedback or proposing changes, log into Forge with your EOL account and click on '''Request access''' link.

	To file an issue, you may follow the procedure illustrated [[How to report a bug#Report a bug on Gitlab\|here]].		To file an issue, you may follow the procedure illustrated [[How to report a bug#Report a bug on Gitlab\|here]].

Carignani at 07:06, 5 December 2019

2019-12-05T07:06:55Z

← Older revision		Revision as of 09:06, 5 December 2019
Line 9:		Line 9:
	== Process documentation ==		== Process documentation ==

	~~A detailed~~ documentation ~~on contributing recommendations and guidelines will be published here~~. ~~Stay tuned!~~		Detailed documentation is maintained at https://forge.etsi.org/rep/etsi-cti-admin/forge-contributions-documentation.

			Your contributions are welcome! To provide feedback or proposing changes, log into Forge with your EOL account and click on '''Request access''' link.

			To file an issue, you may follow the procedure illustrated [[How to report a bug#Report a bug on Gitlab\|here]].

	== Overall process ==		== Overall process ==
	[[File:Forge-and-Portal-process.png\|center\|frameless\|455x455px]]		[[File:Forge-and-Portal-process.png\|center\|frameless\|455x455px]]

Carignani at 13:35, 19 November 2019

2019-11-19T13:35:16Z

← Older revision		Revision as of 15:35, 19 November 2019
Line 9:		Line 9:
	== Process documentation ==		== Process documentation ==

	~~Find the~~ detailed documentation on contributing recommendations and guidelines ~~at the link below~~.		A detailed documentation on contributing recommendations and guidelines will be published here. Stay tuned!

Carignani at 14:06, 18 November 2019

2019-11-18T14:06:21Z

← Older revision		Revision as of 16:06, 18 November 2019
Line 14:		Line 14:

	== Overall process ==		== Overall process ==
			[[File:Forge-and-Portal-process.png\|center\|frameless\|455x455px]]

Carignani at 13:42, 18 November 2019

2019-11-18T13:42:28Z

← Older revision		Revision as of 15:42, 18 November 2019
Line 5:		Line 5:
	The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.		The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.

	~~## Contribution process~~		For inquiries and suggestions, contact cti_support at etsi dot org.

	~~Please find~~ the contributing recommendations and guidelines at		== Process documentation ==

			Find the detailed documentation on contributing recommendations and guidelines at the link below.



			== Overall process ==

Carignani: Created page with "This page describes a process for contributing and including software in normative and informative standardization. The goal is to enable ETSI TBs and ISGs to adopt best prac..."

2019-11-18T13:37:42Z

Created page with "This page describes a process for contributing and including software in normative and informative standardization. The goal is to enable ETSI TBs and ISGs to adopt best prac..."

New page

This page describes a process for contributing and including software in normative and informative standardization.

The goal is to enable ETSI TBs and ISGs to adopt best practices for management of code when dealing with formal and machine-readable languages in the specification process.

The foreseen benefit is to have a more efficient standardization process avoid multiple of content and costly maintenance.

## Contribution process

Please find the contributing recommendations and guidelines at