Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

FOSDEM 2017 – Open Source Design room organization #41

Closed
jancborchardt opened this issue Aug 20, 2016 · 102 comments
Closed

FOSDEM 2017 – Open Source Design room organization #41

jancborchardt opened this issue Aug 20, 2016 · 102 comments

Comments

@jancborchardt
Copy link
Member

The deadline for developer room proposals is on September 9:
https://fosdem.org/2017/news/2016-07-20-call-for-participation/

It will be our third room in a row! We shouldn’t break the streak 🚀

Ref issue from last year #22

Who will be there and wants to join organization? :) @belenbarrospena @ei8fdb @evalica @plastelina @Xaviju @bnvk @elioqoshi @gillisig @danilapellicani @simonv3

@victoria-bondarchuk
Copy link
Member

I'm looking forward to FOSDEM2017, please count me in!

@belenbarrospena
Copy link
Member

Yikes! Didn't see anything on their mailing list. Well spotted @jancborchardt

I will be in Brussels again, so I can help, but I was wondering if someone else would like to take on coordinating the proposal writing, the cfp and so on. I have done it for the past 2 years, so it might be time to pass the baton ;)

@jancborchardt
Copy link
Member Author

@belenbarrospena do you have an exact document of what you submitted to FOSDEM as the proposal? :) Something which with slight alterations we could submit again (I guess). :)

@belenbarrospena
Copy link
Member

@jancborchardt

#22 (comment)

GitHub issues are great! :)

@gillisig
Copy link
Member

gillisig commented Aug 22, 2016

I'm gonna try to make it this time, so count me in.

Edit: Oops sorry for closing the issue 😜

@gillisig gillisig reopened this Aug 22, 2016
@evalica
Copy link
Member

evalica commented Aug 23, 2016

It's a bit too soon for me to know for sure I will be there, but I sure hope I will be able to :) so count me in.

So in order to start the work the content of the proposal could be (adapted from last year - thanks @belenbarrospena ):

Devroom Request for FOSDEM 2017

Title: Open source design
Coordinator: _TODO_Name
Coordinator email: _TODO_Email
Secondary contact: _TODO_Name
Secondary email: _TODO_Email

Description:
After two successful devrooms in FOSDEM 2015 and 2016, we would like to repeat the experience also this year. Since the beginning of our Open Source Design community (http://opensourcedesign.net/) we promoted several initiatives, like having a "jobs board" where FOSS projects looking for design contributors can connect with available designers. FOSDEM helped us having a place to meet yearly face to face, talk about the projects/ideas/challenges we faced over the year and we hope to have a healthy number of proposals submitted and great attendance this year too.

The goal of this devroom is to showcase design work done within free and open source projects, and strengthen the connections between designers involved in FOSS. We mean "design" in a broad sense, and we include within that term typography, graphic design, interaction design, user experience and design research activities.

Possible topics include:

FOSS design tools
Design techniques and deliverables
Design - engineering collaboration approaches
User engagement and design research activities
Project case studies

After receiving several requests, we will probably dedicate an hour to project pitches, so that projects looking for design contributions can introduce themselves and establish contact with designers eager to help.

Coordinator's affinity to the topic of the devroom:

_TODO_Description

Why does it fit FOSDEM

FOSS projects bring in particular challenges that affect almost every aspect of design. Techniques and approaches used in closed software settings must be re-purposed and adapted to FOSS. This is hard to do on your own. We hope that sharing experiences across projects and communities will help establish a set of practices that are effective, flexible and transferable across FOSS projects.

The devroom last year also proved to be a great way of connecting designers with FOSS projects looking for design contributors. Having a devroom again next year will increase our chances to expand the community and will give us the opportunity to spread the word between developers regarding how and where to get design help for their projects.

Relevant URLs:
https://github.com/opensourcedesign
http://opensourcedesign.net/

Timeslot:
Full day

Special requirements:
None

@belenbarrospena
Copy link
Member

Hi @evalica

Thanks for putting this together. It looks good to me. Why not stepping in as coordinator? :)

