[RESULT] [VOTE] Accept Apache Callback for incubation
Hi, On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Thus I'm now calling a formal VOTE on the Apache Callback proposal [...] This vote is open for the next 72 hours. Everyone is welcome to participate, but only votes from the Incubator PMC members are binding. The vote passes with 28 +1s (19 binding) and no -1s, as recorded below: Binding (see http://people.apache.org/committers-by-project.html#incubator-pmc) +1 Alan D. Cabrera +1 Alex Karasulu +1 Ate Douma +1 Bertrand Delacretaz +1 Chris A Mattmann +1 Christian Grobmeier +1 Davanum Srinivas +1 Felix Meschberger +1 Gianugo Rabellino +1 Jean-Baptiste Onofré +1 Jim Jagielski +1 Jukka Zitting +1 Marcel Offermans +1 Matthias Wessendorf +1 Richard Hirsch +1 Ross Gardler +1 Sam Ruby +1 Stefan Seelmann +1 Tommaso Teofili Non-binding +1 Andrew Savory +1 Dave C. Johnson +1 Francis De Brabandere +1 Matthew B. Franklin +1 Maurizio Cucchiara +1 Raffaele P. Guidi +1 Raymond Feng +1 Scott Wilson +1 Thorsten Scherler Thanks, everyone, for voting! And welcome, Callback, to the Incubator! BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Callback for incubation
+1. Raymond Feng Sent from my iPhone On Oct 11, 2011, at 10:55 PM, Jean-Baptiste Onofré j...@nanthrax.net wrote: +1 (binding) Regards JB 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community
Re: [VOTE] Accept Apache Callback for incubation
+1 (non-binding) On 11 Oct 2011, at 22:09, 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Callback for incubation
On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Please VOTE: [ X] +1 Accept Apache Callback for incubation -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Callback for incubation
+1 On Wed, Oct 12, 2011 at 12:29 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.com wrote: Please VOTE: [ X] +1 Accept Apache Callback for incubation -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Best Regards, -- Alex
RE: [VOTE] Accept Apache Callback for incubation
+1 (non-binding). -Original Message- From: Jukka Zitting [mailto:jukka.zitt...@gmail.com] Sent: Tuesday, October 11, 2011 5:10 PM To: general Subject: [VOTE] Accept Apache Callback for incubation 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software
Re: [VOTE] Accept Apache Callback for incubation
Hi, On 11 October 2011 22:09, Jukka Zitting jukka.zitt...@gmail.com wrote: Please VOTE: [ ] +1 Accept Apache Callback for incubation [ ] -1 Don't accept Apache Callback for incubation because... +1 Andrew. -- asav...@apache.org / cont...@andrewsavory.com http://www.andrewsavory.com/
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) On Oct 11, 2011, at 5: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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Tommaso 2011/10/11 Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web
Re: [VOTE] Accept Apache Callback for incubation
+1 On 11 October 2011 22:09, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Regards Felix Am 11.10.2011 um 23:09 schrieb Jukka Zitting: 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development
[VOTE] Accept Apache Callback for incubation
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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web development binding them all. In terms of contribution, excluding Nitobi Software employees, the Callback project has 70 contributors. In terms of user adoption, precise
Re: [VOTE] Accept Apache Callback for incubation
+1 (non-binding) On Oct 11, 2011 11:10 PM, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread
Re: [VOTE] Accept Apache Callback for incubation
+1 Sent from my iPhone On Oct 11, 2011, at 5:09 PM, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Thanks Jukka! On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development
Re: [VOTE] Accept Apache Callback for incubation
+1 On Tue, Oct 11, 2011 at 2:15 PM, Christian Grobmeier grobme...@gmail.com wrote: +1 (binding) Thanks Jukka! On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast
Re: [VOTE] Accept Apache Callback for incubation
+1 (not binding) On Tue, Oct 11, 2011 at 11:09 PM, Jukka Zitting jukka.zitt...@gmail.comwrote: 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common
Re: [VOTE] Accept Apache Callback for incubation
+1 Sent from my mobile device, so please excuse typos and brevity. Maurizio Cucchiara
Re: [VOTE] Accept Apache Callback for incubation
+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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web development binding them all. In terms of contribution, excluding Nitobi Software employees, the Callback project has
Re: [VOTE] Accept Apache Callback for incubation
On Tue, Oct 11, 2011 at 2:09 PM, Jukka Zitting jukka.zitt...@gmail.com 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... +1 (binding) -- Gianugo Rabellino - gianugo at rabellino dot it Blog: http://boldlyopen.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Apache Callback for incubation
+1 On Oct 11, 2011 5:10 PM, Jukka Zitting jukka.zitt...@gmail.com 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web
Re: [VOTE] Accept Apache Callback for incubation
+1, binding, awesome guys, good luck! Cheers, Chris On Oct 11, 2011, at 2: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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Looks great D. On Wed, Oct 12, 2011 at 4:55 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: +1, binding, awesome guys, good luck! Cheers, Chris On Oct 11, 2011, at 2: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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community
Re: [VOTE] Accept Apache Callback for incubation
+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
Re: [VOTE] Accept Apache Callback for incubation
+1 Regards, Alan On Oct 11, 2011, at 2:09 PM, Jukka Zitting wrote: 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.
Re: [VOTE] Accept Apache Callback for incubation
+1 (binding) Regards JB 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 maintaining a codebase of that size. By relying on the platform browser, exposed by the platform SDK, we get a quick win to the browser and only have to focus on our bridge. This means the project requires developers with proficiency on each platform: collaboration is a natural side effect. Community - The community surrounding Callback is vast, diverse, distributed globally, and with all levels of proficiency in software development---the common thread of web development binding them all. In terms of contribution, excluding Nitobi Software employees