--- xml/htdocs/proj/en/glep/glep-0012.html 2003/08/11 14:35:04 1.1 +++ xml/htdocs/proj/en/glep/glep-0012.html 2004/01/31 21:56:55 1.2 @@ -39,7 +39,7 @@
Information about Gentoo development is already significantly fragmented. +Although this GLEP has its merits, the fact that it is a separate source +of information, rather than simply another conduit to existing sources +of information, poses more problems than it solves. Were this GLEP to +be resubmitted/modified so that finger was nothing more than an interface +into existing sources of information, it would probably be accepted.+
The finger protocol is documented in rfc742  and rfc1196 , a simple protocol that returns a human readable report about a particular user of the system. Typically, the information returned will be details such as @@ -84,7 +94,7 @@ clients for those that dont.
Gentoo developers are already aware of the importance of User Relations  .
It is essential to keep the community up to date with current goals, status updates, and information from the development team. Currently it is suggested @@ -118,7 +128,7 @@ key easily obtainable will allow reporters to encrypt their reports.
Providing a finger daemon will allow users to instantly access information on developers, and all details of that developers current projects that they decide to share.@@ -145,7 +155,7 @@
Some admins are concerned about the security of running a finger daemon on their machines, the class of security issues involved with the finger protocol are commonly referred to as "information leaks" .@@ -163,7 +173,7 @@
Adding data to a plan is a lot simpler than updating webpages.
Should a user want information about the author, this might be the output of a finger query:
@@ -197,7 +207,7 @@