4 ms·

I hate to say this, but most of the time, I just fork it, fix it, and forget it. That may sound like I'm not being a good community member. But, most of the ti

by ap22213 10y ago

I hate to say this, but most of the time, I just fork it, fix it, and forget it. That may sound like I'm not being a good community member. But, most of the time, dealing with the maintainers is more effort than I have time for.

no_protocol 10y ago
> I just fork it, fix it, and forget it. When you say you like to just fork it, do you mean that you're publishing the fixes you make somewhere, or just keeping them to yourself? I am very interested in any attempts at some kind of fork aggregator (see [0] and [1]) that can help interested parties see what patches have landed in each fork, rather than just which ones have their own users. [0]http://forked.yannick.io/jquery/jquery http://forked.yannick.io/jquery/jquery [1]http://www.toddsifleet.com/projects/github-forks#jquery/jquery http://www.toddsifleet.com/projects/github-forks#jquery/jque...
- dogma1138 10y ago
  >When you say you like to just fork it, do you mean that you're publishing the fixes you make somewhere, or just keeping them to yourself Really depends, some maintainers and authors really dislike forking, they also tend to be the ones hardest to deal with on pull requests.
- voltagex_ 10y ago
  Most of my projects are forked by people who never make any changes to the fork. I'm not sure if this is some kind of spam or people trying to make GitHub profiles look better to recruiters.
  - vacri 10y ago
    A fork = code under the user's control. A fork doesn't go away if the original source does.
  - afarrell 10y ago
    These types of forks are asirational guitars bought by people who want to spend the time but never find it.
    - reubano 10y ago
      Agreed. For me, forking is like super starring. Ive starred over 1000 repos, but hv forked < 100.
  - chriswarbo 10y ago
    GitHub's UI makes unintentional forking quite easy. When it shows a button like "Fork: 25", clicking the "25" will show the forks (which I often want), clicking "Fork" will perform a fork (which I usually don't want).
PieterH 10y ago
This is so true and so sad. It's what kills many projects: maintainers who think they have some holy mandate for "quality" and create such a difficult environment for new contributors that we fork the project instead. Read my longer comment in this thread about the C4 process and imagine: you send a patch, and it's merged onto project master within half an hour, and you can then depend on it being available to you forever, as long as you invest in some documentation and tests (if it's a new feature).
Klathmon 10y ago
I tend to do something similar, but I always at least open an issue/PR (depending on the amount of work I did on the fork) and just list the things I did, why I did them, and some useful docs/links that can help someone pick up where I left off. on multiple occasions I've gotten emails about PRs I made and self-closed with someone thanking me for the start of the general solution, and that finished it up and made it into a full PR.

by ap22213 10y ago

no_protocol 10y ago

> I just fork it, fix it, and forget it. When you say you like to just fork it, do you mean that you're publishing the fixes you make somewhere, or just keeping them to yourself? I am very interested in any attempts at some kind of fork aggregator (see [0] and [1]) that can help interested parties see what patches have landed in each fork, rather than just which ones have their own users. [0]http://forked.yannick.io/jquery/jquery http://forked.yannick.io/jquery/jquery [1]http://www.toddsifleet.com/projects/github-forks#jquery/jquery http://www.toddsifleet.com/projects/github-forks#jquery/jque...

dogma1138 10y ago
>When you say you like to just fork it, do you mean that you're publishing the fixes you make somewhere, or just keeping them to yourself Really depends, some maintainers and authors really dislike forking, they also tend to be the ones hardest to deal with on pull requests.
voltagex_ 10y ago
Most of my projects are forked by people who never make any changes to the fork. I'm not sure if this is some kind of spam or people trying to make GitHub profiles look better to recruiters.
- vacri 10y ago
  A fork = code under the user's control. A fork doesn't go away if the original source does.
- afarrell 10y ago
  These types of forks are asirational guitars bought by people who want to spend the time but never find it.
  - reubano 10y ago
    Agreed. For me, forking is like super starring. Ive starred over 1000 repos, but hv forked < 100.
- chriswarbo 10y ago
  GitHub's UI makes unintentional forking quite easy. When it shows a button like "Fork: 25", clicking the "25" will show the forks (which I often want), clicking "Fork" will perform a fork (which I usually don't want).

PieterH 10y ago

This is so true and so sad. It's what kills many projects: maintainers who think they have some holy mandate for "quality" and create such a difficult environment for new contributors that we fork the project instead. Read my longer comment in this thread about the C4 process and imagine: you send a patch, and it's merged onto project master within half an hour, and you can then depend on it being available to you forever, as long as you invest in some documentation and tests (if it's a new feature).

Klathmon 10y ago

I tend to do something similar, but I always at least open an issue/PR (depending on the amount of work I did on the fork) and just list the things I did, why I did them, and some useful docs/links that can help someone pick up where I left off. on multiple occasions I've gotten emails about PRs I made and self-closed with someone thanking me for the start of the general solution, and that finished it up and made it into a full PR.