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

Summarizing our project for official GitHub documentation #54

Closed
5 tasks done
Tracked by #2
Aveline-art opened this issue Dec 7, 2021 · 7 comments
Closed
5 tasks done
Tracked by #2

Summarizing our project for official GitHub documentation #54

Aveline-art opened this issue Dec 7, 2021 · 7 comments
Labels
feature: Documentation Pertains to documentation of any kind PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 2pt Can be done in 7-12 hours

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Dec 7, 2021

Overview

As a developer, I would like our documentation to succinctly and effectively summarize our project for new, potential developers. For this issue we will come up with a project summary for our read me and wiki.

Action Items

  • Create an introduction to our project on our read me
  • Create an introduction to our project on our wiki homepage
  • Get approval from the team on the introduction
  • Release dependency on:

Resources/Instructions

README.md
Wiki home

@Aveline-art Aveline-art added role: missing size: 2pt Can be done in 7-12 hours labels Dec 7, 2021
@Aveline-art Aveline-art mentioned this issue Dec 7, 2021
10 tasks
@Aveline-art Aveline-art changed the title Summarizing our project for official developer documentation Summarizing our project for official GitHub documentation Dec 7, 2021
@Aveline-art
Copy link
Member Author

Questions:

  1. Which role does this issue belong to?
  2. What criteria do we have for an intro to our project?
  3. Who needs to review the intro and approve it?

@Aveline-art Aveline-art mentioned this issue Dec 10, 2021
9 tasks
@Aveline-art Aveline-art added the feature: Documentation Pertains to documentation of any kind label Dec 11, 2021
@sdimran sdimran self-assigned this Dec 14, 2021
@sdimran
Copy link
Member

sdimran commented Dec 15, 2021

Hi @Aveline-art, I made a few edits to the project description in the readme.md file in the main branch. added to the the project description as well as included a few links to the technology used. regarding the installation instructions, is there anything specific from a developers end that we need to include? I am not 100% sure if the information already there is the most up to date and in line with how the project is set up

@sdimran
Copy link
Member

sdimran commented Dec 15, 2021

Below is the current introduction for action item 1 in this ticket

CivicTechJobs is a project of Hack for LA. CivicTechJobs helps technology practitioners interested in having civic impact to find job opportunities from a central hub of listings. The website's main features include a linklist to public interest job boards and other resources relevent to their focused journey to work on projects and solve problems with a public benefit.

The CivicTechJobs.org MVP website will be a platform to help prospective volunteers find inter disciplinary projects that will be useful for their career development while contributing to positive civic impact and a CMS for Hack for LA projects to be able to list their open roles.

The tool will match volunteers by availability, role, and program area. Future iterations of the platform will focus helping volunteers find volunteer opportunities that match paid job postings, so that a volunteer can better prepare themselves for the marketplace.

@sdimran sdimran added role: frontend Pertains to frontend tasks and removed role: product labels Dec 15, 2021
@sdimran sdimran assigned Aveline-art and unassigned sdimran Dec 15, 2021
@Aveline-art Aveline-art removed their assignment Dec 15, 2021
@Aveline-art
Copy link
Member Author

Putting this into 'New Issue Approval' because I am unsure where to place it in the prioritized backlog without a milestone.

@sdimran
Copy link
Member

sdimran commented Dec 16, 2021

Hi Ava, I think we can keep this under the Project Setup milestone as the documentation will act as a go-to resource for new joiners to understand what we are doing. let me know what you think

@Aveline-art
Copy link
Member Author

Hi @sdimran! I am not too sure what milestone it should be, since I don't know what exactly each milestone entails. You can decide whichever fits best based on what the project needs?

@Aveline-art
Copy link
Member Author

Aveline-art commented Dec 27, 2021

Closed because items are completed per this comment

@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
Labels
feature: Documentation Pertains to documentation of any kind PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 2pt Can be done in 7-12 hours
Projects
Status: Done
Development

No branches or pull requests

4 participants