I'm not asking us to exclude [email protected], just asking to include a larger community. As far as I can tell there's less than 20 members on this mailing list and most of us work for Microsoft or SAP so it's not a good place to get feedback on something as visible as the name of the library. By contrast odata.org had 61,000 unique visitors in June. We certainly won't get responses from that many people, but I'd hope we can get a voting result that includes more than six votes from two companies. That's not a very representative sample.
-----Original Message----- From: Kobler-Morris, Sven [mailto:[email protected]] Sent: Thursday, July 24, 2014 4:02 PM To: [email protected] Subject: RE: Java Script library Name voting result Hello Mark, think it is best if discussion took place on [email protected], otherwise we have so sync the discussion between mailing list/blog/forum On http://olingo.apache.org/support.html is information of how to join [email protected]. Any interested developer can join. Regards, Sven -----Original Message----- From: Mark Stafford [mailto:[email protected]] Sent: Donnerstag, 24. Juli 2014 09:56 To: [email protected] Subject: RE: Java Script library Name voting result Thanks Sven! Ideally we should consider getting input from the larger OData community. The current Olingo community is mostly composed of members of the TC, which I think biases the discussion somewhat. Is there a way to extend the call for input to the full OData community? Maybe we could put a blog post up on OData.org and send a mail to the main OData DL? -----Original Message----- From: Kobler-Morris, Sven [mailto:[email protected]] Sent: Thursday, July 24, 2014 3:30 PM To: [email protected] Subject: RE: Java Script library Name voting result Hi all, this seems to be a valid point. So I cancelled the vote and we can do further discussions on this. >From my current point of view ODataJS makes also sense as a name because it is >more releated to "OData" then "Olingo" and will show better up in Search >results ( as Yi mentioned). So please free discuss this here. There will be a new Vote on this after the discussion. regards, Sven -----Original Message----- From: Yi Ding [mailto:[email protected]] Sent: Donnerstag, 24. Juli 2014 08:20 To: [email protected] Subject: RE: Java Script library Name voting result Hi all, I would propose that we reconsider using the name OData.JS or ODataJS. OlingoJS certainly got majority of the votes but the number of votes is small (only 6 votes). This JavaScript client library for OData is the core client library for JavaScript mainly developed by sponsors of the TC of OASIS for OData (at least this first version), so it qualifies as an official JavaScript library of OData. Having OData.JS or ODataJS as its name will vastly increase the possibility that users will turn to our library as the first choice when he searches on the internet for "OData JavaScript library" and names like "OData.js", "Breeze.js", "JayData", etc. show up at the same time. Using OlingoJS will likely to cause brand dilution. Apache Olingo as the project name is totally respected but having OData as part of the library name would also be very beneficial. It would be really helpful if people voted on OlingoJS can shed light on your reasons for this choice so that we can discuss about it. Best, Yi -----Original Message----- From: Kobler-Morris, Sven [mailto:[email protected]] Sent: Wednesday, July 23, 2014 11:02 PM To: [email protected] Subject: Java Script library Name voting result Hi, for the name the majority is for "OlingoJS". So we use OlingoJS as name. Regards, Sven -----Original Message----- From: V.A, Chandan [mailto:[email protected]] Sent: Montag, 21. Juli 2014 14:32 To: [email protected] Subject: RE: [VOTE] Java Script library Name OlingoJS +1 Thanks, Kind Regards Chandan VA -----Original Message----- From: Kobler-Morris, Sven [mailto:[email protected]] Sent: Monday, July 21, 2014 2:19 PM To: [email protected] Subject: [VOTE] Java Script library Name Hi all, below is a list of collected names for the Java Script OData client library which makes sense from our point of view. For voting please ad a +1 behind your favorite choice. 1. datajs 2. OlingoJS 3. ODataJS 4. Olingo.OData.JS regards, Sven
