TikiDevNewbie

This page is dedicated to helping new developers understand what they are doing and prevent them from making some very common mistakes. As you learn, please come back and update this page - share what you have learned.

1. Join the ))TikiWikiDev(( mailing lists at https://sourceforge.net/mail/?group_id=64258 and ask lots of questions.
2. Join the group on IRC and ask lots of questions. Read ConnectingToIrc for instructions
3. Use ))TikiWiki(( and understand what it is doing before you ever start trying to change it. Set up a site and use it on an everyday basis until you can fix most of the problems you encounter.
4. Read the SourceForge pages for beginners on CVS https://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1
5. Setup your local system to use one or more of the CVS branches (there are several). The bleeding edge is Head.
6. If you are not sure how to set up a local server and want to use IIS on a Windoz machine read IisInstall. I downloaded a program called Sokkit from http://www.sokkit.net/pragmacms which does an excellent job of installing Apache, ))MySql(( & PHP on a Windoz XP Home system.
7. Set up a hosted site. This will be your playground and is a way to show off your latest feature. Then let everyone on #tikiwiki know you have something new. If you haven't already been asked to join the group - you will be now.
8. Read the SourceForge pages for developers on CVS https://sourceforge.net/docman/display_doc.php?docid=768&group_id=1
9. Ask lots of questions on IRC about CVS. Using CVS correctly could be a degree all by itself. 😀
10. You will need SSH if you are going to be updating SourceForge - so read https://sourceforge.net/docman/display_doc.php?docid=6841&group_id=1
11. Read the 3Rules
12. If this is the first open-source project that you have worked on, then try to understand that an open-source project is NOT like anything that you have ever done. You will be dealing with a large number of people who are scattered all over this beautiful world of ours. Many of our friends learned English as a second (or third) language. Misunderstanding WILL happen! All of this will require an added effort on your part. Please read KinderCode often.
13. Before you DO anything – make sure that you KNOW what you are supposed to be doing and the right way to do it. It doesn't make a lot of sense for you to burn yourself trying to accomplish something the Hard Way when a few simple questions could save you a lot of effort. Again – ask questions and use the expertise that is available.
14. If you need help with something – ASK! Most of us will be more than happy to help when we can – but we need to when (and where) the help is needed. This is a very friendly group who believe in helping each other!
15. Finally – That nasty word Documentation. While nobody expects a developer to spend his time writing the documentation for the manual, some documentation is necessary. Writing a simple proposal in a Wiki page stating what you want to accomplish and how you plan to do it does several things. First, it will help you to clarify your thoughts. Second, it should provide you and others with some specific goals. The most important thing is that it will provide others with a place where they can comment on your ideas. Documenting the source code is also important! Comments allow an unskilled novice (like me) to get become better.