While transforming into an umbrella project I'd like to ask what you think about identifying the parts we really like to support and maintain in the future and then move those to GIT?
Additionally we should also create dedicated JIRA projects for them.
And the step also on our list is to create a brand new site and keeping the old wiki based page only for historic reasons.
We could do this gradually, module by module.
git-repo-name, jira-prj-name, explanation
1.) GeronimoConfig, GERONIMO-CONFIG, geronimo implementation of the MicroProfile config spec and later also the ConfigJSR
2.) GeronimoFailsafe, GERONIMO-FAILSAFE, geronimo implementation of the Failsafe spec
3.) GeronimoSpecs, GERONIMO-SPECS, our specs module. Not sure whether this should also contain our genesis module and whether this is still used somewhere else now that the G server is retired?
4.) GeronimoJavamail, GERONIMO-JAVAMAIL,
5.) GeronimoTxMgr, GERONIMO-TXMRG, the transaction manager. Needs serious love btw - we use ancient libs...
Happy to add more.
Any reason not to start into this direction?
At this point, moving our repos to git would be moving to gitbox, e.g. github hosted repos, but you can still write to the ASF side primary via gitbox.a.o.
Being more active on github will give us a more modern look. It seems like the right approach to take.
Also, Safeguard (not failsafe?) is a git-wip hosted project. I would recommend splitting geronimo-specs into separate repos instead of one massive repo. Since creating the repos is a fully self serve function it should be low over head to create the repo when needed.
+-0 for not MP repos - well not get much tractions on them whatever we do, clearly a +1 and a must for MP repos.
For soecs Id stay in svn since git would make it harder to check maintain until we put them all here which is not correctly supported by git yet.
What about using github pages like layout for the website? geronimo.apache.org/$project?
Le 25 févr. 2018 13:23, "John D. Ament" <[hidden email]> a écrit :
imo we should not mix up svn and git repos because for me its hard to think about which project/module am i working on and which vcs is it using. i would keep it simple
i do not prefer to have a separate repo for each geronimo-specs module… we use this approach in my $$-job and its a mess (at least for me ;))
i would keep all modules with the same groupId in the same repo
or maybe we can say if we create a new/separate jira project maybe this is an indicator for a own repo (or the other way around)?
let me know if i can help with the new site… would be great if more people know about the geronimo-specs :D
|Free forum by Nabble||Edit this page|