[Teammetrics-discuss] What is left.

[Sukhbir Singh]

Hi,

> This would be my highest preference.  Please try to adapt David
> Bremner's code to make sure we really track the commits in debian/.  If
> anything remains unclear please discuss this on the list (perhaps David
> in CC).

Yup! Actually I ran into some problems with the branches/ tags and
merges that were causing misleading metrics so I have decided to check
everything thoroughly.

> graphing of this.  For the moment I could think of preparing different
> graphs featuring
>
>    1. Number of commits (as ist was done by me before)
>    2. lines_inserted
>    3. lines_deleted
>    4. lines_inserted+lines_deleted
>    5. lines_inserted-lines_deleted (??)

As you say :)

> But as I said: Before we can play with the numbers we need the correct
> numbers.

Correct!

> Well, my prefered way is definitely the mbox approach because this is
> the only thing which makes really sense.  However, I do not expect it
> ready in five days.

Well, our converter is ready and so is liststat.py, so this should not
be much of a problem.

> 4. I have copied my code of the Upload statistics into the repository.
>    Please make yourself a bit comfortable with this - perhaps you see
>    some chance for enhancements, but I think it is OK as it is.

Two reasons why I am not going to even _try_ improving this:

    i. You have far far more experience and knowledge with PostgreSQL than I do,
    ii. goto i :D

> 5. I also would have loved to apply the measure Scott mentioned but
>    I'm afraid we are a bit late.

Please refresh my memory. Which of Scott's ideas are we talking about?

> I tend to do the following summary of the work:  At the end of the GSoC
> term we have not finished all the tasks we intended to do (finished in
> the sense of thoroughly tested, stable and documented).  However, we had

I had consider the following complete:

    svnstat.py
    liststat.py

gitstat.py will of course be done before GSoC ends. And we can finish
nntpstat.py also *just* in case.

> to fight some unexpected external influences (missing mboxes etc.) which
> caused hard to calculate delays - as every programming work.  In any
> case we did a great step foreward in this term.  From here it is easy to
> proceed and complete things into the shape I wanted it to have including
> new and interesting ideas - so it was a success in any case.

That's right. The initial step is the one that takes time :) And yayay
for success!

> You also had to spend some time in preparation of DebConf (uhmm, I would
> hate begging for a Visa that much) and your time at DebConf has probably
> also drained from pure coding time.  However, I really regard this as
> much more important to become a member of the project rather than
> writing some lines of code right in time for the and of GSoC term.

Total travel time + getting Visa + DebConf = 15 days. However, like
you said, it was time well spent and I am really happy I made it to
DebConf. Not only I got to meet you, but so many other wonderful
people which was an experience in itself _plus_ which will ensure that
I am going to be a part of Debian and contribute even after GSoC. So
while 15 days could have been used for coding even more, but DebConf
is DebConf and the 15 days will come again but not DebConf, so I am
happy and not complaining!

> Moreover the BOF at DebConf has brought in some additional ideas which
> are not coded as well - but it is easy to do it later.  (I just had some
> quick look into UDD and I thinks we can do something about bugs closed
> by a team member.)

This is perhaps the practical implementation of our project and once
we have the metrics, doing this is going to be easy.

> So in this sense I will fill in my mentor form in Melange that I will
> not score full points for project finished as planed (which is in most
> cases not realistic anyway) but that I regard the GSoC project as a
> success regarding analysing team performance in Debian.

Heh, me too. Remember how I asked you and Scott that this project will
be _under_ three months and now we were not able to actually complete
everything? :) So many factors influenced that but overall I am happy
(and you are!), so all is well.

I will finish Gitstat and we will see where to go from here.