[OSCTC-planning] picking dates for Open Source Comes to Campus this fall

[Remy DeCausemaker]

September 20th is Software Freedom Day, which is more of a bonus than a
conflict. OSCTC is a great fit for a celebration event. We'll be running
our annual event at RIT that day, so I wouldn't be able to travel, but
don't let that discourage you :)

The other days also seem quite reasonable too. Good work.
--RemyD.

P.S. - Also, you should check out the brand new http://bigredhacks.com
Cornell hackathon.
On Jul 1, 2014 4:25 PM, "Shauna Gordon-McKeon" <shaunagm at gmail.com> wrote:

> We're trying a different sort of schedule this fall: instead of running
> events on a semi-random set of days, we're marking off three weekends to
> run events during. I'm trying to pick dates so that I can start scheduling
> with schools.
>
> Factors that play a role:
>
> - the weekends should be at least four weeks apart so that the planning
> burden is manageable
> - holidays (I am consulting this site:
> http://www.timeanddate.com/holidays/us/)
> - common midterms/finals time (difficult to avoid)
> - my own availability
>
> The weekends I've come up with are:
>
> - September 20th & 21st
> - October 18th & 19th
> - Nov 15th & 16th
>
> These are all four weeks apart, and on dates that work for me.  The
> holiday site I consulted suggests they overlap no major holidays.  Some of
> them might overlap with a given school's midterms, but none should overlap
> with finals and hopefully one of the three weekends would work for a school.
>
> What do folks think?  Am I missing anything obvious?  Do these overlap
> with any major conferences that will draw away potential mentors?
>
> ~ Shauna
>
> _______________________________________________
> OSCTC-planning mailing list
> OSCTC-planning at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/osctc-planning/attachments/20140702/079c3965/attachment.html>