• 0 Posts
  • 63 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle











  • Clean git histories are fun for the people who care, but they are also mostly useless.

    I’ve been around a lot of arguments about the commit standards in teams and it’s always boiled down to the “I don’t care, but I don’t want to spend time doing anything special” people vs the “do the things the way I like because I can think of three reasons it’s technically superior but not practically useful to do so” people.

    Bikeshedding at its finest




  • I feel like this is a very modern problem with the community. I’ve been in open source for a long time, I’ve been employed by some of these companies to write open source things.

    Most open source stuff was created by someone who was employed to write that open source thing. There are exceptions, of course, but most things came about because of a need, and that need is often related to work. Companies used to be a lot better with allowing open sourcing of components.

    Then, there are all the community contributions that come from commercial reasons. If someone working at a company fixes a bug they encounter, that’s someone being paid to write open source software.

    I do not understand the reaction people are having to this now. The open source ecosystem was built on this.



  • I’ve been around open source for 20+ years and can tell you right now that it don’t work that way. An issue tracker and a wiki is not a community.

    Most older open source communities were built on irl connections and irc, with some mailing lists thrown in. Hell, we even funded conferences just around the software, not to sell a product but just because it’s good for everyone to be talking to each other.

    The issue tracker tracks the status of things, the wiki is generally user focused. It’s not where development happens or thinks get built.