I don't recall a discussion about this change, but I think it goes against previous efforts to make the website the one canonical location for our documentation. I don't even think infra is backing up wiki repos, so there wouldn't even be a record of the wiki contents in ASF spaces (vs. the main repo, which is backed up to GitBox and the issue tracker, which CCs the notifications list).
In short, I think this should be reverted and we should not use the GitHub wiki. If we need to store documents in a version controlled way, we can store them on the website, or in our project's SVN dev space. The wiki is just another place people would have to follow if they want to participate, and I don't think that serves us. Therefore, I think we shouldn't use it. On Fri, Feb 24, 2023, 15:59 <dlmar...@apache.org> wrote: > This is an automated email from the ASF dual-hosted git repository. > > dlmarion pushed a commit to branch main > in repository https://gitbox.apache.org/repos/asf/accumulo.git > > > The following commit(s) were added to refs/heads/main by this push: > new ae8a817e7b Enable Github wiki in asf.yaml > ae8a817e7b is described below > > commit ae8a817e7b2af8c64096ed1a4274eaef44c0e677 > Author: Dave Marion <dlmar...@apache.org> > AuthorDate: Fri Feb 24 15:59:10 2023 -0500 > > Enable Github wiki in asf.yaml > --- > .asf.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/.asf.yaml b/.asf.yaml > index bc2c943e82..08aa357082 100644 > --- a/.asf.yaml > +++ b/.asf.yaml > @@ -27,7 +27,7 @@ github: > - big-data > - hacktoberfest > features: > - wiki: false > + wiki: true > issues: true > projects: true > > >
