#9

Just as in the situation with washing dishes in a big shared house, sustainability requires everyone to do their own housekeeping. And that means everyone needs a somewhat shared understanding of what it means to have a clean house.

When the kiddos are young, the parents have to do a lot more direction around housekeeping, but as the family ages, more of the family is able to pitch in without prompting.

I think it’s a handy metaphor in this situation.

8 Likes
#10

sorry, just a post from a moderator… you can mark it with a ‘staff colour’ if you have many moderators but I don’t usually bother for this… seems a bit heavy handed (but perhaps that is due to how/when i use staff coloured posts)
but I do like to prefix it with something like ‘Mod Note: post moved due to …’, just so users know Ive got my mod hat on at that moment, and why I’m moving.

as I mentioned this is for splitting topics (unnecessary for moving whole topics, imho) where users go off-topic, which can sometimes be ‘sensitive’, even then I try to point out that this is again, just really housekeeping… often i highlight its done so that ‘future users’ searching will not have to wade thru rambling posts to get the answers they seek.
(obviously more appropriate/important for a site more focused on support of a product)

can be tough at times, being a moderator, hats off to those here at lines doing a great job :slight_smile:

2 Likes
#11

Throwing up apologies to the mods here for flagging a post for moderation when I wanted it pinned.

Didn’t realize that it was only for bad content!

(Also didn’t realize that clicking on the link that says “You flagged this post for moderation” causes the moderation request to be re-sent! That was really not obvious)

#12

i’m looking at the categories and trying to clarify between DEVELOPMENT and TECH.

i assume the former is for discussion of active projects and contributions? latter for more general subjects?

might be worth clarifying in description?

#13

I was wondering where the category descriptions were located. Here they are: https://llllllll.co/categories

I guess I interpreted “development” as being about active monome-related dev projects, whereas Tech was more about programming in general.

#14

Posted some guidelines for the Dev category, About the Development category

Feedback would be great. Post it there, or here…either way works for me.

Yeah, you’re both right, although Development doesn’t need to be limited to monome projects but in practice will probably be mostly monome or monome-alternate firmwares. The intent is to have a category that supports the development of these tools…which means a few housekeeping strategies to keep things focused without crushing the creativity.

1 Like
#15

it is a bit difficult to have to hunt through teletype- and monome-related threads across multiple categories. can the teletype stuff be kept in monome, or better yet, a teletype subcategory just for these endeavors?

also not a fan of crossposting the same thread to more than one category, or crossposting individual posts to multiple threads (ex: the algorithmic post series). crossposting generates a lot of spurious search results and noise, and it’s difficult to keep all those duplicates updated with the same info. there are now four places to discuss software/hardware topics: monome, equipment, dev, and tech, and i see some degree of overlap across all of them.

does the discourse search engine take into account parentheses? if not, maybe there’s no need for the (special) formatting title requirement. what about tags (ex: llllllll) for those topics instead of (prefixes), or are those reserved for top-level highlights? tags might help sort out those topics that touch on multiple categories.

1 Like
#16

i was gonna say that given the volume of (Teletype) posts it would seem to be a good candidate for a subcategory of Development.

and in general if there were a lot of Development traffice then subcats would be generally good, since presumably not everyone is working on every project.

OTOH, trilogy / ansible / TT / aleph all share an MCU architecture and a lot of code.

1 Like
#17

you mentioned subcats and development, and that got me thinking: what about making development a subcategory? instead of top-level, make it a subcategory one level down from an existing top-level category. maybe even apply this approach to existing TLCs:

monome
  development

tech
  development
  studies
1 Like
#18

When I first reached out to @tehn, I wrote up a pretty detailed document to help manage the flow of ideas through lines to github and then into a release. I based it on what I’d seen work at mix of open source and closed source projects. He and a group of the TT devs rightly pointed out that the process was heavy on engineering and would bog things down, also most likely discourage the lines community from participating in discussion. I’m hesitant to speak for that group, but my interpretation of that discussion is to keep things simple and only add additional process when it’s necessary.

My first reaction to the push for simplicity was that it really needed more stuff. I had a hard time coming around to the idea of not using tags, but the more time I spend actively engaged in the process, the more I agree with @tehn (at least my interpretation of @tehn-isms). We could add additional layers of organization to the discussions, but I’d prefer to see how the straight split between Development, Monome and Tech categories goes before we add additional organization layers.

@ioflow / @zebra you each have way more experience supporting this community and working on the monome open source projects respectively, so I’m more than ok with deferring to your opinions, but I thought a bit of context (we started very complicated and then backed off to this current plan) would help.

#19

agreed that maybe subcats are a good move-- particularly in dev where it could be easy to split it up logically.

i don’t want dev as a subcat of monome in that i’d like to allow a non-monome sense of ownership, ie @scanner_darkly’s orca, @bpcmusic’s telex, and many to come perhaps.

the monome category i consider predominately support oriented and general monome questions.

in a sense, studies and equipment could be a subcat of the more general tech cat.

review needs a better term, basically to encompass threads about music/video/art/etc that is not-tech, not-process-discussion, not-tools.

events and trade are perfect as is.

1 Like
#20

Candidates for sub categories,

  • Teletype (seems most obvious given the momentum)
  • Trilogy? Or each module individually
  • Ansible
  • Aleph
  • Telex
  • Max / MSP grid / arc applications? Supercollider / pd grid stuff?

Maybe just start with Teletype and Telex? Not sure where to draw the line to identify enough content to warrant a sub cat.

#21

i think that projects not having a critical mass can just live in Dev. currently tt, aleph, and serialosc seem like worthy candidates

#22

I don’t have the auth-level to make these changes (that I can find).

#23

i can do it-- i’m just looking for feedback first

#24

Possible downsides, though I’m not sure how much I believe they’re an issue: it gives weight to the sub category projects and might discourage new projects from finding footing there. It might set up a perception of official v. not official projects.

Upside is clearer organization, ability to mute dev channels you’re not interested in.

I’m not entirely sure how sub categories look, I think this is an example from the discourse meta discussion site, https://meta.discourse.org/c/dev.

#25

side note - when I read a pinned post, it automatically unpins for me. Is that because of a setting I’ve chosen (but don’t remember) or because I’m a moderator? Or is it a site wide setting?

#26

Ah, found the setting…anyone know if this is the default for people? Wondering if pinning release posts is really getting us the effect we think it is. Setting is under interface, " Automatically unpin topics when I reach the bottom."

2 Likes
#27

Default for me! Thanks for finding this!

@tehn maybe we should make the default for this checkbox “off”?

1 Like
#28

What do you mean with a non-monome sense of ownership?

It seems like there’s 2 main axes being suggested:
the hardware/software/project (monome, ansible, etc) topics are related to vs what type of of content/action (development, support, sharing, etc) the topic contains.

From a discovery perspective for a new user I think a category per device makes sense which contains all device specific content. This device specific content can be in subcategories or not.
A user interested in an Ansible will probably appreciate a single spot where he/she can see what’s going and and ask questions.
This is made more difficult with a non-device based root category + there’s quiet a bit of noise with topics that probably aren’t relevant.