Mobus Operandi

A mob programming community

ZulipGitHubTwitter

Add a mob

Mobs are specified in files in the mobs directory. Take a look at some of those files for examples.

To add a mob, submit a pull request that adds a mob file.

  1. MobFile

    The contents of a mob file

    1. titlescalar

      The mob's title

      Example:

      Agile Bandits
    2. subtitleoptionalscalar

      An optional mob's subtitle

      Example:

      Hackin' and cruisin'
    3. participantssequence of Participant

      Regular participants of the mob

    4. schedulesequence of YamlRecurringSession

      The mob's regular schedule

    5. background_colorColor

      Color of the background of calendar event blocks

      Example:

      aliceblue
    6. text_colorColor

      Color of text inside calendar event blocks

      Example:

      orangered
    7. linksoptionalsequence of Link

      Links associated with the mob

      - !YouTube @agilebandits
    8. freeform_copyMarkdown

      A description of the mob, the purpose of it, its past attainments, etc.

      ## What we do

We study the BrainShock programming language.
    9. statusStatus

      The mob's current status

      Example:

      !Public |
  ## Just show up!

  [Room link](https://meet.jit.si/MedievalWebsPortrayLoud)

  2. Participant

    A participant in a mob

    One of:
    1. !Hidden

      A mob member who prefers to remain anonymous

      Example:

      !Hidden
    2. !PublicPerson

      A mob member who wishes to be publically listed"whitespace-nowrap" "font-mono"

      Example:

      !Public
name: Forbany Klenbin
social_url: https://example.com/fk
avatar_url: https://example.com/fk.png

  3. Person

    The public details about a person

    1. namescalar

      The person's name

      Example:

      Nompomer Pilento
    2. social_urlUrl

      A social URL

      Example:

      https://example.com/np
    3. avatar_urloptionalUrl

      An avatar image URL

      Example:

      https://example.com/np.png

  4. YamlRecurringSession

    Specification for a recurring session

    1. frequencyscalar

      Frequency of the recurrence in RRULE format

      Example:

      FREQ=WEEKLY;BYDAY=MO,TU,WE,TH
    2. timezoneTz

      The schedule's timezone

      Example:

      Africa/Dakar
    3. start_datescalar

      Date of the first session of this schedule

      Example:

      2023-02-27
    4. start_timescalar

      Session start time

      Example:

      04:00
    5. durationscalar

      Session duration in minutes

      Example:

      180

  6. Status

    A mob's status

    One of:
    1. !ShortMarkdown

      This mob is not active yet because it needs more members.

      The value explains how to apply.

      Example:

      !Short |
  To apply contact [Kelly](https://example.com/kelly).
    2. !OpenMarkdown

      This mob is taking applications for new participants.

      The value explains how to apply.

      Example:

      !Open |
  To apply contact [Dawn](https://example.com/dawn).
    3. !FulloptionalMarkdown

      This mob is not currently taking applications.

      The value is optional.

      Example:

      !Full |
  We are currently full.
    4. !PublicMarkdown

      This mob's sessions are open for anyone to join.

      The value explains how to join.

      Example:

      !Public |
  [Room link](https://meet.jit.si/MedievalWebsPortrayLoud)
    5. !TerminatedoptionalMarkdown

      This mob has been terminated.

      The value may explain why.

      Example:

      !Terminated |
  Our goals have been accomplished and we moved on to other activities.

7a5eed2ccd48783827dc291b91448be2f79e6421
Source