On Mon, Jan 14, 2013 at 2:21 PM, janI <j...@apache.org> wrote:
> On 14 January 2013 20:01, Rob Weir <robw...@apache.org> wrote:
>
>> http://openoffice.apache.org/orientation/intro-development.html
>>
>> The idea here is to have a dev-focused introduction page that works
>> along side the similar pages we have for Marketing and QA.  This is
>> the first draft.   I already see a few typos, so don't worry about
>> those.   But I am looking for more content.
>>
> I like the idea that we have a document like this, a few remarks to content:
> - The building guide you refer to is outdated (see first line), and many of
> the other building guides are not complete.
>

Is there a building guide that is more up to date than the one I linked to?

> - since not all programmers are fluent in all languages, it would be nice
> to have a list of which languages are used where...otherwise it becomes
> complicated to pick an "easy task".
>

Maybe when someone marks an issue as an "easy task" they add a comment
in Bugzilla giving some hints like where to start looking, etc.

> - It would also be nice to give a short introduction to debugging, which is
> far from easy (again split on languages/tools).
>

I'd love to have that information, if anyone has a link?

But I think that is the catch-22:   Our dev doc is poor, but it takes
volunteer dev time to improve the doc.  But we need more volunteers.
And that requires good doc.

So maybe this becomes a bootstrapping process, where we gather
feedback from the initial dev volunteers and use that to improve the
doc.

In any case, I don't have the deep knowledge here.  I'm mainly helping
gather it into one place in a consumable form.  So improving this will
require help from a veteran developer, either up front, or later after
answering repeated questions on the mailing list.

Regards,

-Rob

> rgds
> Jan I
>
>
>>
>> What else should we put here?  Any other links?  Any other startup tasks?
>>
>> -Rob
>>

Reply via email to