Weekly check in [week 3 - 10/06 to 16/06]

naccht
Published: 06/17/2019

1. What did you do this week?

  • Apparently the Roundup devs decided to fix all of the warnings, so work started to implement the [-] button on the nosy list.

2. What is coming up next?

  • Finishing the [-] button; when it's finished I will discuss with my mentor how to continue with the work.

3. Did you get stuck anywhere?

  • This week I did not encounter big problems.
View Blog Post

Weekly check in [week 2 - 03/06 to 09/06]

naccht
Published: 06/10/2019

1. What did you do this week?

  • This week I continued familiarizing myself with Roundup, the previously mention https issue was resolved. I now started working on the original Roundup code, and not the CPython implementation. The code was taken from the official Sourceforge repository, and work started to fix all the errors from the tests (only 1271, not much).

2. What is coming up next?

  • Fixing the aforementioned warnings from Roundup, and implementing the [-] button for the nosy list, mentioned in my earlier blog post.

3. Did you get stuck anywhere?

  • As the work was very similar from last week's I did not encounter many problems.
View Blog Post

Weekly check in [week 1 - 27/05 to 02/06]

naccht
Published: 06/04/2019

1. What did you do this week?

  • Most of the work this week was to familiarize myself with Roundup and the specific bugs.python.org instance. The working environment was setup, and I started working on small bug fixes, specifically updating the links from docs.python.org/devguide to devguide.python.org in the link generator. Work started also on fixing all the links to be https instead of http. During this fixes the main work was modifying the regex matching the links.

2. What is coming up next?

  • In the next week I’ll continue working on the https bug fix. I will start to implement a [-] button for the nosy list in the issue page of bugs.python.org to remove the currently logged in user from the nosy list.

3. Did you get stuck anywhere?

  • Unfortunately my knowledge of regex is minimal, and I had to learn it to actually do the bug fixes, obviously my mentor helped me in this process.
  • The instructions to setup the working environment were old and pointed to old directories, it did not really impact the work, as the files I was working on weren’t changed in the current directories, but if you want to work on Roundup now the instructions are up to date.
View Blog Post

Introductory Blog Post

naccht
Published: 06/04/2019

Hello everyone, and welcome to my introductory blog post.

 

My name is Enrico Carbognani and I am an undergraduate from the University of Luxembourg.

In this four months I will work on Python’s bug reporting platform. The main goal of this project is to Integrate the REST API that is being added to upstream Roundup to bugs.python.org (b.p.o), more specifically, as mentioned in my proposal, the following features will be added:

  • Tools to easily generate random issues/messages, useful for testing
  • Command-line interface to access the tracker
  • Advanced statistics, graphs, leaderboards
  • Real time filtering/ordering of issues
  • Customizable dashboard
  • Related issues suggestions
  • Simpler integrations with other services (GitHub, IRC, etc.

 

This was the initial plan, however recently PEP581 was accepted, and most probably the goals of the project will have to change, most probably the tools developed generically for Roundup and not specifically for the b.p.o integration. My mentor is going against this change for reasons you can find at the newly raised PEP595, but only the future will tell how this change will shape the project. In the meantime, at least for the few incoming weeks, work will continue as planned.

 

Thank you for reading and for your time, see you in the next blog post.

View Blog Post