menu
Tatoeba
language
En em enskrivañ Kevreañ
language Brezhoneg
menu
Tatoeba

chevron_right En em enskrivañ

chevron_right Kevreañ

Merdeiñ

chevron_right Diskouez ur frazenn dre zegouezh

chevron_right Diskouez dre yezh

chevron_right Diskouez dre listenn

chevron_right Diskouez dre valiz

chevron_right Diskouez an aodio

Kumuniezh

chevron_right Moger

chevron_right Listenn an holl Izili

chevron_right Yezhoù an Izili

chevron_right Komzerien a-vihanik

search
clear
swap_horiz
search
saeb saeb 3 Mezheven 2014, aozet 12 Mezheven 2014 3 Mezheven 2014 da 09:45:24 UTC, aozet 12 Mezheven 2014 da 09:05:49 UTC flag Report link Liamm-peurbadus

*GSOC week 2 progress report*

Done:
- Full test coverage

Not Done:
- Views

[angry post ahead]
So...let's start with the good news. The current codebase has 52 passing tests that cover every line of code, that means, yes, there's more test code than actual code, which is a good thing I guess. It also means every commit from now on will easily be tested, all the fixtures are very modular and reusable. The bad news is, I haven't been able to write a single new line of code that adds functionality. I pretty much lost 3 days to an urgent family issue that came up this week. And whatever time I put in during the other 3 days happened to be royally sucked by the god damn awful gerrit rebasing workflow. Reviews stalled since last week and I added as much or more patches this week, which left me with a 17 patch commit chain. So every time liori added a comment, I had to make sure any changes I introduced was safely propagated to all the other patches in the chain, without breaking anything. This process is very error prone and takes time. Imagine having to keep this up every time the reviewer felt like you should fix a few lines. I've had a few times where I even lost a commit or two during rebasing and no amount of git reflogging helped getting it back without me losing all my rebasing work that's in progress. In fact, I haven't had time to relax much on sunday and pulled an all nighter yesterday just to make sure I addressed the last round of comments and got them all merged, so I wouldn't end up with a chain this week. So yeah gerrit killed my family and gave me nazi cancer. I'm now homeless and in need of medical attention. But seriously, being behind schedule by a whole week feels pretty terrible so I'm just gonna go ahead and revise my schedule and set some ground rules to my workflow:
- the last buffer week for testing will be dropped and every single commit from now on will have its tests to go with it.
- the admin scripts week will be dropped in favor of doing code review/support for pallav's project and making sure it's reusable by my project.
- the search engine week will be restructured and support for sphinx and its api will be dropped. Django-haystack will be integrated during that week with Xapian as a backend. This means no time will be wasted on writing low level glue code to interact with sphinx's api and will introduce lots of other features out of the box like real time indexing (check xapian's homepage).
- the views will be split over two weeks starting this week

- no more small chains of commits, 1 feature 1 branch 1 patchset 0 dependencies on other patchsets. This means bigger commits but I don't think I care anymore, you can blame gerrit for this.
- all pending patches will be merged sunday night regardless of their review status. I'm sure we can introduce more patches if we wanna fix something later on, but we have to keep things going or we'll end up with terrible chains.
- no work on sunday. None. Ever. And no all nighters.

So I guess this week is gonna be views part 1, take 2. Wish me luck.

----------------------------
intro message:
http://tatoeba.org/eng/wall/sho...#message_19536
progress reports:
week 1: http://tatoeba.org/eng/wall/sho...#message_19654
week 2: http://tatoeba.org/eng/wall/sho...#message_19768
week 3: http://tatoeba.org/eng/wall/sho...#message_19821
-----------------------------
work log:
http://en.wiki.tatoeba.org/arti...work-log-lool0

patches pending review:
https://review.gerrithub.io/#/q...s:open+pytoeba

merged patches:
https://github.com/loolmeh/pytoeba

project template for testing:
https://github.com/loolmeh/pytoeba-dev

{{vm.hiddenReplies[19768] ? 'expand_more' : 'expand_less'}} kuzhat ar respontoù diskouez ar respontoù
AlanF_US AlanF_US 3 Mezheven 2014 3 Mezheven 2014 da 12:51:48 UTC flag Report link Liamm-peurbadus

> So I guess this week is gonna be views part 1, take 2. Wish me luck.

Good luck!

{{vm.hiddenReplies[19769] ? 'expand_more' : 'expand_less'}} kuzhat ar respontoù diskouez ar respontoù
saeb saeb 3 Mezheven 2014 3 Mezheven 2014 da 18:15:58 UTC flag Report link Liamm-peurbadus

thanks! ^^

Hybrid Hybrid 3 Mezheven 2014 3 Mezheven 2014 da 15:15:45 UTC flag Report link Liamm-peurbadus

Thanks for your work on Tatoeba. But who is this evil gerritt you speak of?

{{vm.hiddenReplies[19773] ? 'expand_more' : 'expand_less'}} kuzhat ar respontoù diskouez ar respontoù
saeb saeb 3 Mezheven 2014 3 Mezheven 2014 da 18:18:07 UTC flag Report link Liamm-peurbadus

Thanks. It's a web-based code review software that interfaces with git repositories. We use a gerrit server hosted by gerrithub.io (look at the patches pending link)