Add info about workflows (forum/github/...) into READMEs and Forum Welcome message

[eppfel]

No description provided.

[jancborchardt]

@ei8fdb can you add your writings here? :)

[grahamperrin]

(Speech is barely audible in the Jitsi call …)

Is this issue the one that was mentioned in connection with steering people:

• to GitHub for some things
• to the forum for some things

– and so on?

[eppfel]

@grahamperrin Yes

[ei8fdb]

@eppfel @jancborchardt @jdittrich @evalica @simonv3 @belenbarrospena @grahamperrin and everyone else: Does this capture the main usage for GH and for Discourse?

I've made some assumptions, so if they're terribly wrong please shred this and make improvements.

Unless there are significant changes/thumbs down I'll send a PR to add this to the READMEs and a shortened version of the "what we use Discourse for" to @grahamperrin for Discourse.

Rough notes on this from today's meeting

Using Github (GH)

The objective of using Github to record, discuss, document, and co-ordinate tasks or changes that we (the Open Source Design community) need to do as part of the community.

These different activities are managed in individual GH repositories.

• If new content goes on the website, we've organised this on Github.
• If we are organising a conference or event, we've organised this on Github.
• If a "feature request" for the website (e.g. new jobs board/we need an event landing page) is needed, we've organised this on Github.
• If we want to create/change an new Internet presence (new IRC/Twitter account etc), we've organised this on Github.
• If we're updating/changing the Open Source Community entity, we've organised this on Github.
• We've discussed all of the above on Github, in the repos.

Discourse

Our Discourse forum

Short version (to be used on the Discourse welcome message)

The objective of the OSD Discourse forum is to be an inclusive forum for promoting, and supporting discussions about the broad topic of "designing in open source".

The expected topics for discussion are broad and wide - it is not expected that discussions need to focus on "software development".

Longer version

It is expected the discussions will mirror the broad range of topics at our open source design tracks at various FOSS conferences.

The Discourse discussions are to be open to whoever wants to take part - from interaction designers, user researchers, industrial designers, developers, UX designers, product designers, architects, print designers, graphic designers, accessibility experts, logo designers working on open source software to users of open source design software - GIMP, Inkscape and many more.

Discourse discussions also need to be inclusive and welcoming for people (all the types mentioned above) who are:

• new to FOSS
• new to user centred design
• new to user centred design and FOSS

Twitter

Our Twitter account

We're used Twitter as a way of advertising, and spreading our activities - from advertising jobs on our jobs board to advertising and promoting our activities and events.

We've also used Twitter as a way to communicate with people who are currently "outside" our community, but who we would like to welcome in to OSD community.

IRC

Our IRC channel

IRC serves a useful objective of being a channel that developers (one of the groups of people we want to welcome) are very comfortable with. Some will be more interested in starting their "adventures" with design and open source from a comfortable starting point. Therefore it is a channel we want to maintain.

The OSD community use IRC as a more ephemeral discussion forum. Historical logs are available. A lot of our best ideas have come from a random "what about...." message in IRC.

[grahamperrin]

… and Forum Welcome message

About

Also, the /about text should be less exclusive.

From post 3 under First impressions, part two:

From the previous comment:

… an inclusive forum for promoting, and supporting discussions about the broad topic of "designing in open source".

From post 6 under First impressions, part two, a slight variation to wording that was suggested by @rosecheval:matrix.org in the designUX room:

A community promoting more open design processes • Dedicated to improving the user experience and interaction design of open source software

The omission of trailing punctation (.) is intentional. From the earlier post:

… suspect that people will more often see the text in the context of e.g. tweets. …

[grahamperrin]

To see for yourself how the /about text appears in tweets: https://twitter.com/opensrcdesign/status/855146100956770306