Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time


This page documents RITlug general meetings. Topics include meeting format, meeting topics, how to plan a meeting, and what to do after a meeting. Occasionally, there are "special" meetings or project meetings, which may follow a different format (TigerOS meetings, game nights, etc.). Special meetings are not covered by this page.

Meeting checklist


  1. Plan topic(s) for meeting
  2. :doc:`Announce meeting and topic <../tasks/announcements>`
  3. Prepare presentation, slides, or handouts
  4. Advertise special topics (e.g. posters)
  5. :doc:`Create sign-in form on CampusGroups <../tasks/create-campusgroups-signin>`


  1. Ensure at least one eboard member is present prior to meeting start time (15 minutes preferably)
  2. At start, share any announcements and introduce presenter
  3. Ensure at least one eboard member is present until the end of the meeting


  1. Collect slides as PDF from presenter, post to RITlug website
  2. If guest speaker, be sure to thank them
  3. If no other classes after, notify a lab assistant at The Cage [1] that the room is no longer in use

Date and time

At the start of each semester, eboard members decide a date and time for RITlug general meetings. A date and time should be selected based on availability of all eboard members. Times with better availability for all eboard members are preferred. This helps build in flexibility in case of illness or unexpected circumstances, if someone is unable to attend.

If possible, a consistent date and time across semesters is preferred. This helps eboard and club members plan their semester accordingly. However, if a changed time cannot be avoided, it is better to choose a more flexible time than the same time as a previous semester.

Historically, RITlug meetings are held on Friday evenings, from 4:00pm until 6:00pm.

Pre-meeting preparations

Planning ahead for a meeting is the most important step to run a successful meeting.

Generally, meetings should have a topic five days before the meeting. Once a topic is decided, an email announcement and Slack announcement should be sent (see :doc:`../tasks/announcements`). The sooner an announcement is shared, the better probability of better attendance.

Choosing meeting topics

There are no explicit restrictions for meeting topics. Topics are usually related to Linux. However, open source technology or general technology are also acceptable. It is best when topics are something an eboard member is genuinely interested in.

Sometimes, a guest speaker or club member may propose a topic. If it is someone outside of the eboard, they should submit a talk title and a 3-4 sentence abstract of their talk. Use best judgment if the topic is a good fit for RITlug. All talks should aim to teach and share knowledge. Anything that creates humor at the expense of someone else or a group of people, or contradicts RIT student behavior policy is not acceptable.

Additionally, consider breaking the idea of a "traditional" talk or presentation. Sometimes the best RITlug meetings were not talks or presentations, but game nights or lightning talks. What is detailed here is not the limit to your creativity.

Reusing presentations

Generating new content every week for two semesters is hard. There is a large archive of past presentations by RITlug eboard members in the RITlug Google Drive folder. Reusing past presentations is acceptable, assuming they were not recently given. Avoid giving the same presentation more than once or twice a year.


Surprisingly, posters are wildly effective for advertising and promoting an event. For special topics or more detailed presentations, RITlug prepares and hangs posters around campus (not only GCCIS). These are usually effective for drawing interest and building some "hype" for a presentation.

In the past, we tried hanging posters every week, but for the small size of our eboard, this is challenging. If possible, try to involve club members to help with this task. If not, prioritize topics that may be interesting to outsiders. Then, try to hang posters two weeks ahead of a presentation or meeting. Posters are not as effective if posted during the same week as a scheduled presentation.

Running the meeting

This section covers both the general schedule of a meeting and the format of how they run.


Exact structure and order of events depends on the semester.

In the past, RITlug met late on Friday evenings, and sometimes people had classes that ended in the middle of a RITlug meeting. Because of this, we chose to follow this structure:

  • 30 minutes: General discussion / announcements
  • 1 hour: Presentation / workshop
  • 30 minutes: General discussion / Q&A


Meetings are usually split into the two parts: presentation and general discussion.


The presentation or workshop is the core part of the meeting. Speakers should expect to have a full hour and try to fill that time. To help with this, questions and comments are generally encouraged during the meeting, so long as they are on topic and courteous. Questions help fill the time and help build better understanding of the topic as we go.

This format may be foreign to a guest speaker. Sometimes, club members may have a question or comment, but it may come across as an interruption. If hosting a speaker who is not a regular attendee of meetings, advise them about this ahead of time. You may also suggest they explicitly mention they will take questions and comments at the end of the presentation.

This format has not been problematic. However, the "interruptions" are usually on topic and courteous. As an eboard member, if a side conversation stretches out of hand, do not be afraid to help the presenter and remind attendees there is time for questions at the end.

General discussion

The general discussion parts of the meeting are unstructured. This time is helpful for deeper questions on what was presented or for club members to get help with Linux or other tech problems. Other times, wider discussion on Linux, its community, or open source fit into this time.

As an eboard member, this time is ideal for sharing club announcements or updates. For example, advertising events in the FOSS community, upcoming hackathons, or announcing elections are good topics. Sometimes, the best way to convey information is in person. Do not hesitate to take advantage of the time to talk about RITlug too.

Additionally, this is a great time to get to know the community better. If you notice a new attendee or even a regular, try to include them in a conversation. Ask them how their semester is going, see if they are working on any fun projects, or let them bring something up too. If only a few people are present, it can also be a good opportunity to solicit feedback on how members think things are going.

Post-meeting wrap-up

There are three steps to wrapping up a meeting:

  • Collect PDF copy of slides from speaker
  • Thank guest speaker and escort them out, if applicable
  • Notify lab assistant that room is no longer in use, if applicable

RITlug typically collects PDF slides from speakers to share on our website. If the presenter is not a member of eboard, ask if they would like to share their slides with the club community. If so, request a PDF copy of their slides or presentation material to share. After, post the PDF slides to the website as a new talk (see :doc:`../infrastructure/website`).

If the presenter is a guest speaker, be sure to thank them for their time and participation in RITlug. Offer to help them to their next destination if they are leaving the meeting. A small token of appreciation can also be nice (e.g. a thank you card), especially if it is someone who made a special visit or is a regular supporter of RITlug. Of course, it is also a good idea to thank your fellow eboard members for their time on a presentation too!

Lastly, notify a lab assistant in The Cage [1] if there are no scheduled classes or meetings after RITlug. In the past, RITlug was the last scheduled session in the lab we used. The GCCIS administrators request RITlug to notify a lab assistant when we are finished, so they can lock the room for the night. The administrators usually remind eboard members at the start of the semester, but be mindful whether there is anything after a general meeting.

[1](1, 2) "The Cage" is the equipment closet room for IST lab courses. It is located on the second floor of GCCIS towards Slaughter Hall. GOL-2320 is the System Administration Lab, which has direct access to The Cage.