Open Letter to SourceForge
SourceForge staff,
While I had not noticed this at first, it has come to my awareness that VA is now appending advertising to SourceForge project mailing lists. Advertising is certainly nothing new at SourceForge, as there are annoying banner ads, and consequentially for this reason, and because SourceForge is no longer being developed as free software, I have largely withdrawn from using it, except principally to continue hosting pre-existing mailing lists using your "mailman" list server.
However, I find this new use of mailing lists for stealth advertising both unethical and offensive, because they appear as if they were signature lines placed by the original poster. It is neither clear that the advertised products or services are not being endorsed and promoted by the message poster himself, nor is that any better than spamming unsuspecting users with unwanted junk e-mail, which is an equally disgusting practice. It is also perturbing to consider that such lists may be used to advertise proprietary software or potentially other products or services of similarly questionable ethical character.
Certainly I am free as a developer to terminate the use of any remaining services hosted by VA, and under these present intolerable circumstances, I see no choice but to do this. If there is no satisfactory response to this present situation, I am prepared to immediately close these remaining lists and request [that] any current projects I still have shown on SourceForge be de-listed. Fortunately, we do have several lists already available on gnu.org, and it would not take that long to merge the existing SourceForge list memberships into those with fairly minimal disruption. We also have an excellent system in place for free software development using Savannah.
My hope is that VA would reconsider some of it's recent policies and practices. I believe everyone would like to see SourceForge continue to be available and used as a developer community resource. I also fully appreciate the need VA has for finding some revenue model to continue providing SourceForge as a resource. However, I do not believe these specific practices will make this possible.
David SugarGNU Maintainer
Hello David,
I just saw your email(s). I've been on vacation during the past week and the pile of unread emails was sky high when I returned.
About ~45 days ago we started to put 2 line text messages at the bottom of SourceForge.net mailing lists.
As you probably know, running a site with over 3 million page views a day, 300,000 downloaded files a day, 700,000 emails a day, 80 servers, and a staff of people is very expensive.
We are using the email text messages, like many other sites, as a small way to offset some of the costs of running SourceForge.net for the Open Source Community.
Since the inception of these text messages, we have received very few complaints. I think the number is less than 10, which is pretty good considering we send out over 700,000 emails a day.
I think the reason why the complaints are so low is:
A) We told people about it before we did it. It was listed on the site prior to us going live.
B) Every email has the same ad. We change it approx once a week. Anyone getting more then one email can see that the ads are consistent and hence not part of the sig of the user.
C) The ads are not archived with the email when they are stored on the site for others to see on SF.NET. We strip out the ads to cut down on confusion.
D) Two lines of text is very consistent with what other sites are doing. At the bottom of the email it doesn't get in the way of the actual message.
Of the 10 people who have written us so far, you are the first to bring up the "stealth advertising" discussion. I understand what you are saying, but I haven't seen evidence from the feedback we've been getting that users are confused [by] what is an ad and what is a sig. Certainly there is no stealth intent from either us or our advertisers.
One thing we could possibly do is change the top delimiter from dashes to something like "Sponsored by:". It might help. I'll discuss it with the staff.
Thank you for the feedback. If you have any other questions/concerns please feel free to email me.
--Pat
Editors' Note: David Sugar is the leader of the Bayonne Project, and Patrick McGovern is the site director for SourceForge.net. For more information about Savannah, visit the Savannah project web site and read the March 2002 UpFront column in LJ.
email: sugar@gnu.org
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
If you already use virtualized infrastructure, you are well on your way to leveraging the power of the cloud. Virtualization offers the promise of limitless resources, but how do you manage that scalability when your DevOps team doesn’t scale? In today’s hypercompetitive markets, fast results can make a difference between leading the pack vs. obsolescence. Organizations need more benefits from cloud computing than just raw resources. They need agility, flexibility, convenience, ROI, and control.
Stackato private Platform-as-a-Service technology from ActiveState extends your private cloud infrastructure by creating a private PaaS to provide on-demand availability, flexibility, control, and ultimately, faster time-to-market for your enterprise.
Sponsored by ActiveState
| Containers—Not Virtual Machines—Are the Future Cloud | Jun 17, 2013 |
| Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer | Jun 12, 2013 |
| Weechat, Irssi's Little Brother | Jun 11, 2013 |
| One Tail Just Isn't Enough | Jun 07, 2013 |
| Introduction to MapReduce with Hadoop on Linux | Jun 05, 2013 |
| Android's Limits | Jun 04, 2013 |
- Containers—Not Virtual Machines—Are the Future Cloud
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Introduction to MapReduce with Hadoop on Linux
- Senior Perl Developer
- Technical Support Rep
- Weechat, Irssi's Little Brother
- UX Designer
- One Tail Just Isn't Enough
- Android's Limits
- Free is costly
30 min 17 sec ago - Bought photoshop CS5 for developing a website :(
46 min 37 sec ago - Reply to comment | Linux Journal
1 hour 34 min ago - Reply to comment | Linux Journal
1 hour 35 min ago - Replica Watches
3 hours 59 min ago - Reply to comment | Linux Journal
8 hours 10 min ago - on the path to understanding
8 hours 14 min ago - As a fisher,we know that a
1 day 3 hours ago - All I Say Is Worth Share!
1 day 4 hours ago - GeekSays
1 day 5 hours ago
Featured Jobs
| Linux Systems Administrator | Houston and Austin, Texas | Host Gator |
| Senior Perl Developer | Austin, Texas | Host Gator |
| Technical Support Rep | Houston and Austin, Texas | Host Gator |
| UX Designer | Austin, Texas | Host Gator |
| Web & UI Developer (JavaScript & j Query) | Austin, Texas | Host Gator |
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?



Comments
Re: Open Letter to SourceForge
I really couldn't give a toss about this advertising. I just wish I could get onto Sourceforge at all. I dont know whether it is a problem with Sourceforge, with my ISP - nobody there speaks English - or because I am trying to connect from the heart of China. I can get every other site I try except for Sourceforge and Geocities. Both were fine up until a couple of months ago when I left West Africa & my setup is still the same. Any ideas?
Thomas A Johnson
Direct replies welcome - it's bloody boring here ;^(
Thomas@taj.flyer.co.uk
Re: Open Letter to SourceForge
Two lines at the bottom of the email is not a big deal. The excellent services provided by SourceForge are free and for those who want an alternative, Savannah looks too be pretty good too. Hey, if the two lines helps SourceForge out, it doesn't seem right complaining about it.
I doubt it's going to help SourceForge out much though. It must be really expensive running that service and I wonder how much revenue VA has by selling the SourceForge system. Still, I wish them luck. They have done a lot for the LInux community when other businesses wouldn't even look in our direction.
Re: Open Letter to SourceForge
Interesting read. I am a sourceforge user, currently, and while I have seen the ads mentioned, I really didn't pay any attention to it until I saw this article. After reading David's letter to SF, I was sort of thinking "Yeah, that is lame...". But, after reading Patrick's reply, I quickly dismissed that idea. I am involved in web development and help a friend admin a webhosting company and I know there are rather high costs involved in doing this type of business. The signatures (as they have been modified to include the 'sponsored by' text) don't bother me at all. I will be standing by SF on this one. That said, I still don't feel too good about the other changes that took place a while back with regards to closing the sourceforge development...but whatever.