If needed, we can take over the duties at FOSDEM, although I really hope you'll join us there in the end!

@elioqoshi
Copy link
Member

I am 95% sure I will be there so count me in! @belenbarrospena I'd be happy to help with the CFP.

btw, my colleagues at Ura Design and me plan to be there with a booth (www.ura.design). Maybe we can join forces with a booth since we have the same goal? What do you think?

@belenbarrospena
Copy link
Member

Right, so it sounds like @evalica might be willing to be the coordinator this year, as long as we can cover for her in case she doesn't get to FOSDEM.

@evalica, if I am wrong, let us know! :)

Now we just need a second name. @jancborchardt @gillisig @victoria-bondarchuk @elioqoshi @ei8fdb Would one of you be willing to be the second contact?

Once we decide that, and if nobody has any further comments on @evalica's submission proposal, we should be ready to send it.

@elioqoshi
Copy link
Member

I'd be happy to be Plan B :P

@belenbarrospena
Copy link
Member

@elioqoshi excellent. We are sorted then :)

@evalica
Copy link
Member

evalica commented Aug 24, 2016

yeap - works for me. Thanks @elioqoshi for help ;)

@evalica
Copy link
Member

evalica commented Aug 24, 2016

I created some FOSDEM guidelines/tasks that are easy to follow so that we don't forget anything:

  • Submit proposal for Developer Room on Fosdem.org | example | Deadline: 9 Sept
  • See accepted developer rooms announcement on Fosdem.org | example | Deadline: 21 Sept
  • Create Fosdem 2017 event on opensourcedesign.net | example | Deadline: 9 Oct (or earlier)
  • Create Fosdem 2017 Call for Participation article on opensourcedesign.net | example | Deadline: 9 Oct (or earlier)
    • Fix the dates for the track when they are announced
  • Manage the Fosdem 2017 Call for Participation step on Fosdem.org | Deadline: 9 Oct (or earlier)
  • Promote the Call for Participation on Twitter and OS mailinglists | example | Deadline: 9 Oct (or earlier)
  • Brainstorm on talks | example | Deadline: 11 Dec (or earlier)
  • Create the session proposals review spreadsheet | example | Deadline: 11 Dec (or earlier)
  • Send review mail to community members on mailinglist | mail: Session proposals for review - Open Source Design devroom | Deadline: 11 Dec (or earlier)
  • The acceptance / rejection notifications to speakers via pentabarf | Deadline: 11 Dec (or earlier)
  • Publish developer rooms complete schedules on Fosdem.org | example | Deadline: 11 Dec (or earlier)
  • Create promotional materials (stickers, banners) for opensourcedesign Promotional materials for opensourcedesign #43 | Deadline: 31 Jan
  • Organize the open source design dinner FOSDEM 2017 dinner #54 | Deadline: 31 Jan
  • Contact speakers with additional informations | mail: It's almost FOSDEM | Deadline: 31 Jan
  • Handle the devroom logistics videobox | example | Deadline: 4-5 Feb
  • Cover the event on Twitter | example | Deadline: 4-5 Feb
  • Open Source Design Devroom sessions presenter | Deadline: 4-5 Feb
  • Open Source Design Dinner + picture | Deadline: 3-5 Feb
  • Open Source Design Devroom picture | example | Deadline: 4-5 Feb
  • Submit talks slides on opensourcedesign GitHub| example | Deadline: 1 Mar
  • Write post event article on opensourcedesign.net | Deadline: 1 Mar
  • Provide a link to the video recordings | example | Deadline: 31 Jul

Questions:

  • Do we also want a stand? Joined with Ura Design | Deadline: 31 Oct
  • Did I miss any steps? Would be great some validation :) Ideally multiple people could help on a particular task

Mails:

  • Acceptance:

Submission accepted: FOSDEM 2017 Open Source Design Devroom

Hi <__>,

