Request to remove the "zope" project from LP

Asked by Andreas Jung on 2019-09-02

Hi there,

I am Andreas Jung and a member of the Zope Foundation team.

The "zope" project moved a long time ago to Github.

We would like to see the "zope" project being removed completely from LP since everything is on Github now.

How can care about this issue?

Andreas

Question information

Language:
English Edit question
Status:
Expired
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2019-10-03
Last reply:
2019-10-19
Colin Watson (cjwatson) said : #1

Launchpad is fundamentally designed to track projects that exist elsewhere, as well as projects that are hosted primarily on Launchpad. I'm not sure how good an idea removing all the Zope projects from Launchpad would be, because IIRC there are quite a few bugs that have tasks on zope.something in order to track upstream bugs on GitHub, and removing the projects would be pretty disruptive to that.

What's the root problem that you're trying to solve here? Can we improve things by making it clearer that the Zope projects on Launchpad aren't the primary source?

Andreas Jung (ajung) said : #2

The Zope Foundation moved a long time ago to Github and it is the desire of the current Zope team @ Github for closing this complete obsolete source on Zope.

https://github.com/zopefoundation/Zope/issues/365

github.com/zopefoundation is the canonical place for all Zope repositiories for years.

Andreas Jung (ajung) said : #3

https://github.com/zopefoundation/Zope/issues/365#issuecomment-489597724

says that there is no longer accurate or any uptodate information or resources on LP

The autor of https://github.com/zopefoundation/Zope/issues/365#issuecomment-489597724 is the current release manager of Zope.

Michael Howitz (mh-gocept) said : #4

The continued presence of Zope projects on Launchpad is a huge distraction and confuses people. The Launchpad content has been outdated and unmaintained for many years because there is no point in (and no volunteers for) maintaining two infrastructures, GitHub and Launchpad. The argument that there are open issues in various bug trackers is bogus. We had made the conscious decision many years ago to not copy every single issue over. Nothing that still exists on Launchpad is relevant or holds any value. It distracts and confuses.

Adolfo Jayme (fitojb) said : #5

Personal opinion only:

> The argument that there are open issues in various bug trackers is bogus.

No, it isn’t.

> We had made the conscious decision many years ago to not copy every single issue over

… which is disrespecting the time of the users who bothered to file bugs. It was your responsibility as a project to export the information, as others have done: GNOME migrated all of its Bugzilla to GitLab; MediaWiki did the same when it migrated to Phabricator, et cetera.

Andreas Jung (ajung) said : #6

@fitojb

There is zero need for finger pointing or raising doubts about our request.

It is up to the Zope maintainer team to decide what is best for the project and its community.

The stuff on LP is old, obsolete, outdated and irrelevant for the current Zope community and its users.

References to Zope on LP are misleading and of zero value for current Zope users.

I think it is not your job to judge about the intents and the decisions of a project like Zope.

Zope had a good time on LP for year but this time is long over and there is zero need for preserving ancient and outdated information on LP for the future.

So please proceed with the request.

Michael Howitz (mh-gocept) said : #7

Yes please proceed with the removal request.

The bugs here on LP are normally older than 5 years referencing Zope versions which are no longer supported. Some of them have been ported to Github, others are already fixed or are obsolete because the code they are referring to has been dropped from Zope. If someone really needs to access these old issues, there is archive.org: https://web.archive.org/web/20150906060636/https://bugs.launchpad.net/zope

The bigger problem is that new people are creating tickets here hoping for help, but the maintainers do not get informed because using LP was dropped by the Zope community. This is way less nice to these people than removing issues no-one cares any longer.

Launchpad Janitor (janitor) said : #8

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Andreas Jung (ajung) said : #9

Still not fixed in our sense.

Jens Vagelpohl (dataflake) said : #10

What will it take for the project to be deleted here? I think we have made it very clear that the Zope community has no interest in keeping the project here, that we have moved away years ago, and that keeping these remnants here is detrimental to our open source community.

I repeat our request: Please end this charade and delete the "zope" project.

Launchpad Janitor (janitor) said : #11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Andreas Jung (ajung) said : #12

Not expired

LeoRochael (leorochael) said : #13

> The bigger problem is that new people are creating tickets here hoping for help, but the maintainers do not get informed because using LP was dropped by the Zope community. This is way less nice to these people than removing issues no-one cares any longer.

@cjwatson, would it be possible to make it so that only issues that have a "Link to existing bug" pointing to our github can be saved? This way others wouldn't mistakenly add new issues here hoping for an answer.

This and a big disclaimer that this project remains only for tracking upstream bugs would go some way towards avoiding unwitting users pointlessly adding new issues here.

Colin Watson (cjwatson) said : #14

I've started by at least removing https://launchpad.net/zope, so the overall project group is gone. I haven't done anything with the projects under it at this point.

@leorochael: Anyone in https://launchpad.net/~zope-admin could quite easily do something along these lines (I can't). For instance, https://bugs.launchpad.net/zope2 → "Configure Bugs", and then either set up a bug tracker corresponding to the appropriate GitHub repository, or just select "Somewhere else". That way, you wouldn't get new bug reports (which people have said is the main problem here, e.g. comment #7 on this merge proposal).

If people want to remove more individual Zope-related projects on Launchpad beyond just the "zope" project group, then (a) we'll need an exact list of which ones you want to be removed, and (b) somebody really ought to do the minimal polite thing of bulk-closing bugs on these projects as Invalid before requesting their removal, so that users don't see things vanish without explanation. If nobody is willing to do (b) then I guess I can, but it would make more sense coming from a Zope maintainer.

Colin Watson (cjwatson) said : #15

Er, by "merge proposal" in my last comment I really meant "question". Doing too many things at once ...

Launchpad Janitor (janitor) said : #16

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Jens Vagelpohl (dataflake) said : #17

Since I cannot see any way to change the status on this back to an active status I have opened a new question and created a list of all those projects that...

- are tied to the different groups I am a member of
- are mentioned in the current Zope requirements-full.txt

That means the list does not include any packages that are apparently no longer used by Zope (4). I personally do not care about those enough, if someone else wants to tackle those go ahead.

Jens Vagelpohl (dataflake) said : #19

Just for completeness' sake, Colin has either deleted or marked all projects from my followup in https://answers.launchpad.net/launchpad/+question/685285 as archived. It's also no longer possible to create new trouble tickets there. This is now resolved. The only Zope-related projects not treated this way are Zope 3-only that are not used in Zope (4) anymore.