Migration Jira Issues to GitHub issues

[sparsick]

We have a decision on the mailing list to switch from Jira Issues to Github issues.

This kind of work is perfect for automation. Therefore, a migration tool was created.

Following jira project are founded:

key	name	GitHub Issues enabled?	Migration Tool Configuration Created?	Migration Done?
MASFRES	Apache Maven Resource Bundles	❌	❌	❌
MNG	Maven	❌	❌	❌
MACR	Maven ACR Plugin	❌	❌	❌
MANTRUN	Maven Antrun Plugin	❌	❌	❌
ARCHETYPE	Maven Archetype	❌	❌	❌
MARCHETYPES	Maven Archetype Bundles	❌	❌	❌
MARTIFACT	Maven Artifact Plugin	❌	❌	❌
MASSEMBLY	Maven Assembly Plugin	❌	❌	❌
MBUILDCACHE	Maven Build Cache Extension	❌	❌	❌
MCHANGELOG	Maven Changelog Plugin	❌	❌	❌
MCHANGES	Maven Changes Plugin	❌	❌	❌
MCHECKSTYLE	Maven Checkstyle Plugin	❌	❌	❌
MCLEAN	Maven Clean Plugin	❌	✔️	❌
MCOMPILER	Maven Compiler Plugin	❌	❌	❌
MDEP	Maven Dependency Plugin	❌	❌	❌
MDEPLOY	Maven Deploy Plugin	❌	❌	❌
MDOAP	Maven DOAP Plugin	❌	❌	❌
DOXIA	Maven Doxia	❌	❌	❌
DOXIASITETOOLS	Maven Doxia Sitetools	❌	❌	❌
DOXIATOOLS	Maven Doxia Tools	❌	❌	❌
MEAR	Maven EAR Plugin	❌	❌	❌
MEJB	Maven EJB Plugin	❌	❌	❌
MENFORCER	Maven Enforcer Plugin	❌	❌	❌
MGPG	Maven GPG Plugin	❌	❌	❌
MPH	Maven Help Plugin	❌	❌	❌
MINDEXER	Maven Indexer	❌	❌	❌
MINSTALL	Maven Install Plugin	❌	❌	❌
MINVOKER	Maven Invoker Plugin	❌	❌	❌
MJAR	Maven JAR Plugin	❌	❌	❌
MJARSIGNER	Maven Jar Signer Plugin	❌	❌	❌
MJAVADOC	Maven Javadoc Plugin	❌	❌	❌
MJDEPRSCAN	Maven JDeprScan Plugin	❌	❌	❌
MJDEPS	Maven JDeps Plugin	❌	❌	❌
MJLINK	Maven JLink Plugin	❌	❌	❌
MJMOD	Maven JMod Plugin	❌	❌	❌
JXR	Maven JXR	❌	❌	❌
MLINKCHECK	Maven Linkcheck Plugin	❌	❌	❌
MPDF	Maven PDF Plugin	❌	❌	❌
MPLUGINTESTING	Maven Plugin Testing	❌	❌	❌
MPLUGIN	Maven Plugin Tools	❌	❌	❌
MPMD	Maven PMD Plugin	❌	❌	❌
MPIR	Maven Project Info Reports Plugin	❌	❌	❌
MNGSITE	Maven Project Web Site (Moved to GitHub Issues)	❌	❌	❌
MRAR	Maven RAR Plugin	❌	❌	❌
MRELEASE	Maven Release Plugin	❌	❌	❌
MRRESOURCES	Maven Remote Resources Plugin	❌	❌	❌
MRESOLVER	Maven Resolver	❌	❌	❌
MRESOURCES	Maven Resources Plugin	❌	❌	❌
SCM	Maven SCM	❌	❌	❌
MSCMPUB	Maven SCM Publish Plugin	❌	❌	❌
MSCRIPTING	Maven Scripting	❌	❌	❌
MSHADE	Maven Shade Plugin	❌	❌	❌
MSHARED	Maven Shared Components	❌	❌	❌
MSITE	Maven Site Plugin	❌	❌	❌
MSKINS	Maven Skins	❌	❌	❌
MSOURCES	Maven Source Plugin	❌	❌	❌
MSTAGE	Maven Stage Plugin	❌	❌	❌
SUREFIRE	Maven Surefire	❌	❌	❌
MTOOLCHAINS	Maven Toolchains Plugin	❌	❌	❌
MVERIFIER	Maven Verifier Plugin	❌	❌	❌
WAGON	Maven Wagon	❌	❌	❌
MWAR	Maven WAR Plugin	❌	❌	❌
MWRAPPER	Maven Wrapper	❌	❌	❌
MMETRIC	The Maven Metric Extension	❌	❌	❌

