gerlowskija commented on PR #2767: URL: https://github.com/apache/solr/pull/2767#issuecomment-2436146523
> I'm almost surprised this went here instead of Confluence as it's easier to edit/collaborate on a wiki instead of in code and do PR process. I think that was probably true once, but it's at least arguably different now that Confluence account creation is semi-locked down as a defense against spam. Committers all tend to have Confluence access already, but for non-committers I think there's a good case that GH collaboration has less friction. I've helped a handful of folks get Confluence access this year (for updating SIPs, organizing "Community Meetups", etc.), and it's been a minor pain 🙁 But Eric's already highlighted my main reason for going the "dev-docs" route - for better or worse, Confluence doesn't seem like it gets much attention any more. Personally I'm OK with this - our user-facing documentation lives "in-repo" just fine, benefits from PR review, version control, etc. Why would developer-facing docs be any different? (This is probably worth a discussion on dev@, if anyone feels like injecting life back into use of cwiki as a documentation store.) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
