Reply to thread

Message

<blockquote data-quote="chefkoch" data-source="post: 1020267" data-attributes="member: 10438">It would be great if we could collect and document these information well structured within the wiki for a few reasons:<ul>
<li data-xf-list-type="ul">It documents already the default views/filters for the end user.</li>
<li data-xf-list-type="ul">It documents the default and expected behavior, which helps testing and confirming the implementation is working as it is intended.</li>
<li data-xf-list-type="ul">While it is written down in wiki or read by others we might find improvements or glitches.</li>
<li data-xf-list-type="ul">It is easier for the developer to implement it as it is kind of a check / todo lists.</li>
<li data-xf-list-type="ul">It is already documented for future developments and improvements so the existing structure / overview in wiki can be reused and extended with new views / definitions without writing down the basics again when this post is already treated out of date and old.</li>
<li data-xf-list-type="ul">Since layout and content in wiki can be improved by everyone, it is also a great base for a blog or can even be referenced or included in the release news.</li>
</ul>There might be other reasons for it, the only one against it is: It takes &quot;time&quot; and efforts to copy it over and maybe revise and improve the layout from time to time. I might have requested a documentation about it already a few times in other threads where this feature/improvement has been discussed already.&nbsp;IMO it is a requirement to document it before applying and shipping it within a release. The times when we were able to argue that we are not enough people working/focusing on MP2 are gone, so we should improve documentation with implementing new stuff.</blockquote>

[QUOTE="chefkoch, post: 1020267, member: 10438"] It would be great if we could collect and document these information well structured within the wiki for a few reasons: [LIST] [*]It documents already the default views/filters for the end user. [*]It documents the default and expected behavior, which helps testing and confirming the implementation is working as it is intended. [*]While it is written down in wiki or read by others we might find improvements or glitches. [*]It is easier for the developer to implement it as it is kind of a check / todo lists. [*]It is already documented for future developments and improvements so the existing structure / overview in wiki can be reused and extended with new views / definitions without writing down the basics again when [B]this post is already treated out of date[/B] and old. [*]Since layout and content in wiki can be improved by everyone, it is also a great base for a blog or can even be referenced or included in the release news. [/LIST] There might be other reasons for it, the only one against it is: It takes "time" and efforts to copy it over and maybe revise and improve the layout from time to time. I might have requested a documentation about it already a few times in other threads where this feature/improvement has been discussed already. IMO it is a [COLOR=#ff0000][B]requirement [/B][/COLOR]to document it before applying and shipping it within a release. The times when we were able to argue that we are not enough people working/focusing on MP2 are gone, so we should improve documentation with implementing new stuff. [/QUOTE]

Verification