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

Syft Quickstart Curriculum for Deep Learning Enthusiasts #52

Open
iamtrask opened this issue Sep 7, 2017 · 2 comments
Open

Syft Quickstart Curriculum for Deep Learning Enthusiasts #52

iamtrask opened this issue Sep 7, 2017 · 2 comments

Comments

@iamtrask
Copy link
Owner

iamtrask commented Sep 7, 2017

User Story A: As a Deep Learning enthusiast, I want to hear about OpenMined in one of my Deep Learning Communities in such a way that I land on a page of the project that cators to my interests, explains why I might be interested in the project, and leads me through a curriculum of information that takes me through my first Pull Request into PySyft or syft.js. The curriculum should both serve as a means of conveying information and should also keep me engaged and grow my excitement around what the OpenMined Community is building.

Acceptance Criteria:

  1. A Markdown file in Docs/curriculum should exist specifically for on-boarding individuals into the PySyft and syft.js projects.
  2. BEGINNING: The markdown file of (1) should contain a Step 1, Step 2, Step 3 style list of pointers to various pieces of OpenMined documentation and tutorials that someone onboarding onto the Sonar Project would require to be able to know about this project. This includes ALL demos of the capabilities of the technology (whether just notebooks or in youtube videos on our channel). This Markdown file should be the appropriate next step after finishing the General "Contributor Quickstart Guide".
  3. MIDDLE: along the way, there should include pointers to various tutorials external to OpenMined (such as deeplearning.ai or fast.ai courses) so that people can know where to acquire the skills necessary to contribute to PySyft or Syft.js if they do not already have them.
  4. END: This markdown file should finish with steps referring to an Issues page (with appropriate filters) for identifying Issues that are relevant for new contributors to be able to pick up.
  5. SUCCESS CRITERIA: While (1-4) are suggestions... the true goal here is to eliminate the need for someone to resort to Slack to be able to merge their first PR to Sonar or PySonar
@momonala
Copy link

momonala commented Oct 8, 2017

To clarify - The request here is two different .MD files, right? One for PySyft and one for syft.js? I start with the PySyft one if so

@shshnkg
Copy link

shshnkg commented Oct 9, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants