Hi Werner, I've signed up for the JCP as an Associate member. Politics don't really bother me. ;-) How would you recommend someone like me get involved in the Jakarta EE environment as things are shifting towards that direction?
--William ________________________________________ From: Werner Keil <werner.k...@gmail.com> Sent: Wednesday, November 7, 2018 12:12 PM To: dev@tamaya.incubator.apache.org Subject: Re: RFC: Draft for report - will submit at 2018-11-06 William, Thanks for the reply. Are you a member of the JCP as well? Either Associate (contributors can pretty much help with almost everything, too) or Full JCP Member? I'm afraid there's a lot of politics, I just joined the regular Jakarta EE Spec Committee call and while I won't disclose more than the minutes should document anyway, there is a looming worry, that not only the GroupId has to change but also other dependencies including existing JSRs like CDI, etc. that use the "javax" package namespace or quote the term "Java" could be at risk. That certainly speaks a great bit against JSR 382 which uses the "javax" namespace and could mean, Eclipse Foundation would rather have to start from scratch or simply derive what was done at MicroProfile Config into a new Jakarta.config spec. I cannot say which way it'll happen, but there are a lot of things discussed and lawyers promised stuff (I already know that kind of "Waiting for Godot" while I was still in the JCP EC and Java EE 8 was in a standstill) which nobody dares to make binding decisions before they delivered on those promises. Werner On Wed, Nov 7, 2018 at 6:51 PM William Lieurance < william.lieura...@namikoda.com> wrote: > *blush* I'm just happy to be able to help. > > In truth, I think once the substantial api/spi changes that Anatole has > mentioned for jsr382 (and I think I saw on a branch accidentally) go in, > the biggest thing we are missing is breadth of documentation and even more > examples. Our current answer of "Go look at the tests" to find how to use > tamaya is ok for now but is probably a stumbling block for developers > looking for the easiest path to onboard themselves. > > I'm super interested in helping out with getting jsr382 across the finish > line to unblock that effort and then start churning out examples for all > the different kinds of uses that tamaya has. I think that's also the way to > start getting more people using and then ultimately involved with tamaya. > > --William > > Sent from a tiny keyboard > > ________________________________ > From: Werner Keil <werner.k...@gmail.com> > Sent: Wednesday, November 7, 2018 9:43:13 AM > To: dev@tamaya.incubator.apache.org > Subject: Re: RFC: Draft for report - will submit at 2018-11-06 > > Btw both the contribution activity in JSR 382 (see before) and MicroProfile > Config: https://github.com/eclipse/microprofile-config/graphs/contributors > have massively decreased since a peak about a year ago. > And there are just 2 who contributed more than 5k LOC, 2 (including John) > with up to 1.5k LOC and the rests is irrelevant with sometimes only a > character or two contributed. > > Compared to both of them Tamaya looks quite good: > https://github.com/apache/incubator-tamaya/graphs/contributors > 2 contributed over 20k LOC, 1 over 5k and 2 others over 1.5k over the > history of the project. > > I did not realize how much William has done, so why haven't we voted on his > committer role already? > > Werner > > > > > On Wed, Nov 7, 2018 at 4:32 PM Werner Keil <werner.k...@gmail.com> wrote: > > > Phil mentioned two possible committers. > > Not sure if they meet requirements by ASF based on their existing > > contributions like JIRA, etc. to be nominated right now? > > > > Anatole mentioned support for both JSR 382 and MicroProfile config. > > However the Config standardization efforts are totally fragmented between > > JSR 382, MicroProfile Config and a few others like DeltaSpike. > > MicroProfile Config like most MP efforts is a 1-3 person gig, so not much > > difference to Tamaya. The JSR is canibalized by that because the same > > people have to take care of both: > > https://github.com/eclipse/ConfigJSR/graphs/contributors shows there are > > just 2 who contributed beyond 5k LOC, one about 1.5k and everyone else > less > > than half of that at most. > > The JSR should long have undergone a Renewal Ballot as per JCP.next rules > > (it's 13 months now since the creation on Oct 9, 2017, JCP.next mandates > a > > Renewal Ballot after 9 months) but nobody seems to have started that, nor > > is Spec Lead organization Eclipse sure, what to do with it. I know from > the > > Jakarta EE Spec Committee, that David/Tomitribe put the idea of a > > "jakarta.config" on the table, but that has not been decided on either. > > MicroProfile Config will never be a "standard", so the decision is > between > > putting enough life into the JSR to pass the Renewal Ballot and go Final > > and Withdraw it. > > > > Then a downstream project like Tamaya had to implement yet another 3rd > API > > and abandon at least one or both others it used so far. > > I don't think the pressure is really on Tamaya at this point and it seems > > the decisions for the Config spec will be made any time soon. > > > > So taking the offer of two or three committers looks like a good idea. > > IMO I would mention the upstream config API problem in a few words, it is > > nothing Tamaya itself can solve, but it has an impact also on the pace at > > which new releases make sense. > > > > Regards, > > > > Werner > > > > > > > > > > On Wed, Nov 7, 2018 at 5:50 AM John D. Ament <johndam...@apache.org> > > wrote: > > > >> I've signed off on the report. However, there were a lot of merge > >> conflicts so if you could please double check. > >> > >> I'm concerned about the strength of the project. It's basically a 2 > >> person > >> team. What can we do to try to grow the community? > >> > >> John > >> > >> On Tue, Nov 6, 2018 at 5:36 PM P. Ottlinger <pottlin...@apache.org> > >> wrote: > >> > >> > Am 06.11.18 um 22:06 schrieb Justin Mclean: > >> > > Just a friendly reminder that the report is due today - don't forget > >> to > >> > submit it. > >> > > >> > Thanks, > >> > done: > >> > https://wiki.apache.org/incubator/November2018 > >> > > >> > n8 > >> > Phil > >> > > >> > > >
