Timeline for Modifying an open source application
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2011 at 19:17 | vote | accept | Daniel | ||
| Aug 22, 2011 at 7:49 | comment | added | Rommudoh | if there are automated test cases, run them before you submit the patch. | |
| Aug 22, 2011 at 5:15 | history | edited | ZJR | CC BY-SA 3.0 | added 1 characters in body |
| Aug 22, 2011 at 5:14 | comment | added | ocodo | @ZJR Seriously?! Suggesting that people rant and rave on their blogs because their patch wasn't accepted is hardly likely to improve the levels of maturity in the OSS community is it? Anyway, you get an upvote for pulling that rant incitement, and for adding the github way. :) | |
| Aug 22, 2011 at 5:03 | history | edited | ZJR | CC BY-SA 3.0 | added 602 characters in body |
| Aug 22, 2011 at 4:54 | history | edited | ZJR | CC BY-SA 3.0 | added 602 characters in body |
| Aug 22, 2011 at 4:49 | history | edited | ZJR | CC BY-SA 3.0 | added 602 characters in body |
| Aug 22, 2011 at 4:34 | comment | added | ZJR | @Dani lol, you'll really have to take the share a patch and rant about it way. Avoid forking as it will consume your life, it feels like refactoring continuosly without a paycheck. ...anyway, check with the mailing list and the bug report system if there's one, to see if anyone would be interested in such kind of extension, maybe you're not alone. Aaaand the best would be of they had some API to extend or a plugin-thing to plug your changes into. That is always the best option in such cases: mantaining a plugin. ...will edit that in. | |
| Aug 22, 2011 at 4:30 | comment | added | ZJR | @Slomojo OSS is full of immature people, and that kind of thing happens all of the time, everybody should be prepared to work like a mule and then be rejected on basis that sometimes are solid and sometimes are moot. And then, at least, you always have the chance of ranting about it and find people that feel you maybe are right. Now, forking out of spite, that would be the wrong and very kiddish step to take. | |
| Aug 22, 2011 at 4:27 | comment | added | Daniel | The application I want to change is following a strict standard which with my changes will break the standard. I think I'm not even in position to ask my patch to be applied. | |
| Aug 22, 2011 at 4:19 | comment | added | ocodo | All good until you suggest the OP flames the product authors for not embracing the new feature patch, it's unclear if this was supposed to be funny or serious, either way, it's VERY bad form to effectively cry like a little kid to the whole world because a product team don't like/want your new feature patch. By all means, post it up but always be magnanimous if it wasn't accepted, regardless of how illogical the decision seems to be. -1 - FYI, I'll happily reverse my vote, if you remove that. | |
| Aug 22, 2011 at 4:17 | history | edited | ZJR | CC BY-SA 3.0 | added 81 characters in body |
| Aug 22, 2011 at 4:12 | history | answered | ZJR | CC BY-SA 3.0 |