Some Pull Requests (PRs) seem to be open still, after a year.
https://github.com/ham2k/app-polo/pulls?q=is%3Apr+is%3Aopen+sort%3Acreated-asc
In order to keep this under control, it may be a good idea to regularly triage the open PRs. These should be regularly reviewed, as part of the backlog, and either implemented, or have some other triage outcome.
Thanks,
Chris
2E0FRU
Chris,
Is this a proposal for you to do the triage?
Alan
Nope, but that is a good way to stop people suggesting things. I’m suggesting that in Agile terms, it needs to be on the backlog, or managed somehow.
If Sebastian or yourself don’t think it’s a valid point, I’m more than happy to close it. I just thought that if revisions to the code are being suggested, then they should probably be reviewed.
I know this is in-hand, so I’ll step back. I need to remember that just because I have ideas, it doesn’t mean anyone will be interested in them.
Chris
Thanks Chris,
I dont know of anyone submitting any PRs who are not also communicating directly with Sebastian. So I assume they already know about any delay or have ongoing communication about it. But we’ll see who else picks up on this.
Alan
We want to have a way for people not directly involved in the development to know what issues have already been identified, what things are being worked on, and what ideas have already been discussed.
But most of these “people not directly involved” don’t understand tickets and backlogs and boards and githubs and such. So trying to use common product management flows will not solve this problem.
Also, while I take PoLo very seriously, I do not want it to “feel like work”, so I rather avoid having things that look like backlogs and boards and tickets, or any kind of process beyond a way to coordinate with people what issues have been found, what are we working on next and what ideas are already being considered.
I don’t think the current state, using the forums, is perfect. But it’s not too far from the “good enough” mark.