Commit Graph

150 Commits

Author SHA1 Message Date
Jeremy Stanley 175c615f2d tact-sig: Simplify OpenSearch mention
The TaCT SIG section on the OpenSearch service no longer needs to
link to the old Logstash service, since that's not even reachable
lately after being turned off. Just remove the sentence about it.

Clarify the separate callout for the "global" tenant name, because
the supplied URL already embeds it so the login page doesn't
normally prompt for it, but may do so if the session expires.

Correct the capitalization of Opensearch to OpenSearch, since that
seems to be how their community styles the name.

Change-Id: I533080c8e1c07f6bb046aea4f521b39d4dfc560e
2022-06-21 13:51:45 +00:00
Jeremy Stanley 54f6cf0f56 Security SIG chair rotation
Jeremy is volunteering to lead the Security SIG for the foreseeable
future, given Gage's reduced availability, but is also open to
additional co-chairs if anyone is interested.

https://lists.openstack.org/pipermail/openstack-discuss/2022-April/028251.html

Change-Id: Iecd4fc0fc8288c9572f08f03663452a0525716d1
2022-06-02 13:11:01 +00:00
Daniel Pawlik 2702d830f7 Add Opensearch Dashboard information
This commit is providing information about new Elasticsearch
service base on Opensearch project.

This service is replacing old Elasticsearch service: logstash.openstack.org.

Change-Id: Id72e218709ab2a280e2c6b2aa916fc38230e8017
2022-03-30 16:54:53 +02:00
Zuul 8680c39d89 Merge "Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’" 2021-11-22 18:53:03 +00:00
Ghanshyam Mann d70b00e9dc Rename ‘Extended Maintenance’ SIG to the ‘Stable Maintenance’
As discussed in TC resolution[1], this is renaming
‘Extended Maintenance’ SIG to the ‘Stable Maintenance’ with no
change in this SIG role & responsibility.

[1] https://governance.openstack.org/tc/resolutions/20210923-stable-core-team.html

Change-Id: Ib3f8de72644f22151680d59c4dbfcb5cea11d690
2021-11-10 18:59:54 -06:00
Ghanshyam Mann 877943c7fc Mark 'Technical Writing' SIG complete as it is merged into TC
The Technical Writing SIG has served its purpose to provde
the guidance and tooling to have most of the documentation
ownership to projects. Now we do not have much work in this
SIG and it is also lacking maintainer to lead this SIG. The
current Chair Stephen Finucane would not be able to continue
leading this SIG.

In TC weekly meetings and PTG[1], we decided to merge this
SIG responsibility in TC (depends-on). SIG repos will be moved
to TC and a few repos which are related to upstream institute training
will be moved to First Contact SIG.

One repo 'training-labs' is left for now, which will be called
for the maintainer, and if there is no one, we can retire it.
We are not even sure who is using it. Upstream training and CoA
do not use this repo.

Depends-On: https://review.opendev.org/c/openstack/governance/+/815869

[1] https://etherpad.opendev.org/p/tc-yoga-ptg
    http://lists.openstack.org/pipermail/openstack-discuss/2021-October/025554.html

Change-Id: I5f2061e788346348b4f3ec375e9498a368c4ac47
2021-10-28 17:00:14 +00:00
ricolin 728db8f898 Add Seongsoo Cho for Multi-arch SIG chair
Change-Id: If79aa15a2a87727a6bddf3c01c2cc2c33d86361b
2021-10-19 23:08:03 +08:00
Mohamed Elsakhawy 2c3af8846a Modified Cloud Research SIG to active state
Change-Id: I1462cb07dd2f257cd2ae3fe9573d645f8fd69503
2021-09-17 13:50:31 -04:00
Zuul 23b7e3646f Merge "setup.cfg: Replace dashes with underscores" 2021-07-29 15:39:06 +00:00
Ghanshyam Mann 1ef4d29e97 Moving IRC network reference to OFTC
Change-Id: Ie6fb35683cc1b9d4cbec099b86453a9f2fae67fd
2021-07-08 18:38:54 -05:00
Kendall Nelson e59f5e0671 k8s SIG updates
The k8s SIG was in need of new leadership so this patch
updates the chairs for the SIG.

