While I am sure that you guys are more than capable of running the server outside of Sourceforge, what always concerns me in situations like this is the dependency on certain people to do certain things without a solid backup plan.
If plan A is to have person X run and administer the server, what happens if person X becomes unavailable (let your imagination run wild. ) ? What is plan B? And where does that leave the server/s and all of the people who depend on it. I have to answer this kind of question all of the time for my customers. (And some of them have zero tact, so I frequently get to reflect on my age and health.. ;-) ) I trust you guys will make a good decision. The adds don't bother me. But the possible vulnerabilities do. Thanks for asking for input. :-) Dave On 2/19/2012 10:13 AM, Mark Wendt (Contractor) wrote: > On 2/19/2012 8:23 AM, Jeff Epler wrote: > >> 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 >> >> > If it's feasible, I would lean towards option two. I'm a system and > network administrator in my daytime job, and I'd definitely volunteer to > help with the changeover, and ongoing maintenance of our "stuff." I > manage several bulletin boards, have run mail servers and mailing lists, > and I'm quite familiar with setting up and configuring web sites, CVS > repositories and lately wiki forums. With all the help I've gotten from > all the folks on this list over the years, it'd be a way for me to help > pay back for all that help and assistance, and I'd be more than happy to > jump in with both feet. > > Mark > > ------------------------------------------------------------------------------ > 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 > > ------------------------------------------------------------------------------ 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
