cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Mocny <mmo...@chromium.org>
Subject Re: Post 3.0 release committer and community meeting
Date Fri, 09 Aug 2013 21:17:13 GMT
One original agenda item was "4.0 goals, timeline, and priorities", is that
still on the list?  Perhaps put that at the end, so that we will be
motivated to be concise for the rest of the meeting and have time to
brainstorm :)


On Fri, Aug 9, 2013 at 2:53 PM, Filip Maj <fil@adobe.com> wrote:

> Woot! Thanks to everyone for being accommodating with the timezones
> (Google Pizza party in Waterloo?)
>
> On 8/9/13 11:39 AM, "Andrew Grieve" <agrieve@chromium.org> wrote:
>
> >Okay, Looks like Wednesday Aug 14 @ 7:30pm EST / 4:30 PST works the best!
> >
> >We'll need one person from each co-location to have a webcam / microphone
> >in action, as well as a Google+ account. To prepare, please add my G+
> >account
> ><https://plus.sandbox.google.com/u/0/117659366035020803272/posts>to
> >one of your circles. I'll aim to start the hangout & invite you all 10
> >minutes beforehand.
> >
> >For those just watching, I'll post the youtube live-stream URL to this
> >thread & on #cordova IRC once we get it going on Wednesday.
> >
> >I think we should aim for between 90 and 120 minutes. We'll have to be
> >diligent to not waste too much time with hangout hats :P.
> >
> >Here's the agenda again (a bit tweaked again). Feel free to add.:
> >
> >- Introductions!
> >- Release artifacts and process redux
> >   - Release cadence & coupling of: platforms, cordova-js, plugins, tools,
> >docs
> >   - Versioning strategy for: platforms, cordova-js, plugins, tools, docs
> >       - Can we have our plugin API surface versioned separately from our
> >component versions?
> >       - Deprecation policy given versioning strategy
> >- plugman-registry
> >   - Status update
> >   - How does the registry fit into our release process
> >   - Goals around mixing & matching versions of things (e.g.
> >cordova-android 3.1 & cordova-ios 3.2)
> >- Shortterm plans for Medic
> >   - Buildbot?
> >   - Who wants to be involved?
> >   - Should mobile-spec autotests be pulled out?
> >- AppHarness
> >   - Demo of existing state
> >   - Release plans & future goals
> >- 4.0 goals, timeline, and priorities
> >   - Platforms as build artifacts - Is this our goal? what's
> >big hurdles remain?
> >   - Apps & Plugins to have the same feature set (dependencies, merges/,
> >etc)
> >
> >
> >Andrew
> >
> >On Wed, Aug 7, 2013 at 4:41 PM, Lorin Beer <lorin.beer.dev@gmail.com>
> >wrote:
> >
> >> agrieve, co-location=Google Waterloo
> >> mmocny, co-location=Google Waterloo
> >> maxw, co-location=Google Waterloo
> >> aharding, co-location=Adobe Vancouver
> >> filmaj, co-location=Adobe Vancouver
> >> stevegill, co-location=Adobe Vancouver
> >> bhiggins, co-location=BlackBerry Toronto
> >> jheifetz, co-location=BlackBerry Toronto
> >> devgeeks, co-location=n/a Melbourne, Australia
> >> aogilvie, co-location=n/a Tokyo, Japan.
> >> drkemp, co-location=Google Waterloo
> >> iclelland, co-location=Google Waterloo
> >> jamesjong, co-location=IBM Raleigh
> >> kwallis, co-location=n/a near-Toronto, Canada
> >> purplecabbage, co-location=Adobe Vancouver
> >> lucasholmquist, co-location=Red Hat, Upstate New York
> >> lorinbeer, co-location=Adobe San Francisco
> >>
> >>
> >> updated at Steve's request. Steve will be in Vancouver that week.
> >>
> >>
> >> On Wed, Aug 7, 2013 at 12:09 PM, Filip Maj <fil@adobe.com> wrote:
> >>
> >> > That's it for hangout participants, then.
> >> >
> >> > On 8/7/13 12:01 PM, "dgualdron@gmail.com" <dgualdron@gmail.com>
> wrote:
> >> >
> >> > >Dgualdron, co-location=n/a Bucaramanga, Colombia
> >> > >
> >> > >Sent from my BlackBerry® wireless device
> >> > >
> >> > >-----Original Message-----
> >> > >From: Ken Wallis <kwallis@blackberry.com>
> >> > >Date: Wed, 7 Aug 2013 16:06:25
> >> > >To: dev@cordova.apache.org<dev@cordova.apache.org>
> >> > >Reply-To: dev@cordova.apache.org
> >> > >Subject: RE: Post 3.0 release committer and community meeting
> >> > >
> >> > >Bringing the list to the top and adding myself:
> >> > >
> >> > >agrieve, co-location=Google Waterloo
> >> > >mmocny, co-location=Google Waterloo
> >> > >maxw, co-location=Google Waterloo
> >> > >aharding, co-location=Adobe Vancouver
> >> > >filmaj, co-location=Adobe Vancouver
> >> > >stevegill, co-location=Adobe San Francisco
> >> > >bhiggins, co-location=BlackBerry Toronto
> >> > >jheifetz, co-location=BlackBerry Toronto
> >> > >devgeeks, co-location=n/a Melbourne, Australia
> >> > >aogilvie, co-location=n/a Tokyo, Japan.
> >> > >drkemp, co-location=Google Waterloo
> >> > >iclelland, co-location=Google Waterloo
> >> > >jamesjong, co-location=IBM Raleigh
> >> > >kwallis, co-location=n/a near-Toronto, Canada
> >> > >
> >> > >--
> >> > >
> >> > >Ken Wallis
> >> > >
> >> > >Senior Product Manager ­ WebWorks
> >> > >
> >> > >BlackBerry
> >> > >
> >> > >650-620-2404
> >> > >
> >> > >________________________________________
> >> > >From: Shazron [shazron@gmail.com]
> >> > >Sent: Wednesday, August 07, 2013 11:17 AM
> >> > >To: dev@cordova.apache.org
> >> > >Subject: Re: Post 3.0 release committer and community meeting
> >> > >
> >> > >Ditto - will try to call in since it's at a sane 7:30 am here (audio
> >> only
> >> > >most like). The show must go on
> >> > >
> >> > >
> >> > >On Wed, Aug 7, 2013 at 11:02 PM, Joe Bowser <bowserj@gmail.com>
> >>wrote:
> >> > >
> >> > >> I can't make this meeting. I'm out of the office until the 16th.
> >> > >> On Aug 7, 2013 8:06 AM, "James Jong" <wjamesjong@gmail.com>
wrote:
> >> > >>
> >> > >> > On Aug 7, 2013, at 9:19 AM, Ian Clelland <iclelland@google.com>
> >> > wrote:
> >> > >> >
> >> > >> > >>
> >> > >> > >>> Attendees: If you plan to attend, could you
add your name to
> >> this
> >> > >> list
> >> > >> > >>> (inline so that the list grows) and say whether
you plan to
> >>be
> >> > >> > >> co-located:
> >> > >> > >>> agrieve, co-location=Google Waterloo
> >> > >> > >>> mmocny, co-location=Google Waterloo
> >> > >> > >>> maxw, co-location=Google Waterloo
> >> > >> > >>> aharding, co-location=Adobe Vancouver
> >> > >> > >>> filmaj, co-location=Adobe Vancouver
> >> > >> > >>> stevegill, co-location=Adobe San Francisco
> >> > >> > >>> bhiggins, co-location=BlackBerry Toronto
> >> > >> > >>> jheifetz, co-location=BlackBerry Toronto
> >> > >> > >>> devgeeks, co-location=n/a Melbourne, Australia
> >> > >> > >>> aogilvie, co-location=n/a Tokyo, Japan.
> >> > >> > >>> drkemp, co-location=Google Waterloo
> >> > >> > >>
> >> > >> > >> iclelland, co-location=Google Waterloo
> >> > >> > >> jamesjong, co-location=IBM Raleigh
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > >> Agenda (feel free to add items inline):
> >> > >> > >>
> >> > >> > >>> - Release artifacts and process redux
> >> > >> > >>> - Should platform releases still be coupled?
> >> > >> > >>> - Does semver make more sense to us now that
components are
> >>more
> >> > >> > >> decoupled?
> >> > >> > >>> - Deprecation policy improvements?
> >> > >> > >>> - Can we use cordova-registry to allow older
versions of
> >>things
> >> > >>when
> >> > >> > >> APIs are removed?
> >> > >> > >>> - Can we have our plugin API surface versioned
separately
> >>from
> >> our
> >> > >> > >> component versions?
> >> > >> > >>> - Shortterm plans for Medic
> >> > >> > >>> - Buildbot?
> >> > >> > >>> - Should mobile-spec autotests be pulled out?
> >> > >> > >>> - 4.0 goals, timeline, and priorities
> >> > >> > >>> - Platforms as build artifacts - Is this our
goal? what's
> >> > >> > >> big hurdles remain?
> >> > >> > >>> - Apps & Plugins to have the same feature
set (dependencies,
> >> > >>merges/,
> >> > >> > >> etc)
> >> > >> > >>
> >> > >> >
> >> > >> >
> >> > >>
> >> > >
> >> > >---------------------------------------------------------------------
> >> > >This transmission (including any attachments) may contain
> >>confidential
> >> > >information, privileged material (including material protected by the
> >> > >solicitor-client or other applicable privileges), or constitute
> >> > >non-public information. Any use of this information by anyone other
> >>than
> >> > >the intended recipient is prohibited. If you have received this
> >> > >transmission in error, please immediately reply to the sender and
> >>delete
> >> > >this information from your system. Use, dissemination, distribution,
> >>or
> >> > >reproduction of this transmission by unintended recipients is not
> >> > >authorized and may be unlawful.
> >> >
> >> >
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message