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/12 15:24] – [Roles and Responsibilities] demiankatz | community:planning [2021/03/10 16:45] – demiankatz | ||
---|---|---|---|
Line 5: | Line 5: | ||
===== Roles and Responsibilities ===== | ===== Roles and Responsibilities ===== | ||
- | This section | + | The contents of this section |
- | 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. | + | ==== Decision Making ==== |
- | ==== Open Library Foundation: Required Roles ==== | + | 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" |
- | In order to form an SMLLC and join the OLF, the project needs to designate individuals to serve in these three roles: | + | OSS Watch' |
+ | ==== Regional Considerations ==== | ||
- | * Primary Manager - for the OLF's purposes, this is the primary point of contact within the Project | + | Would it be possible/ |
- | * Treasurer - this person manages or is deeply familiar | + | |
- | * Secretary | + | |
- | ==== Project Administration/ | + | |
- | * Committers | + | ==== Selection |
- | * 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' | + | |
- | * Internationalization Manager - as part of the release cycle, someone needs to coordinate the activity of volunteer translators to keep VuFind' | + | |
- | * 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. | + | |
- | * Project Advocates - some members of the community need to be willing to present on behalf of VuFind at conferences, | + | |
- | * 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 - someone needs to be responsible for scheduling releases, ensuring that outstanding tasks are completed on schedule, and working through the [[changelog: | + | |
- | * Summit Planners - some members of the community need to take responsibility for planning annual conferences: | + | |
- | * 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. | + | |
+ | How do we determine assignment of roles to individuals? | ||
===== Expenses ===== | ===== Expenses ===== | ||
Line 50: | Line 30: | ||
* 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