2017 Winter Project Week/UpdatingCommunityForums

From NAMIC Wiki
Jump to: navigation, search
Home < 2017 Winter Project Week < UpdatingCommunityForums

Key Investigators

  • Andrey Fedorov
  • Andras Lasso
  • Mike Halle
  • Steve Pieper
  • Isaiah Norton
  • Tina Kapur
  • Teodora Szasz

Project Description

Objective Approach and Plan Progress and Next Steps
  • Discuss the procedure for reaching consensus and making decision for the infrastructure issues that will have effect on large number of users
  • Consider mailing list proposal to move Slicer and possibly several related discussion forums to the Discourse platform.
  • Discuss new community-interaction possibilities such as Gitter.
  • Consider the long-discussed proposals to move to github hosting for the web site
  • Breakfast breakout discussion - Tuesday 8:30am - Ron is confirmed to join!
  • Document the procedure for reaching consensus and making decision for the infrastructure issues that will have effect on large number of users
  • Discourse
    • Assess Discourse with broader community.
    • Identify funding mechanism.
    • Logistics to move if chosen:
      • Hosting: fully-managed service? vs DigitalOcean or other provider?
      • Domain name: 'discourse.slicer.org'?
      • SSL certificate for domain: can use Letsencrypt after host and DNS record are configured
      • SMTP service: included in hosted option. For self-hosting: strongly recommended, and mandatory for email-only signup and mailing list mode; not mandatory if using only oauth provider (GitHub/Google/etc.)
  • GitHub
    • Identify remaining action items to complete the long-awaited move of Slicer source hosting to GitHub.
  • Web-site
    • Organize web-site content on github
    • Consider moving hosting to github
  • Discussion took place about general principles of the decision making process (outlined below)
    • 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
  • Gitter
    • in a small group discussion, decided against using gitter for Slicer community at least for now; although it would provide an advantage of having a place for developers to chat in real time and get quick help, we cannot guarantee critical mass of experienced developers participating, and it would not replace mailing list or forum
    • to support project week communication, propose to use gitter channel under github NA-MIC community that JC already created (contact JC to join); we could use that community to discuss projects and connect people in advance of the next project week

Decision-making policy draft

1. Given the topic of interest, initiate discussion on the mailing list

2. Identify a small circle of community members that are interested to study the topic in more depth

3. Take the discussion off the general list, work on the analysis of options and alternatives, summarize findings on the wiki or similar

4. 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)

5. Hopefully, reach consensus at the hangout and proceed with the agreed plan.

Background and References


  • [high] Get email notification about specific themes (releases, announcements, sub-community, such as shape analysis, RT, ...)
  • [high] Import existing users
  • [high] Code highlight
  • [high] indexing by Google
  • [medium] Authentication with github
  • [medium] Option for yearly billing
  • [medium] Polls (vote on features to be developed, collect community feedback for decisions, etc)
  • [medium] Permalinks of thread for easy sharing by email
  • [low] Answer posts through email
  • [low] Vote for good answers, mark accepted answer
  • [low] Support cross referencing of Github issues