1. 51

Sorry for editorializing the title, but I don’t think it would make sense to post this with the original title. Also sorry if this is off-topic, it’s just that I don’t think this side of Linus gets as much coverage.

  1.  

  2. 15

    Since this is old, I was wondering: did they?

    $ git log --oneline --author="Jesper Juhl" | wc -l 
     746
    
    1. 3

      I think this was before git.

      1. 5

        I think they imported history into git.

        Also, that’s 746 commits from that author.

        1. [Comment removed by author]

          1. 2

            Does the grafted history pre 2.6.12 not work?

            https://lwn.net/Articles/285366/

          2. 2

            Well I’m an idiot. That’s cool :)

      2. 7

        I love this concept of having new people submit “tiny” patches. It’s super important to let people participate in the dev process.

        As an aside, I wonder if you could have a “democratic” maintainer system for smaller patches. Like Linus was saying, you can end up with 99 patches and no merging… could there be a sort of voting system where people vote up or down patches and it auto-merges after 50 votes of confidence or something?

        I feel like the abuse potential is high but it would be an interesting exercise for a smaller project

        1. 13

          I think a well-oiled CI toolchain helps a lot here. Remember that that post is 12 years old.

          Rust for example has a bot that automatically asigns reviewers to issues that can quickly answer with “r+” if something is okay, in which case another bot comes, builds the whole thing, tests it and merges it into master. Very tiny patches don’t need much more interaction then that.

          1. 4

            Well, a vote by yet another mini-patcher might not be “worth” much… Ideally, you would want votes by maintainers to count more, but I’m not sure whether that could be built into Git.

          2. 5

            Yeah, it’s interesting to see this side of him. We mostly just see that he’s grumpy (if not mean), but the Linux project wouldn’t be so enormous and popular if he didn’t have some skills as a manager.

            1. 11

              I think his rants just get more press. From what I’ve seen he’s usually pretty nice, and even when he’s not he usually uses hyperbole which gets misinterpreted. Of course, that’s just my impression.

              1. 2

                Nothing sells like conflict.

            2. 4

              It seems to me that this is a good philosophy even beyond the kernel and, in fact, beyond FOSS. Even in a corporate setting, where the software is closed, small contributions are a great way to onboard new employees to a company, team, or project. From the perspective of a given team, accepting small patches from elsewhere in the company is a great way to increase project visibility and buy-in.

              1. 3

                I know anecdotally this is how I’ve gotten started on my last two major projects. It’s an encouraging and quick way to start participating and get into the feedback loop.