To clarify: we've stopped automatically creating mirrors of
eclipse.org Git repositories on GitHub. The existing repositories
are AFAIK still being updated periodically by some magical script
that runs at GitHub.
SWTBot is running a vote to determine whether or not they're going
to ask me to remove their mirror. I think that this is an
outstanding idea. If you want your existing project mirrors to be
removed, please sort that out with your project members and let me
know (via email to emo@xxxxxxxxxxx).
Early in the new year, I'll identify the GitHub mirrors that do not
already have forks and use that list as the initial list of
candidates for deletion. I'm thinking that I can push forward with
these repos using lazy consensus (with at least a month of warning).
Then we need to sort out what we're going to do with the
repositories that have forks. I'm thinking that I'll need more
proactive input from the projects to decide what we're going to do.
Does this make sense?
Wayne
On 12/18/2013 12:43 PM, Wayne Beaton
wrote:
Mirroring project repositories on GitHub seemed like a good idea
at the time. We've stopped automatically mirroring repositories on
GitHub. This is just one more good reason to stop the practice.
In the new year, I'll start the process of shutting down these
repositories. If project teams aren't monitoring them, then I
think that they actually provide a disservice to the community and
should be removed. I need to work out a means of determining which
ones need to stay and how we go about making that work.
Minimally, I think that we need to turn off the mirroring for
those repositories that projects want to keep on GitHub (the
mirroring process is--or at least was--broken). That means we'll
have to figure out some way of making sure that this clones stay
up to date.
We also have some new GitHub hooks that do things like establish
and maintain project teams based on project commit rights, and
ensure that CLAs are in place. Projects that clone into the
Eclipse organization on GitHub should probably have these hooks
installed.
Due to the nature of Git, our repositories can be replicated
anywhere. It's probably a good idea to have a CONTRIBUTING file in
the root of your repository so that contributors have a fighting
chance of doing the right thing.
Wayne
On 12/18/2013 04:36 AM, Mickael
Istria wrote:
I've re-run the same script, and it appears that 103
contributions are pending for Eclipse projects on GitHub:
acceleo: 0 issues, 3 open pull requests
aether-ant: 0 issues, 1 open pull requests
bpmn2-modeler: 0 issues, 2 open pull requests
clatest: 3 issues, 3 open pull requests
e4.tools: 0 issues, 1 open pull requests
ecf: 0 issues, 1 open pull requests
eclipse.jdt.core: 0 issues, 1 open pull requests
eclipse.jdt.debug: 0 issues, 2 open pull requests
eclipse.jdt.ui: 2 issues, 2 open pull requests
eclipse.platform.common: 0 issues, 1 open pull requests
eclipse.platform.ua: 0 issues, 2 open pull requests
eclipse.platform.ui: 0 issues, 2 open pull requests
egit: 0 issues, 1 open pull requests
egit-github: 0 issues, 7 open pull requests
emf: 0 issues, 1 open pull requests
emf.texo: 0 issues, 1 open pull requests
gemini.blueprint: 0 issues, 1 open pull requests
gemini.jpa: 0 issues, 2 open pull requests
jetty.project: 0 issues, 3 open pull requests
jgit: 0 issues, 8 open pull requests
linuxtools: 0 issues, 3 open pull requests
lyo.testsuite: 0 issues, 1 open pull requests
m2e-core: 0 issues, 4 open pull requests
m2e-discovery-catalog: 0 issues, 1 open pull requests
m2e.wtp: 0 issues, 1 open pull requests
nebula: 0 issues, 1 open pull requests
nebula.widgets.nattable: 0 issues, 3 open pull requests
org.aspectj: 0 issues, 1 open pull requests
orion.client: 0 issues, 8 open pull requests
planeteclipse.org: 0 issues, 1 open pull requests
rap: 0 issues, 1 open pull requests
rap.incubator.fileupload: 0 issues, 1 open pull requests
rap.incubator.gef: 0 issues, 1 open pull requests
recommenders: 0 issues, 1 open pull requests
rmf: 0 issues, 1 open pull requests
rt.equinox.bundles: 0 issues, 1 open pull requests
rt.equinox.p2: 0 issues, 4 open pull requests
tycho: 0 issues, 4 open pull requests
vert.x: 0 issues, 13 open pull requests
webtools.jsdt.core: 0 issues, 3 open pull requests
webtools.jsdt.tests: 0 issues, 2 open pull requests
webtools.sourceediting: 0 issues, 1 open pull requests
webtools.webservices: 0 issues, 1 open pull requests
========================================
TOTAL: 5 issues, 103 open pull requests
Wouldn't it be better to disable pull requests for Eclipse
repository mirrors at GitHub? Or enforce usage of a hook on pull
request telling to use Bugzilla & Gerrit?
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
