Amir Michail <[EMAIL PROTECTED]> writes:
| On Thu, 23 Oct 2003 12:28 am, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> | We are always interested. One thing that I would note is that we're a
>> | small collection of programmers and are very wary of enormous
>> | patches, prefering a 'little and often' approach. Moreover, because
>> | we are trying to clean the code base up (and have been doing so for
>> | several years) we have found it useful to have preliminary and
>> | informal discussions about the best way to implement some suggestion.
>> | Often the design becomes far more generic as a result. Getting your
>> | students to participate in such discussions would be an excellent
>> | thing for them to do anyway.
>>
>> Yes, and this would be required for them to get a patch into Lyx
>> anyway, and should absolutely be part of the assignment.
>> I do not know how formal you are going to do this assignment, but for
>> bugs not much are needed..., for new features it would be really nice
>> if a formal design were present (we have been bad at those).
>
| Hi,
>
| It's great to see interest in this.
>
| However note that we are talking about 200 students. Even if they work in
| pairs, having design discussions with 100 pairs may be too much.
>
| I think we might need a filtering scheme so that only meaningful questions
| make it to this list. As I mentioned, student ability varies widely and you
| probably don't want to hear about lots of trivial stuff.
You could setup a separate list for these assignments, then the
students could also help each other with trivial questions. If we
could get a couple of persons from this (lyx-devel) list to also
participate they could easily be told when their question is of a
non-trivial nature.
Also communicating with such a list is an essential part development
(especially open source).
--
Lgb
