openGauss community uses Mailing List, IRC and other channels for communication. We sincerely invite you to join the openGauss Mailing List and IRC channel for discussion.
1. Mailing List
| List Name | Email Address | Description | Archives |
| Community | community@opengauss.org | Mailing list for public discussions in openGauss community. Any community issues can be discussed here. | Archive |
| Connectors | connectors@opengauss.org | Mailing list for SIG Connectors discussion group in openGauss community. | Archive |
| Docs | docs@opengauss.org | Mailing list for SIG Docs discussion group in openGauss community. | Archive |
| Infra | infra@opengauss.org | Mailing list for SIG Infra discussion group in openGauss community. | Archive |
| SecurityAnnounce | securityannounce@opengauss.org | Mailing list for SIG Security Announce discussion group in openGauss community. | Archive |
| SQLEngine | sqlengine@opengauss.org | Mailing list for SIG SQLEngine discussion group in openGauss community. | Archive |
| StorageEngine | storageengine@opengauss.org | Mailing list for SIG StorageEngine discussion group in openGauss community. | Archive |
| TC | tc@opengauss.org | Mailing list for SIG TC discussion group in openGauss community. | Archive |
| Tools | tools@opengauss.org | Mailing list for SIG Tools discussion group in openGauss community. | Archive |
| OM | om@opengauss.org | Mailing list for SIG OM discussion group in openGauss community. | Archive |
| IoT | iot@opengauss.org | Mailing list for SIG IoT discussion group in openGauss community. | Archive |
| In-place Update | inplaceupdate@opengauss.org | Mailing list for SIG in-place update discussion group in openGauss community. | Archive |
| AI | ai@opengauss.org | Mailing list for SIG AI discussion group in openGauss community. | Archive |
| GIS | gis@opengauss.org | Mailing list for SIG GIS discussion group in openGauss community. | Archive |
| CloudNative | cloudnative@opengauss.org | Mailing list for SIG CloudNative discussion group in openGauss community. | Archive |
| SecurityTechnology | securitytechnology@opengauss.org | Mailing list for SIG SecurityTechnology discussion group in openGauss community. | Archive |
| List Name | Description | Archives |
| Community | Mailing list for public discussions | Archive |
| Connectors | Mailing list for SIG Connectors discussion group | Archive |
| Docs | Mailing list for SIG Docs discussion group | Archive |
| Infra | Mailing list for SIG Infra discussion group | Archive |
| SecurityAnnounce | Mailing list for SIG Security Announce discussion group | Archive |
| SQLEngine | Mailing list for SIG SQLEngine discussion group | Archive |
| StorageEngine | Mailing list for SIG StorageEngine discussion group | Archive |
| TC | Mailing list for SIG TC discussion group | Archive |
| Tools | Mailing list for SIG Tools discussion group | Archive |
| OM | Mailing list for SIG OM discussion group | Archive |
| IoT | Mailing list for SIG IoT discussion group | Archive |
| In-place Update | Mailing list for SIG in-place update discussion group | Archive |
| AI | Mailing list for SIG AI discussion group | Archive |
| GIS | Mailing list for SIG GIS discussion group | Archive |
| CloudNative | Mailing list for SIG CloudNative discussion group | Archive |
| SecurityTechnology | Mailing list for SIG SecurityTechnology discussion group | Archive |
1.1 How Do I Subscribe to the Mailing List?
If you have never subscribed to the mailing list, do as follows:
Click the name of the mailing list that you want to subscribe to.
Wait until the browser goes to the subscription page of the mailing list, which provides instructions on how to subscribe.
Read the subscription instructions and provide an email address that you want to use to subscribe to the mailing list.
Enter your email address and click Subscribe. You will receive an email asking you to confirm the subscription.
Reply the email to confirm your subscription.
At last, you will receive a welcome email from the mailing list.
1.2 How Do I Send an Email to the Mailing List?
To send an email to a specified mailing list, send your email to the address listed on the mailing list. Subscribers in this mailing list will receive your email.
Subscribers in this mailing list will receive your email.
1.3 How Can I View the Previous Mailing List?
To view previous emails, visit the archive addresses as shown in the table above.
2. IRC
Internet Relay Chat (IRC) is widely used in open source projects because of its powerful real-time communication capability.
We sincerely invite you to join the openGauss IRC channel for discussion.
openGauss provides free and open communication through freenode.net.
The IRC software can be used in all operating systems. Wikipedia provides a comparison of diverse IRC clients. You may select one suitable client for your operating system.
IRC does not require complex configurations. If you do not want to download or install the software, you can use its web client (see at freenode.net).
Select a nickname to join the openGauss IRC channel.
2.1 openGauss IRC Channel
| IRC Channel | Description |
| #opengauss | Discussion channel for community activities. |
| #opengauss-tc | Community Technical Committee discussion channel. |
| #opengauss-infra | Community infrastructure discussion channel. |
| #opengauss-meeting | Community meeting channel. |
| IRC Channel | Description |
| #opengauss | Discussion channel for community activities. |
| #opengauss-tc | Community Technical Committee discussion channel. |
| #opengauss-infra | Community infrastructure discussion channel. |
| #opengauss-meeting | Community meeting channel. |
2.2 IRC Meeting
IRC meeting is held in plain text. The IRC meeting channel of openGauss community is #opengauss-meeting. You can find all of channels and meeting records from IRC Channel Logs.
openGauss community organizations can choose different channels to carry out online meeting. For details, please see the introduction of each community organization meeting.
| Organization Meeting | Scope of Organization Responsibility |
| TC | TC is in charge of technical guidance, decision-making, and supervision. |
| SIG SQLEngine | Develop and maintain the SQL engines of the openGauss community. |
| SIG StorageEngine | Develop and maintain the storage engine of the openGauss community. |
| SIG Connectors | Develop and maintain the connectors of the openGauss community. |
| SIG Tools | Develop and maintain the tools of the openGauss community. |
| SIG Docs | Develop and maintain the documents of the openGauss community. |
| SIG Infra | Develop and maintain the infrastructure of the openGauss community. |
| SIG Security | Develop and maintain the security of the openGauss community. |
| SIG IOT | Develop and maintain the IoT of the openGauss community. |
| SIG In-place Update | Develop and maintain the in-place update of the openGauss community. |
| SIG AI | Develop and maintain the AI of the openGauss community. |
| SIG GIS | Develop and maintain the Geographic Information System of the openGauss community. |
| SIG CloudNative | Develop and maintain the Cloud Native of the openGauss community. |
| SIG SecurityTechnology | Develop and maintain the database security technology of the openGauss community. |
| Organization Meeting | Scope of Organization Responsibility |
| TC | TC is in charge of technical guidance, decision-making, and supervision. |
| SIG SQLEngine | Develop and maintain the SQL engines of the openGauss community. |
| SIG StorageEngine | Develop and maintain the storage engine of the openGauss community. |
| SIG Connectors | Develop and maintain the connectors of the openGauss community. |
| SIG Tools | Develop and maintain the tools of the openGauss community. |
| SIG Docs | Develop and maintain the documents of the openGauss community. |
| SIG Infra | Develop and maintain the infrastructure of the openGauss community. |
| SIG Security | Develop and maintain the security of the openGauss community. |
| SIG IOT | Develop and maintain the IoT of the openGauss community. |
| SIG In-place Update | Develop and maintain the in-place update of the openGauss community. |
| SIG AI | Develop and maintain the AI of the openGauss community. |
| SIG GIS | Develop and maintain the Geographic Information System of the openGauss community. |
| SIG CloudNative | Develop and maintain the Cloud Native of the openGauss community. |
| SIG SecurityTechnology | Develop and maintain the database security technology of the openGauss community. |
All IRC meeting commands use the # character as the prefix. The useful commands include:
| Commands | Functions | Example |
|---|---|---|
| #startmeeting | Start a meeting. The calling IRC nick becomes the chair. | #startmeeting infra |
| #topic | Set the current topic of discussion, and all of the topics will be highlighted at the end of the meeting. | #topic next release time |
| #endmeeting | End current meeting, the meeting bot will save records and give links of the meeting records. | #endmeeting |
| #action | Provide IRC nicks of people involved and the action items. The action items will be sorted by IRC nick at the end of the meeting. | #action MrGreen organize release plan |
| #info | Highlight a record in a meeting. | #info We need much effort before the next release |
| #link | Add a link record. The URL will be properly detected within the line in most cases, and the URL can’t contain spaces. | #link [MeetBot](http://wiki.debian.org/MeetBot/) |
| #agreed | It means that the participants reached a certain conclusion, and the command is followed by the conclusion. The meeting bot will record the conclusion in the meeting minutes. | #agreed next release time is sunday |
| Commands | Functions | |
|---|---|---|
| #startmeeting | Start a meeting. The calling IRC nick becomes the chair. | |
| #topic | Set the current topic of discussion, and all of the topics will be highlighted at the end of the meeting. | |
| #endmeeting | End current meeting, the meeting bot will save records and give links of the meeting records. | |
| #action | Provide IRC nicks of people involved and the action items. The action items will be sorted by IRC nick at the end of the meeting. | |
| #info | Highlight a record in a meeting. | #info We need much effort before the next release |
| #link | Add a link record. The URL will be properly detected within the line in most cases, and the URL can’t contain spaces. | |
| #agreed | It means that the participants reached a certain conclusion, and the command is followed by the conclusion. The meeting bot will record the conclusion in the meeting minutes. |
2.3 Other Things You Might Want to Know
If you want to create a new IRC channel, visit the IRC channel #opengauss-infra or send an email to infra@opengauss.org for help.
Note: Many IRC channels have logs, and the logs are publicly accessible. Therefore, do not enter your private and sensitive data in these channels.