> On Aug 27, 2019, at 10:44 AM, Mariatta <maria...@python.org> wrote: > > (cross posting to python-committers, python-dev, core-workflow) > > PEP 581: Using GitHub Issues has been accepted by the steering council, but > PEP 588: GitHub Issues Migration plan is still in progress. > > I'd like to hear from core developers as well as heavy b.p.o users, the > following: > > • what features do they find lacking from GitHub issues, or > • what are the things you can do in b.p.o but not in GitHub, or > • Other workflow that will be blocked if we were to switch to GitHub > today > By understanding your needs, we can be better prepared for the migration, and > we can start looking for solutions.
One other bit of workflow that would be blocked if there was a switch to GitHub today: * On the tracker, we have long running conversations, sometimes spanning years. We need to be able to continue those conversations even though the original participants may not have Github accounts (also, if they do have a Github account, we'll need to be able to link to the corresponding BPO account). * I believe some of the accounts are anonymous or have pseudonyms. Am not sure how those can be migrated, we know very little about the participant except for their recurring posts. Raymond _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/MT2PJFS2CVDSWQKCCRUR3BCNXR4OSEKU/
