Bootstrapping the Open Source Design Discourse community - TODO list


(Graham Perrin) #21

Thanks @eppfel


(Graham Perrin) #22

Open Source Design call – Wednesday 2017-05-03

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 (03:00 AEST – sorry, @studiospring)

Related

Bootstrapping the OSD Discourse community - TODO list (2017-04-08)

Post 14 (2017-04-19) under Categorisation, tagging, default appearance

The Lounge: Or Secret Communications (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.)


(Jan-Christoph Borchardt) #24

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.


(Graham Perrin) #25

First was 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 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


(Graham Perrin) #26

Promotion

Known promotions

Indirect

Direct

– plus maybe five other tweets from Open Source Design.


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

I’ll make some more.


First impressions, part two
(Jdittrich) #27

First was 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)
to:

Overview of problems, chances and practices of integrating UX and Open Source Software development (ideally based on research)

– 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.


(Jdittrich) #28

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)


(Graham Perrin) #29

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 A said: … Person B said: … Person C 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 Z). Does that make sense?

Thanks


(Graham Perrin) #30

:thumbsup: 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:


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.