Michael, You have identified an important issue. Please see my comments below:
Michael wrote: "About the todo list, we may have to choose a central place. There are some todo lists on the wiki, there is the sourceforge feature request, the sourceforge bug report and now here... What others think ?" I think it is important to make distinction between a bug report, a feature request, and a programmer's todo. Here is how I imagine things working with our current system and the files that Stefan has set up: [1] We will use the Feature Request log at SourceForge to track user's requests for new or additional features to JUMP. I don't think we should track developer's requests for changes to the code or API in this list. I think this should be for user requests. I'm talking about the "I want to push a button and have this happen" stuff. [2] We will use the Bug Tracker at SourceForge to track bugs. These are problems that generally result from mistakes in the source code. This is not a place to log comments like "I really wished function X would do Y instead of what it does now." That type of comment should be encapsulated in a Feature Request. [3] The todo list that Stefan has set up in the CVS should be used to track improvements or changes that programmers would like to make for the source code. For example, I might be designing a new class or working with an existing class and identify something that would be a great improvement to JUMP's architecture, a way to clarify the source code, or an opoortunity for optimization. But I might not have the time to implement the improvement at that moment. I could add an entry to the todo list for the improvement that I identified. (This would be a great place to start new developers that want to help with OpenJUMP, if we ever get any.) :] Does this make sense to everyone? I'm open to sufggestions for a better system. :] Sascha wrote: "But ones again: Writing a ChangeLog this way is only for the lazy. ChangeLog changes should be checked in each time you do a check in." Agreed. Reading a message generated automatically by the CVS repository or some other tool doesn't tell me a lot about the reasons why you are commiting the changes, or what those changes are. Sascha wrote: "Wikis are not reliable in the long term. It's not working off-line, depends on a internal data base structure not accessible to to user (migration issues)." Agreed. Wikis are great for collaborative documentation efforts, but I think that the text files Stefan has set up in the CVS will work better for logs." The Sunburned Surveyor P.S - Stefan: What is the difference between the Changes file and the ChangeLog files? ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
