Hi, > Don't we just fork it if we need changes? We should be taking the same tact > with Picasso too. We don't need to be limited by what changes can be > upstreamed. We should work with 3rd party code to upstream changes in an > acceptable way for the 3rd party code, but that doesn't mean we are limited. > If we didn't use 3rd party code, we be writing code ourselves. Code that > we'd need to maintain on our own. Not much different than the situation Wes > is talking about.
Also, keep in mind that not all changes are made equal. Things like bug fixes tend to get quicker response than, say, new API proposals. We won't be requesting new APIs for NineOldAndroids as the goal of the project is to mimic the official API anyway. I agree with mfinkle: I'd prefer to maintain a few changes in a local fork of a library than creating and maintaining code for problems that have already been solved pretty well by others. --lucasr _______________________________________________ mobile-firefox-dev mailing list [email protected] https://mail.mozilla.org/listinfo/mobile-firefox-dev
