that confused me too, windows phone already has separate repos. apache/wp7 and apache/wp8. If we stick with the "os vendor" organization, should we refactor those repos into a single "windowsphone" repo?
On Fri, May 10, 2013 at 9:09 AM, Filip Maj <f...@adobe.com> wrote: > Which repos would need refactoring, Brian? > > On 5/9/13 2:56 PM, "Brian LeRoux" <b...@brian.io> wrote: > > >I'm a no on this. Conceptually grouping by operating system vendor > >makes more sense (to me). If we're going down this path the other > >repos need to be refacored to reflect it: cordova-platform-* (and > >Windows will need breaking out). > > > >(Also I'm not a fan of mixing pascal case with camel case but thats a > >separate issue!) > > > >On Thu, May 9, 2013 at 10:50 AM, Lorin Beer <lorin.beer....@gmail.com> > >wrote: > >> Currently, BlackBerry exists as a single repository containing 3 > >>different > >> implementations of Cordova: BB7, PlayBook and BB10. > >> > >> This has been great from a user perspective: the cordova create tool > >> allowed you to specify which target you wanted to build/run to once a > >> project has been created. > >> > >> However, BlackBerry has split the new BB10 implementation off from the > >> previous project structure: it now lives in a separate tree, and runs > >>with > >> it's own implementation of the tools. > >> > >> With the decision to send BB7 off to the farm getting positive > >>feedback, I > >> want to reopen the discussion of BlackBerry's project structure. > >> > >> Proposition: > >> split the BB platform implementations, with 3 repositories: > >> apache/Cordova-BlackBerry7 > >> apache/Cordova-BlackBerryPlaybook > >> apache/Cordova-BlackBerry10 > >> > >> we let the CLI provide the uniform interface between platforms, and > >>treat > >> these as separate implentations. It also gets ahead of the work to drop > >>BB7 > >> and avoids o "re-integrate" task for BB10 which sounds like a waste of > >>time. > >> > >> - Lorin > >
