Perhaps it might be easiest and straightforward if we (for the time being) commit RIM specific things out (like the RIM chrome extension build), then create a new branch with revert commits of those removals, so BlackBerry can easily rebase and keep their features for their releases.
At some point, thought, perhaps there could be a way for external parties to extend the project codebase easily. For example, as suggested by Dan a while ago -> https://github.com/blackberry/Ripple-UI/issues/691 Also, I don't mind taking this issue on, as well as removing all RIM specific things, if this is agreeable. :-) On Wed, Apr 10, 2013 at 5:28 AM, Christian Grobmeier (JIRA) <[email protected] > wrote: > Christian Grobmeier created RIPPLE-12: > ----------------------------------------- > > Summary: Discuss Future of Chrome RIM Extension > Key: RIPPLE-12 > URL: https://issues.apache.org/jira/browse/RIPPLE-12 > Project: Apache Ripple > Issue Type: Bug > Reporter: Christian Grobmeier > > > From discussion on the mailinglist, asking about the RIM Chrome Extension: > > "The rim chrome extension is used for the > http://developer.blackberry.com/html5 release of Ripple, vs the Chrome > Store extension. It has a few extra things such as a slightly different > manifest.json, some different extension files to enable a UI to > build/deploy WebWorks applications, the ability to sign a EULA, etc. > > However now that we are in the incubator, I think stuff like that (and > other RIM specific things) needs to be figured out what to with (in the > best interests of the project as a whole). I.e should they be in an > external fork and not part of the main project? This is something I (or > some others) was hoping to start a discussion about soon. :-)" > (Brent Lintner) > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > -- Brent
