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

Offering help #212

Open
masterT opened this issue Feb 29, 2024 · 2 comments
Open

Offering help #212

masterT opened this issue Feb 29, 2024 · 2 comments

Comments

@masterT
Copy link
Contributor

masterT commented Feb 29, 2024

Hello @hassox, @josevalim, @jsmestad, @whithub,

I've noticed that the repository has seen limited activity in recent years, particularly in terms of issue responses and PR merges.

Recognizing the gem's importance and potential, I am eager to contribute my time to help revitalize the project. Although my direct experience with warden is relatively recent, my extensive background in Ruby development has given me the skills to make significant contributions.

I am fully committed to respecting the project's guidelines, collaborating with the existing team, and contributing to warden's future success. I look forward to the possibility of working together to enhance warden for the community.

Thank you for considering my offer. I am eager to contribute to the warden community and help in any way I can. 🙂

@jsmestad
Copy link
Collaborator

jsmestad commented Mar 1, 2024

Happy to have a helping hand. Keep in mind the lack of contributions means the library is stable. Many changes that've been proposed have more risk than reward. Warden is widely used and any API change can have big impact so we've favored a conservative stance when it comes to merging things in.

If you'd like to help, the biggest area is ensuring any contributions are sufficiently tested and backtested with old versions of Rails/Rack. If you want to start with ensuring contributions are to that standard, I'm happy to merge them. Most of the core contributors just lack time to bolster contributions to a point that they can be merged.

@masterT
Copy link
Contributor Author

masterT commented Mar 1, 2024

I understand the importance of maintaining the library's stability and the cautious approach towards changes and potential impact.

Could you please guide me on the process of getting started with this? Are there specific contributions or areas within the project that need attention regarding testing or compatibility?

I'm looking forward to contributing!

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

2 participants