Hi stackers & neutrinos, I understand the need to adapt the project status to the lack of activity on the project in the past year. During this time, my time as a reviewer, preventing the code submitted to be merged, has been taken by other activites (still OpenStack related!). Having been at the origin of the project, I have to apologize for the lack of communication of where we were about this project. My apologies for that. We still would like to have a place to let the proposal exit, code be reviewed and tested. Hosting under "x/" would work for us. Hope that this can work like this... Thanks! -Thomas Andreas Jaeger :

On 15/11/2019 09.56, Slawek Kaplonski wrote:

...

Hi neutrinos,

As we discussed during the Shanghai PTG I just proposed changes to move neutron-interconnection project out of stadium to "x/" namespace. So it will not be official neutron project anymore after those changes. Patches for that are in [1] and [2]

I also proposed to remove neutron-interconnection api-ref from neutron-lib. Patch is here [3]. Please review it :)

[1] https://review.opendev.org/#/c/694478/ [2] https://review.opendev.org/#/c/694480/ [3] https://review.opendev.org/#/c/694466/

Looking at https://review.opendev.org/#/q/project:openstack/neutron-interconnection

I suggest to retire only with those few changes to the repo - and nothing in the last few months.

Or is there anybody committing to continue the work?

We can also retire now - and create again in the "x/" namespace if interest suddenly arises. But let's not move repos that are de-facto dead around,

Andreas

_________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

On 2019-11-16 17:52:46 +0100 (+0100), Andreas Jaeger wrote: [...]

So, we retire the repo completely (with the existing changes) - and you can anytime push up a new change to create the repo in the "x" namespace import the content (minus the retirement change) into it... [...]

Even easier is probably to import it all (just set the upstream import to the opendev.org clone URL for the original project), and then as part of the first change to the new project revert the retirement commit. That doesn't require pushing a temporary copy of the repository anywhere for import. -- Jeremy Stanley