Relevant ML discussion: http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020663.html

Change-Id: I22937adb582e2b79490616ea5dba927dc81457d6
2021-06-17 15:51:08 +00:00
yangyawei 31d24ae492 setup.cfg: Replace dashes with underscores
Setuptools v54.1.0 introduces a warning that the use of dash-separated
options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without
this, we see 'UserWarning' messages like the following on new enough
versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: Ic904471801c3af6a83ec6229431ac372736d6a73
2021-05-14 14:17:03 +08:00
Ghanshyam Mann 6499556b09 Add email and irc nick for SIG chair/co-chair
Having email id and IRC nick in doc will help to
eaisly reachout the SIG chair/co-chair.

Change-Id: I6e13771e1e8e9393bd135db54d52911e98f09263
2021-05-11 16:49:50 -05:00
ricolin 8e4567fddd Retire Containers SIG
Change-Id: I6b48375946a1e8d4823e1744a955453c93125aa3
2021-03-26 19:36:40 +08:00
ricolin 43c6abee39 Update retire SIG process
Allow retire a non-finish SIG
* add archived-sigs.yaml to collect SIGs consider retired but didn't
  finish it's mission.
* Update documentation
* Add status `completed` and `archived` to SIG.
* Add `reason` field to SIG
* Show retired SIGs in index page

Change-Id: I6e5f35aa093340d6e553fe52c6ffe9061bc9191b
2021-03-26 19:33:18 +08:00
Zuul 6885dafd0d Merge "Make Public Cloud SIG Advisory" 2021-03-08 21:56:52 +00:00
Rico Lin 9286de6c85 Change primary eamil for Rico Lin
Rico recently change his primary email
from rico.lin.guanyu@gmail.com
to ricolin@ricolky.com

Change-Id: I1563d5ab8557aec94361dbb85f5d9dad4f6b0d3f
2021-03-05 17:37:23 +08:00
Kendall Nelson e62b043ac2 Make Public Cloud SIG Advisory
In chatting to Tobias, he said the SIG is not actively
working on anything at this point and can be moved to
advisory.

Change-Id: I6a3d35f0e080565a9726f2d57a1cc0b0fa12d004
2021-03-02 12:53:22 -08:00
Zuul 009cd90d44 Merge "Update automation and multi-arch SIGs" 2021-02-04 16:02:40 +00:00
Javier Pena 77fbaafb15 Add Dirk Mueller as Packaging SIG co-chair
As agreed during the weekly meeting [1].

[1] - http://eavesdrop.openstack.org/meetings/rpm_packaging/2021/rpm_packaging.2021-01-28-13.30.txt

Change-Id: Iac065e91cec744009453cdee06cb5abcd66a058a
2021-01-28 15:00:46 +01:00
ricolin 42401fb845 Update automation and multi-arch SIGs
Changes:
* Automation SIG to advisory
* Multi-arch SIG to active

Change-Id: Ie9cfc43a3d29858fbfa3fa6e7b3927821175c885
2021-01-26 17:17:50 +08:00
Zuul f89474f2cc Merge "Add doc/requirements" 2021-01-13 15:29:30 +00:00
Zuul 27d49a10d3 Merge "remove unicode from code" 2021-01-13 15:29:23 +00:00
Hervé Beraud 616b463b74 Add doc/requirements
This project isn't released but uniformization can't hurt.

The origin of these changes was that we need to specify doc requirements
in doc/requirements.txt to avoid problems with the pip resolver [1]
for the release team [2][3].

The problem here is that this repos haven't doc/requirements.txt
file and by default in this case zuul will use the test-requirements.txt
file to pull requirements [4].

This requirements file contains extra requirements like flake8 that
collided with those allowed in our job environment and so the new
pip resolver fails to install these requirements and the job exits in
error.

This project could meet similar conditions leading to the bug.

