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 8.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244
  1. API:
  2. chairs:
  3. - name: Chris Dent
  4. irc: cdent
  5. email: cdent+os@anticdent.org
  6. - name: Ed Leafe
  7. irc: edleafe
  8. email: ed@leafe.com
  9. - name: Michael McCune
  10. irc: elmiko
  11. email: msm@redhat.com
  12. scope: >
  13. Formerly known as the API-WG, the API SIG scope is to improve the developer
  14. experience of API users by converging the OpenStack API to a consistent and
  15. pragmatic RESTful design. The working group creates guidelines that all
  16. OpenStack projects should follow for new development, and promotes
  17. convergence of new APIs and future versions of existing APIs.
  18. status: active
  19. url: https://wiki.openstack.org/wiki/API_SIG
  20. Auto-scaling:
  21. chairs:
  22. - name: Rico Lin
  23. irc: ricolin
  24. email: rico.lin.guanyu@gmail.com
  25. - name: Duc Truong
  26. irc: dtruong
  27. email: duc.openstack@gmail.com
  28. - name: Zane Bitter
  29. irc: zaneb
  30. email: zbitter@redhat.com
  31. scope: >
  32. Auto-scaling SIG scope is to improve experience on develop, operate, and use
  33. autoscaling and its related features (like metering, cluster schedule,
  34. life cycle management) and to coordinate across projects and communities
  35. (like k8s cluster autoscaling on OpenStack). Also provide a central place
  36. to put tests, documentations, and even common libraries for Auto-scaling
  37. features.
  38. status: active
  39. url: https://wiki.openstack.org/wiki/Auto-scaling_SIG
  40. Bare Metal:
  41. chairs:
  42. - name: Chris Hoge
  43. irc: hogepodge
  44. email: chris@openstack.org
  45. scope: >
  46. The scope of the Bare Metal Sig is to promote the development and use
  47. of Ironic and other OpenStack bare metal software. This will include
  48. marketing efforts like case studies of Ironic clusters in industry
  49. and academia, supporting integration of Ironic with projects like
  50. Airship and the Kubernetes Cluster API, coordinating presentations
  51. for industry events, developing documentation and tutorials,
  52. gathering feedback from the community on usage and feature gaps, and
  53. other broader community-facing efforts to encourage the adoption of
  54. Ironic as a bare-metal management tool.
  55. status: active
  56. url: https://etherpad.openstack.org/p/bare-metal-sig
  57. Extended Maintenance:
  58. chairs:
  59. - name: Tony Breeds
  60. irc: tonyb
  61. email: tony@bakeyournoodle.com
  62. scope: >
  63. Defining, enforcing and accompanying project teams in the application
  64. of a common stable branch policy. Keeping CI working on stable branches.
  65. Creating and improving related tooling and automation.
  66. status: active
  67. url: https://docs.openstack.org/project-team-guide/stable-branches.html
  68. FEMDC:
  69. chairs:
  70. - name: Adrien Lebre
  71. irc: ad_rien_
  72. email: lebre.adrien@free.fr
  73. - name: Paul-Andre Raymond
  74. irc: parus
  75. email: paul-andre.raymond@nexius.com
  76. scope: >
  77. The goal of the FEMDC SIG (formerly Fog/Edge/Massively Distributed Clouds
  78. Working Group) is to debate and investigate how OpenStack can address
  79. Fog/Edge Computing use-cases (i.e. the supervision and use of a large
  80. number of remote data centers through a collaborative distributed
  81. OpenStack system).
  82. status: active
  83. url: https://wiki.openstack.org/wiki/Fog_Edge_Massively_Distributed_Clouds
  84. First Contact:
  85. chairs:
  86. - name: Kendall Nelson
  87. irc: diablo_rojo
  88. email: knelson@openstack.org
  89. scope: >
  90. To provide a place for new contributors to come for information and advice.
  91. This group will also analyze and document successful contribution models while
  92. seeking out and providing information to new members of the community.
  93. status: active
  94. url: https://wiki.openstack.org/wiki/First_Contact_SIG
  95. K8s:
  96. chairs:
  97. - name: Chris Hoge
  98. irc: hogepodge
  99. email: chris@openstack.org
  100. - name: David Lyle
  101. irc: david-lyle
  102. email: dklyle0@gmail.com
  103. - name: Robert Morse
  104. irc: rjmorse
  105. email: robert.morse@ticketmaster.com
  106. scope: >
  107. Community-local counterpart to the k8s-sig-openstack group, focused on
  108. cross community communication and collaboration. Where k8s-sig-openstack
  109. spends a good deal of time managing upstream provider code, sig-k8s
  110. would likewise be focused on code to support and enable K8s deployments
  111. within the OpenStack community. This SIG is directly intertwined with
  112. k8s-sig-openstack within the Kubernetes community, with the same sig
  113. leadership and meetings.
  114. status: active
  115. url: https://github.com/kubernetes/community/tree/master/sig-openstack
  116. Operation Docs:
  117. chairs:
  118. - name: Chris Morgan
  119. irc: mihalis68
  120. email: mihalis68@gmail.com
  121. - name: Sean McGinnis
  122. irc: smcginnis
  123. email: sean.mcginnis@gmail.com
  124. scope: >
  125. The Operation Docs SIG is for those interested in operator guide
  126. documentation to make running OpenStack clouds easier and more efficient.
  127. status: active
  128. url: https://wiki.openstack.org/wiki/Operation_Docs_SIG
  129. Resource Management:
  130. chairs:
  131. - name: Howard Huang
  132. irc: zhipeng
  133. email: huangzhipeng@huawei.com
  134. - name: Chris Dent
  135. irc: cdent
  136. email: cdent+os@anticdent.org
  137. - name: Jay Pipes
  138. irc: jaypipes
  139. email: jaypipes@gmail.com
  140. scope: >
  141. The Resource Management SIG provides a gathering of similar interested
  142. parties and establish an official channel cross different communities,
  143. such as Kubernetes (Resource Management WG), Apache Mesos, Open Compute
  144. Project and so forth, to focus on alignment of resource management
  145. related functionalities.
  146. status: active
  147. url: https://wiki.openstack.org/wiki/Res_Mgmt_SIG
  148. Scientific:
  149. chairs:
  150. - name: Blair Bethwaite
  151. irc: b1airo
  152. email: blair.bethwaite@gmail.com
  153. - name: Stig Telfer
  154. irc: oneswig
  155. email: stig.openstack@telfer.org
  156. - name: Martial Michel
  157. irc: martial_
  158. email: martialmichel@datamachines.io
  159. scope: >
  160. The Scientific SIG (formerly Scientific Working Group) is dedicated to
  161. representing and advancing the use-cases and needs of research and
  162. high-performance computing atop OpenStack. It's also a great forum for
  163. cross-institutional collaboration. If you are (or would like to) run
  164. OpenStack to support researchers/scientists/academics and/or HPC/HTC,
  165. then please join!
  166. status: active
  167. url: https://wiki.openstack.org/wiki/Scientific_SIG
  168. Security:
  169. chairs:
  170. - name: Luke Hinds
  171. irc: lhinds
  172. email: lhinds@redhat.com
  173. - name: Gage Hugo
  174. irc: gagehugo
  175. email: gagehugo@gmail.com
  176. scope: >
  177. The Security SIG (formerly Security Project) is responsible for the
  178. maintaining the list of security notices in OpenStack. These include
  179. OSSN (OpenStack Security Notes), OSSA (OpenStack Security Advisory),
  180. and the VMT (Vulnerability Management Team). Other responsibilities
  181. of the Security SIG include advocating and working alongside
  182. security-focused projects, such as Bandit, Syntribos, and Tatu.
  183. status: active
  184. url: https://wiki.openstack.org/wiki/Security-SIG
  185. Self-healing:
  186. chairs:
  187. - name: Adam Spiers
  188. irc: aspiers
  189. email: aspiers@suse.com
  190. - name: Eric Kao
  191. irc: ekcs
  192. email: ekcs.openstack@gmail.com
  193. scope: >
  194. Coordinate the use and development of several OpenStack projects which
  195. can be combined in various ways to manage OpenStack infrastructure in a
  196. policy-driven fashion, reacting to failures and other events by
  197. automatically healing and optimising services.
  198. status: active
  199. url: https://wiki.openstack.org/wiki/Self-healing_SIG
  200. Upgrade:
  201. chairs:
  202. - name: James Page
  203. irc: jamespage
  204. email: james.page@canonical.com
  205. - name: Lujin Luo
  206. irc: lujinluo
  207. email: luo.lujin@jp.fujitsu.com
  208. scope: >
  209. The objective of the Upgrade SIG is to improve the overall upgrade
  210. process for OpenStack Clouds, covering both offline 'fast-forward'
  211. upgrades and online 'rolling' upgrades, by providing a forum for
  212. cross-project collaboration between operators and developers to
  213. document and codify best practice for upgrading OpenStack.
  214. status: active
  215. url: https://wiki.openstack.org/wiki/Upgrade_SIG
  216. Meta:
  217. chairs:
  218. - name: Matt Van Winkle
  219. irc: VW_
  220. email: mvanwinkle@salesforce.com
  221. - name: Rico Lin
  222. irc: ricolin
  223. email: rico.lin.guanyu@gmail.com
  224. scope: >
  225. A SIG for SIGs so to speak. A SIG to discuss OpenStack SIGs themselves,
  226. to encourage workgroups to become SIGs, accompany them along the way,
  227. give them tools and processes to be efficient. More generally, this SIG
  228. will discuss how to best close the loop between users and developers of
  229. OpenStack.
  230. status: active
  231. url: https://governance.openstack.org/sigs/