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.

Sign up for GitHub

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

Jump to bottom

Audit Issue Templates #102

Open
12 tasks
Aveline-art opened this issue Dec 27, 2021 · 2 comments
Open
12 tasks

Audit Issue Templates #102

Aveline-art opened this issue Dec 27, 2021 · 2 comments
Labels
feature: GitHub Setup Pertains to GitHub settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 13pt+ Must be broken down into smaller issues
Milestone
01 - Compliance

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Dec 27, 2021 •
edited
Loading

Overview

As an open source contributor, I would like to understand how to open issues for errors I have noticed with this project (for example, with errors in our documentation, or bugs on our website). For this issue, we will audit our various issue templates, perform clean up, and discuss additions tailored for open source contributors.

Action Items

  • Create a spreadsheet on our GoogleDrive containing the following columns:
    • name of issue template
    • description of issue template
    • link to issue template from our repository
    • purpose of the template
    • decision (delete or update)
  • Fill out the spreadsheet to the best of your ability. The first three should be doable, the fourth might require making inquiries, and the last should be left blank.
  • Share the spreadsheet with the team so that the decision for each template can be made and agreed upon
    • Make sure to also discuss if new templates need to be made
  • Transfer this issue to development, if not, already by changing the 'role' label to either 'frontend' or 'backend'.
    • Add action items below for developers based on the decisions made, if any

For developers

  • TBD

Resources/Instructions

New issue web interface version of our templates
Issue Template Directory
Our shared drive
@Aveline-art Aveline-art added feature: GitHub Setup Pertains to GitHub settings role: backend Pertains to backend tasks size: 13pt+ Must be broken down into smaller issues labels Dec 27, 2021
@Aveline-art
Copy link
Member Author

Aveline-art commented Dec 27, 2021 •
edited
Loading

@sharadgaurav7 @sdimran My intuition tells me that this issue should be a developer issue, as it involves open source contributors. But I am also not sure where these issue templates come from (they seem to have been copied over from some template outside of this project). Do either of you know if product has anything to do with them? Please let me know and feel free to add further instructions in the issue on who to contact for info about these templates.

@sdimran sdimran added this to the 01- Compliance milestone Jan 9, 2022
@Aveline-art
Copy link
Member Author

Further questions: Do we need an issue template for freelance bug reports? We do not have an MVP yet, so this will be far off. But I do want to make a note of it on our documentation such as the readme or contri.md just to orient visitors to our repository.

@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: GitHub Setup Pertains to GitHub settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: backend Pertains to backend tasks size: 13pt+ Must be broken down into smaller issues
Projects
CTJ: Project Board
Status: 👀 Questions/Review
Milestone
01 - Compliance
Development

No branches or pull requests
3 participants
@sdimran @ExperimentsInHonesty @Aveline-art