<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div> I'm leaning to Vaclav's proposal, but with multiple issues, running in the PETSc repository as Jed suggested. My concern about the clutter of issues is outweighed by Jed's statement of having the history in one place (current PETSc repository) and Jacob's observation we can cleanly do links to MR, other issues, etc For example, someone does a prototype it can be right there and trivially accessible.<div class=""><br class=""></div><div class=""> The drawback to the mailing list is if we have just one then people have to very carefully label the topic of each one and if we have 10 then people have to set up ten mail boxes for them or have them all cluttered together and a pain to read. </div><div class=""><br class=""></div><div class=""> Unless I hear some other great ideas I will start setting up my issues with some notational consistency and we can start communicating and people can add their own issues as needed.</div><div class=""><br class=""></div><div class=""> Barry</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 20, 2020, at 12:42 AM, Fande Kong <<a href="mailto:fdkong.jd@gmail.com" class="">fdkong.jd@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class="">The mailing list sounds a perfect option. </div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Thanks,</div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">Fande,<br class=""><div class=""><br class=""></div><div class=""><br class=""></div></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jun 18, 2020 at 10:49 PM Jed Brown <<a href="mailto:jed@jedbrown.org" class="">jed@jedbrown.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I would prefer this mailing list or GitLab issues because they are<br class="">
<br class="">
1. genuinely open to external participants,<br class="">
2. more async-friendly for those in different timezones and folks with young kids, and<br class="">
3. searchable and externally linkable (e.g., from merge requests and issues)<br class="">
<br class="">
If we need synchronous breakouts, we could do so, but there should be a summary back for those who couldn't participate synchronously.<br class="">
<br class="">
Barry Smith <<a href="mailto:bsmith@petsc.dev" target="_blank" class="">bsmith@petsc.dev</a>> writes:<br class="">
<br class="">
> I'd like to start a discussion of PETSc 4.0 aka the Grand Refactorization but to have that discussion we need to discuss what tool to use for that discussion. <br class="">
><br class="">
> So this discussion is not about PETSc 4.0, please don't discuss it here.<br class="">
><br class="">
> What do people recommend to use for the discussion<br class="">
><br class="">
> * dedicated mailing list<br class="">
> * slack channel(s)<br class="">
> * zulip channel(s)<br class="">
> * something else?<br class="">
><br class="">
> I'd like a single tool that anyone can join at any time, see the full history, can attach files, search, not cost more money the we are already paying, etc.<br class="">
><br class="">
> I expect this discussion to take maybe a week and then the actual discussion to take on the order of two months.<br class="">
><br class="">
> Thanks<br class="">
><br class="">
> Barry<br class="">
><br class="">
> <br class="">
</blockquote></div>
</div></blockquote></div><br class=""></div></body></html>