From Fedora Project Wiki

By the numbers

  • Non-free-software libraries changed to free alternatives: 1 (thanks Sam)
  • New packages created: 7+ (TODO)
    • I listed 7 on my blog there are probably more
    • Double if you count things like F13/14 and 32/64
    • Sanselan
    • mchange-commons
    • rhino-appjet
    • yuicompressor
    • compat-scala
  • Dependencies tracked down (already in repos): 17+
    • dnsjava-2.0.6.jar -> dnsjava
    • jbcrypt-0.2.jar -> jBCrypt
    • jcommon-1.0.15.jar -> jcommon
    • jfreechart-1.0.12.jar -> jfreechart
    • activation.jar -> classpathx-jaf
    • commons-lang-2.4.jar -> jakarta-commons-lang
    • derby- -> derby
    • mail.jar -> javamail
    • servlet-api-2.5-20081211.jar -> tomcat6-servlet-2.5-api
    • tagsoup-1.2.jar -> tagsoup
    • java_uno-3.2.0.jar ->
    • juh-3.2.0.jar ->
    • jurt-3.2.0.jar ->
    • ridl-3.2.0.jar ->
    • unoil-3.2.0.jar ->
    • commons-io-1.4.jar -> jakarta-commons-io
    • commons-fileupload-1.2.1.jar -> jakarta-commons-fileupload
  • Lines of code to make C3P0 lib build with Java 1.6: tons (TODO) (thanks Crawf)
  • Licences inspected: plenty (TODO) some of many (thanks Spot, Jon, DJ, SDZ)

The Pitch

Oliners (who don't know Java/Scala/OSS)

Etherpad. You know it, you love it, you miss it. Why don't you come work on it? Thats right, EtherPad is now Open Source software, and it needs some work.

October 8-10th we're hosting a Fedora Activity Day centered around EtherPad. We'll be working on packaging of the software. That covers technologies like J2EE, Scala, server-side-javascript, javascript, release engineering, and more. If any of those sound exciting, we'd like you to learn about it! We invite you to our hacking and to a few "intro sessions" throughout the weekend:

  • Friday, October 9th @5pm - Intro to OSS development for Olin Students

Java / Scala / JS / Release Engineers

Etherpad is the pinnacle of online, collaborative text editing. If you're not familiar with EtherPad, take a look at this video. Buuut the EtherPad code-base isn't exactly in a packageable state, as demonstrated by SDZ, here. We would like to package EtherPad and package it correctly.

October 8-9th(plus sleepless, greet the 10th nigh session), join us as we dissect EtherPad and mold it into a happy, best-practices following package. We'll get our hands dirty with Scala, build systems, server-side-javascript, and a whole host of other fun technologies. We'll hack along-side European EtherPad contributors, enjoy a delicious Indian brunch, and learn/teach fascinating stuff.

List Resources

This event doesn't need many resources, luckily. We aren't using any hardware toys. Attendees bring their computers and thats pretty much the end of the story. Few things:

  • Tables and Chairs: CC209 has them
  • Projector: CC209 has one
  • Digital Cameras: Attendees will bring
  • Video Camera: Colin will borrow one from IT
  • Fedora Infrastructure for EtherPad installation


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

Event Facility

Floor Plan

Computercolin olin crescent room diagram.png

We have 209 and 211


Computercolin etherpad fad olin cc209 reservation.png

The Task

Notes from Victor Vasilyev


I've successfully compiled and launched the project on the Fedora 13, and can confirm that is working well. But, I've also noticed that the Google wave has a bit more facilities  :-(

After a brief researching of the project I've opinion that you'll have a lot of the tasks that should be completed before release of the project for the Fedora Linux distribution will happen. I see at least the following tasks:

  • Decomposing of the project, and selecting of all "internal" and "external" components.
  • Replacing the all third-party components with the requirements for each component to have a list of all external dependencies.
  • Providing of the RPM packages for required third-party components that are not in Fedora yet (if any).
  • Dividing of all external dependencies into build-time and run-time dependencies.
  • Sorting of all "internal" components by their languages, and avoiding unneeded languages to simplify the project.


I think, you should also decide to use a build system that is "usual" for Java (e.g. Ant, Maven, etc.) instead of Bash-scripts.

...And, finally, will be better to see a components diagram for the project (e.g. UML components diagram) that might explain a role of each component, and their dependencies.

Planning Archives


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 In progress
  • Decide on dates
  • Arrange Facilities (reservation)
  • List Resources
  • Be Somewhat Structured (Arguable =P)
  • Arrange Lodging (Attendees will have to cover themselves)
  • Arrange Refreshments
  • Arrange a Social Event
  • Add other action items here

Detailed Work Items & Final Attendees

  1. Inventory attendees and skill sets
  2. Create plan of action
  3. TODO: Fill in ...
  4. Get Fedora EtherPad package approved
  5. Deploy package to Fedora Infastructure

Getting up on Fedora Infastructure

Discussion on Educating New People -- Asheesh

Thanks Greatly Asheesh (Paul Proteous) Laroia!