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: Interest in Apache beanshell incubation?
Hi Pedro, +1 that sounds really interesting - who doesn't know Beanshell, it's amazing! - I may could help on the proposal, but unfortunately I have too many stuff to manage this time to manage so I cannot be fully involved :( Looking forward to see more people interested before putting black on white! All the best, have anice day, Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Tue, Oct 11, 2011 at 10:34 PM, Pedro Giffuni p...@apache.org wrote: (Sorry for crossposting for this time, please redirect any response only to general@incubator) Hello; As some advocacy related to Apache OpenOffice.org, I asked the beanshell.org guys to adopt the Apache License 2. Not only did Patrick Niemeyer and Daniel Leuck agree to this, they were willing to transfer beanshell to the ASF. They are willing to sign a SGA, hand over a mirror of their SVN server and a dump of their CWiki. They are busy in their own projects though, so in general they would want to spend time in an incubation process themselves. http://www.beanshell.org/ I see there are several Apache projects (BSF, Camel, Script, AOOo) using Beanshell so I think this would be beneficial to the ASF. Perhaps someone already used to Apache ways, would like to take the lead in an incubation process? best regards, Pedro. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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 (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: Clutch blue-green background colour obscures entries
http://people.apache.org/~sebb/clutch.html#clutch OK to change that? This colour scheme was carefully chosen to assist with colour-blindness. I have been meaning to find the old discussion and development here about that, and add to Clutch notes. It used to have decent contrast for the links. Now the new bootsrap CSS has changed link colour to be a lighter blue. It has also changed the visited link colour to be the same (which is poor design). No, its not. I like it. Marking visited links with different colors is so 90ies. You see, it is in the eye of the observer. I started yesterday to develop some CSS to fix that for this table, but really it is an overall site issue. Now the visited links in the clutch table cannot be differed from the green background. I should mention that I have a color-weakness. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - 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) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Clutch blue-green background colour obscures entries
Finally the wonderful bootstrap css is destroyed: http://incubator.apache.org/guides/committer.html I do not agree to changing the colors of visited links. The headings now have a different line-height and look pretty ugly (see Mailing lists heading). Heading were bold before, and I think we should keep them bold. And looking at this page compared to: http://code.grobmeier.de/incubator-draft-v2/guides/committer.html Even the heading color should not be black. It gives everything a depressing look and feel. The clutchtable has a class called colortable, can we format this class instead of formatting the standard bootstrap classes? Can we change that again, please? Thanks, Christian On Wed, Oct 12, 2011 at 5:38 AM, David Crossley cross...@apache.org wrote: sebb wrote: David Crossley wrote: sebb wrote: Clutch uses a blue-green background colour for satisfactory entries. However, many entries include clickable blue links which are not very distinct from the background. I suggest changing the background to light green (#90EE90) which works much better for me. See the sample lines for Ace and Airavata at http://people.apache.org/~sebb/clutch.html#clutch OK to change that? This colour scheme was carefully chosen to assist with colour-blindness. I have been meaning to find the old discussion and development here about that, and add to Clutch notes. +1 There are now some notes and acknowledgement at the bottom. It used to have decent contrast for the links. Sorry, should have checked that out. I've already rebuilt the original site to check the strange header behaviour, and indeed the table used to display very well. Now the new bootsrap CSS has changed link colour to be a lighter blue. It has also changed the visited link colour to be the same (which is poor design). I started yesterday to develop some CSS to fix that for this table, but really it is an overall site issue. Indeed. Thanks for fixing that for the whole site. That is much better. There is also the issue of ul lists being coloured faint grey. That reduces readability. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
David, congratulations to the new release. Just a comment I cannot see the new release on the website: http://incubator.apache.org/deltacloud/ Should't it be updated together with the release? Then I think it is not very good to send the /dist folder link around, because to my knowledge it is bypassing the mirror system. Instead we usually use some kind of download page generator. At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. Cheers Christian On Tue, Oct 11, 2011 at 11:47 PM, David Lutterkort lut...@redhat.com wrote: I am pleased to announce the availability of Apache Deltacloud 0.4.1. Apache Deltacloud is a RESTful cloud abstraction API. The release consists both of the API server and a Ruby client. The release can be found at http://www.apache.org/dist/incubator/deltacloud/0.4.1/ Gems and RPM's for Fedora will become available shortly. Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: * change how dependencies are managed: canonical deps are now in the gemspecs Server: * clarify how user_data injection should work; make sure all drivers accept base64 encoded data and make the decoded version available to instance * fix URL generation so that server works when run behind a reverse proxy * init script: honor defaults from sysconfig file * init script: fix 'status', properly background deltacloudd * deltacloudd: support verbose option * Drivers: + Condor - use UUIDTools instead of UUID to simplify deps + Google - new driver for Google storage API + RHEV-M - treat status as case-insensitive - inject data through a virtual floppy rather than modifying the instance storage directly + vSphere - report minimum of max memory across all hosts in a data center, so that instances can be placed on any host - user_data is placed in file 'deltacloud-user-data.txt' Client: * fix parsing of enums in HWP properties * fix handling of float value for number of vCPU in HWP David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Interest in Apache beanshell incubation?
Wow, many cool stuff coming to apache recently. Hopefully there are some mentors out there. I have hands full with open source work already. Cheers Christian On Tue, Oct 11, 2011 at 10:34 PM, Pedro Giffuni p...@apache.org wrote: (Sorry for crossposting for this time, please redirect any response only to general@incubator) Hello; As some advocacy related to Apache OpenOffice.org, I asked the beanshell.org guys to adopt the Apache License 2. Not only did Patrick Niemeyer and Daniel Leuck agree to this, they were willing to transfer beanshell to the ASF. They are willing to sign a SGA, hand over a mirror of their SVN server and a dump of their CWiki. They are busy in their own projects though, so in general they would want to spend time in an incubation process themselves. http://www.beanshell.org/ I see there are several Apache projects (BSF, Camel, Script, AOOo) using Beanshell so I think this would be beneficial to the ASF. Perhaps someone already used to Apache ways, would like to take the lead in an incubation process? best regards, Pedro. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - 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: Clutch blue-green background colour obscures entries
On 12 October 2011 10:04, Christian Grobmeier grobme...@gmail.com wrote: Finally the wonderful bootstrap css is destroyed: http://incubator.apache.org/guides/committer.html I do not agree to changing the colors of visited links. The headings now have a different line-height and look pretty ugly (see Mailing lists heading). Sorry, I don't see the line-height issue. I don't mind too much about the visited links being a different colour. Heading were bold before, and I think we should keep them bold. I was not aware I had changed the font weight. And looking at this page compared to: http://code.grobmeier.de/incubator-draft-v2/guides/committer.html Even the heading color should not be black. It gives everything a depressing look and feel. I find black more legible, and having headings the same colour as links is very confusing. The clutchtable has a class called colortable, can we format this class instead of formatting the standard bootstrap classes? Can we change that again, please? Perhaps the earlier suggestion of creating a branch to test out the new formatting would now be useful. If this is stored on p.a.o in a personal directory, we can try different settings very quickly. Thanks, Christian On Wed, Oct 12, 2011 at 5:38 AM, David Crossley cross...@apache.org wrote: sebb wrote: David Crossley wrote: sebb wrote: Clutch uses a blue-green background colour for satisfactory entries. However, many entries include clickable blue links which are not very distinct from the background. I suggest changing the background to light green (#90EE90) which works much better for me. See the sample lines for Ace and Airavata at http://people.apache.org/~sebb/clutch.html#clutch OK to change that? This colour scheme was carefully chosen to assist with colour-blindness. I have been meaning to find the old discussion and development here about that, and add to Clutch notes. +1 There are now some notes and acknowledgement at the bottom. It used to have decent contrast for the links. Sorry, should have checked that out. I've already rebuilt the original site to check the strange header behaviour, and indeed the table used to display very well. Now the new bootsrap CSS has changed link colour to be a lighter blue. It has also changed the visited link colour to be the same (which is poor design). I started yesterday to develop some CSS to fix that for this table, but really it is an overall site issue. Indeed. Thanks for fixing that for the whole site. That is much better. There is also the issue of ul lists being coloured faint grey. That reduces readability. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Clutch blue-green background colour obscures entries
Will respond to rest later Can we change that again, please? Perhaps the earlier suggestion of creating a branch to test out the new formatting would now be useful. +1 If this is stored on p.a.o in a personal directory, we can try different settings very quickly. +1 Cheers Thanks, Christian On Wed, Oct 12, 2011 at 5:38 AM, David Crossley cross...@apache.org wrote: sebb wrote: David Crossley wrote: sebb wrote: Clutch uses a blue-green background colour for satisfactory entries. However, many entries include clickable blue links which are not very distinct from the background. I suggest changing the background to light green (#90EE90) which works much better for me. See the sample lines for Ace and Airavata at http://people.apache.org/~sebb/clutch.html#clutch OK to change that? This colour scheme was carefully chosen to assist with colour-blindness. I have been meaning to find the old discussion and development here about that, and add to Clutch notes. +1 There are now some notes and acknowledgement at the bottom. It used to have decent contrast for the links. Sorry, should have checked that out. I've already rebuilt the original site to check the strange header behaviour, and indeed the table used to display very well. Now the new bootsrap CSS has changed link colour to be a lighter blue. It has also changed the visited link colour to be the same (which is poor design). I started yesterday to develop some CSS to fix that for this table, but really it is an overall site issue. Indeed. Thanks for fixing that for the whole site. That is much better. There is also the issue of ul lists being coloured faint grey. That reduces readability. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - 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 (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: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
Hi Christian, thanks for your comments - you're right, the website is pretty under-updated recently. We've finished a tidying up of the website content - clearer download/setup instructions, more info for developers etc but have been holding off on deploying the updated site content specifically waiting for release 4.0.1. Mainly because the updated site documents the 'easy' installation of deltacloud using rubygems (i.e. gem install deltacloud-core) - and this only works because of the updated .gemfile dependencies in release 4.0.1. (basically, the gemfile outlines all 'runtime' gems - especially the ones that deltacloud uses to talk to the cloud providers like aws). I just checked rubygems.org and we haven't yet pushed the updated deltacloud-core gem (4.0.1); this should happen in the next few hours/day. Once that is done I will also deploy the updated site content. One the new gem is pushed to rubygems.org, you'll be able to get the latest release by: gem install deltacloud-core For now, you can get the release at the www.apache.org/dist/incubator/deltacloud/0.4.1/ - I take your point about the mirroring system. If you have the time/interest, you can use the git mirror to get the sources+build the latest: mkdir DeltacloudProject; cd DeltacloudProject git clone git://git.apache.org/deltacloud.git cd ./deltacloud/server rake package sudo gem install ./pkg/deltacloud-core-0.4.1.gem We also have a github page which mirrors the apache repo at https://github.com/apache/deltacloud if you prefer github. As I say, the 4.0.1 will be deployed to rubygems very soon - once that happens 'gem install deltacloud-core' will give you the latest release and all its dependencies, all the best, marios On 12/10/11 12:13, Christian Grobmeier wrote: David, congratulations to the new release. Just a comment I cannot see the new release on the website: http://incubator.apache.org/deltacloud/ Should't it be updated together with the release? Then I think it is not very good to send the /dist folder link around, because to my knowledge it is bypassing the mirror system. Instead we usually use some kind of download page generator. At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. Cheers Christian On Tue, Oct 11, 2011 at 11:47 PM, David Lutterkort lut...@redhat.com wrote: I am pleased to announce the availability of Apache Deltacloud 0.4.1. Apache Deltacloud is a RESTful cloud abstraction API. The release consists both of the API server and a Ruby client. The release can be found at http://www.apache.org/dist/incubator/deltacloud/0.4.1/ Gems and RPM's for Fedora will become available shortly. Many thanks to all those who contributed patches, reported bugs, and asked for features. It's great to see that the list of committers and patch contributors is steadily increasing. Overview of the changes for this release: * change how dependencies are managed: canonical deps are now in the gemspecs Server: * clarify how user_data injection should work; make sure all drivers accept base64 encoded data and make the decoded version available to instance * fix URL generation so that server works when run behind a reverse proxy * init script: honor defaults from sysconfig file * init script: fix 'status', properly background deltacloudd * deltacloudd: support verbose option * Drivers: + Condor - use UUIDTools instead of UUID to simplify deps + Google - new driver for Google storage API + RHEV-M - treat status as case-insensitive - inject data through a virtual floppy rather than modifying the instance storage directly + vSphere - report minimum of max memory across all hosts in a data center, so that instances can be placed on any host - user_data is placed in file 'deltacloud-user-data.txt' Client: * fix parsing of enums in HWP properties * fix handling of float value for number of vCPU in HWP David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[SITE] Samples of site with different CSS settings
I've uploaded the current site to my pao directory: http://people.apache.org/~sebb/incubator/ This was created using a reworked site.vsl that creates relative links where possible, so the LH menu should work OK the directories are: current - as for existing CSS files bootstrap - css files as per original commit of bootstrap I can easily create other samples with different CSS files for comparison. [Note - I dropped the audit and altRMI folders and some other stuff to make the site smaller] - 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
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
[VOTE] Release Droids 0.1-incubating RC4
Please vote on the release candidate for Apache Droids Incubating, version 0.1-incubating. I've received two binding IPMC +1 votes and 4 non-binding +1 votes. The blockers identified by Marvin and sebb should be fixed in this release. I need one more binding IPMC +1 vote. PPMC release vote thread: http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201109.mbox/%3c4e84e1b9.2050...@apache.org%3E Source files: https://repository.apache.org/content/repositories/orgapachedroids-075/org/apache/droids/droids/0.1.0-incubating/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachedroids-075/ SVN source tag (r1172386): https://svn.apache.org/repos/asf/incubator/droids/tags/0.1.0-incubating/ PGP release keys (signed using 3698A2B1): https://svn.apache.org/repos/asf/incubator/droids/KEYS [ ] +1 [ ] +0 [ ] -1 Thanks, Richard - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [SITE] Samples of site with different CSS settings
On 12 October 2011 13:46, sebb seb...@gmail.com wrote: I've uploaded the current site to my pao directory: http://people.apache.org/~sebb/incubator/ This was created using a reworked site.vsl that creates relative links where possible, so the LH menu should work OK the directories are: current - as for existing CSS files bootstrap - css files as per original commit of bootstrap I can easily create other samples with different CSS files for comparison. [Note - I dropped the audit and altRMI folders and some other stuff to make the site smaller] I just changed the About the Apache Incubator header on the first page to use h2 id=xxx instead of a name=xxx. This was the alternative fix I discussed previously. It would mean just about every page would change. But if combined with moving to relative hrefs that would reduce the SVN commit noise. S/// - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Format of email
On 12 October 2011 16:50, Daniel Shahaf d...@daniel.shahaf.name wrote: sebb wrote on Wed, Oct 12, 2011 at 16:36:27 +0100: On 12 October 2011 16:23, Daniel Shahaf d...@daniel.shahaf.name wrote: sebb wrote on Tue, Oct 11, 2011 at 18:24:19 +0100: On 11 October 2011 18:21, Daniel Shahaf d...@daniel.shahaf.name wrote: It's the ezmlm -x/-X flag. I don't know how to determine it without shell access to apmail. Could query@pulse be updated to return this information? pulse runs on pulse.a.o, not hermes.a.o. How would you transfer the information from hermes to pulse? No idea, but then I don't know how it currently obtains the information it does return. Would it be possible to install some kind of agent on hermes which accepted specific requests from pulse? It's technically feasible to extract the information from hermes:~apmail into some other place. Why should we do that? Do what? install an agent? or extract the info? If it can be done, why not do it for Larry? - 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 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: Format of email
Wrong list sebb wrote on Wed, Oct 12, 2011 at 17:03:01 +0100: On 12 October 2011 16:50, Daniel Shahaf d...@daniel.shahaf.name wrote: sebb wrote on Wed, Oct 12, 2011 at 16:36:27 +0100: On 12 October 2011 16:23, Daniel Shahaf d...@daniel.shahaf.name wrote: sebb wrote on Tue, Oct 11, 2011 at 18:24:19 +0100: On 11 October 2011 18:21, Daniel Shahaf d...@daniel.shahaf.name wrote: It's the ezmlm -x/-X flag. I don't know how to determine it without shell access to apmail. Could query@pulse be updated to return this information? pulse runs on pulse.a.o, not hermes.a.o. How would you transfer the information from hermes to pulse? No idea, but then I don't know how it currently obtains the information it does return. Would it be possible to install some kind of agent on hermes which accepted specific requests from pulse? It's technically feasible to extract the information from hermes:~apmail into some other place. Why should we do that? Do what? install an agent? or extract the info? If it can be done, why not do it for Larry? - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On Wed, 2011-10-12 at 11:13 +0200, Christian Grobmeier wrote: David, congratulations to the new release. Just a comment I cannot see the new release on the website: http://incubator.apache.org/deltacloud/ Should't it be updated together with the release? Yes, this was a case of the mail servers being way faster than the mirroring scripts. It's there now. Then I think it is not very good to send the /dist folder link around, because to my knowledge it is bypassing the mirror system. Instead we usually use some kind of download page generator. Sorry, that was an oversight on my part. I'll replace the links with http://www.apache.org/dyn/closer.cgi/incubator/deltacloud/ in the future. At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
David, At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? Ah, very small, now I see it :-) But: You can get the source code: git clone git://git.fedorahosted.org/deltacloud/libdeltacloud.git Slowly I begin to understand this is a non-apache package, correct? otherwise I would expect the link to an ASF git mirror instead Cheers David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On Wed, 2011-10-12 at 18:42 +0200, Christian Grobmeier wrote: David, At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? Ah, very small, now I see it :-) But: You can get the source code: git clone git://git.fedorahosted.org/deltacloud/libdeltacloud.git Slowly I begin to understand this is a non-apache package, correct? otherwise I would expect the link to an ASF git mirror instead Yeah, I think we need to tweak the stylesheet. The 'Additional Tools' header doesn't stand out enough, and doesn't make it clear that this is additional stuff, only related to, and not part of, the Apache project. David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Apache Deltacloud 0.4.1 (incubating)
On 12 October 2011 17:39, David Lutterkort lut...@redhat.com wrote: On Wed, 2011-10-12 at 11:13 +0200, Christian Grobmeier wrote: David, congratulations to the new release. Just a comment I cannot see the new release on the website: http://incubator.apache.org/deltacloud/ Should't it be updated together with the release? Yes, this was a case of the mail servers being way faster than the mirroring scripts. It's there now. It's normally best to wait 24 hours or so after posting files to allow mirrors to catch up. Then I think it is not very good to send the /dist folder link around, because to my knowledge it is bypassing the mirror system. Instead we usually use some kind of download page generator. Sorry, that was an oversight on my part. I'll replace the links with http://www.apache.org/dyn/closer.cgi/incubator/deltacloud/ in the future. At your website: http://incubator.apache.org/deltacloud/download.html I read nothing of how to get the release. Instead I am send to fedorahost for the code. The very first link (Official releases can be downloaded from the Apache website) on that page goes to http://www.apache.org/dist/incubator/deltacloud/ Do you see a different version of the page ? David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Interest in Apache beanshell incubation?
On 11 October 2011 21:34, Pedro Giffuni p...@apache.org wrote: (Sorry for crossposting for this time, please redirect any response only to general@incubator) Hello; As some advocacy related to Apache OpenOffice.org, I asked the beanshell.org guys to adopt the Apache License 2. Not only did Patrick Niemeyer and Daniel Leuck agree to this, they were willing to transfer beanshell to the ASF. They are willing to sign a SGA, hand over a mirror of their SVN server and a dump of their CWiki. They are busy in their own projects though, so in general they would want to spend time in an incubation process themselves. http://www.beanshell.org/ I see there are several Apache projects (BSF, Camel, Script, AOOo) using Beanshell so I think this would be beneficial to the ASF. Also JMeter. It would be great to have BeanShell as an ASF project. Perhaps someone already used to Apache ways, would like to take the lead in an incubation process? I'd certainly be interested in helping as a committer, and could act as a Mentor. best regards, Pedro. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - 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) 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---the
Re: Interest in Apache beanshell incubation?
I think the maven-invoker-plugin also uses Beanshell for scripting the verification. LieGrue, strub - Original Message - From: sebb seb...@gmail.com To: general@incubator.apache.org Cc: Sent: Wednesday, October 12, 2011 10:14 PM Subject: Re: Interest in Apache beanshell incubation? On 11 October 2011 21:34, Pedro Giffuni p...@apache.org wrote: (Sorry for crossposting for this time, please redirect any response only to general@incubator) Hello; As some advocacy related to Apache OpenOffice.org, I asked the beanshell.org guys to adopt the Apache License 2. Not only did Patrick Niemeyer and Daniel Leuck agree to this, they were willing to transfer beanshell to the ASF. They are willing to sign a SGA, hand over a mirror of their SVN server and a dump of their CWiki. They are busy in their own projects though, so in general they would want to spend time in an incubation process themselves. http://www.beanshell.org/ I see there are several Apache projects (BSF, Camel, Script, AOOo) using Beanshell so I think this would be beneficial to the ASF. Also JMeter. It would be great to have BeanShell as an ASF project. Perhaps someone already used to Apache ways, would like to take the lead in an incubation process? I'd certainly be interested in helping as a committer, and could act as a Mentor. best regards, Pedro. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [SITE] Samples of site with different CSS settings
sebb wrote: I've uploaded the current site to my pao directory: http://people.apache.org/~sebb/incubator/ This was created using a reworked site.vsl that creates relative links where possible, so the LH menu should work OK the directories are: current - as for existing CSS files bootstrap - css files as per original commit of bootstrap I can easily create other samples with different CSS files for comparison. Thanks for your efforts. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[DISCUSS] Graduation of Deltacloud to TLP
Hi all, the Deltacloud community and mentors feel that we are ready to graduate to a toplevel Apache project. A while ago, we held a vote on the deltacloud-dev mailing list[1] about graduation, with 8 +1 votes (2 from mentors) and no 0 or -1 votes[2]. Since we started incubation, we've made 4 releases and added 3 new contributors[3] We would like to move the process of graduation forward; to that end, I would like feedback on the draft resolution (included below) and, assuming the discussion doesn't turn up any absolute blockers, call for a vote for the IPMC on this list on 2011-10-17. cheers, David [1] http://mail-archives.apache.org/mod_mbox/incubator-deltacloud-dev/201108.mbox/%3c1313190921.5165.4.ca...@avon.watzmann.net%3E [2] http://mail-archives.apache.org/mod_mbox/incubator-deltacloud-dev/201109.mbox/%3c1316040219.17880.34.ca...@avon.watzmann.net%3E [3] http://incubator.apache.org/projects/deltacloud.html Draft resolution: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software implementing web service API's for interacting with cloud providers, and corresponding client libraries, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Deltacloud Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Deltacloud Project be and hereby is responsible for the creation and maintenance of software related to web service API's for interacting with cloud providers, and corresponding client libraries; and be it further RESOLVED, that the office of Vice President, Deltacloud be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Deltacloud Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Deltacloud Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Deltacloud Project: * Marios Andreou (mar...@apache.org) * Michal Fojtik (mfoj...@apache.org) * Jim Jagielski (j...@apache.org) * Chris Lalancette (clala...@apache.org) * David Lutterkort (lut...@apache.org) * Sang-Min Park (sp...@apache.org) * Eric Woods (wood...@apache.org) NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Lutterkort be appointed to the office of Vice President, Deltacloud, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Deltacloud Project; and be it further RESOLVED, that the initial Apache Deltacloud Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Deltacloud podling; and be it further RESOLVED, that all responsibility pertaining to the Apache Incubator Deltacloud podling encumbered upon the Apache Incubator PMC are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[SITE] navigation
The Incubator website has many documentation pages and sections. It is especially important for incoming projects to be able to easily navigate our documentation quagmire. Of course also important for Mentors. Some other aspects of our site navigation are already being addressed. Thanks. Another aspect that needs attention is the recent changes to link colours, which have removed the ability to know where one has been. It is important to be able to know which parts of the documentation have already been visited. If we need to change from the default blue, then so be it. However, the visited colour needs to be a *different* colour, not the same as a not-yet-visited link. References: [1] The Site map http://incubator.apache.org/sitemap.html [2] Incubation Policy http://incubator.apache.org/incubation/Incubation_Policy.html [3] Incubation Guides http://incubator.apache.org/guides/ [3] Assist with Incubation Steps http://incubator.apache.org/clutch.html#steps -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
