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 brian.leroux@gmail.com
 designates 209.85.210.172 as permitted sender)
MIME-Version: 1.0
Sender: brian.leroux@gmail.com
In-Reply-To: 
 <CABiQX1Wu5=idTb-D70GZb8ykBaMdK1oYO09SvSKj60eyeXxK3g@mail.gmail.com>
References: 
 <CAOBL_k4EhX0UzWdP1UVHEwB2SgOEH+8F2nUB5cPRxmP7nYxJhQ@mail.gmail.com>
	<CANpVHHy0b63ju_t2ghesyioFRbpxLFENd=GBzxzX+ryAH68XCA@mail.gmail.com>
	<CADVgkyOoC4AcrTvbFwdNziM1ohs+sLO68n7fYcs5LvPeQnXNCA@mail.gmail.com>
	<DC9B7BA4-83FD-483D-81E8-7D7875C4D82F@redhat.com>
	<CAAzFgygyNdD+w9=-gbE_KnsvcfLqyaSRCCBFwwjM4yziWfTSVA@mail.gmail.com>
	<CAOBL_k5=sjkVcQ+onu+tOzjN7Oh7wx6wvQV_QJB9t9x9r0AGNg@mail.gmail.com>
	<CAAzFgyiSZ8-kfYWBMQHvv5YXyCV9hqfPhb2aWRXZdxnB7TsbXA@mail.gmail.com>
	<CAOBL_k47a6T8ApxFyxCOu3sX-Aq=DnK-GKW5dksgb0UGfUL4Mg@mail.gmail.com>
	<CADVgkyMhhjZmYNdQmSQP2SZBYF1kfjHcknyPmbsx=xFVBYfEMg@mail.gmail.com>
	<CABiQX1Wu5=idTb-D70GZb8ykBaMdK1oYO09SvSKj60eyeXxK3g@mail.gmail.com>
Date: Fri, 5 Apr 2013 13:40:41 -0700
Message-ID: 
 <CADVgkyPYAepLaH5H2fd+Ykoqbm6j6+DnYwQ9oQ0pqSUY3ejRww@mail.gmail.com>
Subject: Re: The plugin repos and reality
From: Brian LeRoux <b@brian.io>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=089e01538d5cb7fc6f04d9a319cb

--089e01538d5cb7fc6f04d9a319cb
Content-Type: text/plain; charset=ISO-8859-1

Those should be rolled back in by the COHO tool (using the plugman tool)
for the phonegap dist.


On Fri, Apr 5, 2013 at 1:24 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> I agree that moving plugins into repos isn't tied to API audits, but
> doesn't moving plugins gradually prevent our ability to do releases? E.g.
> 2.7 is missing two plugins since they were moved into different repos.
>
>
> On Fri, Apr 5, 2013 at 4:20 PM, Brian LeRoux <b@brian.io> wrote:
>
> > That synopsis on the wiki was super helpful Joe. I think we should stop
> > thinking we have to do EVERYTHING ALL AT ONCE. We do not need to audit
> any
> > apis. We do not need to update anything before moving into plugins.
> >
> > We need to slowly move a plugin at a time, keep their current APIs, and
> > methodically move to the next API.
> >
> > Anything that does not fit: don't move it out. We'll deal w/ it later. It
> > looks like everything 'with specs' can be moved with relative ease. Start
> > there. Worry about the rest when you get there. I suspect that is plenty
> to
> > try to achieve in the meantime.
> >
> >
> >
> > On Fri, Apr 5, 2013 at 12:51 PM, Joe Bowser <bowserj@gmail.com> wrote:
> >
> > > On Fri, Apr 5, 2013 at 12:34 PM, Max Woghiren <maxw@chromium.org>
> wrote:
> > > >
> > > > In Android, I've split out common File code into a FileHelper class.
> > >  It's
> > > > not a plugin, and will be exposed to developers.  This is the only
> > > > shared-code example I know of, but if we find others (via the
> > visibility
> > > > removal test), we can similarly pull out the common code.
> > > >
> > >
> > > There's a lot of code that's meant to be public on CordovaWebView,
> > > since CordovaWebView is supposed to be a stand-alone component that's
> > > embeddable in other Android projects.  We really need to decide what
> > > to expose.  I also want to see DroidGap paired down and gone, since I
> > > don't want people messing with anything in that class at all.
> > >
> > > Other than that, I can't think of any Android code that should be
> > > public. That being said, I think we're getting off-topic.  I think we
> > > need to start on the dreaded API audit that we've been putting off.
> > > It's clear that every plugin will need to be updated to the new spec
> > > before we do this exercise.
> > >
> >
>

--089e01538d5cb7fc6f04d9a319cb--