Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:planning
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
community:planning [2020/10/13 10:34] – [Project Administration/Management: Required Roles] demiankatz | community:planning [2021/03/10 16:45] – demiankatz | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Roles and Responsibilities ===== | ===== Roles and Responsibilities ===== | ||
- | This section lists roles and responsibilities that members | + | The contents |
- | + | ||
- | It is certainly possible for one person to fulfill many roles, and for some roles to be shared by multiple people; | + | |
- | + | ||
- | ==== Open Library Foundation: Required Roles ==== | + | |
- | + | ||
- | In order to form an SMLLC and join the OLF, the project needs to designate individuals to serve in these three roles: | + | |
- | + | ||
- | * Primary Manager - for the OLF's purposes, this is the primary point of contact within the Project for OLF Communications + Collaboration. | + | |
- | * Treasurer - this person manages or is deeply familiar with the finances of the project. | + | |
- | * Secretary - this person manages the minutes of the project including any resolutions required to document business with the OLF. This person also manages and maintains all contracts brokered and executed through the SMLLC on behalf of the project, and supports the activities of the Primary Manager and the Treasurer. | + | |
- | ==== Project Administration/ | + | |
- | + | ||
- | === Critical Administrative Roles === | + | |
- | + | ||
- | * Internationalization Manager - as part of the release cycle, coordinate the activity of volunteer translators to keep VuFind' | + | |
- | * Project Server Administrator - patch/ | + | |
- | * Dokuwiki | + | |
- | * Jenkins | + | |
- | * JIRA | + | |
- | * VuFind demo instance | + | |
- | * VuFind website (reverse proxy on top of GitHub pages) | + | |
- | * Project Software Administrator(s) - manage key software applications for the project. These include: | + | |
- | * Dokuwiki Administrator - use escalated privileges to manage Dokuwiki application; | + | |
- | * GitHub Administrator - use escalated privileges to manage GitHub resources (vufind-org community, releases, etc.) | + | |
- | * Jenkins Administrator - use escalated privileges to manage Jenkins application; | + | |
- | * JIRA Administrator - use escalated privileges to manage JIRA application, | + | |
- | * SourceForge Administrator - use escalated privileges to manage SourceForge resources (news feed, mailing lists, downloads). | + | |
- | * Release Manager - schedule releases, ensure that outstanding tasks are completed on schedule, and work through | + | |
- | + | ||
- | === Core Community Roles === | + | |
- | + | ||
- | * Committers / Code Reviewers - commit to the main vufind-org repositories and review/ | + | |
- | * Documentation Experts - maintain the project' | + | |
- | * Technical Support Experts - monitor incoming communication channels (mailing lists, Slack, JIRA tickets, etc.) and assist users who are encountering problems. | + | |
- | + | ||
- | === Communication Roles === | + | |
- | + | ||
- | * Community Call Host - plan monthly Community Calls (set agendas) and moderate/ | + | |
- | * Newsletter Editor - monitor ongoing development (pull requests, JIRA tickets, Community Calls, etc.) in order to maintain the activity lists for the monthly newsletter; an executive summary also needs to be written each month to highlight key developments. | + | |
- | * Project Advocates - present on behalf of VuFind at conferences, | + | |
- | * Summit Planners - take responsibility for planning annual conferences: | + | |
- | * Video Editor - edit tutorial videos, Summit outputs, etc.; polish/ | + | |
==== Decision Making ==== | ==== Decision Making ==== | ||
Line 54: | Line 12: | ||
OSS Watch' | OSS Watch' | ||
+ | ==== Regional Considerations ==== | ||
+ | |||
+ | Would it be possible/ | ||
+ | |||
==== Selection / Succession Planning ==== | ==== Selection / Succession Planning ==== | ||
Line 83: | Line 45: | ||
* Weighted input into decision-making/ | * Weighted input into decision-making/ | ||
* Do we need a formal mechanism for recognizing non-financial support (e.g. commitment to assign institutional resources to a particular role for a particular amount of time)? | * Do we need a formal mechanism for recognizing non-financial support (e.g. commitment to assign institutional resources to a particular role for a particular amount of time)? | ||
+ | * How can we recognize regional differences (currencies/ | ||
+ | * Options beyond membership model: | ||
+ | * Grant-seeking: | ||
+ | * Service-provision: | ||
+ | * Sale of content (e.g. books) -- how would we structure this, and how would we differentiate it from free offerings in a fair/useful way? Perhaps a "pay what you wish" model would be a viable option, but this would require infrastructure to set up. | ||
+ | * Donation solicitations -- many projects ask for donations on their download screen; would this be appropriate for us? Again, administration is a cost. | ||
---- struct data ---- | ---- struct data ---- | ||
---- | ---- | ||
community/planning.txt · Last modified: 2021/03/10 16:46 by demiankatz