[prev in list] [next in list] [prev in thread] [next in thread]
List: privoxy-commits
Subject: [privoxy-commits] current TODO,1.105,1.106
From: Fabian Keil <fabiankeil () users ! sourceforge ! net>
Date: 2014-05-13 11:16:14
Message-ID: E1WkAgz-0007yh-He () sfs-ml-3 ! v29 ! ch3 ! sourceforge ! com
[Download RAW message or body]
Update of /cvsroot/ijbswa/current
In directory sfp-cvs-1.v30.ch3.sourceforge.com:/tmp/cvs-serv30560
Modified Files:
TODO
Log Message:
Add the hosting wish list relevant for #53
Originally proposed in:
http://sourceforge.net/p/ijbswa/mailman/message/32306540/
Slightly modified to fix spelling errors etc.
Index: TODO
===================================================================
RCS file: /cvsroot/ijbswa/current/TODO,v
retrieving revision 1.105
retrieving revision 1.106
diff -C2 -d -r1.105 -r1.106
*** TODO 13 May 2014 11:15:28 -0000 1.105
--- TODO 13 May 2014 11:16:12 -0000 1.106
***************
*** 121,124 ****
--- 121,127 ----
projects did when migrating away from SF.
+ 2014-05-13: Work in progress. Hosting wish list at the end
+ of this file.
+
54) Move away from CVS to a more modern revision control system.
Find out if there are any objection against going with Git.
***************
*** 355,356 ****
--- 358,408 ----
125) Allow clients to HTTPS-encrypt the proxy connection.
+
+ ##########################################################################
+
+ Hosting wish list (relevant for #53)
+
+ What we need:
+
+ - Bug tracker
+ - Mailinglists (Mailman with public archives preferred)
+ - Webspace (on a Unix-like OS that works with the webserver targets
+ in GNUMakefile)
+ - Source code repositories (currently CVS, but migrating away
+ from it is TODO #54 anyway and shouldn't be too much trouble)
+ - Commit mails (preferably with unified diffs)
+
+ (Unsorted) details to look at when evaluating hosters:
+
+ 1. Preferably no third-party ads and trackers.
+ External images, CSS and JavaScript may count as trackers
+ but texts like "supported by company XYZ" may be acceptable.
+
+ 2. JavaScript should be optional or not used at all.
+
+ 3. Services we don't need shouldn't be enabled anyway.
+ (We currently don't use Web forums, wikis, surveys etc.)
+
+ 4. It would be preferable if the hoster didn't have a bad track
+ record as far as user experience, security and privacy are
+ concerned and if the terms of services are "reasonable" and
+ haven't changed too often in the past. Updates in the past
+ should have been improvements and not regressions.
+
+ 5. It would be preferable if most of the server administration
+ is done by a trusted third-party (or at least not a lot of work
+ for us).
+
+ 6. The server(s) should be located in a country with laws we can
+ understand and follow (or at least not unintentionally violate).
+
+ 7. A server location in a country with some kind of due process
+ and strong data protection laws (at least on paper) would be
+ preferable.
+
+ 8. Given that Privoxy is a free software project it would be
+ preferable if the hoster would use free software where possible.
+
+ 9. Migrating away from the hoster in the future without losing
+ any important data should be possible without writing web
+ scrapers first.
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
ijbswa-commits mailing list
ijbswa-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ijbswa-commits
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic