Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20210907
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
community_call:minutes20210907 [2021/09/07 13:08] – [1. Development Planning] demiankatz | community_call:minutes20210907 [2021/09/07 15:53] (current) – demiankatz | ||
---|---|---|---|
Line 46: | Line 46: | ||
During this meeting, participants worked on the "We Can If..." activity; see also [[https:// | During this meeting, participants worked on the "We Can If..." activity; see also [[https:// | ||
+ | |||
+ | === Highlights: === | ||
+ | |||
+ | == Challenge 1. Project leadership should be more distributed (bottleneck/ | ||
+ | |||
+ | Possible Actions: | ||
+ | * Communication plan related to fundraising which highlights the value of community participation/ | ||
+ | * Fundraising for increased project independence (realistically: | ||
+ | |||
+ | == Challenge 2. Documentation can not be all things to all people; how do we balance keeping it evergreen vs. having very clear, specific examples? == | ||
+ | |||
+ | Possible Actions: | ||
+ | * Investigate whether Dokuwiki contains a plug-in for alerting to old/ | ||
+ | * Investigate whether Dokuwiki contains a mechanism for page ownership, so people can “own” pages and be responsible for revisions, keeping things up to date, etc. | ||
+ | * Even if no automated mechanism exists, some of this could be done manually using pages listing other pages in need of attention and assigned owners. | ||
+ | * Form a group to develop a documentation maintenance policy. | ||
+ | * Gather analytics on usage of the wiki (add Matomo, etc.) | ||
+ | |||
+ | == Challenge 3. Video editing tends to get backlogged == | ||
+ | |||
+ | Possible Actions: | ||
+ | * Set up video editing project in GitHub. | ||
+ | * Column for pending work (with link to files) | ||
+ | * Column for in process (assign card to person) | ||
+ | * Solicit more volunteers if a system is prototyped and works well. | ||
+ | |||
+ | == Challenge 4. Community call participation could be significantly higher == | ||
+ | |||
+ | Possible Actions: | ||
+ | * Look at past attendees, reach out to occasional contributors to learn why they do not visit more frequently. | ||
+ | * Consider a survey about timing, content, etc. | ||
+ | * Marketing: clarify the purpose/ | ||
+ | * Encourage users to visit the call to discuss support questions, feature suggestions, | ||
+ | * New communication channels for advertising call? Not just listservs? | ||
+ | |||
+ | == Challenge 5. There are relatively few technical contributors who contribute large amounts of code and who have a comprehensive understanding of the very large code base == | ||
+ | |||
+ | Possible Actions: | ||
+ | * Reaching out to hosting companies during fundraising phase. | ||
+ | * "Good first issue" highlighting for onboarding; in conjunction with Hacktoberfest? | ||
+ | * Reach out to existing users to contribute their local features/ | ||
+ | * Even consider looking at published forked code bases from other users to propose/ | ||
+ | * Develop a more comprehensive/ | ||
==== 4. Other Topics? ==== | ==== 4. Other Topics? ==== | ||
+ | None this month. | ||
===== Next Call ===== | ===== Next Call ===== | ||
Line 54: | Line 98: | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
community_call/minutes20210907.1631020084.txt.gz · Last modified: 2021/09/07 13:08 by demiankatz