From Fedora Project Wiki

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

  1. Our purpose is to...
    • Expose EtherPad, and its source code, to new eyeballs
    • Develop (and then document) understanding of the source code
    • Identify requirements for making EtherPad more distributable (Yum-friendly?)
  2. In addition, we will attempt to complete the following secondary goals as time allows:
    • secondary goal
    • secondary goal
    • secondary goal

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 location Olin 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

Date

October Something Or Other, 2010 FIXME (preferably before the Ontario Linux Fest?)

Schedule

  • Participants arrive at THIS_TIME_AND_DATE
  • Schedule item
  • Schedule item
  • Schedule item
  • Participants leave at THIS_TIME_AND_DATE

Skills needed

  • javascript/java/scala decipherment
    • framework expertise in jetty, Comet, AppJet or Rhino would be helpful
    • also some mysql or apache derby
  • software project management
  • code (re)architecture
  • developer documentation / API creation
  • packaging
  • infrastructure deployment

People

  • 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) - developer, Etherpad fanboy Will be there
  • Sebastian Dziallas ( Needham, MA) - developer, packager Will make it
  • DJ Gallagher (Boston, MA) - dev, documentation Will probably come
  • Name (location, role) Confirmed? (Y/N)
  • Name (location, role) 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: Details go here.

Lunch: Details go here.

Dinner: Details go here.

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
  1. Travel: $A for airfare, bus, train, etc. funding needed to get attendees to the FAD
  2. Housing: $B for hotel, etc. needed to have attendees sleep during the FAD
    • link to hotel room booking website, if applicable
  3. Space: $C for renting space to hack in, if applicable
    • address and travel details for the space
  4. Supplies: $D for anything else you may need
    • item
    • item
    • item

Total budget: $A+B+C+D