Re: Suggestion for SoC

David Anderson wrote:
> Hi,
>
> * Stefan Küng <tortoisesvn@gmail.com> [2006-04-21 20:18:29]:
>> Since there's some discussion about what issues could be used for SoC,
>> I'd like to add one more:
>>
>> Issue #901 : http://subversion.tigris.org/issues/show_bug.cgi?id=901
>>
>> I think this issue is big enough to keep a student busy during the
>> summer, but still not so big or complicated that it couldn't be
>> finished. And it can be done in stages, which is nice because even if it
>> doesn't get finished the parts already done can be used.
>
> Thanks for suggesting this. I must say I have some reservations,
> simply because it seems like an extremely open-ended task: "Provide
> finer grained notification". Could the issue be specified more
> precisely, so that the task falls clearly in the SoC scope?

I kind of like that it's open-ended. That way even if the student
doesn't get to do it all, we still could use whatever (s)he finished.

To make it more precise, I suggest:

* define the required API (client callback, enum for progress type like
'files', 'bytes', 'chunks', ...)
* locate the modules where this has to be implemented (ra modules,
libsvn_wc, ...)
* start with one command like checkout or import (not diffs, only
complete files). Then expand (if there's still time in the SoC
timeframe) to other commands like commit, update, diff.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org