Repository navigation
Replies: 2 comments 1 reply
|
Thanks for offering to contribute! As far as I know, we don't have a comprehensive SRS. I'm hesitant to introduce one without a clear need, as it would become another document to maintain. I think improving our existing documentation would be more useful, including the user manual, source code comments, and developer documentation. For example, we could revisit Doxygen documentation generation, which was set up previously. We already have developer and translator documentation, such as I'd prefer to focus on improving these existing resources and documenting specific requirements only where there is a clear need. Thanks again for your interest in improving WinMerge's documentation! |
|
Thanks for the quick and clear answer, and for confirming that no comprehensive SRS exists. I'll base it on the user manual, the developer documentation and the application itself, and I'll only come back here with specific questions where the existing documentation is unclear. Thanks also for pointing me to the existing docs. |
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
I'd like to contribute by writing a Software Requirements Specification (SRS) for the project: a document that describes what WinMerge is expected to do (functional and non-functional requirements, supported platforms, user roles and use cases), based on the user manual, the developer documentation and the application itself.
I looked through the Docs folder, the wiki and the repository search, but I couldn't find anything like this. Before I start, could you let me know:
I'd also be happy to ask follow-up questions here if some behaviours are unclear from the manual.
Thanks
All reactions