If you are unfamiliar with reporting bugs, here is a useful [Guide for effective bug reports] - this really helps developers to reproduce and isolate a problem. |
To see the list of existing bug reports, click [here].
The most useful bug reports (and the ones most likely to get quick results), are ones that describe in as much detail as possible what happens, and under what conditions. You should include information about your system, what RTOS you are using, etc. Describe the conditions that lead to the bug, what the program did, and what you think it should have done. Errors in documentation should be reported the same way - describe what the doc says, and what you think it should say. Indicate whether it is simply unclear, or if it doesn't match the actual behavior of the program.
If possible, you should register with SourceForge and log in before submitting a bug report. That will allow us to keep you informed about the progress of your report, or contact you for more information. To register, click [here]. If it is impossible or impractical for you to register, you can still submit a bug report. However anonymous reports are harder for us to act on and may get a lower priority.
If you are unfamiliar with reporting bugs, here is a useful [Guide for effective bug reports] - this really helps developers to reproduce and isolate a problem.
To submit a bug report, click [here].
The Enhanced Machine Controller design process is open to ensure a system that reflects the needs of the user community. Listening to the needs of users and developers ensures that valuable suggestions for improvement can flow into project. As you consider submitting a feature request, toss it about a bit with others on the EMC lists so that your request comes to the Board ready for them to set priority and assign people.
You must register with SourceForge and log in before submitting a feature request. That will allow us to keep you informed about the progress of your request, and contact you if we need more information. To register, click [here].
To submit a feature request, click [here].
Priorities are assigned to each tracker item by the EMC board of directors. The priority of an item indicates how important it is to the overall project, and each developer should ideally work on the highest priority item that they feel capable of handling. (Although there is nothing wrong with fixing some low priority items if you don't have the time or energy to tackle something big.)
The following list is a combination of the existing categories and some proposals. (Currently there is only one category for all EMC1 items.) This list is subject to change.
EMC1 related categories
EMC2 related catagories