naccht's Blog

Weekly check in [week 10 - 29/07 04/08]

naccht
Published: 08/07/2019

1. What did you do this week?

  • The GitHub integration is almost finished but not quite, some work still needs to be done. In the meantime this week I also started to look around on how to integrate some sort of markdown support for Roundup messages. I was able to find a somewhat old issue opened in Roundup where the thought of implementing it was brought up, but no real development was made. Right now I'm still studying a bit how to develop how to implement this feature, and I could follow up on some of the ideas brought up in the issue.

2. What is coming up next?

  • Next week will be probably be spent on developing markdown support for Roundup. I will also do some testing on the GitHub login function to make sure that everything works.

3. Did you get stuck anywhere?

  • This week fortunately I did not find amy real issues that halted development in a significant way.
View Blog Post

Weekly check in [week 9 - 22/07 - 28/07]

naccht
Published: 08/05/2019

1. What did you do this week?

  • This week I worked on finalizing the GitHub login integration. It has yet to be finished, but the work is almost done. I worked mainly on getting information from the link headers in roundup, something that sounds easy but it's not. I also started working on managing login issues (for example duplicate accounts that might get created) and a way to link the GitHub account to a pre-existing b.p.o. account. Thankfully for this task there was some already existing code created by Berker Peksag from the old non-functional integration.

2. What is coming up next?

  • Next week the last issues in the GitHub login page will be fixed, and work will start on a new feature: adding support for markdown in messages, creating also a preview window, and adding the ability of modifying the message after being posted.

3. Did you get stuck anywhere?

  • I had similar problems as last week, I had issues getting the headers in the GET request in Roundup Actions. As the documentation doesn't have much on this regard and as I couldn't find similar pieces of code I had to study Roundup's source code to understand how to achieve it.
View Blog Post

Weekly check in [week 8 - 15/07 - 21/07]

naccht
Published: 07/24/2019

1. What did you do this week?

  • This week I worked mainly on adding the login using GitHub option to the Python Bug Tracker. This was already attempted in the past with partial success. On the previous attempt they tried to authenticate using OpenID, but for this time I completely changed approach and used Oauth2 (which is the method suggested by GitHub). For the moment the implementation is only partly working, the GitHub authentication works, but there are some Roundup related problems. Also the random issue generator was moved from the web interface to a server side script, as it's safe to assume that it will never be used during normal operations. BTW my yet-to-be-created Blog Post will cover how to do Oauth2 authentication with GitHub, so if you need to do something similar it might help you, as I didn't find any good tutorials on this.

2. What is coming up next?

  • In the next week the GitHub login functionality will be finished, and any issues that at the moment are still to be solved (for example someone that already has an account also wants to login with GitHub) will be solved.

3. Did you get stuck anywhere?

  • I did have issues with Roundup, especially in the way that it handles links, because while the documentation is great, on certain parts it's a bit lacking. I was able to understand properly Roundup's link handling by digging deep enough in the code, but it certainly wasn't fun.
View Blog Post

Weekly check in [week 7 - 08/07 - 14/07]

naccht
Published: 07/19/2019

1. What did you do this week?

  • This week I did principally three things: I studied the REST API, I created a random issue generator and started creating a command-line interface. I studied a bit more the REST API, specifically I studied the implementation that is used in Roundup, since I will have to work with it later. I also created a new section in the website where a developer can generate any number of random new issues, this will be very useful to help with testing later (and probably will be useful to other developers in the future). Last I started creating a command-line interface to access the tracker; I'm still in the early stages of development, and I'm still planning exactly how to implement this feature, and I also need to take in consideration that some sort of command-line access is already present in Roundup.

2. What is coming up next?

  • In the next week I will finish the command-line interface, and I will start work on two new features for the site: a statistic page (the exact details that will be shown in this page still need to be defined) and a new ways of ordering the issues in the main page, as the current implementation is a bit lacking. Eventually a customizable dashboard will be added, but this idea needs to be discussed a bit more.

3. Did you get stuck anywhere?

  • I didn't necessarily got stuck, but I had some difficulties understanding the way Roundup works on a code level, with the added difficulty understanding the changes made in the bpo instance. I had to this as the work now on is not concentrated anymore only on the front-end but also on the back-end.
View Blog Post

Weekly check in [week 6 - 01/07 - 07/07]

naccht
Published: 07/09/2019

1. What did you do this week?

  • This week I transfered the code for the button from JavaScript to HTML. Also I started familiarizing myself and working with the REST API.

2. What is coming up next?

  • For the next week I will continue familiarizing myself with the REST API. Also I will update my installation of Roundup to the latest version, and fix issues that might (but almost surely) will arise.

3. Did you get stuck anywhere?

  • I didn't get stuck as most of the work wasn't technical. Also some good news, at the end of next week there might be new developments with the PEP581, so it might be more clear on how the project will evolve.
View Blog Post