├── README.md ├── ISSUE_TEMPLATE.md └── contributing.md /README.md: -------------------------------------------------------------------------------- 1 | ## ProgCode Operations Team Functions 2 | [**Progressive Coders Network**](https://progcode.org) is a non-partisan, [**non-hierarchical**](https://medium.com/progressive-coders-network/structure-of-the-tyrannyless-37007b5ac7f5) community of technologists and (frequently non-coding!) tech support volunteers whose mission is to remove or reduce the impact of big money in politics by supporting the creation of open source tools to empower the grassroots. 3 | 4 | The ProgCode community operates from the bottom up. As such, organizational ideas and suggestions of each ProgCode member are valued from the first day you become a member. Members may add any topic to the weekly Operations Meeting Agenda at any time by creating a new Issue on the Operations Team Functions board. You will find detailed instructions for submitting your idea on the [**Contributions Page**](https://github.com/ProgressiveCoders/functions/blob/master/contributing.md) of this repository. 5 | 6 | ## Thank you for your interest in learning how to contribute to this amazing community! 7 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 6 | 7 | ## Required Information 8 | 9 | #### Description 10 | 11 | ... 12 | 13 | #### Problem 14 | 15 | ... 16 | 17 | #### Benefit 18 | 19 | ... 20 | 21 | #### Plan 22 | 23 | - [ ] 24 | ... 25 | 26 | #### Decision Making 27 | 28 | ... 29 | 30 | ## Optional Information 31 | 32 | #### Reference link(s) 33 | 34 | ... 35 | -------------------------------------------------------------------------------- /contributing.md: -------------------------------------------------------------------------------- 1 | ## Items to Consider Before Submitting Your Proposal 2 | 3 | Following are best practice steps and requirements for contributing your community Operations (or functions) idea to the ProgCode community for consideration. If you want to submit a tech idea to the community, please follow the **New Partners Best Practices Guide**, [**here**](https://github.com/ProgressiveCoders/projects/projects/1) 4 | 5 | ### Problem / Description (Required) 6 | Please describe your idea or proposal. What is the issue your **proposed change** may improve? 7 | 8 | ### Solution (Best Practice Option) 9 | Briefly describe how your idea or proposal how might enhance the community _(i.e., streamline existing processes, increase community engagement, distribute operations tasks, make ProgCode more inclusive, etc.)_. 10 | 11 | ### Mission Alignment (Required) 12 | Briefly describe how your proposal aligns with ProgCode's core mission to remove or reduce the influence of big money in politics by supporting the creation of open source software to empower the grassroots. 13 | 14 | ### Plan (Best Practice Option) 15 | Provide a short step-by-step process for implementing your plan in order of priority. Include specific tasks and action items, names of the members who would complete those tasks, expected delivery date or deadlines. _(It's helpful to include check boxes. You may copy and paste the sample list below into your new Functions issue)._ 16 | - [ ] Step One. 17 | - [ ] Step Two. 18 | 19 | ### Consent & Decision Making (Best Practice Option) 20 | 21 | Is your proposal meant only for community discussion at this time? Do you seek a vote for consent to continue researching/exploring your proposed idea, or do you seek a vote for consent to implement your proposal? For further guidance, please review our current **[Change Process](https://github.com/ProgressiveCoders/functions/wiki/Change-Process)**. Don't hesitate to ask team members for clarification in the #operations channel on Slack! 22 | 23 | _If left blank, your proposal will be listed for discussion on the next week's [**Operations Agenda**](http://progco.de/ops-agenda) and scheduled for vote at a later date, per the notifications requirements set forth in the Change Process.)_ 24 | 25 | ### Additional Information (Best Practice Option) 26 | This is a free-form area, but could be used for links to documents, videos, studies, statistics or proof of concept which help bolster your proposal. 27 | 28 | ### Reference Link(s) (Best Practice Option) 29 | This is a free-form area, but could be used for links to the Progressive Coders Wiki, existing Operations Functions Issues addressing similar problems, etc. 30 | 31 | ### Once you are ready to submit your proposal: 32 | 1. Create a GitHub Account. _(Don't have one yet? Create one [**here**](https://github.com/join)_! 33 | 2. Create a new GitHub Functions Issue, [**here**](https://github.com/ProgressiveCoders/functions/issues/new). Be sure to tag ProgCode Operations Staff (@adcor, @jbp5013, @PamelaJohn and @stephenscapelliti) in your new issue so that your idea can be included on the Operations Agenda for next week. 34 | 3. Attend the next Operations Meeting to discuss the merits of your proposal with the community. _Operations Meetings are held every Monday at 8pm ET (US). If you are outside the US, you may in attending the Operations Planning Meeting which is held each Monday at 10pm GMT/9pm BST (UK), more convenient. If neither of these times works for you, let us know in the #operations Slack channel and the Operations team can schedule a recorded Zoom call at a mutually convenient time and share the recording at the regularly scheduled Monday Operations Meeting. For more details about Operations Meetings and how to participate, read Page One of the Operations Meeting Agenda, [**here**](http://progco.de/ops-agenda)._ 35 | 36 | ## Thank you for your contributions to ProgCode's community operations! 37 | --------------------------------------------------------------------------------