Get Involved - Githubissues

Shoalsteed commented 1 year ago

A list of specific tasks to point to when people ask how they can help. This should also be viewed as a way to onboard new long term contributors and ensure that the team has up to date learning resources for new devs.

Shoalsteed commented 1 year ago

Each task or contribution item should have:

clear scope
guides for onboarding
contact person

Shoalsteed commented 1 year ago

Support I2P Core Development The project hosts meetings on the first Tuesday of every month that are open to the community. This is a great opportunity to see what is happening with I2P core development and familiarize yourself with Roadmap tasks. Additionally, protocol development meetings take place every Tuesday and zzz's development forum is available all of the time as a place to participate in development and issues that need fixing. See the new developer's guide for how to get started.

Help translate the website and the software into your language Translators are a very important part of the project and your work is always appreciated. See the new translator's guide for details. The project also welcomes support to help keep its documentation updated. See the new translator's guide for details.

Host a Reseed Server Helping new users onto the network is a very important task, and that task is handled by reseed servers. The more reseed servers the network has, the more de-centralized and redundant its infrastructure is. Detailed instructions can be found in the reseed server page.

Create Applications For the I2P Network Write or port applications for I2P. There's some guidelines and a list of ideas on the applications page.

Test and Review Code Run test builds and provide feedback during release cycles.

Research and Security Help the project find where it may need to address a vulnerability. Study or test the code to look for vulnerabilities. Both anonymity vulnerabilities from the various threat models, and DOS and other weaknesses due to security holes, benefit from ongoing research

Shoalsteed commented 1 year ago

Realistic Example: Get contributors for Easy-Install Mac, replace the Easy-Install for Mac Lead

Contributors to the I2P Easy-Install for Mac. Contributors who demonstrate responsibility by virtue of their contributions could eventually be considered for maintainership of the bundle, if they are willing to also become the signer of the bundle.

Experience in Java Development

Experience in Apple Application Development

Should be able to complete: https://github.com/i2p/i2p-jpackage-mac/blob/master/BUILD.md successfully

Contact us by filing issues against https://i2pgit.org/i2p-hackers/i2p-jpackage-mac

Yes - this includes scope , guidance for a new contributor and a specific task.

Shoalsteed commented 1 year ago

Support I2P Core Development The project hosts meetings on the first Tuesday of every month that are open to the community. This is a great opportunity to see what is happening with I2P core development and familiarize yourself with Roadmap tasks. Additionally, protocol development meetings take place every Tuesday and zzz's development forum is available all of the time as a place to participate in development and issues that need fixing. See the new developer's guide for how to get started.

Help translate the website and the software into your language Translators are a very important part of the project and your work is always appreciated. See the new translator's guide for details. The project also welcomes support to help keep its documentation updated. See the new translator's guide for details.

Host a Reseed Server Helping new users onto the network is a very important task, and that task is handled by reseed servers. The more reseed servers the network has, the more de-centralized and redundant its infrastructure is. Detailed instructions can be found in the reseed server page.

Create Applications For the I2P Network Write or port applications for I2P. There's some guidelines and a list of ideas on the applications page.

Test and Review Code Run test builds and provide feedback during release cycles.

Research and Security Help the project find where it may need to address a vulnerability. Study or test the code to look for vulnerabilities. Both anonymity vulnerabilities from the various threat models, and DOS and other weaknesses due to security holes, benefit from ongoing research

THIS is what is salvageable from the existing page, however the copy needs to be improved.

Shoalsteed commented 1 year ago

Participate In Maintaining I2P Development

Experience in Java Development
- Experience in Windows and macOS Application Development
- Participate in testing during our release cycle
- Should be able to complete: https://github.com/i2p/i2p-jpackage-mac/blob/master/BUILD.md successfully
- Contact us by filing issues against
- https://i2pgit.org/i2p-hackers/i2p-jpackage-mac
- https://i2pgit.org/i2p-hackers/i2p.firefox

Contributors should be able to participate in I2P Dev monthly meetings.

eyedeekay commented 1 year ago

Much better, but it should also have http://i2pgit.org/i2p-hackers/i2p.firefox in contact filing issues against if we're doing both Windows and OSX in this entry

Shoalsteed commented 1 year ago

My next question is about the reseed process. As I understand it, we have no formal meetings for reseed operators. Aside from the docs on the site, is there a place for reseed operators to connect?

Shoalsteed commented 1 year ago

Much better, but it should also have http://i2pgit.org/i2p-hackers/i2p.firefox in contact filing issues against if we're doing both Windows and OSX in this entry

and the build linked - is that the only resource required?

Shoalsteed commented 1 year ago

I am also going to include my own asks for the Secure Design Collective

eyedeekay commented 1 year ago

No the Windows one is https://github.com/i2p/i2p.firefox/blob/master/README.md under "End-to-End Windows Build Process using WSL"

eyedeekay commented 1 year ago

And it's way harder than the Mac version of the same thing unfortunately

eyedeekay commented 1 year ago

Contributors who want to work on the I2P code should be able to connect to Irc2P and should join the #i2p-dev channel, which is moderated. They must register a nickname on Irc2P to use #i2p-dev.
They should be familiar with the basics of using SSH and be able to sign and encrypt email with GPG
Git experience is helpful but not required

re: top one, the guide I used was here: http://deadlytechnology.com/linux/irc-on-ubuntu/ or we could write our own

Shoalsteed commented 1 year ago

http://deadlytechnology.com/linux/irc-on-ubuntu/

the link goes to a suspended page for me - is it for how to register a nick name?

eyedeekay commented 1 year ago

Shoot, I just pulled it out of my bookmarks and didn't check if it was still up

eyedeekay commented 1 year ago

Yes it's for registering a nick

eyedeekay commented 1 year ago

https://libera.chat/guides/registration

Shoalsteed commented 1 year ago

https://libera.chat/guides/registration

Is there a place to register a nick in irc2p?

eyedeekay commented 1 year ago

https://libera.chat/guides/registration

Is there a place to register a nick in irc2p?

Yes it works the same way as the other nickservers, you send a message to NickServe containing the name and password

Shoalsteed commented 1 year ago

file with updates posted to Gitlab for review.

Shoalsteed / I2P-Secure-Design-Collective

Get Involved #66