[Marketing] QtCS registration (was RE: Can perhaps help a bit to prepare QtCS 2012)
alexandra.leisse at nokia.com
alexandra.leisse at nokia.com
Wed Mar 14 13:35:44 CET 2012
On 12.3.2012 5:41 PM, "Gil Quim (Nokia-DXM/SiliconValley)"
<quim.gil at nokia.com> wrote:
>The existence of the Qt Project and a first Summit should make
>registration to Qt CS a lot easier.
Actually, I don't agree. See below.
>teria we can see that
>- Approvers and maintainers are known by JIRA/Gerrit as such.
>- Participants in the first Summit are known by
>some "trolls-2011" might be missing there).
>- We can tell who is in the organization team.
>- We can tell who is a sponsor.
>This makes accepting a nice % of the candidates a no-brainer task.
This was pretty much the case before as well. Those who asked for an
invitation knew that they would fit. There was really only a tiny number
of edge cases, and they were pretty obvious.
>About the invited participants, they should also have a JIRA/Gerrit or
>DevNet account. Acceptance or not will probably be an easy task as well,
>based on who invites, who is the invited and how many seats are left.
Yup. All pretty straight forward, also last time.
>I will leave to Sivan the decision to use a wiki page, a spreadsheet or
>else. In my opinion the closer to the Qt Project infra the better. For
>instance, we could have a public list where candidates would fill this
>- Qt Project membership URL: http://qt-project.org/member/nnnnn (login to
>find out & make sure your email address is correct in order to receive
>- Only code contributors: http://codereview.qt-project.org profile URL
>- Name (as printed in badge)
>- Organization (as printed in badge)
>- Select checkbox: Maintainer, Approver, Sponsor, 2011 participant,
>- Optional field: Invited by? (needs to be maintainer or organizer)
>- Requires visa support?
>- Requires travel sponsorship?
>- Tshirt: M / F S - M - L - XL - XXL (just in case we DO get budget for
>An extra field CONFIRMED would be left for the organizers. It would be
>blank by default, or OK for those confirmed.
So far so good. And that's where the actual work starts. After people
received their invitations, you need to confirm their attendance.
Otherwise you're operating with fuzzy numbers, and you will end up with
empty seats and people not getting in. All of this needs to be tracked.
In conclusion, the registration process was not the difficult or
complicated part. Keeping track of people was, especially since you need
reliable attendance numbers for food, infrastructure and potentially hotel
rooms. And to my experience, good developers are not necessarily good at
organizing themselves ("Oh? Is it next month already?"). :P
>http://qt-project.org/groups/qt_contributors_summit/members could be
>reset and the organizers would add there the participants confirmed. I
>bet this has some advantages when it comes to send notifications at once
>and collaboration between participants? And we can get them a nice badge,
We'll start a new group, for historic reasons and because of the way the
badge system works. I'll rename the old group to Qt Contributors' Summit
2011, and we're safe. Sending emails to all group members is fairly easy
but it requires that everyone is registered on DevNet and has accepted
messages from other members.
More information about the Marketing