3 ms·
Yes, GitHub is wonderful. It makes contributions so trivial that it's worth to pull even the littlest of the modifications. For instance: http://github.com/anti
by antirez 16y ago
Yes, GitHub is wonderful. It makes contributions so trivial that it's worth to pull even the littlest of the modifications. For instance: http://github.com/antirez/redis/commit/ca3f830b32a0a8303a5a761d6212925d9b5ac365 http://github.com/antirez/redis/commit/ca3f830b32a0a8303a5a7...
Instead I think that an impressive amount of energy and work is often wasted because many developers will design & code an important patch before getting in touch with the author of some project. So the author will see a patch that probably makes totally sense but is not what was desirable for some reason (future directions, too bloat, there is a better way to do that).
If it's the kind of project where you can join some IRC channel or drop an email to some mailing list and get in touch with one of the developers, it's really a good idea before starting to code.
- _glass 16y agoFor trivial changes as describe in the article? I tend to disagree. Decentralization saves you this administrative issues, like getting in touch with people in advance, before they can see if you are really interested by actually coding. I think it shows your value of this community if you are contributing in the small at first if it is a larger project.
- antirez 16y agoI wrote "... will design & code an important patch ...". For important patches this is required, not for small changes.
- _glass 16y agoHm, I am sorry, but have to be picky about language: changes can be important but trivial. What I really meant: If this patch is easy and fast to produce, don't contact the developer. Even if it is an important change.