- Welcome, Ryan Steans!
- How can we use Ryan's time to get more resources for documentation?
- We have some infrastructure in place for tracking versioning, but it's not ideal. Could we improve the template to better handle versioning?
- Can we hire someone to write some documentation? What would that look like? (Discussion ensued.)
- Could they co-locate and organize existing documentation?
- Better structure or layout for documentation?
- Lots of enthusiasm for hiring someone who really knows jekyll
- Could we hire someone to organize a documentation sprint?
- Could we get some training for people about writing documentation?
- Can we host a "Write the Docs" event? How about a virtual event where we:
- Identify top priorities
- Identify who has the knowledge
- Pair (or triple) them up with someone who can interview them and take notes – or maybe it's a webinar?
- Process those notes after into digestable docs
- Proposal:
- Let's announce an event – what does it look like?
- Outcomes: Actual documentation
- Welcome, Ryan Steans!
- Potential uses for the financial support
- restructure jekyll theme especially for left hand menu structure, addressing versioning across multiple gems, generalized organization of the site
- moving existing documentation spread across all the wikis to move the documentation to the centralized samvera.github.io site
- writing documentation (this requires some expertise that may present an obstacle)
- Use of Ryan's time
- Organize short term focused documentation effort that can be used as a prototype for bi-annual documentation efforts
- Option 1: Webinar style with a primary interviewer but that anyone in the community can attend and ask questions (would need to be shorter for Webinar part and use followup meetings for clarification and document writing)
- Option 2: Paired developer - documentor virtual sprint – (perhaps 1-3 days in length)
- For both options,
- there needs to be a prioritization process of which docs to write that includes the general prioritization of the working group AND voting by the community
- determine the number of features/processes that we can document during this effort
- there needs to be an identification process of the developer expert for that area and an appropriate documentor to capture the knowledge in documentation
- Organize short term focused documentation effort that can be used as a prototype for bi-annual documentation efforts
- Potential uses for the financial support
Manage space
Manage content
Integrations