This document is forming a proposal to present to OuiShare, OuiShare Labs, shareNL and other Collaborative Economy communites. Feel free to add to the document and make comments in the main body. We should then work to modify comments into normal text so that they become part of the document.
The model is very nice when time is abundant, but we need a contingency plan for when time is in short supply as well. How does an individual knows, let's say in the time of the event itself, if she/he can make an 'on-the-spot' decision regarding something that needs to be solved at that particular moment, without time for consultation with other maintainers, surely not with all of them (Consensus requirement).
[DRAFT] It's a 'Lab' because it's a place to come and work on/develop/prototype collaborative economy projects. Perhaps conversation will spark new ideas which will inspire the creators in the room to prototype products, make art or etc. during the event. Perhaps people will bring their running projects to open them for discussion, invite new collaborators, test them on an interested audience, etc. Perhaps organisations will bring their challenges, needs, wants, hopes to the community to help understand how we can best assist and tailor what we're doing.
[DRAFT] It's a 'Camp', because it's a place to for visionaries and creators to come and spend 'quality time' together without a conference structure. We will cook, and eat together. Groups and conversations form dynamically. There will be the option to stay.
Building bridges between sectors such as hackers and business people. Dispel fears.
If there is enough interest, we will extend to a longer period to make a temporary 'hackbase' to continue the work started at the camp.
two modes of hackathon: networking, doing. Doing requires preparation
Financial / Organisational issues
This is a collaborative economy event, what is our strategy?
When considering organisational issues, and particularly those that require money, we should be very clear about how we are going to organise. The whole point of this event is to introduce collaboriatve practices to a larger audience, like:
Crowdsourcing, P2P, facilitating self organisation, keeping management structures flat, realising solutions that use the giving and sharing economies.
For large organisational issues, reverting to 'old' style event structures (sponsorship, outsourcing catering, centralised large conference venue) fail immediately at the goals we are trying to promote. This can be acceptable if for us it is more important to promote the values of our event than it is to practice them at and for the event.
A great example of this is food. Feeding 100 people is a challenge, but we need to solve it collaboratively
The event is free to enter. This means that either:
Venue needs to be given to us for free, or,
Venue paid by a third party, i.e. sponsor/s
The food is for free. Free food, for about 100 people, 3 meals a day, for 5 days (4,5,6,7,8). Added to this is the aspiration of cooking together. I am truly sorry to say that all this together is too much to ask. To be able to enable people to cook for themselves as a community for 5 days, supplying food to about 100 people, requires an operation that will be bigger than the rest of the event all together. By that I mean personnel-wise, equipment-wise (kitchen, with all amenities, plus a lot of fridge space, etc), location-size-wise (place will have to be much bigger and include some kind of kitchen, or at least permits to cook indoors), and probably other 'wise's as well...
One suggestion is 'Magic Hat'
I suggest that we do not concentrate efforts on parts of the event that do not support the themes directly, and even if the Health theme is directly connected (for example), then we can do one lunch or two which will be cooked together, while explaining the benefits of that specific meal, and of a healthy diet in general, and then have a session about nutrition that people can listen to while they eat.
This is actually very much in the spirit of 'Healthy(!) & Affordable', my own social business, one & a half months old ;-)
Educating while feeding, feeding while educating, healthy but cheap food, free education.
Last remark surrounding this matter: What about drinks?
I would like to discuss it in terms of daemons / apps, i see no problem that apps fetch public data from other profiles directly, also an app can request access controlled data directly without going through daemon (web server) hosting profile of person operating given app
James L Portability - must be easy to move to another host
- should not keep you tied to one host
// Copying - must be allowed to copy any method
// Replicating common types of requests?
// Connecting outputs with inputs - i want to support a feature, this is what's required to do this.
ToS: if you host someone's profile you should redirect to another host if they want to move
Profile hosting recommendations (eg. domain registered for min. 3 years ahead)
// Services & Aggregation?
- app to crawl some set of profiles to contain
- notify original creator and he takes a copy or makes a reference
Only a specific user can write to a particular profile
Notifications - changes in one profile cause notifications to specific sets of users
Issues for resolution / deferred:
Should profiles be for people only, or can e.g. events have their own profiles
Protocol for Client/Server communication?
Protocol for event notification?
Minimal language - 'is a', 'same as'
How to search, query language
Publishing profile in common format
Fair Profile Hosting ToS
Goals for next few weeks:
We're unlikely to solve 10% of the problems we discover, goals can be to solve a small
Daniel to continue working on same project.
James, build from simple use case, write To-Do's
Process - one check in in morning, and decide second check in in the morning when everyone will
check in at same time.
- don't tell other people how to do what they're going to do. ask if they'd like your feedback.
(Y) work session in Berlin Sunday&Monday June 1-2? :-)
Daniel would like to see a process by which we can define a clear statement of aims for OuiShare Labs and OuiShare Labs Camps once and for all! Because everyone keeps asking and I'm sure it's there in the group and website but we just need to get clear on it. ;-)
Labs = Labs Camp. Camp is just one version of the overall process. The roof, as Auli said.
What is Labs?
Labs Camp vs Labs Hacks. Bigger vs smaller events.
Maxime: I'm definitly for 2 big events/year + satellites events so that we can have a clear invitation for the community to gather 2 times a year.
Helene: Camp = ad hoc piggybacking of existing events. vs more sedentary. Labs = itinerant hacking
Labs spaces & related spaces
There's also interest in permanent, long-term co-working spaces
Henry: Assemblée Virtuelle preparing hackerbase in Fil Rouge (centre of Paris) for a semantic-web-dedicated permaspace
James LDaniel considering making event in Amsterdam
Auli KHelene - define a type of direction to work towards. Sharing economy, transactional part; also creating distributed web, federated tools, and have this as the attractor to plug in or project.
Helene: How OuiShare is helping projects emerge? Has there been discussions/statements in OS on this
Maxime: OS needs from the Labs: tech help for website etc, but they never tried to propose a vision for Labs. because nobody knows/understands what are the projects in the Labs. We should do what we think is the best for #collec.
Helene: Ben had ideas
Maxime: dynamic is brought by project leaders. When we offer a project,
Labs = pool of projects. Converging of sibling projects, that's what the value comes from.
James: interested in connecting with people who share similar values: sharing economy, nonprofit,
Alex: whether about meeting and networking, or about producing and identifying things that need to be done and try to produce them.