Re: PEP 581 and Google Summer of Code

Ralf Schlatterbeck <[email protected]>
Newsgroups gmane.comp.bug-tracking.roundup.devel
Message-ID <[email protected]>
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.

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

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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.