The wikis are now using the new authentication system.
If you did not migrate your account yet, visit

openSUSE:Board best practices

Jump to: navigation, search

Best practices

This page collects so called best practices for common board tasks plus templates for handling stuff, mostly by email.

Board Meetings

Meeting reminder/invite

Two days before regularly scheduled board meetings, board@ receives an invitation/reminder. You can easily adjust timing and text of that reminder via .

As we started holding those meetings in public in June 2021, such an invitation should also go to project@ and include

  • date, time (and time zone),
  • virtual location,
  • the current tentative agenda/topics, and
  • how to submit topics.

Minutes taking

Board members alternately take minutes, in alphabetical order based on first names; by default the chair moderates the meeting.

Draft minutes should be sent to board@ within a day (or two) after the meeting. and after review by, ideally at least two others, to project@. It shall also be added to .

Minutes should also include an early invitation for the following meeting.

Action items

The minutes taker shall also

  • create tickets for AIs that came up, and
  • close resolved tickets (such as agenda items fully covered).

Trademark-related issues

Domain Names

Like other trademark-related topics all openSUSE Internet domains such as country-/language-specific domains and domains used by the marketing team are handled by the board.

After the board has agreed, domain will be registered by the trademark owner (currently SUSE, in the future this might be the openSUSE Foundation). SUSE IT is managing those domain registrations. Cost is covered by SUSE. DNS is managed by the openSUSE Heroes.

openSUSE country-/language-specific domains will only be made available to known and trusted openSUSE members, and ideally a group of those to avoid singe points of failure.

They are intended for language- or country-specific presence and use cases and should not "compete" with contents and services provided via our general infrastructure. Two possible examples are for a presence in Japenese language and for a presence of the Mauritian community.

Such domains are to serve subsets of the global openSUSE community, which entails abiding by the openSUSE Code of Conduct and all other rules and practices.

Practical steps to register a new domain:

  1. Discuss among the group of people later using that domain, which can be the openSUSE marketing team or a local community/group of volunteers.
  2. Approach the board, either directly or via
  3. When/if the board has approved, create a ticket in if there isn't one yet.
  4. The chair of the board (or possibly another board member) is going to liaise with SUSE IT.
  5. They also confirm the openSUSE ticket.
  6. openSUSE Heroes set up DNS for the new domain.
  7. SUSE IT registers the domain pointing to DNS servers provided by openSUSE (currently ns1/ns2/
  8. Have fun!


Joining the Board

  • After the handover meeting, send an email to to be provided with Wiki admin access to be able to edit the Board pages.
  • Subscribe to by sending an email to (Alternatively, as of 2021-03-08 Gerald has admin access.)
  • Add yourself to the Board and Board history Wiki pages.
  • Give the Board pages a thorough read.


First Warning + 3 months ban

Hello [name],

the board has received a complaint about your behavior [place where it happened].

We have reviewed the incident during our last board call and came to the conclusion that your behavior was not in line with the way we want to interact with each other and is a breach of our code of conduct.

The board has decided to issue a *warning* to you and ban you from the openSUSE mailing lists and social media channels for three months.

After that period you are welcome to participate again.

If you continue to misbehave, you will be completely banned from the openSUSE mailing lists & social media channels.

On behalf of the openSUSE Board [Board Member's name]