Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates
 209.85.214.181 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CAE6O_-a1YdFUF7PoiirJbLp1dC+2_CY-qr42sNa5DWJrdvRYAg@mail.gmail.com>
References: 
 <CABiQX1VtucRnKMfnnCPi4wcJqJ2kT05_f4U0O5gKBNVLC_wUug@mail.gmail.com>
 <CADVgkyO05UE2en3VWizO-50JtfcbuY7CWoFPOko125LuZm1QGg@mail.gmail.com>
 <CANpVHHw-_h=vfgV5sOT1J=_=Ahct-hFTUGaE3jC-cqfGs6WXNA@mail.gmail.com>
 <CAKP6k2uy3Z_yO6_Pz3fWzVA0aqe1Zp62PA7Oae7qVUsTO_RC9w@mail.gmail.com>
 <CAE6O_-a1YdFUF7PoiirJbLp1dC+2_CY-qr42sNa5DWJrdvRYAg@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Tue, 5 Feb 2013 09:34:53 -0500
Message-ID: 
 <CABiQX1UWty6+n_Bz7O6Ssv=48k5rb_-Nhj51HGJeApVQGwROxw@mail.gmail.com>
Subject: Re: Creating repos for core plugins
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=14dae93a12571a866504d4fb1e78

--14dae93a12571a866504d4fb1e78
Content-Type: text/plain; charset=ISO-8859-1

Great! Sounds like an agreement :). I'll file an INFRA to get them created.


On Mon, Feb 4, 2013 at 9:44 PM, Shazron <shazron@gmail.com> wrote:

> +1 on separate repos. It's the sane choice.
>
>
> On Mon, Feb 4, 2013 at 11:53 PM, Jesse <purplecabbage@gmail.com> wrote:
>
> > +1, I agree on the separate repositories.
> > I still contend that nothing should need to be 'built' and there should
> be
> > NO dependencies on the plugins from cordova-js, ( aside from device.js +
> > network.js which are both required pre device ready, and I think should
> > remain in the cordova-js repo )
> >
> >
> >
> > On Mon, Feb 4, 2013 at 2:46 PM, Anis KADRI <anis.kadri@gmail.com> wrote:
> >
> > > +1 for separate repositories. Should take a bit longer than normal to
> > > package a release but not too long especially if the repos are pulled
> > from
> > > a local source (ie no network overhead).
> > > I'd be ok to ship a set of default plugins and give the ability for
> > people
> > > to build their 'own' Cordova.
> > >
> > >
> > > On Mon, Feb 4, 2013 at 2:11 PM, Brian LeRoux <b@brian.io> wrote:
> > >
> > > > I'm in favor of discreet plugin repos. It shouldn't effect a release
> > > > if we automate install/remove and add to the Coho tool... though
> > > > perhaps this is a naive assumption.
> > > >
> > > > On Mon, Feb 4, 2013 at 1:44 PM, Andrew Grieve <agrieve@chromium.org>
> > > > wrote:
> > > > > Thought it'd be worth having a discussion around whether we want a
> > > > separate
> > > > > repo for each core plugin or not.
> > > > >
> > > > > As far as I can see, we can either have all core plugins in one
> repo,
> > > or
> > > > > have each in it's own and call them:
> > > > > cordova-plugin-file
> > > > > cordova-plugin-network
> > > > > cordova-plugin-media
> > > > > etc...
> > > > >
> > > > > I think my preference would be to have them as their own repos so
> > that
> > > it
> > > > > will be easier to add/remove lists of plugins to the "which ones
> are
> > > > core"
> > > > > list. It will also let us version them separately (if we want to do
> > > > this).
> > > > >
> > > > > The downside is that it may take longer to perform a release? Would
> > we
> > > > even
> > > > > bundle the plugins with releases anyways though?
> > > >
> > >
> >
> >
> >
> > --
> > @purplecabbage
> > risingj.com
> >
>

--14dae93a12571a866504d4fb1e78--