Notice: Weaveworks git repo transitioning to Community Project

[asaf400]

Weaveworks and now it's domain has been closed since February 2024,

The project will be moving to a new domain in the near future!

[casibbald]

We are in the process of setting up the domain and the git organisation using a community-driven approach. We have got FOSSA and other security concerns back up and running and @asaf400 we look forward to seeing your PR’s and code contrinutions to the project.

…

On 11 Dec 2024, at 17:58, Asaf Levy ***@***.***> wrote: Weaveworks and now it's domain has been closed since February 2024, and yet, non of the repos, or issues mention the future of this org on github, who is currently maintaining it, and same goes for Flux: https://www.linkedin.com/posts/richardsonalexis_hi-everyone-i-am-very-sad-to-announce-activity-7160295096825860096-ZS67/ #4235 <#4235> There's no public notice for the current state, as a devops engineer which previously used fluxcd and weave-gitops in the past, There are big questions as to the safety of using this product, someone can 'easily' do an hostile takeover of this org and integrate malicious code into future update, essentially using this repo and org as supply-chain attack surface.. I would expect some explanation on the README.md of all currently still active repos under this org to address these concerns, and maybe also poke the fluxcd blog to acknowledge the now defunct weaveworks, since, they also still have links and testimonials on their main site.. P.S I've looked through the issues, to find some acknowledgment, but all I have found are issues like #4235 <#4235> and not something broad.. — Reply to this email directly, view it on GitHub <#4243>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA6C32UB7QU6WUFOSPUI232FBOJFAVCNFSM6AAAAABTNZ3WZ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSG4ZTGMZWGE2DCNA>. You are receiving this because you are subscribed to this thread.