FYI I renamed the proposal fleece and here is the proposal:
https://wiki.apache.org/incubator/Fleece.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-01 14:27
On Tuesday, June 3, 2014, Romain Manni-Bucau rmannibu...@gmail.com wrote:
FYI I renamed the proposal fleece and here is the proposal:
https://wiki.apache.org/incubator/Fleece.
We'll be looking forward to those free Apache Fleece vests at the next
ApacheCon ;-)
-Bertrand
Later
On 3 Òkúdu 26 Heisei, at 3:47 Ọ̀sán, Bertrand Delacretaz
bdelacre...@apache.org wrote:
On Tuesday, June 3, 2014, Romain Manni-Bucau rmannibu...@gmail.com wrote:
FYI I renamed the proposal fleece and here is the proposal:
https://wiki.apache.org/incubator/Fleece.
We'll be
If Fleece is decided as the name, you can probably remove or edit the “Project
Name” section on the proposal.
Suresh
On Jun 3, 2014, at 2:57 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote:
FYI I renamed the proposal fleece and here is the proposal:
Hi
Should be ok now
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-03 15:17 GMT+02:00 Suresh Marru sma...@apache.org:
If Fleece is decided as the name, you can
I’m pretty sure this is something CXF would be interested in as well. We
currently have some level of JSR-353 support in CXF, but it’s currently just
using the reference implementation [1]. Having an alternative implementation
that we can use to make sure we aren’t tied specifically to the
I think building up these downstream dependencies on Fleece is essential
for the Fleece's success.
Marlon
On 6/3/14 2:44 PM, Daniel Kulp wrote:
I’m pretty sure this is something CXF would be interested in as well. We
currently have some level of JSR-353 support in CXF, but it’s currently
On Sun, Jun 1, 2014 at 2:32 AM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
Hi guys,
Started to write a proposal to create a project to implement JSR-353 (json
API).
Here is the current proposal (draft):
https://wiki.apache.org/incubator/JsonImpl
It needs some mentors so if you are
Hello Sagara,
Updated, thanks.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2014-06-01 9:06 GMT+02:00 Sagara Gunathunga sagara.gunathu...@gmail.com:
On Sun, Jun 1,
On Sun, Jun 1, 2014 at 3:38 AM, Romain Manni-Bucau
rmannibu...@gmail.com wrote:
Hi John,
The link is the right one ( https://github.com/rmannibucau/json-impl ).
Created it yesterday so community is small ATM ;).
Initial developpers are the one intended to get perms on the asf repo, did
I
On 1 Jun 2014, at 0:31, Justin Mclean wrote:
Hi,
About the name any proposition is welcomed. I though to brace BTW.
Apache Argonaut sounds good but I assume that name is in common use so
perhaps Argus (the ship builder), or perhaps Fleece?
I actually once wrote an article called Json and
Hi Christian,
updated the proposal page according to your comments (added you as mentor
for now and merged initial/core dev parts).
Will try to import noggit parser (actually I was in thr process of removing
antlr which was mainly here to get started quickly so if noggit avoids me
to rewrite a
Hi!
commons might be an option. But we still would need to go through the
incubator.
Otoh Commons proved not to be very JSR friendly to be honest. We had this
discussion for BVal etc, and recent JCS discussions where also not in favour
for it. I'd be happy to host it over there though.
Hi,
commons might be an option. But we still would need to go through the
incubator.
Otoh Commons proved not to be very JSR friendly to be honest. We had
this discussion for BVal etc, and recent JCS discussions where also
not in favour for it. I'd be happy to host it over there though.
On 1 Jun 2014, at 12:21, Romain Manni-Bucau wrote:
Hi Christian,
updated the proposal page according to your comments (added you as mentor
for now and merged initial/core dev parts).
Will try to import noggit parser (actually I was in thr process of removing
antlr which was mainly here to
Ok,
removed antlr, think few things need review/test/etc (typically unicode is
not yet supported) but at least DoS attacks are controlled normally.
Next step for me: get an idea of the performances
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn:
Hi,
Here is the current proposal (draft):
https://wiki.apache.org/incubator/JsonImpl
There's a minor copy/paste error as the proposal still contains a reference to
Delta Spike.
The following JIRA project would be required to track issues for the Apache
DeltaSpike project:
It needs some
Hi Justing,
thanks for the catch! I updated the page and added yourself as Mentor.
About the name any proposition is welcomed. I though to brace BTW.
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github:
Romain,
Can you add a link to the existing github sources? Or is the one
mentioned later on what's intended? Doesn't seem like a big community
thus far, but more on that... The current code base (if accurate)
only has a single contributor yet you list 5 initial developers.
I'll also point out
Hi John,
The link is the right one ( https://github.com/rmannibucau/json-impl ).
Created it yesterday so community is small ATM ;).
Initial developpers are the one intended to get perms on the asf repo, did
I misunderstand?
If we make it a subproject of G or TomEE this will never be used
Hi,
About the name any proposition is welcomed. I though to brace BTW.
Apache Argonaut sounds good but I assume that name is in common use so perhaps
Argus (the ship builder), or perhaps Fleece?
Thanks,
Justin
-
To
21 matches
Mail list logo
