Difference between revisions of "Vote to Replace Google Groups with Discourse Forum"

From Pumping Station One
Jump to navigation Jump to search
 
(8 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
* Andrew Camardella
 
* Andrew Camardella
 
* Alex Berkowitz
 
* Alex Berkowitz
 +
* Sky Nova
  
 
== History ==
 
== History ==
Line 14: Line 15:
 
The Private Google Groups is the main form of communication for members, and accounts for the majority of communications with regards to authorizations and pertinent space information. Due to it's flat and simple format there are many issues that arise with this communication channel. In particular:
 
The Private Google Groups is the main form of communication for members, and accounts for the majority of communications with regards to authorizations and pertinent space information. Due to it's flat and simple format there are many issues that arise with this communication channel. In particular:
 
*all messages are sent to everyone (you can't tune out discussions you aren't interested in).
 
*all messages are sent to everyone (you can't tune out discussions you aren't interested in).
*sorting and finding specific information is difficult.
+
*sorting and finding specific information is difficult
*no community standards or moderation options.
+
*minimal community standards or moderation options
 
*signing up new members and removing old members is completely manual
 
*signing up new members and removing old members is completely manual
 
*low new member engagement
 
*low new member engagement
 +
*no fine access control -- users can either see everything or see nothing
 +
*cannot be backed up, completely reliant on Google infrastructure
  
  
 
Discourse solves many of the issue with Google-Groups because it:
 
Discourse solves many of the issue with Google-Groups because it:
*is a well-thought-out modern forum that is feature rich and geared specifically to generate quality civilized discussion.
+
*modern open source forum that is feature rich and geared specifically to encourage relevant and valuable discussion
*can be used to combine our public and private google groups by using category tags with permissions.
+
*is actively developed and updated
*has an amazing code of conduct that is reflected in the design of the forum and that dovetails with our own policies.
+
*can be used to combine our public and private google groups by using category tags with permissions
*works through email clients just like Google Groups does.
+
*supports mailing list emulation
*can interface with our member database which means new users are automatically added when they create their PS:One user account and deactivated when they leave. This automates the current process board members go through.
+
*can be integrated with existing automated systems to provision accounts for new members, which lowers the bar for engagement and community discussion
 +
*can be backed up, the organization owns and operates the instance
 +
*has a community of developers for support
 +
*offers a rich toolset for moderation
  
==Cost==
+
== Cost ==
As we already have an instance of Discourse running, and hosting costs are already included in the CTO's budget, there are no new costs to the organization that this change will introduce.
+
As we already have an instance of Discourse running, and hosting costs are already included in the CTO's budget, there are minimal new costs to the organization that this change will introduce. The only future cost increases would be a result of increased use of Discourse.
 +
 
 +
== Archival ==
 +
 
 +
The board will lock the Google Groups but all existing members will retain access for historical reference. There is not currently a known method of extracting or archiving a Google Groups instance due to the lack of development by Google.  
 
   
 
   
 
== Language ==
 
== Language ==
  
* We authorize the board to use Discourse as the main member forum sanctioned by Pumping Station: One, NFP.
+
* The Membership authorizes the Board to switch to Discourse as the main member forum sanctioned by Pumping Station: One, NFP, to take effect following a transitional period of three months from the time of the passing of this vote.
* We authorize the board to lock out the Public and Private Google Groups from additional posts after as long as it remains available to the membership for review and historical information.
+
* The Membership authorizes the Board to lock the Public and Private Google Groups from additional posts at the end of the stated transitional period, and to ensure the contents therein remain available to the membership as a historical record.
  
 
== Results ==
 
== Results ==
Quorum: The number of votes required to have a valid vote (1/3rd of the full members must vote, check [http://members.pumpingstationone.org the member site]. If the vote doesn't meet quorum it will have to be proposed again, and can be voted on the following week (consider campaigning for your particular vote).
+
Quorum: The number of votes required to have a valid vote (ten percent (10%) of the Membership]. If the vote doesn't meet quorum it will have to be proposed again, and can be voted on the following week (consider campaigning for your particular vote).
 
Yay: This is the number of members that vote but that agree with the vote language.
 
Yay: This is the number of members that vote but that agree with the vote language.
 
Nay: This is the number of members that vote but that disagree with the vote language.
 
Nay: This is the number of members that vote but that disagree with the vote language.

Latest revision as of 04:20, 26 November 2019

Sponsors

  • Andrew Camardella
  • Alex Berkowitz
  • Sky Nova

History

  • Announced:
  • Language locked:
  • Voted on:

Background

The Private Google Groups is the main form of communication for members, and accounts for the majority of communications with regards to authorizations and pertinent space information. Due to it's flat and simple format there are many issues that arise with this communication channel. In particular:

  • all messages are sent to everyone (you can't tune out discussions you aren't interested in).
  • sorting and finding specific information is difficult
  • minimal community standards or moderation options
  • signing up new members and removing old members is completely manual
  • low new member engagement
  • no fine access control -- users can either see everything or see nothing
  • cannot be backed up, completely reliant on Google infrastructure


Discourse solves many of the issue with Google-Groups because it:

  • modern open source forum that is feature rich and geared specifically to encourage relevant and valuable discussion
  • is actively developed and updated
  • can be used to combine our public and private google groups by using category tags with permissions
  • supports mailing list emulation
  • can be integrated with existing automated systems to provision accounts for new members, which lowers the bar for engagement and community discussion
  • can be backed up, the organization owns and operates the instance
  • has a community of developers for support
  • offers a rich toolset for moderation

Cost

As we already have an instance of Discourse running, and hosting costs are already included in the CTO's budget, there are minimal new costs to the organization that this change will introduce. The only future cost increases would be a result of increased use of Discourse.

Archival

The board will lock the Google Groups but all existing members will retain access for historical reference. There is not currently a known method of extracting or archiving a Google Groups instance due to the lack of development by Google.

Language

  • The Membership authorizes the Board to switch to Discourse as the main member forum sanctioned by Pumping Station: One, NFP, to take effect following a transitional period of three months from the time of the passing of this vote.
  • The Membership authorizes the Board to lock the Public and Private Google Groups from additional posts at the end of the stated transitional period, and to ensure the contents therein remain available to the membership as a historical record.

Results

Quorum: The number of votes required to have a valid vote (ten percent (10%) of the Membership]. If the vote doesn't meet quorum it will have to be proposed again, and can be voted on the following week (consider campaigning for your particular vote). Yay: This is the number of members that vote but that agree with the vote language. Nay: This is the number of members that vote but that disagree with the vote language. Present: This is the total number of members that voted (physically present and by proxy) and includes those that abstained from voting.