Lines Matching refs:Group

2 LLVM Security Group
5 The LLVM Security Group has the following goals:
16 The LLVM Security Group is private. It is composed of trusted LLVM contributors. Its discussions re…
25 …ourse forums`_ asking to get in touch with someone from the LLVM Security Group. **The escalation …
28 Group Composition
31 Security Group Members
59 * Nominees for LLVM Security Group membership should fall in one of these groups:
77 … the following are necessary but not sufficient criteria for membership in the LLVM Security Group:
79 …- If already in the LLVM Security Group, has actively participated in one (if any) security issue …
80 …- If already in the LLVM Security Group, has actively participated in most membership discussions …
81 …- If already in the LLVM Security Group, has actively participated in writing or reviewing a trans…
82 … other entity, the parent entity has no more than three members already in the LLVM Security Group.
84 …- Nominees are trusted by existing Security Group members to keep communications embargoed while s…
89 …s, or may be nominated by a third party such as an existing LLVM Security Group member. The nomina…
98 …Group membership is supported by a majority of existing LLVM Security Group members, then it carri…
103 …Group membership is finalized, the successful nominee should accept membership and agree to abide …
108 * At least every six months, the LLVM Security Group applies the above criteria. The membership lis…
109 * Any Security Group member can ask that the criteria be applied within the next five business days.
110 …r of the LLVM Security Group does not act in accordance with the letter and spirit of this policy,…
111 …Group member who blatantly disregards the LLVM Security Policy may have their membership temporari…
112 * The LLVM Board may remove any member from the LLVM Security Group.
117 Every year, the LLVM Security Group must publish a transparency report. The intent of this report i…
122 Privileges and Responsibilities of LLVM Security Group Members
128 LLVM Security Group members will be subscribed to a private `Discussion Medium`_ (*FUTURE*: see sec…
133 Members of the LLVM Security Group will be expected to treat LLVM security issue information shared…
136 * If the LLVM Security Group agrees, designated members may share issues with vendors of non-LLVM b…
137 * If the LLVM Security Group agrees, key experts can be brought in to help address particular issue…
142 Following the process below, the LLVM Security Group decides on embargo date for public disclosure …
147 Members of the LLVM Security Group are expected to:
162 The medium used to host LLVM Security Group discussions is security-sensitive. It should therefore …
174 We also occasionally need to discuss logistics of the LLVM Security Group itself:
188 * Within two business days, a member of the Security Group is put in charge of driving the issue to…
189 * Members of the Security Group discuss in which circumstances (if any) an issue is relevant to sec…
191 …Group members can recommend that key experts be pulled in to specific issue discussions. The key e…
193 …ent versions to old versions cannot always work. It is up to the Security Group to decide if such …
194 * The Security Group figures out how the LLVM project’s own releases, as well as individual vendors…
195 * Embargo date can be delayed or pulled forward at the Security Group’s discretion.
204 The LLVM Security Policy may be changed by majority vote of the LLVM Security Group. Such changes a…
210 *FUTURE*: this section will be expanded once the Security Group is formed, and it agrees on an init…
214 …ntain these security properties over time. In all cases the LLVM Security Group should be consulte…
216 …is security process or not, err towards assuming that it is. The Security Group might agree or dis…