# Bootstrapping the Open Source Design Discourse community - TODO list

**URL:** <https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24>\
**Category:** Forum feedback\
**Created:** [April 8, 2017, 9:13am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24 "2017-04-08T09:13:19Z")\
**Posts on this page:** 9\
**Page:** 2

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 3, 2017, 5:41pm UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/21 "2017-05-03T17:41:27Z")

</div>

> <https://github.com/opensourcedesign/organization/issues/89>

Thanks @eppfel

> [@Contact information](https://discourse.opensourcedesign.net/t/contact-information/123):
>
> I see that promotion of the forum began last week, so let’s rationalise the contact stuff ASAP. [http://opensourcedesign.net/organization/](http://opensourcedesign.net/organization/) describes itself as a repository, it’s not (it’s a representation of part of a repo). Underlying [https://github.com/opensourcedesign/organization#community:](https://github.com/opensourcedesign/organization#community:) is outdated directs readers to five GitHub identities for forum administrators. – it should be better for the Discourse part of that content to simply refer to: [https://discourse.opensourcedesign.ne…](https://discourse.opensourcedesign.net/about)

---

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 3, 2017, 6:08pm UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/22 "2017-05-03T18:08:21Z")

</div>

## Open Source Design call – Wednesday 2017-05-03

[Notes from monthly Open Source Design call · Issue #49 · opensourcedesign/events · GitHub](https://github.com/opensourcedesign/events/issues/49#issuecomment-298700689) – items on the agenda included:

- Increasing Discourse use
- What to do in the open? And what not?

[18:00 BST](https://www.timeanddate.com/worldclock/converted.html?iso=20170503T19&p1=48&p2=1352&p3=240) (03:00 AEST – sorry, @studiospring)

## Related

[Bootstrapping the OSD Discourse community - TODO list](https://discourse.opensourcedesign.net/t/bootstrapping-the-osd-discourse-community-todo-list/24) (2017-04-08)

[Post 14](https://discourse.opensourcedesign.net/t/categorisation-tagging-default-appearance/21/14) (2017-04-19) under _Categorisation, tagging, default appearance_

> [@Categorisation, tagging, default appearance](https://discourse.opensourcedesign.net/t/categorisation-tagging-default-appearance/21/14):
>
> … renamed “Public Lounge” to “Lounge” …

[The Lounge: Or Secret Communications](https://discourse.opensourcedesign.net/t/the-lounge-or-secret-communications/40) (2017-04-10 – 2017-04-20, **archived** )

- what was the _Lounge_ became the _Private lounge_
- nothing there since Thursday 2017-04-13.

* * *

(After the call ended, I merged this announcement into the TODO topic.)

---

<div class="post-metadata">

**Author:** ![jan](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jan/32/8_2.png) [@jan](https://discourse.opensourcedesign.net/u/jan)\
**Post date:** [May 5, 2017, 2:41pm UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/24 "2017-05-05T14:41:47Z")

</div>

> [@grahamperrin](#):
>
> Please: did it test OK?

No, in another test I just did unfortunately didn’t work either. :\ Tested in a private window, not logged in. All links in the welcome message open in the same window, pushing people away from the forum site.

---

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 12, 2017, 11:34pm UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/25 "2017-05-12T23:34:04Z")

</div>

> [@grahamperrin](#):
>
> … imagine seeking permission, in GitHub, to experiment with:
> 
> 1. first, migration of just one test issue
> 2. then, migration of a handful of issues.

First was [overview of problems, chances and practices of integrating UX and Open Source Software development (ideally based on research) · Issue #74 · opensourcedesign/organization · GitHub](https://github.com/opensourcedesign/organization/issues/74#issuecomment-301157162) thanks @jdittrich. I changed the reference there from:

> `https://discourse.opensourcedesign.net/t/overview-of-problems-chances-and-practices-of-integrating-ux-and-open-source-software-development-ideally-based-on-research/150/2`

to:

> `https://discourse.opensourcedesign.net/t/-/150`

– OK, @jdittrich? (Or was skipping the opening post intentional?)

* * *

Second (originally suggested to be the first) can be [preparations for use of Discourse for discourse.opensourcedesign.net · Issue #79 · opensourcedesign/organization · GitHub](https://github.com/opensourcedesign/organization/issues/79) and if you do migrate the issue, please do so in its entirety. It can be:

- closed and archived in the _Forum feedback_ area
- (please) not hidden; a historical point of reference about the forum, within the forum.

* * *

If I recall correctly, there’s the option to change ownership of posts. Consider changing from `@jdittrich` (or whoever performs the migrations) to `@system`

Thanks again

---

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 13, 2017, 6:19am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/26 "2017-05-13T06:19:45Z")

</div>

## Promotion

> [@evalica](#):
>
> **Decide when to open to the masses.** … IMO this should go ASP. … let people create content on it and use it. …

> [@simonv3](#):
>
> … agree with @evalica about opening this to the masses. …

> [@studiospring](#):
>
> … agree about organic growth, but to improve the odds of success, I don’t see any harm in boosting publicity to build critical mass. …

> [@Contact information](https://discourse.opensourcedesign.net/t/contact-information/123/1):
>
> … promotion of the forum began …

### Known promotions

#### Indirect

[https://twitter.com/grahamperrin/status/849115538848698369](https://twitter.com/grahamperrin/status/849115538848698369)

#### Direct

[https://twitter.com/grahamperrin/status/852496087873191936](https://twitter.com/grahamperrin/status/852496087873191936)

[https://twitter.com/opensrcdesign/status/857658850370961408](https://twitter.com/opensrcdesign/status/857658850370961408)

– plus maybe five other tweets from Open Source Design.

> **[Please visit our Discourse Forum! (Directory)](https://meta.discourse.org/t/please-visit-our-discourse-forum-directory/3102/352?u=grahamperrin)**
>
> Thanks to everyone who participated in this topic! As Discourse has grown from 2013 to 2018, it has become difficult to keep this topic up to date. As of 2017 there are more than 10,000 active Discourse instances on the internet, so we’re no...

[https://twitter.com/RebelDevNews/status/860238514126016512](https://twitter.com/RebelDevNews/status/860238514126016512)

* * *

I don’t intend to update what’s above unless there’s a significant omission.

I’ll make some more.

---

<div class="post-metadata">

**Author:** ![jdittrich](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jdittrich/32/42_2.png) [@jdittrich](https://discourse.opensourcedesign.net/u/jdittrich)\
**Post date:** [May 13, 2017, 6:34am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/27 "2017-05-13T06:34:45Z")

</div>

> First was [overview of problems, chances and practices of integrating UX and Open Source Software development (ideally based on research) · Issue #74 · opensourcedesign/organization · GitHub](https://github.com/opensourcedesign/organization/issues/74#issuecomment-301157162) thanks @jdittrich. I changed the reference there from:

> [Overview of problems, chances and practices of integrating UX and Open Source Software development (ideally based on research) - #2 by jdittrich](https://discourse.opensourcedesign.net/t/overview-of-problems-chances-and-practices-of-integrating-ux-and-open-source-software-development-ideally-based-on-research/150/2)  
> to:
> 
> [Overview of problems, chances and practices of integrating UX and Open Source Software development (ideally based on research)](https://discourse.opensourcedesign.net/t/-/150)
> 
> – OK, @jdittrich? (Or was skipping the opening post intentional?)

No, was unintentional. Thanks!

> If I recall correctly, there’s the option to change ownership of posts. Consider changing from @jdittrich (or whoever performs the migrations) to @system

I have a look.

---

<div class="post-metadata">

**Author:** ![jdittrich](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jdittrich/32/42_2.png) [@jdittrich](https://discourse.opensourcedesign.net/u/jdittrich)\
**Post date:** [May 13, 2017, 6:44am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/28 "2017-05-13T06:44:02Z")

</div>

> [@grahamperrin](#):
>
> If I recall correctly, there’s the option to change ownership of posts. Consider changing from @jdittrich (or whoever performs the migrations) to @system

Would that be for semantic reasons, or does it give special rights to others (who might be the original posters)? (Just thinking, since often such accounts come with further restrictions – I sadly could not find an overview of the build-in discourse users)

---

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 13, 2017, 6:54am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/29 "2017-05-13T06:54:16Z")

</div>

Semantic, I guess.

The first migration may be not the best example but as a rule of thumb, if results are in the style of “Person&nbsp;A&nbsp;said: … Person&nbsp;B&nbsp;said: … Person&nbsp;C&nbsp;said: …” then I think it will be better for each such line to be presented by e.g. the system (not all presented by Person&nbsp;Z). Does that make sense?

Thanks

---

<div class="post-metadata">

**Author:** ![grahamperrin](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/grahamperrin/32/62_2.png) [@grahamperrin](https://discourse.opensourcedesign.net/u/grahamperrin)\
**Post date:** [May 14, 2017, 9:06am UTC](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24/30 "2017-05-14T09:06:58Z")

</div>

> [@jdittrich](#):
>
> … I have a look.

👍 improvement noted, with thanks – there’s no longer the risk of a reader mistakenly assuming that `@jdittrich` _alone_ is the person to contact about migrations.

* * *

@jdittrich I suggest editing the opening post so that newcomers to the topic will know _whose story_ it is **without** going to GitHub:

 ![](https://canada1.discourse-cdn.com/flex029/uploads/opensourcedesign/original/1X/8f96ff9e5cb75e7aa964c516afede2640c485ad6.png)

* * *

I sent a test message to system.

I _imagine_ that notification of the message will be:

- received by staff (~4 local, plus Discourse)
- not directed at other leaders.

[Previous page](https://discourse.opensourcedesign.net/t/bootstrapping-the-open-source-design-discourse-community-todo-list/24.md?page=1)