"Close" Issue trackers on repos "user-callbacks" and "docs"
Hello, this is a side topic related to the thread "Proposal: Pool of Label's for Issues" [1]. Beside the main repository "backintime" there are also "doc" and "user-callback" repos. And I realized that they have their own Issue tracker with a very small amount of open and closed tickets. My proposal is to centralize the ticket/issue tracking into "backintime" repo. This helps to manage things. It is easy to achieve: - The "Issue" feature in "doc" and "user-callback" don't need to be deactivated/closed (in the repo settings) yet while there are open tickets. - We can redirect the "New Issues" on that repos into the "backintime" repo via the ISSUE_TEMPLATE feature of GitHub. See an example here [2]. Thats it. When the Issues are closed we can deactivate the "Issue" complete in that repos and point the to backintime Issue tracker in the README.md. And far away in the future we maybe can join that two repos in the "backintime" repo. I see no advantage of separating them; technical and organizational. [1] -- <https://mail.python.org/archives/list/bit-dev@python.org/thread/YSTLO6UC3I6X...> [2] -- <https://github.com/buhtzz/spielwiese/issues/new/choose>
I agree, this plan makes sense! :) Michael On 07.09.2022 14:49, c.buhtz@posteo.jp wrote:
Hello,
this is a side topic related to the thread "Proposal: Pool of Label's for Issues" [1].
Beside the main repository "backintime" there are also "doc" and "user-callback" repos. And I realized that they have their own Issue tracker with a very small amount of open and closed tickets.
My proposal is to centralize the ticket/issue tracking into "backintime" repo. This helps to manage things.
It is easy to achieve:
- The "Issue" feature in "doc" and "user-callback" don't need to be deactivated/closed (in the repo settings) yet while there are open tickets.
- We can redirect the "New Issues" on that repos into the "backintime" repo via the ISSUE_TEMPLATE feature of GitHub. See an example here [2].
Thats it.
When the Issues are closed we can deactivate the "Issue" complete in that repos and point the to backintime Issue tracker in the README.md.
And far away in the future we maybe can join that two repos in the "backintime" repo. I see no advantage of separating them; technical and organizational.
[1] -- <https://mail.python.org/archives/list/bit-dev@python.org/thread/YSTLO6UC3I6X...> [2] -- <https://github.com/buhtzz/spielwiese/issues/new/choose> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de
Looks like a good plan to me. An organized repository makes everything more approachable and easier to maintain. :) Cheers, Hakan On Wed, September 7, 2022 16:50, Michael Büker wrote:
I agree, this plan makes sense! :)
Michael
On 07.09.2022 14:49, c.buhtz@posteo.jp wrote:
Hello,
this is a side topic related to the thread "Proposal: Pool of Label's for Issues" [1].
Beside the main repository "backintime" there are also "doc" and "user-callback" repos. And I realized that they have their own Issue tracker with a very small amount of open and closed tickets.
My proposal is to centralize the ticket/issue tracking into "backintime" repo. This helps to manage things.
It is easy to achieve:
- The "Issue" feature in "doc" and "user-callback" don't need to be deactivated/closed (in the repo settings) yet while there are open tickets.
- We can redirect the "New Issues" on that repos into the "backintime" repo via the ISSUE_TEMPLATE feature of GitHub. See an example here [2].
Thats it.
When the Issues are closed we can deactivate the "Issue" complete in that repos and point the to backintime Issue tracker in the README.md.
And far away in the future we maybe can join that two repos in the "backintime" repo. I see no advantage of separating them; technical and organizational.
[1] -- <https://mail.python.org/archives/list/bit-dev@python.org/thread/YSTLO6UC3I6X...> [2] -- <https://github.com/buhtzz/spielwiese/issues/new/choose> _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de
Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: hakan@bayindir.org
participants (3)
-
c.buhtz＠posteo.jp -
Hakan Bayindir -
Michael Büker