Infra team:
On behave of TC, I’m proposing following changes to openEuler infrastructure for your consideration.
1. Regarding to Wiki
Background: We think Wiki is a good way to consolidate and present knowledge systematically. openEuler already has its own document site (https://openeuler.org/zh/docs), we think it could be further improved.
a) The namespace of pages should be flattened. For example, https://openeuler.org/zh/docs/Administration/%E7%AE%80%E4%BB%8B.html , the name of page implies to be an introduction
to system administration. But in fact, it’s an introduction to system only. We propose to add directories for each domain.
b) Currently documents are divided into different SIG, we think it’s important to extend it for multiple SIG. For example, if we introduce oVirt into openEuler, the document
of oVirt should be part of the https://openeuler.org/zh/docs/Virtualization, not it’s own.
c) It’s very different to use cross reference now. We think it is an important feature to have. For example, https://openeuler.org/zh/docs/Administration/%E8%AE%BE%E7%BD%AE%E8%AF%AD%E8%...
should refer to systemd. It’ difficult or even impossible to do so now.
2. Regarding to issues handling
Background: There’re difficulties during day-to-day work on openEuler community. Especially, when issues are reported. We think it needs to be further improved.
a) When an issue is reported, we think it’s very helpful to have it assigned to a default triage. The developers don’t know each other, and even they know each other, they can
not match the ID with real people. The best way now is to assigned to a default triage based on the components or sub-module.
b) There’re too many messages on the web interface. Developers are easily overwhelmed. We suggest to have a default mail notification for all un-handled or un-closed issue
to assigned developers. If there’re existing mechanism we can leverage, please advise too.
Looking forward to your feedback and suggestions.
Shinwell Technical Committee openEuler Community