You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Dick Groskamp <th...@quicknet.nl> on 2011/06/26 14:14:25 UTC
Re: [PATCH -corrected} Fixing some typos in ppmc-faqs.mdtext
Op 25-6-2011 20:25, Eike Rathke schreef:
> Hi Dick,
>
> I'm not a native English speaker, but I think I have some corrections.
Me neither, but I think you're right
> Confusing enough your diff used '-' for your version and '+' for the
> original version, please try to produce diffs specifying files in the
> correct order.
Didn't know there was a specific order :-)
Now I do and will apply
> On Saturday, 2011-06-25 19:25:06 +0200, Dick Groskamp wrote:
>
>> + 1. You have send in patches that were well-respected to improve the software.
>> That should be "You have sent" instead.
Yep, missed that completely
> You have shown that you can discuss in the mailing lists and that this has
> "mailing lists" IMHO was correct, the nouns aren't concatenated in
> English.
Couldn't find anything that contradicts your view, so corrected them
back to "mailing lists"
> I think "e-mail address" was correct.
Couldn't find anything that contradicts your view, so corrected them
back to "e-mail address "
> Eike
Thanks.
Created a new patch and attached it to this message
--
DiGro
Windows 7 and OpenOffice.org 3.3
Scanned with Ziggo uitgebreide Internetbeveiliging (F-Secure)
Re: [PATCH -corrected} Fixing some typos in ppmc-faqs.mdtext
Posted by Dick Groskamp <th...@quicknet.nl>.
Op 26-6-2011 14:40, TJ Frazier schreef:
> Hi, Dick,
> On 6/26/2011 08:14, Dick Groskamp wrote:
> [snip]
> Thanks for fixing those compound nouns. I'm not sure that the
> progression of "user name" to "user-name" to "username" is complete,
> but—if it's an Apache convention—I can live with it.
> You might also fix "abbrIviations" and "Corporate Contributor LiSenCe
> Agreement".
>
Thanks for that.
Now I've learned to keep my changes a bit longer on file and not to
delete them after sending the e-mail :-)
(I had changed the Lisence in the first draft to License, but it got
lost in the second)
next thing I've learned is to be more careful with compound nouns, we
tend to bring them all together, but
I've noticed that might not be the right way to do it.
I've rapplied my changes and made up a new patch.
--
DiGro
Windows 7 and OpenOffice.org 3.3
Scanned with Ziggo uitgebreide Internetbeveiliging (F-Secure)
Re: [PATCH -corrected} Fixing some typos in ppmc-faqs.mdtext
Posted by TJ Frazier <tj...@cfl.rr.com>.
Hi, Dick,
On 6/26/2011 08:14, Dick Groskamp wrote:
[snip]
> Created a new patch and attached it to this message
> > Index: ppmc-faqs.mdtext.diff
> ===================================================================
> --- ppmc-faqs.mdtext.diff (revision 0)
> +++ ppmc-faqs.mdtext.diff (revision 0)
> @@ -0,0 +1,59 @@
> +--- D:/Documents en Settings/Dick/Apache Openoffice.org/site/trunk/content/openofficeorg/ppmc-faqs.mdtext vr jun 24 18:56:53 2011
> ++++ D:/Documents en Settings/Dick/Apache Openoffice.org/site/trunk/content/openofficeorg/ppmc-faqs.mdtext.fix zo jun 26 13:52:04 2011
> +@@ -34,17 +34,17 @@
> +
> + The following are conditions to become a committer:
> +
> +- 1. You have send in patches that were well-respected to improve the software.
> ++ 1. You have sent in patches that were well-respected to improve the software.
> + 2. You have added documentation to the Wiki or website that were well-respected to
> +- improvent the non-code part of the project.
> ++ improve the non-code part of the project.
> + 3. You have shown that you can discuss in the mailing lists and that this has
> + brought us forward.
> + 4. You are well known to the established members, who you are and what you have
> + done in the past. Regarding this project, a former-one or another project.
> +
> +-If 1 of the 4 statements above are true, then you can be voted in as committer.
> ++If 1 of the 4 statements above is true, then you can be voted in as committer.
> +
> +-When the vote resut is positive, you will be asked for some information to setup
> ++When the vote result is positive, you will be asked for some information to setup
> + your committer status.
> + <br> ([see here for more information][4])
> +
> +@@ -52,9 +52,9 @@
> +
> + The following is a brief summary of what to expect as committer:
> +
> +- 1. After your (Invividual Contributor Lisence Agreement ([iCLA][5]) has been
> ++ 1. After your (individual Contributor Lisence Agreement ([iCLA][5]) has been
> + received and registered, you will be invited to specify one or more preferred
> +- Apache user names.
> ++ Apache usernames.
> +
> + **Important**: The e-mail address you provide in your iCLA will be used for the
> + following communications with you.
> +@@ -62,11 +62,11 @@
> + Please note that there is also a [Corporate Contributor Lisence Agreement
> + (CCLA)][6] if you want/have to commit in the name of a company or organization.
> +
> +- 2. Choose one or more User Names that would be acceptable to you. These are short
> ++ 2. Choose one or more Username(s) that would be acceptable to you. These are short
> + names or abbriviations that will be used for a Unix account login.
> +
> + **Example:** <br>
> +- Your name is "John Doe", so an ID cound be "johnd" or "jdoe". [Here you can see
> ++ Your name is "John Doe", so an ID could be "johnd" or "jdoe". [Here you can see
> + if the ID is still free][7] or already given to another committer.
> +
> + Supply all other information that is requested. Return the ID requests as
> +@@ -77,7 +77,7 @@
> + the order you would like to have, so the first one is the most wanted.
> +
> + 4. You will receive an e-mail, from "root@apache.org", that confirms the Apache
> +- user name for you and also provides you with an initial password. There are also
> ++ username for you and also provides you with an initial password. There are also
> + instructions for changing your password. Please be patient as this mail can take
> + some days.
> +
Thanks for fixing those compound nouns. I'm not sure that the
progression of "user name" to "user-name" to "username" is complete,
but—if it's an Apache convention—I can live with it.
You might also fix "abbrIviations" and "Corporate Contributor LiSenCe
Agreement".
--
/tj/
(Notorious proof-reading nitpicker.)