On 02/08/2013 10:37 PM, Richard Fontana wrote:
On Fri, Feb 08, 2013 at 04:49:29PM -0500, Joshua Gay wrote:
Both Section 7(ii) and Section 8 allow users to provide the Corresponding Source from a network location so long as it is provided at no charge.
I would like to add additional requirements.
The basic thing I'm looking for is that the source be made publicly available and not put behind some wall of inconvenience (such as requiring a specific device or requiring a user account, etc).
Below are three sections: 1) stuff I want to prevent, 2) stuff I don't want to prevent, 3) stuff I'm not sure about.
## Stuff I want to prevent
A person providing source shouldn't make a user do any of the following in order to be able to download the source:
- Create a user account
- Undergo identity verification/authentication (or sign in with some
third party service like Facebook or Twitter)
- Complete a survey or lengthy data collection process.
- First request send a request to the host that your IP address be added
to a whitelist
- Require the use of running proprietary software in order to download
the source code (e.g., requiring the use of some proprietary App Store App).
- Require the use of a specific kind of device or require a person to
spoof device metadata (similar to how the Android App store will prevent you from downloading an App that is not compatible with a certain device).
- Require some PACER like step of having a PIN mailed to you in the mail.
With the exception of PACER, I have encountered each of the above issues when trying to download source of programs licensed under the GPL.
Any suggestions for how to do this in ~25 words or less?
[snip]
How about:
"Corresponding source shall be accessible via non-proprietary means of access without charge, need for identity verification, or user traffic logging."
That comes to 20 words and would be a start.
Stephen Michael Kellat