Hi,
Wow, that's quite the list. I'll try and answer some of your points briefly:
1. Links SQL will move towards encrypted passwords. Gossamer Mail won't as they are often required for authentication via POP server (where the password must be sent in plain text due to the POP3 protocol).
2. The lost password options depend on how the passwords are stored. Community will provide a central login/signup/lost password features for all products.
3,4: We are constantly looking at how to improve the admin layout to make it more user friendly. One of the things we are exploring is removing the framed interface, and also moving the admin into the user side.
5: We may look at framing things with a top level admin, but I don't see us doing any tighter integration then that.
6: Doubtful we will do this, as a library change could break older products and may slow down releases of updates until all products have been updated (as then you couldn't install the latest Gossamer Forum until we came out with a Links SQL upgrade for instance).
7. I think you mean files, not modules, as the modules are all named separately (and have to be so things can live happily under mod_perl).
10: Common represents a template set that other template sets inherit from and is different then default.
11,12: Paul answered these pretty well.
14: You can change this after you install. Currently the installed checks to make sure the fileman directory is writeable.
15: No, it wouldn't work. Gossamer Forum installer does not give you the option for a separate admin path. If you do it manually, then it's going to make upgrades quite hard.
16: This is an issue with MySQL. The LOAD DATA/SELECT INTO work only with a file on the SQL server.
18: This is needed only in Links SQL, not in the others (required for the parallel link checker to work on windows)
19: Same as 5
20: The tables have been designed (especially in the case of Gossamer Forum), for maximum performance. I don't see why anyone familiar with SQL would not have an easy time pulling user information out of the database. The MailArc plugin has a simple example of how to add a user from another program.
21: Community will provide a solution to this.
22: Different products have different needs for what path's and URL's they ask for.
25: We will be offering a solution for this soon.
Cheers,
Alex
--
Gossamer Threads Inc.
Wow, that's quite the list. I'll try and answer some of your points briefly:
1. Links SQL will move towards encrypted passwords. Gossamer Mail won't as they are often required for authentication via POP server (where the password must be sent in plain text due to the POP3 protocol).
2. The lost password options depend on how the passwords are stored. Community will provide a central login/signup/lost password features for all products.
3,4: We are constantly looking at how to improve the admin layout to make it more user friendly. One of the things we are exploring is removing the framed interface, and also moving the admin into the user side.
5: We may look at framing things with a top level admin, but I don't see us doing any tighter integration then that.
6: Doubtful we will do this, as a library change could break older products and may slow down releases of updates until all products have been updated (as then you couldn't install the latest Gossamer Forum until we came out with a Links SQL upgrade for instance).
7. I think you mean files, not modules, as the modules are all named separately (and have to be so things can live happily under mod_perl).
10: Common represents a template set that other template sets inherit from and is different then default.
11,12: Paul answered these pretty well.
14: You can change this after you install. Currently the installed checks to make sure the fileman directory is writeable.
15: No, it wouldn't work. Gossamer Forum installer does not give you the option for a separate admin path. If you do it manually, then it's going to make upgrades quite hard.
16: This is an issue with MySQL. The LOAD DATA/SELECT INTO work only with a file on the SQL server.
18: This is needed only in Links SQL, not in the others (required for the parallel link checker to work on windows)
19: Same as 5
20: The tables have been designed (especially in the case of Gossamer Forum), for maximum performance. I don't see why anyone familiar with SQL would not have an easy time pulling user information out of the database. The MailArc plugin has a simple example of how to add a user from another program.
21: Community will provide a solution to this.
22: Different products have different needs for what path's and URL's they ask for.
25: We will be offering a solution for this soon.
Cheers,
Alex
--
Gossamer Threads Inc.
