search

EclipseFdn / eclipsefdn-github-sync

This toolset is responsible for synchronizing committers, contributors and settings across all Eclipse Foundation GitHub repositories and organizations.
Eclipse Public License 2.0
0 stars 7 forks source link

Proposal to change repository name to reflect actual usage #138

Open autumnfound opened 3 years ago

autumnfound commented 3 years ago

In the past year, our Github sync repo has grown by leaps and bounds to encompass sync operations across our different version control platforms. In light of this, should we update the name of the repo to more accurately reflect the actual contents of this repo? Something along the lines of eclipsefdn-vc-sync or eclipsefdn-vc-tools (as we have some scripts that are managagement scripts as well) maybe?

autumnfound commented 3 years ago

@chrisguindon thoughts?

chrisguindon commented 3 years ago

+1 I agree that it makes no sense to keep github in the name of this repo. Let's do a poll before we rename:

fredg02 commented 3 years ago

Would it make sense to split up the repos (e.g. eclipse-github-sync, eclipse-gitlab-sync and eclipse-common-sync) or is there too much overlap?

autumnfound commented 3 years ago

Would it make sense to split up the repos (e.g. eclipse-github-sync, eclipse-gitlab-sync and eclipse-common-sync) or is there too much overlap?

The issue is that there are tools that are made to integrate the 2 (see the new backup/import script we created for OHWG). If we start to fragment this repository, we still have dependencies on the other which just creates a weird dep cycle which isn't ideal either.