├── .nojekyll ├── CNAME ├── _config.yml ├── sop-timeanddate-example.png ├── sop-meeting-agenda-example.png ├── .github └── ISSUE_TEMPLATE │ ├── 3-mtg-discussion.md │ ├── 4-mtg-stacksfoundation.md │ ├── 2-mtg-action.md │ ├── stale.yml │ └── 1-mtg-agenda.md ├── index.html ├── README.md ├── LICENSE └── sop.md /.nojekyll: -------------------------------------------------------------------------------- 1 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | pm.stacksgov.com -------------------------------------------------------------------------------- /_config.yml: -------------------------------------------------------------------------------- 1 | theme: jekyll-theme-minimal -------------------------------------------------------------------------------- /sop-timeanddate-example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/pm/HEAD/sop-timeanddate-example.png -------------------------------------------------------------------------------- /sop-meeting-agenda-example.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/stacksgov/pm/HEAD/sop-meeting-agenda-example.png -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/3-mtg-discussion.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "Agenda: Add Discussion Item" 3 | about: "Use this template to create a new agenda discussion item." 4 | title: "" 5 | labels: mtg-discuss 6 | --- 7 | 8 | ## Discussion Item 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/4-mtg-stacksfoundation.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "Agenda: Add Stacks Foundation Item" 3 | about: "Use this template to create a new agenda item related to the Stacks Foundation." 4 | title: "" 5 | labels: mtg-stacksfoundation 6 | --- 7 | 8 | ## Stacks Foundation 9 | 10 | 11 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/2-mtg-action.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "Agenda: Add Action Item" 3 | about: "Use this template to create a new agenda action item." 4 | title: "" 5 | labels: mtg-action 6 | --- 7 | 8 | ## Action Item 9 | 10 | 22 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/stale.yml: -------------------------------------------------------------------------------- 1 | # Number of days of inactivity before an issue becomes stale 2 | daysUntilStale: 14 3 | # Number of days of inactivity before a stale issue is closed 4 | daysUntilClose: 7 5 | # Issues with these labels will never be considered stale 6 | exemptLabels: 7 | - pinned 8 | - security 9 | # Label to use when marking an issue as stale 10 | staleLabel: stale-issue 11 | # Comment to post when marking an issue as stale. Set to `false` to disable 12 | markComment: > 13 | This issue has been automatically marked as stale because it has not had 14 | recent activity. It will be closed if no further activity occurs. Thank you 15 | for your contributions. 16 | # Comment to post when closing a stale issue. Set to `false` to disable 17 | closeComment: false -------------------------------------------------------------------------------- /index.html: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
13 | 22 | 23 | 24 | 25 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Project Management 2 | 3 | This repository contains [project boards](https://github.com/stacksgov/pm/projects), [open issues](https://github.com/stacksgov/pm/issues), and [meeting agendas](https://github.com/stacksgov/pm/issues/labels/mtg-agenda) for the Stacks Governance initiative. 4 | 5 | All of the information in this README is viewable on the related website for this repository, located at the link below: 6 | 7 | https://stacksgov.github.io/pm 8 | 9 | ## Additional Outlets 10 | 11 | More information about the Stacks Foundation and its mission can be found at the links below: 12 | 13 | - Website: https://stacks.org 14 | - Twitter: [@StacksOrg](https://twitter.com/StacksOrg) 15 | - Resources: https://stacksgov.github.io/resources 16 | - Community Calls: https://stacksgov.github.io/resources/#/calls/README 17 | 18 | ## Standard Operating Procedures 19 | 20 | General guidance including best practices for project management of the Governance Working Group can be found in the [Standard Operating Procedures document](https://stacksgov.github.io/pm/#/sop). 21 | 22 | ## Licensing 23 | 24 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/pm/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 25 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/1-mtg-agenda.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: "Agenda: Create New" 3 | about: "Use this template to create a new meeting agenda." 4 | title: "Working Group Call #X" 5 | labels: mtg-agenda 6 | --- 7 | 8 | ## Meeting Details 9 | 10 | - **Date/Time:** Month Date, Year @ 4:00pm UTC / 12:00pm ET 11 | - **Location:** Link will be posted in the `#governance` working group channel [on Discord](https://community.blockstack.org/discord) shortly before the call. 12 | - **Moderator:** TBA 13 | 14 | The [Stacks Governance - Calls](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group) page contains a table of past calls, including a link to the agenda, recording, notes, and resources. 15 | 16 | ## Standup Updates 17 | 18 | **What happened over the past two weeks? Standup!** 19 | 20 | - What is everyone working on right now? 21 | - Any blockers? 22 | - What will happen over the next two weeks? 23 | 24 | ## Stacks Foundation Updates 25 | 26 | See issues with the label `mtg-stacksfoundation` for more info. 27 | 28 | [https://github.com/stacksgov/pm/labels/mtg-stacksfoundation](https://github.com/stacksgov/pm/labels/mtg-stacksfoundation) 29 | 30 | ## Action Items 31 | 32 | See issues with the label `mtg-action` for more info. 33 | 34 | [https://github.com/stacksgov/pm/labels/mtg-action](https://github.com/stacksgov/pm/labels/mtg-action) 35 | 36 | ## Discussion Items 37 | 38 | See issues with the label `mtg-discuss` for more info. 39 | 40 | [https://github.com/stacksgov/pm/labels/mtg-discuss](https://github.com/stacksgov/pm/labels/mtg-discuss) 41 | 42 | ## Miscellaneous Items 43 | 44 | Feel free to list out and add additional items below! 45 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Creative Commons Legal Code 2 | 3 | CC0 1.0 Universal 4 | 5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 12 | HEREUNDER. 13 | 14 | Statement of Purpose 15 | 16 | The laws of most jurisdictions throughout the world automatically confer 17 | exclusive Copyright and Related Rights (defined below) upon the creator 18 | and subsequent owner(s) (each and all, an "owner") of an original work of 19 | authorship and/or a database (each, a "Work"). 20 | 21 | Certain owners wish to permanently relinquish those rights to a Work for 22 | the purpose of contributing to a commons of creative, cultural and 23 | scientific works ("Commons") that the public can reliably and without fear 24 | of later claims of infringement build upon, modify, incorporate in other 25 | works, reuse and redistribute as freely as possible in any form whatsoever 26 | and for any purposes, including without limitation commercial purposes. 27 | These owners may contribute to the Commons to promote the ideal of a free 28 | culture and the further production of creative, cultural and scientific 29 | works, or to gain reputation or greater distribution for their Work in 30 | part through the use and efforts of others. 31 | 32 | For these and/or other purposes and motivations, and without any 33 | expectation of additional consideration or compensation, the person 34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 35 | is an owner of Copyright and Related Rights in the Work, voluntarily 36 | elects to apply CC0 to the Work and publicly distribute the Work under its 37 | terms, with knowledge of his or her Copyright and Related Rights in the 38 | Work and the meaning and intended legal effect of CC0 on those rights. 39 | 40 | 1. Copyright and Related Rights. A Work made available under CC0 may be 41 | protected by copyright and related or neighboring rights ("Copyright and 42 | Related Rights"). Copyright and Related Rights include, but are not 43 | limited to, the following: 44 | 45 | i. the right to reproduce, adapt, distribute, perform, display, 46 | communicate, and translate a Work; 47 | ii. moral rights retained by the original author(s) and/or performer(s); 48 | iii. publicity and privacy rights pertaining to a person's image or 49 | likeness depicted in a Work; 50 | iv. rights protecting against unfair competition in regards to a Work, 51 | subject to the limitations in paragraph 4(a), below; 52 | v. rights protecting the extraction, dissemination, use and reuse of data 53 | in a Work; 54 | vi. database rights (such as those arising under Directive 96/9/EC of the 55 | European Parliament and of the Council of 11 March 1996 on the legal 56 | protection of databases, and under any national implementation 57 | thereof, including any amended or successor version of such 58 | directive); and 59 | vii. other similar, equivalent or corresponding rights throughout the 60 | world based on applicable law or treaty, and any national 61 | implementations thereof. 62 | 63 | 2. Waiver. To the greatest extent permitted by, but not in contravention 64 | of, applicable law, Affirmer hereby overtly, fully, permanently, 65 | irrevocably and unconditionally waives, abandons, and surrenders all of 66 | Affirmer's Copyright and Related Rights and associated claims and causes 67 | of action, whether now known or unknown (including existing as well as 68 | future claims and causes of action), in the Work (i) in all territories 69 | worldwide, (ii) for the maximum duration provided by applicable law or 70 | treaty (including future time extensions), (iii) in any current or future 71 | medium and for any number of copies, and (iv) for any purpose whatsoever, 72 | including without limitation commercial, advertising or promotional 73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 74 | member of the public at large and to the detriment of Affirmer's heirs and 75 | successors, fully intending that such Waiver shall not be subject to 76 | revocation, rescission, cancellation, termination, or any other legal or 77 | equitable action to disrupt the quiet enjoyment of the Work by the public 78 | as contemplated by Affirmer's express Statement of Purpose. 79 | 80 | 3. Public License Fallback. Should any part of the Waiver for any reason 81 | be judged legally invalid or ineffective under applicable law, then the 82 | Waiver shall be preserved to the maximum extent permitted taking into 83 | account Affirmer's express Statement of Purpose. In addition, to the 84 | extent the Waiver is so judged Affirmer hereby grants to each affected 85 | person a royalty-free, non transferable, non sublicensable, non exclusive, 86 | irrevocable and unconditional license to exercise Affirmer's Copyright and 87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 88 | maximum duration provided by applicable law or treaty (including future 89 | time extensions), (iii) in any current or future medium and for any number 90 | of copies, and (iv) for any purpose whatsoever, including without 91 | limitation commercial, advertising or promotional purposes (the 92 | "License"). The License shall be deemed effective as of the date CC0 was 93 | applied by Affirmer to the Work. Should any part of the License for any 94 | reason be judged legally invalid or ineffective under applicable law, such 95 | partial invalidity or ineffectiveness shall not invalidate the remainder 96 | of the License, and in such case Affirmer hereby affirms that he or she 97 | will not (i) exercise any of his or her remaining Copyright and Related 98 | Rights in the Work or (ii) assert any associated claims and causes of 99 | action with respect to the Work, in either case contrary to Affirmer's 100 | express Statement of Purpose. 101 | 102 | 4. Limitations and Disclaimers. 103 | 104 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 105 | surrendered, licensed or otherwise affected by this document. 106 | b. Affirmer offers the Work as-is and makes no representations or 107 | warranties of any kind concerning the Work, express, implied, 108 | statutory or otherwise, including without limitation warranties of 109 | title, merchantability, fitness for a particular purpose, non 110 | infringement, or the absence of latent or other defects, accuracy, or 111 | the present or absence of errors, whether or not discoverable, all to 112 | the greatest extent permissible under applicable law. 113 | c. Affirmer disclaims responsibility for clearing rights of other persons 114 | that may apply to the Work or any use thereof, including without 115 | limitation any person's Copyright and Related Rights in the Work. 116 | Further, Affirmer disclaims responsibility for obtaining any necessary 117 | consents, permissions or other rights required for any use of the 118 | Work. 119 | d. Affirmer understands and acknowledges that Creative Commons is not a 120 | party to this document and has no duty or obligation with respect to 121 | this CC0 or use of the Work. 122 | -------------------------------------------------------------------------------- /sop.md: -------------------------------------------------------------------------------- 1 | # Stacks Governance - Standard Operating Procedures 2 | 3 | This document contains recommended best practices for managing various aspects of the Stacks governance initiative. 4 | 5 | 6 | 7 | - [Stacks Governance - Standard Operating Procedures](#stacks-governance---standard-operating-procedures) 8 | - [Get Involved](#get-involved) 9 | - [Additional Outlets](#additional-outlets) 10 | - [Governance Working Group Calls](#governance-working-group-calls) 11 | - [Governance Working Group Call Procedures](#governance-working-group-call-procedures) 12 | - [Preparing for a Call](#preparing-for-a-call) 13 | - [Hosting a Call](#hosting-a-call) 14 | - [Uploading Call Videos](#uploading-call-videos) 15 | - [Updating Resources Call Table](#updating-resources-call-table) 16 | - [Formatting Tips](#formatting-tips) 17 | - [Publishing Call Updates](#publishing-call-updates) 18 | - [Governance Working Group Resources](#governance-working-group-resources) 19 | - [GitHub Pages and Docsify](#github-pages-and-docsify) 20 | - [Licensing](#licensing) 21 | 22 | 23 | 24 | ## Get Involved 25 | 26 | From [Stacks Governance Update #1 - 4 March, 2020](https://github.com/stacksgov/updates/blob/master/updates/20200304-update-001.md): 27 | 28 | > Stacks governance is a community-run initiative! As such, it cannot work without your help, and without the input of as many community members as possible. You do not need anyone’s permission to get involved and contribute to the initiative. The #governance working group channel on [Stacks Discord](https://discordapp.com/invite/ny6wGkx) is a great place to begin getting involved, as many community members regularly share ideas, updates, and resources there. You can also find a number of topics under the [governance category](https://forum.stacks.org/c/Working-Groups/governance/) on the Stacks Community Forum which need your input. 29 | 30 | ## Additional Outlets 31 | 32 | More information about the Stacks Foundation and its mission can be found at the links below: 33 | 34 | - Website: https://stacks.org 35 | - Twitter: [@StacksOrg](https://twitter.com/StacksOrg) 36 | - Resources: https://stacksgov.github.io/resources 37 | - Project Management: https://stacksgov.github.io/pm 38 | 39 | ## Governance Working Group Calls 40 | 41 | Governance Working Group calls are held every other week, and follow the basic agenda format listed below: 42 | 43 | - A quick standup update from each attendee 44 | - Updates from the Stacks Foundation 45 | - Review of Action Items 46 | - Review of Discussion Items 47 | - Review of Miscellaneous Items 48 | 49 | The meeting agendas and various topics discussed can be found on GitHub, under the [issues tab](https://github.com/stacksgov/pm/issues) of the `stacksgov/pm` repository. There are labels for each issue based on the agenda categories, and the issues tab can be filtered by each label for review. 50 | 51 | - Meeting Agendas: [mtg-agenda](https://github.com/stacksgov/pm/labels/mtg-agenda) 52 | - Stacks Foundation: [mtg-stacksfoundation](https://github.com/stacksgov/pm/labels/mtg-stacksfoundation) 53 | - Action Items: [mtg-action](https://github.com/stacksgov/pm/labels/mtg-action) 54 | - Discussion Items: [mtg-discuss](https://github.com/stacksgov/pm/labels/mtg-discuss) 55 | 56 | > **Note:** When using GitHub, the word "issue" also means "topic", "item", or "idea". Issues are used to track individual discussion items, and labels are used to help categorize and group the issues. More information can be found in the [Mastering Issues](https://guides.github.com/features/issues/) guide from GitHub. 57 | 58 | The notes and resources from previous calls are stored in the `stacksgov/resources` repository, and listed in a table on the [Stacks Governance Resources - Calls Page](https://stacksgov.github.io/resources/#/calls/). 59 | 60 | ## Governance Working Group Call Procedures 61 | 62 | Below are the steps for setting up, hosting, and following up on a call. 63 | 64 | ### Preparing for a Call 65 | 66 | 1. Create a new agenda by opening an issue based on template 67 | - ideally this is done right after the last call, to give people enough time to add agenda items for the next meeting 68 | - example of the issue template on GitHub: 69 | 70 | ![Agenda Issue Template Example](sop-meeting-agenda-example.png) 71 | 2. Update the Date/Time to the future meeting date 72 | 3. Create an Event Time Announcer link to help with time zone conversions 73 | - Access the [Event Time Announcer form](https://www.timeanddate.com/worldclock/fixedform.html) from timeanddate.com 74 | - Name the event, e.g. `Stacks Governance Working Group Call #26` 75 | - Set the Event Location to `UTC` 76 | - Enter the Month, Day, Year, Hour, and Duration values based on `UTC` 77 | - Add a link to the result following the Date/Time in the issue 78 | - e.g. in Markdown format: `[time zone conversion](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Stacks+Governance+Working+Group+Call+%2326&iso=20201022T16&ah=1)` 79 | - example of the announcement after someone clicks on it: 80 | 81 | ![Event Time Announcer Example](sop-timeanddate-example.png) 82 | 4. Update the roles, or list TBA if unknown 83 | 5. Close the issue from the previous call (instructions below) 84 | - open the issue from the previous call 85 | - add a comment: "Closing in favor of #X" where #X is the issue number of the new agenda 86 | - click **Close issue** next to the comment button 87 | 6. Share the new issue in the `#governance` channel on Discord 88 | 89 | Reminders about the governance call and a link to the agenda should be shared in the `#governance` channel on Discord based on the following schedule: 90 | 91 | - After the new agenda is created 92 | - One week before the call 93 | - One day before the call 94 | - The day of the call 95 | 96 | > **Note:** do NOT post the link anywhere public, including on social media 97 | 98 | A sample post is included below, but feel free to modify based on current events and/or tag relevant people based on the issues! 99 | 100 | > Reminder that our next governance meeting is scheduled for next Thursday - agenda here: https://github.com/stacksgov/pm/issues/105 101 | > 102 | > In the meantime, please update your issues with any progress you've made! 103 | 104 | ### Hosting a Call 105 | 106 | **Moderator Responsibilities** 107 | 108 | Moderators act as the meeting host, which gives them additional abilities in the meeting software, and are responsible for stewarding the meeting. 109 | 110 | The basic flow of moderating a call: 111 | 112 | - Wait until 5-10 minutes past the hour, or at least until there is a reasonable quorum, before starting the call. 113 | - Quickly scan the names of all Zoom participants to make sure the names are correct and that nobody's phone number is displayed publicly. As moderator, you can rename a participant if necessary. 114 | - Notify everyone before starting the recording, and that the rest of the call will be public and on the record. 115 | - Click **Record** then **Record to the Cloud** before starting the meeting. 116 | - State the date, time and meeting number, followed by introducing yourself as the moderator. 117 | - Ask if there are any new attendees, and if anyone else would like to introduce themselves to the group. 118 | - Share your screen with the current meeting agenda, and proceed through each agenda item with the group. 119 | - At the end of the meeting, summarize all topics discussed, and post the summary to the meeting agenda issue on GitHub. 120 | 121 | Some helpful tips for being a moderator: 122 | 123 | - Keep an eye on the time. Don't spend more than 5-10 minutes max on any given topic. If the discussion of a particular topic goes over this amount of time, offer to reserve some time to continue discussing the topic at the end of the call, politely remind everyone that there are other items on the agenda to discuss, and introduce the next topic. 124 | - Let people speak freely, but feel free to cut someone off if they speak for more than a few minutes. Do so politely, and remind them that it's important that we give everyone a chance to share their thoughts. Suggest that, if they have more to say on this topic, they could write up their thoughts and post them to the forum and/or share them in the chat channel. 125 | - Try to keep the conversation focused on the present topic. Slight diversions are fine, but if the topic diverges too far from the current agenda item, bring it back on track by gently reminding the group of the question at hand - and offering to return to the new topic later, time-allowing. 126 | 127 | 139 | 140 | ### Uploading Call Videos 141 | 142 | A basic outline of the process is outlined below, however more details will be added at a later date. 143 | 144 | - Download files from Zoom 145 | - Upload files to Youtube Studio using the template below 146 | - Log into Youtube Studio and select the Stacks Governance channel 147 | - From the dashboard, click `CREATE` then `Upload videos` 148 | - Select the downloaded video file from Zoom 149 | - Fill in the information below while the video processes 150 | 151 | ```none 152 | Title: Stacks Governance Call #X [YYYY/MM/DD] 153 | Description: 154 | Agenda: [link to agenda issue] 155 | Links shared on call: 156 | - Link 1 157 | - Link 2 158 | Playlists: Stacks Governance Calls 159 | ``` 160 | 161 | - Set the visibility to Public 162 | - Publish the video 163 | - Save the Youtube link to add to the stacksgov/resources calls table 164 | - Share link in `#governance` discord channel 165 | 166 | > Note: It is really helpful to review the video, in particular, the very beginning and end. Make sure that there isn't too much silence or banter in the recording before the actual meeting begins. Trim the video if necessary. 167 | 168 | ### Updating Resources Call Table 169 | 170 | All governance working group calls are documented in a markdown-formatted table on the stacksgov/resources repository, and [displayed publicly via GitHub Pages](https://stacksgov.github.io/resources/#/calls/?id=governance-working-group). 171 | 172 | Updating this information requires making changes to the repository on GitHub, followed by submitting a pull request for the changes. The general procedure is: 173 | 174 | - Fork the stacksgov/resources repository 175 | - Make the changes to your forked version of the repository 176 | - Submit a pull request with your changes back to stacksgov/resources 177 | 178 | More information on the [markdown syntax](https://docs.github.com/en/github/writing-on-github/basic-writing-and-formatting-syntax) and [collaborating with issues and pull requests](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests) can be found in the linked GitHub tutorials. 179 | 180 | If you have any questions, feel free to reach out in the `#governance` channel of Discord, too! 181 | 182 | #### Formatting Tips 183 | 184 | The key element to understand when updating the content is the structure of a markdown table and a markdown link. 185 | 186 | Tables use a pipe `|` to separate data in columns, such that: 187 | 188 | ```none 189 | | Heading 1 | Heading 2 | Heading 3 | 190 | | --- | --- | --- | 191 | | Content 1 | Content 1 | Content 1 | 192 | | Content 2 | Content 2 | Content 2 | 193 | ``` 194 | 195 | Which produces: 196 | 197 | | Heading 1 | Heading 2 | Heading 3 | 198 | | --- | --- | --- | 199 | | Content 1 | Content 1 | Content 1 | 200 | | Content 2 | Content 2 | Content 2 | 201 | 202 | So to add a new row, we just have to match the number of columns: 203 | 204 | ```none 205 | | Heading 1 | Heading 2 | Heading 3 | 206 | | --- | --- | --- | 207 | | New Content | New Content | New Content | 208 | | Content 1 | Content 1 | Content 1 | 209 | | Content 2 | Content 2 | Content 2 | 210 | ``` 211 | 212 | Which produces: 213 | 214 | | Heading 1 | Heading 2 | Heading 3 | 215 | | --- | --- | --- | 216 | | New Content | New Content | New Content | 217 | | Content 1 | Content 1 | Content 1 | 218 | | Content 2 | Content 2 | Content 2 | 219 | 220 | For links, square brackets are used for the link text, followed by parentheses for the link destination. 221 | 222 | ```none 223 | This is [a link](https://stacksgov.github.io/resources) in markdown. 224 | ``` 225 | 226 | Which produces: 227 | 228 | This is [a link](https://stacksgov.github.io/resources) in markdown. 229 | 230 | ### Publishing Call Updates 231 | 232 | **Publisher Responsibilities** 233 | 234 | This person will create an official, high-level update for the community and general public summarizing the actions of the Stacks Governance Working Group. 235 | 236 | Ideally, this will be posted to the [Stacks Forum](https://forum.stacks.org/) within one week of the original meeting. Previous updates can be found in the [stacksgov/updates repository](https://github.com/stacksgov/updates). 237 | 238 | Once posted, the update should be shared with the community via the `#governance` category. Please make sure the update includes a link to the agenda and notes for the most recent call, as well as a brief update on each of the main initiatives the working group is working on. 239 | 240 | ## Governance Working Group Resources 241 | 242 | Working on the items above will require access to the related software and services, listed below. If you do not have access and would like to contribute, please reach out via the Stacks Discord server in the `#governance` channel. 243 | 244 | - [GitHub Repositories](https://github.com/stacksgov) 245 | - [YouTube Channel](https://www.youtube.com/channel/UCirhluDUpSPVMZQn210HETg) 246 | - Zoom Pro Account 247 | 248 | ## GitHub Pages and Docsify 249 | 250 | All content in the `resources` and `pm` repos are available on GitHub pages, and most links point to this website instead of forcing a user to navigate around GitHub. 251 | 252 | GitHub pages are updated whenever a change is pushed to the `master` branch of the repository. 253 | 254 | - resources: https://stacksgov.github.io/resources 255 | - pm: https://stacksgov.github.io/pm 256 | 257 | The content in the repository is automatically turned into a [web page via Docsify](https://docsify.js.org/#/). 258 | 259 | - all links must be absolute (i.e. start with https://) 260 | - configuration can be found in `index.html` for the repo, sample below 261 | 262 | Markdown pages are converted into a link without the extension, i.e. 263 | 264 | > `/interviews/interview-001.md` 265 | > becomes 266 | > `https://stacksgov.github.io/resources/#/interviews/interview-001` 267 | 268 | To directly link to a file in the repository, the `#` must be removed, i.e. 269 | 270 | > `/survey/20200213_community_call_001.pdf` 271 | > becomes 272 | > `https://stacksgov.github.io/resources/calls/20200213_community_call_001.pdf` 273 | 274 | ```html 275 | 276 | 277 | 278 | 279 | 280 | 281 | 282 | 283 | 284 |
285 | 294 | 295 | 296 | 297 | ``` 298 | 299 | ## Licensing 300 | 301 | This repository and all contributions herein are licensed under [Creative Commons Zero v1.0 Universal](https://github.com/stacksgov/pm/blob/master/LICENSE). Please note that, by contributing to this repository, whether via commit, pull request, issue, comment, or in any other fashion, **you are explicitly agreeing that all of your contributions will fall under the same permissive license.** 302 | 303 | 311 | --------------------------------------------------------------------------------