Notes on Discourse setup


(Isaiah Norton) #1

TODO:

  • decide on/configure contact email (rarely needed but good to have) (posted in Staff)
  • research Google OAuth endpoint that can be controlled by group?(posted details in Staff)
  • move GitHub OAuth endpoint to Slicer org
  • find/make a better horizontal logo, “3DSlicer” is too small in the current one.
  • consider/test whether we can use inbound email support with slicer-users@bwh.harvard.edu – for muscle memory posting seamlessly. Responses would pass through discoursemail domain, and users could eventually log in and fully configure the automatic shadow account. (I think this would be too complicated. Let’s try without first)

Points of contact:

  • team@discourse.org
    or
  • simply @discourse (note that @-name will ping user, just like GitHub. Use backticks to avoid ping!).

OAuth config is very simple:



(Jean Christophe Fillion Robin) #2

Well done @ihnorton :thumbsup:

I didn’t have issue to sign up using GitHub. That said, when I first tried using google email, it failed. The screenshot below illustrate the issue.

Additionally, the authorization for GitHub is not associated with a Slicer logo but with @ihnorton handle. Is there a way to change it to @slicer (@slicerbot) or something like this ?

Here the failed one from Google:


(Jean Christophe Fillion Robin) #3

And here is the one from GitHub where we can see the missing Slicer logo:


(Andras Lasso) #4

I’ve signed up using github and indeed it is very confusing that I have to give permission to my github account personally to Isaiah. Slicerbot or similar would be good.


(Isaiah Norton) #5

@jcfr I requested to transfer the github oauth application to the Slicer org. Google is fixed, though I’m not sure yet if we can move it to a group-control (it’s on the list).


(Andras Lasso) #6

Great, thank you.

I like the current logo, but maybe we can switch to the horizontal logo, available at:
https://www.slicer.org/wiki/Slicer3:Slicer3Brand#Full_color.2C_horizontal_format


(Andras Lasso) #7

By default there is a large pinned message (Questions and comments are welcome here! (about usage, coding – or bugs)
PLEASE NOTE: any data shared/linked on this site must be anonymized…).
I find it too big (and took some time to realize I can remove it with the X button) and not all information is relevant here.
Could you move the note about not include any patient data to the text that is displayed when you first post a message? Also, this note on patient data should go to a some permanent page that explains rule of what/how to post.


(Isaiah Norton) #8

I added you Jc Steve to admin group, feel free to make changes (just don’t break login :grinning:). I’ll be out until tonight and can make these changes later otherwise.


(Andrey Fedorov) #9

Great job @ihnorton!

Can we configure the colors for the topics? I would choose something more lively than black, brown and light brown!


(Andras Lasso) #10

I can change the colors. Do you have any specific suggestion for colors?


(Andrey Fedorov) #11

I don’t. R-G-B? I don’t know if we need a deep thought into it, just a bit more lively.


(Andrey Fedorov) #12

Integration with github issues works!

Just a test:


(Andras Lasso) #13

I’ve changed the colors to more lively ones.


(Steve Pieper) #14

For that “Slicer look” we could use the generic anatomy colors.

https://www.slicer.org/wiki/Slicer3:2010_GenericAnatomyColors

https://www.slicer.org/wiki/Slicer3:2010_Label_Colors