We don't have any standards at my company, but we're small. We've tried all sorts of documentation systems such as wikis, READMEs, CVS comments, bug tracker and nothing has worked as well as blogging about it. It's not really a standard (answer to your question) but if you skip the strict rules of standards and just ask production people to blog about it, then you'll easily build up a wealth of information that is sort- and searchable to help anybody get involved in a project.
For bug tracking we use issuetrackerproduct which is great too for making sure the communication between various parts (client and production team) happens in a consistent standardised manner.
A downside of being a web developer is the amount of crap you have to deal with because of IE. If MS is going to focus more on AJAX, they'll have to produce a better web browser for their OS users. Won't this then mean that we web developers get better tools which takes us further away from using the operating system more.
Ha ha haaa!! Yes, you are becoming a laughingstock!
I wonder how many million dollars are lost in potential revenues from pharmaceutical and other biology natural science enterprises who will not steer away from Kansas.
I would of course recommend the http://www.issuetrackerproduct.com/ which is Open Source and thus free. The advantage with the IssueTrackerProduct is that it's written with focus on usability and simiplicity. If it's too complicated, like many of the above mentioned are, people stop using it and go back to making spreadsheets or todo lists in Word.
The IssueTrackerProduct requires a simple installation of the Zope server which you can run either on it's own or fronted by an apache.
One tremendous advantage is that it's written in Python (unlike VBScript like for Fogbugs) with storage in a object database that is really easy to work with in your custom applications/reports.
My company runs 48 instances of the IssueTrackerProduct for about 30 people.
IssueTrackerProduct is your best bet if you want something that is easy to use. Supports POP3 inbound requests and does not require any of the below:
PhD in formfilling
Every user to be logged in
Lots of time
The IssueTrackerProduct has been developed from real users demands only. No cool and excessive feature overload. Plain, slick and simple.
(built around Zope which you'll need to install)
Of course it's Open Source. Check out the screenshots
Slashdot Mirror
I've blogged about it here:
http://www.peterbe.com/plog/pandora
We don't have any standards at my company, but we're small. We've tried all sorts of documentation systems such as wikis, READMEs, CVS comments, bug tracker and nothing has worked as well as blogging about it. It's not really a standard (answer to your question) but if you skip the strict rules of standards and just ask production people to blog about it, then you'll easily build up a wealth of information that is sort- and searchable to help anybody get involved in a project. For bug tracking we use issuetrackerproduct which is great too for making sure the communication between various parts (client and production team) happens in a consistent standardised manner.
A downside of being a web developer is the amount of crap you have to deal with because of IE. If MS is going to focus more on AJAX, they'll have to produce a better web browser for their OS users. Won't this then mean that we web developers get better tools which takes us further away from using the operating system more.
Ha ha haaa!! Yes, you are becoming a laughingstock!
I wonder how many million dollars are lost in potential revenues from pharmaceutical and other biology natural science enterprises who will not steer away from Kansas.
I would of course recommend the http://www.issuetrackerproduct.com/ which is Open Source and thus free. The advantage with the IssueTrackerProduct is that it's written with focus on usability and simiplicity. If it's too complicated, like many of the above mentioned are, people stop using it and go back to making spreadsheets or todo lists in Word.
The IssueTrackerProduct requires a simple installation of the Zope server which you can run either on it's own or fronted by an apache.
One tremendous advantage is that it's written in Python (unlike VBScript like for Fogbugs) with storage in a object database that is really easy to work with in your custom applications/reports.
My company runs 48 instances of the IssueTrackerProduct for about 30 people.
- PhD in formfilling
- Every user to be logged in
- Lots of time
The IssueTrackerProduct has been developed from real users demands only. No cool and excessive feature overload. Plain, slick and simple. (built around Zope which you'll need to install) Of course it's Open Source.Check out the screenshots