I don't think GitHub wiki will help us. I would really like all Ozone content to be published on the new website, which would make our confluence page obsolete and we can then deprecate/remove it. Having a separate wiki anywhere creates split brain and is harder to manage. There's no clear answer for what content would go on one platform vs. the other.
Ethan On Mon, Mar 17, 2025 at 1:48 PM Wei-Chiu Chuang <weic...@apache.org> wrote: > FYI > > Also do we want to enable GitHub wiki? > We used to have > https://cwiki.apache.org/confluence/display/OZONE/Ozone+Wiki+Home > but for some reason its SEO is so bad, I couldn't google it. It's probably > time to migrate stuff from the wiki to Ozone's user doc site or GitHub > wiki. > > ---------- Forwarded message --------- > From: Daniel Gruno <humbed...@apache.org> > Date: Mon, Mar 17, 2025 at 10:37 AM > Subject: [ASF] A note to projects with GitHub Discussions in use > To: <annou...@infra.apache.org> > > > Projects that are using GitHub Discussions and have suddenly found that > feature to be missing, please see > > https://github.com/apache/infrastructure-asfyaml?tab=readme-ov-file#repo_features > > GitHub Discussions are now managed entirely through .asf.yaml, and will > default to being disabled unless enabled in your .asf.yaml file, OR if > you do not have a valid 'discussions' entry in your notifications > section in the configuration. > > > The TL;DR for enabling Discussions in .asf.yaml is to weave these > settings into your .asf.yaml file in your default branch: > > > notifications: > discussions: iss...@foo.apache.org (use your own mailing list here) > ... > github: > features: > discussions: true >