[1] http://lists.openstack.org/pipermail/release-job-failures/2021-January/001500.html
[2] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019611.html
[3] http://lists.openstack.org/pipermail/openstack-discuss/2021-January/019612.html
[4] https://opendev.org/zuul/zuul-jobs/src/branch/master/roles/ensure-sphinx/tasks/main.yaml#L36

Change-Id: I0101b340fef5ae465eb64e7d7b21973d36fd2a6a
2021-01-07 11:24:12 +01:00
liyou01 4b2b14c708 remove unicode from code
Change-Id: Idc8b6a0905e9161b5abc5491a0fe002f9e4ac53e
2021-01-07 16:35:50 +08:00
Tony Breeds 3210778096 Remove tonyb as co-chair of Extended Maintenance and Multi-Arch
Change-Id: I35397b29070ec2632faf1eda242deab234960012
2020-12-21 15:58:55 +11:00
Zuul 276b36f551 Merge "Update Tech Writers SiG chairs" 2020-11-11 16:13:18 +00:00
Zuul 8b4b0732e3 Merge "Mark API SIG status as advisory" 2020-11-11 16:09:17 +00:00
Amy Marrich (spotz) c1f5eaa2f9 Update Tech Writers SiG chairs
asettle is no longer part of the community so updating to reflect.

Change-Id: I3d0903b46c6c58cdff4f9d9d56c385d4adf17221
2020-10-27 17:11:24 -05:00
Dmitry Tantsur 1a1aa50696 Mark API SIG status as advisory
We no longer actively meet or propose guidelines, but some of us
are still here to help.

Change-Id: I3ccd9f5d731c05a2c417e1bdda42fd883e84c0a9
2020-09-28 17:26:52 +02:00
Jean-Philippe Evrard ac83a0b8cd Create the Packaging SIG
Nowadays, the rpm-packaging team can be moved to a lightweight
governance model that the SIG brings. We should move the
rpm-packaging to a SIG to make it easier for the contributors,
they wouldn't need to worry about elections in the future either,
just giving a regular heartbeat would be enough.

Change-Id: I4cafe9bb05c9e50d24286c4d6add0705338949d9
2020-09-18 12:17:19 +02:00
Thierry Carrez 709a567071 Reorganize SIG guidelines
Reorganize and simplify SIG guidelines, so that creating and operating
a SIG does not seem so daunting. In particular:

- Remove redundant information (like the definition of a SIG) and
  generally be more concise
- Regroup SIG lifecycle guidelines (creating, updating, retiring) in
  the same chapter rather than spread it out across all the document
- Be generally less prescriptive and more on the 'best practices' side
- Mention SIG statuses as part of the SIG lifecycle guidelines, rather
  that on its own separate document
- Remove the "completed" status which is redundant with the presence in
  the completed-sigs.yaml file

Change-Id: Id1a754512f08bed55926dd7b65916c1f42fb446f
2020-08-21 16:14:26 +02:00
Mohammed Naser 77c2344824 Update Ansible SIG chairs
I'm no longer able to be as involved as I can be in the Ansible SIG and
Sagi is doing a great job in keeping up with all the patches and work
that needs to be there.

They've accepted to chair thise SIG as well at this point.

Change-Id: I9b7a07be31c7d4d255db4546141bb3bb933fa9ad
2020-08-17 09:15:03 -04:00
Zuul be63df5ce9 Merge "The Meta SIG is no longer needed" 2020-08-14 11:04:20 +00:00
Zuul ebad41890b Merge "Remove deprecation warning from docs build" 2020-08-14 10:58:49 +00:00
Zuul b7bdaea33d Merge "Fix pygments style" 2020-08-14 10:58:48 +00:00
Zuul 4fce0b3868 Merge "Mark Hardware Vendor SIG as active" 2020-08-14 10:56:57 +00:00
Sean McGinnis 5407c907e7
Mark Hardware Vendor SIG as active
With the formation of this SIG, and the move of python-dracclient to be
under the SIG with Ie8bf14dd52b175790e6f33cee1f91ae354bbf36a, we can now
mark it active.

