Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Developers

We welcome everyone to join CUBRID's growing Open Source Community. All users, developers and administrators are highly encouraged to work on enhancing CUBRID, asking questions, and helping other peers with their issues at our CUBRID Forum. Our core developers together with other community users will gladly reply to your issues.

  1. Before you start probably you wish to learn how to quickly start using CUBRID DBMS. You can start from Getting Started section.
  2. Make sure you have brief understandings about the structure of CUBRID Manual. Look around, see how it is organized, so that when some issues arise you could immediately realize where to search for an answer.
  3. CUBRID Documentation will probably be the place you visit the most while you are learning how to use CUBRID.
  4. We constantly create detailed Tutorials how to use different tools and web applications with CUBRID.
  5. In addition to the above mentioned resources, we often publish detailed tutorials and HOWTOs on our CUBRID Blog. Make sure you visit our Blog regularly. Better to subscribe to RSS.

Please, visit these resources, read the manuals and documentations, and if you still have questions, do not hesitate to post them at CUBRID Forum.

How to become a Contributor

Any open source project needs active contributors. So does CUBRID. Thanks to our CUBRID Developers Community, now everyone can download and deploy a very fast and highly optimized database server. If you want to be a part of CUBRID Community, the first thing you can do is provide feedback. Download and install CUBRID, start using and tell us what you think of it. Report any problems or issues at CUBRID Forum.

Here are the list of all activities you can get involved in.

Provide feedback

Use CUBRID and provide feedback to CUBRID Developers Community. Share your knowledge and experiences with us, tell the community users how you reached unbelievable performance. Feel free to post your requests for new features that you would like to see in our next release of CUBRID DBMS. Your voice is counted! You may also want to read the CUBRID Manual. You may find it very useful.

Documentation

If you are good at writing and understanding someone's code, your well-written documents will be highly welcomed. We always need exhaustive documents for our enthusiastic users, web and open source developers. You can start writing your knowledge and know-how on wiki page little by little together with other developers. The more the merrier.

Reporting bugs

If you found specific issues and ideas while using CUBRID, you can submit a bug report to CUBRID Forum. To help us quickly identify and fix the bug, be sure to include as much information with your report as possible such as your platform, version numbers, error logs, configurations, screen shot and so on. Before you post your issue, make sure your bug has not already been reported. You will definitely receive tons of enthusiastic responses from other developers like you.

Submitting patches

If you are good at coding, you can contribute to the CUBRID project directly. Instead of just reporting bugs, you can fix what really bothers you and submit patches. Once you have the code checked out, built, and made your changes, you'll need to learn how the bug-fixing process works, coding guidelines, and other information necessary in order to make them accepted.

  1. Check out the latest copy of the sources from SVN
    http://sourceforge.net/scm/?type=svn&group_id=280608
  2. Change the source files to incorporate your patches. Make sure your code complies with the CUBRID coding convention and also provides appropriate code documentation along with your code.
  3. Compile it and check if it runs correctly.
  4. Run any number of tests or regression tests.
  5. Upload your patch for review. All patches from contributors must be reviewed by code-reviewers who will mainly look for code quality. The review process can consist of multiple iterations between you and the reviewers as revisions are made to your patch.
  6. Make any changes recommended by the reviewers and submit your final patches.
  7. Submitting the CUBRID Committer’s Agreement.
  8. This step is necessary to make your patches committed. You need to fill out the CUBRID Committer’s Agreement and submit it to us. Read it carefully and sign it if you understand and agree to our legal requirements. If you had already sent the form, you don’t have to send it repeatedly as long as your contact information is not updated.

    You can deliver the CUBRID Committer's Agreement via email. Print the PDF document and fill it with necessary information. After you sign it, scan it legibly and then email a signed copy to: legal@cubrid.org.




You are either using a very old browser or a browser that is not supported.
In order to browse cubrid.org you need to have one of the following browsers:



Internet Explorer: Mozilla Firefox: Google Chrome: