Shall I move all of the issues here to ipfs/infra and archive this repo?

[daviddias]

@eefahy what do you think?

[eefahy]

Whoa. There are a bunch of issues here. I think it would be good to go through them to ensure

1. they are appropriate for ipfs/infra
2. if they are still needed or not already represented in ipfs/infra or protocol/infra

I'm missing some context for some of the issues here so I wonder if @victorb would be able to help out?

[daviddias]

@eefahy makes sense. What about going through them together, closing the already done and labeling the ones we believe that are good to move to ipfs/infra so that you can review and do the final move?

[daviddias]

Gave a first pass -- https://github.com/ipfs/dev-team-enablement/issues?q=is%3Aissue+is%3Aopen+label%3A%22move+to+ipfs%2Finfra%22 --, unlabel the ones you disagree :)

[momack2]

Moving issues to a new repo will break any existing links...

…

On Tue, Dec 4, 2018 at 1:03 AM David Dias ***@***.***> wrote: Gave a first pass -- https://github.com/ipfs/dev-team-enablement/issues?q=is%3Aissue+is%3Aopen+label%3A%22move+to+ipfs%2Finfra%22 --, unlabel the ones you disagree :) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#166 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlwF3H0YG0Bg1qkkTFhC7ig345_XNntks5u1jpbgaJpZM4Y7YOc> .

[daviddias]

@momack2 it doesn't. Github is pretty good with the redirects :)

[momack2]

Really? Impressive. Then why not for renames??

…

On Tue, Dec 4, 2018 at 8:48 AM David Dias ***@***.***> wrote: @momack2 <https://github.com/momack2> it doesn't. Github is pretty good with the redirects :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#166 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAlwF4h-lySsk_klMVxblE_mBBB8xJ3Zks5u1qdDgaJpZM4Y7YOc> .

[eefahy]

Most of those issues I think would be better tracked in https://github.com/ipfs/jenkins - which seems to be anything already tags with CI/* Does that seem correct to you?

[victorb]

A while ago when we decided that infra team would take ownership of CI, I went through all issues and labelled them according to what subject they belong to. The ones we discussed that should be moved are the following:

• CI/Bugs
• CI/Service
• Releases

The one that might be infra, but should probably be the dev-teams themselves is CI/Pipelines, which is about the scriptable pipelines themselves.

[eefahy]

@victorb ah ok, cool. But why not have those issues in https://github.com/ipfs/jenkins ?