Differences between revisions 28 and 29
Revision 28 as of 2017-01-23 20:02:43
Size: 8793
Editor: ?Solveig
Comment: + Solveig attends :)
Revision 29 as of 2017-01-26 15:26:38
Size: 8876
Comment: Added myself to attendee :)
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
|| 5. || Sebastien Badia || sebian || sbadia@d.o || || vegan will be fine || ||

This is a work-in-progress page for the organization of a Debian Bug Squashing Party, to be held in Mozilla Paris in May, in order to work on the next Debian release (Stretch), that is expected in 2017.

Details

Promotion

Please link to mails, blog posts, tweets or other promotion done for the event.

Reports

Please add links to reports, blog posts, photos etc about the BSP here:

Schedule

Attendees

If you are interested please add your name to the list below. Feel free to add yourself even if you're not sure if you will attend.

Name

Nick

email

sleep

diet

notes

1.

Julien Cristau

jcristau

jcristau@d.o

for the weak

i like food

2.

intrigeri

intrigeri

intrigeri@d.o

WIP

vegan will be fine

2.

spriver

spriver

done

vegan

3.

Julien Voisin

jvoisin

I can host ~2 people on my floor

vegan will be fine

Living in Paris; can help with logistic issues

4.

Solveig

Solveig

debian@s.o

done

vegetarian

5.

Sebastien Badia

sebian

sbadia@d.o

vegan will be fine

Transport

Bring

Please consider bringing the following items:

  • computers
  • network cable
  • power adaptors
  • power bars

Organizing

Communication

Making the space safe

  • Header on top of this page and of the various announces:
    • ACTION: spriver copies the intro to Rust Community page as the short version (to be included in communication), and adjusts it to make it clear that attending the event goes together with acknowledging and respecting the CoC

  • Code of conduct
    • ACTION: spriver adds the "what happens if things go wrong" thing from the Rust CoC to our CoC, initially copied from the Tails' one)

    • ACTION: spriver adds private harassment to the CoC e.g. as another bullet point
    • TBD: print it
  • Moderation team
    • TBD: members
    • TBD: contact info
  • TBD: announce all this at least once a day

Misc

Food

We want to provide a lunch on both days. It shall be vegan to simplify handling diverse diet. The attendees table has a column for other diet desires and needs.

  • ACTION: intrigeri gives jvoisin contact info for local cooking team [WIP: asked contact info]
  • ACTION: jvoisin handles communication with local cooking team, starting with getting quote for 2 * 20-50 people lunch
  • ACTION: intrigeri asks jcristau a quote from Mozilla's usual caterer, making it clear it's not our top option so far, and that we want vegan (backup plan) [WIP]

Accommodation

  • TBD: call for solidarity hosting
  • TBD: match hosting requests with offers
  • TBD: (if we have enough budget) book remaining needed hosting in a hostel, Airbnb or whatnot

Finances

  • ACTION: intrigeri starts looking for sponsorship [WIP]
    • ACTION: intrigeri asks the DPL [WIP]
    • ACTION: intrigeri thinks of other potential sponsors
  • TBD: ensure we can sponsor at least travel for potential new contributors who need it (one doesn't get a diverse set of attendees if only only-timers get support)

  • TBD: how to manage travel sponsorship requests? (assuming we have a budget for that)
    • make it clear there's a budget for that in the various announcements
    • receive and store requests, and at some point make a call
    • manage reimbursements
  • ACTION: intrigeri includes food in the support budget we're gonna ask to potential sponsors

Optimizing for a broader public

(i.e. not only Debian developers)

Reach out to, and properly welcome, people who can contribute to the quality assurance effort, with their pre-existing skills, in other ways than fixing bugs and uploading packages. E.g.

  • testing the upcoming version and providing feedback; evaluating the state of translations and the support of accessibility technologies could be interesting focuses;
  • triaging release blocking bugs (reproducing them, assessing their severity, pointing the relevant people to them);
  • providing feedback about "the top N things I dislike the most in the current Debian release, that I very much hope will be fixed in the next one";
  • collecting data relevant to the release notes.

Make it real once we're there

There will be people committing to host a station, i.e. holding some physical space dedicated to people with a given set of skills, and making it welcoming and productive.

  • ACTION: intrigeri asks Hypra if they want to host a "Stretch accessibility testing/feedback" station [WIP: waiting for answer]
  • ACTION: intrigeri finds a "consultant" who'll be available to provide advice to the bug triaging station [WIP: waiting for answer]
  • ACTION: intrigeri tries to find someone to host a station about graphics and design [WIP: waiting for answer]

Make it clear in our communication

  • ACTION: intrigeri writes a few lines about each station, and a sentence that says there might be more stations if we find hosts, that we can include in our announcements etc.
    • users testing/feedback (intrigeri, jvoisin)
    • bug triaging (Solveig)

Invites

TBD:

  • people who could give a hand organizing (e.g. spreading the word and themselves inviting cool people)
  • people we want to see there

Publicity

Announcement

  • ACTION: intrigeri drafts announcement text (early Feb)
    • make it clear that there will be a team ready to deal with problems (safe space)
    • include a placeholder about sponsorship, that we'll update when it's time to publish the announcement, depending on the progress we made on fundraising
    • the space is accessible to wheelchairs
  • ACTION: intrigeri asks geb if he want to coordinate communication & publicity, and start to spread the word around Feb 10-12

  • We have a pad that's meant to list people & websites we want to send the announcement to. It's kept private as it contains social network information some of us prefer not to disclose publicly.

CategoryBsp CategoryEvents