![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Wed, 20 Dec 2000, Keith Moore wrote: > > We *should* worry about people who come to the IETF once and never come > > back - because they probably came to the wrong meeting, and went home > > unhappy. > > interesting idea. > > so assuming that a lot of folks come to the IETF expecting something > different than it is, and going home disappointed, what can we do to > make future prospective attendees more aware of what they're getting into? Don't make them more aware at all. All the work is done on the mailing lists, yes? Only post information about IETF meet locations etc. to those mailing lists. Do not link to event registration pages from www.ietf.org. If they're not on any mailing list, why would they want to come anyway? L. 'Thirdly, there was often confusion about how to get involved in IETF standards effort, submit requirements, and get delivery commitments.' -- RFC3002 can be quite unintentionally hilarious at times. <L.Wood at surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.