Norns technical discussions on lines (& moderation)


#21

I think Discourse is a pretty great tool for discussion. I find it much preferable to IRC, which excludes people who can’t communicate in real time (I can’t, and my impression is that some of the core norns devs can’t either). It’s also preferable to a mailing list for its moderation features.

Maybe the concern is one of lines being overrun by norns dev discussion? Perhaps we should have a separate Discourse instance for norns itself?

On documentation, it helps to foster a culture of “write that down”. That is, whenever some useful piece of information comes up in discussion, it should be possible for any participant to copy that text and add it to a corpus of knowledge. A wiki seems ideal for this. GitHub has wikis but I think they’re only open to project contributors, so that’s not really ideal. Can anyone recommend good wiki software?

With all that said I think it’s important to emphasize opening and contributing to GitHub issues whenever that makes sense.


#22

I’m glad we’re having this discussion here, because as someone new to the monome community, and open-source projects (github too), wondering how to contribute to discussion/development effectively can be very daunting at times. I like @enneff’s idea of adopting a “write that down” mindset, as I’ve already found myself frustrated with the lack of documentation in some areas of norns, (I understand, we are still in the early stages of development though, and time is better spent improving code) and have to spend more of my time reading between the lines, so to speak. I keep up with all the threads here on lines, but as @zebra and others have said, that takes a lot of time. Time I would rather spend improving my programming.

I think @barnaby is onto something in creating a more sensible flow of information. Maybe the monome devs and major norns contributors can get together to create a strict (as in logical) system for collaboration and accessible documentation, then directing new norns community members there. As others have mentioned fostering environments like this take effort and continuous, encouraging moderation. Ultimately though, it might help norns flourish and be more welcoming to newcomers.


#23

so there is “summarize this topic” feature which i guess is based on the number of likes/replies. is there a way in discourse to “star” posts (or how feasible would it be to create a custom field / make a plugin) and see only starred posts in a topic?

this could be a good way to identify all the posts that contain important information and could serve as a temporary wiki replacement. being able to set the flag could be limited to certain level / admins / topic owner. eventually starred posts could be moved to a wiki.


#24

posts themselves CAN be “made wiki”, no?

yes they can :sweat_smile:


#25

i think that just allows anybody to edit them (which could still be useful as a community driven post that aggregates links, for instance)


#26

coud use moderation flags i guess?


#27

if i understand the flagging feature correctly it’ll just bring the flagged post to mods attention, but wouldn’t mark it visually and wouldn’t help with generating a summary… if discourse doesn’t have the option to star posts it would require some custom development (assuming it’s feasible at all).

maybe i’m overthinking it, and all we need is community curated wiki pages that link to individual posts (or we could have volunteer curators - i could do that for teletype, for instance). they would be responsible for watching all threads related to a specific topic and updating the wiki (tagging topics like we already do for teletype/norns would help keeping track which topics they would need to watch).

it’s just, we have so much shared coding knowledge on this forum, why not apply it to the forum itself? (of course, there might be some very valid reasons to keep the forum software unmodded).


#28

Discourse has a plugin framework

And a directory of plugins


#29

There’s a wiki plugin that converts a category into a set of HTML pages: https://blog.discourse.org/2016/05/using-discourse-as-a-community-powered-wiki/


#30

a bit of my experience of documentation on axoloti, which is a kind of similar product to norns.
(at least in ‘challenges’), and also uses discourse (and GitHub, for both code and contributions)… its been running for 3 years now(?) so is mature, and i think has a pretty vibrant community…

so when we first created the axoloti discourse forum, I seeded the forum with a user guide, and install instructions all created in category (called user guide), using wiki posts.
it took me a while, and im not a technical writer, just a developer, so the hope was others would expand an improve on it.

some thoughts on this:

discourse only allows the first post to be a wiki entry.

this actually is quite nice, you can actually allow comments to be about improving the doc, or close it, but this still allows editing.

the markup is ‘ok’

i thought fine for my needs, but many kept saying it would be better in a proper wiki (linking is the main thing, but i also often users lack of familiarity with the finer points markdown)
its advantage is quick and easy (for me), and it sits nicely alongside other posts for searching, and its easy to link to… but its has it limitations.
(as @vehka has just posted, we also export it to html (or pdf?) so it can be delivered with the software as offline documentation)

non-collaborative

a technical issue, is there is no multi user locking/collaboration (at least last time i tried)
this means two users can edit, without any notification, and the the last ‘save’ wins.
really was only an issue initially, when i was adding new parts, and someone else decided to fix my typos :slight_smile:

flagging content for adding

thats an interesting idea…
id say that one issue is lines (for norns) is kind of promoting a use model of discourse that its not designed for… discourse (and most forum) are designed such that new topics are put in new threads… and so tagging etc, is done at the topic level. and then are grouped by categories

