Mapping SVN usernames to git

[Michael Zangl]

Am 27.11.23 um 00:35 schrieb Frederik Ramm:
> let's make a list of what is required, 

My personal list (might be a bit outdated, but general flow should be OK):

  * Set up your favorite GIT hosting (I personally prefer GItlab self
    hosted, but you can also use Gitlab cloud, Github, Bitbucket, ...)
  * (Optional: Set up new CI)
  * Decide on / set up a common i18n solution (I personally prefer Weblate)
  * Change JOSM to add a version to each release (like 24.1.0, 24.1.1,
    24.2.0) (e.g. setting a variable before each stable version)
  * Make adjustments to JOSM so that it will check compatibility for
    either version or revision
  * (Optional: Specify a new format for the plugin list, with central
    crawler as CI-Job)
  * For each Plugin that is still supported, do
      o Convert that Plugin to a separate GIT repository
      o Move that GIT to our git hosting
      o Change build system to Gradle (Plugin by Florian)
      o Use JOSM version for compatibility
      o Use a Git-Workflow (branches + merge requests) for new
        contributions and i18n changes; use git tags for releases
      o Milestone: All active plugins use same build system and JOSM
        core members have access to them (to make changes).
  * Drop the revision from being used anywhere (use version instead)
  * Move JOSM to git (Optional: Move to new CI)
  * Use a Git-Workflow (branches + merge requests) for new contributions
    and i18n changes; use git tags for releases
  * Change build to use gradle - rework directory structure (will make
    build scripts easier to read). Drop Ant+Eclipse
  * Make first release using a git tag, drop that version hack from above.

> and find volunteers who commit to doing that. 
Sadly, I cannot commit much time into this for the next year or so. I 
have to find some paid programming (as Freelancer) in January again 
(currently not as easy as it used to be, especially if one does not just 
want to work for a banking company …). I would really like to help, but 
my time is limited.

If you're still interested by the end of 2024 or 2025, I'd be willing to 
help with programming. Provided the ideological discussion points (GIT, 
Maven vs. Gradle, i18n) are settled, and we can agree on a general order 
of changes, step by step, within a total timeframe of less than 6 months.

If you just want to chat about the issue, I'm open to a call or a 
meeting at the Karlsruhe Hack Weekend or another event in or near Germany.

I really want to see JOSM continue to develop in the future, and I'd 
like to have Dirk on board. We may have differences in methodology, but 
he's doing a great job of keeping JOSM running and stable.

Michael