Line 124: | Line 124: | ||
'''Lunch:''' TBD | '''Lunch:''' TBD | ||
''computercolin: | ''computercolin: Only for Saturday. Something to keep costs down (or have participants pitch in and get something nice).'' | ||
'''Dinner:''' | '''Dinner:''' | ||
''computercolin: would be cool to have a dinner outing. Budget may only pay for outside-experts (size?)'' | ''computercolin: would be cool to have a dinner outing. Budget may only pay for outside-experts (size?)'' | ||
== Infastructure / Communication == | == Infastructure / Communication == |
Revision as of 08:07, 3 August 2010
This is the main page for the Etherpad FAD, which is a FAD focused on Etherpad.
Background: EtherPad was a high-performance web-based collaborative document editor, launched in 2008 from etherpad.com. It was acquired by Google during the development of Google Wave, and the service's code base was open-sourced. Several websites now run an EtherPad service and there is interest in making private installs (such as one for the Fedora Project) easier to create.
Purpose
- Our purpose is to...
- Expose EtherPad, and its source code, to new eyeballs
- Identify requirements for making EtherPad more distributable (Yum-friendly?)
- Repackage EtherPad in a consistent, Java standard, portable way
- In addition, we will attempt to complete the following secondary goals as time allows:
- Create a EP web-config interface -- easier to deploy EP
- Document EP
Detailed Work Items & Final Attendees
To be filled in.
Planning Prerequisites
See the How to organize a FAD list; you can keep your to-do list here.
Decide on locationOlin College, Needham MA- Work out budget
- Decide on dates
- Arrange Facilities
- List Resources
- Be Somewhat Structured
- Arrange Lodging
- Arrange Refreshments
- Arrange a Social Event
- Add other action items here
Plan
Location
Olin College, 1000 Olin Way, Needham MA USA
Venue
Milas Hall atrium, hopefully. Nice space, we can get some tables and chairs it would be perfect for hacking. Plus there are some nooks around for team stuff.
computercolin: also considers trying to put the FAD someplace more public to the Olin community (so they can't help joining!)
Date
October, 2010 FIXME Still Tentative
- October 2nd: Pre-FAD
- Afternoon/evening
- May collaborate/tele-hack with Euro devs. Morning/early-afternoon preferable
- October 8-9th(-10th?): FAD
- Friday evening w/ Dinner
- Saturday lunch and dinner
- Sunday: Colin will personally make you breakfast if you're still here!
computercolin: Some conflicts:
- Weekend of 15th is family weekend
- Weekend of 22th is admissions open-house
- Weekend of 22th also Ontario Linux Fest
- 25th is my birthday and I intend to be... busy ;)
computercolin: If we want pre-Ontario, gotta be weekend of Oct 1st or Oct 8th
Schedule
- Participants arrive Friday (TBD) [afternoon | evening]
- Introductions
- Hacking introspection
- Outline hackathon (from introspection). Determine useful roles of participants.
- Presentation on OSS
- Hacking
- Another non-hack session (presentation, game, Q&A?)
- Participants leave late Saturday / Sunday morn (if they're really hard-core)
Eating interspersed.
computercolin: Think we could do a most-of-night (all-night?) hack session one of the nights. Both, probably too much.
Skills needed
- Java application packaging
- Javascript/java/scala decipherment
- framework expertise in jetty, Comet, AppJet or Rhino would be helpful
- also some mysql or apache derby
- infrastructure deployment
- software project management
- code (re)architecture
- developer documentation / API creation
- Malleable mind to fill (this list look intimidating? come learn something, hear war stories, see what this web-service, Comet, open-source, computer stuff is all about!)
People
- Colin Zwiebel (Needham, MA) - Organizer (it appears) - developer, Oliner, Will be there
- Find us some Java Propeller-heads
- Snag some cool space at Olin
- Get some awesome Oliners (not hard)
- Make sure everyone learns something and has fun
- Mel Chua (Raleigh, NC) - QA implementation - Can probably come if the event occurs, if my schedule is free.
- Ticket tracker setup (move this to fedorahosted.org?)
- Collect all existing bugs/enhancement requests and get them written and triaged properly
- Test case/results system implementation
- Write and execute first round of test cases, starting with a smoke test, then moving to focus on scaleability, cross-platform/browser testing
- QA infrastructure experimentation (probably looking at Mozilla's tools for starters)
- Andy Pethan (Needham, MA) - Attendee/hacker/facilitator - developer, Etherpad fanboy Will be there
- Sebastian Dziallas ( Needham, MA) - Fedora Packager - developer, packager Will make it
- DJ Gallagher (Boston, MA) - Java Propeller-head - dev, documentation Will probably come
- Name (location) - role - about/skills Confirmed? (Y/N)
- Name (location) - role - about/skills Confirmed? (Y/N)
- others?
Other considerations
- Contributor V can offer a living room for evening social gatherings.
- Contributor W has a car and is willing to do airport pick-ups.
- Contributor X needs as much advance notice as possible.
- Contributor Y has a schedule that is better on Fridays than on Tuesdays, and prefers weekend times after 4:28 AM.
- Contributor Z is allergic to peanuts.
Logistics
Snacks/Beverages: TBD
computercolin: We'll send out a survey to the interested as we get closer. Will be in budget.
Lunch: TBD
computercolin: Only for Saturday. Something to keep costs down (or have participants pitch in and get something nice).
Dinner:
computercolin: would be cool to have a dinner outing. Budget may only pay for outside-experts (size?)
Infastructure / Communication
- Projector in room / borrow from Olin IT
- Borrow video camera for streaming video / screencast
Budget
If you want funding from Red Hat, ask the Community Architecture team. If you can find other ways to fund your FAD, that's great too!
Contributor | Dept | Arrv | Dept | Arrv | Cost |
---|---|---|---|---|---|
Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
Name | Travel to FAD, departure | Travel to FAD, arrival | Travel from FAD, departure | Travel from FAD, arrival | Ticket cost |
- Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
- Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
- link to hotel room booking website, if applicable
- Space: $C for renting space to hack in, if applicable
- address and travel details for the space
- Supplies: $D for anything else you may need
- item
- item
- item
Total budget: $A+B+C+D