-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Semaphore Boilerplate] Issue 3: Create the Code of conduct template and Contributing files #3
Comments
I’d like to resolve this. |
I would like to work on this issue |
Would love to tackle this! |
Can I attempt this issue? |
May I be assigned to this? I love to take it making it my first contribution to the community |
i will love to be assigned this issue. please assign me |
Could I take a shot at this? |
Hello can i be assigned this issue, i am a new contributor and i would love to work on this , my ETA is >12 Hours and ill create a draft PR in 10 hours time. Thank you for this opportunity. :) |
Can I attempt this issue? |
Hello can I be assigned this please? I am a blockchain developer and I'm also good at documentations. Below are some of the documentations I've done that were merged: dojoengine/book#308, Please I’m ready to work, assign me please. |
I’d like to resolve this. |
May I try my hand at this? |
hey sir I'd like to handle this task. |
i'm a technical writer, frontend dev and a blockchain dev |
Hello! My name is t0fudev and I'm currently a computer science student and also a web3 developer. I'm fully confident on working on this issue since I have experience on working this type of files and also I had contributed on last OD Hack to this incredible project. Sincerely, t0fudev ETA: 1 day |
I'd love to give this a go. |
Description:
To foster a welcoming and inclusive environment, the Semaphore Boilerplate project needs a Code of Conduct and a comprehensive Contributing file. These documents will ensure that contributors understand the expectations for participation and the processes for making contributions.
The text was updated successfully, but these errors were encountered: