Child pages
  • BarCamp Summer '07
Skip to end of metadata
Go to start of metadata

JA-SIG conferences represent a wonderful opportunity for collaboration and networking. To promote this, for the summer conference we've allocated time for a BarCamp-style session. A BarCamp is an ad-hoc gathering born from the desire for people to share and learn in an open environment. It is an intense event with discussions, demos, and interaction from participants. The name BarCamp was inspired as a complement to FooCamp. http://barcamp.org/

When: Wed afternoon (6/27) 1:30pm-5:00pm
Where: The large meeting room

Possible Topics
  • FLUID
  • Bitesized uPortal Tasks
  • CAS Development
  • AJAX rendering
  • CAS Authentication to uPortal
  • Embedding CAS in uPortal
  • uP3 Architecture Overview/Q&A (like what we did that the dev meeting)
  • uP3 Dev tasks (TBD by May 4)
  • JA-SIG web presence
Rules

The rules of BarCamp (as listed by barcamp.org) are:

  • 1st Rule: You do talk about Bar Camp.
  • 2nd Rule: You do blog about Bar Camp.
  • 3rd Rule: If you want to present, you must write your topic and name in a presentation slot.
  • 4th Rule: Only three word intros.
  • 5th Rule: As many presentations at a time as facilities allow for.
  • 6th Rule: No pre-scheduled presentations, no tourists.
  • 7th Rule: Presentations will go on as long as they have to or until they run into another presentation slot.
  • 8th Rule: If this is your first time at BarCamp, you HAVE to present. (Ok, you don't really HAVE to, but try to find someone to present with, or at least ask questions and be an interactive participant.)
How to participate
  • Sign up below. Please put your name and any organization you represent
  • Bring a laptop - It's great for showing off that program you mentioned in your session. 
  • Be ready to participate - come with an idea for a session you can lead. You don't have to be an expert at your topic; as long as it's not too specific, there'll probably be someone else present who can help you out. You can also contribute to the conversation during a session. This is a great way to participate, since it spreads knowledge from everyone, instead of just the leader.
I'm In!

Susan Bramhall

Yale University

Colin Clark

University of Toronto

Jens Haeusser

University of British Columbia

Jim Helwig

University of Wisconsin-Madison

Andrew Petro

Unicon, Inc.

Jason Shao

Rutgers University

Paul Zablosky

University of British Columbia

William Kubie

University of Colorado at Boulder

Kevin Crafts

University of Colorado at Boulder

  • No labels

4 Comments

  1. Do we have an idea when BarCamp will be scheduled? I'd like to participate but I've already made travel arrangements.

  2. AJAX rendering brings up a number of issues for schools in the California State University system, as we are now being held to the same 508 accessibility standards as the rest of the government agencies, and I suspect most other states will do the same quite soon.

    Can all the ajax fun stuff happen with JavaScript disabled?

    Oh, and sorry I wont be able to attend...my flight back on Wednesday is already booked.

    1. Hi Patrick,

      The issue of Section 508 and JavaScript is a tricky one. The problem with 508 is that it is out of date; JavaScript really hasn't been an accessibility problem for many years. The 508 legislation is being re-worked, and the requirement for sites to work with JavaScript disabled will be removed.

      On the other hand, there are certainly accessibility problems with JavaScript when doing DOM manipulation. The W3C has been working on new specifications called Accessible Rich Internet Application (ARIA) that address ways in which DHTML and Ajax can be made accessible.

      For FLUID, we are building our whole accessible framework on DHTML, Ajax, and JavaScript. That's why we've been working with the Dojo community to make it more accessible. It's going to take some time, but I expect Ajax and DHTML to be fully accessible, regardless of what 508 says about it. (smile)

    2. http://www.webaim.org/techniques/javascript/ seems to imply that AJAX rendering along shouldn't break any 508 compliance issues, though WCAG 1.0 doesn't seem to allow it.

      Colin knows more about this than me though (smile)