whereas lines tried to put all norns topics into one topic (ok, several topics like scripting, but still coarse granularity)

so its creating a rod for its own back really
move to a development category with individual topics, then you can start using existing discourse features (as others monome products have?)
this also empower users to be more selective over the topics they wish to watch and not.

community documentation experience

I have to say im intrigued by any model that encourages community members to help the documentation effort.

that said, i suspect the ‘tech’ is unlikely to be the issue :frowning:

this has been an area I’ve been hugely frustrated with on Axoloti…
whilst we had core documentation in place, of course new users wanted more, understandably. and they also were frustrated that this meant searching over the forum.
we agreed this was a problem, and ive been very vocal that the community needs to be part of the solution.

but countless times, Ive had new users turning up whinging, and saying if I help them get going, that they will document their process, and then contribute it… so i carried thru on this, gave them even more support than normal, and even said i would review what they put together.
sounds like a fair deal, good for everyone - no?

not one of them actually followed thru, sure they took the support and guidance, but didnt write a thing.

the results is , we have had only a couple of contributions to the documentation effort (which ive of course been hugely grateful for!)

but still we get the same complaints.
so unfortunately it appears, everyone wants documentation , but few are willing to put the effort in to create it.

so yeah, I feel a bit jaded/cynical about it now :frowning:

important note: to balance this a bit…
i think the reason im frustrated about this, is because the rest of the ‘community’ features of axoloti works really well, we have lots of code/patch contributions, and lots of users that help each other on every aspect, and there are excellent discussions on broader topics like dsp.
so… its just this one aspect, that feels like it lets us down, and its the first encounter new users have.

so, if a different model , as @barnaby suggests works, it be awesome, and id look into following on axoloti…

documentation usage

from axoloti, id also say its apparent some people just dont read documentation, they will still want to post issues/discuss…
but at least if you have the documentation, you can just link them to it :slight_smile:
(also as common issues arise, i try to update the relevant ‘doc’, again being in the same place as posts, makes this easier.)

however, i think alternative forms work really well…

  • the studies are a great way.
    axoloti has tutorials, and help pages (like max), but they lack the explanations of the studies, and i think the studies are really nicely balanced in terms of size/length.

  • ive also done quite a lot of videos , which is now my preferred route
    seems a split on users who prefer videos to docs, and vice versa.
    (more on organelle, that axoloti in fairness, just because thats where my focus has been)

but also you have to consider the real issue…
e.g. do most users want a rPI how to guide, or would they prefer a download image.
(i did the former, as i didnt want to tread on norns toes, but i suspect most wanted the later!)

axoloti forum

if anyone is interested in what this all looks like you can see it here:
http://community.axoloti.com/c/user-guide,

also you might want to look at how axoloti discourse is structured…
of course, its different, as its doesn’t have the mixed focus of lines, but it does have the ‘development of code’ vs end-user split of norns.

one particular area that might be interesting, is how we organised ‘contributions’, basically giving each contributor there own thread - this seems to work quite nicely,
it gives each contributor a place to talk to ‘their’ users, and announce updates…
perhaps not the best way to organise it, but it has a nice feel to it


#31

As a developer, I found that the interaction over norns and rPi here quickly became unfollowable if one wasn’t staying on top of it. I gave up.

It seems that much of the interaction in the various threads would have really be much better suited to a slack, or other form of live interaction. And the non-interactive useful bits were buried in the threads… and you needed to read them through to the end to find the caveats, corrections, and improvements.

In my experience with open source, forums like discourse are best after the core of the software structure and documentation has already been developed.

As for lines itself, I feel like to serve as a developer forum for norns would require a large number of finer tuned threads, and then those threads would dominate the board. Perhaps if they were in their own major category… but again, still feels to me like the wrong vehicle.


#32

The software development organization I’ve managed for the last 7 years has used the following:

  1. A live text chat environment (with separate “rooms” for specific topics and projects) e.g., Gitter or Slack
  2. A live voice chat environment (with screen sharing and notes tab) e.g., Google Hangouts
  3. A durable wiki for preserving project documents with related narratives e.g., MediaWiki
  4. A ticketing environment (with a vigorously-groomed backlog, release planning and assignments facility) e.g., GitHub or JIRA
  5. A public forum facility (for accepting public feedback and discussing topics with users) e.g., Discourse, UserVoice
  6. An executive-level project planning facility (for showing the ebb and flow of projects at the level of milestones), e.g., Trello

Software development is a team sport that suffers when roles become blurred. This is especially true of open source projects with large communities, something I’ve avoided managing because I value my health.


#33

