Search results

Create the page "Special interest group" on this wiki! See also the search results found.

• API Special Interest Group (category Working Groups)
  Application_Ecosystem_Working_Group (AE WG). The API Working Group (API WG) is complementary to the End User Working Group. The API WG is focused on creating
  13 KB (1,426 words) - 15:40, 14 June 2018
• OpenStack SIGs (section OpenStack SIGs (Special Interest Groups))
  OpenStack SIGs (Special Interest Groups) are teams within the community where we collaborate to bring unified discussions for all community members who
  3 KB (441 words) - 20:57, 7 August 2020
• StarlingX/First Contact SIG
  This is the Special Interest Group for StarlingX community members who are interested in helping new community members become active contributors and users
  451 bytes (55 words) - 19:39, 30 May 2019
• Scientific SIG (redirect from Scientific working group)
  Flanders <Flanders@OpenStack.org> Welcome to the OpenStack Scientific Special Interest Group (SIG) landing page. Please cite this SIG using the #scientific
  6 KB (674 words) - 21:41, 15 March 2022
• StarlingX (section Special Interest Groups (SIGs))
  StarlingX Release Planning Development Process Tags and Prefixes Storyboard Group All active stories All active stories for StarlingX 4.0 All open bugs
  9 KB (55 words) - 15:02, 3 January 2024
• API SIG (category Special Interest Groups)
  Application_Ecosystem_Working_Group (AE WG). The API-SIG (API- Special Interest Group) is complementary to the End User Working Group. The API-SIG is focused
  13 KB (1,433 words) - 17:48, 3 January 2019
• StarlingX/Draft new wiki home page (section Special Interest Groups (SIGs))
  update) StarlingX Defect Handling Process Tags and Prefixes Storyboard Group Newly created stories Stories with no sub-project tags All active stories
  7 KB (85 words) - 17:56, 26 June 2019
• StarlingX/Archived wiki home page (section Special Interest Groups (SIGs))
  for a description of how we use them. The StarlingX Storyboard project group is here. IMPORTANT: If you create a new story, please mark it with the tag
  15 KB (172 words) - 17:50, 26 June 2019
• Forum/Vancouver2018 (section Etherpads from Teams, Working Groups, and SIGs)
  openstack.org/p/YVR18-cinder-ha-forum [1100-1140] Room 217 - API Special Interest Group Session - https://etherpad.openstack.org/p/YVR18-API-SIG-forum
  13 KB (1,691 words) - 15:14, 30 May 2018
• Operations/Meetups (section Working Groups - "Small, working sessions")
  legitimately get work done - not just talk. You'll have yourself, and a small group of people who are experienced with OpenStack and actually very interested
  24 KB (3,338 words) - 23:24, 13 June 2022
• Fuel/How to contribute (section Special flow for bugs with swarm-blocker tag)
  and other teams. Feel free to pick any of those. It is assigned to group, so group can get an email notification about a bug. Unless it is reassigned to
  42 KB (5,589 words) - 09:22, 6 May 2016
• Governance/Foundation/22July2014BoardMinutes
  Toman and unanimously approved by the Board: WHEREAS, it is in the best interest of the Foundation to approve and adopt the forecast budget change for the
  35 KB (847 words) - 20:53, 23 September 2014
• Oslo
  generalist code reviewers and specialist API maintainers. They share a common interest in tackling copy-and-paste technical debt across the OpenStack project
  39 KB (3,441 words) - 15:49, 16 June 2021
• Neutron/TempestAPITests
  pay special attention to the Tempest Field Guide to API tests The code of the Tempest tests is stored in the OpenStack Git repo. Of special interest for
  6 KB (672 words) - 19:37, 9 December 2013
• Activity Board
  Releases and Companies Browser provides an analysis of the community with special emphasis in the companies participating in each release and their developers
  5 KB (689 words) - 21:23, 26 March 2015
• Meetings/ML2
  topics of interest to ML2 - Open Agenda based upon the interest Open Discussion Announcements M2 is next week Driver API for SecurityGroup https://bugs
  126 KB (17,217 words) - 05:14, 13 December 2017
• CinderUssuriPTGSummary (section Cross Project Discussion with Edge Working Group)
  rosmaita put together a community poll to determine days/times There is interest in having a midcycle. Although everyone recognizes that face-to-face is
  36 KB (5,851 words) - 19:04, 4 December 2019
• CinderVictoriaPTGSummary
  iSCSI when they're on the same node. The problem is that this is a very special case. The team discussed a few ways to do this: introduce this as an optimization
  32 KB (5,340 words) - 02:56, 10 June 2020
• KeyManager
  would make data protection more readily available, enable harnessing of any special hardware encryption support on the servers, make available a larger set
  19 KB (2,932 words) - 17:04, 12 August 2016
• Documentation/WhatsUpDoc Archive
  and the docs core team is an 'included group' in both repos. This is intended to stop the core teams for these groups drifting out of date too quickly. Note
  260 KB (41,968 words) - 16:49, 22 March 2017