directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject svn commit: r1777053 - in /directory/site/trunk/content: apacheds/coding-standards.mdtext api/coding-standards.mdtext fortress/coding-standards.mdtext mavibot/coding-standards.mdtext
Date Tue, 03 Jan 2017 02:36:50 GMT
Author: smckinney
Date: Tue Jan  3 02:36:50 2017
New Revision: 1777053

URL: http://svn.apache.org/viewvc?rev=1777053&view=rev
Log:
slight chg to welcome dev parags


Modified:
    directory/site/trunk/content/apacheds/coding-standards.mdtext
    directory/site/trunk/content/api/coding-standards.mdtext
    directory/site/trunk/content/fortress/coding-standards.mdtext
    directory/site/trunk/content/mavibot/coding-standards.mdtext

Modified: directory/site/trunk/content/apacheds/coding-standards.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/coding-standards.mdtext?rev=1777053&r1=1777052&r2=1777053&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/coding-standards.mdtext (original)
+++ directory/site/trunk/content/apacheds/coding-standards.mdtext Tue Jan  3 02:36:50 2017
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Software
 
 # Coding Standards
 
-Welcome to you, developper ! You have been elected committer on the project, or you want
to contribute some code or some patch? This is great news. However, in order to be able to
share your 'vision' and your code, some rules must be followed.
+Welcome to you, developer -- you've maybe been elected committer on the project, or want
to contribute some code / patch? This is great news! However, in order to be able to share
your 'vision' and your code, some rules must be followed.
 
 Hey, remember that those rules are not the best nor the worst, they are pretty much what
they are for historical reasons, or for technical reasons, however, please, accept them as
they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using
spaces instead of tab ??? How stupid is this rule etc etc.) Rules are **alway*s* stupid, but
smart people follow them ;)
 
@@ -164,4 +164,4 @@ Always declare all the classes you impor
 
 Well, this was a very short introduction about coding rules. Use commen sense, look at what
you see around you when adding some code, ask people about format, if you have a question.
 
-That's it ! (I wait your comments, guys :-)
\ No newline at end of file
+That's it ! (I wait your comments, guys :-)

Modified: directory/site/trunk/content/api/coding-standards.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/coding-standards.mdtext?rev=1777053&r1=1777052&r2=1777053&view=diff
==============================================================================
--- directory/site/trunk/content/api/coding-standards.mdtext (original)
+++ directory/site/trunk/content/api/coding-standards.mdtext Tue Jan  3 02:36:50 2017
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Software
 
 # Coding Standards
 
-Welcome to you, developper ! You have been elected committer on the project, or you want
to contribute some code or some patch? This is great news. However, in order to be able to
share your 'vision' and your code, some rules must be followed.
+Welcome to you, developer -- you've maybe been elected committer on the project, or want
to contribute some code / patch? This is great news! However, in order to be able to share
your 'vision' and your code, some rules must be followed.
 
 Hey, remember that those rules are not the best nor the worst, they are pretty much what
they are for historical reasons, or for technical reasons, however, please, accept them as
they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using
spaces instead of tab ??? How stupid is this rule etc etc.) Rules are **alway*s* stupid, but
smart people follow them ;)
 
@@ -164,4 +164,4 @@ Always declare all the classes you impor
 
 Well, this was a very short introduction about coding rules. Use commen sense, look at what
you see around you when adding some code, ask people about format, if you have a question.
 
-That's it ! (I wait your comments, guys :-)
\ No newline at end of file
+That's it ! (I wait your comments, guys :-)

Modified: directory/site/trunk/content/fortress/coding-standards.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/fortress/coding-standards.mdtext?rev=1777053&r1=1777052&r2=1777053&view=diff
==============================================================================
--- directory/site/trunk/content/fortress/coding-standards.mdtext (original)
+++ directory/site/trunk/content/fortress/coding-standards.mdtext Tue Jan  3 02:36:50 2017
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Software
 
 # Coding Standards
 
-Welcome to you, developper ! You have been elected committer on the project, or you want
to contribute some code or some patch? This is great news. However, in order to be able to
share your 'vision' and your code, some rules must be followed.
+Welcome to you, developer -- you've maybe been elected committer on the project, or want
to contribute some code / patch? This is great news! However, in order to be able to share
your 'vision' and your code, some rules must be followed.
 
 Hey, remember that those rules are not the best nor the worst, they are pretty much what
they are for historical reasons, or for technical reasons, however, please, accept them as
they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using
spaces instead of tab ??? How stupid is this rule etc etc.) Rules are **alway*s* stupid, but
smart people follow them ;)
 
@@ -164,4 +164,4 @@ Always declare all the classes you impor
 
 Well, this was a very short introduction about coding rules. Use commen sense, look at what
you see around you when adding some code, ask people about format, if you have a question.
 
-That's it ! (I wait your comments, guys :-)
\ No newline at end of file
+That's it ! (I wait your comments, guys :-)

Modified: directory/site/trunk/content/mavibot/coding-standards.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/mavibot/coding-standards.mdtext?rev=1777053&r1=1777052&r2=1777053&view=diff
==============================================================================
--- directory/site/trunk/content/mavibot/coding-standards.mdtext (original)
+++ directory/site/trunk/content/mavibot/coding-standards.mdtext Tue Jan  3 02:36:50 2017
@@ -18,7 +18,7 @@ Notice: Licensed to the Apache Software
 
 # Mavibot Coding Standards
 
-Welcome to you, developer ! You have been elected committer on the project, or you want to
contribute some code or some patch? This is great news. However, in order to be able to share
your 'vision' and your code, some rules must be followed.
+Welcome to you, developer -- you've maybe been elected committer on the project, or want
to contribute some code / patch? This is great news! However, in order to be able to share
your 'vision' and your code, some rules must be followed.
 
 Hey, remember that those rules are not the best nor the worst, they are pretty much what
they are for historical reasons, or for technical reasons, however, please, accept them as
they are, and avoid religious war (please, oh please, no mail to say "WTF ? You are using
spaces instead of tab ??? How stupid is this rule etc etc.) Rules are **alway*s* stupid, but
smart people follow them ;)
 
@@ -164,4 +164,4 @@ Always declare all the classes you impor
 
 Well, this was a very short introduction about coding rules. Use common sense, look at what
you see around you when adding some code, ask people about format, if you have a question.
 
-That's it ! (I wait your comments, guys :-)
\ No newline at end of file
+That's it ! (I wait your comments, guys :-)



Mime
View raw message