Changes by last author:
Changed:
| * usually new developers are first involved in new projects, and negotiate some interface for the new developments. New code is audited and integrated by existing developers. Later well cooperating developers can get more involved in the project. |
|
* usually new developers are first involved in new projects, and negotiate some interface for the new developments. New code is audited and integrated by existing developers. Later well cooperating developers can get more involved in the project.
* the detailed plans are necessary so the team can cooperate with the applicant to sort the necessary files/functions for which access is needed for the given task. ** The development team attempts to cooperate. Access to the chosen functions is granted after the development team decides that cooperation is likely to work out. |
| ---- |
|
** [htpasswds CGI via https]
** or [htpasswd cgi via http] - only as very last chance !!! Not a secure (or recommended) way, but anyone on win32 has probably waived bye to security a long ago anyway. Still better than sending cleartext pwd in email (email is logged by too many paries) |
|
** [htpasswds CGI via https] (out of order now).
** Do not send cleartext pwd in email (email is logged by too many parties) |