4 ms·
> I wish there was a formula for making things more attractive to contribute to (in both the short and long term), but it's a fiddly process. I'm trying to ela
by mabynogy 9y ago
> I wish there was a formula for making things more attractive to contribute to (in both the short and long term), but it's a fiddly process.
I'm trying to elaborate something for that. On way I see is to reduce the entry level as much as possible.
I deduce that a project aiming a lot of contributors should be heterogeneous (contributors can choose their favorite language)and shouldn't have a single build system (interfaces exists at runtime with a middleware, vms, or files).
- fundamental 9y agoThat might work or it could backfire. With more build systems and more languages, then you can easily end up in the category that someone needs to know all of them to make meaningful changes. If you have people staying in their own part of the codebase it's easy to imagine significant bitrot occurring over time.
- mabynogy 9y agoI imagine software isolated in vms. Many people could do the same thing or overlap with someone's else project. It would allow projects to compete.
- fundamental 9y agoInteresting. That's a radically different view on what a project should strive for than my own. My own FLOSS work focuses on getting work closer to the system's metal in order to have a responsive low-latency/realtime configuration (realtime being in the realtime signal processing sense). In this area in particular people doing the same things results in reasonable breadth of work, but insufficient depth. So plenty of options, but all of them not good enough to compete with larger development teams.
- mabynogy 9y agoI've seen your website. It's really fascinating.