Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.220.170 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: 
 <CADVgkyM0fGFatWhm-5PkVMsA0RwFV-mXSWEQbu=HEptDkkOggg@mail.gmail.com>
References: 
 <CAE6O_-aCYwN56Nzsu27AicAi4GOVfgHhWpkzV8KsCW+5Xj+8dg@mail.gmail.com>
 <CAHYtTqnc+WTLeZLmP4ax64P3+pS5ZKmFW0vJBP53+Wcc9c9YXA@mail.gmail.com>
 <CAMSbhBiYHVDMev7Hmi7OY1QjiC=DkeNubDucRUf9ttnn89ZBtQ@mail.gmail.com>
 <CAEeF2TdB6-Z4d9-g=wRXs+HDCWtKM8xfYn+fLaREBZfhvKzofg@mail.gmail.com>
 <CAKP6k2v6qNtaoFkr-K-4Um3YUs-m0=J8M1LCwDAmBf103vx-2w@mail.gmail.com>
 <CAEeF2TcfZhLr8uv-ztf73RVno6BHNv=U4KYsGRq9AOwofOay_g@mail.gmail.com>
 <CAMk5LLmHV0FsVemdLVxjYCRwFVKjiKAa_perEtHw27mzLpSB6w@mail.gmail.com>
 <CADVgkyM0fGFatWhm-5PkVMsA0RwFV-mXSWEQbu=HEptDkkOggg@mail.gmail.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Mon, 25 Nov 2013 11:44:34 -0800
Message-ID: 
 <CAEeF2TcmxL4E8xnH5RVU_ONdx_GEK=RVsWwyOZOBq5HJyeLv2g@mail.gmail.com>
Subject: Re: cordova-plugins repo release
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7b339e07183e8b04ec059900

--047d7b339e07183e8b04ec059900
Content-Type: text/plain; charset=ISO-8859-1

Okay -- while I do agree with Braden -- in the interests of not debating
again, I'll concede to not publishing core plugins from a shared repo (if
for no other reason than for consistency with the other core plugins).  But
I think its still worth having a cordova-plugins repo for early
experiments/incubation period so you don't have to file a ticket with INFRA
before you even get started.

Seems the two published plugins are keyboard and statusbar, so we should
get INFRA tickets to make repos for those?

-Michal


On Mon, Nov 25, 2013 at 10:47 AM, Brian LeRoux <b@brian.io> wrote:

> Super disagree about putting src into a single big repo. I get why we do
> that. I do not buy that we 'have too many repos' or that complexity is
> minimized by combining. Anyhow: not a discussion I think is even worth us
> having AGAIN. =/
>
>
> On Mon, Nov 25, 2013 at 10:32 AM, Braden Shepherdson <braden@chromium.org
> >wrote:
>
> > Hang on a second:
> >
> > The release you send to the plugman registry doesn't care about git. You
> > point it at a (sub)directory and it uploads the plugin. The version is
> set
> > by the plugin.xml of that plugin.
> >
> > If we want tags for when those plugins were pushed to npm, what's wrong
> > with tags like "whateverplugin-1.0.0"? It's a little cluttered to see all
> > the tags for all the plugins, but you can still see all the releases of a
> > given plugin. They're in this repo precisely because they're small or
> > experimental and not ready for their own repos yet.
> >
> > -10 to one repo per plugin; we have way too many repos already, and this
> > cordova-plugins repo is intended to be the catchall place for small and
> > experimental plugins.
> >
> > Braden
> >
> >
> >
> >
> > On Mon, Nov 25, 2013 at 11:05 AM, Michal Mocny <mmocny@chromium.org>
> > wrote:
> >
> > > Would that only be true if you shared readable tag names between
> plugins?
> > >  If we used tags unique to each plugin, perhaps by prefixing tags with
> > the
> > > target plugins' name, then plugin releases would be isolated, right?
> > >
> > > -Michal
> > >
> > >
> > > On Fri, Nov 22, 2013 at 8:02 PM, Jesse <purplecabbage@gmail.com>
> wrote:
> > >
> > > > The issue that if use a tag to signify the new version, then the tag
> is
> > > > applied to all plugins in the repo. This is probably not a big deal
> for
> > > > minor bumps, but when a plugin needs a major bump, they all will. So
> > you
> > > > will/could have a plugin with a major version bump even though the
> code
> > > has
> > > > not changed.
> > > >
> > > >
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Fri, Nov 22, 2013 at 6:36 PM, Michal Mocny <mmocny@chromium.org>
> > > wrote:
> > > >
> > > > > I don't understand, whats the problem?  I thought you publish
> plugins
> > > by
> > > > > git-repo & subdir & hash -- so multiple plugins makes no
> difference.
> > > > >
> > > > > The master & dev branch deal was to do with cordova-3.0 users that
> > did
> > > > not
> > > > > support plugin repo install from !master branch, right?  But none
> of
> > > > these
> > > > > plugins in cordova-plugins existed back then, so we just set engine
> > > > > requirement to 3.1?
> > > > >
> > > > > -Michal
> > > > >
> > > > >
> > > > > On Fri, Nov 22, 2013 at 1:32 PM, Steven Gill <
> stevengill97@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > +1 on one plugin per repo. Would making releasing and tagging
> much
> > > > > simpler.
> > > > > >
> > > > > >
> > > > > > On Fri, Nov 22, 2013 at 1:29 PM, Carlos Santana <
> > > csantana23@gmail.com
> > > > > > >wrote:
> > > > > >
> > > > > > > Yep that's the problem with having independent plugins in a
> > single
> > > > > repo,
> > > > > > > and just using directories to separate them.
> > > > > > >
> > > > > > > If I would have a choice I would strongly encourage one plugin
> > per
> > > > repo
> > > > > > > containing its own version and source control.
> > > > > > >
> > > > > > >
> > > > > > > On Friday, November 22, 2013, Shazron wrote:
> > > > > > >
> > > > > > > > The cordova-plugins repo has plugins as well, but are outside
> > of
> > > > the
> > > > > > > > purview of the planned weekly core plugins release - I plan
> to
> > > > upload
> > > > > > > > independently.
> > > > > > > >
> > > > > > > > The repo does not have the concept of "dev" and "master"
> > plugins
> > > as
> > > > > > well
> > > > > > > > like the core plugins. It was suggested we have tags, but
> this
> > is
> > > > > > > > problematic because we have multiple plugins in that one
> repo.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Carlos Santana
> > > > > > > <csantana23@gmail.com>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--047d7b339e07183e8b04ec059900--