Re: Leaving SF (was: SF ticket regressions)

Is SF all that bad?   I just answered one of the privoxy support
requests & it looks like it worked even tho the only sites I allowed
were sourceforge.net and fsdn.com
It would be nice if javascript wasn't required, and if there is an
alternative hosting site that doesn't require javascript that would be
a strong reason to move.

As far as privacy goes, the SF privacy statement starts off looking
pretty good -  'We self-certify compliance with US-EU Safe Harbor.'
But the site won't work unless fsdn.com is allowed & I didn't see any
links to the fsdn.com privacy statement, so the only safe assumption
is that you have no privacy when visiting sourceforge :(

Mr. Hinojosa - since sourceforge.net won't work if fsdn.com is
blocked, could you have someone update
http://slashdotmedia.com/privacy-statement/ to include what, if any,
privacy sf users can expect from fsdn.com?

Thanks,
Lee


On 4/20/14, Fabian Keil <[email protected]> wrote:
> Fabian Keil <[email protected]> wrote:
>
>> Daniel Hinojosa <[email protected]> wrote:
>>
>> > I'm the SourceForge Community Manager. Is the no-JS editing on tickets
>> > the
>> > only blocker for you all to stay on SourceForge, or are there other
>> > reasons?
>>
>> There is no official and complete list of reasons to leave
>> SourceForge and no decision to leave has been made yet either.
>>
>> The TODO list item merely reads:
>>
>> 53) Find a more reliable hoster. Involves finding out what our
>>     requirements are and which SF alternatives fulfil them.
>>     It would probably also make sense to look into what other
>>     projects did when migrating away from SF.
>>
>> My personal impression is that privacy and security aren't a
>> priority for SourceForge and thus its not a good fit for a
>> supposedly privacy-enhancing proxy like Privoxy.
>>
>> The unnecessary JavaScript requirement is not the first service
>> degradation we've experienced and I doubt that it will be the last
>> one.
>>
>> Another obvious privacy issue with the new design is that one no
>> longer gets essential CSS unless one allows requests to third parties
>> that are colluding with the NSA (Google).
>>
>> If you check the bug reports I'm sure you'll find various other
>> privacy issues that have been ignored. I stopped reporting such
>> issues to SF years ago, because I could see no indication that
>> anyone cares.
>>
>> For example it took SF weeks to fix an obvious regression that
>> caused login data including passwords to be transmitted unencrypted.
>
> Two months later none of the issues mentioned above have been addressed
> and there hasn't even been an commitment to address them eventually.
>
> Therefore I think we should try to migrate away from SF before the
> end of May.
>
> The last months I have been somewhat preoccupied but I intend to
> spend more time on Privoxy in the near future again and consider
> the migration one of the more pressing issues.
>
> Please let me know if there are any objections, preferably before
> the end of April.
>
> Fabian
>

------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform