Docs say this is still a proof of concept

[davidben]

The documentation for rules_license says:

Proof of concept. License restriction.

https://bazelbuild.github.io/rules_license/latest.html

That seems to suggest this is not yet ready for general use, but Bazel's documentation already suggests using it.
https://bazel.build/reference/be/functions#package.default_package_metadata

Is the documentation out-of-date, or is this package not yet ready?

[jcecil]

CC @aiuto

[alexeagle]

See #152

[tonyaiuto]

The docs are out of date, and there is a lot of work to be done. We're doing a BOF at BazelCon in October, where we will do some direction setting.

[davidben]

Can the phrase "proof of concept" be removed before then? We were asked to adopt this project but the documentation made it extremely difficult to have confidence that we could safely do so.

[jcecil]

I wasn't able to attend BazelCon unfortunately (I look forward to watching the vods later), but I didn't see any discussion topics related to licenses. Was this discussed?

I just want to confirm that rules_license is the way forward. My project has deps that use the old and new way of defining licenses, and my strategy for handling it depends on this decision. Should I work on updating my dependencies to use the new version, or should I try to make my project support deps that use either version?

[davidben]

Any news on this?

[igormcoelho]

Since version was bumped from
0.x to 1.0.0, I assume its not a proof of concept anymore.. right? Can this phrase be removed from readme? It seems usable as is.

[alexeagle]

@igormcoelho in what way were you able to use it? My understanding is that 1.0.0 was premature, and this module is likely abandoned. See the issue filed immediately before this one #152

[davidben]

That is... unfortunate. BoringSSL started using this because some downstream project told us it was required. I was led to believe this was the new preference for Bazel modules. Is that no longer the case? Should uses be reverted?

[tonyaiuto]

We've moved all new development to https://github.com/bazel-contrib/supply-chain.
The plan is not to invalidate existing licenese() declarations, but we have not worked out the exact migration path where old and new repos are essentially equivalent. There is no reason to revert. When we get the migration path proved out, we'll start hunting for the repos to send PRs to.