Drawing the attention to a group not an individual in Discourse

In a reply I made here in relation to the hide-body field which is part of the standard tiddlywiki. I documented an issue that could reasonably be considered a request for a change to the standard wiki distribution (or core) .

My thought was then, what if I could tag the reply or @mention either core developers or another team. They would then be alerted to a possible improvement which if they go ahead and implement they could tag or @mention the documentation team.

Thus we could democratise the raising of ideas in talk.tiddlywiki.org however in the context where they are raised and leave it to those in the various “groups” to share/collaborate on, perhaps with their specialist knowledge.

  • What do you think?
  • What would be the best discourse method?

I’m familiar with both tagging (devs, bug, wish, etc) and callouts, e.g. @jeremyruston @saqimtiaz (the onus/decision is on those guys to monitor such and take further action where applicable). However…

I think the devs are likely to favor the exiting channels for the kind of things you’re talking about – post on GitHub perhaps with a link to the forum thread.

@CodaCoder

That is fine but if the broader community is not given a user friendly mechaisium, the divide will remain.

Recent talk on contributions to the documentation came to the same conclusion. A lot of people are ready to contribute, but there is too many technical barriers for a larger audience.

There is an argument that one channel be given primacy and it be as simple as possible, even if it ends up with a backlog, Which the existing systems (GitHub) already have anyway, despite their inaccessibility to many.