+1 on using Google docs for sharing design docs. IIRC even spark has used google docs for collaborating on designs. We already have the gmail account shared with private@.
Now, once the designs are finalized, do we move them to cwiki or just keep in gdoc itself? For eg, kafka has all the design docs in cwiki. I am okay with just sticking to gdocs Any thoughts? Others? On Sun, Feb 3, 2019 at 11:32 PM nishith agarwal <[email protected]> wrote: > Hi All, > > I wanted to start a discussion around contributing and collaborating on > design for large features. I've noticed that for some of the projects such > as apache beam, google docs is chosen as a means to collaborate on design > documents and large changes (Find it here > <https://beam.apache.org/contribute/>. Read under "Share your intent" > section). > I've researched and seen some other projects (such as Hadoop) use PDF's to > share design documents which may be is the final design but unsure how > collaboration happened on those. > Some projects like apache spark mention the use of mailing lists for design > discussions. (Find it here <https://spark.apache.org/contributing.html>. > Read under Contributing bug reports). > Traditionally, for Hudi, we've used google docs to collaborate and it has > been very useful. We also have some existing outstanding design documents > in google docs and would favor using the same going forward for apache > hudi. > I'd like to gather your thoughts on this. > > Thanks, > Nishith >
