You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Filip Maj <fi...@adobe.com> on 2012/10/02 20:34:54 UTC
Pluginstall tool discussion
FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis has
made many improvements, including adding plugin removal. Mike has also
done a lot of work and fixed a variety of different issues. However, their
work is diverging, so we are going to discuss the differences between
their forks and set a plan on how to get their code bases merged. Also
will touch on the API for this tool. Feel free to join in the discussion!
I will report back notes to ML after.
Call in info
------------
Conference code:
5566718809
Access Numbers:
Toll-free dial-in number (U.S. and Canada):
(855) 870-5454
International dial-in number:
(408) 773-6768
Re: Pluginstall tool discussion
Posted by Dave Johnson <da...@gmail.com>.
https://docs.google.com/spreadsheet/ccc?key=0Al813Y70ZNWbdC0zRFduOEY2M0tjZWYxOVVUbmVFRGc
On Wed, Oct 10, 2012 at 2:38 AM, Andrew Lunny <al...@gmail.com> wrote:
> October 2012 17:00, Mike Reinstein <re...@gmail.com> wrote:
>
>> Hi Andrew,
>>
>> I agree on all points. Some additional feedback on a few specifics:
>>
>> > It looks like Mike has made a start on that with his
>> > cordova-pluginrepo repository
>>
>> Correct! Thanks for taking the time to look at it. I'm hoping to have a
>> working prototype by end of week.
>>
>> > The only way to find those problems is to try writing those plugins.
>>
>> Agreed, though I think inspecting existing plugins is a good start too.
>> Have you had a chance to look at my google docs spreadsheet on plugin work?
>> tab 1 is a grid of all plugins and their supported platforms, plus a few
>> bits of meta data. Tab 3 was my attempt to go through some of the more
>> "popular" plugins, analyizing their suitability for packaging via
>> pluginstall. Where it fell short I documented. Green means good to go
>> as-is, red means some issues, yellow means unsure (might be ok.) I'd love
>> some more feedback on this. the doc is globally shared so everyone can
>> modify it. I think we could use tab 3 to coordinate our work and provide
>> visibility. thoughts?
>>
>
> I didn't see the doc - can you post the link again?
>
>
>>
>> -Mike
>>
>>
>>
>>
>>
>> On Tue, Oct 9, 2012 at 7:44 PM, Andrew Lunny <al...@gmail.com> wrote:
>>
>>> I've missed most of this discussion, but I wanted to make a few quick
>>> points:
>>>
>>> * `pluginstall` (the tool I developed, that is used by PhoneGap Build) is
>>> a
>>> tool for installing plugins. Per the Unix philosophy, it doesn't and won't
>>> do anything other than that.
>>>
>>> * There may well be a need and a demand for a tool that grabs plugins from
>>> git repositories, uninstalls plugins, generates starter plugins, etc. But
>>> that's not pluginstall, and I think that tool should probably be named
>>> something else. It looks like Mike has made a start on that with his
>>> cordova-pluginrepo repository, which is awesome.
>>>
>>> * The problems that need to be solved by pluginstall are of the form "I
>>> can't install plugin x with pluginstall", or "I can't write a plugin that
>>> does x that can be installed by pluginstall." The only way to find those
>>> problems is to try writing those plugins. The PGB team is moving forward
>>> on
>>> a few, and we've worked with some other companies who have helped us see
>>> where pluginstall was lacking (adding multiple children to an Android
>>> intent-filter, installing a dylib into an iOS project).
>>>
>>> * node-xcode is a separate project, and will be useful for any plugin
>>> tools
>>> written with node. It would probably be better for everyone's sanity if
>>> there was a single version of that parser. I've been pretty slack about
>>> merging changes, so I'll get up to speed on that.
>>>
>>> * If other tools want to interoperate with pluginstall, they should follow
>>> the plugin spec here:
>>> https://github.com/alunny/cordova-plugin-spec
>>> That's a working document and is open to changes. Again, my preference is
>>> for changes of the form "I can't write a plugin that does X in this
>>> format"
>>> rather than "this element has a slightly misleading name; how about this
>>> name?". The GitHub issues for that repo is the best place to discuss
>>> changes to that spec.
>>>
>>> Cheers,
>>> Andrew
>>>
>>> On 6 October 2012 09:08, Mike Reinstein <re...@gmail.com> wrote:
>>>
>>> > Andrew's is the one used by pg build. Anis has changes from all of us
>>> and
>>> > has the most the up to date code:
>>> >
>>> > https://github.com/imhotep/pluginstall
>>> >
>>> > -Mike
>>> >
>>> >
>>> >
>>> > On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pm...@gmail.com>
>>> wrote:
>>> >
>>> > > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
>>> > >
>>> > > > Think its time we nominated a canonical repo for this. Fil's?
>>> > > >
>>> > >
>>> > > URL please? Are we talking about forks of pluginstall?
>>> > >
>>> > > --
>>> > > Patrick Mueller
>>> > > http://muellerware.org
>>> > >
>>> >
>>>
>>
>>
Re: Pluginstall tool discussion
Posted by Andrew Lunny <al...@gmail.com>.
October 2012 17:00, Mike Reinstein <re...@gmail.com> wrote:
> Hi Andrew,
>
> I agree on all points. Some additional feedback on a few specifics:
>
> > It looks like Mike has made a start on that with his
> > cordova-pluginrepo repository
>
> Correct! Thanks for taking the time to look at it. I'm hoping to have a
> working prototype by end of week.
>
> > The only way to find those problems is to try writing those plugins.
>
> Agreed, though I think inspecting existing plugins is a good start too.
> Have you had a chance to look at my google docs spreadsheet on plugin work?
> tab 1 is a grid of all plugins and their supported platforms, plus a few
> bits of meta data. Tab 3 was my attempt to go through some of the more
> "popular" plugins, analyizing their suitability for packaging via
> pluginstall. Where it fell short I documented. Green means good to go
> as-is, red means some issues, yellow means unsure (might be ok.) I'd love
> some more feedback on this. the doc is globally shared so everyone can
> modify it. I think we could use tab 3 to coordinate our work and provide
> visibility. thoughts?
>
I didn't see the doc - can you post the link again?
>
> -Mike
>
>
>
>
>
> On Tue, Oct 9, 2012 at 7:44 PM, Andrew Lunny <al...@gmail.com> wrote:
>
>> I've missed most of this discussion, but I wanted to make a few quick
>> points:
>>
>> * `pluginstall` (the tool I developed, that is used by PhoneGap Build) is
>> a
>> tool for installing plugins. Per the Unix philosophy, it doesn't and won't
>> do anything other than that.
>>
>> * There may well be a need and a demand for a tool that grabs plugins from
>> git repositories, uninstalls plugins, generates starter plugins, etc. But
>> that's not pluginstall, and I think that tool should probably be named
>> something else. It looks like Mike has made a start on that with his
>> cordova-pluginrepo repository, which is awesome.
>>
>> * The problems that need to be solved by pluginstall are of the form "I
>> can't install plugin x with pluginstall", or "I can't write a plugin that
>> does x that can be installed by pluginstall." The only way to find those
>> problems is to try writing those plugins. The PGB team is moving forward
>> on
>> a few, and we've worked with some other companies who have helped us see
>> where pluginstall was lacking (adding multiple children to an Android
>> intent-filter, installing a dylib into an iOS project).
>>
>> * node-xcode is a separate project, and will be useful for any plugin
>> tools
>> written with node. It would probably be better for everyone's sanity if
>> there was a single version of that parser. I've been pretty slack about
>> merging changes, so I'll get up to speed on that.
>>
>> * If other tools want to interoperate with pluginstall, they should follow
>> the plugin spec here:
>> https://github.com/alunny/cordova-plugin-spec
>> That's a working document and is open to changes. Again, my preference is
>> for changes of the form "I can't write a plugin that does X in this
>> format"
>> rather than "this element has a slightly misleading name; how about this
>> name?". The GitHub issues for that repo is the best place to discuss
>> changes to that spec.
>>
>> Cheers,
>> Andrew
>>
>> On 6 October 2012 09:08, Mike Reinstein <re...@gmail.com> wrote:
>>
>> > Andrew's is the one used by pg build. Anis has changes from all of us
>> and
>> > has the most the up to date code:
>> >
>> > https://github.com/imhotep/pluginstall
>> >
>> > -Mike
>> >
>> >
>> >
>> > On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pm...@gmail.com>
>> wrote:
>> >
>> > > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
>> > >
>> > > > Think its time we nominated a canonical repo for this. Fil's?
>> > > >
>> > >
>> > > URL please? Are we talking about forks of pluginstall?
>> > >
>> > > --
>> > > Patrick Mueller
>> > > http://muellerware.org
>> > >
>> >
>>
>
>
Re: Pluginstall tool discussion
Posted by Mike Reinstein <re...@gmail.com>.
Hi Andrew,
I agree on all points. Some additional feedback on a few specifics:
> It looks like Mike has made a start on that with his
> cordova-pluginrepo repository
Correct! Thanks for taking the time to look at it. I'm hoping to have a
working prototype by end of week.
> The only way to find those problems is to try writing those plugins.
Agreed, though I think inspecting existing plugins is a good start too.
Have you had a chance to look at my google docs spreadsheet on plugin work?
tab 1 is a grid of all plugins and their supported platforms, plus a few
bits of meta data. Tab 3 was my attempt to go through some of the more
"popular" plugins, analyizing their suitability for packaging via
pluginstall. Where it fell short I documented. Green means good to go
as-is, red means some issues, yellow means unsure (might be ok.) I'd love
some more feedback on this. the doc is globally shared so everyone can
modify it. I think we could use tab 3 to coordinate our work and provide
visibility. thoughts?
-Mike
On Tue, Oct 9, 2012 at 7:44 PM, Andrew Lunny <al...@gmail.com> wrote:
> I've missed most of this discussion, but I wanted to make a few quick
> points:
>
> * `pluginstall` (the tool I developed, that is used by PhoneGap Build) is a
> tool for installing plugins. Per the Unix philosophy, it doesn't and won't
> do anything other than that.
>
> * There may well be a need and a demand for a tool that grabs plugins from
> git repositories, uninstalls plugins, generates starter plugins, etc. But
> that's not pluginstall, and I think that tool should probably be named
> something else. It looks like Mike has made a start on that with his
> cordova-pluginrepo repository, which is awesome.
>
> * The problems that need to be solved by pluginstall are of the form "I
> can't install plugin x with pluginstall", or "I can't write a plugin that
> does x that can be installed by pluginstall." The only way to find those
> problems is to try writing those plugins. The PGB team is moving forward on
> a few, and we've worked with some other companies who have helped us see
> where pluginstall was lacking (adding multiple children to an Android
> intent-filter, installing a dylib into an iOS project).
>
> * node-xcode is a separate project, and will be useful for any plugin tools
> written with node. It would probably be better for everyone's sanity if
> there was a single version of that parser. I've been pretty slack about
> merging changes, so I'll get up to speed on that.
>
> * If other tools want to interoperate with pluginstall, they should follow
> the plugin spec here:
> https://github.com/alunny/cordova-plugin-spec
> That's a working document and is open to changes. Again, my preference is
> for changes of the form "I can't write a plugin that does X in this format"
> rather than "this element has a slightly misleading name; how about this
> name?". The GitHub issues for that repo is the best place to discuss
> changes to that spec.
>
> Cheers,
> Andrew
>
> On 6 October 2012 09:08, Mike Reinstein <re...@gmail.com> wrote:
>
> > Andrew's is the one used by pg build. Anis has changes from all of us and
> > has the most the up to date code:
> >
> > https://github.com/imhotep/pluginstall
> >
> > -Mike
> >
> >
> >
> > On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pm...@gmail.com>
> wrote:
> >
> > > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
> > >
> > > > Think its time we nominated a canonical repo for this. Fil's?
> > > >
> > >
> > > URL please? Are we talking about forks of pluginstall?
> > >
> > > --
> > > Patrick Mueller
> > > http://muellerware.org
> > >
> >
>
Re: Pluginstall tool discussion
Posted by Andrew Lunny <al...@gmail.com>.
I've missed most of this discussion, but I wanted to make a few quick
points:
* `pluginstall` (the tool I developed, that is used by PhoneGap Build) is a
tool for installing plugins. Per the Unix philosophy, it doesn't and won't
do anything other than that.
* There may well be a need and a demand for a tool that grabs plugins from
git repositories, uninstalls plugins, generates starter plugins, etc. But
that's not pluginstall, and I think that tool should probably be named
something else. It looks like Mike has made a start on that with his
cordova-pluginrepo repository, which is awesome.
* The problems that need to be solved by pluginstall are of the form "I
can't install plugin x with pluginstall", or "I can't write a plugin that
does x that can be installed by pluginstall." The only way to find those
problems is to try writing those plugins. The PGB team is moving forward on
a few, and we've worked with some other companies who have helped us see
where pluginstall was lacking (adding multiple children to an Android
intent-filter, installing a dylib into an iOS project).
* node-xcode is a separate project, and will be useful for any plugin tools
written with node. It would probably be better for everyone's sanity if
there was a single version of that parser. I've been pretty slack about
merging changes, so I'll get up to speed on that.
* If other tools want to interoperate with pluginstall, they should follow
the plugin spec here:
https://github.com/alunny/cordova-plugin-spec
That's a working document and is open to changes. Again, my preference is
for changes of the form "I can't write a plugin that does X in this format"
rather than "this element has a slightly misleading name; how about this
name?". The GitHub issues for that repo is the best place to discuss
changes to that spec.
Cheers,
Andrew
On 6 October 2012 09:08, Mike Reinstein <re...@gmail.com> wrote:
> Andrew's is the one used by pg build. Anis has changes from all of us and
> has the most the up to date code:
>
> https://github.com/imhotep/pluginstall
>
> -Mike
>
>
>
> On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pm...@gmail.com> wrote:
>
> > On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> > > Think its time we nominated a canonical repo for this. Fil's?
> > >
> >
> > URL please? Are we talking about forks of pluginstall?
> >
> > --
> > Patrick Mueller
> > http://muellerware.org
> >
>
Re: Pluginstall tool discussion
Posted by Mike Reinstein <re...@gmail.com>.
Andrew's is the one used by pg build. Anis has changes from all of us and
has the most the up to date code:
https://github.com/imhotep/pluginstall
-Mike
On Sat, Oct 6, 2012 at 8:08 AM, Patrick Mueller <pm...@gmail.com> wrote:
> On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
>
> > Think its time we nominated a canonical repo for this. Fil's?
> >
>
> URL please? Are we talking about forks of pluginstall?
>
> --
> Patrick Mueller
> http://muellerware.org
>
Re: Pluginstall tool discussion
Posted by Patrick Mueller <pm...@gmail.com>.
On Sat, Oct 6, 2012 at 5:22 AM, Brian LeRoux <b...@brian.io> wrote:
> Think its time we nominated a canonical repo for this. Fil's?
>
URL please? Are we talking about forks of pluginstall?
--
Patrick Mueller
http://muellerware.org
Re: Pluginstall tool discussion
Posted by Brian LeRoux <b...@brian.io>.
Think its time we nominated a canonical repo for this. Fil's?
On Fri, Oct 5, 2012 at 11:41 AM, Mike Reinstein
<re...@gmail.com> wrote:
> Thanks for scribing the meeting Fil. Here are some updates:
>
> Anis and I realized after the meeting that there were still some
> disagreement points. Our main disagreement was over the plugin.xml changes;
> I wanted to do them now, and Anis wanted to wait. After discussing with
> Fil, Anis, and myself, we decided to compromise by merging in all of my
> changes *except for* plugin namespacing, and plugin.xml/plugin directory
> changes. The reasoning being:
> a) we really need to work off the same basic codebase, which is beginning o
> diverge dramatically
> b) we'd like to get the pg build team to use our code as well, so pg build
> doesnt diverge from cordova cli efforts. Fil pointed out that not changing
> the plugin format at this point in time makes this much easier in the
> short term.
>
> We also re-iterated that the plugin changes are wanted improvements, and
> after succesfully merging, Fil will work with the build team to get buy-in.
> In the meantime I'll branch the code and add my plugin format changes there
> so when we're ready we can merge them into master.
>
> Fil, Anis, I just sent a pull request with all my changes (minus plugin
> formatting and namespacing) via github:
> https://github.com/imhotep/pluginstall/pull/1
> I'd really appreciate some feedback on this so we can get it merged. I dont
> want to create that branch containing the plugin changes until after the
> merge is complete.
>
> -Mike
>
> On Tue, Oct 2, 2012 at 6:34 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Recap of the meeting:
>>
>> - Mike's + Anis' forks of pluginstall to be merged
>> - the cli api will tend toward Mike's slightly more verbose interface
>> - also included in all of this are Mike's changes to the plugin.xml spec.
>> includes eliminating some verbosity and going the implicit route where
>> possible (I.e. Source code target location for java files, for example).
>> Renames to a few plugin.xml elements included (I.e. Config-change to
>> xml-graft)
>> - trying to formalize a good starting point for plugin authors, some kind
>> of skeleton to work off of. Cordova-echo plugin (per the docs) does seem
>> like a good starting point for this.
>>
>> On 10/2/12 12:05 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>>
>> >I'm thinking about screen casting as we walk through the changes. If it
>> >happens I'll email a link here so anyone thats interested can follow along
>> >visually with the code review/discussion.
>> >
>> >
>> >
>> >On Tue, Oct 2, 2012 at 2:48 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> Valuable info..
>> >>
>> >> 2PM PDT!
>> >>
>> >> On 10/2/12 11:42 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>> >>
>> >> >When?
>> >> >
>> >> >
>> >> >On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
>> >> >
>> >> >> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis
>> >>has
>> >> >> made many improvements, including adding plugin removal. Mike has
>> >>also
>> >> >> done a lot of work and fixed a variety of different issues. However,
>> >> >>their
>> >> >> work is diverging, so we are going to discuss the differences between
>> >> >> their forks and set a plan on how to get their code bases merged.
>> >>Also
>> >> >> will touch on the API for this tool. Feel free to join in the
>> >> >>discussion!
>> >> >> I will report back notes to ML after.
>> >> >>
>> >> >> Call in info
>> >> >> ------------
>> >> >>
>> >> >> Conference code:
>> >> >> 5566718809
>> >> >>
>> >> >> Access Numbers:
>> >> >>
>> >> >> Toll-free dial-in number (U.S. and Canada):
>> >> >>
>> >> >> (855) 870-5454
>> >> >>
>> >> >> International dial-in number:
>> >> >> (408) 773-6768
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
Re: Pluginstall tool discussion
Posted by Mike Reinstein <re...@gmail.com>.
Thanks for scribing the meeting Fil. Here are some updates:
Anis and I realized after the meeting that there were still some
disagreement points. Our main disagreement was over the plugin.xml changes;
I wanted to do them now, and Anis wanted to wait. After discussing with
Fil, Anis, and myself, we decided to compromise by merging in all of my
changes *except for* plugin namespacing, and plugin.xml/plugin directory
changes. The reasoning being:
a) we really need to work off the same basic codebase, which is beginning o
diverge dramatically
b) we'd like to get the pg build team to use our code as well, so pg build
doesnt diverge from cordova cli efforts. Fil pointed out that not changing
the plugin format at this point in time makes this much easier in the
short term.
We also re-iterated that the plugin changes are wanted improvements, and
after succesfully merging, Fil will work with the build team to get buy-in.
In the meantime I'll branch the code and add my plugin format changes there
so when we're ready we can merge them into master.
Fil, Anis, I just sent a pull request with all my changes (minus plugin
formatting and namespacing) via github:
https://github.com/imhotep/pluginstall/pull/1
I'd really appreciate some feedback on this so we can get it merged. I dont
want to create that branch containing the plugin changes until after the
merge is complete.
-Mike
On Tue, Oct 2, 2012 at 6:34 PM, Filip Maj <fi...@adobe.com> wrote:
> Recap of the meeting:
>
> - Mike's + Anis' forks of pluginstall to be merged
> - the cli api will tend toward Mike's slightly more verbose interface
> - also included in all of this are Mike's changes to the plugin.xml spec.
> includes eliminating some verbosity and going the implicit route where
> possible (I.e. Source code target location for java files, for example).
> Renames to a few plugin.xml elements included (I.e. Config-change to
> xml-graft)
> - trying to formalize a good starting point for plugin authors, some kind
> of skeleton to work off of. Cordova-echo plugin (per the docs) does seem
> like a good starting point for this.
>
> On 10/2/12 12:05 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>
> >I'm thinking about screen casting as we walk through the changes. If it
> >happens I'll email a link here so anyone thats interested can follow along
> >visually with the code review/discussion.
> >
> >
> >
> >On Tue, Oct 2, 2012 at 2:48 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> Valuable info..
> >>
> >> 2PM PDT!
> >>
> >> On 10/2/12 11:42 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >>
> >> >When?
> >> >
> >> >
> >> >On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
> >> >
> >> >> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis
> >>has
> >> >> made many improvements, including adding plugin removal. Mike has
> >>also
> >> >> done a lot of work and fixed a variety of different issues. However,
> >> >>their
> >> >> work is diverging, so we are going to discuss the differences between
> >> >> their forks and set a plan on how to get their code bases merged.
> >>Also
> >> >> will touch on the API for this tool. Feel free to join in the
> >> >>discussion!
> >> >> I will report back notes to ML after.
> >> >>
> >> >> Call in info
> >> >> ------------
> >> >>
> >> >> Conference code:
> >> >> 5566718809
> >> >>
> >> >> Access Numbers:
> >> >>
> >> >> Toll-free dial-in number (U.S. and Canada):
> >> >>
> >> >> (855) 870-5454
> >> >>
> >> >> International dial-in number:
> >> >> (408) 773-6768
> >> >>
> >> >>
> >>
> >>
>
>
Re: Pluginstall tool discussion
Posted by Filip Maj <fi...@adobe.com>.
Recap of the meeting:
- Mike's + Anis' forks of pluginstall to be merged
- the cli api will tend toward Mike's slightly more verbose interface
- also included in all of this are Mike's changes to the plugin.xml spec.
includes eliminating some verbosity and going the implicit route where
possible (I.e. Source code target location for java files, for example).
Renames to a few plugin.xml elements included (I.e. Config-change to
xml-graft)
- trying to formalize a good starting point for plugin authors, some kind
of skeleton to work off of. Cordova-echo plugin (per the docs) does seem
like a good starting point for this.
On 10/2/12 12:05 PM, "Mike Reinstein" <re...@gmail.com> wrote:
>I'm thinking about screen casting as we walk through the changes. If it
>happens I'll email a link here so anyone thats interested can follow along
>visually with the code review/discussion.
>
>
>
>On Tue, Oct 2, 2012 at 2:48 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> Valuable info..
>>
>> 2PM PDT!
>>
>> On 10/2/12 11:42 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>>
>> >When?
>> >
>> >
>> >On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
>> >
>> >> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis
>>has
>> >> made many improvements, including adding plugin removal. Mike has
>>also
>> >> done a lot of work and fixed a variety of different issues. However,
>> >>their
>> >> work is diverging, so we are going to discuss the differences between
>> >> their forks and set a plan on how to get their code bases merged.
>>Also
>> >> will touch on the API for this tool. Feel free to join in the
>> >>discussion!
>> >> I will report back notes to ML after.
>> >>
>> >> Call in info
>> >> ------------
>> >>
>> >> Conference code:
>> >> 5566718809
>> >>
>> >> Access Numbers:
>> >>
>> >> Toll-free dial-in number (U.S. and Canada):
>> >>
>> >> (855) 870-5454
>> >>
>> >> International dial-in number:
>> >> (408) 773-6768
>> >>
>> >>
>>
>>
Re: Pluginstall tool discussion
Posted by Mike Reinstein <re...@gmail.com>.
I'm thinking about screen casting as we walk through the changes. If it
happens I'll email a link here so anyone thats interested can follow along
visually with the code review/discussion.
On Tue, Oct 2, 2012 at 2:48 PM, Filip Maj <fi...@adobe.com> wrote:
> Valuable info..
>
> 2PM PDT!
>
> On 10/2/12 11:42 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
> >When?
> >
> >
> >On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
> >
> >> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis has
> >> made many improvements, including adding plugin removal. Mike has also
> >> done a lot of work and fixed a variety of different issues. However,
> >>their
> >> work is diverging, so we are going to discuss the differences between
> >> their forks and set a plan on how to get their code bases merged. Also
> >> will touch on the API for this tool. Feel free to join in the
> >>discussion!
> >> I will report back notes to ML after.
> >>
> >> Call in info
> >> ------------
> >>
> >> Conference code:
> >> 5566718809
> >>
> >> Access Numbers:
> >>
> >> Toll-free dial-in number (U.S. and Canada):
> >>
> >> (855) 870-5454
> >>
> >> International dial-in number:
> >> (408) 773-6768
> >>
> >>
>
>
Re: Pluginstall tool discussion
Posted by Filip Maj <fi...@adobe.com>.
Valuable info..
2PM PDT!
On 10/2/12 11:42 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>When?
>
>
>On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis has
>> made many improvements, including adding plugin removal. Mike has also
>> done a lot of work and fixed a variety of different issues. However,
>>their
>> work is diverging, so we are going to discuss the differences between
>> their forks and set a plan on how to get their code bases merged. Also
>> will touch on the API for this tool. Feel free to join in the
>>discussion!
>> I will report back notes to ML after.
>>
>> Call in info
>> ------------
>>
>> Conference code:
>> 5566718809
>>
>> Access Numbers:
>>
>> Toll-free dial-in number (U.S. and Canada):
>>
>> (855) 870-5454
>>
>> International dial-in number:
>> (408) 773-6768
>>
>>
Re: Pluginstall tool discussion
Posted by Michal Mocny <mm...@chromium.org>.
When?
On Tue, Oct 2, 2012 at 2:34 PM, Filip Maj <fi...@adobe.com> wrote:
> FYI, Mike, Anis and I will be discussing the pluginstall tool. Anis has
> made many improvements, including adding plugin removal. Mike has also
> done a lot of work and fixed a variety of different issues. However, their
> work is diverging, so we are going to discuss the differences between
> their forks and set a plan on how to get their code bases merged. Also
> will touch on the API for this tool. Feel free to join in the discussion!
> I will report back notes to ML after.
>
> Call in info
> ------------
>
> Conference code:
> 5566718809
>
> Access Numbers:
>
> Toll-free dial-in number (U.S. and Canada):
>
> (855) 870-5454
>
> International dial-in number:
> (408) 773-6768
>
>