Content about SIGs on governance.o.o
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

sigs.yaml 10KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288
  1. Ansible:
  2. chairs:
  3. - name: Mohammed Naser
  4. irc: mnaser
  5. email: mnaser@vexxhost.com
  6. - name: Kevin Carter
  7. irc: cloudnull
  8. email: kecarter@redhat.com
  9. scope: >
  10. Ansible is an orchestration tool that is becoming increasingly common
  11. in usage across many parts of OpenStack. There are a few deployment
  12. projects that are using it, alongside many of our CI systems. This
  13. SIG exists to help create a colloborative space between different
  14. interested parties to share Ansible code under one group.
  15. status: active
  16. url: https://etherpad.openstack.org/p/ansible-sig
  17. API:
  18. chairs:
  19. - name: Chris Dent
  20. irc: cdent
  21. email: cdent+os@anticdent.org
  22. - name: Ed Leafe
  23. irc: edleafe
  24. email: ed@leafe.com
  25. - name: Michael McCune
  26. irc: elmiko
  27. email: msm@redhat.com
  28. scope: >
  29. Formerly known as the API-WG, the API SIG scope is to improve the developer
  30. experience of API users by converging the OpenStack API to a consistent and
  31. pragmatic RESTful design. The working group creates guidelines that all
  32. OpenStack projects should follow for new development, and promotes
  33. convergence of new APIs and future versions of existing APIs.
  34. status: active
  35. url: https://wiki.openstack.org/wiki/API_SIG
  36. Auto-scaling:
  37. chairs:
  38. - name: Rico Lin
  39. irc: ricolin
  40. email: rico.lin.guanyu@gmail.com
  41. - name: Duc Truong
  42. irc: dtruong
  43. email: duc.openstack@gmail.com
  44. - name: Zane Bitter
  45. irc: zaneb
  46. email: zbitter@redhat.com
  47. scope: >
  48. Auto-scaling SIG scope is to improve experience on develop, operate, and use
  49. autoscaling and its related features (like metering, cluster schedule,
  50. life cycle management) and to coordinate across projects and communities
  51. (like k8s cluster autoscaling on OpenStack). Also provide a central place
  52. to put tests, documentations, and even common libraries for Auto-scaling
  53. features.
  54. status: active
  55. url: https://docs.openstack.org/auto-scaling-sig
  56. Bare Metal:
  57. chairs:
  58. - name: Chris Hoge
  59. irc: hogepodge
  60. email: chris@openstack.org
  61. scope: >
  62. The scope of the Bare Metal Sig is to promote the development and use
  63. of Ironic and other OpenStack bare metal software. This will include
  64. marketing efforts like case studies of Ironic clusters in industry
  65. and academia, supporting integration of Ironic with projects like
  66. Airship and the Kubernetes Cluster API, coordinating presentations
  67. for industry events, developing documentation and tutorials,
  68. gathering feedback from the community on usage and feature gaps, and
  69. other broader community-facing efforts to encourage the adoption of
  70. Ironic as a bare-metal management tool.
  71. status: active
  72. url: https://etherpad.openstack.org/p/bare-metal-sig
  73. Containers:
  74. chairs:
  75. - name: Jean-Philippe Evrard
  76. irc: evrardjp
  77. email: jean-philippe@evrard.me
  78. scope: >
  79. The scope of the Containers SIG is to share practices for the
  80. build, deploy, and operate of OpenStack using application
  81. containers. This is not another deployment tool of containers.
  82. Instead, this SIG should have as members people from the
  83. different projects in the business of dealing with OpenStack
  84. in application containers. The participants should be
  85. interested in container building, willing to share their
  86. practices, and/or define common practices for use within
  87. all OpenStack projects. One example of the deliverables of
  88. the SIG would be a common series of "rules" for the bindep
  89. files relevant for container image building. These rules
  90. would then be applied consistenty across all the OpenStack
  91. projects, but also maintained over time by this group.
  92. Another example of common ground would be sharing how
  93. deployment projects are writing their container "check
  94. probes", and figure out what can be re-used. In other words,
  95. defining together what are application containers "readiness"
  96. and "aliveness" for each service project.
  97. status: active
  98. url: https://etherpad.openstack.org/p/containers-sig
  99. Extended Maintenance:
  100. chairs:
  101. - name: Tony Breeds
  102. irc: tonyb
  103. email: tony@bakeyournoodle.com
  104. scope: >
  105. Defining, enforcing and accompanying project teams in the application
  106. of a common stable branch policy. Keeping CI working on stable branches.
  107. Creating and improving related tooling and automation.
  108. status: active
  109. url: https://docs.openstack.org/project-team-guide/stable-branches.html
  110. FEMDC:
  111. chairs:
  112. - name: Adrien Lebre
  113. irc: ad_rien_
  114. email: lebre.adrien@free.fr
  115. - name: Paul-Andre Raymond
  116. irc: parus
  117. email: paul-andre.raymond@nexius.com
  118. scope: >
  119. The goal of the FEMDC SIG (formerly Fog/Edge/Massively Distributed Clouds
  120. Working Group) is to debate and investigate how OpenStack can address
  121. Fog/Edge Computing use-cases (i.e. the supervision and use of a large
  122. number of remote data centers through a collaborative distributed
  123. OpenStack system).
  124. status: active
  125. url: https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds
  126. First Contact:
  127. chairs:
  128. - name: Kendall Nelson
  129. irc: diablo_rojo
  130. email: knelson@openstack.org
  131. - name: Matt Oliver
  132. irc: mattoliverau
  133. email: matt@oliver.net.au
  134. scope: >
  135. To provide a place for new contributors to come for information and advice.
  136. This group will also analyze and document successful contribution models while
  137. seeking out and providing information to new members of the community.
  138. status: active
  139. url: https://wiki.openstack.org/wiki/First_Contact_SIG
  140. K8s:
  141. chairs:
  142. - name: Chris Hoge
  143. irc: hogepodge
  144. email: chris@openstack.org
  145. - name: David Lyle
  146. irc: david-lyle
  147. email: dklyle0@gmail.com
  148. - name: Robert Morse
  149. irc: rjmorse
  150. email: robert.morse@ticketmaster.com
  151. scope: >
  152. Community-local counterpart to the k8s-sig-openstack group, focused on
  153. cross community communication and collaboration. Where k8s-sig-openstack
  154. spends a good deal of time managing upstream provider code, sig-k8s
  155. would likewise be focused on code to support and enable K8s deployments
  156. within the OpenStack community. This SIG is directly intertwined with
  157. k8s-sig-openstack within the Kubernetes community, with the same sig
  158. leadership and meetings.
  159. status: active
  160. url: https://github.com/kubernetes/community/tree/master/sig-openstack
  161. Operation Docs:
  162. chairs:
  163. - name: Chris Morgan
  164. irc: mihalis68
  165. email: mihalis68@gmail.com
  166. - name: Sean McGinnis
  167. irc: smcginnis
  168. email: sean.mcginnis@gmail.com
  169. scope: >
  170. The Operation Docs SIG is for those interested in operator guide
  171. documentation to make running OpenStack clouds easier and more efficient.
  172. status: active
  173. url: https://wiki.openstack.org/wiki/Operation_Docs_SIG
  174. Public Cloud:
  175. chairs:
  176. - name: Tobias Rydberg
  177. irc: tobberydberg
  178. email: tobias.rydberg@citynetwork.eu
  179. - name: Howard Huang
  180. irc: zhipeng
  181. email: huangzhipeng@huawei.com
  182. scope: >
  183. The aim of this sig is to represent the interests of the OpenStack
  184. public cloud provider community, and to further adoption of OpenStack
  185. public cloud usage.
  186. status: active
  187. url: https://wiki.openstack.org/wiki/PublicCloudSIG
  188. Resource Management:
  189. chairs:
  190. - name: Howard Huang
  191. irc: zhipeng
  192. email: huangzhipeng@huawei.com
  193. - name: Chris Dent
  194. irc: cdent
  195. email: cdent+os@anticdent.org
  196. - name: Jay Pipes
  197. irc: jaypipes
  198. email: jaypipes@gmail.com
  199. scope: >
  200. The Resource Management SIG provides a gathering of similar interested
  201. parties and establish an official channel cross different communities,
  202. such as Kubernetes (Resource Management WG), Apache Mesos, Open Compute
  203. Project and so forth, to focus on alignment of resource management
  204. related functionalities.
  205. status: active
  206. url: https://wiki.openstack.org/wiki/Res_Mgmt_SIG
  207. Scientific:
  208. chairs:
  209. - name: Blair Bethwaite
  210. irc: b1airo
  211. email: blair.bethwaite@gmail.com
  212. - name: Stig Telfer
  213. irc: oneswig
  214. email: stig.openstack@telfer.org
  215. - name: Martial Michel
  216. irc: martial_
  217. email: martialmichel@datamachines.io
  218. scope: >
  219. The Scientific SIG (formerly Scientific Working Group) is dedicated to
  220. representing and advancing the use-cases and needs of research and
  221. high-performance computing atop OpenStack. It's also a great forum for
  222. cross-institutional collaboration. If you are (or would like to) run
  223. OpenStack to support researchers/scientists/academics and/or HPC/HTC,
  224. then please join!
  225. status: active
  226. url: https://wiki.openstack.org/wiki/Scientific_SIG
  227. Security:
  228. chairs:
  229. - name: Gage Hugo
  230. irc: gagehugo
  231. email: gagehugo@gmail.com
  232. scope: >
  233. The Security SIG (formerly Security Project) responsibilities include
  234. aiming to improve overall security of the various OpenStack projects,
  235. maintaining the list of security notices in OpenStack, and ensuring
  236. that security incidents are handled in a coordinated fashion. This
  237. involves maintaining the OSSN (OpenStack Security Notes) and OSSA
  238. (OpenStack Security Advisories), which are primarily handled under
  239. the OpenStack Vulnerability Managment Team (VMT), a more
  240. autonomous subgroup of the Security SIG.
  241. status: active
  242. url: https://wiki.openstack.org/wiki/Security-SIG
  243. Self-healing:
  244. chairs:
  245. - name: Adam Spiers
  246. irc: aspiers
  247. email: aspiers@suse.com
  248. - name: Eric Kao
  249. irc: ekcs
  250. email: ekcs.openstack@gmail.com
  251. scope: >
  252. Coordinate the use and development of several OpenStack projects which
  253. can be combined in various ways to manage OpenStack infrastructure in a
  254. policy-driven fashion, reacting to failures and other events by
  255. automatically healing and optimising services.
  256. status: active
  257. url: https://wiki.openstack.org/wiki/Self-healing_SIG
  258. Meta:
  259. chairs:
  260. - name: Matt Van Winkle
  261. irc: VW_
  262. email: mvanwinkle@salesforce.com
  263. - name: Rico Lin
  264. irc: ricolin
  265. email: rico.lin.guanyu@gmail.com
  266. scope: >
  267. A SIG for SIGs so to speak. A SIG to discuss OpenStack SIGs themselves,
  268. to encourage workgroups to become SIGs, accompany them along the way,
  269. give them tools and processes to be efficient. More generally, this SIG
  270. will discuss how to best close the loop between users and developers of
  271. OpenStack.
  272. status: active
  273. url: https://governance.openstack.org/sigs/