Hi Adam.
On 22/05/2014 03:06 πμ, Adam Wulkiewicz wrote:
2014-05-21 12:51 GMT+02:00 Adam Wulkiewicz <adam.wulkiewicz@gmail.com>:
Hi,
Barend Gehrels wrote:Thanks for the suggestion. I fixed it (and other minor things).
This is a (very clear) technical description. I think we should add one or two things in the section "Modify the branch":
It now contains "At this point it's up to you what to do with your new branch." which is fine.
But I think we should add some hint that if people create a new feature, or a bugfix, or some parts for the docs, or an example, it is often wise to consult the mailing list if that is a good idea. Maybe other people are working on the same thing too. If it is a larger feature it is good to post a sort of implementation plan to check if the feature, and the implementation, is what is expected.
Good idea, however for now the guidelines are only in the QBK form, right?
Also we should refer to the coding guidelines.
We could think about moving them to the Wiki (or duplicate and keep in both places).
In the last code snippet, I would also add the DOXYGEN_NO_* macros.