Authorization to transfer to backstage community repository

[fjudith]

Hello !

We are maintaining internally a fork of this plugin for year. We managed to follow up with the framework updates along with the support of the Kubernetes permissions (i.e. kubernetes.cluster.read, kubernetes.resource.read).

Could you please provide us the authorization to transition the code to the https://github.com/backstage/community-plugins so this plugin can benefit from regular updates ?

[casibbald]

surely you can just fork the repo or contribute and push your changs to this repo?

[stefanprodan]

I think the official community-plugins is the best place for this project to continue.

~Sadly Weaveworks didn't setup a license for this project, but given that the company has shutdown no one should be able to raise IP claims to it.~

[bigkevmcd]

The plugin does have a licence https://github.com/weaveworks/weaveworks-backstage/blob/main/plugins/backstage-plugin-flux/LICENSE

[bigkevmcd]

And I'd be happy for it to go under the community-plugins too

[stefanprodan]

The plugin does have a licence https://github.com/weaveworks/weaveworks-backstage/blob/main/plugins/backstage-plugin-flux/LICENSE

I guess the fork is for the contents of that dir so should be fine to move it given that it's an OSS license.

[monadic]

Mpl2 is asl-compatible. And you can fork, or use asl2 for new code.

[fjudith]

Thank you all for feedback. Regarding the license, the community-plugins repo is managed by the CNCF, i guess i will have to move to Apache 2.0.

[fjudith]

The issue has been created the official community-plugins. Maintainers may ask you to confirm the transfer and archive this repo.

[casibbald]

Please kindly update the issue with links for where to redirect traffic, or even better, put in a PR to that effect, and I will look at it and approve it!

On 27 Jun 2025, at 21:21, Florian JUDITH @.***> wrote:

fjudith left a comment (weaveworks/weaveworks-backstage#71) https://github.com/weaveworks/weaveworks-backstage/issues/71#issuecomment-3014012697 The issue has been created the official community-plugins https://github.com/backstage/community-plugins. Maintainers may ask you to confirm the transfer and archive this repo.

— Reply to this email directly, view it on GitHub https://github.com/weaveworks/weaveworks-backstage/issues/71#issuecomment-3014012697, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA6C335DJFBOC2RL7ZMV6L3FWDTPAVCNFSM6AAAAACAG453OKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMJUGAYTENRZG4. You are receiving this because you commented.

[fjudith]

Hello team,

The source code of the flux plugin has been reviewed and merged in the backstage/community-plugins repository.

I have submitted the pull request #72 to add the deprecation notice to the README.

Next steps

• [ ] Archive the weaveworks/weaveworks-backstage repository
• [ ] Deprecate the @weaveworksoss/backstage-plugin-flux package published on NPM

npm deprecate \
  @backstage-community/plugin-flux@"<= 0.8.5" \
  "This package has been moved to the backstage/community-plugins repository. You should migrate to using @backstage-community/plugin-flux instead."

[stefanprodan]

@bigkevmcd do you have access to the NPM package to run the deprecate command and archive this repo? I do not

[bigkevmcd]

@bigkevmcd do you have access to the NPM package to run the deprecate command and archive this repo? I do not

I don't, I am fairly sure the creds were stored in our shared storage...which I doubt anybody still has access to?