Sorry all, I have to disagree.
Confluence is fine for public-facing stuff. But for stuff that's still in work, it just doesn't support collaboration or document structure at the level that google docs do. The following (at least) is missing in confluence (and unthinkable in email): * Inline edit suggestions, * anchoring comments to particular pieces of text, * interactions on those suggestions and anchored comments * A resolution workflow for comments. * A tracked relationship between a version and a comment/suggestion. You can do this stuff to some extent in git, but workflows which require git won't be inclusive for people coming to our communities from conference organization roles or documentation roles, and these are the people with the most know-how to contribute to D&I work. We have some control over the degree to which google docs are open or visible (sharing permissions), and we should use that control. Google docs are transparent, and asynchronous. Some of our developers will need learn to use the technology, but the UX work done on google docs is for non-specialist level users, so we should be able to do it too. Very few people (if any at all) can follow email threads which branch and weave and jump unless they are reading and responding in real time. But asynchronous collaboration is one of our major goals. (But I'll accept it if y'all want to go another way. : o) Best, Myrle On Mon, Jun 3, 2019 at 12:03 PM Bertrand Delacretaz <bdelacre...@apache.org> wrote: > On Fri, May 31, 2019 at 2:45 AM Justin Mclean <jus...@classsoftware.com> > wrote: > > ...I also don’t see the need for the google drive and would prefer that > we use something more > > in the open and visible like the wiki (confluence).... > > Big +1 to that as I said in another thread. > > -Bertrand > > --------------------------------------------------------------------- > To unsubscribe, e-mail: diversity-unsubscr...@apache.org > For additional commands, e-mail: diversity-h...@apache.org > >
