preparations for use of Discourse for discourse.opensourcedesign.net #79
Comments
|
Cool on taking the initiative here to make something out of the discussion @grahamperrin! :) I do think Discourse will be good to give a place to the broader Open Source Design community. We do use/abuse Github Issues for a lot of these things at the moment. Which has its upsides because it’s in one place, but also the downside that it might not be well accessible for lots of people not yet familiar with Github, and also that it mixes Just looping in @simonv3 @belenbarrospena @bnvk @evalica @elioqoshi @victoria-bondarchuk @ei8fdb @jdittrich @Incabell – what do you think? |
|
Looking forward to this. Discourse is great once you get used to it. I just hope we refrain from having important conversations on GitHub afterwards. |
|
Thanks folks. For now, I suggest a tight focus on preparations such as:
– so that this Discourse-specific issue can be closed, in due course, without difficulty. For as long as this issue |
|
So, usually we go with generic subdomains and not product-specific ones like http://chat.opensourcedesign.net. So I’d go with http://forum.opensourcedesign.net, or http://community.opensourcedesign.net or talk. instead of What do you think? |
|
Thanks.
– I wonder whether the plea to "follow the discourse.example.com sub-domain convention" relates to the exceptional offer of free hosting. I'll let someone from Discourse advise on this point. Whilst |
+1 One could say that our Github or IRC activities are "Community", too, so I like "forum", it tells what to expect pretty well. |
Yes, this is a requirement for our free hosting. It's the only piece of branding we apply to the free plan. Aside from this, the forum is 100% whitelabeled and can be customised to your liking. |
|
Since it's a requirement I guess it's what we'll do! |
|
Thanks. For now I'll assign this issue to myself, I need to send one or two more e-mails before proceeding with form-filling. To whoever will be able to make (or arrange) changes to DNS:
– or take it now, if you prefer :-) |
|
@grahamperrin I have the domain – just let me know when it’s set up and what I need to change and I’ll do it. :) You can also send me an email at: hey at myusername dot net – I’ll see that quicker. |
No response, yet, to the first. I have plenty of free time this weekend so I went ahead with the application. From the resulting e-mail, one action point:
(Hint: please do not rush to browse to that target. Nothing there, yet. When Also, for reference:
|
|
Hey @grahamperrin I'm not sure I get all the context of your update. Have you been in touch with Discourse? |
|
Yep, I made the application this morning, which led to an e-mail from the Discourse Team. |
|
And before we put the forum public it would be good to have some discussion about how we use it:
I think this separation is important so we don’t lose focus, but also nurture the greater Open Source Design community. For example, from the monthly Open Source Design calls we should post the minutes in the Discourse, but when individual work items relate to stuff which needs to be done here we should open issues on Github. For tags we could use:
What do you think @simonv3 @evalica @victoria-bondarchuk @bnvk @elioqoshi @jdittrich @Incabell and others? :) |
|
I would use Discourse more like a way to talk asynchronous. We have IRC for synchronous, we have GitHub for work and tasks, but if someone has some ideas or wants to brainstorm she should use Discourse. We shouldn't use it as a wiki. If we want summaries of the meetings we could post them on website or in the Github wiki, as a reference. Everything that is final should go on GitHub->Site. Now is unclear if we can't discuss anymore on the GitHub issues and I would resist a bit. I see Discourse more for beginners or people that don't like GitHub :) to be honest I don't know how we will use it. I guess it will be organic, but we still need to promote it / use it if we want others to feel encouraged to use it. I see it more as an experiment, since I don't think we really had a problem to solve. But since I haven't use the product I'm curious to test it. I hope it will encourage more non-technical designers contributions. I'm sure people will be confused where we should talk or do stuff, if one place or the other, but we will fix this in time. |
|
We now have @jancborchardt for security, please, will |
All open source sites get HTTPS for free. It's been queued for your site ;) |
From my point of view two issues are outstanding:
– then the forum itself can be used to discuss how the forum should be used. In the meantime I should encourage attention to issues such as #69 and #73 so that meta discussions do not proliferate :-) Thanks |
|
@grahamperrin so can we sign up? I think we're fine to sail without a logo on the forum for now? |
|
Cross reference #68 (comment), a preview of how one of the logo options might appear in the forum:
Over to #68 for comments on logos, please; and bear in mind that the context above is experimental. Thanks. |
|
I'll be using this issue to keep everyone abreast of developments in the Discourse forum until members here have an opportunity to sign up to the forum. At present it is invite only and there are some areas which are not visible to the general public. Firstly, @grahamperrin has kindly asked me to be a co-administrator of the forum, which is why I am keeping everyone up to date. Things are obviously very quiet and lonely in the forum at the moment, so our most pressing task is to invite OSD members. Unless there is a better suggestion, I will create a gmail account and ask everyone to send an email to that account if they wish to sign up. Then I can send a bulk or individual invite to OSD members. There are obviously a lot of details about the forum (and OSD in general) that are pending until OSD members join and can have a say in those matters. |
|
If I understand correctly: for OSD members (who use GitHub) there should be no need to sign up. Building a Discourse communityThe build should not be in isolation; I'll add to #73. GitHubThe option to use GitHub for authenticated access to the forum was enabled a few days ago –
– and was tested by me, but re: #79 (comment) above, I suggest not taking that option until after it has been improved to use the github_client_secret for opensourcedesign. The need for that improvement was identified a couple of days ago – thanks @jancborchardt – with follow up yesterday, so people should be kept waiting not too much longer. Thanks, everyone, for your patience! |
Do we have an idea what work items are? Do we need to explain them?
Looking for/giving advice about research and design? Posting messages about events/jobs with links to the OSD website/other places. As @evalica said "if someone has some ideas or wants to brainstorm".
From @jancborchardt and @evalica's messages I read the only things we put in GH issues is website/repo tasks and the conversations needed to achieve them. The objective is to close issues once finished?
+1
And that'll require people to become friendly with Github!
I agree with @evalica this type of information should be on the website, otherwise why do we need it? ;)
I kinda agree, except we do need some place for discussion. Otherwise issues are left open.. |
Back to #69 |
@grahamperrin thanks for the clarification. In which case, invites are not really needed except to inform members who are inactive. |
|
A preview of how the front page of the forum might appear after things become open to the public:
After dismissing the banner:
If you would like to propose a change of wording to the banner, please reply to #73 (comment) |
|
Re: #68 (comment) here's an example of the square logo, in the context of preparations for go live of the forum:
Compare with the hexagonal logo, in context, at #79 (comment) above. Votes in 68 please:
|
|
I'm a bit confused now. Can someone tell me if the discourse.osd is now live or not? I've tried to register over the last 2-3 days but the Github account linkage isn't working. I see mentions of invites, but don't understand how they are sent/who needs to request one. |
|
@ei8fdb the server is on, but it's not available to the public yet. There are like 5 people on it. We currently don't have the admin, so we rely on grahamperrin and studiospring. They wanted to do some prestuff, like creating some categories, decide on administrators. It should be public ASP, but we don't have control over it. |
|
I've been fully supportive of setting up and having a Discourse as a forum for general discussion pertaining to OSD, but not for content. Content is what our website is for. I don't recall this ever being something we desired doing. Regarding the Discourse platform:
Does this sound about right to you @jancborchardt @simonv3 @evalica @belenbarrospena @ei8fdb @victoria-bondarchuk @elioqoshi @jdittrich ? @grahamperrin @studiospring does this all make sense? Can we move forward with these parameters or is there a block for some reason? |
|
@bnvk yes there are blocks, some of which are being discussed in multiple channels. GitHub
It was suggested to me that the routine should become opensourcedesign-oriented. (Better that, than association with my grahamperrin GitHub account. Of course I agreed.) Without delay I did what was required to the Discourse side of things; that's when (as I half-expected) GitHub-based authentication ceased to work. The part that seems to be not yet done is beyond my control. Context: – step 2 was completed by me in the early hours of Tuesday morning, 11th April, less than two hours after I received what was required for the Discourse side of things. A few minutes later I e-mailed the opensourcedesign person,
Six hours ago a more detailed explantion was shared in the forum. I'm keen for the issue to be resolved, but (as I don't wish to be pushed), I don't wish to push the person, or people, who can complete the work. |
In as few words as possible (I politely beg for this conversation to not span three or more channels (and attempting to follow things such as this in GitHub is excruciatingly painful)): on the morning of Thursday 6th April, a core committer to OSD was asked whether they would like to be a joint administrator. I hope that we're close to progressing such things. |
|
I'm aware of these multiple channels of discussion...
@grahamperrin I believe Github login / signup functions separate from normal email signup, which is what I mean with:
One of the whole points of OSD having Discourse is so people who don't like or use Github can participate in discussions- in which case, Github signup is not needed. Additionally, if this is taking hours of configuration (and still not working), please drop Github signup for now.
Yep, this is why I am stepping in and focusing things- this needs to happen publicly, and here, as this is where conversations and decisions have been happening since 2015.
We do not need to "decide" on this as we have a "core" group, these people should be admins as well as you and @studiospring since you're helping set this up. I believe you already have all of our emails sent by @jancborchardt no further discussion is needed. Simple :-) |
|
I politely begged, and what happened. The public oversimplification of matters that I preferred to be private is horribly destructive. |
|
@grahamperrin what is being oversimplified? What has been horribly destructive?
I'm just trying to make progress and get to the next step of a functioning
Discourse instance as per our community processes...
We are still really grateful for you taking the lead and making as much progress
as you have :)
|
With additional emphasis: matters that I preferred to be private. Again: private. Logically, and respectfully, I beg people to refrain from asking "what" in public; it simply will not be answered by me in public, and I sincerely hope that other people will – conscientiously, colletively and individually – demonstrate respect by showing comparable restraint. Now: the forum staff accounts can – and should – be used to expedite the preparations that could not be made in this issue :-) Beyond that: I respect the closure of this issue and so, will write nothing further here. |
|
I believe that public discussions are the base for any open source related interaction. To be honest I'm not sure what the outcome of these discussions will be, since there is a barrier/difference in the way we usually do things. We are going in circles between the preferences of X vs. Y. We should try to focus on the well being of the community. So in order to progress, please give admin right to @bnvk and let's make the Discourse instance public in order for everyone to be able to use it. |
|
Thanks to @evalica for the on-point comment and for @bnvk to make the instance public. Folks, sign up at https://discourse.opensourcedesign.net and participate in the discussions. Before we spread the word more, I’d like this private/public stuff to be resolved. For the threads which are currently private I see two resolutions, which has to be decided on a case-by-case basis on every topic:
And then subsequently, the private »Staff« category should be completely abolished because it encourages clique-building and »Staff«-discussions in private. This is nothing we ever needed or used so far, and would be against our tenets of openness. |
Spun off from https://github.com/opensourcedesign/resources/issues/16 (Free-as-in-freedom tools for Designer Dev communication and creation), #69 (Cross-Project-Communication and community: Creation of Mailinglists?) and #73 (Strategy for OSD's goals, user base, platform and growth):
From preliminary advice, which I received via e-mail, two key points:
– and:
Domain name and address
Given the open nature of OSD community developments, I assume that it will be OK to use – from the outset – an address that can endure:
https://discourse.opensourcedesign.netPlease, does anyone foresee a problem with use of that address?
(If not
discourse.opensourcedesign.netthen a temporary domain name may be used.)Who should be my point of contact for co-ordinated changes to DNS?
Related
Other issues, in this repo, where subscribers may wish to be aware of the Discourse development:
[email protected]email forwarders)The text was updated successfully, but these errors were encountered: