forked from ircv3/ircv3-specifications
-
Notifications
You must be signed in to change notification settings - Fork 0
/
charter
56 lines (39 loc) · 2.68 KB
/
charter
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
%pragma page-title("Charter");
# Charter
The IRCv3 working group is chartered to prototype, develop and test further incremental changes to
the IRC client protocol. It does not define any other aspect of an IRC network, such as IRC services,
or the server-to-server protocol, although the changes it develops may require cooperation from vendors
in both areas.
## Participation
Interested stakeholders are encouraged to participate in the group. We consider stakeholders to be:
* Developers of IRC daemons which are actively used;
* Developers of IRC clients with widespread usage;
* Developers of other software relating to the IRC ecosystem with widespread usage
(such as IRC services, bots, bouncers, libraries);
* Developers from IRC networks greater than 1,000 active at-peak users which have adopted
the IRCv3 specifications.
Other users may participate in the group in a semi-moderated fashion. We encourage developers of new
software relating to IRC to participate in the public resources.
## Resources
* The `ircv3/ircv3-specifications` Github repository and issue tracker. The Github repository is the
official repository containing the latest version of the official specifications. Changes are to
be submitted using a pull request. We request that pull requests not be submitted to social
media aggregators, as we have no mechanism to moderate the bug tracker efficiently.
Atheme provides the following resources to the group.
* The `#ircv3` channel at `irc.atheme.org`. This is the main public space for the working group.
You are required to follow specific rules to participate in this IRC channel, else you may be
removed at any time.
* The `#ircv3-dev` channel at `irc.atheme.org`. This is a read-only channel, where the only
participants allowed to write to it are active stakeholders as described above. The same rules
apply to `#ircv3-dev` that apply to `#ircv3`.
## Ground Rules
To ensure smooth operations of the working group, we request that:
* Participants assume good faith from other participants. The stakeholders have full moderation
privilege over the working group resources and may make moderation decisions if one or more
participants is unable to assume good faith.
* Participants do not use social media aggregators to "bomb" working group resources because they
do not personally agree with a change being made.
* Participants maintain a respectful and professional atmosphere. This means no use of coercive
threats to force cooperation.
* Participants refrain from soapboxing on the IRC channels. If there is an issue that needs that
level of discussion, a bug or pull request should be filed and discussed on the tracker.