On Sunday, February 19, 2012 08:35:34 AM Jeff Epler did opine:

> In the board's original announcement of the rebranding of the
> project as LinuxCNC, we mentioned a future renaming of the
> SourceForge project, so that our mailing lists would be under the
> LinuxCNC name.  However, the board has not yet filed this renaming
> request with sourceforge.net.  Instead, we are soliciting community
> input on the future of our mailing list and bug tracking system.
> 
> The board sees two possible options:
>  * Keep mailing lists and bug trackers hosted at sourceforge but
>    under a new group name.  Advantages of this choice include that
>    most maintenance is done by sourceforge.net administrators.
>    Disadvantages include the relatively feature-poor bug tracker and
>    the ads displayed on all mailing list messages and project pages.
>    Also, some disruption is expected in the course of the sf.net
>    project renaming process.  It is possible that some information
>    will be lost during the rename process.
> 
>  * Administer our own mailing lists and bug tracker, eventually
>    closing the sourceforge project.  Advantages of this choice
>    include a more powerful bug tracker (probably bugzilla), ad-free
>    mailing lists and project pages, and the possibility of an
>    overlap period of sf.net and self-hosted services.  Disadvantages
>    of this choice include greater administration requirements and
>    the need for users to create new accounts with the new services.
>    Furthermore, it is unclear whether it will be possible to migrate
>    data from the sf.net tracker to a self-hosted tracker, though the
>    board will investigate this matter further.  If we choose this
>    option, the board accepts the ongoing work of hosting these
>    services.  There are no extra monetary costs anticipated for
>    self-hosting these services.
> 
> Ideally, this discussion will result in a clear consensus of the
> community.  If there is not a clear consensus, the board will take
> into account community comments and make a decision by vote but not
> before March 5.
> 
> Yours,
> The LinuxCNC board of directors
 
While I find the adv's appended to our messages are often of zero interest 
to us, and therefore noise, they are a way for sourceforge to pay the 
bills.

Having it hosted at sourceforge.net would seem to offer advantages in terms 
of the lists security, its been quite a while since I've seen a 'spam' or 
'phishing' message make it through the server.  I am on a python mailing 
list that also has a gated link to google.groups and the spam level there 
is probably 25% of the messages I get despite the fact that I have some 
procmail poison sending 75% of that to /dev/null.

I would assume that maintenance time, keeping up with the latest methods to 
achieve that level of security would require a pretty dedicated effort to 
achieve that same level by ourselves.

The sourceforge.net servers generally have decent latency and BIG pipes.  I 
often get my posts back as echos from their server in my next fetchmail 
scan, a maximum of 3 minutes away.  I am on one or two lists where this is 
pretty variable, and I may not see the echo of my posts for 2 or 3 hours.

So I guess this is my half hearted vote to just rename the existing list, 
with perhaps a signature based instruction about the upcoming rename that 
it will be dual named for a few days so that we all have time to modify our 
email agents login string to post, and a corresponding dual filtering in 
our receive filtering so we don't miss anything.  It seems like a weeks 
notice would be a great plenty for most of us to make the changes on our 
end, with perhaps a month for folks like Kent who might have a health 
problem they have no control over, and who have higher priorities involved 
with their wives.

As for bugzilla, my battles with it are legendary in my own mind but I must 
admit the user interface has been improved to where its tolerable, but it 
has taken bugzilla a decade to get there.  But it still seems designed to 
make bug reporting 10 times harder than it should be.  It cannot for 
instance, be used to report a problem where the only data you have is the 2 
minute to half a day gap in the system logs between a normally logged 
event, and the logging daemons restart notice on the next line of the log.

That however, seems like another, different critter to me and I wasn't 
aware they were even linked.

In the boardroom, I know you folks will do what you think is best for 
LinuxCNC, so thats my $0.02 on it.

Cheers, Gene
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
My web page: <http://coyoteden.dyndns-free.com:85/gene>
The difference between America and England is that the English think 100
miles is a long distance and the Americans think 100 years is a long time.

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users

Reply via email to