White Papers - Revision history

Chris Davenport: Categorisation.

2008-11-03T18:36:43Z

Categorisation.

CirTap: /* Submitting White Papers */

2008-03-23T17:09:30Z

‎Submitting White Papers

CirTap: forum link, new URL format

2008-03-07T20:32:39Z

forum link, new URL format

Chris Davenport: /* Why a white paper approach? */

2008-02-21T17:41:43Z

‎Why a white paper approach?

MasterC: /* Special Exception for Minor Changes */

2008-02-21T00:25:10Z

‎Special Exception for Minor Changes

MasterC: Fixed some minor typos / gramatical errors

2008-02-21T00:09:18Z

Fixed some minor typos / gramatical errors

Masterchief: /* Exception for minor changes */

2008-02-14T11:27:30Z

‎Exception for minor changes

Willebil at 21:31, 10 February 2008

2008-02-10T21:31:25Z

Masterchief: /* Why a white paper approach? */

2008-02-07T23:47:28Z

‎Why a white paper approach?

Masterchief at 23:36, 7 February 2008

2008-02-07T23:36:44Z

@@ Line 74: / Line 74: @@
 The remainder of the papers are moved out of ''Under Review'' (link?) back into the main white paper forum, unless they have been deemed to be something that can't or won't be implemented, in which case they are moved to ''Not accepted''.  Over time guidelines for what things are likely not to be accepted will be established, and also templates by which people can submit white papers.
+<noinclude>[[Category:Development Working Group]]</noinclude>
 [[Category:Development]]

@@ Line 36: / Line 36: @@
 ==Submitting White Papers==
-White Papers are submitted on a specical sub-forum; http://forum.joomla.org/viewforum.php?f=500. This is open to the public. It has sub-forums for "Accepted", "Under review" and "Not Accepted" into which threads are moved during the review process.
+White Papers are submitted on a {{jforum|wp|special sub-forum|}}. This is open to the public. It has sub-forums for "Accepted", "Under review" and "Not Accepted" into which threads are moved during the review process.
 A white-paper topic would be started as a thread. The author(s) must briefly outline what it is in the thread-starter, but from there the actual content of the paper can be anywhere, provided it is publically available. Examples would be a public Google Doc, a wiki page, a content item on a website, a downloadable PDF, or text within the thread itself.  The media doesn't really matter providing that drafts are publically viewable.  A simple approach is to keep the ''master'' text in the original topic, and make changes to it as you received feedback.

@@ Line 36: / Line 36: @@
 ==Submitting White Papers==
-White Papers are submitted on a specical sub-forum; http://forum.joomla.org/index.php/board,500.0.html. This is open to the public. It has sub-forums for "Accepted", "Under review" and "Not Accepted" into which threads are moved during the review process.
+White Papers are submitted on a specical sub-forum; http://forum.joomla.org/viewforum.php?f=500. This is open to the public. It has sub-forums for "Accepted", "Under review" and "Not Accepted" into which threads are moved during the review process.
 A white-paper topic would be started as a thread. The author(s) must briefly outline what it is in the thread-starter, but from there the actual content of the paper can be anywhere, provided it is publically available. Examples would be a public Google Doc, a wiki page, a content item on a website, a downloadable PDF, or text within the thread itself.  The media doesn't really matter providing that drafts are publically viewable.  A simple approach is to keep the ''master'' text in the original topic, and make changes to it as you received feedback.

@@ Line 8: / Line 8: @@
 Second this new mechanism is ''community driven''.