Thank you for submitting your proposal to the FOSDEM 2017 Open Source Design Devroom.

We are very happy to tell you that your proposal has been accepted.

Your session:
<>
has been scheduled for Sunday, February 5th, from <
> to <__>.

Please CONFIRM that you'll be attending by replying to this email or by changing the status of >your session to "Confirmed" in https://penta.fosdem.org, before Friday 16th December.
If we don't hear from you by then, we will assume you are not coming and we'll schedule a >different session in your time slot.

The Open Source Design Devroom will take place in room AW1.121. The room does not come >with a computer, so please bring your own laptop. Also, remember that your session will be >recorded (both audio and video) and probably streamed live.

You have 20 minutes on the spotlight that you can use at your discretion: you can either take all >20 to present, or leave some time for more questions / discussion. There are MAX 5 more >minutes to questions, outside of the initial 20 min. Out of respect to all attendees, we'll be >enforcing the time, so please make sure your content fits into those 20 minutes: we would hate >to cut you short.

If you have other questions don't hesitate to contact us.

Looking forward to meeting you in Brussels,
<__> on behalf of the devroom co-ordinators

  • Confirmation:

Hi <__>,

Thanks for confirming. I've mark the session accordingly.
https://fosdem.org/2017/schedule/track/open_source_design/
The schedule will become more complete as people confirm. This is automatically generated >periodically.

Regards,
<__>

  • Reject:

Submission rejected: FOSDEM 2017 Open Source Design Devroom

Hi <__>,

Thank you for submitting your proposal to the FOSDEM 2017 Open Source Design Devroom.

The team has now evaluated all proposals and decided which ones to accept.
We regret not being able to accept all submissions, yours included:
<__>

You may want to consider submitting any rejected proposals for consideration to one of
the other developer rooms.

See https://fosdem.org/ for more information on this year's developer
rooms and their coordinators.

The Open Source Design Devroom will take place on Sunday, February 5th in room AW1.121.
We look forward to seeing you at FOSDEM!

Best wishes,
<__> on behalf of the devroom co-ordinators

@ei8fdb
Copy link
Member

ei8fdb commented Aug 24, 2016

Hea @evalica as they say at home in Ireland that's fecking brilliant! I think you have covered everything that I can think of (right now..after a long day).

The main thing I can think of is when (not if, but when!) the design devroom gets accepted, we should try and promote it as early as possible to maximise the chances of filling the schedule.

Last year I subscribed to a number of OSS design, and "privacy and Internet do-gooders" lists (I'm on a few lists :)) and e-mailed them the CFP. These are the lists I sent it to. @belenbarrospena sent it to these lists.

I also used the schedule tweet feature in Tweetdeck and automated a tweet every 2-3 days. Maybe we should ask people, when they submit, "where did you see the CFP?" - you know, a bit of user research ;)

About the brainstorming, what does everything think of a general theme for talks? I bit we might be a bit too small to be restrictive to a theme...but just suggesting it?

About the promotional materials, we can do that even earlier, no?

About the tasks, I'm happy to help out with:

  • Create Fosdem 2017 event on opensourcedesign.net
  • Create Fosdem 2017 Call for Participation article on opensourcedesign.net
  • Promote the Call for Participation on Twitter and OS mailinglists
  • Brainstorm on talks
  • Create promotional materials (stickers, banners) for opensourcedesign <- I can put money in for this.
  • Handle the devroom logistics videobox <-- please please help!

Bernard

@belenbarrospena
Copy link
Member

@evalica, that list is excellent. I think I am only missing:

  • The Call for Participation publication step in fosdem.org. Once we publish the CFP in opensourcedesign.net, a link to it and the submission deadlines should appear in the FOSDEM website. This is done with a GitHub pull request, if I remember correctly. It's not hard, but I can help if needed. The FOSDEM organisers will remind you of this any way, as part of the coordination process.
  • The acceptance / rejection notifications to speakers that I sent by email before publishing the schedule in fosdem.org - which is done via pentabarf, a truly delightful web application ;)

