[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

You can have advanced more advanced controls like checkboxes or dropdownboxes in issue forms, see https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#dropdown. Some of this is used in

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

I like the idea of mimicking the trac setup, but moving away from trac also lets us reconsider parts of the trac interface. I personally do not find the "Priority" label very helpful, other than whether it's a blocker or not. What do others think? We could just ask people to label "Blocker" if

[sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

Calls for Europe / Africa / Americas: Monday noon, 12:15pm San Francisco Monday afternoon, 3:15pm New York Monday evening, 21:15 Paris https://meet.jit.si/VibrantTribesBearEver

[sage-devel] Re: Help wanted: Issue and PR templates, replacement for ticket dependencies

I think there are two steps to be taken. The first step is to define a suitable template to collect all the important information in the header of issues and PRs that we are used to from the Trac ticket box. In terms of dependencies between PRs, this will map what we are used to. The second