[wp-meta] [Making WordPress.org] #1183: Checkbox for Contributor Days

[Making WordPress.org]

#1183: Checkbox for Contributor Days
----------------------------------------+---------------------------
 Reporter:  miss_jwo                    |       Owner:  DrewAPicture
     Type:  enhancement                 |      Status:  assigned
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |
----------------------------------------+---------------------------

Comment (by coreymckrill):

 Replying to [comment:13 DrewAPicture]:
 > @coreymckrill OK, and what about the WordCamp application? I'm assuming
 there's currently a tie-in between the information entered there and what
 ends up in the WordCamp post type, no?

 My understanding is that dates and venues are usually not determined until
 after the application has been vetted/accepted. But maybe a question in
 the app like, "Will your WordCamp event include a day or session focused
 on contributing to the WordPress project?"

 > From the discussion here, I think the first best step would be to create
 a new session type for contributor days, and tie to whether a contributor
 day has been "enabled" for the WordCamp. How the thing will actually work
 should be determined by somebody from the design team. #designfirst

 The existing session types are "Regular Session" and "Break, Lunch, etc.".
 The only place they are used, as far as I can tell, is in the logic for
 the `[schedule]` shortcode to determine whether a particular item in the
 schedule table should link to a session post. So in that regard,
 "contributor" sessions would still be "regular" sessions.

 This isn't to say we shouldn't go the `type` route. I just think it's
 worth taking into account that co-opting the `type` parameter for a
 different purpose might have unintended side effects.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1183#comment:14>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org