IEEE.org     |     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit 790426db authored by Beth Hancock's avatar Beth Hancock 🌿
Browse files

Update 20220329-doc-cur-mtg-notes.md -

parent 8fbc9aac
......@@ -10,7 +10,7 @@ https://communityag.leadingbit.com
**Meeting Recording:**
This [meeting]() was recorded in BigBlueButton. BigBlueButton supports playback in Chrome and Firefox.
## Agenda
......@@ -31,20 +31,25 @@ https://communityag.leadingbit.com
**Please add your name and affiliation (work and volunteer)**
*
*
* Beth Hancock - Leadingbit Solutions for IEEE SA OPEN
* Nuritzi Sanchez - Leading the T/PgM team for Flutter & Dart at Google
*
## Meeting Notes
* Need to decide where to add this new page. https://opensource.ieee.org/community-handbook
* Added to the landing page: "This handbook is the central repository for how we operate the IEEE SA Open Community. Learn more about how we use the handbook and how to contribute to it: https://opensource.ieee.org/community-handbook/community-processes/handbook-guidelines/"
* During this meeting we updated https://opensource.ieee.org/community-handbook/community-processes/handbook-guidelines/-/blob/main/README.md
* Next meeting: Continue working on [Handbook guidelines](https://opensource.ieee.org/community-handbook/community-processes/handbook-guidelines/-/blob/main/README.md). Write general page guidelines and have an explicit call out about policies (e.g. keeping a changelog for a policy vs not for ).
* Nuritzi will be in Germany April 16 - May 29th. Would like to move the meeting during those dates to a more EMEA-friendly zone (8 am PST or earlier would be preferable).
Previpous Meeting Notes:
## Previous Meeting Notes:
* We should create a "How to create a Handbook entry page" with a link to template.
* There is an IEEE SA Group that would like to start using the handbook to document various practices they've created. It would be helpful for us to create a general handbook page format.
* We think it would be helpful for pages to indicate who the audience is for that specific handbook page. For example, some may be for developers, others may be for marketing folk. In general, we want to encourage the community to give as much context as possilbe around what they are creating.
* We think it would be helpful for pages to indicate who the audience is for that specific handbook page. For example, some may be for developers, others may be for marketing folk. In general, we want to encourage the community to give as much context as possible around what they are creating.
* This seems like it's more best practices around writing pages, not general format.
* It's more similar to policy docs. Some have revision histories, and in general there is more rigor to documenation for policy-minded organizations like IEEE SA Open. Some pages will need to have review dates as a function of the working group no longer being active, for example.
* Next time we meet: Consider writing the "How to add a new page to the handbook" page. Some information on this page may be helpful: https://about.gitlab.com/handbook/
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment