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 revisionNext revisionBoth sides next revision | ||
community:planning [2020/10/12 15:18] – [Project Administration/Management: Required Roles] demiankatz | community:planning [2020/11/02 13:48] – [Project Administration/Management: Required Roles] demiankatz | ||
---|---|---|---|
Line 6: | Line 6: | ||
This section lists roles and responsibilities that members of the VuFind Community will need to fulfill in order to keep the project functional. | This section lists roles and responsibilities that members of the VuFind Community will need to fulfill in order to keep the project functional. | ||
+ | |||
+ | It is certainly possible for one person to fulfill many roles, and for some roles to be shared by multiple people; this list is simply intended to highlight all key activities that need to be accounted for. | ||
==== Open Library Foundation: Required Roles ==== | ==== Open Library Foundation: Required Roles ==== | ||
Line 16: | Line 18: | ||
==== Project Administration/ | ==== Project Administration/ | ||
+ | === Critical Administrative Roles === | ||
+ | |||
+ | * Community Manager - maintain code of conduct and other community standards; facilitate/ | ||
+ | * Internationalization Manager - as part of the release cycle, coordinate the activity of volunteer translators to keep VuFind' | ||
* Project Server Administrator - patch/ | * Project Server Administrator - patch/ | ||
* Dokuwiki | * Dokuwiki | ||
Line 24: | Line 30: | ||
* Project Software Administrator(s) - manage key software applications for the project. These include: | * Project Software Administrator(s) - manage key software applications for the project. These include: | ||
* Dokuwiki Administrator - use escalated privileges to manage Dokuwiki application; | * 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; | + | * GitHub Administrator - use escalated privileges to manage GitHub resources (vufind-org community, releases, etc.) |
- | * JIRA Administrator - use escalated privileges to manage JIRA application. | + | |
+ | * JIRA Administrator - use escalated privileges to manage JIRA application, including license renewals through Atlassian. | ||
* SourceForge Administrator - use escalated privileges to manage SourceForge resources (news feed, mailing lists, downloads). | * SourceForge Administrator - use escalated privileges to manage SourceForge resources (news feed, mailing lists, downloads). | ||
- | * Release Manager - someone needs to be responsible for scheduling | + | * Release Manager - schedule |
- | * Committers / Code Reviewers - some members of the community need to be able to commit to the main vufind-org repositories and to review/ | + | |
- | * Community Call Host - someone needs to plan for monthly Community Calls (set agendas) and moderate/ | + | |
- | * Documentation Experts - some members of the community need to maintain the project' | + | |
- | * Newsletter Editor - someone needs to 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. | + | |
- | * Technical Support Experts - some members of the community need to monitor incoming communication channels (mailing lists, Slack, JIRA tickets, etc.) and assist users who are encountering problems. | + | |
+ | === 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 ==== | ||
+ | |||
+ | The list of roles above does not explicitly account for decision-making within the project. How do we set priorities, make architectural decisions, etc.? Does the project need a "lead architect" | ||
+ | |||
+ | OSS Watch' | ||
+ | ==== Regional Considerations ==== | ||
+ | |||
+ | Would it be possible/ | ||
+ | |||
+ | ==== Selection / Succession Planning ==== | ||
+ | |||
+ | How do we determine assignment of roles to individuals? | ||
===== Expenses ===== | ===== Expenses ===== | ||
Line 45: | Line 73: | ||
* Emergency fund (to hire temporary staff to aid in a leadership transition) | * Emergency fund (to hire temporary staff to aid in a leadership transition) | ||
+ | * Grants/ | ||
* Server fees (if we switch from institution-supported project resources to cloud-hosted services) | * Server fees (if we switch from institution-supported project resources to cloud-hosted services) | ||
+ | * Training costs (to hire trainers and cover other expenses for ongoing training programs) | ||
+ | |||
+ | ===== Support ===== | ||
+ | |||
+ | The project needs a formal mechanism for receiving support. Some questions to discuss: | ||
+ | |||
+ | * Do we need to define specific levels/ | ||
+ | * What are the benefits of support? | ||
+ | * A listing on the website? | ||
+ | * Increased/ | ||
+ | * Privileged access to certain project roles? | ||
+ | * 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)? | ||
+ | * 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