Hi,
On 29.05.23 15:50, Christoph Läubrich wrote:
I must confess "another central project" do not feels right:
1) there already is a "central" one everyone can easily find if
searching for "maven github": https://github.com/apache/maven/
That does not help here because that project is Maven itself (maven
core)... which will produce much more confusion from my POV.
2) for "subprojects" its usually better to discuss things close where
the code is
In general yes ... but unfortunately many people do not see the need
focus for that...(https://maven.apache.org/plugins/) shows every project
with link to appropriate GH projects etc...
Please note that some feature in GH do not work well across repositories
(e.g. embedding code snippets in issues), also I don't see any advantage
in scattering things around.
Yes that is a real problem with GH issues etc.
Having a "central place "where contributors need to watch out and move
things around or need to find out what the topic is about will make
things more confusing, usually users are quite familiar with finding the
right place.
I have different experiences...
If one wants to group things more, it would be better to have an
apache-maven organization on gihub and move all maven related there (the
one can also have organization readme, pinned repositories and so on),
this works quite well (e.g. Eclipse Foundation uses that approach).
Yes that might be a better solution going via a Apache Maven Project
Organisation ... +1 for that...
But in the end it will not solve the problem to redirect the people to
the "correct" project....
Kind regards
Karl Heinz Marbase
Am 29.05.23 um 13:50 schrieb Karl Heinz Marbaise:
Hi,
I would suggest to create an umbrella project like:
apache-maven-project
on github and make it the central starting point for users... to ask
question (discussions) and optionally reroute them to the appropriate
github repos...
In general I agree to the tendency to use GH issues etc. instead of JIRA
based on the hurdles which exists (for a lot of reasons)...
I second Hervé's suggestion to write down the needed/practical steps ...
and start going...what about things currently in JIRA and needed to be
migrated moved etc. ..We have a large history in JIRA...
To fulfill the formalism (also have documented the decision here on the
ML) we should start simply a VOTE to get an in general decision about
moving to GH-issues to leave JIRA behind... (not about the details) that
can be done later on...(for example using GH discussions etc.)
afterwards we can decide with which project we would like to start and
fiddle the details.
Kind regards
Karl Heinz Marbaise
On 27.05.23 09:22, Hervé Boutemy wrote:
on testing GH issues migration from Jira: yes
cache-extension [1] looks like an interesting example, given it has a
small
history with its Jira content
we also have mvnd which uses GH issues from the start: testing and
making
clear practices on release and release notes could also be worked
there [2]
we'll need to write down what practical steps such a migration requires
=> probably a good fit for our Wiki, where we already organized
equivalent
updates in the past [3]
on using GH discussions, I suppose this should be an independent next
discussion
[1] https://github.com/apache/maven-build-cache-extension
[2] https://github.com/apache/maven-mvnd
[3]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Infrastructure
Le vendredi 26 mai 2023, 09:44:00 CEST Olivier Lamy a écrit :
Hi,
This has been already discussed in the past.
But due to recent changes in ASF Jira infrastructure (limitation of
Jira users, validation of account creation).
Maybe we could reconsider moving from Jira to GH issues and why not
simplify the workflow as well.
I imagine not having to create an issue if a PR exists first (sounds
like duplicate work).
By the way, release notes will be automatically created from PRs.
(could be manually modified if a change doesn't have a PR).
Regarding migration, we can start project by project.
Few options:
- extreme simplicity, do not migrate any data (just mark the Jira
project as read only with a banner/link to corresponding gh issues).
If someone really needs an issue to get fixed he will clone it to GH
- middle complexity, migrate only open issues (components moved as a
label)
- extreme complexity, migrate all issues of a project (components
moved as a label and version created)
We can start by small projects such as cache-extension and one plugin
(compiler?)
Regarding GH discussions, maybe we can open discussions for
https://github.com/apache/maven which sounds like a natural place for
users to go. (discussions could be mirrored to a ML)
I do not have a strong opinion here, but I feel like opening
discussions for every single repo will be complicated to follow up.
WDYT?
cheers
Olivier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
