Move Grizzly to the GlassFish project?

[arjantijms]

Hi all,

It seems that Grizzly didn't quite get the life outside of GlassFish that we thought it might get. Just like HK2, Grizzly has been exclusively been contributed to from within the GlassFish community.

I'd like to propose we move this to the GlassFish project, so that the much bigger group of GlassFish committers can review and merge commits.

Thoughts?

[kofemann]

If it stays as an independent module, that is fine with me. I definitely don't want to have Glassfish as a dependency. Even the whole http part in Grizzly is too much for me. I need just NIO and memory management (https://github.com/dCache/oncrpc4j). I think this is true for some others as well, like opendj.

[pzygielo]

If it stays as an independent module

I guess the question is not about moving project code, which would stay as-is, but rather to move grizzly repositories under ee4j.glassfish - like many listed at https://projects.eclipse.org/projects/ee4j.glassfish/developer.

[carryel]

If Grizzly can be improved more actively and become an environment in which more participants can participate, I think it would be a good direction.

[carryel]

If Grizzly is moved to the Glassfish project, I have a few questions.

• Will Grizzly's independent release process change?
• Will Grizzly's version control rules also change?

[pzygielo]

IMO, i.e. non-authoritative:

If Grizzly is moved to the Glassfish project, I have a few questions.

* Will Grizzly's independent release process change?

No, it won't. There are many independently released components under ee4j.glassfish, like maven plugins, HK2, Concurrō.

* Will Grizzly's version control rules also change?

No need to do so.

---

There is also option to elect new Committers to existing project. And keep protocols established here and set up infrastructure.

[arjantijms]

No, it won't. There are many independently released components under ee4j.glassfish, like maven plugins, HK2, Concurrō.

True

No need to do so.

Very much true too.

[arjantijms]

With some delay, the process has been initiated now. See https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/869

[carryel]

I believe this issue has been resolved and will now close it.

[pzygielo]

I think GlassFish should elect previous Grizzly committers to become GlassFish members yet.

[dmatej]

I think GlassFish should elect previous Grizzly committers to become GlassFish members yet.

I agree.
Should we limit that for active committers in last two years or so? Do we have the list of original committers, not just the list of contributors here?

Also we should ask them first: @carryel , @kofemann ... maybe @kemalturksonmez could join us too?

[carryel]

Of course, I would like to become a GlassFish member.

Another wish is that I could re-release some grizzly-related projects below, like I did before(I'm guessing their release process has changed):

https://github.com/eclipse-ee4j/glassfish-grizzly-memcached/
https://github.com/eclipse-ee4j/glassfish-grizzly-thrift/

I'm not sure about the original committers' information, it's too old.

PS) In the past, I had released the following procedures.

- Trigger the release job from CI.
- "Create New Release" at https://projects.eclipse.org/projects/ee4j.grizzly
- Send mail to the channel about this release.
- Then release the repository using the job in CI.

The CI seems to have been moved to "https://ci.eclipse.org/glassfish/view/grizzly/" https://ci.eclipse.org/glassfish/view/Grizzly/, and the right to run the job seems to have disappeared.