+1 On Wednesday, October 12, 2011, Ate Douma <a...@douma.nu> wrote: > +1 > > On 10/11/2011 11:09 PM, Jukka Zitting wrote: > > Hi, > > As discussed, the PhoneGap project would like to enter the Incubator > under the Apache Callback name (potential alternative names to be > discussed during incubation). The initial proposal has been well > received and there are no major open issues, so it's time to vote! > > Thus I'm now calling a formal VOTE on the Apache Callback proposal as > included below. The proposal is also available at > http://wiki.phonegap.com/w/page/46311152/apache-callback-proposal on > the PhoneGap wiki, and I'll place a copy for our archives on the > Incubator wiki as soon as it stops giving me internal server errors. > > Please VOTE: > > [ ] +1 Accept Apache Callback for incubation > [ ] -1 Don't accept Apache Callback for incubation because... > > This vote is open for the next 72 hours. Everyone is welcome to > participate, but only votes from the Incubator PMC members are > binding. > > Thanks! My vote is +1. > > Best regards, > > Jukka Zitting > > ---- > > Apache Callback Proposal > ======================== > > Abstract > -------- > > Apache Callback is a platform for building native mobile applications > using HTML, CSS and JavaScript. > > Proposal > -------- > > Apache Callback allows web developers to natively target Apple iOS, Google > Android, RIM BlackBerry, Microsoft Windows Phone 7, HP webOS, Nokia Symbian > and Samsung Bada with a single codebase. The Callback APIs are based on > open web standards. The Callback bridge technology enables access to native > device capabilities. Utilizing the Callback bridge native plugins allow > for any type of native access from the embedded webview. > > Background > ---------- > > Apache Callback is the free software evolution of the popular PhoneGap > project. > > PhoneGap evolved from a hack that enabled a FFI (Foreign Function Interface) > to an embedded WebView on iOS to a complete suite of tools for tackling > parity across many mobile device and desktop platforms. > > PhoneGap has always focused on two complementary goals. Our first goal, > is to see the web as a first class development platform. Not a sandbox > without a filesystem but a real first class platform that includes access > to the local system apis, sensors and data, in addition to first class > tooling such as system debuggers. The second goal of PhoneGap is for > the project to cease to exist. This is not a nihilistic sentiment, rather > we at the PhoneGap project are providing a reference implementation for > web browsers to assist and guide the standardization process of browser APIs. > > The name and trademark of PhoneGap will become the commercial entity for > the project. The source, code, documentation and related assets will all > be contributed to the Apache Foundation as Callback. > > The Callback name comes from the event of the same name that is fired > when the FFI bridge is established. > > Rationale > --------- > > The dominate window to the web is quickly becoming devices, mostly phones. > The manufacturers of devices, creators of mobile operating systems, and > authors of web browsers are consolidating. (In many cases these are all > already the same company.) Those stakeholders may see a future for the > web but their bottom line is not necessarily motivated to participate in > an open web. It is especially clear that while many of these platforms > have been seeing some level of strategic neglect in favor of enhanced > experiences at the price locking developers into their respective > platforms. The Callback project exists to bring the focus back to an > open and accessible web. > > Initial Goals > ------------- > > * License all PhoneGap source code and documentation to the Apache > Software Foundation. (We already name the Apache license in our CLA.) > * Setup and standardize the open governance of the Callback project. > * Rename all assets from PhoneGap to Callback in project src, docs, > tests and related infrastructure. > > Current Status > -------------- > > Callback is a mature software project recently shipping 1.0 on July 29, 2011. > > Meritocracy > ----------- > > Callback has always been a project driven by merit and, in a sense, our > solution is brute force requiring many collaborating developers to > solve our goals. > > It would be far easier, and perhaps more "correct", for the Callback > project to port a single web browser codebase, and API bindings, across > platforms but our executable size would be appreciably larger, unacceptably > so for mobile, and our target abstraction would be only tertiary to > m
-- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
