[petsc-dev] Prediscusion of appropriate communication tool for discussion of PETSc 4 aka the Grand Refactorization

Satish Balay balay at mcs.anl.gov
Fri Jun 19 13:03:29 CDT 2020


And the monolithic/single issue aka#360 is very slow to access/browse..

Satish

On Fri, 19 Jun 2020, Jacob Faibussowitsch wrote:

> > I think a special GitLab issue (something akin #360 CI Tracker) would do the job quite nicely.
> I agree more with this. This also allows you to immediately see the list of linked MR’s and issues right in the conversation, as well as being able to link code snippets. One gripe however is that the issue becomes monolithic with multiple conversation threads (as you can see the CI error issue is a totally unstructured Smörgåsbord). To keep a more structured overview we should have multiple issues that are linked together. 
> 
> Best regards,
> 
> Jacob Faibussowitsch
> (Jacob Fai - booss - oh - vitch)
> Cell: (312) 694-3391
> 
> > On Jun 19, 2020, at 12:34 PM, Hapla Vaclav <vaclav.hapla at erdw.ethz.ch> wrote:
> > 
> > I like Slack but it does NOT have the full history in the free plan - it's limited to 10k messages.
> > 
> > I think a special GitLab issue (something akin #360 CI Tracker) would do the job quite nicely.
> > 
> > Vaclav
> > 
> >> On 19 Jun 2020, at 06:48, Jed Brown <jed at jedbrown.org> wrote:
> >> 
> >> I would prefer this mailing list or GitLab issues because they are
> >> 
> >> 1. genuinely open to external participants,
> >> 2. more async-friendly for those in different timezones and folks with young kids, and
> >> 3. searchable and externally linkable (e.g., from merge requests and issues)
> >> 
> >> If we need synchronous breakouts, we could do so, but there should be a summary back for those who couldn't participate synchronously.
> >> 
> >> Barry Smith <bsmith at petsc.dev> writes:
> >> 
> >>>  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. 
> >>> 
> >>>  So this discussion is not about PETSc 4.0, please don't discuss it here.
> >>> 
> >>>  What do people recommend to use for the discussion
> >>> 
> >>>     * dedicated mailing list
> >>>     * slack channel(s)
> >>>     * zulip channel(s)
> >>>     * something else?
> >>> 
> >>> 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.
> >>> 
> >>> I expect this discussion to take maybe a week and then the actual discussion to take on the order of two months.
> >>> 
> >>>  Thanks
> >>> 
> >>>    Barry
> >>> 
> >>> 
> > 
> 
> 


More information about the petsc-dev mailing list