Changes between Initial Version and Version 1 of Ticket #21902, comment 22


Ignore:
Timestamp:
2022-08-24T18:22:48+02:00 (3 years ago)
Author:
stoecker

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #21902, comment 22

    initial v1  
    55> As far as I see it the problem isn't with git or github, it's with third party repositories that you don't have access to and where the owner no longer responds. That seems like a fairly easy problem to solve though as you can just fork the repo and move all plugin links to the new one. Completely disallowing third party repositories is not a good idea (and partly defeats the purpose of a plugin system)
    66
    7 Not totally true. We, josm admins, still have access. We still enforce the policy that any plugin not in the JOSM group gets marked as "could be suspicious", so that authors usually agree to have the plugin in JOSM group where we can care for it. But compared to the original goal it means more work and not less. Before I had one SVN for all plugins. Now I have one SVN for many plugins and many GITs for the others. And like before with SVN all of them have been abandoned by the authors which "needed" the GitHub migration after some time.
     7Not totally true. We, josm admins, still have access. We still enforce the policy that any plugin not in the JOSM group gets marked as "could be suspicious", so that authors usually agree to have the plugin in JOSM group where we can care for it. But compared to the original goal it means more work and not less. Before I had one SVN for all plugins. Now I have one SVN for many plugins and many GITs for the others. And like before with SVN all of them have been abandoned after some time by the authors which "needed" the GitHub migration.
    88
    99That's simply the way it goes for plugins and has NOTHING to do with GIT or SVN.