The person who started the initiative to fork Audacity has stepped down, due to IRL harassments from 4chan.


We really can't have nice things.

audacity, music software 

This whole thing has given me a bad taste in my mouth. As an audio developer who enjoys creating open source software, this hits close to home.

The message this gives off is "stay small, don't let your software get too popular". Which is kinda shitty because it means some blend of super niche tooling helpful to no one or some form of intentional gate keeping.

I don't like it.

audacity, music software 

It's not just Audacity. I've seen issues with VCVRack and Non DAW this year. And in the past, I have had personal gripes with LMMS. The community grows, and then toxic personalities and behaviors emerge.

I'd like to work towards making open source projects of mine more accessible to people. I've even been tempted now and again to foster a community around them and explore ideas.

But then I see what happens to these people and I hesitate. I don't need that crap in my life.

My source code is available for my software. I put everything under generously permissive licensing. I lovingly document as much as I can, and try to make it easy to use for those willing to read. People can write me emails with questions, and I will usually answer them quickly and thoroughly. I think that's enough for a while.

audacity, music software 

@paul Yea, the nom story is really ugly, on both sides of the story if you ask me... I've read about the VCVRack thing too, at least one side of the story. These are just some prominent examples. Forming a community is hard. I believe, people will come if you put out a well written piece of application and promote it a bit. And eventually a community will form.

As maintainer I guess you have to make a decision, if you want to be a part of that community or not. You can throw your code over the fence and do your own thing, like Vital, or you can embrace it and make a platform for that community. Both are fine alternatives if you ask me. As original author you are not obliged to do anything. I have no clue if HexoSynth will be useful to other and if I have the motivation to do more than just development and light promotion.


@paul What I mean: and means, the moment you publish your code under a license, the code does not belong to you anymore. You have the original copy right over (large) parts of it, but that is it. If you see Github issues as things you have to address, if you want to create a platform for a community (and then moderate it) or if you want to create a website for it are super optional things.You can grow into that if you receive a lot of feedback and feel motivated though.

· · Web · 0 · 0 · 0
Sign in to participate in the conversation

This is a brand new server run by the main developers of the project as a spin-off of 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!