Design Workflow - Revision history

Nozmajner: Removing mailing list and simplifying a bit.

2017-09-03T09:29:56Z

Removing mailing list and simplifying a bit.

Aza at 08:03, 16 June 2017

2017-06-16T08:03:36Z

Ae-2222 at 07:45, 7 September 2012

2012-09-07T07:45:01Z

Ae-2222 at 07:36, 7 September 2012

2012-09-07T07:36:48Z

Ae-2222 at 07:35, 7 September 2012

2012-09-07T07:35:46Z

Ae-2222 at 07:25, 7 September 2012

2012-09-07T07:25:27Z

Ae-2222 at 07:23, 7 September 2012

2012-09-07T07:23:30Z

Ae-2222 at 07:17, 7 September 2012

2012-09-07T07:17:45Z

Ae-2222 at 07:16, 7 September 2012

2012-09-07T07:16:09Z

Ae-2222 at 07:15, 7 September 2012

2012-09-07T07:15:29Z

@@ Line 1: / Line 1: @@
-Table thingy outlining the appropriate places for use at different stages of the workflow for both design and resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.
+Table thingy outlining the appropriate places for use at different stages of the workflow for both design and resolution of issues.
 {| class="wikitable"
@@ Line 11: / Line 11: @@
 ! '''Stage 3.'''
 Documenting outcomes<br/> (When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)
@@ Line 19: / Line 16: @@
 | '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
 | '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
-| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
+| '''Wiki for Docs.'''
 |-
 | '''Forums'''
-| '''Mailing list''' - Discussion of project policy or wider design issues
+| '''Forums, IRC'''
 | Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
 |}
-The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.
+The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github''&nbsp;or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.
 '''''If a new Policy or Design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''
 [[Category:Design]]

@@ Line 1: / Line 1: @@
 Table thingy outlining the appropriate places for use at different stages of the workflow for both design and resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.
 {| class="wikitable"
 |-
-! '''Stage 1.
+! '''Stage 1.'''
-Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community''' <br />(purely optional)
+Informally bounce ideas off people to see if they are worth bringing to the attention of the entire community<br/> '''(purely optional)'''
 ! '''Stage 2.
-Put things up for discussion'''
+! '''Stage 2.'''
-! '''Stage 3.
+Put things up for discussion
-Detailed discussion'''
-! '''Stage 4.
+! '''Stage 3.'''
-Documenting outcomes <br />(When a solution has been found or discussion has slowed down/stalled and is unlikely to resume in the near future)'''
+Detailed discussion
 |-
 | '''IRC''' - the most feedback. Engine room of opensource projects and used for collaboration ''exlusively'' by a lot of contributors.
-|| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
+| '''Issue tracker''' - is focused enough to allow immediate solution. ''Workflow ends here.''
-|| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
+| '''Mailing list''' and possibly a '''pirate pad''' for issues that are too extensive or benefit from realtime or re-structurability aspects.
-|| '''Wiki'''
+| '''Wiki'''
 |-
 | '''Forums'''
-|| '''Mailing list''' - Discussion of project policy or wider design issues
+| '''Mailing list''' - Discussion of project policy or wider design issues
-|| It's possible to use wiki pages like a piratepad
+| It's possible to use wiki pages like a piratepad
-|| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
+| Multiple issues in '''Issue tracker''' - ''focused'' and ''implementable'' tasks
 |-
+| &nbsp;
-|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
+| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
-||
+| &nbsp;
-||
+| &nbsp;
 |}
 The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.
 '''''If a new Policy or Design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

← Older revision		Revision as of 07:45, 7 September 2012
Line 1:		Line 1:
−	Table thingy of ~~Workflow~~ for design/resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.	+	Table thingy outlining the appropriate places for use at different stages of the workflow for both design and resolution of issues. Experimenting with tables:). Still WIP, feel free to reformat/fix/make clearer.

	{\| class="wikitable"		{\| class="wikitable"

← Older revision		Revision as of 07:36, 7 September 2012
Line 30:		Line 30:
	The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.		The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.

−	'''''If a new Policy~~/design~~ issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''	+	'''''If a new Policy or Design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

@@ Line 28: / Line 28: @@
 |}
-The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later.
+The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are ''available only through Github/mailinglist'' or forum for collaboration and new contributors only observe ''Github or the Wiki''. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not ''visible to the critical audience'', it ''disturbs the process of reviewing'' a Pull Request or discussing the present issue, and it ''makes things hard to find'' later.
-''If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)''
+'''''If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)'''''

← Older revision		Revision as of 07:25, 7 September 2012
Line 28:		Line 28:
	\|}		\|}

−	The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later. If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)	+	The different media for communication are there for a reason. For instance, discussion on the IRC cannot be regarded as official, as it's not used as a medium of collaboration by all - some contributors are available only through Github/mailinglist or forum for collaboration and new contributors only observe Github or the Wiki. Similarly it is not appropriate to discuss aspects of ''project management/policy or non-relevant topics'' in a focused Github Issue or on a Pull Request - it is not visible to the critical audience, it disturbs the process of reviewing a Pull Request or discussing the present issue, and it makes things hard to find later.
		+
		+	''If a new Policy/design issue arises during a Pull Request,Issue, or Discussion please follow the stages above:)''

@@ Line 23: / Line 23: @@
 |-
+|
-|| Detailed proposal on '''Wiki''' then linked to '''mailing list'''
+|| Detailed proposal on the '''Wiki''' then linked to the '''Mailing list'''
 ||
 ||