2017 Winter Project Week/UpdatingCommunityForums - Revision history

Fedorov: /* Background and References */

2017-01-13T15:45:48Z

Background and References

2017-01-13T15:45:31Z

Project Description

2017-01-11T23:18:25Z

Requirements

2017-01-11T20:00:46Z

2017-01-11T19:45:23Z

Background and References

2017-01-11T03:55:38Z

Background and References

2017-01-11T03:47:41Z

Decision-making policy draft

2017-01-11T03:46:25Z

Decision-making policy draft

2017-01-11T03:46:03Z

2017-01-11T03:41:45Z

Project Description

@@ Line 75: / Line 75: @@
 * https://experts.feverbee.com/t/discourse-vs-nodebb/1384/6
 * Comparison of forum software: https://en.wikipedia.org/wiki/Comparison_of_Internet_forum_software
 ==Requirements==

@@ Line 49: / Line 49: @@
 ** Participants: Ron, JC, Steve, Andras, Isaiah, Csaba, Andrey
 ** Specific to mailing list to forum migration, Ron's main concern is that with recurring payments there is a possibility of things falling through the cracks and potential interruption of the service
 |}

@@ Line 77: / Line 77: @@
 * [high] Import existing users
 * [high] Code highlight
 * [medium] Authentication with github
 * [medium] Option for yearly billing

@@ Line 76: / Line 76: @@
 * [high] Get email notification about specific themes (releases, announcements, sub-community, such as shape analysis, RT, ...)
 * [high] Import existing users
 * [medium] Authentication with github
 * [medium] Option for yearly billing
 * [medium] Polls (vote on features to be developed, collect community feedback for decisions, etc)
 * [low] Answer posts through email
 * [low] Vote for good answers, mark accepted answer

← Older revision		Revision as of 19:45, 11 January 2017
Line 72:		Line 72:
	* https://experts.feverbee.com/t/discourse-vs-nodebb/1384/6		* https://experts.feverbee.com/t/discourse-vs-nodebb/1384/6
	* Comparison of forum software: https://en.wikipedia.org/wiki/Comparison_of_Internet_forum_software		* Comparison of forum software: https://en.wikipedia.org/wiki/Comparison_of_Internet_forum_software
		+
		+	==Requirements==
		+	* [high] Get email notification about specific themes (releases, announcements, sub-community, such as shape analysis, RT, ...)
		+	* [high] Import existing users
		+	* [medium] Authentication with github
		+	* [medium] Option for yearly billing
		+	* [medium] Polls (vote on features to be developed, collect community feedback for decisions, etc)
		+	* [low] Answer posts through email
		+	* [low] Vote for good answers, mark accepted answer

← Older revision		Revision as of 03:55, 11 January 2017
Line 71:		Line 71:
	* NodeBB - like Discourse https://nodebb.org/pricing		* NodeBB - like Discourse https://nodebb.org/pricing
	* https://experts.feverbee.com/t/discourse-vs-nodebb/1384/6		* https://experts.feverbee.com/t/discourse-vs-nodebb/1384/6
		+	* Comparison of forum software: https://en.wikipedia.org/wiki/Comparison_of_Internet_forum_software

@@ Line 58: / Line 58: @@
 . Take the discussion off the general list, work on the analysis of options and alternatives, summarize findings on the wiki or similar
-. Announce the in-depth discussion of the topic for the Slicer Community hangout, encourage anyone that is interested in weighing in on the topic to join the discussion (Note: we might want to advertise Slicer Hangout appropriately, include agenda in the announcement email directly, and advertise the event to Slicer users as well as developers)
+. Announce the in-depth discussion of the topic for the Slicer Community hangout, encourage anyone that is interested in weighing in on the topic to join the discussion. If there is someone who is interested to participate in the discussion, but cannot join the meeting due to conflict, they should notify the leaders of the given project and identify the time suitable for everyone. (Note: we might want to advertise Slicer Hangout appropriately, include agenda in the announcement email directly, and advertise the event to Slicer users as well as developers)
 . Hopefully, reach consensus at the hangout and proceed with the agreed plan.

@@ Line 53: / Line 53: @@
 ==Decision-making policy draft==
 . Given the topic of interest, initiate discussion on the mailing list
 . Identify a small circle of community members that are interested to study the topic in more depth
 . Take the discussion off the general list, work on the analysis of options and alternatives, summarize findings on the wiki or similar
 . Announce the in-depth discussion of the topic for the Slicer Community hangout, encourage anyone that is interested in weighing in on the topic to join the discussion (Note: we might want to advertise Slicer Hangout appropriately, include agenda in the announcement email directly, and advertise the event to Slicer users as well as developers)
 . Hopefully, reach consensus at the hangout and proceed with the agreed plan.

@@ Line 50: / Line 50: @@
 ** Specific to mailing list to forum migration, Ron's main concern is that with recurring payments there is a possibility of things falling through the cracks and potential interruption of the service
 |}
 ==Background and References==

@@ Line 46: / Line 46: @@
+|
 <!-- Progress and Next steps bullet points (fill out at the end of project week) -->
+* Discussion took place about general principles of the decision making process (outlined below)
 |}