[RESULT][VOTE] Accept Olingo proposal as an incubating project
Hi all, Thanks for voting. The VOTE is now closed and has passed with the following result. Binding +1 VOTES: Alan Cabrera Jean-Baptiste Onofré Niall Pemberton Dave Fisher Florian Müller Non-binding +1 VOTES: Dennis E. Hamilton I'll work with the initial committers to get the podling started. Thanks again, Florian Hi all, I'd like to call a VOTE for acceptance of Olingo into the Apache incubator. The proposal is pasted at the bottom on this email. The corresponding wiki page is: http://wiki.apache.org/incubator/OlingoProposal [ ] +1 Accept Olingo into the Apache incubator [ ] +0 Don't care. [ ] -1 Don't accept Olingo into the incubator because... +1 from me (binding) I'll close the VOTE next Sunday. Thanks, Florian = Apache Olingo Proposal = === Abstract === Apache Olingo is a generic Java language implementation of the OData 2.0 specification which will serve as a code base for the upcoming OASIS OData specification. === Proposal === The Open Data Protocol (OData) [1] is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores. The Apache Olingo is a library which enables developers to implement OData producers and OData consumers. Basic principles of the library are to provide an OData 2.0 specification compliant OData Library, enhancements shall be possible in a compatible manner, have a clear separation between Core and API, to provide an option to build extensions on top. This library should be base for implementing future releases of the specification. === Background === OData was originally developed by Microsoft and is released in a version 2.0 under an Open Specification Promise [2]. A lot of companies did show interests in this protocol, used it in products and gave feedback back to Microsoft. This joined effort resulted in a new release OData 3.0 in 2012, this version became the basis for the OASIS technical committee [3] which is currently working on a new version of the specification. This OASIS standard release is expected this year. The initial Java code of this project was developed by a development team that had already experience with other OData 2.0 and 3.0 implementations at SAP AG. The current code base implements OData 2.0 and because of this version is widely used it is a good starting point to build an open source community for the OData standard. The current code also comes up with an implementation of an OData sample service. On the one side this is an example for users which want to use the library to expose their own data and on the other side it illustrates how implemented features work. Additionally, the code base includes an extension which is called JPA processor. With this extension it is easy to expose any JPA persistence model via OData protocol without a lot of coding. === Rationale === More software vendors moving to OData means more choice for customers who will be able to use different implementations. For the standard to succeed, however, ensuring interoperability is paramount: in order to manage an ever growing context and leverage the enormous portability and interoperability issues that a globally adopted standard brings, it is necessary to think about how to make the related ecosystem healthy and sustainable. Successful modern standards are driven by: Clear documentation, built iteratively with continuous feedback from stakeholders A clearly defined compatibility process, enforced by tools that allow to gauge how implementations can be compatible and interoperable Accurate compliance criteria, documented in writing as well as in actual testing code that measure how tools and libraries are able to interoperate A sample implementation to clear up potential doubts and ensure that the standard can actually be implemented in real life scenarios The above mentioned pieces are able to make the development activity, towards an OData implementation, easier and more successful. Having an healthy ecosystem will ensure a smoother implementation process, more compliant products, and ultimately, a wider adoption of the standard. The OData ecosystem has been successful in creating and documenting early versions of the standard, yet it might potentially lack two very important aspects, that is a exhaustive implementation of the complete protocol that can be used productively and to ensure interoperability. As much as such artifacts can be developed independently by any OData proponent, the value of having a neutral party as a steward of actual code is to be considered. The Apache Software Foundation has been playing this kind of role for many years, and can provide the perfect environment to foster contributions on the OData
Re: Is an android framework good candidate for Apache Incubation?
Hi, On Mon, Jul 8, 2013 at 1:44 AM, yigong liu yigong.liu.apa...@gmail.com wrote: ...Is an android framework good candidate for Apache Incubation?... In general, any code that's developed in an open manner is welcome at Apache, it's more about whether you are able to build a community around your project. Approaching the incubator with an existing community (even a small one) and codebase (even far from finished), is much more likely to generate enthusiasm here. ... From incubation docs, i read advisors or champions will help bootstrapping candidate projects. Is there a list of champions who we can contact to see if they are interested?... That's mostly people on this list, so making people aware of your project, as you just did, is a good first step. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] OData Proposal for Incubator
Anny, Thanks for your feedback. Maybe you have recognized that Apache Olingo has passed the vote (Thanks all!!!) and starts now incubation. As soon as we have a mailing list I would like to encourage you to have this interesting discussion on our incubator mailing list. Regards, Stephan On 05.07.13 15:17, Anny G gvnan...@gmail.com wrote: Dear all, This is a very good initiative. We use OData in our integration projects as the standard protocol. Based on our experiences with OData as a standard and its exiting ecosystem, I have a few suggestions, 1. Please start by supporting OData v3 (not v2). v2 is relatively old, lacks some key features that are present in v3. Also, the ACCEPT header semantics for JSON format is compatible between v3 and v4 (the current in progress version) but not v2. This is critical from a consumer point of view. Another reason to start with v3 is that it is the version that was submitted to OASIS for standardizing which will come out very soon as v4. 2. Please evaluate odata4j which is designed very well despite some bugs and deficiencies. This allows this apache project to take the best of ideas from 2 of the available implementations of odata on java. Thanks Regards, Anny G -- View this message in context: http://apache-incubator-general.996316.n3.nabble.com/PROPOSAL-OData-Propos al-for-Incubator-tp35801p36019.html Sent from the Apache Incubator - General mailing list archive at Nabble.com. - 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: Is an android framework good candidate for Apache Incubation?
Hi Yigong, On Mon, Jul 8, 2013 at 1:44 AM, yigong liu yigong.liu.apa...@gmail.com wrote: Sorry for the repost. My last email is messed up. Is an android framework good candidate for Apache Incubation? I have been working on an Android framework(library, service and app) for connecting android devices (phones and tablets) in a peer-to-peer fashion and enable communications among them. Some use cases are media sharing and multi-player games. Devices can be connected over WiFi, WiFi Direct or mobile hotspot; and the connecting process can be initiated through multicast, NFC tap or using camera scanning QR code. The design doc can be found here: http://www.peerdevicenet.net/arch.html The source code can be found here: https://github.com/yigongliu/PeerDeviceNet_Src Some API user guide can be found here: http://www.peerdevicenet.net/api.html Is such android framework good candidate to submit for Apache? Skimming through the design doc I don't see anything that's Android specific. Is it your goal to provide a general framework for multiple mobile devices, with the android framework as first implementation? A framework that can then be used by others in their applications? Or do you want to keep it android only? Lieven From incubation docs, i read advisors or champions will help bootstrapping candidate projects. Is there a list of champions who we can contact to see if they are interested? Thanks Yigong - 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: [REPORT] Re: Shepherd assignments July 2013
On Sun, Jul 07, 2013 at 11:09:16AM -0700, Dave Fisher wrote: On Jul 2, 2013, at 7:23 AM, Marvin Humphrey wrote: Dave FisherStratos Still getting started. Very active lists. I noted a slight impatience with Infrastructure. Is it worth establishing a timeline or SLA with Infra to keep podling expectations aligned to reality? Perhaps not a formal timeline / SLA, but setting expectations would be good. OTOH, that podling was already told to be patient. ;-) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Is an android framework good candidate for Apache Incubation?
Hi Lieven, Thanks for the reply. Skimming through the design doc I don't see anything that's Android specific. Is it your goal to provide a general framework for multiple mobile devices, with the android framework as first implementation? A framework that can then be used by others in their applications? Or do you want to keep it android only? Yes, the design is general. Android is the place the idea is bootstrapped. Implementation in Win8 environment should be relatively straight forward; while in iOS, some work around may be necessary. With my current resource, i focused on Android implementation right now. Yes it is a framework/runtime exposing APIs to allow others write connected mobile apps (over multiple devices). It consists of three layers: device connection, group communication and remote activity startup. At my github site, there are some sample apps, such as Chat - for a group of peers to chat together, and a cube-rotation OpenGL app - for a group of peers to rotate a cube together. Also as testing case, on top of the runtime i developed a media sharing app for a group of devices to share media files (pic, video, word/pdf, web links, etc) among a group of devices, which is published at Google play (https://play.google.com/store/apps/details?id=com.xconns.free.peerdevicenet). Best regards Yigong - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [REPORT] Re: Shepherd assignments July 2013
On Mon, Jul 8, 2013 at 9:35 AM, Chip Childers chip.child...@sungard.com wrote: Perhaps not a formal timeline / SLA, but setting expectations would be good. This recently created wiki page may be helpful, if it has not already been passed along: https://wiki.apache.org/incubator/WhatToExpect Thanks to the primary creators, Alex Harui and Rob Vesse. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Canonical podling count
Greets, For our report, I'd like to supply an official count of podlings under incubation. Here's one way of doing it from the incubator svn checkout: grep . content/report_due_* | wc -l Any better ideas, or is that algo good enough? Would a podling_count.py make sense or do we already have something like that? For the purposes of the report, the important thing is to provide consistent numbers over time. Up-to-the-minute accuracy is less of a concern. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Write permission for wiki
Hi, can I please get write access to the wiki so I can help with the reports for ODF Toolkit? User is FlorianHopf. Thanks! Florian -- Florian Hopf Freelance Software Developer http://blog.florian-hopf.de - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Canonical podling count
Why not take it from the number Clutch reports? On Monday, July 8, 2013, Marvin Humphrey wrote: Greets, For our report, I'd like to supply an official count of podlings under incubation. Here's one way of doing it from the incubator svn checkout: grep . content/report_due_* | wc -l Any better ideas, or is that algo good enough? Would a podling_count.py make sense or do we already have something like that? For the purposes of the report, the important thing is to provide consistent numbers over time. Up-to-the-minute accuracy is less of a concern. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:;
Re: Write permission for wiki
On Mon, Jul 8, 2013 at 2:39 PM, Florian Hopf fh...@apache.org wrote: can I please get write access to the wiki so I can help with the reports for ODF Toolkit? User is FlorianHopf. Done. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Canonical podling count
On Mon, Jul 8, 2013 at 2:46 PM, Tim Williams william...@gmail.com wrote: Why not take it from the number Clutch reports? Ah, here, just above the table: http://incubator.apache.org/clutch.html#current Also in svn. http://svn.apache.org/repos/asf/incubator/public/trunk/content/clutcht.ent Thanks, Tim. (PS: the algo in my previous mail counts dupes, so no one should ever use it.) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Canonical podling count
Marvin Humphrey wrote: Tim Williams william...@gmail.com wrote: Why not take it from the number Clutch reports? Ah, here, just above the table: http://incubator.apache.org/clutch.html#current Also see http://incubator.apache.org/clutch.html#data which shows the clutch.txt list of current podlings. There is also the Incubator History chart: http://incubator.apache.org/history/ (However it has stopped working for me recently.) See the links from: http://incubator.apache.org/facilities.html -David Also in svn. http://svn.apache.org/repos/asf/incubator/public/trunk/content/clutcht.ent Thanks, Tim. (PS: the algo in my previous mail counts dupes, so no one should ever use it.) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
