Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of name com_github_nelhage_rules_boost and name it only rules_boost #572

Open
Vertexwahn opened this issue Jun 10, 2024 · 4 comments

Comments

@Vertexwahn
Copy link
Collaborator

We should get rid of the name com_github_nelhage_rules_boost and name it only rules_boost

@nelhage
Copy link
Owner

nelhage commented Jun 10, 2024

I'm 👍 to this change. It's also the case that I have less time for rules_boost these days, and you and @cpsauer have been taking on more of the maintenance, so I wonder if it makes sense to coincide a rename with a move of the repository to a new or existing organization. I don't have a sense of whether there's a place in the existing ecosystem that might want to accept it or if just creating a rules_boost organization or similar might make sense.

@Vertexwahn
Copy link
Collaborator Author

Vertexwahn commented Jun 10, 2024

@zaucy Can we use your "Bazel Boost" orga for this?

@zaucy
Copy link

zaucy commented Jun 10, 2024

rules_boost and bazelboost are different approaches to utilising boost with bazel and including rules_boost under bazelboost may be confusing.

I think I'd prefer to keep bazelboost focused as a fork of "modular boost" with bazel support instead of a general org.

@Vertexwahn
Copy link
Collaborator Author

Vertexwahn commented Jun 10, 2024

@zaucy Makes sense.

Other idea: We can move it to Bazel Contrib orga

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants