Wednesday - Hackathon Go

On Wednesday, 8 July at 11am ET, the "Hackathon: Go" session wil=
l launch Sakai Boston hackathon activities. We plan to organize the hackath=
on in unconference format, which means that whoever=
shows up decides what will happen. That means you!

=20

What you can you do right now? Add your suggestions for hackathon sessio=
n projects you'd like to contribute to and lightening talks you'd like to g=
ive below. We will work together to schedule time to work on these projects=
and hear these talks during Sakai Boston.

=20

We will go over these lists and generate more ideas in the "Hackathon: G=
o" session to start planning the rest of the week's activities. More projec=
ts and lightening talks may well be added along the way. If you want to hel=
p shape the hackathon, please contribute to this wiki page and attend the "=
Hackathon: Go" session.

=20

The hackathon will take place throughout the Boston conference, concludi=
ng with the "Hackathon: Stop" session 2:30pm ET Friday, 10 July, where we w=
ill review hackathon activities, evaluate the hackathon process, and plan a=
ny next hackathon steps.

=20

Anthony Whyte, David Horwitz Noah Botimer and I proposed this hackathon =
to encourage and make visible the hands-on work that goes on at Sakai gathe=
rings. We hope the hackathon will be a chance for community members of all =
types?not just developers?to focus on small, tangible pieces of work while =
they are face-to-face that will have direct effects on the functionality, u=
sability, accessibility, internationalization, design, development, and/or =
quality assurance of Sakai and its tools.

Is there anything to this beyond the mockup? In other words, does=
view source get it all, or is there Sakai 2.6/Sakai 3 backend functionalit=
y too? James Marca

=20

Looking at getting this into Profile2 if anyone wants to talk to me abo=
ut an impl, or do it Steve Swinsburg

=20

I've been thinking about doing this (well, what we talked about in the =
K2 workshop) REST-fully properly. The 5 cent version is that there should b=
e more specificity on the actual resource being addressed. If anybody is in=
terested I'd be happy to dump my thinking in a child page here. James Marca