Or take a myriad of JSRs I help one way or the other. Not every EG member always commits the same amounts of code, some probably never do, especially if the driving companies (Red Hat, Oracle or IBM on the EE side) mostly prefer to do that by themselves. The last time you (Mark) seem to have committed to CDI must have been 1.1 or so (up to 4 years ago) since then John was probably a notable non-Red Hat EG member who did. Both Anatole, myself or e.g. Otavio are in the EG but we have not touched the code. Nevertheless at least I try to join calls as often as I can. And participate on the mailing list.
You'll find plenty of other JSRs e.g. both ME 8 JSRs where I was the only Individual you saw contribute to design decisions and join EG calls in most cases. Similar with JSRs on the EE side including the EE Umbrella, JPA, JSF, JSON-P or JMS. With Security (375) next to countless effort by Arjan I did most work not only speaking. I see, Mark you even made 3 commits over a year ago to its "sandbox". I'm afraid the Spec Lead isn't too responsive, but if they pick up again, I'm sure the JSR was more than happy to list that in the new "Contributor" section. If JSR 375 created the impression one can simply fork or do "your own JSR" then sorry for that on behalf of Alex or David who started this "sandbox". It's a bit of a "jigsaw puzzle" and having Soteria contain an "embedded API" is more than sad, but some members of the EG like Arjan, Ivar myself and occasionally others spreading the word and trying to get it to a working shape is not easy with a "Spec Lead Emeritus" until Oracle decides what it wants to do. That's why we should wait before proposing new JSRs how the life of existing ones goes, especially those Java EE relevant (and as much as CDI2 or Tamaya/Config should work for desktop/RCP they play their biggest role in the Enterprise, so they're both EE-relevant if not possible parts of future EE umbrella distros) Werner
