Hi,

I've looked at the roles page (on which I'll comment later) and
found an item which I already worked on in a previous project:
conference badges. So I repurposed my code and came up with the
following sample document below.

I noticed last year (like on many conferences) that people tend
to become sloppy wearing their badges after day 1 or 2. And I be-
lieve this is because after two days their information value has
dropped significantly, since people by then mostly know "who is
who", at least for a conference of this size (PyCon might be
different).

So I thought the badges should make a statement about the days
a participant will attend (so others know when to go hunting them
for a chat).

And they should express the basic conference related topics/tags
a participant is interested in (or is speaking about), so people
can more easily find peers, discover common interests, share ex-
perience, get better involved and make the most out of the con-
ference.

Regarding the marix code (in this case QR-Code): it could be used
either for identification using mobile phones with the respective
software or for pointing others to a website (or anything else)
of its carrier. Or both with double-sided badges, maybe.

The logo could be any bitmap, SVG (with reduced feature set) or
PDF. So here's the sample using an old EuroPython logo:

   http://me.in-berlin.de/~darwin/tmp/badges.pdf

One more thing, I know that "good" plastic "containers" for such
badges tend to be expensive for a community event like this, apart
from not being quite "environmentally correct". But recently I
watched some old American seminar video recordings with people
wearing labels sticked on their jackets, shirts, etc. This might
be an idea, even if such labels are likely to deteriorate physi-
cally after a couple of days.

Just a few ideas to improve this part of the conference experience.

Regards,

Dinu

_______________________________________________
Europython-improve mailing list
[email protected]
http://mail.python.org/mailman/listinfo/europython-improve

Reply via email to