[sparsick]

Shared Component List:

Shared Component Name	GitHub Issues Enabled?	Migration Done?
file-management	❌	❌
maven-ant	❌	❌
maven-app-configuration	❌	❌
maven-archiver	❌	❌
maven-artifact-transfer	❌	❌
maven-common-artifact-filters	❌	❌
maven-dependency-analyzer	❌	❌
maven-dependency-tree	❌	❌
maven-doxia-tools	❌	❌
maven-filtering	❌	❌
maven-invoker	❌	❌
maven-jarsigner	❌	❌
maven-mapping	❌	❌
maven-project-utils	❌	❌
maven-reporting-api	❌	❌
maven-reporting-exec	❌	❌
maven-reporting-impl	❌	❌
maven-script	❌	❌
maven-script-interpreter	❌	❌
maven-shared-incremental	❌	❌
maven-shared-io	❌	❌
maven-shared-jar	❌	❌
maven-shared-monitor	❌	❌
maven-shared-resources	❌	❌
maven-shared-utils	❌	❌
maven-verifier	❌	❌

This list is necessary, because the Shared Component Jira Project should be splitted in many repository.

[slawekjaranowski]

MSITE - has GitHub issues enabled

[slachiewicz]

Can we migrate issues from MSITE ? what You need from us?

[slachiewicz]

MMETRIC - no issues from jira - nothing to migrare.

[slachiewicz]

MSKINS - that's multi repo jira

[ascheman]

Can we migrate issues from MSITE ? what You need from us?

As far as I understood, @slawekjaranowski didn't want to (completely) migrate MSITE (cf. apache/maven-site#599 (comment))?

[slawekjaranowski]

Can we migrate issues from MSITE ? what You need from us?

As far as I understood, @slawekjaranowski didn't want to (completely) migrate MSITE (cf. apache/maven-site#599 (comment))?

As I wrote many time I don't see a benefit to copy all issues (about 500) for MSITE.
It is documentation site, so we don't have a versions, regressions and so on
We simply have a current state of documentation.

For other type of project it may be valuable.

[slawekjaranowski]

for reference next project - apache/maven-apache-resources#23

[slachiewicz]

I thought about maven-site and only open issues. As they are relatively new and the community could help to improve.
Pinned a new issue with ref to Jira would also work, but will limit a bit discussions or asking questions. And could be a good try for migration.

[slawekjaranowski]

We already have a link to jira https://github.com/apache/maven-site/issues/new/choose

[slachiewicz]

for reference next project - apache/maven-apache-resources#23

https://issues.apache.org/jira/browse/MASFRES
No open issues - so nothing to migrate.

[slachiewicz]

We already have a link to jira https://github.com/apache/maven-site/issues/new/choose

True, I forgot that this link is when I want to raise a new issue. Not visible if someone is looking around for something to start contributing. So it's a UX issue.

[slawekjaranowski]

I thought about maven-site and only open issues. As they are relatively new and the community could help to improve. Pinned a new issue with ref to Jira would also work, but will limit a bit discussions or asking questions. And could be a good try for migration.

But pinned issue is also good idea

[sparsick]

Thanks for your feedback. After discussion with @ascheman, I think it is better to move the tables to the migration tool repos and give Maven committers write permission to that repository. I will also write it to the mailing list.