yeah, I agree, lines its a bit split on its identity…
there are many that want it to be less ‘gear focused’ (see comment on hiding trade category),
yet its backed by a ‘gear manufacturer’, so its walking a difficult line.
(not only norns, aleph seemed similar, as also eurorack at times)
no solution or critique, just recognising its hard, and a balancing act the mods are doing a good job on.

this may be true, though many of us are in different timezones, so not sure how ‘live’ it would be, but certainly the ‘transient’ nature of the discussions perhaps is better suited.

however
Like some others, Im trying to reduce my social media consumption/footprint , and using yet more platforms - fills me with dread (actually, more likely i just wont signup, as I have to draw a line somewhere :frowning: ).
this makes me wonder, perhaps this is a sub-conscious concern I have with GitHub issues for discussion.
whilst I use it as a repo server - I really don’t want to turn it into another social media platform.
(esp. now its microsoft owned)

but again, these concerns may be limited to me…
and there is an argument for the ‘best tool for the job’, rather than trying to arbitrarily limit social media platforms and forums i interact with.


#34

apologies for my slow response. i’m traveling and internet access has been spotty.

one proposal:

use the (presently underutilized) Development Category which lines users are free to mute.

but i feel this is only effective if we avoid mega-threads.

unfortunately avoiding mega-threads is fundamentally impossible without heavy-handed moderation (because a huge percentage of users will not stay on topic and moderators will get sick of the extra volunteer work to be verbose at letting people know they’re off topic and their message was moved)

but, we can try this, but i’d almost caveat that if by posting in the Dev category we all make our best effort to stay organized and on-topic, and agree to be moderated (this may mean calling for more volunteer moderators).


it’s good also to remember that what we’re discussing here is effective means for collaboration, and i’m grateful that you all are sticking around to discuss the very idea of collaboration. thank you! i’m hoping we can figure something out quickly, so we can get back to programming, and then stop programming sometimes so we can all enjoy the musical utility of the stuff we’ve built together.


#35

I think this is a ‘culture’ / by example thing…

here, creating new threads for specific technical things, or questions, has not been the way its done,
rather things get lumped into broader topics.
(because of lines broad nature)

if you start creating lots of specific threads, like
e.g. (Norns) how do I sync midi clock with norns.

then others will follow, as its seen as a norm

if anything on Axoloti we at times have the opposite issue,
where similar threads get created (as people dont search), so I sometimes combined (if its important)…
I less frequently have to split threads (but thats also pretty easy on discourse)

Ive generally never had too many comments about moving posts around (unlike closing),
people seem to view it as ‘tidying up’ - the only issue (which I think others have mentioned on lines) , is discourse doesn’t really inform the poster of the move very well - so Ive had people thinking its disappeared/been deleted (which they get uppty about … till you point them to it :slight_smile: )

however, axoloti is a product specific forum, so ‘thread explosion’ is no issue
how well that works on lines - not sure…

do you think it been better to make development as ‘opt-in’ rather than ‘opt-out’?
then the new noise, might be less of an issue?


#36

Development has been part of monome culture since day one. Lines has expanded beyond that but I’d be sad to see it become a place where development is no longer seen as an inviting playground.

But I’d love to see more granular threads, more volunteer moderators (raises hand) and if the development category became opt-in, I’d definitely do that (but I hope we can make this action super easy to discover!)


#37

Chipping in my two cents as a follower who is not deeply involved in development:

I really have enjoyed reading through the talk between active developers of the Norns platform. As someone not as well versed in these topics, I’ve found myself using these threads as a way of understanding 1) the development process, 2) the hardware side of things, 3) how these tie together. I’m fine with the discussion moving elsewhere (whatever works best for y’all’s ~process~), but I’m sure I’m not the only one who reads through all of the Norns threads top to bottom, even the development ones, and thoroughly enjoys it.

The developer category seems like a good idea. Hopefully it isn’t muted like the trade category, though.


#38

I think that is what might be what is meant by “opt-in” and it seems unnecessary to me as well.


#39

Ill offer another non dev perspective via an analogy - fun huh?

these threads in a general forum (meaning everything from obscure coding to high range ethical discussions - its the strength of this place IMO) are like a magic eye picture - if you see it right (ie your a dev and or right across the tech be it hardware/software ect), or your a musician (drummer say, like me) you might see nothing but noise. So any contributions from ideas from non techy people are difficult as its so splintered where would you put this info for it to be seen and relevant if you could nut your way to hopefully the right area

Also given Norns isnt even at release it makes it even more confusing to get a grasp of the whole ecosystem…

I dont have an answer to this problem


#40

i love the analogy. i wonder if categories treated as lenses might not help here? (i admit i pay little attention to them myself but maybe with a little discipline they can be part of a partial answer?)

which is just to say, maybe it’s not important to be able to as long as there are ways to not lose the thread of the narratives you care about.