Re: PEP 581 and Google Summer of Code
Ezio Melotti <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.devel |
|---|---|
| Message-ID | <CACBhJdGK-=DDYWwXE_qq+V6u1_B1oSjXqp5abqj8eHSuh5NA7g@mail.gmail.com> |
Hello, On Thu, May 16, 2019 at 6:34 PM Ralf Schlatterbeck <[email protected]> wrote: > > On Wed, May 15, 2019 at 11:47:30PM +0200, Ezio Melotti wrote: > > Hello, > > earlier today it was announced on python-dev[0] that PEP 581[1] has > > been accepted. > > PEP 581 proposes that CPython abandons Roundup in favor of using > > GitHub issues. > > Oh, sad. > > > The migration plan is described in PEP 588[2], which is still a draft > > and not yet accepted, so it will likely take some time before PEP 588 > > is approved and the actual migration takes place. > > In the same thread, Guido said[3] that people can submit PR to the > > peps repo[4] to correct factual errors in the PEP 581 or to write a > > PEP against the move. Berker Peksag and I are working on a PEP about > > improving bugs.python.org (b.p.o). > > That sounds promising. As already discussed I think that we can fix some > of the issues cited by you. > We pushed our PEP (PEP 595) to the peps repo yesterday. You can read it at https://www.python.org/dev/peps/pep-0595/ The source is available at https://github.com/python/peps/blob/master/pep-0595.rst The announcement on Python-dev is at https://mail.python.org/pipermail/python-dev/2019-May/157669.html Feel free to comment on the PEP (here, on python-dev, or on GitHub) and let me know if I missed anything. The PEP is not final yet, so we are planning to update it once we gather some more feedback. > Note that I'm maintaining a tracker sync project that keeps (part of) > two trackers in sync. I'm using this for customers in the automotive > industry who need to sync issues for a current project from the OEM > Bug-Tracker with their own bugtrackers. This has (among the backends for > proprietary automotive bugtrackers) interfaces to Jira and Roundup. This > could be extended to allow syncing new issues from github. That way > people could use the (generally accepted) github interface for posting > new issues and the workflow could then be handled in roundup keeping the > github issue up-to-date. > > https://github.com/schlatterbeck/trackersync > Thanks for letting me know. If we decide to move forward with the migration, this might be an interesting approach. Best Regards, Ezio Melotti > Ralf > -- > Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 > Open Source Consulting www: http://www.runtux.com > Reichergasse 131, A-3411 Weidling email: [email protected]