*+1 for raising this topic.* I’d suggest we consider a *GitHub-centric collaboration model*, which has become common practice across many ASF projects. This approach keeps design proposals, discussions, and governance all versioned and reviewable in one place, lowering the contribution barrier and improving transparency.
Typical mapping could look like this: - *Auron Improvement Proposals (AIP)* → docs/aip/ directory, reviewed via PR *(similar to Apache Pulsar [1])* - *Design / Governance discussions* → GitHub *Discussions* or Issues *(similar to Apache DataFusion [2])* - *Implementation tracking* → Project boards or milestones *(similar to Apache Iceberg [3])* - *Process / Community documents* → auron-site repository - *Meeting notes / Internal records* → Markdown under auron-site or in Auron Issues This model keeps the entire project history in GitHub, simplifies maintenance, and makes community participation straightforward. It further reduces administrative overhead, as anyone with a GitHub account can follow discussions, provide feedback, or submit improvements without requiring separate Confluence access. [1] https://github.com/apache/pulsar/tree/master/pip [2] https://github.com/apache/datafusion/discussions [3] https://github.com/apache/iceberg/projects On Mon, Nov 3, 2025 at 10:22 PM Mang Zhang <[email protected]> wrote: > +1 > > > > > > -- > > Best regards, > Mang Zhang > > > > At 2025-11-04 11:39:57, "王磊" <[email protected]> wrote: > >Hello everyone > > > > > > > >I'm starting this thread to discuss the possibility of creating a new > >Confluence space for Auron to share and store important information, code > >snippets, and project procedures. > > > > > > > >What do others think about this? Thank you for the valuable feedback. > > > > > >Kind regards, > > > >Lei Wang >
