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 purplecabbage, co-location=Adobe Vancouver
@purplecabbage risingj.com On Wed, Aug 7, 2013 at 9:06 AM, Ken Wallis <kwal...@blackberry.com> wrote: > 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 [shaz...@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 <bows...@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" <wjamesj...@gmail.com> wrote: > > > > > On Aug 7, 2013, at 9:19 AM, Ian Clelland <iclell...@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. >
