spyscope

[slipset]

dgrnbrg/spyscope#26
So the question is if @randomizedthinking or @dgrnbrg would be willing to transfer the project?

[dgrnbrg]

I would be open to this. What does it take?

[slipset]

Doesn't take much. You transfer the repo to clj-commons, we maintain it.
If you also add clj-commons to the group that owns spyscope on clojars, we can continue to publish under the same artefact id. Otherwise, we'll change it to clj-commons/spyscope.

[randomizedthinking]

It sounds good. @dgrnbrg Can you add me to the maintainer of the project. I think we can keep the artifact id for now... less interruption to users.

…

On Mon, Jan 21, 2019 at 7:57 AM Erik Assum ***@***.***> wrote: Doesn't take much. You transfer the repo to clj-commons, we maintain it. If you also add clj-commons to the group that owns spyscope on clojars, we can continue to publish under the same artefact id. Otherwise, we'll change it to clj-commons/spyscope. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFCeZn-AOao4CKdQ04rrVGS4ccn2hMI-ks5vFeNXgaJpZM4aKTbn> .

[slipset]

I've added you both as members of clj-commons. You should then be able to transfer spyscope to us.

[buzzdan]

Any updates on this issue?

[randomizedthinking]

@dgrnbrg Can you please add me as a collaborator to the original repository then I can transfer the repo to clj-commons? Or you can do the transfer by yourself.

[randomizedthinking]

Clone the repo at clj-commons. Since @dgrnbrg already agreed, and it requires no action from him assuming he is busy. Close the issue now.