Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration directives at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
[0] http://wiki.phpmyadmin.net/pma/Config
On 19/04/12 22:27, Marc Delisle wrote:
Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration directives at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
I agree, but we need to merge the two first. The wiki, for example, seems to contain some information about in which version the value for a particular variable has changed.
Bye, Rouslan
On Apr 19, 2012, at 4:33 PM, Rouslan Placella rouslan@placella.com wrote:
On 19/04/12 22:27, Marc Delisle wrote:
Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration directives at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
I agree, but we need to merge the two first. The wiki, for example, seems to contain some information about in which version the value for a particular variable has changed.
Bye, Rouslan
While there is some extra information in the wiki, I don't know that tracking when something changed needs to be maintained painstakingly in Documentation.html. As I recall, adding that to the wiki was a workaround to deal with the fact that Documentation.html is always targeted at a specific release version. The wiki had to deal gracefully with multiple, and sometimes conflicting, configuration values. I'm all for merging the two; I try to keep the wiki updated from time to time but obviously that falls apart when I'm too busy.
I personally feel that documentation of configuration changes belongs in the release notes rather than Documentation.html, but I'm pretty sure whatever solution you all find will be great.
Thanks
Kind regards, Dieter Adriaenssens. Op 20 apr. 2012 00:13 schreef "Isaac Bennetch" bennetch@gmail.com het volgende:
On Apr 19, 2012, at 4:33 PM, Rouslan Placella rouslan@placella.com
wrote:
On 19/04/12 22:27, Marc Delisle wrote:
Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration
directives
at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
I agree, but we need to merge the two first. The wiki, for example, seems to contain some information about in which version the value for a particular variable has changed.
Bye, Rouslan
While there is some extra information in the wiki, I don't know that
tracking when something changed needs to be maintained painstakingly in Documentation.html. As I recall, adding that to the wiki was a workaround to deal with the fact that Documentation.html is always targeted at a specific release version. The wiki had to deal gracefully with multiple, and sometimes conflicting, configuration values. I'm all for merging the two; I try to keep the wiki updated from time to time but obviously that falls apart when I'm too busy.
I personally feel that documentation of configuration changes belongs in
the release notes rather than Documentation.html, but I'm pretty sure whatever solution you all find will be great.
FYI : there is a third place where information/documentation about the configuration options can be found, i.e. the libraries\config.Inc.php
Thanks
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
Le 2012-04-22 09:23, Dieter Adriaenssens a écrit :
Kind regards, Dieter Adriaenssens. Op 20 apr. 2012 00:13 schreef "Isaac Bennetch" bennetch@gmail.com het volgende:
On Apr 19, 2012, at 4:33 PM, Rouslan Placella rouslan@placella.com
wrote:
On 19/04/12 22:27, Marc Delisle wrote:
Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration
directives
at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
I agree, but we need to merge the two first. The wiki, for example, seems to contain some information about in which version the value for a particular variable has changed.
Bye, Rouslan
While there is some extra information in the wiki, I don't know that
tracking when something changed needs to be maintained painstakingly in Documentation.html. As I recall, adding that to the wiki was a workaround to deal with the fact that Documentation.html is always targeted at a specific release version. The wiki had to deal gracefully with multiple, and sometimes conflicting, configuration values. I'm all for merging the two; I try to keep the wiki updated from time to time but obviously that falls apart when I'm too busy.
I personally feel that documentation of configuration changes belongs in
the release notes rather than Documentation.html, but I'm pretty sure whatever solution you all find will be great.
FYI : there is a third place where information/documentation about the configuration options can be found, i.e. the libraries\config.Inc.php
Dieter, you probably mean libraries/config.default.php.
Op 23 april 2012 18:52 heeft Marc Delisle marc@infomarc.info het volgende geschreven:
Le 2012-04-22 09:23, Dieter Adriaenssens a écrit :
Kind regards, Dieter Adriaenssens. Op 20 apr. 2012 00:13 schreef "Isaac Bennetch" bennetch@gmail.com het volgende:
On Apr 19, 2012, at 4:33 PM, Rouslan Placella rouslan@placella.com
wrote:
On 19/04/12 22:27, Marc Delisle wrote:
Hi, I realize that we should have discussed this at the last team meeting but I just remembered this issue.
I find it difficult and error-prone to document configuration
directives
at two places: Documentation.html and the wiki [0].
My suggestion is to remove it from the wiki.
I agree, but we need to merge the two first. The wiki, for example, seems to contain some information about in which version the value for a particular variable has changed.
Bye, Rouslan
While there is some extra information in the wiki, I don't know that
tracking when something changed needs to be maintained painstakingly in Documentation.html. As I recall, adding that to the wiki was a workaround to deal with the fact that Documentation.html is always targeted at a specific release version. The wiki had to deal gracefully with multiple, and sometimes conflicting, configuration values. I'm all for merging the two; I try to keep the wiki updated from time to time but obviously that falls apart when I'm too busy.
I personally feel that documentation of configuration changes belongs in
the release notes rather than Documentation.html, but I'm pretty sure whatever solution you all find will be great.
FYI : there is a third place where information/documentation about the configuration options can be found, i.e. the libraries\config.Inc.php
Dieter, you probably mean libraries/config.default.php.
Yes (didn't have pma repo around when writing that comment), and in libraries/config.values.php there is also some information.
Data from these two files could be used to create the documentation.
-
Dieter Adriaenssens -
Isaac Bennetch -
Marc Delisle -
Rouslan Placella