Changes between Version 1 and Version 2 of Contribute

Timestamp:

Jun 30, 2010, 10:13:00 AM (14 years ago)

Author:

Frederico Caldeira Knabben

Comment:

--

Contribute

@@ -2 +2 @@
 [[PageOutline]]
 
-= How to contribute to (F)CKEditor =
+= How to contribute to the CKEditor project =
 
-There are several ways you can help its development, here's the guidelines:
+There are several ways you can help CKEditor to become a better software to you and to others. You can do that by:
 
- * By [#Reportingbugs reporting bugs].
- * By [#Providingpatches submitting patches].
- * By [#Translating translating]
- * By [#Documentation writing] documentation.
- * By writing [http://docs.cksource.com/FCKeditor_3.x/Design_and_Architecture/Plugin_Based plugins] around (F)CKEditor.
- * By '''helping''' others through our [http://cksource.com/forums/viewforum.php?f=10 support board] on forum.
- * By '''discussing''' on how (F)CKEditor could be improved by posting on the [http://cksource.com/forums/viewforum.php?f=11 development board] on forum.
+ * [#Reportingbugs Reporting bugs].
+ * [#Providingpatches Submitting patches].
+ * [#Translating Translating]
+ * [#Documentation Writing] documentation.
+ * Writing [http://docs.cksource.com/FCKeditor_3.x/Design_and_Architecture/Plugin_Based plugins] around CKEditor.
+ * '''Helping''' others through our [http://cksource.com/forums/viewforum.php?f=10 support board] on forum.
+ * '''Discussing''' on how CKEditor could be improved by posting on the [http://cksource.com/forums/viewforum.php?f=11 development board] on forum.
 
 == Reporting bugs ==
@@ -23 +23 @@
 Inside a patch, following [wiki:CodingStyle coding standards] is one of the easiest way for everybody to understand everybody's code and require no housekeeping.
 
-Patch files are the official way to present us your contirubtion, it should always be in the [http://en.wikipedia.org/wiki/Diff unified diff] format and apply to the conventoin described [wiki:TicketLifeCycle#ProposingPatches here].
+Patch files are the official way to present us your contribution, it should always be in the [http://en.wikipedia.org/wiki/Diff unified diff] format and apply to the convention described [wiki:TicketLifeCycle#ProposingPatches here].
 
 Please don't put the patch in the ticket description or comment, unless it's a single line patch.
@@ -32 +32 @@
 
 To make sure the quality of project, we only open repository commit permission for core developers, as a community contributors, it's enough to add ''''HasPatch'''' to the '''keyword''' ticket field, and let the core developers take care of the integration it into the [wiki:TicketLifeCycle workflow].
-Depending on the review result, your patch may finally get accepted and get commited, or you may choose to come with a new patch in case the review fails.
+Depending on the review result, your patch may finally get accepted and get committed, or you may choose to come with a new patch in case the review fails.
 
 === Translating ===