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

[Feature Request] Guide for New Students to Contribute to Open Source #65

Closed
lazyplatypus opened this issue Jan 4, 2021 · 9 comments
Closed

Comments

@lazyplatypus
Copy link
Member

Is your proposal related to a problem?
Students new to programming aren't given the resources to contribute to the repo.

Describe the solution you'd like
Add guides that teach the fundamentals of open source.

@project-bot project-bot bot added this to To do in Bit Project Jan 4, 2021
@lazyplatypus lazyplatypus changed the title [Feature Request] [Feature Request] Guide for New Students to Contribute to Open Source Jan 4, 2021
@lazyplatypus
Copy link
Member Author

How to open a pull request, open an issue, conduct a code review.

@MinyMeep1
Copy link
Collaborator

MinyMeep1 commented Jan 4, 2021

A guide on how to work with markdown. During my task, I wasn't sure what the three ### was and when I look through the edits via serverless I saw that ### meant heading 3. Maybe if we had a markdown documentation students or open contributors would know how to properly use markdown.

@lazyplatypus
Copy link
Member Author

@MinyMeep1 we are going to create a new document targeted at students who want to make their first PR into our repo. This will have a checklist of things they should do/know before they tackle a particular issue.

For example,
Knowing how

  • PRs
  • Github Issues
  • Markdown
  • Code Reviews
  • Other aspects of Github
    works is crucial to the success of the student.

In addition, we should have more instructions on how they can start tackling a particular issue. For example, let's say that step 4 on a particular learning lab doesn't go enough in depth about a particular topic. Students should try the learning lab from step 1 all the way to step 4 before trying to fix the issue.

Also, students should be encouraged to open issues for other issues they discover while they are working on their own task.

@shreythecray
Copy link
Contributor

Make contributing more interesting, friendly and eye-catching. Maybe gamify it so we can have challenges for the number of PR's that students make and those who reach certain levels get badges or swag?

@lazyplatypus
Copy link
Member Author

@shreythecray maybe we should add something like -> https://allcontributors.org/ to the repo?

@emsesc
Copy link
Collaborator

emsesc commented Jan 4, 2021

Emphasize the importance of contributing and how it helps students (I think @MinyMeep1 brought this up before)

@danzelo1
Copy link
Contributor

danzelo1 commented Jan 4, 2021

I think the points @lazyplatypus made are really great and will help students a lot. Going off of that, I think it’s important that we make these resources quick and easy to access and follow by linking step-by-step instructions to the notion page associated with each BitCamp, or whatever page the code and homework’s will be linked on.

To encourage them to contribute, maybe we could try to get students to share their work every week. I’m not sure if this would be possible with the streaming platforms we’re using, but maybe we could get a student to explain the homework every week instead of the mentors going over it and those who volunteer will get some reward like @shreythecray said.

@MinyMeep1
Copy link
Collaborator

We need to as well include how to do "Gitignore"

@MinyMeep1
Copy link
Collaborator

I just wanted to get an opinion on it right now. I'm still fixing the kinks but this is what I have now and I'll be adding more sections like "What is a GitHub issue"

Bit Project automation moved this from To do to Done Jan 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Bit Project
  
Done
Development

Successfully merging a pull request may close this issue.

5 participants