MashupCamp6DiscussionIdeas

From MashupCamp

Jump to: navigation, search

Contents

[edit]

Proposed Discussion for Mashup Camp 6

[edit]

Overview

This page is where you should give people an idea of the session(s) that you may end up proposing at Mashup Camp 6. But first, you should familiarize yourself with how things work at our Mashup Camps.

Mashup Camp 6 will be conducted Open Space style (more about Open Space and unconferences can be found here). Much the same way prior Camps were run, at the beginning of each day, there will be a general assembly where attendees can propose the discussions that they're interested in leading. Attendees will line up for their turn at the microphone, propose a discussion and, on a whiteboard that lists all of the available rooms and timeslots in grid fashion, slot their proposed discussion into one of the available room/times.

We'll follow the same protocol as in prior Camps where the details about the proposed discussions are written in magic marker on a piece of paper and then taped into an available slot (this way, they're easily moved). To get an idea of what this looks like, check out the images on the CampAgenda for Mashup Camp I. There are about 10 different rooms and 5 different time slots per day which means there's opportunity for a lot of different sessions.

On the second day of the event, one or more blocks of time will be reserved for SpeedGeeking. SpeedGeeking is like speed dating. Developers and others with a technology to demo will set up stations and attendees will spend five minutes at each station before moving to the next one at the sound of a buzzer. This is one of the most popular parts of Mashup Camp.

Be prepared to be surprised.

[edit]

Principles of open space

There are several principles of Open Space:

  • Whoever comes are the right people.
  • Whatever happens is the only thing that could have.
  • Whenever it starts is the right time.
  • When it is over, it is over.
  • Document your session on the wiki.
[edit]

The law of two feet

There is also the Law of Two Feet:

If during the course of the gathering, any person finds themselves in a situation where they are neither learning from nor contributing to the discussion, they should use their two feet and go to a more productive place.

[edit]

Proposed discussions

Below is a list of probable/proposed discussions (if none appear yet, feel free to start the list). At the end of each description could be a link to a detail level page where you can get more information, indicate your interest in attending the discussion, and flesh out the topic in more detail with other attendees. However, in some cases, the proposed discussion is neither listed yet or the detail level pages are not setup yet. So, feel free to add to this wiki. If you click on a link for which a page hasn't been created, it will take you to a page that you can start to edit (if you are one of the people who proposed a topic, feel free to start the detail level page associated with that topic and get the conversation going!).

Check out our help page for getting started when it comes to logging in and creating or editing pages on this wiki.

Proposed Discussions: Please "copy" the format used by one of the entries below to create a new entry.

  • Making the case (internally) for taking the Mashup approach to that next enterprise software project - There are a lot of benefits to the mashup approach for business software projects. But getting sign-off on breaking from the norm can be a challenge. In this discussion, we want to begin the collaboration on the documents (text, slides, etc.) that will remain publicly accessible for anyone who wants a big head start on making the case for mashups inside their organizations.
  • Mashups for ordinary humans - ChrisRadcliff - Mashups are seen as cutting-edge applications, but the same techniques can be used to set up a clean, usable Web presence on a shoestring budget, to be used by people who think the Internet is a series of tubes. I'm currently working on such a site for the San Diego Space Society, and I'd be happy to share my experiences or spark a discussion.
  • Adding the phone to mashups - NickBranstator - MyVox has recently released an API that allows developers to add voice recording to their apps through the phone at no cost. I'd like to share thoughts on why it's important to make phones an easy-to-incorporate technology for non-telephony developers, how the API has been used so far, and what directions people might take it.
  • API-Free Zone: Creating Mashups using only Open Standards - APIs take work to learn and use. Once you write to an API you're mashed up with exactly one other app. Lets explore techniques such as OpenSAM.org and dataportability.org to build reusable mashups that connect easily to new, innovative services.
  • Mashups for non-PC devices - With devices like mobile phones and TVs increasingly sporting browsers, mashups on non-PC devices are coming into view. To get things started, Yong Tian of ACCESS will discuss the mashup environment for non-PC devices and some of the capabilities of the ACCESS platform. Afterwards, Phil Keys, a reporter with Nikkei Electronics will try to get a discussion going around interest in doing mashups for such devices and perceived issues/solutions for creating such.
  • Crossing the Mashup Chasm. Requirements for Enterprise Mashups - Jhidalgo - Are mashups ready to "cross the chasm", or are we already doing it without knowing? What are the requirements that painful enterprise users require in order to consider Enterprise Mashups as a primary player in the data integration arena? I´d like to spend some time with you guys explaining my point of view, my experiences in enterprise data mashup projects and offering some questions as food for discussion so that, hopefully, we gain some insight about what we will be seeing in Mashup Camp...10? :). Update (March 19th): I´ve uploaded the initial presentation I want to show you through slideshare.
  • Design strategies for valued added functionality - JimPringle - Making a mashup is one part of the equation. Wanting to value add the data you are collecting with new data and functionality is another. One simple example is wanting to take restaurant listings from YahooLocal, applying the data to a map, mixing in zagat style professional reviews, then allowing for your own unique review and rating system for your users as a contract to professional reviews. You will query Yahoo & Zagat for the data, but will be storing the user reviews and ratings in your own DB. What are the best strategies for building database designs that are compatible with the developer licenses from the data vendors? How much caching is used (and TTL) for RSS and other feeds/data? And how is the indexing properly structured to enhance performance across a variety of incoming data, being mixed with your own?
Retrieved from "http://wiki.mashupcamp.com/index.php/MashupCamp6DiscussionIdeas"
Personal tools