What I did in the past was sending the emails out, and give the speakers a deadline to confirm. Once I received confirmation, I published their session in pentabarf. You probably have the email I sent you last year, so you can reuse that, or you can write a new one: I made them up anyway the first time :)

Everything else seems spot on.

About the stand, @elioqoshi was suggesting we join forces with ura design. That might be a good thing: it will be less work for everybody to organise and cover.

Thanks for the work!

@evalica
Copy link
Member

evalica commented Aug 25, 2016

I submitted the proposal to FOSDEM with the content:


= Project details =

  • Title of devroom:
    Open Source Design
  • Elaborate description of proposed devroom (including possible topics):
    After two successful devrooms in FOSDEM 2015 and 2016, we would like to repeat the experience also this year. Since the beginning of our Open Source Design community (http://opensourcedesign.net/) we promoted several initiatives, like having a "jobs board" where FOSS projects looking for design contributors can connect with available designers. FOSDEM helped us having a place to meet yearly face to face, talk about the projects/ideas/challenges we faced over the year and we hope to have a healthy number of proposals submitted and great attendance this year too.

The goal of this devroom is to showcase design work done within free and open source projects, and strengthen the connections between designers involved in FOSS. We mean "design" in a broad sense, and we include within that term typography, graphic design, interaction design, user experience and design research activities.

Possible topics include:

FOSS design tools
Design techniques and deliverables
Design - engineering collaboration approaches
User engagement and design research activities
Project case studies

After receiving several requests, we will probably dedicate an hour to project pitches, so that projects looking for design contributions can introduce themselves and establish contact with designers eager to help.

  • Why does it fit FOSDEM?

FOSS projects bring in particular challenges that affect almost every aspect of design. Techniques and approaches used in closed software settings must be re-purposed and adapted to FOSS. This is hard to do on your own. We hope that sharing experiences across projects and communities will help establish a set of practices that are effective, flexible and transferable across FOSS projects.

The devroom last year also proved to be a great way of connecting designers with FOSS projects looking for design contributors. Having a devroom again next year will increase our chances to expand the community and will give us the opportunity to spread the word between developers regarding how and where to get design help for their projects.

  • Preferred slot:
    Full day

= Contact information =

== Primary contact ==

  • First name: Ecaterina
  • Last name: Moraru
  • E-mail: [email protected]
  • Submitter's affinity to the topic of the devroom:

I have been the interaction designer for XWiki (www.xwiki.org) since 2008 and part of the Open Source Design community (opensourcedesign.net) since the beginning in 2015.

== Secondary contact ==

= Additional information =


You should receive a confirmation email soon. If you don't, please contact [email protected]. Your proposal will be reviewed and we will inform you if it is accepted or not via email by the 21st of September 2016.


@ei8fdb Regarding the deadline, you are right that we can start the promoting as soon as possible and would be great to use the lists from last year. Same for the brainstorming and promotional materials (I've created #43)
Regarding Tweetdeck, there is a functionality that we can create a team for the opensrcdesign Twitter account and have multiple people have access to it. I don't remember the password for the account :) but it would be great if we could set it up.

@belenbarrospena Thanks for the additional notes, they are useful :) I'll see if I can add more details in the tasks list

@elioqoshi Hope I put the correct email in the submission :) also I'll let you handle the submission for the stand. Let us know if you need help.

@jancborchardt
Copy link
Member Author

@evalica awesome work! :) 🚀

@elioqoshi
Copy link
Member

Wow, splendid work! I must admit I have yet to read all of it in details but it looks very well prepared!

I will be at FOSDEM together with 1 or 2 colleagues from my startup Ura who can help at the booth. If we have at least 2 people at the booth at any given time, that would be excellent. What do you think?

@ei8fdb
Copy link
Member

ei8fdb commented Aug 27, 2016

@evalica regarding the Twitterings I have access to the OSD Twitter account - I can also schedule those tweets if it helps.