Change-Id: Ic2e737ef89ffe8df2e47289ec336dd3a1d8b94db
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-08-12 10:40:26 -05:00
Thierry Carrez 6ad5d54f49 Improve SIG intro
Remove mentions of governance bodies, as it's now a bit confusing
(SIGs being under the TC+UC body).

Be more explicit about the difference between a project team and
a SIG.

Change-Id: I7cf8f2b5ae0131d5226c3284665ce492a7e72336
2020-08-12 17:29:42 +02:00
Thierry Carrez e76ad922f8 The Meta SIG is no longer needed
The Meta SIG was created to administrate and promote the SIGs.
This was needed as the SIGs were co-owned by the OpenStack TC
and the OpenStack UC. Now that they operate as a single group,
we can just put the SIGs under the responsibility of the TC,
like other community work groups in OpenStack.

Change-Id: I1f6e3aa90d3f83c7d37df4e726f3e983ae948bff
2020-08-11 18:15:35 +02:00
Sean McGinnis 38a0b352b5
Propose new Hardware Vendor SIG
This proposes the creation of a new SIG for those working on integration
with different hardware platforms. This is to enable collaboration and
open development for things like drivers, tooling, libraries, and any
other needs related to specific hardware support. The hope is this will
allow vendors to work together and share code and expertise to improve
overall hardware support.

Change-Id: If7f47e1cb12b27f5118dcd2d16464fac10463534
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-08-07 14:51:13 -05:00
Sean McGinnis f723ec5cc3
Remove deprecation warning from docs build
The yaml.load() call has been deprecated if Loader= is not provided. It
is recommended to use safe_load() instead. This updates our Sphinx
extension to use safe_load() to avoid DeprecationWarnings from being
emitted while building docs.

Change-Id: I695cec8e272f143a1edd3de0ec2c8606ed403c47
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-08-06 12:14:13 -05:00
Sean McGinnis 20f38fd7db
Rename Operation Docs SIG to expand scope
We plan on expanding the scope of this SIG to also include tooling and
other code for use by operators.

http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016169.html

Change-Id: Icb85915b267a9ee017589127bb398318a1f8d2c6
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
2020-07-30 10:49:54 -05:00
Amy Marrich (spotz) e5ae2fce06 Clean up some wording to be clearer
Change-Id: Ia445286ef1dd720114307c557ec7d58146c5676e
2020-07-07 13:43:13 -05:00
Mohamed Elsakhawy f6e43d04ec Added the Cloud Research SIG in the forming state
Change-Id: I3c39a9f241cf9e0a0e9c3ba33bb81441228538c7
2020-07-06 18:04:15 -04:00
Andreas Jaeger b6859cc4c5 Switch to newer openstackdocstheme version
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems

Update Sphinx version as well.

Disable openstackdocs_auto_name to use 'project' variable as name.

Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.

openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.

See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html

Change-Id: Ib928a4799233cf1d85a2b045bd7323c0576c72cb
2020-06-03 20:48:16 +02:00
xuanyandong 1c00e76994 Fix pygments style
New theme of docs (Victoria+) respects pygments_style.
Since we starts using Victoria reqs while being on Ussuri,
this patch ensures proper rendering both in Ussuri and Victoria.

Change-Id: Ib1e3ad452b59445bfb6287cb87e1560ff90214f3
2020-05-20 10:12:06 +08:00
Zuul c9d6891cf9 Merge "Creating the i18n SIG" 2020-05-11 09:01:30 +00:00
Zuul ea5802bcde Merge "Add page for TaCT SIG" 2020-05-08 09:15:29 +00:00
Jeremy Stanley a3bb2f0853 Add page for TaCT SIG
The TaCT SIG is lightweight, and doesn't have any official
publications where it makes sense to point the SIG URL. Instead,
just add a page for it to this repository and link that.

Change-Id: I68f5606d3cd50ef74fdfaf0df8c146459b9acff9
2020-05-07 19:05:13 +00:00