Closed hutchig closed 5 years ago
This proposal is a development of the ideas here: https://groups.google.com/d/msg/microprofile/F0ehhd1MFMc/UPFcUOjGBwAJ @cescoffier @gunnarmorling I am implicating you two too!
Would it be a good idea to work on an actual implementation, possibly in SmallRye, before looking to create a specification on this idea?
Yes I think you could be right @kenfinnigan, this draft PR is just a stake in the ground and a place to collabourate on. I need a folder somewhere that I (we hopefully) can push commits to.
To be honest, we need somewhere stateful to record how it might work at least as much as somewhere to build something that runs - of course the two could be in one place.
More than happy to create a SmallRye repo to start experimenting with API/Impl that can then feed into a spec
@kenfinnigan I will seek the opinion of Clement @cescoffier and Gunnar @gunnarmorling and Kevin Sutter @kwsutter here in IBM but I am happy anywhere I can push -u
to, really I am.
Ken @kenfinnigan, I (and IBM) are +1 on taking you up on the smallrye repo offer as a PoC location if Gunnar @gunnarmorling and Clement @cescoffier are happy with that. Thank you!
We definitely need an implementation first to have an idea of what's possible to do and the usability. SmallRye is fine for me (already active there).
I've created https://github.com/smallrye/smallrye-event-sourcing and given @hutchig, @cescoffier, and @gunnarmorling access.
Let me know if anyone else needs access to work on the repo.
Do we leave this PR open or close in short term?
Thank you very much Ken.
Please leave the PR open as it is a useful breadcrumb for me.
I think it is useful as a description and sign-post to the smallrye repo and as a way to bagsy the event-sourcing folder name under proposals.
We will have to come back here (to this repo) someday unless the MicroProfile new project process changes and it will do no harm to 'own' the name.
I have some text locally to do this that I will push (and merge) in the near future. Further work to prepare for community approval I would aim to do by concensus of https://github.com/orgs/smallrye/teams/event-sourcing/members in the smallrye repo.
Based on https://wiki.eclipse.org/MicroProfile/FeatureInit: which says: "Submit as many PRs as you need to explore the ideas behind the proposal. No approvals or prior notification required."
I am going to take that as 'meaning what is says and saying what it means' and modify the proposal in a number of PRs.
@cescoffier Clement, I agree with you when you say "We definitely need an implementation first to have an idea of what's possible to do and the usability." I did want to dump some text somewhere visible though about what I think the project might aim at and the value. I need to do this partly as a resource to aid in my bid for time to work on the PoC (mostly after Reactive Messaging 1.0 delivery for OpenLiberty) and also to 'socialise' the idea early on to get feedback. To this end I have dropped https://github.com/eclipse/microprofile-sandbox/blob/master/proposals/event-sourcing/proposal/src/main/asciidoc/proposal.asciidoc (only version 0.01 currently) to share what was in my head. Feel free to throw stuff at it or PR it.
This is just a shell at the moment to hold the place for further work. Hence a draft pull request.
Signed-off-by: Gordon Hutchison Gordon.Hutchison@gmail.com