I'm currently evaluating OrangeHRM as an HRIS option for my company, but I have to say that the documentation makes it difficult!
1. Documented installation procedures are difficult to follow. (And, using the installer pack as an "easy" option didn't result in a functioning application for me...)
2. Much of the documentation included in the installer package for v2.4.1 stable has not been updated since v126.96.36.199.
3. Importantly, the Orange Future wiki seems as though it has not been properly updated in a while. Last update was 7 August 2008 and it accounts for v2.2.1. That means I can't look at the future feature suggestions as a quick way of seeing what OHRM cannot do, and see if any of that is critical for me. A lot of the suggestions seem to have been implemented in v2.4.1, going by the forums. Can someone on the development team please sweep through the Future wiki and update it so that it's only listing things that have not been implemented? You're more likely to get additions made to it then, too.
4. Depending on what the system can currently do, I may be looking at doing some minor customisations for our install. Various notes and tips are scattered throughout the forums, but very difficult to find! How about establishing a section somewhere (probably in the Developer wiki) where people can post info about what manual hacks they've done, sort of an "at your own risk" database of developer info?
The Orange Future wiki still has not been updated except for changes which I made myself at this time.
Is anybody monitoring the Orange Future wiki? Is this information available anywhere else instead?
Can we assume then that nobody is planning on monitoring or updating the Orange Future wiki?
By making it so hard you're missing out on a lot of ideas and participation from your user community, and probably putting off new users too.
I've got to say that I find the lack of response here and the zero maintenance on the wiki discouraging.
We're monitoring OrangeWiki from time to time, but we're no longer promoting the Wiki as the place for users make feature requests. The Wiki served its purpose when we were getting only a few requests, but the current issue is that there are so many different feature requests from users, and it is impossible for us to implement all features users want. Therefore we need to know what sort of demand each of the features has, such that we can focus on features with the highest demand from the community. For this, surveys have been more effective.
There is a number of feature surveys on the roadmap section of the Wiki:
Hundreds of users have already taken these surveys and it gives us a better idea of the level of demand. For example the highest demand right now is for a performance review module with more than 40% of users wanting that.
The roadmap section also has details of features currently being defined.
E.g. Leave Accrual: http://www.orangehrm.com/wiki/index.php/Accrual_of_Leave
We review the surveys quite frequently to see what the demand is and define our immediate development tasks. Although OrangeWiki is still being monitored, it's now serving the purpose of generating feature ideas to be added to the surveys where users can vote for them.
Also from time to time, we publish the planned development tasks and new surveys on our Blog:
Regarding user guide, I agree that it's not up-to-date. However, from OrangeHRM 2.5 onwards, we plan to have a comprehensive Wiki based user guide directly accessible from the product from a Help menu. You can check the work in progress from here.
This is still at its initial stages, and only Attendance Tracking section is close to being completed.
Thanks for getting back to me! Your response has cleared a few things up.
We're monitoring OrangeWiki from time to time, but we're no longer promoting the Wiki as the place for users make feature requests.
...then the appropriate thing to do would be to make that clear in the wiki, as that's a place where people are likely to end up (and then find out of date) if they first look at the forums for guidance. Otherwise, it really just looks like you're not keeping the documentation up to date and it makes it very hard for users to contribute their ideas to help you on the dev side. I have added some notes there for you.
There is a number of feature surveys on the roadmap section of the Wiki: http://www.orangehrm.com/wiki/index.php/Product_Roadmap
...which is not linked to from the Roadmap section of the website for some reason. I've added a link to this section from the Orange Future wiki, also.
Although OrangeWiki is still being monitored, it's now serving the purpose of generating feature ideas to be added to the surveys where users can vote for them.
The Orange Future wiki is not serving that purpose. It's cluttered with historical requests and suggestions that have often been implemented, and noone's added any new content to the OF wiki section since October.
...from OrangeHRM 2.5 onwards, we plan to have a comprehensive Wiki based user guide directly accessible from the product from a Help menu.
Good to hear that this is coming along, and having it wiki based will also be a benefit!
Thanks Bruce for your comments.
OrangeFuture will be removed sometime in future. However, we did not want to remove it immediately as some users may have book marked it, and we also have some forum posts linking to this. However, OrangeFuture is not linked from anywhere on the Wiki (earlier there used to be a link on the left menu on Wiki). This may be the reason that there is not much activity there since last year. However, we will still keep on scanning it from time to time for new ideas (if any).
I agree that the website needs some improvements. We're planning on changing the features and roadmap sections. We're in the process of designing the content. However your post also gave me the idea that we could probably have a temporary link from website to the roadmap section on Wiki until we come up with a proper design for this web page.
Thanks for sharing the information.It is definitely going to help me some time.
Mateusz Haligowski wrote a good summary of the kinds of documentation Pylons needs:
* very general tutorial (like the one on the PylonsHQ)
* expanded tutorials - general tutorial divided into parts, with deeper explanation of what happens
* HOWTOs on most popular tasks - something I'm really missing on Pylons. I still can't do a good user system at my application
* Up-to-version screencasts - they are lovely indeed, provided that they consider the current version.