Comments below: 1. WRT to the client code, why not simply git clone gecko-dev and make a branch? Git is good for this stuff.
2. I don't think we want a fork as a long-term prospect. Just for the next week or so while we work out the right thing. 3. I very much do not want to use a versioned hg series. That's very git-unfriendly. I would prefer not to have a branch. Let's solve the logistical problem and land right on m-c. -Ekr On Thu, Feb 27, 2014 at 8:54 PM, Dan Mosedale <[email protected]> wrote: > Loop already has a server in github, which is off to a fine start. > Figuring out how to structure our code for mozilla-central has turned out > to be a bit complex. In order to remove that as a roadblock from more of > the MLP technical work, and get the technical work moving faster ASAP, > here's a proposal for where to put the various pieces of Loop work in the > interim now as the rest gets sorted out. > > At the very least, we need to find an interim home for the browser-side > front-end and the standalone conversation window before Sunday, when a > number of folks will be working on standing stuff up in London. > > Here's the proposal, on which I'd love feedback: > > https://webrtc.etherpad.mozilla.org/loop-temp-process > > If I don't hear significant objections by the end of business tomorrow > (Friday, Pacific time), I'll go ahead with creating the loop-client repo as > proposed in the Etherpad. > > I expect that it'll take a day or two next week before we can nail the > rest, in part because I very much want Standard8's input there, and he's > out of the office today. > > Thanks, > Dan > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media > _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
