Changes between Version 1 and Version 2 of Contribute


Ignore:
Timestamp:
Jun 30, 2010, 10:13:00 AM (9 years ago)
Author:
Frederico Caldeira Knabben
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Contribute

    v1 v2  
    22[[PageOutline]]
    33
    4 = How to contribute to (F)CKEditor =
     4= How to contribute to the CKEditor project =
    55
    6 There are several ways you can help its development, here's the guidelines:
     6There are several ways you can help CKEditor to become a better software to you and to others. You can do that by:
    77
    8  * By [#Reportingbugs reporting bugs].
    9  * By [#Providingpatches submitting patches].
    10  * By [#Translating translating]
    11  * By [#Documentation writing] documentation.
    12  * By writing [http://docs.cksource.com/FCKeditor_3.x/Design_and_Architecture/Plugin_Based plugins] around (F)CKEditor.
    13  * By '''helping''' others through our [http://cksource.com/forums/viewforum.php?f=10 support board] on forum.
    14  * 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.
     8 * [#Reportingbugs Reporting bugs].
     9 * [#Providingpatches Submitting patches].
     10 * [#Translating Translating]
     11 * [#Documentation Writing] documentation.
     12 * Writing [http://docs.cksource.com/FCKeditor_3.x/Design_and_Architecture/Plugin_Based plugins] around CKEditor.
     13 * '''Helping''' others through our [http://cksource.com/forums/viewforum.php?f=10 support board] on forum.
     14 * '''Discussing''' on how CKEditor could be improved by posting on the [http://cksource.com/forums/viewforum.php?f=11 development board] on forum.
    1515
    1616== Reporting bugs ==
     
    2323Inside a patch, following [wiki:CodingStyle coding standards] is one of the easiest way for everybody to understand everybody's code and require no housekeeping.
    2424
    25 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].
     25Patch 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].
    2626
    2727Please don't put the patch in the ticket description or comment, unless it's a single line patch.
     
    3232
    3333To 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].
    34 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.
     34Depending 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.
    3535
    3636=== Translating ===
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy