5 ms·

Erlang alterline

9 points by yrashk 17y ago

noss 17y ago
This project is possibly a better choice to base private patches on: http://github.com/mfoemmel/erlang-otp/tree/master http://github.com/mfoemmel/erlang-otp/tree/master
- yrashk 17y ago
  may be yes, may be no — I didn't know about this repo existence when I created my repo, anyway. thanks for pointing it out!
davidw 17y ago
> However, since most probably it will not be easy to push some of these patches through Erlang/OTP, Why's that?
- yrashk 17y ago
  Well, it is what I heard from people who tried that before.
  - davidw 17y ago
    So, you have patches, and you haven't even attempted to get them committed?
    - jrockway 17y ago
      The problem is solved for him. He is really under no obligation to do anything else; if upstream is interested, they can just pull from his repo.
      - davidw 17y ago
        If anyone has bothered mentioning it to them. I sent some Erlang patches in years ago, and in due time, they showed up in the main release. Obligation? No, but it's a nice thing to do. He's demonstrated he's interested in helping out by publishing them in the first place.
        yrashk 17y ago
        I don't understand you. Wiki page I linked to explicitly states "The intention of alterline is not to fork Erlang, though — the best outcome for it is to be merged into official source tree". And I already started pushing some of the patches out: http://www.erlang.org/cgi-bin/ezmlm-cgi?3:mss:451:200908:oalelhbknmalgbgnoehf http://www.erlang.org/cgi-bin/ezmlm-cgi?3:mss:451:200908:oal...
        davidw 17y ago
        > And I already started pushing some of the patches out Cool, that's all I wanted to know. Good work!
    - yrashk 17y ago
      I am actually going to attempt to get them merged in, that's what I am saying on linked wiki page. I am just saying it might be not easy to push them there.
      - jerf 17y ago
        Are you just keeping this patches in a public tree so others can get to them, with every intention of handing them to the Erlang project, but keeping them separate and available should the Erlang project not choose to use them (and of course they can't release a patch "tomorrow")? I ask because if that's the case and you say so, it should clear up the criticism seen in this discussion. I'm not sure the community at large has internalized what github means for that sort of thing; the days where you had to take your patch to the project and that was both your first and essentially last resort are gone. There's nothing wrong with the workflow I outlined above.
        yrashk 17y ago
        Yes, there is an intention to push these patches to Erlang project, I was just saying that it might be hard.
        davidw 17y ago
        > the days where you had to take your patch to the project and that was both your first and essentially last resort are gone. They were never here. It's always been easy to fork a project, or put patches up on a web page or whatever. git makes it a little bit easier, but it doesn't change the dynamic of participating in a community much: you have to send in a patch, explain what it does, why it does it, what problems it fixes, what it improves, what costs or side effects it may have, and so on. If you send in something big (either in terms of code or effects), and care about getting it included, you may have to modify it or be prepared to defend it or otherwise work on it. git/github are not a magic replacement for this communication. Sure, you can just put stuff up on github and call it good, not caring what happens to it, but that doesn't really drive things forward as much as interacting with other people to reason about what's going on.
tsuraan 17y ago
Have you sent this to the erlang list? I just checked for both yrashk and alterline, and I'm not getting any threads for those queries. The OTP team is generally really good about merging bugfixes, from what I've seen on the list.
- yrashk 17y ago
  I've sent one of the patches so far, yes.

9 points by yrashk 17y ago

noss 17y ago

This project is possibly a better choice to base private patches on: http://github.com/mfoemmel/erlang-otp/tree/master http://github.com/mfoemmel/erlang-otp/tree/master

yrashk 17y ago
may be yes, may be no — I didn't know about this repo existence when I created my repo, anyway. thanks for pointing it out!

davidw 17y ago

> However, since most probably it will not be easy to push some of these patches through Erlang/OTP, Why's that?

yrashk 17y ago
Well, it is what I heard from people who tried that before.
- davidw 17y ago
  So, you have patches, and you haven't even attempted to get them committed?
  - jrockway 17y ago
    The problem is solved for him. He is really under no obligation to do anything else; if upstream is interested, they can just pull from his repo.
    - davidw 17y ago
      If anyone has bothered mentioning it to them. I sent some Erlang patches in years ago, and in due time, they showed up in the main release. Obligation? No, but it's a nice thing to do. He's demonstrated he's interested in helping out by publishing them in the first place.
      - yrashk 17y ago
        I don't understand you. Wiki page I linked to explicitly states "The intention of alterline is not to fork Erlang, though — the best outcome for it is to be merged into official source tree". And I already started pushing some of the patches out: http://www.erlang.org/cgi-bin/ezmlm-cgi?3:mss:451:200908:oalelhbknmalgbgnoehf http://www.erlang.org/cgi-bin/ezmlm-cgi?3:mss:451:200908:oal...
        davidw 17y ago
        > And I already started pushing some of the patches out Cool, that's all I wanted to know. Good work!
  - yrashk 17y ago
    I am actually going to attempt to get them merged in, that's what I am saying on linked wiki page. I am just saying it might be not easy to push them there.
    - jerf 17y ago
      Are you just keeping this patches in a public tree so others can get to them, with every intention of handing them to the Erlang project, but keeping them separate and available should the Erlang project not choose to use them (and of course they can't release a patch "tomorrow")? I ask because if that's the case and you say so, it should clear up the criticism seen in this discussion. I'm not sure the community at large has internalized what github means for that sort of thing; the days where you had to take your patch to the project and that was both your first and essentially last resort are gone. There's nothing wrong with the workflow I outlined above.
      - yrashk 17y ago
        Yes, there is an intention to push these patches to Erlang project, I was just saying that it might be hard.
      - davidw 17y ago
        > the days where you had to take your patch to the project and that was both your first and essentially last resort are gone. They were never here. It's always been easy to fork a project, or put patches up on a web page or whatever. git makes it a little bit easier, but it doesn't change the dynamic of participating in a community much: you have to send in a patch, explain what it does, why it does it, what problems it fixes, what it improves, what costs or side effects it may have, and so on. If you send in something big (either in terms of code or effects), and care about getting it included, you may have to modify it or be prepared to defend it or otherwise work on it. git/github are not a magic replacement for this communication. Sure, you can just put stuff up on github and call it good, not caring what happens to it, but that doesn't really drive things forward as much as interacting with other people to reason about what's going on.

tsuraan 17y ago

Have you sent this to the erlang list? I just checked for both yrashk and alterline, and I'm not getting any threads for those queries. The OTP team is generally really good about merging bugfixes, from what I've seen on the list.

yrashk 17y ago
I've sent one of the patches so far, yes.