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

[Semaphore Boilerplate] Issue 3: Create the Code of conduct template and Contributing files #3

Closed
evgongora opened this issue Nov 21, 2024 · 16 comments · Fixed by #5
Closed
Assignees
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers ODHack10

Comments

@evgongora
Copy link
Collaborator

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.

@evgongora evgongora added documentation Improvements or additions to documentation good first issue Good for newcomers ODHack10 labels Nov 21, 2024
@evgongora evgongora changed the title [Semaphore Boilerplate] Issue 2: Create the Code of conduct template and Contributing files [Semaphore Boilerplate] Issue 3: Create the Code of conduct template and Contributing files Nov 21, 2024
@Immanuelolivia1
Copy link

I’d like to resolve this.
To organise the smart contracts, I'll create a contracts folder with subfolders for each contract. then place the source files (lib.rs and test.rs) in a src directory within each subfolder, along with a Cargo.toml file for dependencies. Lastly i'll update the workspace in the root Cargo.toml. This keeps the project modular and Soroban-compliant.

@BrunoAmbricca
Copy link

I would like to work on this issue

@NueloSE
Copy link
Contributor

NueloSE commented Nov 21, 2024

Would love to tackle this!
Am a frontend dev and an experienced technical writer.
previous merge technical doc:

@mimisavage
Copy link

Can I attempt this issue?

@Joe-joe25
Copy link

May I be assigned to this? I love to take it making it my first contribution to the community

@caxtonacollins
Copy link

i will love to be assigned this issue. please assign me

@Benjtalkshow
Copy link

Could I take a shot at this?

@akintewe
Copy link

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. :)

@Michaelkingsdev
Copy link

Can I attempt this issue?

@od-hunter
Copy link

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,
keep-starknet-strange/joyboy#143,
Scaffold-Stark/ss2-docs#31,
horuslabsio/Starknet-Scaffold#94,
Hyle-org/examples#15.

Please I’m ready to work, assign me please.

@petersdt
Copy link

I’d like to resolve this.

@ryzen-xp
Copy link

May I try my hand at this?

@vestor-dev
Copy link

hey sir I'd like to handle this task.
i'm a frontend developer and a blockchain dev
i would really love to contribute to your project
please kindly assign :)

@martinvibes
Copy link

martinvibes commented Nov 21, 2024

i'm a technical writer, frontend dev and a blockchain dev
please kindly assign :)

@t0fudev
Copy link

t0fudev commented Nov 21, 2024

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.
I'm eager to continue contributing to this amazing project.

Sincerely, t0fudev

ETA: 1 day

@emarc99
Copy link

emarc99 commented Nov 22, 2024

I'd love to give this a go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers ODHack10
Projects
None yet
Development

Successfully merging a pull request may close this issue.