Maintenance considerations

[bkmgit]

MPI has significant functionality and is quite mature. Maintenance should also be considered in new proposals.

[devreal]

I like it, just have a suggestion to make the text a little less awkward :)

[devreal]

Thinking about it: do you refer to maintenance in the standard document or the maintenance for implementations? Do you have a specific example for required maintenance in the document?

[cniethammer]

It's a very good point to mentioning potential use cases/users!
However, I would have expected, that this is already part of the Problem and Impact on Users sections already?

As @devreal I do not know what "Impact on Maintainability" refers to - user applications/MPI implementations/the MPI standard document(s)

[bkmgit]

Implementation maintenance, expect document maintenance changes will likely be affected much less often by issues raised that use this template. Effect on user applications would probably be addressed in the "Problem and Impact on Users".

[jeffhammond]

We have impact on users and implementations already. How is this not included in those already?

GitHub issue templates aren't normative. It's still up to the forum to perform due diligence on every change. If the forum isn't considering maintenance costs already, that's our failure and a GitHub issue template won't fix it.

[bkmgit]

The templates are suggestions for relevant information to be included. They provide hints for appropriate information to include. At present, few issues include information that allows for a cost benefit analysis of adding and maintaining a feature against its potential use. Another option is to add these as hints under the "Impact on Users" and "Impact on Implementations".