| Re: [jaxrs-dev] Round of Introductions |
Not officially, but done. ;-) From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth I don't think that an official invitation for everyone interested in JAX-RS to join this list posted to ee4j-community does any harm. If the PMC doesn't inform people about these lists, we have to do it. ;-) 2018-02-19 20:11 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: Christian, no offence taken. In fact I share the same vision. I just am not sure whether it is a good idea if we now should catch up now and write to those mailing list? -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Hi Markus, sure, I know that most likely the PMC requested the creation of the list. My comment wasn't targeted at you in any way. It was just a general idea for improvement and no criticism. But I think I should post that on ee4j-communty to reach out to the right people. Christian 2018-02-18 16:39 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: You are right with all what you say but I simply do not know who asked for creation of this particular list. I doubt it was the project lead as he never posted anything here so far. I was told of the existence long after it was created. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Hi Markus, sure, the EMO creates these mailing lists, but someone from the EE4J umbrella project or the project leads of the individual sub-projects requested to create these lists. So it should be the responsibility of the party that requested the mailing list to announce it on the EE4J specific mailing list ee4j-community to let everyone know about it. At least this is my view as someone who is watching the ee4j-community list for such announcements. ;-) Christian 2018-02-18 14:24 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: Christian, * ee4j-community mailing list -- Added to my Wiki. Thanks! :-) * Announcement of new mailing list: Naming and creation of mailing lists (and all other technical resources) is performed by the EMO. I assume they will be happy to receive your improvement proposal. There is nothing project leads can change here, unfortunately. The EF "apparently" seems to work a bit in private here (more like a vendor's club, not like a public institution), far not in that way "open" as I would like to have it. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Hi Markus, that's a great idea. The list you prepared looks fine! Perhaps we could also post to the ee4j-community list? Most people interested in EE4J and the future of Java EE have subscribed to this list. And to be honest, I expected announcements about new mailing lists to be posted there. That's why I was surprised to see that lists like ee.net-wg, jax-rs-dev, etc. are already in use. Christian 2018-02-18 13:42 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: Christian, I am currently preparing an invitiation which I plan to post wherevery possible. If you have more ideas about useful mailing lists / groups then please tell me! :-) Invitation status in maintained in my personal wiki: https://github.com/mkarg/jaxrs-api/wiki/%5BManagement%5D-Invitations. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Hi Markus, thanks a lot for the warm welcome. I agree that having separate JSRs for JAX-RS and MVC was the correct decision back then. However, good integration with JAX-RS is a very important success factor for us and therefore I would love to help moving JAX-RS forward. I agree that it may be a bit early to start discussions about issues on GitHub. But I hope that we can get more people on this mailing list soon. I agree with Kevin that it would be a good idea to send some kind of invitation to the old JAX-RS list on groups.io. There are currently about 50 members on this list and it would be great to get them on the new list. Christian 2018-02-17 16:35 GMT+01:00 Markus KARG <markus@xxxxxxxxxxxxxxx>: Hello Christian, I am very glad to have you in the boat, as I do see MVC API -besides the compliant runtimes and applications- as an important stakeholder for the JAX-RS API! I remember very well when I proposed to split up the JAX-RS EG into one for JAX-RS and one for MVC, and while I still think it was the correct decision back then, sharing contributors is a great thing to get our APIs aligned, indeed. I noticed that you already started some threads in the Github issues tracker, which is great! Please don't mind if discussions will start slowly, as not all committers have access to Github and the mailing list as of today, but day after day more committers do enter, so (hopefully) we have lively discussions rather soon! CU -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth Hi everyone, I would like to take the opportunity to introduce myself. Even though I'm not (yet) a committer. :-) My name is Christian Kaltepoth. I'm specification lead for JSR 371 (MVC 1.0) and also was in the EG for JSR 380 (Bean Validation 2.0). As MVC 1.0 is built on top of JAX-RS, I'm very interested in JAX-RS's future. As part of my work on MVC 1.0 many JAX-RS related issues came up, which I reported to the JAX-RS EG. Unfortunately most of them are still unresolved and I would love to help getting them fixed. Beside that I'm also using JAX-RS almost daily in my job, so I have quite some experience with the API and know about the good parts and what could be improved. ;-) Regards
--
--
--
--
-- |