Skip to end of metadata
Go to start of metadata
Date
Attendees
Goals
- Start defining workplan for 2017-2018
Discussion items
Time | Item | Who | Notes |
---|
| Introductions | All |
|
| Workplan for 2017-2018 | All | See ideas from TAC 2017-09-15 Meeting notes - Provisioning / system administration
- Specifically on configuring HTTPS
- Existing documentation is too Apache specific and not AS specific enough
- Plugins
- Needs improved general documentation on how to develop/use plugins
- Sorts of things you can do with plugins
- Examples of what people have done
- How to configure plugins
- API
- Autogenerated documentation is not sufficient
- Needs examples of what a specific record result should look like
- Mapping
- Need EAD documentation on which elements map to which AS fields
- Existing maps are out of date and difficult to find
- Consolidate and improve existing technical documentation
- Documentation on how to add documentation
- Who creates documentation
- Process for submitting new documentation (pull requests)
- Consider having its own GitHub repository
- Could encourage more community submissions
- Separates development tasks from documentation tasks
- Will bring this idea to the next TAC meeting
|
| Upcoming Focus |
| Where we see each falling in terms of priority, and whether they could be done on this subteam or would need a separate ad hoc group - HTTPS
- We seem to have enough people familiar with this to tackle ourselves
- Might be able to make small contributions right away
- Plugins
- Same for plugins, we have a few people who can contribute
- API
- Might need more input from developers on this (or just more people in general)
- Updating and relocating mapping
- Need input from migrations team
|
| Next Meeting |
| Late October or early November |
Action items
- Trevor Thornton will write brief rationale for moving tech docs to its own Github repo