Timeline for How do I alter an open source library for my own use?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 25, 2013 at 18:53 | vote | accept | OdieO | ||
| Sep 25, 2013 at 18:33 | comment | added | Karl Bielefeldt | Right. Keep in mind, they might accept part of your changes even if the entire thing isn't accepted. The closer you are to the official version, the easier it will be for you to maintain. | |
| Sep 25, 2013 at 18:22 | comment | added | OdieO | OK, just to be super clear so I know where I'm heading. I fork it. If I end up making major mods then maybe the author accepts them all and the original project is now significantly altered. If they don't accept it then I either maintain my own fork or spin it off into a separate project. Is this right? | |
| Sep 25, 2013 at 18:16 | comment | added | Karl Bielefeldt | That heavy of modifications, you probably want to run by the library author first. Either way, a github fork is the way to go. At least if he doesn't accept it, it will be easily found by other users. | |
| Sep 25, 2013 at 18:14 | comment | added | OdieO | @Philipp. Thanks. Both of your answers made the answer to my question very clear... A follow-up question - I've looked over the library and it looks like I might want to modify very heavily as I work on this component (the camera component of the app). I might end up changing perhaps 50% of the code in the main class... If this ends up being the solution, would forking be the proper way to start on this path? And then if it diverges enough to where it becomes a different project then I eventually just separate it into it's own project? | |
| Sep 25, 2013 at 13:13 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |