New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate discourse #306

Closed
johnmckerrell opened this Issue Jun 14, 2016 · 19 comments

Comments

Projects
None yet
7 participants
@johnmckerrell
Member

johnmckerrell commented Jun 14, 2016

No description provided.

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Jun 14, 2016

got one online (on a 7 day free trial before being billed $20 a month) at http://doesliverpool.discoursehosting.net

DefProc commented Jun 14, 2016

got one online (on a 7 day free trial before being billed $20 a month) at http://doesliverpool.discoursehosting.net

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Jun 14, 2016

It's working, bar the incoming emails (which I've hit a bit of a wall with) I think the internet just needs to catch up with the new gmail account I created!

It's interesting that if the incoming mail stuff does work, we may be able to retire supportbee, as discourse should be able to do the "message a group of people when incoming emails arrive"

DefProc commented Jun 14, 2016

It's working, bar the incoming emails (which I've hit a bit of a wall with) I think the internet just needs to catch up with the new gmail account I created!

It's interesting that if the incoming mail stuff does work, we may be able to retire supportbee, as discourse should be able to do the "message a group of people when incoming emails arrive"

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Jun 15, 2016

Right, incoming email and outgoing email seem to work OK

DefProc commented Jun 15, 2016

Right, incoming email and outgoing email seem to work OK

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Jun 20, 2016

We're just about to go over the 7 day threshold, and have to pay the first month's hosting for this trial.

As we're only up to 8 users, I'd recommend letting this one run, to at least see if there's more traction with this. So unless anybody objects I'll let this trial continue for a few more weeks.

DefProc commented Jun 20, 2016

We're just about to go over the 7 day threshold, and have to pay the first month's hosting for this trial.

As we're only up to 8 users, I'd recommend letting this one run, to at least see if there's more traction with this. So unless anybody objects I'll let this trial continue for a few more weeks.

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Oct 4, 2016

Member

What are we aiming to achieve with moving to Discourse? How do we decide if we're going to move to it? How are we going to manage the people side of moving across (if we decide to move)? (Telling people it's happening, the timescale for expressing opinions one way or t'other, etc.)

Member

amcewen commented Oct 4, 2016

What are we aiming to achieve with moving to Discourse? How do we decide if we're going to move to it? How are we going to manage the people side of moving across (if we decide to move)? (Telling people it's happening, the timescale for expressing opinions one way or t'other, etc.)

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Oct 4, 2016

It should allow us to replace support bee (which is just going up in
price), allow for group emails a la #244, and replace the Google group with
a nicer to use mailing list with easier public access.

I'd suggest if the organisers agree that the demo's suitable, and there's
no good objections from the community, that would be enough to move across.

Other hackspace migrations notified in their original group, migrated the
discussions and then switched at a set date, setting the original group
read only from that point.

Migration of the discussion threads should create user accounts with the
same email addresses, which can then be claimed in Discourse. These can
still be used via email without any new login.

On 4 Oct 2016 19:15, "Adrian McEwen" notifications@github.com wrote:

