include::ROOT:partial$attributes.adoc[]

= Additional Policies

* The {team_name} will have a regular face-to-face in November each year.
  The region will be dependent on the location of {team_name} members at the time.
  We will also conduct in-person meetings at Flock and DevConf.CZ for {team_name} members in attendance.
* Fedora Magazine is the venue for user-targeted communication and the Community Blog is the venue for contributor-targeted communication.
* The {team_name} supports greater efficiency in the infrastructure to allow more to be done, even when this means that we move away from self-hosted or self-maintained infrastructure.
* The Fedora Project wants to advance free and open source software and as a pragmatic matter we recognize that some infrastructure needs may be best served by using closed source or non-free tools today.
  Therefore the {team_name} is willing to accept closed source or non-free tools in Fedora’s infrastructure where free and open source tools are not viable or not available.
* Because we value participation over strict bureaucracy ('Friends' foundation!) candidates for Fedora elections may be accepted within a reasonable grace period after the deadline.
  However, be aware that this may mean missing out on Fedora Magazine interviews, town halls, and other opportunities for campaigning.
* The {team_name} has no objections to events being held in the local language or in English, and separate events can be held if there are multiple audiences.
  We encourage event organizers to specify the language(s) for their event.
* Unspent budget allocated to the $150 event program will be pulled into the {team_name} budget at the end of each fiscal quarter.
* The {team_name} may choose to withdraw Fedora's support from events or other activities that involve fiscal sponsorship or use of Fedora trademarks when it determines that participation is not in the interests of the Fedora Project.
  Decisions to withdraw support will be published in venues normally used for {team_name} decisions.
  Deliberation and reasoning for the decision should be public to the extent possible.
  The {team_name} will engage with the committee/group/team that is involved with the event in question to ensure their input is considered.
