Bootstrapping the Open Source Design Discourse community - TODO list


(Graham Perrin) #10

@jan hi, just checking whether you saw the second e-mail that I sent in the early hours of this morning (01:10)

Early afternoon now, I’m knocking off work early aiming to catch up on sleep. The past few days have been intense :slight_smile:


(Sean) #11

Same! Way past my bedtime. Don’t burn yourself out!


(Graham Perrin) #12

I’d like to move this topic to the Public lounge.

@studiospring (opening poster): OK with you?

To everyone else: if you’d like to flag any post as potentially problematic, you may use features (such as flagging) that are integral to Discourse. Thanks.


(Sean) #13

How about Site Feedback? You choose.


(Graham Perrin) #14

Yeah, this is better. (I did think first of this category … must have been subconsciously overtaken by the word Public. A good thing.)


(Graham Perrin) #15

Yes – post 3 under External link target setting not being respected - support - Discourse Meta

The default has been changed and tested by me, would you like to check for yourself?

Maybe try any/all of the links from within the Welcome … topic.


(Jan-Christoph Borchardt) #16

Doesn’t seem to work for me yet for the top sticky welcome message. Will test again later.


(Graham Perrin) #17

AFAIR from something in Discourse Meta, a client side browser refresh may be appropriate.

Also please be familiar with:

  • the hamburger menu
  • to the right of the hamburger, the menu beneath your avatar (I guess it’s called the personal menu, something like that)

– you’ll find personal preferences (the cog icon), including Open all external links in a new tab

Thanks, and if it continues to not work for you we should swing over to Discourse Meta.


(Jan-Christoph Borchardt) #18

I am very familiar with Discourse :wink: we use it at Nextcloud with quite a big userbase: https://help.nextcloud.com

All the interface elements are pretty standard, so I don’t think there’s anything really to school people about. :slight_smile:

Regarding the issue: I just opened it in a private tab, the issue remains. But we can just see if it’s a timing issue.

Btw, can any admin change the title of the site from »open source design« to »Discourse – Open Source Design«? (Again, small things like this is why we should have multiple admins to prevent bottlenecks.)


(Graham Perrin) #19

Great to know that you’re familiar with Discourse.

As far as I recall: when I (too) found the issue after changing the preference at a site level, it was resolved immediately after changing the preference at my user level.

Here:

Can you provide a shot from your view of your preferences? Thanks.


(Graham Perrin) #20

Please: did it test OK?


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