With the opening of Core Conversation session submissions on January 1, we'd like to have adequate publicity, so probably a blog post from Drupalcon, tweets, etc. I think Dries will also blog. I'd be happy to write something, or we can just go with a standard announcement recycled.

Thanks!

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Here's a blog article that may be used. Note that the links must be filled in correctly before it can be used.


Session submissions for the <a href="...">Core Conversations track</a> at Drupalcon Denver are now open.

Since it was introduced at Drupalcon San Francisco, the Core Conversations track has grown to become a fundamental place for contributors to promote new ideas, discuss community issues, and present problems for brainstorming.  Core conversations cover technical topics, community needs, existing initiatives, and new proposals, among other things, and are aimed at those who are contributing in the Drupal Community.

If you're a contributor to the Drupal community, consider <a href="...">proposing a Core Conversation session</a> today. Session submission closes January 31, 2012 at midnight Denver time (GMT-7).

Core conversation sessions will be selected from among the submissions by a group consisting of Larry Garfield, Randy Fay, and Dries Buytaert in early February, and the selected sessions will be announced on February 16, 2012.
webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

One addition to make to that post, which otherwise looks great, is that this is going to be like DrupalCon Chicago/London where the Core Conversations is a track happening during the normal conference. Been getting a few questions about whether it would be "pre-con" or "during-con" from various folks.

cyberswat’s picture

cyberswat commented

I agree ... we should be completely clear that core conversations happen concurrently with the regular schedule as we have hosted both approaches in the past.

I feel that your targeting a different demographic than the regular sessions and have the expectation that your session submitters will send you quality submissions. Otherwise, I would suggest a few notes on the importance of verbosity to avoid submissions along the lines of "I am FOO therefore you should select me". You may also want to highlight that the cutoff for submissions is a firm deadline and that late submissions will not be considered without a high amount of wand waving and pixie dust. I've noticed a bit of ... procrastination ... when it comes to these kinds of deadlines.

Nice write-up Randy.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

Well.... in this context, I actually think "I am FOO and you should select me" is perfectly fine. I attend Core Conversations because I want to hear from all the FOOs. If I'm interested in only hearing from FOOs who also happen to be good at putting a session proposal together, and/or are excellent speakers, then I will attend the main Con.

However, I agree that putting at least enough time into a proposal so it is understandable by people who don't set their home page to /project/issues/drupal is a good thing, and we should encourage that. ;)

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

I also think we should make the deadline as close to the con as possible, if we're not going to let it slip. The reason these things tend to slip btw isn't because people are lazy, it's because there might literally be some radical new awesome community initiative that simply doesn't materialize until 2 weeks before the con when people are in DrupalCon fever. We should go for the best possible session material, not get hung up on dates and process, IMO. :)

coltrane’s picture

coltrane
he/him
commented
Status: Active » Needs review

Is this ready to go? Edit: Or if the dates are being changed let's continue discussion.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Needs review » Reviewed & tested by the community

Sorry, I'm working on other things in Nicaragua and haven't been too available. I'm taking the liberty of marking this RTBC. Neither Dries nor Cress responded about changing the date, and of course session submitters need time to prepare their sessions as well (and with these dates end up with just a month). So let's leave the dates as is. I added a sentence about it being a parallel track.

I have no objection to minor edits to this as you see useful. Note that the links have to be fixed of course.

Session submissions for the <a href="...">Core Conversations track</a> at Drupalcon Denver are now open.

Since it was introduced at Drupalcon San Francisco, the Core Conversations track has grown to become a fundamental place for contributors to promote new ideas, discuss community issues, and present problems for brainstorming.  Core conversations cover technical topics, community needs, existing initiatives, and new proposals, among other things, and are aimed at those who are contributing in the Drupal Community. At Denver, the Core Conversations track will run in parallel with all the other sessions, just as it did in Chicago and London.

If you're a contributor to the Drupal community, consider <a href="...">proposing a Core Conversation session</a> today. Session submission closes January 31, 2012 at midnight Denver time (GMT-7).

Core conversation sessions will be selected from among the submissions by a group consisting of Larry Garfield, Randy Fay, and Dries Buytaert in early February, and the selected sessions will be announced on February 16, 2012.
coltrane’s picture

coltrane
he/him
commented
Status: Reviewed & tested by the community » Fixed

This will go out tomorrow (Monday) unless there is any other news being published. I'll coordinate with the rest of the team.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

Thanks so much!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.