├── .github └── ISSUE_TEMPLATE │ ├── Offboard_Mentor.md │ ├── Onboard_Lead.md │ ├── Onboard_Mentor.md │ ├── add-project-logo-or-image-to-your-main-repository.md │ ├── blank-issue.md │ ├── create-agenda.md │ ├── custom.md │ ├── feature_request.md │ ├── guest_speaker_questions.md │ ├── offboard-engineering-cop-lead.md │ ├── recruit-new-lead.md │ ├── recruit-new-mentor-s-.md │ ├── template-for-making-guides-templates-template.md │ ├── update-content-for-readme-file.md │ ├── update-meeting-information.md │ └── update-team-roster.md ├── CODEOFCONDUCT.md ├── LICENSE └── README.md /.github/ISSUE_TEMPLATE/Offboard_Mentor.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Offboard Mentor 3 | about: Consistent formatting make Issues concise and easy to navigate 4 | title: Offboard Mentor [name of mentor] 5 | labels: 'program: Mentor Nights, role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### OVERVIEW 11 | We need to offboard [mentor name] from our Mentor team. 12 | 13 | ### ACTION ITEMS 14 | - [ ] Remove them from the [Engineering CoPs wiki](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-mentors) 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/Onboard_Lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Onboard Engineering CoP Lead 3 | about: Use this checklist for onboarding Leads 4 | title: Onboard [name of new lead] 5 | labels: 'role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to onboard [NEW LEAD NAME] onto the project. 12 | 13 | ### Onboard Checklist 14 | - [ ] Slack channel membership 15 | - [ ] #engineering 16 | - [ ] #engineering-cop-leads 17 | - [ ] Calendaring 18 | - [ ] Add to Engineering Contacts with leads label 19 | - [ ] Add to Google calendar invites 20 | - [ ] Add to [community page](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-leads) on Wiki 21 | - [ ] Add to [HfLA CoP page](https://www.hackforla.org/communities-of-practice) by filling out [this website issue](https://github.com/hackforla/website/issues/new?assignees=&labels=role%3A+product%2CP-Feature%3A+Communities+of+Practice%2Ctime+sensitive%2CComplexity%3A+Missing%2Csize%3A+missing&projects=&template=communities-of-practice-information-updates.yml&title=Communities+of+Practice+information+updates%3A+%5BINSERT+NAME+OF+Community+of+Practice%5D) 22 | - [ ] Google Drive 23 | - [ ] Add to Engineering drive as Manager 24 | - [ ] GitHub 25 | - [ ] Add to team [write team](https://github.com/orgs/hackforla/teams/engineering-write/members) 26 | - [ ] Change membership to maintainer 27 | - [ ] Add to [read vault](https://github.com/orgs/hackforla/teams/engineering/members) 28 | - [ ] Change membership to maintainer 29 | - [ ] Check their github handle by assigning them to this issue, to see if they have added their name, so that you don't have to memorize their handle 30 | - [ ] Add them to the [leadership team list](https://github.com/hackforla/engineering/projects/1#card-88413743) and link to their issues 31 | - [ ] 1password 32 | - [ ] Send name and email to Admin on Slack and ask to grant access to: 33 | - Engineering vault 34 | - Zoom vault 35 | - [ ] Email 36 | - [ ] Add to email address filter (forwarder) 37 | - [ ] make sure they can log onto engineering@hackforla.org 38 | - [ ] Train how to 39 | - [ ] login to team email account 40 | - [ ] use zoom spreadsheet, vault, and accounts 41 | - [ ] use kanban board and wiki 42 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/Onboard_Mentor.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Onboard Mentor 3 | about: Consistent formatting make Issues concise and easy to navigate 4 | title: Onboard Mentor [name of mentor] 5 | labels: 'program: Mentor Nights, role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### OVERVIEW 11 | We need to onboard sr developer [mentor name] to our Mentor team. 12 | 13 | ### ACTION ITEMS 14 | - [ ] Let them know their information will be posted on the wiki 15 | - [ ] Add their name, Slack, GitHub, and LinkedIn to the [Engineering CoPs wiki](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-mentors) 16 | - [ ] Add their email to the Engineering CoP calendar invite and give them the "Mentor" label in contacts 17 | - [ ] Add them to the [project board mentor list](https://github.com/hackforla/engineering/projects/1#card-89258504) 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/add-project-logo-or-image-to-your-main-repository.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Add project logo or image to your main repository 3 | about: Simple action that will make it possible to add project to hackforla.org website 4 | title: '' 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | By adding the project's logo/image to your project's primary repository, we will be able to dynamically deliver up to date information about your project to the hackforla.org website. Also when people add the link to the repository in LinkedIn or Slack, or other social media it will automatically use the image as well as the description, improving the link's chances of getting clicked on. 12 | 13 | ### Action Items 14 | Add project's logo/image to your primary Github repository using the instructions below. You should use the same image as is on the hackforla.org website, or if another image is desired, please replace both with the same image. 15 | 16 | ### Resources/Instructions 17 | Tip: Your image should be a PNG, JPG, or GIF file under 1 MB in size. For the best quality rendering, we recommend keeping the image at 640 by 320 pixels. 18 | Read Github's [Customizing your repository's social media preview](https://help.github.com/en/articles/customizing-your-repositorys-social-media-preview) 19 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/blank-issue.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Blank Issue 3 | about: Consistent formatting make Issues concise and easy to navigate 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | REPLACE THIS TEXT -Text here that clearly states the purpose of this issue in 2 sentences or less. 12 | 13 | ### Action Items 14 | REPLACE THIS TEXT -If this is the beginning of the task this is most likely something to be researched and documented. 15 | 16 | REPLACE THIS TEXT -If the issue has already been researched, and the course of action is clear, this will describe the steps. However, if the steps can be divided into tasks for more than one person, we recommend dividing it up into separate issues, or assigning it as a pair programming task. 17 | 18 | ### Resources/Instructions 19 | REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here. 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/create-agenda.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Create Agenda 3 | about: Assign issue to all team members day after meetup in prep for next meetup 4 | title: '' 5 | labels: documentation, help wanted, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Gather all items team members want to propose for this weeks' agenda. 12 | 13 | ### Action Items 14 | Add comment to this issue with your proposed agenda item. if item warrants an issue of its own please start a new issue, by going to the issues tab above and clicking on the New Issues green button. 15 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/custom.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Custom issue template 3 | about: Describe this issue template's purpose here. 4 | title: '' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for this project 4 | title: 'Feature Suggestion: ' 5 | labels: documentation 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Please write a user story for this feature suggestion in the following format: As a ______, I want to do X for Y reason and replace this text with it. 12 | 13 | ### Action Items 14 | - [ ] Define your Feature Suggestion 15 | - [ ] What is the feature you are suggesting? 16 | - [ ] Is this feature urgent 17 | - [ ] if so why? 18 | - [ ] How long do you expect it take to implement this issue? 19 | - [ ] Who is needed to implement this feature (Could you implement it yourself?) 20 | - [ ] Design 21 | - [ ] Front End 22 | - [ ] Back End 23 | - [ ] Database 24 | - [ ] What problem does this feature solve? 25 | - [ ] What technologies are needed for this feature? 26 | 27 | ### Resources/Instructions 28 | If there is a website which has documentation that helps with this issue provide the link(s) here: 29 | 30 | 31 | **Additional context** 32 | Add any other context or screenshots about the feature request here. 33 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/guest_speaker_questions.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Guest Speaker Questions 3 | about: Create issue to collect questions for guest speakers ahead of time 4 | title: 'Generate Questions for [YYYY-MM-DD]: [NAME/COMPANY]' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to create a list of questions for our guest speaker [PERSON OR COMPANY] attending on [DATE]. 12 | 13 | ### Action Items 14 | - [ ] Send issue to Engineering Slack channel and ask Engineering members to write their questions in the comments. 15 | - [ ] Send format of talk to guest 16 | - [ ] Collate the questions into a list of unique questions (non-duplicated questions). 17 | - [ ] Send ***Questions*** and ***Consent Form*** within 2 weeks of their talk. 18 | - [ ] Update Wiki 19 | 20 | ### Resources/Instructions 21 |
22 | Slack Announcement 23 | 24 | **[GUEST SPEAKER]** will be visiting the Engineering Community of Practice on **[DATE]**! 25 | 26 | **Topic:** [Input Discussion Topic] 27 | 28 | Please post **your questions** in this [GitHub issue] 29 | 30 | **About:** [INSERT BIO] 31 | 32 | **[LinkedIn or WEBSITE]** [LINKEDIN LINK] 33 | 34 | We will be collecting questions until the end of day : [Date of last day] 35 | 36 | Thank you! 37 | Engineering CoP co-leads 38 | 39 |
40 | 41 | - [WEBSITE FOR GUEST SPEAKER] 42 | 43 | ### Speaker Bio 44 | [INSERT SPEARKER BIO] 45 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/offboard-engineering-cop-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Offboard Engineering CoP Lead 3 | about: Use this checklist for offboarding Leads 4 | title: Offboard [name of new lead] 5 | labels: 'role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to remove [NEW LEAD NAME] from the Engineering CoP leads team. 12 | 13 | ### Offboard Checklist 14 | - [ ] Remove from #engineering-cop-leads Slack channel 15 | - [ ] Calendaring 16 | - Remove Leads label from Engineering Contact 17 | - Remove from Leads team meeting Google calendar invites 18 | - [ ] Move to "previous leads" on the [community page](https://github.com/hackforla/engineering/wiki/Community#engineering-cop-leads) on Wiki 19 | - [ ] Remove from [HfLA CoP page](https://www.hackforla.org/communities-of-practice) by filling out [this website issue](https://github.com/hackforla/website/issues/new?assignees=&labels=role%3A+product%2CP-Feature%3A+Communities+of+Practice%2Ctime+sensitive%2CComplexity%3A+Missing%2Csize%3A+missing&projects=&template=communities-of-practice-information-updates.yml&title=Communities+of+Practice+information+updates%3A+%5BINSERT+NAME+OF+Community+of+Practice%5D) 20 | - [ ] Demote to 'Contributor' on Engineering drive 21 | - [ ] GitHub 22 | - Change [write team](https://github.com/orgs/hackforla/teams/engineering-write/members) role to 'member' 23 | - Change [read vault](https://github.com/orgs/hackforla/teams/engineering/members) role to 'member' 24 | - Remove them from the [leadership team list](https://github.com/hackforla/engineering/projects/1#card-88413743) and link to their issues 25 | - [ ] Send name and email to Admin on Slack and ask to remove from 1 Password vaults: 26 | - Engineering vault 27 | - Zoom vault 28 | - [ ] Email 29 | - Remove from email address forwarder 30 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/recruit-new-lead.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Recruit new lead 3 | about: Use this checklist when recruiting a new Engineering CoP Lead 4 | title: Recruit new Engineering CoP lead 5 | labels: 'role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | 12 | We need a lead to help us out with [description of work needed]. 13 | 14 | ### Action Items 15 | - [ ] Post [card](https://github.com/hackforla/engineering/projects/2#card-90139782) on Open Roles board 16 | - [ ] Post in [Community Leads Open Roles wiki](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles) 17 | - [ ] If you need to create a new posting, you may need to create a new [interest form](https://drive.google.com/drive/u/0/folders/1A8KSPEQ5oupkp5iCK53Xu85lh7Wm7q0r) 18 | - [ ] Notify community in [#Engineering Slack](https://hackforla.slack.com/archives/C01CU709SER) 19 | - [ ] Notify community in CoP meeting 20 | - [ ] Host an info session with interested parties 21 | - [ ] Check for responses to the interest form (these should automatically forward to your email, but you can check in [the drive](https://drive.google.com/drive/u/0/folders/1A8KSPEQ5oupkp5iCK53Xu85lh7Wm7q0r), too) and interview qualified candidates with the other leads to make sure: 22 | - They are able to commit to at least 6 months 23 | - They are available to come to Thursday meetings 24 | - They are able to participate in meaningful conversation and interested in community development ('Why are you interested in this role?) 25 | - [ ] [Onboard](https://github.com/hackforla/engineering/issues/new?assignees=&labels=role%3A+lead&projects=&template=Onboard_Lead.md&title=Onboard+%5Bname+of+new+lead%5D) the selected new lead 26 | 27 | ### Resources/References 28 | - Open Roles Cards 29 | - [Mentor Coordinator](https://github.com/hackforla/engineering/projects/2#card-90139782) 30 | - Open Roles wiki 31 | - [Mentor Coordinator](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles#engineering-cop-community-co-lead---mentor-coordinator) 32 | - Recruitment forms can be found [here](https://drive.google.com/drive/u/0/folders/1A8KSPEQ5oupkp5iCK53Xu85lh7Wm7q0r) 33 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/recruit-new-mentor-s-.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Recruit new mentor(s) 3 | about: Use this checklist when we need to recruit new mentors. 4 | title: Recruit new mentor(s) 5 | labels: 'program: Mentor Nights, role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | 12 | We need to recruit more engineering mentors. 13 | 14 | ### Background 15 | 16 | Mentors are always in demand. Potential mentors can find an open role card [here](https://github.com/hackforla/engineering/projects/2#card-90139757) which will lead them to the [wiki](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles#engineering-mentor-wanted) which will direct them to fill out [this form](https://docs.google.com/forms/d/1qYnqZM5JfboFd4Jux-m0puy0ahAlNvmatd09XsxG7YQ/edit) to show their interest. When someone fills out that form, it will send a notification to engineering@hackforla.com, which will forward to all of the current community leads. You can also find the results of the form [here](https://docs.google.com/spreadsheets/d/1k18KYPZxrl8tEbHCo6dgVz4olKvkfVlrlJPxWihKM-4/edit#gid=1483880522). 17 | 18 | So that is what the process looks like on the candidate's side. Here is what you need to do... 19 | 20 | Action Items: 21 | - [ ] Check the open roles board and make sure the '[Engineer Mentors](https://github.com/hackforla/engineering/projects/2#card-90139757)' card: 22 | - is posted under 'Community Lead' 23 | - the link goes to the correct wiki posting for more details 24 | - [ ] Check the[ leads open roles wiki page ](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles)and make sure the '[Engineering Mentors Wanted](https://github.com/hackforla/engineering/wiki/Community-Leads-Open-Roles#engineering-mentor-wanted)!' section: 25 | - correctly links back to the card on the open roles board 26 | - has correct information 27 | - correctly links to the '[Engineering Mentor Interest Form](https://forms.gle/ajzPihZ9Xjb56K4HA)' 28 | - [ ] Let the community know we are looking via: 29 | - Slack 30 | - In the meetings 31 | - [ ] Optional: Ask in a Zoom poll if people are interested in building leadership skills and reach out to them directly 32 | - [ ] Schedule and host an info session to anyone interested in mentoring but are on the fence when needed 33 | - [ ] Review responses to form and reach out to qualified candidates to confirm their availability 34 | - [ ] [Onboard them](https://github.com/hackforla/engineering/issues/new?assignees=&labels=program%3A+Mentor+Nights%2C+role%3A+lead&projects=&template=Onboard_Mentor.md&title=Onboard+Mentor+%5Bname+of+mentor%5D) 35 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/template-for-making-guides-templates-template.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Template for Making Guides/Templates template 3 | about: Describe this issue template's purpose here. 4 | title: 'Create a Guide/Template: [name of item]' 5 | labels: 'documentation, feature: guide creation, TG: Gather Examples' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to create a guide to making [name of item] so that [purpose of the item] 12 | 13 | ### Action Items 14 | - [ ] Gather examples of how other projects have done it, adding each example as a link in the resources section. It is really important to annotate as you go in this issue, so that if you have to stop working on the issue, its already up to date with your findings. 15 | - [ ] Once done, remove the "TG: Gather Examples" label and add the "TG: Draft Template" label 16 | - [ ] Create a draft template, either in markdown format in this issue or a google doc in the [Engineering google drive](https://drive.google.com/drive/u/0/folders/1xWllQli2wUSsRF9OaSQBBQ1vaY7kRkAT) 17 | - [ ] Once done, remove the "TG: Draft Template" label and add the "TG: Create Guide" label 18 | - [ ] Create a guide on how to use the template 19 | - [ ] Once done, remove the "TG: Create Guide" label and add the "TG: Review Guide" label 20 | - [ ] Review the guide with product management communities of practice 21 | - [ ] Once done, remove the "TG: Review Guide" label and add the "TG: Leadership Review" label 22 | - [ ] Present to Hack for LA leadership team for sign off 23 | - [ ] Once approved, remove the "TG: Leadership Review" label and add the "TG: Place Guide" label 24 | - [ ] Possibly create an issue template on .github 25 | - [ ] Include link to template under resources if you add it as a template in .github 26 | 27 | ### Resources 28 | Update tracker issue (TBD) with the name of item you are working 29 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-content-for-readme-file.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Content for ReadMe file 3 | about: Instructions for revising the README.md file inside this repository 4 | title: '' 5 | labels: documentation, good first issue, help wanted, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | We need to have a working READme file to easily on-board new team members. 12 | 13 | ### Action Items 14 | - [ ] Add the following information as a comment to this issue: 15 | - [ ] Identify what information needs to be collected. 16 | - [ ] Identify who holds each piece of information. 17 | - [ ] Collect information. 18 | 19 | ### Resources/Instructions 20 | PUT LINK TO README.md FILE HERE 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-meeting-information.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Meeting information 3 | about: Use this checklist when changes are being made to the Engineering CoP meetings. 4 | title: Update meeting information 5 | labels: 'role: lead' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | There are a lot of places meeting information gets published. Use this checklist to make sure that the correct information is published everywhere. 12 | 13 | ### Checklist 14 | - [ ] [VRMS](vrms.io) 15 | - [HfLA CoP's page](https://www.hackforla.org/communities-of-practice) 16 | - [HfLA events page](https://www.hackforla.org/events/) 17 | - [ ] [Communities of Practice repo](https://github.com/hackforla/communities-of-practice#our-communities) 18 | - [ ] Slack channel topic 19 | - [ ] Engineering Repo 20 | - [Engineering repo readme](https://github.com/hackforla/engineering#when-we-meet) 21 | - [CoP meetings wiki page](https://github.com/hackforla/engineering/wiki/CoP-Meetings) 22 | - [Engineering CoP project board](https://github.com/hackforla/engineering/projects/1#card-57160496) 23 | - [ ] Zoom 24 | - [ ] [Zoom assignment spreadsheet](https://docs.google.com/spreadsheets/d/15P3MYyNQ7Xn0pqdrTynDDipjrLl5LCN9xHVLhk9SWa8/edit#gid=0) 25 | - [ ] Google calendar invite 26 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/update-team-roster.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Update Team Roster 3 | about: Provides new team members a link to team roster to input their information 4 | title: '' 5 | labels: documentation, good first issue, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Rolling Roster of Team Participants. 12 | 13 | ### Action Items 14 | Add or update your personal info to the team roster. 15 | 16 | ### Resources/Instructions 17 | ADD URL TO TEAM ROSTER HERE 18 | -------------------------------------------------------------------------------- /CODEOFCONDUCT.md: -------------------------------------------------------------------------------- 1 | ## Code of Conduct 2 | 3 | As part of Hack for LA, we observe the organisation's [Code of Conduct](https://github.com/hackforla/codeofconduct). 4 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Software Engineering Community of Practice 2 | 3 | Welcome to the Software Engineering Community of Practice. We are happy you are here! Please follow the steps below to get started: 4 | 5 | 6 | ## When We Meet 7 | 8 | Thursday nights 6:00PM Pacific Time 9 | 10 | 11 | ## Let's Get Started 12 | 13 | If you have not attended Hack for LA onboarding, plase read the [Guide for New Volunteers](https://www.hackforla.org/getting-started), and register for an upcoming onboarding session. 14 | 15 | 16 | ### Step 1. Join Software Engineering Community of Practice 17 | 18 | 1. Join the [#engineering](https://hackforla.slack.com/archives/C01CU709SER) Slack channel and introduce yourself. 19 | 2. Slack our [Engineering Community of Practice lead](https://www.hackforla.org/communities-of-practice) with your Gmail address. 20 | 3. Accept your Google Drive invite to access the [shared folder](https://drive.google.com/drive/u/0/folders/1xWllQli2wUSsRF9OaSQBBQ1vaY7kRkAT). 21 | 4. Add yourself to the [Team Roster](https://docs.google.com/spreadsheets/d/1lK6VziVqPb1FPmX8_z148AEOrpwsEzTPct7Bo7kjaqI/edit). 22 | 23 | ### Step 2. Familiarize with Our Processes 24 | 25 | 1. All Hack for LA teams use Kanban boards to encourage continuous improvements at all the level of the organization. Learn more about Kanban with our [Guide to How-To Use Our Github Kanban Board](https://docs.google.com/document/d/11Fe7mNdmPBP5bD_yLJ1C0_I1TmoK47AuHHrdhdDyWCs/edit#heading=h.nl3p4nf4eqb4) (working draft). 26 | 2. Kanban is one of the popular frameworks used to implement agile development. Learn more about [Agile](https://www.atlassian.com/agile). 27 | 3. Check out the currently [open Engineering roles](https://github.com/orgs/hackforla/projects/67/views/3). 28 | 29 | 30 | ### Step 3. Join the CoP Meeting - Come Meet Engineers from All Teams 31 | 32 | * Join our Engineering Community of Practice meeting Thursdays at 6 PM PST 33 | * Take the [Remote Onboarding Survey](https://docs.google.com/forms/d/e/1FAIpQLScXnJSyCXgO_RCAuCyOkG4sqGILpAepTlJ0HOaK4H_ccEVmNw/viewform) to provide feedback about your experience joining Hack for LA. 34 | 35 | The Engineering Community of Practice is one of many. [See all our Communities of Practices](https://github.com/hackforla/communities-of-practice/blob/main/README.md) 36 | 37 | See our [Code of Conduct](./CODEOFCONDUCT.md) and [License](./LICENSE) documents. 38 | 39 | --------------------------------------------------------------------------------