This is a listing of Technology Team projects:
A number of projects were established to support Open Source Bridge. If you would like to help with them, read the descriptions below, familiarize yourself with the source code and technical documentation, and participate on the mailing list with suggestions, offer patches and attend code sprints.
The conference sessions, sessions, schedules and speaker profiles are managed by OpenConferenceWare, a general-purpose open source platform that we developed which we and other conferences use:
The servers are setup and managed using recipes. You do NOT need to have root access to the production servers to assist with writing or improving recipes, you should read the instructions to learn how they work, setup your own virtual machine and submit patches:
The web applications use a common set of CSS styles, including OpenConferenceWare, WordPress, MediaWiki and DokuWiki:
The conference blog uses WordPress:
The conference's attendee wiki uses MediaWiki:
This conference public planning wiki uses DokuWiki:
There are Bittorrent files shared by the servers:
torrent account on the production servers and run from the osbp_bittorrent directory. See the source code above or run rake help from the checkout for usage instructions.torrent@hawthorne:~/osbp_bittorrent/files/ using a program like rsynctorrent@opensourcebridge.org accountosbp_bittorrent directoryrake restart to have the server use the new filesosbp_bittorrent directory and run rake pull restart, which will pull the files from the opensourcebridge.org server to the local stash and restart the Bittorrent server.Staff should be able to issue complimentary tickets to volunteers, speakers, raffle winners, etc.
People should be able to purchase tickets so they can attend the conference. The system to support this can be complex or simple. A complex system could be a themeable, general-purpose purchasing system that uses API calls to a credit card merchant account and maintains its own inventory and accounting history. At the other extreme, we may be able to just use a simple web page to list the ticket types and use “buy now” links to to a 3rd party hosted purchasing solution to complete the transaction, using a vendor like Google Checkout, Amazon Checkout, or Paypal. We'd also like to have all or most of those that purchase a ticket to fill out a pre-conference attendee demographics survey, which is another project.
Conference attendees should be able to fill out a demographics survey before the event so the organizers have a better idea of what kind of people are attending, with what kinds of skills and interests, from what location, etc. We'd like to have all or most of those that purchase a ticket fill out this survey. However, we will also have attendees that are not going to purchase tickets (e.g., volunteers and speakers) and they will need to be able to fill out this survey too.
UPDATE 2010-03-03: The ticket purchasing and pre-conference survey systems have been combined, we're likely going to use Eventbrite. Work is underway to provide these.
There are projects we would like to start. At this point, we're not sure of the details and need help to define requirements and implement. To help, please participate on the mailing list in discussions and offer suggestions regarding these projects.
Audio for the 2009 event needs to be processed and published. This is an important and valuable activity because much of the content is still current and worth sharing.
These projects require no further work:
UPDATE 2010-02-11: A decision was made to use Highrise as a CRM. If it works out, great; if it doesn't, we'll restart the research.
Interactions between sponsors/vendors/etc and Open Source Bridge should be tracked and their contact information captured. We'd like to have people that are either familiar with open source CRM tools (or an interest in researching them thoroughly) survey the options and report back what these tools do to help make the conference organizers lives easier. We'll then need advice on the best way to set these up and use them.