<<< Date Index >>>     <<< Thread Index >>>

Re: about coders, docs and users



=- cga2000 wrote on Tue  5.Sep'06 at 15:39:44 -0400 -=

> > > But it would be a lot more profitable where I am concerned
> > > to adopt one of the ur-users' ways of doing things than
> > > spend countless hours reinventing the wheel.
> > 
> > Righto, see above. But which ur-user should do it?
> 
> ?
> After only a few months on this list it's pretty obvious that
> there are a handful of contributors who seem to fulfill most of
> the requirements.
> { list of more or less required qualities }
> - the ability and the desire to write,
> - As always, availability and motivation are likely a problem ..

Bingo, so my Q remains unanswered: which ur-user should do it?
Or rather: who is left (to meet the latter 2 prerequisites, too)?

> > > > See MuttGuide on wiki, add YOUR ideas to UserGuide. See
> > > > also my agenda on RadoS: the MuttFaq shows what people
> > > > miss and therefore needs better coverage in a guide.
> > > 
> > > At this point my "ideas" are so vague that I don't see the point.
> > 
> > { the wiki way: start small, others join }
> 
> And it turns out the MuttGuide is pretty much the approach that
> I had in mind. Although I switched to mutt only 3-4 months ago I
> just did not find the MuttGuide/Wiki at that time.
> Possibly because I had looked into switching in the past when
> this framework did not exist and therefore was not looking for
> it when I did switch ..

The wiki itself exists for 2y+(?), but even now the MuttGuide
looks different than it looked some months ago.

> I realize the project is in its early stages but all the same,
> at some point in the future, the www.mutt.org page should have a
> reference to this ambitious documentation project somewhere
> right near the top

Come on, don't be so evasive, let's keep the talk about the future
in the future, and add your ideas to UserGuide for the "ur-users"
to pick them up to convert them into the MuttGuide, _NOW_! :)

> .. A short paragraph under "latest news" perhaps would both
> ensure that potential new users would not miss it and make a
> statement to the effect that a new documentation project
> deserves the same recognition as new releases .. major
> patches .. etc.

Heh, I know you're aware of the 'Call for Votes' for the
ManualVarNames project and other offers (by me and others
regarding docs. You see how much docs support is valued compared
to other things. ;)
 Maybe once Thomas finds the time to fairly deal with it this can
be changed. Thomas, say when?! :)

> A good deal of criticism focused on mutt not providing MRA/MTA
> functionality {...}

Just a matter of better docs.

> So maybe the Mutt Guide needs to look beyond mutt at the typical
> full-blown mail setup in an introductory chapter explaining how
> it's done and more importantly why it is worth going to a bit
> more trouble rather than emulating the Microsoft Outlook model.

MailConcept is meant to cover that (have a look), as well as the
/Send and /Receive sections (to be filled).
If you miss anything, be more specific, add it to UserGuide in the
content section.

> Naturally, it is possible to do basic testing by sending mail to
> yourself.  {...}

Indeed, this hasn't been covered at all yet, add to UserGuide.

> { why mutt is so much superior to GUI MUAs in contrast to the
> initial impression people might get that it's inferior because
> not being GUI. }

I thought that was already covered on the homepage.

> So maybe it is time for a little bit of advocacy .. showing mutt in
> action .. with plenty of screenshots just to show new users that with
> 256 colors to choose from mutt can also look rather kewl ...

Ehm, this is already there, see ConfigList.
Feel invited to add yourself.
Uhm, and it needs no 256 colors to look cool.
(being a "keep it simple" advocate :)

> I can only judge by the contributors to this list but there are
> also a few knowledgeable users here who are always extremely
> helpful and ready to share their knowledge with the neophyte.
> No matter how trivial the issue. 

Aye, if only all this could be compiled into the guide rather than
being repeated all over again each time.



When I was in the beginning of the ManualVarNames project, I was
told "talk is cheap". That's so true.
 Please do something about what you're missing, see my sig! :)

Maybe it would help if we posted a RecentChanges summary (weekly?)
so people get more aware of it (much like the changes notice for
the code in CVS)?!

-- 
© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.