https://github.com/assert-kth/kth-software-talks

How we run the KTH Software meetups

https://github.com/assert-kth/kth-software-talks

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (9.4%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

How we run the KTH Software meetups

Basic Info
  • Host: GitHub
  • Owner: ASSERT-KTH
  • Default Branch: main
  • Size: 22.2 MB
Statistics
  • Stars: 1
  • Watchers: 15
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 5 years ago · Last pushed about 1 year ago
Metadata Files
Readme

README.md

KTH Software Research Meetups

Documentation for meetup organizers

The main page of the KTH Software Research Meetup: https://www.meetup.com/KTH-Software-Research-Meetup/

A General Procedure of Organizing a Meetup

The source information of a meetup

Usually, you will get the information about an activity that needs to be announced on the meetup by email from Martin and Benoit. If you find an interesting seminar that could be disseminated via the meetup, double-check it with Martin and Benoit.

The necessary information for announcing a meetup should include: 1) The title of the seminar
2) When and where (zoom link/meeting room) the seminar will be held
3) An abstract of the topic 4) A short biography of the speaker

If a meetup is held remotely, you can use Zoom to schedule a meeting so that you will get the Zoom link in advance. If a meetup is held on site, you can use KTH Outlook Web App to book a meeting room (more info here).

Here is an example of the information: Example event

Announcing a meetup

You can use the feature copy event on one of the past events to reuse the structure.

  • Update the information for the new event
  • Fill the blanks
  • Update the keywords for the specific event

Remember to make sure it is clear for new people how they can attend, e.g. by having accurate "How to find us" info, and filling in an additional "attending" section in the meetup event description, e.g.

Attending: We will be available to open the doors on E-house's 4th floor approximately 10 minutes before the session.

Publishing

Click the Publish button at the bottom right corner. Note that all the members in the meetup will see the event after publishing it. If you are unsure about the page, click save as draft instead and send the preview link to Martin and Benoit for discussion. This is because all the organizers have access to review the drafts.

When the event is published, send the actual link to Martin, Benoit, and maybe the speaker also, to see if the page needs any revision. If everything is settled down, click the announce button on the event page so that all the members in the meet up will receive a notification about this event. You could also spread the news via the ASSERT mailing list.

after announcing: remember to pay attention to the comments on the event page. Sometimes we might have participants who ask questions there. You can turn on the notification for event updates via your account setting page: https://www.meetup.com/account/

Hosting a meetup

If the meetup is hosted online

If you are the host of the Zoom meeting, remember to start the meeting in advance (e.g., 5 mins before the event starts). It's also good to add someone as an alternative host, just in case you are not available during the meeting.

If the meetup is hosted on site

For some meeting rooms (e.g., room 4523 on our floor), external participants need our help to get inside the corridor. You can put a card which contains your contact information at the entry door. In this way, a participant could make a call to you if he/she arrives too early. You could also wait a little bit around the entry before the event starts.

Owner

  • Name: ASSERT
  • Login: ASSERT-KTH
  • Kind: organization
  • Location: Sweden

assertEquals("Research group at KTH Royal Institute of Technology, Stockholm, Sweden", description);

GitHub Events

Total
  • Delete event: 1
  • Push event: 1
  • Create event: 1
Last Year
  • Delete event: 1
  • Push event: 1
  • Create event: 1