The Wiki doesn't actually require a login, when prompted for a user name you can enter anything, but typically your Wiki name (EricEverman). It's not really authenticated. I don't like the Wiki software very much, but it works on SourceForge so that'll have to do.
----- Original Message ----- From: "Eric Everman" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 02, 2002 1:58 PM Subject: Re: [Tapestry-developer] Volume vs. Work Load vs. Life > Howard- > > Your time responding to questions is very much appreciated-- thank you very > much for your responses. > > One reason why people (like myself) end up sending mail directly to you is > that this list uses the 'Reply to All' convention. If I want to send email > to this list, I usually scan my back email for the correct > address. "[EMAIL PROTECTED]" is very close to > "[EMAIL PROTECTED]" and its easily possible to grab > the wrong one. Is there a reason why we use reply to all? It also > generates 2x the mail for people involved in a discussion. > > On a related note: I would like to participate in the Wiki, but I am > unable to login and there doesn't seem to be a page to create a new > login. Am I missing something? > > Thanks, > > Eric Everman > > > At 11/2/2002, Howard M. Lewis Ship wrote: > >It's nice to see that the volume of list is increasing. It's also really > >great to see the other Tapestry committers in there and answering > >questions at all levels. > > > >I've just been noticing that my backlog of messages is getting larger and > >larger. I try really hard to answer as many questions as possible, but > >its turning into a losing battle. > > > >These aren't official rules or guidelines (we didn't vote on them :-) ), > >they are my personal considerations. > > > >First off, don't send mail just to me, always send it to the group. > > > >If you are having a problem with Tapestry, provide details! Don't say "I > >did this and it failed". What is "failed"? Provide more details off the > >bat for a faster response ... especially stack traces and other details > >from the exception report. More information is rarely a problem. Source > >code is usually helpful as well. Basically, if we have to get in a long > >dialog to extract the information from you, it may not happen ... we'd all > >rather be coding! > > > >If you've posted a question and gotten no response, try reposting with > >more description and detail. Posting "My form broke" may not get a > >response, but a detailed question about how, on submit, the form submit > >operations didn't occur in the way you would have expected (for example), > >may get a fast response instead of none at all. > > > >Also, any mail sent to me about Tapestry is likely to get a response CC'ed > >to the list unless YOU EXPLICITLY SAY NOT TO. > > > >---- > >Howard Lewis Ship > ><mailto:hlship@;attbi.com>[EMAIL PROTECTED] > >http://tapestry.sf.net > > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
