Revision: 59c2d89a2f29
Author: nogu.dev <[email protected]>
Date: Mon Oct 8 02:22:00 2012
Log: Add description on GitHub pull requests to ContributeUim.wiki.
* ContributeUim.wiki
- Add description on how to contribute uim using GitHub.
http://code.google.com/p/uim/source/detail?r=59c2d89a2f29&repo=wiki
Modified:
/ContributeUim.wiki
=======================================
--- /ContributeUim.wiki Sat Oct 6 17:03:08 2012
+++ /ContributeUim.wiki Mon Oct 8 02:22:00 2012
@@ -4,11 +4,12 @@
= Introduction =
-This page describes how to contribute uim and make uim better. In general,
you have 2 ways to constribute uim:
+This page describes how to contribute uim and make uim better. In general,
you have 3 ways to constribute uim:
+ * Sending a [https://help.github.com/articles/using-pull-requests pull
request] to a [https://github.com/uim GitHub repository]
* Reporting to the [https://bugs.freedesktop.org/ Bugzilla]
* Posting to the [https://groups.google.com/forum/#!forum/uim-en uim-en]
mailing list
-While you need to create an account for the Bugzilla before reporting to
the Bugzilla, you need to subscribe the mailing list before posting to the
uim-en mailing list.
+You need to create an account before contributing uim: a GitHub account
for sending a pull request, a Bugzilla account for reporting to the
Bugzilla and a Google account for subscribing and posting to the uim-en
mailing list.
The intended audience of this page is mainly a non-committer, who doesn't
permission to commit the uim repository.
@@ -26,11 +27,11 @@
== Fixing a bug ==
When fixing a bug, you should include the following items in your report:
- * your patch to fix the bug
+ * your patches to fix the bug (your commits for a GitHub pull request)
* description on the bug
* description on what your patch does
-You should use "git format-patch" to create your patch. For detail, see
[DevelopUim].
+You should use "git format-patch" when creating your patch. For detail,
see [DevelopUim].
You can see the existing bug reports by
[https://bugs.freedesktop.org/buglist.cgi?bug_status=__open__&product=UIM
searching the Bugzilla].
@@ -41,13 +42,13 @@
== Adding a feature ==
When you want to add a new feature to uim, you should include the
following items in your report:
- * your patches to add a new feature
+ * your patches to add a new feature (your commits for a GitHub pull
request)
* description on the feature
* description on what your patches do
-If your patches pass a commiter's review, your patches will be merged into
the uim repository.
+If your patches (commits) pass a commiter's review, your patches (commits)
will be merged into the uim repository.
-If your patches are non-trivial and accepted by a committer, the committer
may make you a committer.
+If your patches (commits) are non-trivial and accepted by a committer, the
committer may make you a committer.
== Translating ==
@@ -59,7 +60,7 @@
}}}
The names of the po files are based on language code. For example, the po
file for the German language is "de.po" because "de" is a language code for
the German language. You can see all the language codes in
[http://www.gnu.org/software/gettext/manual/gettext.html#Language-Codes
Appendix A Language Codes in the official gettext manual].
-If the uim repository have a translation file corresponding to your native
language, edit the file and post the file to post the Bugizlla or the
uim-en mailing list.
+If the uim repository have a po file corresponding to your native
language, edit the file and post the po file to post the Bugizlla or the
uim-en mailing list. Instead, you can also send a GitHub pull request to
add the po file.
If the repository doesn't have a correspoing po file, you need to create
one. Here is how to create a po file.
@@ -82,4 +83,4 @@
* Lokalize
* Poedit
-Finally, post the po file to post the Bugzilla or the uim-en mailing list.
+Finally, post the po file to post the Bugzilla or the uim-en mailing list.
Instead, you can also send a GitHub pull request to add the po file.
