Ok so if i summarize: 1. Small abstract (with "keywords") in proposals 2. Systematic ticket (or pr if time allows) to migrate it to the website when integration is done
Sounds good to me this way, thanks guys. Le 10 mars 2018 06:49, "Jean-Baptiste Onofré" <j...@nanthrax.net> a écrit : > Hi Romain, > > we already discussed about that. > > I stated the following while ago (quick short summary): > > "No problem to use Google Doc but a summary/discussion has to always be > sent on the mailing list" > > Regards > JB > > On 09/03/2018 23:14, Romain Manni-Bucau wrote: > >> Hi guys >> >> A lot of design docs are done through gdoc. I see how awesome it is to >> work but @asf it has a few issues - and more bothering, it quickly makes >> the tracking blurry. >> >> Out of my head here are a few issues I see/hit: >> >> - it doesnt happen on the list (even if a mail is sent the content is not >> available) - makes the search kind of harder >> - it is not under asf umbrella I think (is there an asf account or so >> under pmc scope which can track all actions?) >> - versionning is hard to follow or it is not versionned at all >> - it is "somewhere" but very hard to find with common tools (list >> archives, main git, ...) >> >> Therefore I propose to use gdoc for short period of time if you feel it >> better and just integrate designs as sources as well (in asciidoctor to >> have diagrams and all potential syntax or directly the site source but >> inline/not link?). This will fix all but the first issue and even allow to >> comment on PRs/reviews instead of gdoc. >> >> For the first point we can do as for incubator projects and include the >> original content in text form at the end of the mail. Will give enough >> context to find the thread back hopefully. >> >> Wdyt? Anyone else hitting these issues from time to time? >> >>
