You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Hung Mark <ma...@gmail.com> on 2014/08/23 10:22:27 UTC
Introduction & question about contributing source code?
Hello there,
I started to subscribe these list since May. I began by asking question on
API list, volunteer translation on l10n and doc, than finally, I start to
investigate annoying issues I encountered. I come from Taiwan and am
interested about issues specific to traditional Chinese.
I tried to submit issues I've found (
https://issues.apache.org/ooo/show_bug.cgi?id=125400 ),
also attached the patch I've made, not knowing if I've did it right. I
think you are busy releasing new version these days. Now that I know how to
build and debug now, I may be able to help more.
However it seems that wiki page for contributor is outdated:
https://wiki.openoffice.org/wiki/Contributing_Patches
( it suggest to use hg to make patch, and domain developer list marked
outdated, URL to IRT & IIT links are invalid now.
What is the correct procedure to propose a patch for defect ( or
enhancement) ?
Please advice.
Sincerely.
--
Mark Hung
Re: Introduction & question about contributing source code?
Posted by Andrea Pescetti <pe...@apache.org>.
On 30/08/2014 Hung Mark wrote:
> I followed the link here:
> https://wiki.openoffice.org/wiki/Development
> The development page were found by google 'OpenOffice contributing'
Thanks, I updated some very obsolete content there and in linked pages
too. It should now be less confusing for a new volunteer.
As you go and read stuff, should you find anything clearly obsolete feel
free to edit it yourself or ask here how it should be modified.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Introduction & question about contributing source code?
Posted by Hung Mark <ma...@gmail.com>.
Hi Andrea,
I followed the link here:
https://wiki.openoffice.org/wiki/Development
The development page were found by google 'OpenOffice contributing'
Sincerely.
2014-08-30 5:17 GMT+08:00 Andrea Pescetti <pe...@apache.org>:
> On 23/08/2014 Hung Mark wrote:
>
>> I tried to submit issues I've found (
>> https://issues.apache.org/ooo/show_bug.cgi?id=125400 ),
>> also attached the patch I've made, not knowing if I've did it right. I
>> think you are busy releasing new version these days.
>>
>
> Indeed, but I see that conversation is now ongoing on your patches
> Bugzilla pages, good.
>
>
> However it seems that wiki page for contributor is outdated:
>> https://wiki.openoffice.org/wiki/Contributing_Patches
>> ( it suggest to use hg to make patch, and domain developer list marked
>> outdated, URL to IRT & IIT links are invalid now.
>>
>
> It was absurdly outdated and misleading, you are right. I've updated it
> now. Of course, feel free to edit it (you should have an account) or ask if
> something is unclear.
>
> Had you found it using a search engine or from some navigation path in our
> wiki?
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Mark Hung
Re: Introduction & question about contributing source code?
Posted by Andrea Pescetti <pe...@apache.org>.
On 23/08/2014 Hung Mark wrote:
> I tried to submit issues I've found (
> https://issues.apache.org/ooo/show_bug.cgi?id=125400 ),
> also attached the patch I've made, not knowing if I've did it right. I
> think you are busy releasing new version these days.
Indeed, but I see that conversation is now ongoing on your patches
Bugzilla pages, good.
> However it seems that wiki page for contributor is outdated:
> https://wiki.openoffice.org/wiki/Contributing_Patches
> ( it suggest to use hg to make patch, and domain developer list marked
> outdated, URL to IRT & IIT links are invalid now.
It was absurdly outdated and misleading, you are right. I've updated it
now. Of course, feel free to edit it (you should have an account) or ask
if something is unclear.
Had you found it using a search engine or from some navigation path in
our wiki?
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Introduction & question about contributing source code?
Posted by jan i <ja...@apache.org>.
On 23 August 2014 10:22, Hung Mark <ma...@gmail.com> wrote:
> Hello there,
>
> I started to subscribe these list since May. I began by asking question on
> API list, volunteer translation on l10n and doc, than finally, I start to
> investigate annoying issues I encountered. I come from Taiwan and am
> interested about issues specific to traditional Chinese.
>
> I tried to submit issues I've found (
> https://issues.apache.org/ooo/show_bug.cgi?id=125400 ),
> also attached the patch I've made, not knowing if I've did it right. I
> think you are busy releasing new version these days. Now that I know how to
> build and debug now, I may be able to help more.
>
The core developers are quite busy. I had a quick look at your patch and it
seems fine, but I am not a specialist in that part of the code so I cannot
apply the patch.
>
> However it seems that wiki page for contributor is outdated:
> https://wiki.openoffice.org/wiki/Contributing_Patches
>
> ( it suggest to use hg to make patch, and domain developer list marked
> outdated, URL to IRT & IIT links are invalid now.
>
If you have a wiki account go ahead and update, otherwise ask for a wiki
accoun.
>
> What is the correct procedure to propose a patch for defect ( or
> enhancement) ?
>
Either through BZ (as you have done) followed by a mail on this list or by
simply mailing the patch here.
If its a patch for a known BZ issue, of course it should be attached to
that issue.
Lookiing forward to see more patches from you.
rgds
jan i
> Please advice.
>
> Sincerely.
>
> --
> Mark Hung
>