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

CONTRIBUTING.md: how to progress through issues according to complexity #2760

Closed
7 tasks done
JessicaLucindaCheng opened this issue Feb 9, 2022 · 3 comments · Fixed by #3007
Closed
7 tasks done
Assignees
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less

Comments

@JessicaLucindaCheng
Copy link
Member

JessicaLucindaCheng commented Feb 9, 2022

Overview

As a developer on the team, I want to know how to progress through issues according to its complexity so I know what issue I am eligible to work on next. For this issue, we will update the CONTRIBUTING.md file with information about issue progression based on complexity.

Action Items

- Progress through issues with increasing complexity in the following order:
  - Good first issue
  - Good second issue
  - Small 
  - Medium 
  - Large
    - The reasons for this progression are:
      - The issues start out as being prescriptive and become less so as you gain more experience by working through increasingly complex issues.
      - We are trying to teach you the team methodology through the issues themselves.
      - It ensures you understand what we expect and the quality of contributions.
  • To see the visual changes for the CONTRIBUTING.md and make sure the changes look good:
    • Push the changes to your remote forked repo's topic branch
    • Go to your remote forked repo on GitHub
    • Switch to your topic branch
    • Click on the CONTRIBUTING.md file
    • On the upper right, click on "Display the rendered blob" to see what your changes look like. Here is an image of what the "Display the rendered blob" button looks like:
      image

Resources/Instructions

@JessicaLucindaCheng JessicaLucindaCheng added role: front end Tasks for front end developers role: back end/devOps Tasks for back-end developers Complexity: Medium time sensitive Needs to be worked on by a particular timeframe Feature: Onboarding/Contributing.md Ready for Prioritization size: 1pt Can be done in 4-6 hours labels Feb 9, 2022
@github-actions

This comment was marked as outdated.

@JessicaLucindaCheng JessicaLucindaCheng changed the title Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) DRAFT: Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) Feb 10, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title DRAFT: Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) DRAFT: Update Feb 10, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title DRAFT: Update Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) Feb 10, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) DRAFT: Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) Feb 10, 2022
@JessicaLucindaCheng JessicaLucindaCheng added size: 0.5pt Can be done in 3 hours or less and removed time sensitive Needs to be worked on by a particular timeframe size: 1pt Can be done in 4-6 hours labels Mar 12, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title DRAFT: Update how to progress through issues according to size (good first issue -> good second issue -> small -> medium -> large) DRAFT: Update Contributing.md with how to progress through issues according to complexity Mar 12, 2022
@JessicaLucindaCheng JessicaLucindaCheng added Complexity: Small Take this type of issues after the successful merge of your second good first issue and removed Complexity: Medium labels Mar 12, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title DRAFT: Update Contributing.md with how to progress through issues according to complexity DRAFT: Update CONTRIBUTING.md with how to progress through issues according to complexity Mar 12, 2022
@JessicaLucindaCheng JessicaLucindaCheng changed the title DRAFT: Update CONTRIBUTING.md with how to progress through issues according to complexity Update CONTRIBUTING.md with how to progress through issues according to complexity Mar 12, 2022
@ExperimentsInHonesty ExperimentsInHonesty changed the title Update CONTRIBUTING.md with how to progress through issues according to complexity CONTRIBUTING.md: how to progress through issues according to complexity Mar 13, 2022
@Jaretzbalba Jaretzbalba self-assigned this Mar 23, 2022
@JessicaLucindaCheng
Copy link
Member Author

JessicaLucindaCheng commented Mar 23, 2022

@Jaretzbalba
Since you have already worked on a small issue, we request that you please pick up a medium issue as your next issue as that is the recommended order of progression for members of the Website Team, and it provides you with the opportunity to learn how to work on more complex issues that are less prescriptive. Also, since we have a limited number of Small issues and each one takes a while to write, we want to make sure there are Small issues available to newer developers that have not worked on one yet. Please let us know if you have any questions or challenges while picking up a medium complexity issue.

@Jaretzbalba
Copy link
Member

@JessicaLucindaCheng Sorry for the confusion! Still learning a lot right now so was just trying to help out where I could. I'll definitely pick up a medium issue for my next one, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 0.5pt Can be done in 3 hours or less
Projects
Development

Successfully merging a pull request may close this issue.

3 participants