Many of us write opensource code in a void: nobody ever looks at it, uses it nor reviews it. We are the only users and authors.

In order to improve, where can we get our code reviewed? I don’t mean professionally, just from like-minded individuals.

  • stifle867@programming.dev
    721·
    1 year ago

    This is not an answer to your question but it’s tangentially related.

    Someone I greatly respected ran an open-source project with the policy of merge everything. Completely flip this idea of carefully review, debate and revise every PR. His theory was that it helps to build an open community, and if something breaks someone else will revert that commit. He says that the main branch was almost always stable, a massive improvement to how it was run previously. He passed several years ago and for some reason this reminded me of him.

    I guess what I’m trying to say is if you get something out there that people find useful, the code will be looked at. It doesn’t help you if you’re looking for someone to collaborate sorry.

    • varsock@programming.dev
      16·
      1 year ago

      There is a very effective approach (34:00), that big companies like cloudflare use, to ship a product in a fast and quality way. It bears parallels to what you are describing. In essence engineers should not get hung up in the details to trying to solve everything.

      1. Just build a proof of concept
      2. Discard the prototype no matter what and start from scratch keeping the initial feedback in mind
      3. Build something internally that you yourself will use
      4. Only once something is good enough and is used internally, then release it to beta.

      So that tedious process in trying to flush out all the details before seeing a product (or open source effort) working end to end, might be premature before having the full picture.

    • jeremyparker@programming.dev
      11·
      1 year ago

      That’s Wikipedia’s approach, arguably one of the most successful “open source” projects in history - certainly not without its problems, but overall it’s pretty great

          • stifle867@programming.dev
            21·
            1 year ago

            It’s great to see the attempt and also an example of what the C4 guidelines are made to avoid.

            Notice how many comments are little nitpicks about this and that. Completely stalling the commit and getting further away from the original point of C4 which is to reduce contributor friction and avoid these kind of endless discussions on PRs.

            I don’t want to be too critical because some of that is a clear lack of understanding of the motivations of C4 which is explained more thoroughly in Pieter’s blog posts. You don’t want to adopt a contributor guidelines that you don’t understand of course.

            IMO it’s better just to implement it as-is and start using it in practice rather than bikeshedding.

    • kisor@programming.devEnglish
      3·
      1 year ago

      This is for 0mq right? I remember reading Pieter Hintjens about this realization he had over a long time of developing 0mq.

      • stifle867@programming.dev
        7·
        1 year ago

        Yes that’s right. I was only just transitioning into adulthood and Pieter mentored me and profoundly changed how I view many things. It wasn’t just zeromq but that was the main thing. I still keep his books at hand on my bookshelf. His death impacted me greatly.

      • kassuro@feddit.de
        15·
        1 year ago

        Would love something like this, but it’s very hard to get such a community working. Most of the time there will be way more people wanting a review of their code than people wanting to put in the work and review something.

        Maybe some kind of point system could work. Like one needs to review at least two times before you can get your work reviewed.

        • lhamil64@programming.dev
          9·
          1 year ago

          One issue I can see with the points system is that people could just approve it with a “Looks good to me!” without even looking at the code. Or just looking at a small portion of the code.

          • coloredgrayscale@programming.dev
            3·
            1 year ago

            Also bike shedding. Simple stuff may get many people willing to review / argue about how you should have used A over B, or even C

            Big / complicated projects - forget it. Especially if if they would need major refactoring.

            • kassuro@feddit.de
              3·
              1 year ago

              But who decides that? If the person who requested it can do this, you only need a friend to abuse the system and give each other a few extra points.

              Maybe a open point history could help with this and users moderate themselves with this.

          • kassuro@feddit.de
            1·
            1 year ago

            Yeah that’s definitely a possibility. It’s really a tricky topic to build a review community. One could try other approaches like dedicated volunteer reviewers. But if you look at exorcism, that will become hard to manage for languages with huge demand.

            A system where everyone also needs to review is definitely better. Especially since everyone also learns reading other peoples code.

        • Ategon@programming.devM
          3·
          1 year ago

          with that there would need some way for people to have things to initially review to get the community started. Could do something like after the first 3 posts the point system goes into effect

          • kassuro@feddit.de
            2·
            1 year ago

            True, it’s not a fleshed out idea haha. But starting with a few points would work.

            Could actually be a cool in it self, wish I had time for something like that.

            • vrek@programming.devEnglish
              1·
              1 year ago

              Something like c sharp acedemy would be kinda cool. Basically do some beginner projects with good code reviews you get a “belt”. That belt allows you to review the beginner projects as you work on intermediate projects. Then you complete those and get another belt that let’s you do advanced projects and review the intermediate projects others submitted.

  • RoToRa@discuss.tchncs.deEnglish
    26·
    1 year ago

    There is a Stack Exchange community for code reviews: https://codereview.stackexchange.com/

    However they have some strict rules on what is allowed so it may not be suitable for open source projects. Two problematic ones are: 1) The poster must be the author/owner of the code. You, for example, can’t post code that someone else has written. 2) All code that is to be reviewed must be included in the post. You can’t just link to a repository.

  • Nulubez@sh.itjust.works
    13·
    1 year ago

    I would totally get in on that. Seems almost like a fun OS project itself. Like a volunteer hub type site to just seek reviews

  • theherk@lemmy.world
    6·
    1 year ago

    There was something like that on Reddit but I can’t remember the sub. I haven’t seen one here. The best way to get reviews of open source is via contributions to larger projects. That of course doesn’t answer your question directly but is worth noting.

    I’d recommend joining some discord or matrix servers for the language you work in or likeminded folk. They tend to have channels for that, and some have really helpful communities.

    eta: I just checked my local instance and saw a community with very few subs and zero posts called /c/reviewmycode. Somebody has to post first.