I like the idea with this documents this is very good. Regarding the gaols I would rephrase "Learnloop should be quite simple to administrate" to something like:
Learnloop should have a user interface where the administrator could perform administrative tasks. It must be clearer.
I would also add something about backwards capability. I think it's important that we supply tools for upgrading between versions.
I like the idea with a global change log. But regarding comments in the changed files I would recommend that we use the possibility that CVS has of adding comments when we do an upload instead.
That will keep the source cleaner and could easily be seen in the CVS repository.
But we should comment the source that will help to understand.
I also think we should say something about realistic time to react... ? What do we mean? My recommendation would be 1 week.
We should also think of what software releases we should support i.e. php3 and 4 or only php4, browsers. And what do we have a possibility to test ?
My environment consists of php4 (4.1.0), apache (1.3.23), mysql (3.23.48), ie 5.5 - 6.0, mozilla 0.9.8.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some thoughts:
I think we should set the server-requirement to a minimum. Ie: php don't need to be compiled with gettext or anything similar.
For LL2 I think we should require php 4.1 and with register_globals off. This allows us to use th $_GET and $_POST and thereby tightens the security.
The only browser that I don't think we should support is the old netscape 4.x because of compability-issues with DHTML. The browsers that we should support and test everything in should be IE5+ , Opera and Mozilla on both Windows and Macintosh (since mac is used alot in schools).
The only requirement on webserver is that php is run as a module so the header-commands can be used.
MySQL-requirements should also be set to 3.23 (3.22 has some irritating bugs)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tried to write down some goals and developing policys. Read and give your comments!
(My english are not so good and I glad to get your language corrections too...)
http://ullvitorget.koping.se/~EIB/gestur/developing_policy.pdf
I like the idea with this documents this is very good. Regarding the gaols I would rephrase "Learnloop should be quite simple to administrate" to something like:
Learnloop should have a user interface where the administrator could perform administrative tasks. It must be clearer.
I would also add something about backwards capability. I think it's important that we supply tools for upgrading between versions.
I like the idea with a global change log. But regarding comments in the changed files I would recommend that we use the possibility that CVS has of adding comments when we do an upload instead.
That will keep the source cleaner and could easily be seen in the CVS repository.
But we should comment the source that will help to understand.
I also think we should say something about realistic time to react... ? What do we mean? My recommendation would be 1 week.
We should also think of what software releases we should support i.e. php3 and 4 or only php4, browsers. And what do we have a possibility to test ?
My environment consists of php4 (4.1.0), apache (1.3.23), mysql (3.23.48), ie 5.5 - 6.0, mozilla 0.9.8.
Some thoughts:
I think we should set the server-requirement to a minimum. Ie: php don't need to be compiled with gettext or anything similar.
For LL2 I think we should require php 4.1 and with register_globals off. This allows us to use th $_GET and $_POST and thereby tightens the security.
The only browser that I don't think we should support is the old netscape 4.x because of compability-issues with DHTML. The browsers that we should support and test everything in should be IE5+ , Opera and Mozilla on both Windows and Macintosh (since mac is used alot in schools).
The only requirement on webserver is that php is run as a module so the header-commands can be used.
MySQL-requirements should also be set to 3.23 (3.22 has some irritating bugs)
Cant we add this in the document section ?