[Debconf-team] pre-registration or registation opens and CfP announcements
Dear DebConf and DebConf Content teams: If you want to announce Call for Proposals when registration (or pre-registration) is open, we may should begin to draft the Call for Proposals. I'm not sure if it's already being done in some place. If yes, just coordinate with me or publicity team in order to publish the blog post at the same time you deliver the mail to the corresponding mailing lists. If it's not being done, we can start with the DC15 call for proposals: https://bits.debian.org/2015/03/debconf15-cfp.html Then, some things should be decided in order to publish DC16 Call: * If we provide a page with explanation about the registration process * If we stick to 20 or 45 minutes long sessions * When the first batch of accepted proposals will be announced. * Deadline for proposals. * Topics and tracks (if any) * Is cont...@debconf.org an alias to the current people in charge? Finally, we can decide to just open pre-registration or registration first, and then the CfP when it's ready. If this is what we want, I would propose to microblog the "(pre)-registration open" as soon as it's open, and keep the blog post for the CfP. (No two blog posts). Best regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] pre-registration or registation opens and CfP announcements
On 03/04/2016 07:23 AM, Laura Arjona Reina wrote: Dear DebConf and DebConf Content teams: If you want to announce Call for Proposals when registration (or pre-registration) is open, we may should begin to draft the Call for Proposals. Here's a draft in progress, starting with the DC15 CFP as a base: https://titanpad.com/1YVOp0C6vG Then, some things should be decided in order to publish DC16 Call: * If we provide a page with explanation about the registration process Registration is no longer necessary to submit an event (that was an implementation detail of summit), we can remove that text from the CFP. * If we stick to 20 or 45 minutes long sessions * When the first batch of accepted proposals will be announced. * Deadline for proposals. Sticking with approximately the same schedule as last year would mean: * First batch of approvals in April * Final deadline for event submissions May 1st * Topics and tracks (if any) The discussion we've had on the team list so far indicates that we don't have the capacity to organize formal tracks this year. Suggested topics are helpful, we can leave those in the CFP. And, tags can be added during review and scheduling if we decide they're useful. Maybe not ideal, but we have to accept that we're running in a resource constrained year, and keep a practical focus on getting things done. * Is cont...@debconf.org an alias to the current people in charge? Yes. Finally, we can decide to just open pre-registration or registration first, and then the CfP when it's ready. If this is what we want, I would propose to microblog the "(pre)-registration open" as soon as it's open, and keep the blog post for the CfP. (No two blog posts). Yes, CFP and registration are entirely independent, so launch whatever is ready, whenever it is ready. (Again, practical focus, just get it done.) Allison ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] pre-registration or registation opens and CfP announcements
Missed one. On 03/04/2016 01:11 PM, Allison Randal wrote: On 03/04/2016 07:23 AM, Laura Arjona Reina wrote: * If we stick to 20 or 45 minutes long sessions Yes, that seems to be the consensus. TBH, in several decades of conference organizing and attending, I've found 20 minute slots are too short to be useful for anything more than "hey, I had this crazy idea...". But for a new speaker, filling 45 minutes can seem really daunting, so it makes sense to offer both options, and let the speaker decide what they can handle, and what will be adequate time to do their topic justice. 20 and 45 minute lengths allow us to keep a regular schedule, always starting talks on the :00 or :30 marks, which is good for attendee sanity. Allison ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
Re: [Debconf-team] pre-registration or registation opens and CfP announcements
also sprach Allison Randal [2016-03-04 19:11 +0100]: > Registration is no longer necessary to submit an event (that was > an implementation detail of summit), we can remove that text from > the CFP. I think you still need to create a user account or authenticate through SSO though, but no additional information especially pertaining to the conference is required. -- .''`. martin f. krafft @martinkrafft : :' : DebConf orga team `. `'` `- DebConf16: Cape Town: https://wiki.debconf.org/wiki/DebConf16 DebConf17 in your country? https://wiki.debconf.org/wiki/DebConf17 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
[Debconf-team] (Draft) blog post thanking first group of sponsors
Dear DebConf, DebConf-Fundraising, and Publicity teams I've committed an initial draft for a blog post in bits.debian.org thanking the first DebConf16 group of sponsors: http://anonscm.debian.org/cgit/publicity/bits.git/tree/content/2016/dc16-welcome-its-first-sponsors.md It's work in progress: for now, I copied the similar blogpost from last year and edited adding the names of the current sponsors. I'll work on it in the following days, review/rewrite the text when needed, and add more sponsors when their logo appears in the debconf16 website ;) IMHO we should wait at least to the end of next week, and also wait until registration is open, to publish it. Best regards -- Laura Arjona Reina https://wiki.debian.org/LauraArjona ___ Debconf-team mailing list Debconf-team@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-team
