Lower the Barrier for Scratching Open Source Itches
ill-logic-tech.blogspot.com
ill-logic-tech.blogspot.com
apt-get source packagex
apt-get build-dep packagex
tar xzf …
code code code
dpkg-buildpackage
diff -u … > patch.diff
bugreport -A patch.diff packagex
The functionality's all there; all that's really needed is a FAQ pointing it out.
So, sorry, just to be clear, what does the ... mean?
Granted, tar & diff are the two steps which could most stand to be streamlined (and are by your git approach), but at least they're nothing earth-shattering.
I thought this was quite useful. I made quite a few patches this way and was very productive using this script (in some cases, it took me only about 2-5 minutes to prepare a patch if the fix was easy).
Though, the script was very hacky and it still often needed some hand-work to be made. I asked some Gentoo developers if there might want to make a full project out of this (because I thought that this might be a useful and important thing) but nobody really was interested.
A typical open source experience for me (some 90% of cases) is I download a package, compile it, and it doesn't compile. Something is missing or it can't handle the latest version of the OS, or there is some library with the wrong version.
Now fixing it can take 1 hr to 6 months of work and you don't have any idea before you start.
The answer for me now is "why bother" and I stop there. In general it saves money to buy commercial software that does the exact same thing rather than figure this stuff out for 9 out of 10 open source downloads.
In the past I would fix the problem and try to submit a fix. Wrong answer! You can't submit a fix. Most projects won't accept it unless you join their cult, endure hazing, chat about politics and accept their belief system, and adulate their leaders and trolls.
Not worth it at all.
edit: Thanks for the downvotes. Do you really feel the above contributes nothing, or do you just not tolerate those who point out there are serious problems with the ability of non-project members to make open source contributions? I assure you these are real problems. I also am not surprised that anything other than adulation of Stallman's testicles is furiously downvoted by basement denziens.
This, and a bit more, is what I'm hoping can be eliminated here.
As to the rest of it, I guess I never got far enough to find out. I hope it's not always true :( I don't see the point of voting you down either, if it's true it's true.
Truth is you'll get a better reception without pointless angry tripe.
I've no way of knowing what your OSS experiences have been, so I'll take you at your word. However, a broad statement such as this:
"Most projects won't accept it unless you join their cult, endure hazing, chat about politics and accept their belief system, and adulate their leaders and trolls."
... strikes me as patent bullshit. Maybe most projects you've tried to contribute to have turned out this way, but then I have to wonder if the problem is with the project owners or if maybe you approach things with an incredibly dismal attitude.
Some project owners and communities may suck, but most? You'll have to provide something more than bitter anecdote.
The biggest problems I've had with OSS projects is not getting an answer to questions. There are a good number of "works for me" code repos that simply refuse to build on my system no matter what dependency dance I do. If that's the case I go look for an alternative (though on Linux it's typically not something I can purchase).
Mostly I get things to almost work and get stuck, and then join a forum or mailing list or something to get some help.
Help tends to be of two forms: None at all, or friendly and pragmatic.
I've offered patches to a few projects, and everyone has been very nice about it, even when I forget to include unit tests or fucked up their coding convention. Maybe I've just been lucky.
As the maintainer of several OSS projects I empathize with those I contact for help ro offer patches. Time is often short, and most people aren't getting paid to support their OSS projects.
Most of this is all a gift, and when a gift turns out to be not quite what you hoped for better to just move on and be grateful for you have, not bitter about what you didn't get.
If you're using Debian stable or Ubuntu, in almost 100% of cases, you can get things to build. apt-get source and apt-get build-depends will get the exact source code and prebuilt dependencies that were used to build the exact binary you are running. Gentoo is presumably even better, since they don't even distribute binaries. And, of course, anything in an interpreted language lacks this problem.
Most projects these days have public bug-tracking systems where you can post your patch. Then anyone else who has the same problem or wants the same feature can use your patch, even if it hasn't been accepted.
Is there such a thing, is this a good idea?
I love that there are communities where "regular user" and "coding skills" overlap.