[Ktechlab-devel] Forums

[Alan Grimes]

-1.

I hate forums.
they suck.
There does not appear to be a time-efficient way to use forums and they
require you to manage yet another login account. I've chosen to try to
resist such accounts, cuz I have a hundred more accounts than I can
actually manage right now.

Mailing lists, on the other hand, are supremely efficient. You log in
once to set it up and then forget about it. The list manager will almost
always honor a command issued from your own e-mail address. What you
need to know gets handed to you immediately and you never have to reload
a page to see if someone's posted anything. You can deal with mailing
lists using any piece of software you wish. I've signed up for mailing
lists more than a decade ago and they've only required a minute or two
to update e-mail addresses once in a blue moon. Using mailing lists (for
long term use) is so effortless that I can't fathom why anyone would
ever bother setting up a form. I'm probably on more than a hundred lists
right now and I don't even have to think about it.


Juan De Vincenzo wrote:
> +1 here.
> 
> A forum would be a great place to also gain new devs/users.
> 
> On Tue, Feb 3, 2009 at 12:17 AM, Michael T. <mickljosapth at gmail.com> wrote:
>> Hi Lawrence,
>>
>> I think the forums are very needed on the site even if some / many
>> developers  may prefer otherwise.  I think from a user perspective a forum
>> is "cozy" to the end user. I know from what has already been discussed,
>> additionally my own feelings both forms of communication has inadequacies
>> one way or the other.   So to satisfy  to some degree I think mailing lists
>> and forums can coexist.  The hard part will be the moderation as the user
>> base grows. It might be a  friendly place right now with not too many
>> people. But once more and more join it can become reckless but still not
>> like forums disappeared from the www.  Another suggestion that I think is
>> really needed from the start is a Roles module. Before the project had time
>> to expand or it will become spaghetti.  Remember what you seen on my  site
>> as "Management" ? I think you should create something like that. So it will
>> be a directory of  various parts of the project. It is vital can't stress it
>> enough really important. For one  team to be able to communicate very well
>> with the other.  So a ready base  grouped  into each field would be nice.
>> Otherwise   just example: Picture    the simulator  performing a simulation
>> at the same time  half of the form is cutoff. Because the Coder did not
>> agree upon some aspect with the gui designer. This is just an example of
>> course, it probably would not come down to this.  Or lets say suddenly a
>> script on the main site broke, the user needs to contact the "Web master(s)"
>>   not "Coders" or "GUI" designers   Who really might not (should not even
>> care about the web sites  workings)  want to be bothered.  They go to the
>> section Webmaster and pick one, ok  he / she is out of town on vacation.
>> They select the assistent Web master who will be able to fix the problem.



-- 
New president: Here we go again...
Chemistry.com: A total rip-off.
Powers are not rights.