WebOSroundup Hackathon

From WebOS101

Jump to: navigation, search

Contents

Introduction

The webOSroundup Hackathon is a one-day event where the webOS community comes together to create an open source app in a single day. The first event was planned for August 21st, 2010.

Beta ToDo List

  • No error message when a duplicate account name is registered
  • Offline storage
  • Reading articles inside the app
  • Help documentation
  • Sharing / Social Networking
  • Translation
  • Encryption and security
  • Style validation message on add bookmark errors

API Key

During development, the following shared ReadItLater API key can be used: 17eg3B50pyjr6Sb409Te3d8k04AHH63b

Note that this is temporary and is NOT the key that will be used by the application upon release. It's strictly for development.

Media

Splash Screen: File:RelegoSplash.png‎ Background for all Scenes: File:RelegoBG.png

Teams

API

  • API Details
  • Lead: Frank Zammetti
  • James Harris
  • Ed Finkler
  • Markus Leutwyler
  • Bryan Roth

UI

  • Lead: David Baxter
  • Cliffton Thomas
  • Trevor Moore
  • Jordan Gensler

Signup/Login

  • Lead: Goatslacker
  • SirataXero

Encryption and Security

  • Lead: Jordan Gensler

Main/Reader/Article List Scene

  • Lead: Greg Hrebek
  • Roy Sutton
  • Will Honey (Tibfib)
  • Janni Kovacs

Add New Bookmark

  • Lead: Jeremy Thomas
  • Janni Kovacs (I created a add bookmark dialog in the main-assistant, may need some tweaking. Actual API call not yet performed)

Caching/Offline Mode

  • Lead: SirataXero
  • Dave Freeman (sugardave)

Help Docs

  • Lead: James Harris

Architecture

  • Lead: Roy Sutton

Patch/External App Support

App Prefs/Cookies

  • Brian Haeffner (haeffb)

Social Networking

  • Lead: Stan Toney (StanleyMToney)
  • anotherguy

Translation

  • Markus Leutwyler

Wherever help is needed

  • HattCzech
  • Donald Kirker (dkirker, find me in #webos on freenode)
  • Tim Stiffler-Dean
  • René Meister (rretsiem)

Testers

  • Lead: Roy Sutton
  • Justin Partain
  • Rob Whisler (rwhiz8577)
  • Donald Kirker
  • Brian Haeffner (haeffb)
  • Larry Clark
  • Dave Balmer

Events

Read It Later Hackathon

Getting Started

Useful Links

Source code repository on Github:

Hackathon Number 1 on Github

Read It Later API:

Read It Later API Documentation

Palm SDK:

Palm SDK Download

Ares:

Palm Ares

Download and install a git client. You may want to check out SmartGit, a Git client for Windows, Linux and OS X:

Download SmartGit

Git documentation for Windows users:

An Illustrated Guide to Git on Windows


Git workflow example:

Zend Framework Git Guide


Video of setting up Git on Windows:

Gitcast Git on Windows

First Steps
  1. Create an account at Palm and download the SDK
  2. Create a Github account if you want to be able to contribute source code back easily
  3. Fork the Hackathon source repository
  4. Download the sourcode using Git or import into an Ares project
Connecting to Github from Ares
  1. Click on the source code repository dropdown (looks like a safe)
  2. Setup a keychain if you have not already
  3. Click Checkout Project
  4. Select SVN as the repository type
  5. For url enter your github repository in the form: (replacing webOSroundup with your username)
 http://svn.github.com/webOSroundup/Hackathon-Number-1.git
  1. For project name enter Hackathon
  2. For keychain password enter the password for your keychain
  3. Enter your github username and password
Merging new code into your GitHub repo

You will get "Pull Requests" from webosRoundup on Github to pull in new code. To pull the new code into your master branch on your repo:

  1. Read your email! You should get a notification about the pull request there. Alternately, check your notifications list on GitHub (top bar, next to username)
  2. Go to your Fork Queue on GitHub. This will list the commits you can pull.
  3. Check the commits you want to merge.
  4. Select "Apply" in the dropdown for that commit set.
  5. Click "Update" on the next page. This will merge these commits into your repo on your current branch (probably "master")
  6. Now your repo is up to date!

Unanswered Questions

Personal tools