像是任何的開放原始碼的應用, LiquiBase is built 由許多人, 通常 in their spare time. 正當 我們 are proud of what we have accomplished so far, there is 還是 much to do and 我們總是在尋找新的人們 to help out.
As a software application, there is always a need for coding. Take a look at the issue tracker or future directions page for ideas on what needs to be done or tackle something that you have noticed could use improving. Both patches and simple pointers on how to improve or fix the code are always appreciated. If you have questions on how the code works, visit the Architecture page or contact the liquibase-devel mailing list.
Face it, we all like coding more than documenting. To the end user, however, the documentation is what makes a tool usable. The liquibase.org site is implemented as a wiki to allow anyone to quickly and easily add to and fix the site, so feel free.
75% of the liquibase.org traffic is from non-English users. If you are interested in translating sections (or even single pages) of the site, feel free to do so. If you have any questions, contact the liquibase-doc mailing list.
German, French, and Portuguese are in the most need of translators.
Love LiquiBase? Tell your friends. Blog us. We don't have an advertising budget, so word of mouth is what we need.
If you find a bug or know of a feature that would be useful to you, let us know. We try to guess at what end-users want and need, but real feedback from real users is extremely valuable and makes LiquiBase better for everyone.
Tips are never expected, but always appreciated. All donations go toward LiquiBase hosting and development costs.