What are we aiming to achieve with moving to Discourse? How do we decide if
we're going to move to it? How are we going to manage the people side of
moving across (if we decide to move)? (Telling people it's happening, the
timescale for expressing opinions one way or t'other, etc.)


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#306 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAU72JR8SOkmERVpaRMOc3wfpEys_gTFks5qwpeGgaJpZM4I1Upv
.

DefProc commented Oct 4, 2016

It should allow us to replace support bee (which is just going up in
price), allow for group emails a la #244, and replace the Google group with
a nicer to use mailing list with easier public access.

I'd suggest if the organisers agree that the demo's suitable, and there's
no good objections from the community, that would be enough to move across.

Other hackspace migrations notified in their original group, migrated the
discussions and then switched at a set date, setting the original group
read only from that point.

Migration of the discussion threads should create user accounts with the
same email addresses, which can then be claimed in Discourse. These can
still be used via email without any new login.

On 4 Oct 2016 19:15, "Adrian McEwen" notifications@github.com wrote:

What are we aiming to achieve with moving to Discourse? How do we decide if
we're going to move to it? How are we going to manage the people side of
moving across (if we decide to move)? (Telling people it's happening, the
timescale for expressing opinions one way or t'other, etc.)


You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#306 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAU72JR8SOkmERVpaRMOc3wfpEys_gTFks5qwpeGgaJpZM4I1Upv
.

@cheapjack

This comment has been minimized.

Show comment
Hide comment
@cheapjack

cheapjack commented Oct 4, 2016

Comments between Ross & Patrick on Discourse

@amcewen

This comment has been minimized.

Show comment
Hide comment
@amcewen

amcewen Oct 4, 2016

Member

I can understand the arguments for replacing SupportBee (although would that mean everyone's email count would increase as you wouldn't have SupportBee's "person X replied first, so I'll just email them" feature? There are pros and cons to that :-D) and also for the group emails.

In what ways is it nicer to use than the Google Group?

It sounds like you're proposing that existing Google Group uses will have to actively do something to receive emails? Are we happy with all the users of the GG we'd lose as a result?

I'd be happier if there were more people arguing that we should make the move, or providing more arguments for what we'd gain. It feels like a technological fix for a social problem (not enough discussion within the community) to me at the moment.

Member

amcewen commented Oct 4, 2016

I can understand the arguments for replacing SupportBee (although would that mean everyone's email count would increase as you wouldn't have SupportBee's "person X replied first, so I'll just email them" feature? There are pros and cons to that :-D) and also for the group emails.

In what ways is it nicer to use than the Google Group?

It sounds like you're proposing that existing Google Group uses will have to actively do something to receive emails? Are we happy with all the users of the GG we'd lose as a result?

I'd be happier if there were more people arguing that we should make the move, or providing more arguments for what we'd gain. It feels like a technological fix for a social problem (not enough discussion within the community) to me at the moment.

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Oct 13, 2016

Although with Supportbee, I can't see if something's been replied to (although I thought it used to do that) without going to the web interface (which I don't do). And as one of the reasons to use Supportbee was so we could see other people's replies, so they didn't go out of the group email, this seems like a mark against Supportbee.

The signup specifically is easier, google groups requires a google account, and discourse will allow 3rd party logins (github is already enabled). The forum+ features means it has threaded and chronological ordering (without changing the view). The web interface acts like live chat, so incoming new posts will appear live in other users, so we get a friendlier web interface, plus the mailing list. And it allows breakout threads that stay linked to the original conversation (a la github issue cross references).

Other hackspaces (eg. Hackman) chose to default to the "mailing list mode" so post are automatically emailed out, rather than the current default for google groups where we currently list instructions on what to do to activate that. Using mailing list mode would encourage this result, but it's a judgement call if we'd want to change this behaviour.

I don't see it as just a "technological solution to a social problem" (we won't get discussion if there isn't any to have ), it specifically saves us money over supportbee, provides us with a solution to #244, follows the recommendation of #18.

DefProc commented Oct 13, 2016

Although with Supportbee, I can't see if something's been replied to (although I thought it used to do that) without going to the web interface (which I don't do). And as one of the reasons to use Supportbee was so we could see other people's replies, so they didn't go out of the group email, this seems like a mark against Supportbee.

The signup specifically is easier, google groups requires a google account, and discourse will allow 3rd party logins (github is already enabled). The forum+ features means it has threaded and chronological ordering (without changing the view). The web interface acts like live chat, so incoming new posts will appear live in other users, so we get a friendlier web interface, plus the mailing list. And it allows breakout threads that stay linked to the original conversation (a la github issue cross references).

Other hackspaces (eg. Hackman) chose to default to the "mailing list mode" so post are automatically emailed out, rather than the current default for google groups where we currently list instructions on what to do to activate that. Using mailing list mode would encourage this result, but it's a judgement call if we'd want to change this behaviour.

I don't see it as just a "technological solution to a social problem" (we won't get discussion if there isn't any to have ), it specifically saves us money over supportbee, provides us with a solution to #244, follows the recommendation of #18.

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Oct 25, 2016

I have a more customisable install running now on disourse.doesliverpool.com (once the DNS propogates to include 188.166.158.202) that has the google group posts imported, plus the user accounts and discussions from doesliverpool.discoursehosting.net. It's currently on a Digital Ocean droplet that I'm paying for. Still on doesliverpool.discoursehosting.net

There are a few things left to check:

  • check the google group posts are reasonably complete
  • relink the website so comments go to discourse
  • set the main url to community.doesliverpool.com (once the DNS propogates)
  • Incoming email (to aliases of a new community@doesliverpool.com account)
  • Groups and email replies (eg. lasercutter@doesliverpool.com)
  • better indicate on the blog that replies can be made via discourse

DefProc commented Oct 25, 2016

I have a more customisable install running now on disourse.doesliverpool.com (once the DNS propogates to include 188.166.158.202) that has the google group posts imported, plus the user accounts and discussions from doesliverpool.discoursehosting.net. It's currently on a Digital Ocean droplet that I'm paying for. Still on doesliverpool.discoursehosting.net

There are a few things left to check:

  • check the google group posts are reasonably complete
  • relink the website so comments go to discourse
  • set the main url to community.doesliverpool.com (once the DNS propogates)
  • Incoming email (to aliases of a new community@doesliverpool.com account)
  • Groups and email replies (eg. lasercutter@doesliverpool.com)
  • better indicate on the blog that replies can be made via discourse
@johnmckerrell

This comment has been minimized.

Show comment
Hide comment
@johnmckerrell

johnmckerrell Nov 10, 2016

Member

Cons of Google Groups

  • Sign-up is complicated
  • Some people don't like that Google own it
  • Not self hosted or "owned"

Cost of switching to Discourse

  • Migrating accounts across - don't want to force people to get emails, or not get emails, if they don't want to.
  • New email address for posting - have to inform people
Member

johnmckerrell commented Nov 10, 2016

Cons of Google Groups

  • Sign-up is complicated
  • Some people don't like that Google own it
  • Not self hosted or "owned"

Cost of switching to Discourse

  • Migrating accounts across - don't want to force people to get emails, or not get emails, if they don't want to.
  • New email address for posting - have to inform people
@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Feb 27, 2017

Added a forum link onto the website (listed as testing)

DefProc commented Feb 27, 2017

Added a forum link onto the website (listed as testing)

@willcrobinson

This comment has been minimized.

Show comment
Hide comment
@willcrobinson

willcrobinson Feb 27, 2017

Link appears to be cut off for me. Checked in Chrome, Safari and Firefox and all showing the link as "doesliverpool.dis"

willcrobinson commented Feb 27, 2017

Link appears to be cut off for me. Checked in Chrome, Safari and Firefox and all showing the link as "doesliverpool.dis"

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Feb 27, 2017

doh, fixed

DefProc commented Feb 27, 2017

doh, fixed

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 10, 2017

Contributor

Moved from #383, regarding comment button:

Any chance we can change its background-colour - make it green (like github comment button: #28a745) or something? It's practically invisible when just glancing at the screen.

Contributor

aubergine10 commented May 10, 2017

Moved from #383, regarding comment button:

Any chance we can change its background-colour - make it green (like github comment button: #28a745) or something? It's practically invisible when just glancing at the screen.

@aubergine10

This comment has been minimized.

Show comment
Hide comment
@aubergine10

aubergine10 May 10, 2017

Contributor

Is it possible to edit the header bar on discourse?

  • DoES logo
  • Links to website, wiki, issue tracker?
Contributor

aubergine10 commented May 10, 2017

Is it possible to edit the header bar on discourse?

  • DoES logo
  • Links to website, wiki, issue tracker?
@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Oct 22, 2017

As this has been waiting on a decision by grouping it in with the website improvements ( #19 & #548 ) but appears to have been unlinked from the blog, has seen little engagement, and is still costing us money each month (pending a decision on it's future) I recommended at the most recent organiser's meeting that we save a backup of the current site, shutter it, and not be paying for it until the website overview gets picked up again.

While I still think that discourse offers us a lot of benefits over sticking with the google groups, there's no need for us to keep paying for it while we're waiting on a decision.

DefProc commented Oct 22, 2017

As this has been waiting on a decision by grouping it in with the website improvements ( #19 & #548 ) but appears to have been unlinked from the blog, has seen little engagement, and is still costing us money each month (pending a decision on it's future) I recommended at the most recent organiser's meeting that we save a backup of the current site, shutter it, and not be paying for it until the website overview gets picked up again.

While I still think that discourse offers us a lot of benefits over sticking with the google groups, there's no need for us to keep paying for it while we're waiting on a decision.

@DoESsean

This comment has been minimized.

Show comment
Hide comment
@DoESsean

DoESsean Oct 26, 2017

Contributor
Contributor

DoESsean commented Oct 26, 2017

@DefProc

This comment has been minimized.

Show comment
Hide comment
@DefProc

DefProc Nov 20, 2017

I've applied to have the forum closed.

DefProc commented Nov 20, 2017

I've applied to have the forum closed.

@DoESsean DoESsean closed this Dec 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment