Navigation Menu

Home

About LOE

News

Screenshots

Download

Support

LOE Forum

Contributions

This site is best viewed with Firefox.



Problems?  Email the Webmaster.



This site hosted by:
SourceForge.net Logo

Contributions:

Since Law Office Essentials is still a start-up project, we are really not picky as to who contributes nor how they wish to contribute.  If you would like to volunteer to help us get this project going, make suggestions as to where this project should head, assist in planning and desiging this project's Web site, donate money to this project, or whatever else you may be able to think of, please, drop me a line.  Thank you.



Developer Rules

  1. Comment, comment, comment!  I cannot stress this enough!  Please comment your code, regardless of how "self-explanatory" you may think the code is.  We may have young (read:  NooB) developers working with us, so be kind to them and explain what it is that you are doing in your code.  Comments do not make the source files that much bigger and have no effect whatsoever on the size of the compiled files, so comment excessively.
  2. When a developer adds code, comment why the code was added, date the code was added and Unix name of the developer who added the code.
  3. When a developer changes another developer's code, comment out the original code, comment why the code was modified, date the code was modified and Unix name of the developer who modified the code.
  4. DO NOT create a new CVS tree without the prior permission of the Project Administrator.
  5. When permission has been given to create a new CVS tree, please upload only the source code files and not the entire project structure from the IDE that you choose to use.  This is because not all developers on this project use the same IDE and we don't want any problems created by "forcing" developers to use an IDE they either don't like or don't know.  Remember, some "old-school" developers don't even use an IDE, they do all of their develpment on the command-line using tools such as emacs and vi.
  6. Other rules may be placed here from time to time, so check back often for updates.  These rules may change at any time, with or without notice.

Developers:  The "Office" CVS source tree is now dead!  To check out the source code for the Law Office Essentials (LOE) Project, please use the "LOE" tree.  Also, contrary to the "Developer Rules" above, I did upload the entire project tree from NetBeans IDE 6.0.  If this causes you any problems, please let me know and I will see what I can do to fix the problem.  I did this so that all required libraries for the project are available from the CVS tree.  This should prevent everyone from having to go out and search the Internet to find the JAR files of the libraries that we are relying on for this Project.

I guess that what I'm saying is that you can kind of ignore the rule regarding placing entire IDE project structures on the CVS tree.

Also, notice that there is now a PekinSOFTResources tree on the CVS server.  This tree is invalid.  I tried to "defunct" the "LogViewer" tree and replace it with the "PekinSOFTResources" tree, because that project is not just the PekinSOFT Standard Log Viewer.  That project has a bunch of other required functionality in it as well.  However, for some reason the files would not upload properly, so the "PekinSOFTResources" tree is not valid.  Also, since I am unable to use the "LogViewer" tree that mashraf created, the PekinSOFT Resource Library only exists on my computer with modifications.  I know that this causes a lot of problems, and I do apologize for that.  However, if you need the PekinSOFT Resource Library, I will happily email you the binary.  I will also send you the source if you ask for it, but ask that if you make modifications to the source, do not upload those changes to the CVS server.  I would rather you just sent me an email telling me which file you made changes in, what the changes were, your Unix name and the date that you made the changes.  I will then place those changes into the appropriate location (with the appropriate comments) and email out the recompiled binary package to everyone.  This way, I'm the only one who suffers due to this situation.  I thank all of you for your support and cooperation until I can get this CVS problem figured out.

Contribution Ideas…