On Mon, Feb 11, 2013 at 4:01 PM, Georg Baum
<georg.b...@post.rwth-aachen.de> wrote:
> Scott Kostyshak wrote:
>
>> On Wed, Feb 6, 2013 at 3:05 PM, Georg Baum
>> <georg.b...@post.rwth-aachen.de> wrote:
>>>
>>> This has been requested several times, but I did not find the time to
>>> write one up to now. I do not want to dump it into a hidden place where
>>> nobody will find it. Recently I had the idea of a development manual in
>>> lib/doc that could contain descriptions for testing, code design issues
>>> etc. This might even help to convert more users to developers (it would
>>> be more visible, and IMHO it looks friendly if the development docs are
>>> as accessible as the user docs). What do you think?
>>
>> I would be interested in reading something like this. When I first
>> started trying to contribute to LyX, I felt lost. I think most of this
>> was my inexperience in programming in general, but documentation like
>> this would have made it easier. That's one question if this
>> documentation is pursued -- whom to target? What level of programming
>> experience should be assumed -- An experienced C++ programmer who is
>> just unfamiliar with the LyX code?
>
> I had no target in mind at all. I would simply add some bits of missing
> information, which exist currently only in the heads of some developers, and
> which treat a specific topic like the tex2lyx tests. Then, we could see how
> it evolves: If somebody wants to add more general stuff it could also target
> less experienced programmers. If nobody does that, it would target more
> experienced programmers and only explain LyX specific topics.
>
>> I wonder if this would improve chances of being accepted for Google
>> Summer of Code.
>
> Based on the past experiences with SoC I would not apply anymore: A good
> application is a lot of work (more than was done in the past, although I
> realize that some delepoers spent a lof of time), and the chances are quite
> low to be accepted.

It's not possible to just use the same application that was used in
previous years?

>> If there's any task that you can delegate to me, I'd be happy to help.
>
> Not at the moment. Unless somebody complains I'll simply create this
> document when I'll find some time again, and if you'd like a specific topic
> to be covered you could add it (or read my stuff and complain about bad
> explanations :-)

Sounds good.

Scott

Reply via email to