On Mon, May 12, 2008 at 1:19 PM, Jakub Narebski <jnareb@xxxxxxxxx> wrote: > One note: why not provide HTML version in addition to PDF? HTML version is now available too: http://alturin.googlepages.com/Use_cases.html > This is "Finding the owner of the code" (i.e. something like > non-existent 'git blame --summary') with the goal of "Find who > needs to be contact about changing (or adding) license / relicensing". Ah, it is a simple aggregation of 'git blame' then, you are right, that is not the same as what I had in mind for the mentioned use case. > This is similar, but not exactly the same as "Find maintainer of given > subsystem", or "Who is responsible for this part of code". Agreed, since those should look back in history too. > * Maintainer: how close should I examine provided patch? I'm not sure I understand what you mean with this, perhaps related to "Name: Finding parts of the content in which a lot of bugs are introduced and fixed" (e.g., patches to bug prone areas should be examined more closely). > * Contributor: who is maintainer of the code / whom should I contact > and send copy of a patch? I think this -is- the "Finding a Contributor that is active in a specific bit of content" use case this time. > * Bug-fixer: who is responsible about this part of code? Who might have > introduced the bug? How would you define 'responsible'? "Having a lot of signed-off-by lines in that part of the content" would seem like a candidate, but the "activity" use case seems applicable again here. > * Contributor: what happened with my code? Do you mean a "track my code" like feature? Showing the movement of a particular piece of code through the code? (Displaying information like "moved from foo.c to bar.c in commit 0123456789abcd"?) > * Searching where to contribute: what are oldest part of code dealing > with error messages (find ancient code)? In other words, find the lines with the oldest modification time stamp from 'git blame'? -- Cheers, Sverre Rabbelier -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
