Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

When

17-18 December 2018
10:00am - 4:00pm each day

Remote Participation

https://duraspace.zoom.us/my/fedora

Where

Johns Hopkins University, Baltimore, MD

Arriving by Metro/Bus

Homewood Shuttle

Purple Charm City Circulator

Arriving by Car

Campus Visitor Parking 

Lodging

Closest hotel is the Inn at the Colonnade


Meals

Morning coffee and snacks will be provided.

There are many wonderful lunch options around campus,

What to Bring

A laptop for hackathon activities

Attendees

If you plan to attend the meeting, please add your name below.

Agenda/Presentations

The theme of this Fedora user's group meeting is improving Fedora based on experience in the field.  With more institutions having experience with Fedora 4+ in production, or interested in adapting fedora 4+, now is an excellent opportunity to translate this experience into improvements in Fedora.  In that context, the format of this meeting will be a series of presentations, updates, and/or discussions, followed by a hackathon with the goal of producing code, design, or documentation.

Possible discussion/presentation/update topics

(please add items here.  Feel free to comment or add your name if a topic is of particular interest)

  • 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.

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. 

Schedule

(proposed.  Feel free to add a presentation to the calendar, or ad it to the discussion/presentation topic list above)

Day 1

Time

Topic

Presenter

10:00 - 10:30Welcome and Introductions


10:30 - 11:00Update from UMD

TBD

11:00 - 11:30

Presentations


11:30 - 12:00

Presentations


12:00 - 1:15Lunch Break 
1:15 - 1:45Presentations


1:45 - 2:15Presentations


2:15 - 2:30Break 
2:30 - 3:00Discussion and Hackathon planning


3:00 - 3:30Discussion and Hackathon planning
3:30 - 4:00Discussion and Hackathon planning 


Day 2

Time

Topic

Presenter

10:00 - 10:30Hackathon launch


10:00 - 11:30

Hackathon


12:00 - 1:15Lunch Break 
1:15 - 2:15Hackathon


2:15 - 2:30Break 
3:00 - 3:30Hackathon planning
3:30 - 4:00Wrap up, report out, and next steps 
  • No labels