Go-SIG

Fedora's Go Special Interest Group

Group of Fedora users, developers and contributors interested in Go in any way that want to contribute to improvement of packaging and general user experience in relation to Go.

Are you interested in building and deploying your Go based Application and Projects on Fedora? Are you interested in packaging Go based applications for Fedora? Are you interested in using Fedora as your system for developing Go based Applications and Projects? Or generally, you want to do anything with Go on Fedora. This is the group for you to share your experiences and concerns and look for help from people with similar interests.

Getting Involved

Come and hang out with us at our communication channels and apply for membership.

All you need is to have an FAS account and be a packager. Add comment in the issue at go-sig. "Please add me" is enough, but brief self-introduction is appreciated.

Communication channels

• Discourse
• Mailing List
• Matrix Room
• IRC Channel
• Meeting

N.B. the Matrix Room and IRC Channel are bridged, i.e. both access the same shared chat from different interfaces.

Running IRC meeting

To start meeting use command #startmeeting Go SIG meeting.

Wait for all the participants to show up.

List of topics that are brought up at that meeting is determined by issues tagged with meeting in the pagure issue tracker.

To start covering topic #topic "TOPIC" and in same way to start next one... It is good to note action items via #action "USERNAME" what they will do and other general noteworthy information via #info SOME NOTE.

After covering all topics schelduled it is good to start an Open Floor discussion until there is nothing to discuss or time runs out.

To end the meeting use command #endmeeting. After the meeting ends minutes and log of the meeting is available at the meetbot.

Common order of meeting is:

• #topic Roll Call
• allowing participants to be #chair-ed by the chair
• tagged issue from the SIG's issue tracker
• #topic [issue title] [URL to the issue]
• #topic Open floor
• Here anyone pressent can rise any Go SIG related topic, news or issue. If the topic should be bigger it is better to file a issue in the issue tracker.
• #topic Next Meeting
• Who will chair next meeting?
• Meetbot docs

Voting

On some topics, we will need to vote. The following rules apply to the voting process.

For Regularly Scheduled Meetings:

A quorum for the meeting is 5 people, or 51% of the members of the SIG as listed in the group, whichever is lower. Votes are "+1" (in favor), "-1" (against), or +0 (abstain). Voting items must pass with a majority of the members voting at the meeting.

For General Ad-Hoc Votes:

• All ad-hoc votes will be held via pagure issues in the go-sig repo.
• Ad-hoc votes must be announced on the current primary mailing list for Go-SIG.
• Ad-hoc votes must be open for at least three working days (see below) after the announcement.

At least 5 people must vote, or 51% of the SIG membership, whichever is less. Votes are "+1" (in favor), "-1" (against), or +0 (abstain). Votes pass by a simple majority of those voting.

For Urgent Ad-Hoc Votes:

• All ad-hoc votes will be held via pagure issues in the go-sig repo.
• Ad-hoc votes must be announced on the current primary mailing list for Go-SIG.
• Ad-Hoc votes must be open for at least three hours after the announcement.

At least 5 people must vote, or 51% of the SIG membership, whichever is less. Votes are "+1" (in favor), "-1" (against), or +0 (abstain). Votes pass by a 2/3 majority of those voting (round up).

Working days: non-holiday weekdays. Relevant holidays are the national holidays of the USA, Western Europe, India or any other territory that any member might be living in. If any voting period extends over such holiday, the member of the SIG that is affected by such holiday should mention that in the vote so the vote period can be extended.