@elioqoshi and everyone: would it be an idea to have a design surgery booth where people can come with their "design emergencies"?

@ei8fdb
Copy link
Member

ei8fdb commented Aug 27, 2016

I've created PR #44 to add FOSDEM to OSD.net. Once we get accepted I guess it can be added...

@ei8fdb ei8fdb added this to the create fosdem event milestone Aug 27, 2016
@elioqoshi
Copy link
Member

@ei8fdb That's a good idea, but let's make sure the OSD name is well communicated

@jancborchardt
Copy link
Member Author

@evalica @elioqoshi by the way I just added you both to the https://twitter.com/opensrcdesign via https://tweetdeck.twitter.com :) You can Tweet from there and retweet anything which has to do with Open Source Design.

@elioqoshi
Copy link
Member

@jancborchardt perfect, thank you!

@danilapellicani
Copy link
Member

@evalica for the Open Source Design dinner, do you have something in mind or it's just a dinner somewhere? Because would be cool to involve these designer http://designmarketo.com/ and make a real OS Dinner :) What do you think?

@danilapellicani
Copy link
Member

Or maybe just home made pasta, would be fun ;)

@ei8fdb
Copy link
Member

ei8fdb commented Dec 11, 2016

Great work @evalica! Is there anything you need help in doing? Do we have enough people to do the default sessions?

I'll pack extra bottles of water and headache tablets for the 9am start.

I'm not looking forward to the early start, but I am glad that we will be able to have all the good talks that were submitted.

Random idea: maybe we should apply for 2 days next year? 💃 !

@ei8fdb
Copy link
Member

ei8fdb commented Dec 11, 2016

And now that we're underway, can I suggest people look at #54 (FOSDEM Dinner preferences - do we organise dinner?) and cast their votes....

@belenbarrospena
Copy link
Member

Thanks @evalica for all the great work!

I have 2 sessions, which is 2 too many ;) Would anybody not speaking like to take the pitch your project one? That's where projects can come and ask for design work. @jancborchardt can tell you what's involved: he did it last year. It's more like a moderation role.

If you are interested, just reply here. Thanks!

@evalica
Copy link
Member

evalica commented Dec 12, 2016

Following Belen's example: if somebody wants to handle the "Closing" or "Success Stories from our community" sessions let me know. Preferable some community members that don't have other sessions :)

@ei8fdb
Copy link
Member

ei8fdb commented Dec 12, 2016

Unless anyone specifically wants to do the pitch your project session, I'm happy to do it.

About teh closing - maybe it might be nice if we all gave a minute each?

@evalica
Copy link
Member

evalica commented Dec 12, 2016

@ei8fdb the problem with a minute each is that we might be more than 5 in that session :) the schedule is a bit tight, plus we will need to clean up and hurry for the official closing. Anyway, in that session we should do at least 1 photo :) to continue the tradition.

@ei8fdb
Copy link
Member

ei8fdb commented Dec 13, 2016

@evalica OK how about we all do it together - what I mean is, the closing session is the closing of the Open Source Design track at FOSDEM that we all organised.

I kinda feel that it should be as a collective. Organise it however..each person says one word, and rotate around to the next.

I just think its an opportunity to say thank you to everyone.

@belenbarrospena
Copy link
Member

I think calling everybody to the front of the room is a nice idea, but it will be much more coherent and understandable for the audience if one or two people do the talking. If we all want to say something we will have to practice! ;)

@evalica, as the person pulling off most of the work in this case, should probably be one of them. And then maybe @victoria-bondarchuk or @jancborchardt, as the organisers of the FOSSASIA track, could also also say something.

@belenbarrospena
Copy link
Member

@ei8fdb about taking the pitch your project session, I see you already have a short presentation: "Promoting your FOSS project to university student designers". It would be nice if someone from the community, but not talking, could take this. What about @gillisig? Or maybe he would prefer taking the "Success Stories from our community" one?

If noboby else volunteers, it is definitely yours @ei8fdb :)

@evalica
Copy link
Member

