...
- The Public Access Submission System (PASS) JHU's experience and pain points
- Link is to a google doc with various notes from our experience. This would be the basis of a presentation and one of many inputs for possible hackathon topics
- Fedora from a sysadmin perspective - configuring, deploying, or maintenance (e.g. backup/restore).
- Performance - experience reports, workarounds, and wins.
- Roundtable discussion: Making the case for Fedora. Despite some past efforts to do this, the cannot hurt to reconsider the project's goals and why decisions have been made. If potential adopters are not on board with the rationale behind, for example, the adoption of RDF and LDP, it will continue to be difficult to convince them that the extra overhead those choices entail is worth it.
Hackathon tasks
TBD. This will be determined by a discussion at the end of the first day, based on shared interests, experience, and practical consideration. The goal at the end of the first day will be to produce a concrete set of tasks for individuals or teams to accomplish on the second day. Ideally, these tasks will be inclusive of the talent in the room. Possible areas include software development, design, or documentation updates.
...
Time | Topic | Presenter |
---|---|---|
10:00 - 10:30 | Welcome and Introductions | |
10:30 - 11:00 | Update from UMD | |
11:00 - 11:30 | Update from NLM | TBD |
11:30 - 12:00 | ||
12:00 - 1:15 | Lunch Break | |
1:15 - 1:45 | Fedora 5 Update | |
1:45 - 2:15 | Presentations | |
2:15 - 2:30 | Break | |
2:30 - 3:00 | Discussion and Hackathon planning | |
3:00 - 3:30 | Discussion and Hackathon planning | |
3:30 - 4:00 | Discussion and Hackathon planning |
...