├── .github └── ISSUE_TEMPLATE │ ├── add-project-logo-or-image-to-your-main-repository.md │ ├── blank-issue.md │ ├── control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md │ ├── create-agenda.md │ ├── create-project-card-for--project-name-.md │ ├── custom.md │ ├── feature_request.md │ ├── lighthouse--accessibility---forms.md │ ├── lighthouse--accessibility---links.md │ ├── lighthouse--cross-origin-destinations-are-unsafe.md │ ├── lighthouse--how-to.md │ ├── lighthouse--image-optimization.md │ ├── proposal-to-change-project-md-file-format.md │ ├── update-content-for-readme-file.md │ ├── update-project-profile---name-of-project-.md │ ├── update-team-roster.md │ ├── wave-chrome-extension--accessibility-review.md │ └── which-accessibility-testing-tool-should-you-use-.md ├── LICENSE └── README.md /.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/control-what-appears-when-you-paste-your-sites-link-in-social-media-sites.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Control what appears when you paste your sites link in social media sites 3 | about: Add Open Graph Markup tags to header 4 | title: Control what appears when you paste your sites link in social media sites 5 | labels: enhancement, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | When your website is shared on slack, facebook, twitter, etc. It should automatically display with an image and title instead of just the URL. 12 | 13 | ### Action items 14 | Identify what to put in the following fields: 15 | og:url 16 | g:type 17 | og:title 18 | og:description 19 | og:image 20 | og:type (optional) 21 | og:local (option) 22 | using the standards set forth in the instructions. 23 | 24 | Add content to header and test with the tool provided in the instructions. 25 | 26 | ### Instructions 27 | [A Guide to Sharing for Webmasters](https://developers.facebook.com/docs/sharing/webmasters#markup) 28 | -------------------------------------------------------------------------------- /.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/create-project-card-for--project-name-.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Create project card for [project name] 3 | about: Gather information to add this project to HackforLA's website 4 | title: '' 5 | labels: documentation, good first issue, question 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Provide collateral for the HackforLA website 12 | 13 | ### Action Items 14 | - [ ] Gather items 15 | - [ ] 600 x 400 image 16 | - [ ] Alt image text 17 | - [ ] 1500 x 700 hero image (please do not put project title on hero image) 18 | - [ ] Alt image text 19 | - [ ] Name of project 20 | - [ ] A blurb about your project 21 | - [ ] Links (github, slack channel url, Testing Site, Live Site, etc.) 22 | - [ ] Any resources for a Getting Started link (a link to a wiki, readme(s) or both) 23 | - [ ] What you are looking for skills wise 24 | - [ ] Partner(s) 25 | - [ ] Location 26 | - [ ] Status 27 | - [ ] Add project Card to website 28 | 29 | ### Resources/Instructions 30 | See project cards on the hackforla.org website for examples 31 | -------------------------------------------------------------------------------- /.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, product 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/lighthouse--accessibility---forms.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Lighthouse: Accessibility - Forms' 3 | about: Instructions for creating or improving forms to make them accessible when visitors 4 | use screen readers AKA Form elements must have labels 5 | title: 'Lighthouse: Accessibility - Forms' 6 | labels: '' 7 | assignees: '' 8 | 9 | --- 10 | 11 | ### Overview 12 | In order for your sites form(s) to be usable by visitors using screen readers all the form elements need labels. There are specific details and exceptions, which can be found in the instructions below. 13 | 14 | ### Action Items 15 | *If your site already has forms* review the instructions and document the changes needed to bring your form(s) into WCAG compliance, by commenting on this issue. 16 | *If your site does not have forms* review the instructions and design new forms using the WCAG standards. 17 | 18 | ### Instructions 19 | Deque University 20 | https://dequeuniversity.com/rules/axe/3.2/label 21 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/lighthouse--accessibility---links.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Lighthouse: Accessibility - Links' 3 | about: AKA Links must have discernible text 4 | title: 'Lighthouse: Accessibility - Links' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | The formatting of links can make them readable or unreadable by screen readers. Which includes creating programmatic events for links without making them device specific (e.g., onfocus() instead of onmouseover(), etc.), and other ways of making sure all links are visible by screen readers. 12 | 13 | ### Action Items 14 | *If your site already has links* review the instructions and document the changes needed to bring your link(s) into WCAG compliance, by commenting on this issue. 15 | *If your site does not have links yet* review the instructions and design all new links using the WCAG standards. 16 | 17 | ### Instructions 18 | Deque University 19 | https://dequeuniversity.com/rules/axe/3.2/link-name 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/lighthouse--cross-origin-destinations-are-unsafe.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Lighthouse: Cross-origin destinations are unsafe' 3 | about: Instructions for addressing the cross-origin linking vulnerabilities 4 | title: 'Lighthouse Issue: Cross-origin destinations are unsafe' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Links to cross-origin destinations are unsafe both from a security and performance perspective. 12 | 13 | ### Action Item 14 | Run [Lighthouse](https://developers.google.com/web/tools/lighthouse/) and then follow the instructions in [cross-origin destinations are unsafe] 15 | (https://developers.google.com/web/tools/lighthouse/audits/noopener) . 16 | 17 | ## Summary of instructions 18 | When using *target=_blank* also adding *rel="noopener"* to the tag ensures that new page runs in a separate process. 19 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/lighthouse--how-to.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Lighthouse: How To' 3 | about: Provides overview of how to use Lighthouse and links to additional resources 4 | title: 'Lighthouse: How To' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, and more. Hack For LA recommends that you run the tests and evaluate what changes you might want to make on your website to improve performance and accessability. 12 | 13 | ### How To Use 14 | Lighthouse is in the Audits panel of the Chrome DevTools. To run a report: 15 | 16 | 1. Download Google Chrome for Desktop. 17 | 2. In Google Chrome, go to the URL you want to audit. You can audit any URL on the web. 18 | 3. Open Chrome DevTools. 19 | 4. Click the Audits tab. 20 | 5. Click Perform an audit. DevTools shows you a list of audit categories. Leave them all enabled. 21 | 6. Click Run audit. After 60 to 90 seconds, Lighthouse gives you a report on the page. 22 | 23 | For more information go to : 24 | https://developers.google.com/web/tools/lighthouse/ 25 | 26 | ### Tip 27 | You will want to re-run lighthouse on any code changes before integrating them into your site. Sometimes the specific suggestions it makes, do not actually result in improved performance or can actually harm performance. 28 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/lighthouse--image-optimization.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Lighthouse: Image Optimization' 3 | about: Instructions for optimizing images 4 | title: 'Lighthouse: Image Optimization' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | When you run the lighthouse review it may suggest some specific image optimizations such as choosing another image format and making those changes may or may not improve your sites actual performance. 12 | 13 | ### Action Items 14 | Run lighthouse on a local version of the website and then apply suggested changes and retest locally before determining if you want to keep the changes. 15 | 16 | ### Instructions/Resources 17 | Google's Tools for Web Developers: [Optimize Images](https://developers.google.com/web/tools/lighthouse/audits/optimize-images) 18 | Read [closed issue #111](https://github.com/hackforla/website/issues/111) from when HackforLA.org did our audit, to see why we decided not to do the image optimization 19 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/proposal-to-change-project-md-file-format.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: proposal to change project.md file format 3 | about: To propose changes to project.md file format 4 | title: Proposal to change project.md file format [that accomplishes x] 5 | labels: documentation, enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | Describe the purpose for the proposal change 12 | 13 | ### Action items 14 | - [ ] Indicate current state in a yaml snipit here: 15 | 16 | - [ ] Indicate desired future state in a yaml snipit here: 17 | 18 | - [ ] Perform test 19 | - [ ] one project.md file 20 | - [ ] updating logic of appropriate include file 21 | - [ ] Get signoff 22 | - [ ] update all project.md files with new or revised fields 23 | - [ ] Update Template project.md wiki page 24 | - [ ] Submit pull request - indicating Issue #294 is affected (format changes log), and the text "fixes Issue #[number that you are creating now] 25 | 26 | ### Resources 27 | Wiki page - [Template of a project.md file](https://github.com/hackforla/website/wiki/Template-of-a-project.md-file) 28 | 29 | ***Links to comments on other issues where this proposal originated*** 30 | REPLACE TEXT - put links here 31 | -------------------------------------------------------------------------------- /.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-project-profile---name-of-project-.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Update Project Profile: [name of project]' 3 | about: We are making a project home page for each project and need some additional 4 | info 5 | title: 'Update Project Profile: [name of project]' 6 | labels: documentation 7 | assignees: '' 8 | 9 | --- 10 | 11 | ### Overview 12 | Update the following fields for your project. These updated fields will then be updated to be shown on the website. 13 | 14 | ### Action Items 15 | - [ ] Update wording of anything currently on the project card (see [hackforla.org](https://www.hackforla.org/)) 16 | - [ ] Provide information on which Tools your team is using for the project (Ex: figma, Balsamiq, photoshop, etc.) . This is different than programming languages 17 | - [ ] Update "Looking For" Section 18 | - [ ] Update any links that are not currently displayed on the site (do you have a demo site?) 19 | - [ ] Hero image to be displayed on Project Home Page at 1500 x 700 px 20 | - [ ] Any resources for a Getting Started link (either a link to a wiki or readme) 21 | 22 | ### Resources/Instructions 23 | See the hero image on the [hackforla.org](https://www.hackforla.org/) homepage 24 | -------------------------------------------------------------------------------- /.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 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/wave-chrome-extension--accessibility-review.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: 'Wave Chrome Extension: Accessibility review' 3 | about: Describe this issue template's purpose here. 4 | title: 'Wave Chrome Extension: Accessibility review' 5 | labels: '' 6 | assignees: '' 7 | 8 | --- 9 | 10 | ### Overview 11 | 12 | #### Action Items 13 | 1. add [WAVE chrome extension](https://chrome.google.com/webstore/detail/wave-evaluation-tool/jbbplnpkjmmeebjpijfedlgcdilocofh) 14 | 2. visit site 15 | 3. click the extension and review the red flags. 16 | 4. Run the same steps for the development site (localhost). Ensure that the chrome extension has the "Allow access to file URLs" enabled. 17 | 5. Document all suggested changes in the comments. 18 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/which-accessibility-testing-tool-should-you-use-.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Which accessibility testing tool should you use? 3 | about: There are a lot of tools, this issue has a list of our favorites and links 4 | to more 5 | title: Which accessibility testing tool should you use? 6 | labels: '' 7 | assignees: '' 8 | 9 | --- 10 | 11 | ### Overview 12 | There are more than 100 accessibility testing tools. Figuring out which ones to use can be a black hole. For guidance we recommend this article: [Which accessibility testing tool should you use?](https://medium.com/pulsar/which-accessibility-testing-tool-should-you-use-e5990e6ef0a) 13 | 14 | ### Summary of Article 15 | The author recommends using the tools in the following order fixing as you go along, since no one tool catches all the relevant issues 16 | 17 | [aXe](https://www.deque.com/axe/) 18 | [SiteImprove](https://chrome.google.com/webstore/detail/siteimprove-accessibility/efcfolpjihicnikpmhnmphjhhpiclljc) 19 | [Tenon](https://tenon.io/) 20 | [WAVE](https://wave.webaim.org/extension/) 21 | [Lighthouse](https://developers.google.com/web/tools/lighthouse/#devtools) 22 | 23 | But if you want to test your site with other tools, here is a bigger [list](https://www.w3.org/WAI/ER/tools/) 24 | -------------------------------------------------------------------------------- /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 | # Communities of Practice 2 | 3 | A Community of Practice (CoP) is a group of people who share a common interest in a topic and meet regularly to fulfill both individual and group goals. At Hack for LA, we use CoPs to share effective practices and relevant domain knowledge to help our members grow. 4 | 5 | All new volunteers at Hack for LA should join the relevant CoP and work on a couple of issues there to familiarize yourself with GitHub and how things work at Hack for LA. Once you have some proficiency, you will be assigned to a project. You are encouraged to continue attending CoP meetings to continue domain learning and peer to peer mentorship. 6 | 7 | ### Our Communities 8 | Meeting times and CoP leaders can be found here: https://hackforla.org/communities-of-practice 9 | 10 | ### How to Join a Community of Practice 11 | - Read the Wiki or Readme for your Community of Practice 12 | - Click the Get Access link and follow the instructions 13 | - Attend your Community of Practice meetings (if there are two, you can attend the one that is convenient) 14 | 15 | ### How to Start a new Community of Practice 16 | - Slack the Admin channel. 17 | 18 | ### Open Roles (on Projects) with Role Definitions by Practice Areas 19 | _If you are a Product Manager who needs to recruit any of the below talent for your team, please click on the relevant role boards and add the role you are looking for._ 20 | 21 | - [**UI/UX - Content**](https://github.com/orgs/hackforla/projects/67/views/9) 22 | - [**UI/UX - Design**](https://github.com/orgs/hackforla/projects/67/views/4) 23 | - [x] [ui-designer](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/ux-designer.md) 24 | - [x] [ux-designer](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/ux-researcher.md) 25 | - [**UI/UX - Research**](https://github.com/orgs/hackforla/projects/67/views/8) 26 | - [x] [ux-researcher](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/ux-researcher.md) 27 | - [ ] needed: ux-program-designer 28 | - [ ] needed: ux-community-of-practice-lead 29 | - [ ] needed: ux-research-lead 30 | - [**Data Science**](https://github.com/orgs/hackforla/projects/67/views/6) 31 | - [x] [data-scientist](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/data-scientist.md) 32 | - [x] [data-analyst](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/data-analyst.md) 33 | - [x] [Database Architect](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/database-architect.md) 34 | - [**Engineering**](https://github.com/orgs/hackforla/projects/67/views/3) (programming) 35 | - [x] [front-end-developer](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/front-end-developer.md) 36 | - [x] [back-end-developer](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/back-end-developer.md) 37 | - [x] [full-stack-developer](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/full-stack-developer.md) 38 | - [x] [qa-engineer (also SDET)](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/qa-engineer.md) 39 | - [x] [Database Architect](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/database-architect.md) 40 | - [**DevOps**](https://github.com/orgs/hackforla/projects/67/views/7) 41 | - [x] [data-engineer-devops](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/data-engineer-devops.md) 42 | - [**Product Management**](https://github.com/orgs/hackforla/projects/67/views/5) 43 | - [x] [business-analyst](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/business-analyst.md) 44 | - [x] [product-manager](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/product-manager.md) 45 | - [x] [product-owner](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/product-owner.md) 46 | - [x] [special-projects-coordinator](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/special-projects-coordinator.md) 47 | - [ ] needed: lead-product-manager 48 | - [**Marketing**](https://github.com/orgs/hackforla/projects/67/views/10) 49 | - [x] [marketing-and-communications-coordinator](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/marketing-and-communications-coordinator.md) 50 | - [x] [marketing-and-communications-director](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/marketing-and-communications-director.md) 51 | - [x] [marketing-and-communications-intern](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/marketing-and-communications-intern.md) 52 | - [x] [marketing-and-communications-manager](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/marketing-and-communications-manager.md) 53 | - [**Revenue**](https://github.com/hackforla/revenue/projects/2) 54 | - [ ] needed: [institutional-giving-manager](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/individual-giving-manager.md) 55 | - [ ] needed: [individual-giving-manager](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/institutional-giving-manager.md) 56 | - [ ] needed: [project-fundraising-specialist](https://github.com/hackforla/civic-opportunity/blob/master/roles-1/project-fundraising-specialist.md) 57 | 58 | #### Help us Add Roles 59 | - Help us write new role descriptions ([list of all current role descriptions](https://github.com/hackforla/civic-opportunity/tree/master/roles-1)) 60 | - [x] = We have a role definition 61 | - [ ] = We need a role definition 62 | --------------------------------------------------------------------------------