On 10/11/2017 01:58 PM, Mike Beckerle wrote: > Lots of things are just too complicated to discuss and comment on in an email > thread. > > > E.g., code. E.g., design documents. > > > We have a big backlog of design notes/specs to create. My immediate task is > to start writing these and getting them into review. > > > How should I be creating these? Where should I be putting these? > > > I looked at Apache Spark - their wiki has been deprecated in favor of > markdown files that live in the docs tree of their git repo. However, those > pages are also published in presentation form on a web site, and that's not a > interactive environment for messing with them. > > > Suggestions? >
I think confluence is probably the best place for storage of design documents. However, discussions and decisions related to the designs should be done on the mailing list, and if reasonable/possible, the design itself should be copied to the mailing list to start discussions. I've opened an INFRA bug to create a confluence wiki for us: https://issues.apache.org/jira/browse/INFRA-15263 Related, we should all create both Confluence and JIRA accounts. The accounts are not linked to each other or to the apache id accounts, so you'll need to sign up separately for them. Sign up pages are here: Confluence: https://issues.apache.org/jira/secure/Signup!default.jspa JIRA: https://cwiki.apache.org/confluence/signup.action - Steve
