Development Meetings

From MasonSRCT's Wiki
Jump to: navigation, search

Development meetings are not subject to the rigorous standards outlined above. They are entirely optional meetings. Development meetings will be used to provide developers and contributors with an opportunity to meet in person and work together on projects in a relaxed atmosphere. There are no time or attendance limits, requirements, or expectations placed on development meetings. -- SRCT Constitution

Development meetings can be workshops, devoted hacking on a specific project, or additional coding challenges. They give students extra time beyond the constraints of workshops at organizational meetings, or allow focused on development in real life, instead of solely communicating through Slack.


a) Try to make your arrangements by the preceding Wednesday, so it can be announced at the weekly organizational meeting.

b) Do your organizing not in #general, but amongst developers, or in #meeting-planning. Use #general for announcements, thus limiting the number of pings to default channels to one. Remember that when you @channel #general, you are sending a push notification or email to everyone who's ever joined. Users cannot leave #general. Make sure to mirror the Slack announcement on Twitter.

c) Book a Fenwick or JC library study room for their max length--like four hours--of a sufficient capacity. Study room sizes range from 2 to 8, and you should book for at least four. Some rooms designed for four people actually comfortably fit five or even six.

The reservation system is here,, along with their regulations.

d) The best availability times are usually between lunch and dinner on a Saturday or Sunday (12:30-4:30). If there are religious obligations, you can switch between days every other week. Observant Jews cannot use electricity on Shabbat, from Friday evening to Saturday evening.

e) Discuss availability with other developers such that you can have two people to staff it during that time so everyone can be helped out. Two people practically often translates to one person on a whiteboard and one person quietly helping out, or one person during one part of the meeting and another trading off for the remainder.

f) While you can encourage people to arrive at the beginning, if possible, try to structure your curriculum such that anyone can come in at any point during the meeting time for however long they want.

g) For supplies, remember to bring a power strip and whiteboard markers-- during the winter, an electric tea kettle and tea assortment is nice to have for everyone. If you're going to be speaking or presenting, have a water bottle or cough drops so your voice doesn't become hoarse.

h) If possible, see who can bring physical copies of relevant development books. Two Scoops of Django and Don't Make Me Think are org favorites. The latter is available online through Mason's libraries.

Guiding Newcomers

Be nice. :-)