evalica commented Dec 13, 2016

I'm fine in having the Closing as a collective (I quite prefer it this way) as long as we keep it short :)
Regarding the "Speakers" column in the schedule: should we have more people listed there? Just let me know if you want your name added.

@evalica
Copy link
Member

evalica commented Dec 16, 2016

Today is the deadline for FOSDEM 2017 sessions confirmations. At the moment we are lacking 4 speakers:

  • "Designing MuseScore" by Miroslav Mazel (pinging @lasconic and @thomasbonte maybe they know him since I can't find a GitHub account)
  • "Interviews as user research" by Andreas Nilsson @andreasn
  • "Mozilla Open Design" by Elio Qoshi @elioqoshi
  • "Promoting your FOSS project to university student designers" by Bernard Tyers @ei8fdb

Can somebody else also try to reach them? Or maybe you know them personally and can ask them to read their e-mails :) I need confirmations for their sessions. Thanks.

@evalica evalica closed this as completed Dec 16, 2016
@evalica evalica reopened this Dec 16, 2016
@andreasn
Copy link
Member

I can confirm I'm speaking!

@andreasn
Copy link
Member

But I can't change the status to confirmed! :/

@andreasn
Copy link
Member

replied to the e-mail now.
Sorry for the mess.

@12people
Copy link

@evalica Miroslav Mazel here, I am attending

@ei8fdb
Copy link
Member

ei8fdb commented Dec 16, 2016

@evalica Yes, I'm confirming. Sorry - didn't see this 'til @jancborchardt shame-tweeted me ;)

@ei8fdb
Copy link
Member

ei8fdb commented Dec 16, 2016

@belenbarrospena I'm totally fine with someone else doing it. I think it should be a few people anyway..

@jancborchardt
Copy link
Member Author

Same for the »Our Open Source Design collective« talk btw. I expect a few of you @belenbarrospena @bnvk @ei8fdb @evalica @elioqoshi @jdittrich (and @simonv3 @victoria-bondarchuk, and others, if you could be there!) to be on stage for that too. :)

(@evalica if it’s possible to add multiple speakers or free text, it would be great to use »Open Source Design team« for these collective / default sessions.)

@evalica
Copy link
Member

evalica commented Dec 17, 2016

So, thanks for confirming. We are still missing @elioqoshi

@jancborchardt regarding speakers: you can only add penta users. I guess the rationale is that each speaker has a profile page and in order to look nice on the website. I cannot add free text.
So I will let each person assigned now to handle each of the "collective" sessions and send me in mail what exact users should be listed there. Please consider that you privately confirm with those people and that you have enough time for everyone on the stage to say something or just look pretty :)
We can discuss more about the "collective sessions" on 10 Jan in the Monthly meeting.

@evalica
Copy link
Member

evalica commented Dec 17, 2016

Maybe we can mark in the title, have like a tag "[Collective]" ... or "[Group]"

@ei8fdb
Copy link
Member

ei8fdb commented Dec 17, 2016

@evalica yep, I think thats a good idea - having a tag to signify "it's the whole group". 👍

@bnvk
Copy link
Member

bnvk commented Dec 18, 2016 via email

@elioqoshi
Copy link
Member

Hey sorry, I had 2FA problems with GitHub lately. I'm still seeking official confirmation for my sponsorship from Mozilla but I'm 90% sure I will be there.

@evalica
Copy link
Member

evalica commented Jan 11, 2017

We will some volunteer(s) for Video. Requirements:

  • pointing the camera at the speaker
  • keeping an eye on the local leg of the recording system
  • (possibly) do live mixing using a web app (currently in beta)
  • keep in touch with the video operations control

And also some volunteers to help if the room gets too crowded.

@eppfel
Copy link
Member

eppfel commented Feb 8, 2017

This was splendid work everyone. Videos are up, so I guess we're done here.

@eppfel eppfel closed this as completed Feb 8, 2017
@evalica evalica self-assigned this Jul 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests