Organisation of the SC Guild


The weekly report

  1. Every monday the editor will publish a short, descriptive report on the activities of the guild during the preceeding week.

  2. The editor is CSDUMMI and tomat0 if he is unavailable.

  3. Anything that every member of the guild should know, must be sent to the editor to be included in the weekly report.

  4. The report will be published in a topic on

The forum

  1. is the location for long-form discussion of the guild. There is a category called sc-guild for this purpose.


  1. The Matrix chat is for optional-but-quick communication.

  2. Matrix will not be used as a basis of the weekly reports.

Video Conferences

  1. Video conferences should not aim to be with all guild members.

  2. Consider time zones when scheduling video conferences.

  3. Keep video conferences spontaneous.

Issues and Pull Requests

  1. These serve for technical discussion relating to the respective repository.
  2. For discussions about the group, it’s structure and group decisions, please use the forum.
  3. Feel free and encouraged to assign yourself to issues, milestones and PRs.
  4. If a PR is reviewed by a second member, you can merge it.


  1. Announcement

    • Gather people

    • Members fill out a survey.

    • Logistics are laid out

  2. Gather ideas

    • Use the forum to discuss the ideas

    • From all ideas, three ideas are prepared with a ROADMAP, time estimates, milestones and the broad strokes of the architecture.

  3. Voting

    • Vote on the three prepared ideas to determine what idea the guild will develop.

    • Vote on the license the guild should use for any new projects developed (unless the project is a fork).

    • Proposals for the license can be submitted to the editor. Only one license for any broad category will be voted on (one permissive, one copyleft, etc.)

  4. Start work

    • Create / fork a repository on our forge.

    • Add LICENSE, ROADMAP and Milestones from idea proposal

    • Project initialization (poetry init, npm init, etc.)

  5. Development


  • As source forge we will use

  • We set up CI using woodpecker

  • If we fork an existing project from another source forge, we will still use Codeberg for development. Once we have something we want to upstream, we can create a repository on the other source forge as well.

See: socialcoding