Vulnerable dependencies

[leandro-lucarella-sociomantic]

See https://github.com/sociomantic-tsunami/flounder/network/alerts

Please update.

[leandro-lucarella-sociomantic]

It looks like this project is abandoned. Shall we archive it to make that clear for the general public?

[mousemke]

i have:

• a git fork
• the keys to the npm repo
• the keys to the slack community

so it does not bother me one way or another whether the Soc side of things stays active (Though i've enjoy working with Soc DH, it does appear abandoned from that side)

as we use it in some areas in Zalando i will continue to maintain and (occasionally) update my branch

[leandro-lucarella-sociomantic]

If we don't use it internally, I would also be open to transfer the repo to another organization if you plan to keep maintaining it.

[damian-rodriguez-sociomantic]

@leandro-lucarella-sociomantic we are still using an old version of flounder in some parts of the UI, but eventually it will be removed, and yes, the development/maintenance from our side is abandoned.

[leandro-lucarella-sociomantic]

@damian-rodriguez-sociomantic so a transfer/archival should be OK as long as:

• the old versions are still provided by the new maintainer if we transfer it
• the old versions can be still checked out via git if we archive it

Right?

[damian-rodriguez-sociomantic]

@leandro-lucarella-sociomantic yes, it should be fine

[leandro-lucarella-sociomantic]

@mousemke can you confirm if you are interested in getting this repo transferred to you/Zalando? If you are then I need to find out if I can actually do it (at the Dunnhumby side). Otherwise we will archive it.

[mousemke]

confirmed

[leandro-lucarella-sociomantic]

We will move forward with the transfer, and then we fork it from you in our org to make sure we can access the code as long as we need. @mousemke should we transfer to https://github.com/zalando or to https://github.com/mousemke?

[mousemke]

mousemke. thanks!

[leandro-lucarella-sociomantic]

You should rename remove your fork then:

The target account must not have a repository with the same name, or a fork in the same network.

https://help.github.com/en/articles/transferring-a-repository

All users of this repo should also read that whole guide, as they should update their git URLs in their clones for example.

[leandro-lucarella-sociomantic]

If you are uncomfortable with that we could also just add a note to the README saying the project moved and archive this one.

[mousemke]

renamed

[mousemke]

ah. saw the edit. one sec

[mousemke]

removed

[leandro-lucarella-sociomantic]

You can only transfer a repository from an organization to yourself at this time

Really, GitHub? 🙄

[leandro-lucarella-sociomantic]

Is not even mentioned in the guide, so I wonder if it is a temporary limitation or an undocumented limitation. I could try asking to GH support, I'll try.

[mousemke]

lol it's always something

[leandro-lucarella-sociomantic]

OK, GitHub never got back to me so I went through the triangle. You should get a transfer request from my user.

[leandro-lucarella-sociomantic]

OK, just for the records, transfer done. This issue is now on your hands @mousemke :)

[mousemke]

🥳 - 🐭 On April 11, 2019 at 16:29 GMT, Leandro Lucarella <[email protected]> wrote: OK, just for the records, transfer done. This issue is now on your hands [@mousemke](https://github.com/mousemke) :) — You are receiving this because you were mentioned. Reply to this email directly, [view it on GitHub](#217 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/ABaV6Cwp4q2LBJT-MdSTM_-jLU0I8r8Gks5vf2LPgaJpZM4a5-yy).