-This simply means that all input into the ''next'' release will come from anyone in the community, not just Development Workgroup Members. This is done to prevent scope creep mid-release, and also to actually get a feel for what community wants. Joomla! is an effort from a group of developers. It is important to embrace the talents that are in this group. But equally important is the opinion of, and the social responsibility we have to the millions of site owners.  An open and transparent process like this allows for significantly more people to have their opinions and ideas heard.
+This simply means that all input into the ''next'' release will come from anyone in the community, not just Development Workgroup Members. This is done to prevent scope creep mid-release, and also to actually get a feel for what the community wants. Joomla! is an effort from a group of developers. It is important to embrace the talents that are in this group. But equally important is the opinion of, and the social responsibility we have, to the millions of site owners.  An open and transparent process like this allows for significantly more people to have their opinions and ideas heard.
 ==Who can post white papers?==

@@ Line 47: / Line 47: @@
 ===Special Exception for Minor Changes===
-We are giving a special expection for very minor issues that people might like to bring up, but that are too trivial to warrant writing a full paper on the subject.  For these cases we will have a sticky thread for submitting minor issues.  Moderators will monitor this thread and any issue that are deemed to need more input will be split off and a full White Paper will be requested.
+We are giving a special exception for very minor issues that people might like to bring up, but that are too trivial to warrant writing a full paper on the subject.  For these cases we will have a sticky thread for submitting minor issues.  Moderators will monitor this thread and any issue that are deemed to need more input will be split off and a full White Paper will be requested.
 This thread will actually be closed during the review process simply to help with the logistics of processing it.

@@ Line 2: / Line 2: @@
 A white paper is more or less a formal "feature request".  The idea behind this is to change the mechanics of how development is done.
-Firstly it's ''planned''.
+First it's ''planned''.
 When a white paper is accepted everyone knows what is supposed to be achieved and there is a clear milestone that can be achieved.  With this approach we also can interact more effectively with the other working groups like documentation earlier in the process rather than later.
-Secondly this new mechanism is ''community driven''.
+Second this new mechanism is ''community driven''.
-This simply means that all input into the ''next'' release will come from anyone in the community, not just Development Workgroup Members. This is done to prevent scope creep mid-release, and also to actually get a feel for what community wants. Joomla! is an effort from a group of developers. It is important to embrace the talents that are in this group. But equally important is the opinion of, and the social responsibility we have to the many of the millions of site owners.  An open and transparent process like this allows for many more people to have their opinions and ideas heard.
+This simply means that all input into the ''next'' release will come from anyone in the community, not just Development Workgroup Members. This is done to prevent scope creep mid-release, and also to actually get a feel for what community wants. Joomla! is an effort from a group of developers. It is important to embrace the talents that are in this group. But equally important is the opinion of, and the social responsibility we have to the millions of site owners.  An open and transparent process like this allows for significantly more people to have their opinions and ideas heard.
 ==Who can post white papers?==

← Older revision		Revision as of 11:27, 14 February 2008
Line 45:		Line 45:

	At this time, polls are not permitted as we want to encourage a process of peer review rather than anonymous voting.		At this time, polls are not permitted as we want to encourage a process of peer review rather than anonymous voting.
		+
		+	===Special Exception for Minor Changes===
		+	We are giving a special expection for very minor issues that people might like to bring up, but that are too trivial to warrant writing a full paper on the subject. For these cases we will have a sticky thread for submitting minor issues. Moderators will monitor this thread and any issue that are deemed to need more input will be split off and a full White Paper will be requested.
		+
		+	This thread will actually be closed during the review process simply to help with the logistics of processing it.

	==Planning==		==Planning==

← Older revision		Revision as of 23:36, 7 February 2008
Line 69:		Line 69:

	The remainder of the papers are moved out of ''Under Review'' (link?) back into the main white paper forum, unless they have been deemed to be something that can't or won't be implemented, in which case they are moved to ''Not accepted''. Over time guidelines for what things are likely not to be accepted will be established, and also templates by which people can submit white papers.		The remainder of the papers are moved out of ''Under Review'' (link?) back into the main white paper forum, unless they have been deemed to be something that can't or won't be implemented, in which case they are moved to ''Not accepted''. Over time guidelines for what things are likely not to be accepted will be established, and also templates by which people can submit white papers.
		+
		+	[[Category:Development]]