Hello Paul,
Paul Selormey <paul@...> wrote:
PS> Hello,
>> I've contemplated moving the list for more than six months. It makes
PS> since to
>> have it with the web site. And the move of the flashing banners to the
PS> top of
>> the mail just aggrevates me enough to finally do it.
PS> Since you are not the only one using the list, is it not better to ask how
PS> others
PS> feel about it?
PS> The flexibility eGroups offers makes me like it, banners or not. After all,
PS> they
PS> need to survive too, and pay their bills.
Just to make point more clear: Earnie Boyd and Dale Handerson are
"owners" (in eGroups terms) of current maillist. They are persons in
position to start such move. Decision to do the relocation of list to
sourceforge was made by current admins of Mingw project, see
http://sourceforge.net/mingw/ for who's who. Since relocation will be
transparent for subscribers, I see no grounds for discontent.
As for eGroups, it does great job for allowing people easily start
their discussion forums, and we used their services for a long time
with appreciation. However, now we are reaching the new level and
having more freedom and control (that's what SourceForge gives) will
be benificial.
For last, about features SF maillist will have. List will be run
by GNU Mailman. It offers all usual majordomo capabilities, such as
immediate/digested delivery, pause, etc. What it does not offer (at least
AFAIK) is web-based access (to list's messages, I mean). However,
that's not problem since list will archived by www.geocrawler.com . The
latter should have web-posting ability too, I believe.
So, there's hardly be any feature lacking with new maillist, and
most people probably simply won't notice movement at all ;-)
Last note about Mingw project itself: its our project, and won't
run without our own attention. So, everyone is welcome. If you have
some ideas how to make Mingw live and develop, and going to spend time
on this, send mail to Earnie Boyd or just post here (well, there - to
new maillist ;-) ). Even if you just spotted bug or made little patch
which allowed for more smooth compilation, please consider spending
couple of minutes to post it in appropriate project section at SF (Well,
to be precise, we didn't discussed precise bug/patch flow procedure,
so any comments welcome).
PS> Regards,
PS> Paul.
--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135