Hi, On Di, 2016-04-12 at 11:45 +0200, Lasse Schuirmann wrote:
I'd certainly still be interested but won't have the time to coordinate everything around this as always. GSoC's going crazy right now and I'm doing stuff for too many orgs here. I hope I can work out a few rough proposals, post them here and let you choose which you like so I can refine.
OK, someone will need to make a couple of executive decisions though, as I won't be the person actually doing the workshops. :)
I think a few questions are missing for the workshops IMO: - How long should the workshop take? (Half day, day, two days possible?)
It is planned for 1 full day right now (i.e. August 11th).
- What should participants be able to do after the workshop. (Helps setting expectations right and usually also helps planning very much.)
Few organizational questiosn: - Do we have any idea about the target audience? Very important for workshop holders to know.
I am totally fine with you deciding on the exact audience. Ideally, I think it would be nice to have something that targets (local) students who are interested in free software and hopefully GNOME. So my guess is that it makes sense to expect some prior knowledge, but not much actual experience (e.g. they know what git is, but have never send a patch upstream).
- Will you be able to organize material locally? That usually includes lots and lots of sticky notes and threeish pieces of custom printed paper per participant. A projector with a few adaptors.
Sorry, I didn't forward that list to you. We will provide a seminar room with the following: * projector * blackboard * WiFi and 1-2 LAN ports * multiway power extensions (1 socket per person) * chairs/tables Adaptors are on my todo list to check and ping later. Anything else should be requested so we can organize something. Didn't think about paper/sticky notes before, sounds sensible to include that for all workshops.
- Are there tables, arrangeable for group work?
Yes.
- For longer workshops, at least some water would be nice to prohibit dehydration.
Good point. Noted.
- It'd be great to have a BoF related or accompanying every workshop. A very critical point is to get people to try out the stuff even after the actual workshop. Knowing a place where they can come and hack *and ask* would be awesome. IMO we should encourage workshoppers to organize a BoF.
Oh, that is a good idea and easy to implement.
- Would be nice to have feedback sheets so we can measure the success and impact of the workshops. This is one big experiement so let's not forget gathering data.
Interesting, thought. For whatever reason I hadn't considered that yet, even though I have done exactly the same thing for other events. Added it to my list. Biggest task is to figure out the questions to put on the sheets. Benjamin
Sincerely, Lasse Schuirmann contact viperdev io http://viperdev.io/ 2016-04-12 11:30 GMT+02:00 Benjamin Berg <benjamin sipsolutions net>:Hey, On Mi, 2016-01-27 at 14:27 +0000, David King wrote:I have done some introductions to git and GNOME inspired Workflows, maintaining projects properly in two universities recently and people seemed to like it. I could think of turning this into a workshop if there is demand.Yeah, something like a GIT and maybe FOSS basics workshop would be great to see!I'd be happy to help plan and deliver these. I can only do them in English, so some German speakers might be good too (hi Lasse!)are you two (Dave, Lasse) still interested? It would be great to have descriptions for the workshops up before registration starts. So if you are still up for it, then I would appreciate it if one of you could step up to coordinate the effort and decide more precisely what we can offer at GUADEC :) To be more specific, the information I am looking for is: * Title of the workshop * Short Description (for an overview page) * Long Description (for detailed page) * Expected prior knowledge * Pre-Requisites for attendees (e.g. VM with certain packages) * Minimum/Maximum number of Attendees * Name of everyone giving the workshop * Should your employer be listed as a sponsor? * Will you need travel sponsorships? * Optional: bio (+ image) for website Benjamin
Attachment:
signature.asc
Description: This is a digitally signed message part