Write the text of the pull request

jspaaks commented 2 years ago

Maybe things to include are:

who is making the issue / where we are coming from?
what to do next?
what if they don't feel like following up / accepting our suggestion?
where can they leave feedback?
include notification/mention of other team members. How can we get a clean list of notifications, only the ones that have something to do with these PRs/issues? (Maybe by including @nlescgt?)

Might be that certain repos prefer that issues are created in a certain way, using certain formats. (How) do we try to stick to those rules?

jspaaks commented 2 years ago

Initial stab here: https://github.com/cffbots/filtering/blob/main/issue-text.md

fdiblen commented 2 years ago

Also come up with a text for external repositories (outside NLeSC).

jspaaks commented 2 years ago

I'm wondering if it isn't better to make PRs directly, since we don't know when/if people will respond to our issue, and we're not confident we'll read it/see the notification.

jspaaks commented 2 years ago

We decided that making PRs rather than issues is more managable for us given the time we have

jspaaks commented 2 years ago

PR was merged, clsoing

cffbots / filtering

Write the text of the pull request #14