Skip to content

Provide a CONTRIBUTING.md guideline #56

@bbraunstein

Description

@bbraunstein

I (and I'm sure others) would like to contribute to the permit-golang repository. There isn't clarity on how to implement new features in a predictable and consistent way. For example, there are disparities between the exposed REST API and the SDK. The SDK does not interact with certain endpoints and/or the generated models do not match the response objects from the API. Given that the models and other resources are generated automatically using openapi-generator.tech, no documentation exists for how a new contributor could generate/update these file. These disparities affect other integrations, such as the terraform-permit-io provider, which is very immature and not as robust as other providers on the market.

A new contributor that is interested in submitting a PR would quickly be overwhelmed and discouraged from improving PermitIO's open-source tooling. Having high-level contribution guidelines would make the repository more open and inviting to new contributors and foster better collaboration.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requesthelp wantedExtra attention is needed

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions