<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi,<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Aug 17, 2016, at 2:05 PM, Tanya Lattner via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org" class="">llvm-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">On Aug 4, 2016, at 6:58 AM, Renato Golin <<a href="mailto:renato.golin@linaro.org" class="">renato.golin@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi Tanya,<br class=""><br class="">Do you have an idea on how we'll put up this survey online?<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I can put it in Google Forms/Docs (or you can if you prefer). Survey monkey is also an option but its about the same I think but more costly.. so lets go with free and easy. </div><br class=""><blockquote type="cite" class=""><div class=""><br class="">The other thread on the foundation list had some good proposals, but I<br class="">don't know how we'll make sure we follow all of them when we actually<br class="">publish it.<br class=""><br class="">I'd like to have some process going before early Sep, so we can just<br class="">"put it up" as soon as all the proposals are finished.<br class=""><br class="">Some questions...<br class=""><br class="">Q1. How do we choose the questions / format?<br class=""><br class="">Starting from the other thread would be good, but we may need a review<br class="">process to make sure everyone think it's a fair questionnaire (or the<br class="">exercise won't have the desired effect).<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I do think its been reviewed quite a bit, but if you want to give anyone else a chance to review then ok.</div><br class=""><blockquote type="cite" class=""><div class=""><br class="">Q2. Where do we host it?<br class=""><br class="">This is mostly independent and a bit irrelevant, but it could make a<br class="">difference to answer the question above.<br class=""></div></blockquote><div class=""><br class=""></div><div class="">Google Forms/Docs should work.</div><br class=""><blockquote type="cite" class=""><div class=""><br class="">Q3. Do we fix a date, or make it depend on the proposals?<br class=""><br class="">If the former, we may run with incomplete proposals. If the latter, we<br class="">may run it too late. A mix of both will be the answer, but I<br class="">personally think we need to set a limit date (early Sep).<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I’m not sure I follow. Are you talking about the one repo versus many discussion? Otherwise, why wouldn’t there be one GIT proposal document that describes GITHUB versus SVN (pros and cons) and then people can give feedback?</div></div></div></blockquote><div><br class=""></div><div>I think the survey should be regarding question based-off a single document putting side-by-side the options that we came-up with on the mailing-list.</div><div>Indeed I don’t plan to write a document describing a “mono-repo” proposal to counter the submodules one, but I plan instead to unify it with the existing one (submodules…) along with the possible variants/options in a single document.</div><div>I plan to include examples of workflow today and after for each scenario, side-by-side. I hope to have it up for public review by the end of the month.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><a href="http://llvm.org/docs/Proposals/GitHubSubMod.html" class="">http://llvm.org/docs/Proposals/GitHubSubMod.html</a></div><div class=""><br class=""></div><div class="">I also don’t think this is a process that needs to be rushed. It will take awhile to publicize the survey and give people a chance to comment. Its more reasonable to give until Dec (1 month after the dev meeting BoF) give time for feedback. But thats just my opinion. </div></div></div></blockquote><div><br class=""></div><div>I’d regret not having the results of the survey for the BoF as these data seem critical to drive the discussion.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><br class="">Q4. How do we present the results?<br class=""><br class="">I volunteer to do the analysis and conclusions, but I think that the<br class="">bulk of the results should be made public at some point. If we decide<br class="">to have private text boxes, we must keep them out, but everything else<br class="">should be public.<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I would just make a note that the feedback may be made public and whoever is filling it out should be responsible for making sure its not releasing sensitive information. Everything should be anonymized of course.</div><br class=""><blockquote type="cite" class=""><div class=""><br class="">I also think we should have a session at the US LLVM to present the<br class="">results and maybe have a final decision there.<br class=""></div></blockquote><div class=""><br class=""></div><div class="">I would use the BoF as a way to discuss in person but I wouldn’t put pressure to make a decision during it. It will probably become more clear when you start getting feedback.</div></div></div></blockquote></div><br class=""></div><div class="">Right, I don’t think the BoF will much productive without the feedback on the proposal.</div><div class=""><br class=""></div><div class="">— </div><div class="">Mehdi</div><div class=""><br class=""></div></body></html>