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
Move project to cpplint/cpplint #31
Comments
Seconded! |
So I for one am happy to add @mattyclarkson to the pypi list of people with rights to make releases. An independent github organisation might be overkill for now. My personal vision is for this to remain a close siamese twin of the google upstream, only adding Python3 compatibility and very tiny changes. |
@tkruse, I think it makes the project feel more of a community project rather than one persons project. I don't particularly want to be the sole maintainer but am happy to share the load with a few maintainers. I will generally be available to work on this though as we use it at work. I agree that we should keep it close to the upstream |
@tkruse is right -- I'm no longer using cpplint at work so I haven't had the motivation to work on it. Would be great if you'd like to take over, @mattyclarkson. If you'll let me know what your username on pypi is, I'll add you as an owner. And I will update theandrewdavis/cpplint to point to wherever y'all decide cpplint should live (cpplint/cpplint or mattyclarkson/cpplint) |
@theandrewdavis, my user name on PyPi is I'm happy to keep maintaining it whilst we use it at work. Would be nice if a few of you are around to bounce ideas/PRs off. |
@mattyclarkson No need to involve GitHub staff. Create the organization, then give @theandrewdavis admin privileges in the organization. He can then trivially transfer the repo to the organization via The Danger Zone™ options, |
Full details can be found here: |
OK have made the organisation. https://github.com/cpplint How should be part of the organisation team? |
That was simple enough. You're on the pypi now, @mattyclarkson, and the repo is transferred. |
Rock on 🤘 |
Add support for specifying no lint on multiple lines using a NOLINTBEGIN comment to start the block and one or more NOLINTEND comments. Multiple NOLINTBEGIN comments can stack different categories and the same number NOLINTEND comments need to be used to re-enable the category. This is similar to the clang-tidy NOLINTBEGIN/END feature. Also, add support for specifying multiple categories in a single NOLINT comment using commas as separators.
Add support for specifying no lint on multiple lines using a NOLINTBEGIN comment to start the block and one or more NOLINTEND comments. Multiple NOLINTBEGIN comments can stack different categories and the same number NOLINTEND comments need to be used to re-enable the category. This is similar to the clang-tidy NOLINTBEGIN/END feature. Also, add support for specifying multiple categories in a single NOLINT comment using commas as separators.
If we move the project to a organisation we can have multiple collaborators on the project and share the maintenance. We use this version of
cpplint
internally at work and would happily spend time maintaining the project, issues and PRs.The text was updated successfully, but these errors were encountered: