Network services/Draft statement: Difference between revisions

From WikiDotMako
(caps; "user-controlled" for deployers morethan developers; pile up all architecture; and to avoid loopholes; we know they create problems; desk/laptop irrelevant--computer; services more direct)
(attempt to capture public/private and data/works of authorship)
Line 3: Line 3:
March 16, 2008, a workgroup convened at the FSF to discuss issues of freedom for users, given the rise of network services. We considered a number of issues, among them what impacts these services have on user freedom, how implementers of network services can help or harm their neighbors, and how users can tell which services are friendly to freedom. We believe this will be an ongoing conversation, potentially spanning many years, and our hope is that the FSF will expand its traditional role of moral and technical leadership to include this area.
March 16, 2008, a workgroup convened at the FSF to discuss issues of freedom for users, given the rise of network services. We considered a number of issues, among them what impacts these services have on user freedom, how implementers of network services can help or harm their neighbors, and how users can tell which services are friendly to freedom. We believe this will be an ongoing conversation, potentially spanning many years, and our hope is that the FSF will expand its traditional role of moral and technical leadership to include this area.


We consider network services that are '''Free Software''' and which share '''Free Data''' as a good starting-point for ensuring users' freedom. Although we have not yet formally defined what might constitute a 'Free Service', we do have suggestions that developers, deployers, and users should consider:
We consider network services that are '''Free Software''' and which share '''Free Data''' as a good starting-point for ensuring users' freedom. Although we have not yet formally defined what might constitute a 'Free Service', we do have suggestions that developers, service providers, and users should consider:


* '''Developers''' of network service software are encouraged to:
* '''Developers''' of network service software are encouraged to:
Line 9: Line 9:
** Develop freely-licensed alternatives to existing popular but non-Free network services.
** Develop freely-licensed alternatives to existing popular but non-Free network services.
** Develop software that can replace centralized services and data storage with distributed software and data deployment, giving control back to users.
** Develop software that can replace centralized services and data storage with distributed software and data deployment, giving control back to users.
* '''Deployers''' of network services are encouraged to:
* '''Service providers''' are encouraged to:
** Choose Free Software for your service.
** Choose Free Software for your service.
** Release customizations to your software under a Free Software license.
** Release customizations to your software under a Free Software license.
** Make data available to the service's users (not necessarily the general public) under a free data license, such as those approved for [http://opendefinition.org/licenses Open Knowledge] and [http://freedomdefined.org/Licenses Free Cultural Works].
** Make data and works of authorship available to the service's users under legal terms and in formats that enable users to move and use the data outside of the service.
*** Users should control their private data.
*** Data available to all users of the service should be available under terms  approved for [http://opendefinition.org/licenses Open Knowledge] and [http://freedomdefined.org/Licenses Free Cultural Works].
* '''Users''' should:
* '''Users''' should:
** Consider very carefully whether to use software on someone else's computer at all. While we acknowledge that such services may have substantial benefits, they also create new problems such locking in users to particular services and compromising user privacy. Many hosted applications have Free Software equivalents that run on your own computer.
** Consider very carefully whether to use software on someone else's computer at all. While we acknowledge that such services may have substantial benefits, they also create new problems such locking in users to particular services and compromising user privacy. Many hosted applications have Free Software equivalents that run on your own computer.
** When deciding whether to use a network service, look for services that use Free Software, provide source code, and that make their data available under a free license, so that when necessary you still have the freedom to modify or replicate the service without losing your own data.
** When deciding whether to use a network service, look for services that use Free Software, provide source code, and that make their data available under a free license, so that when necessary you still have the freedom to modify or replicate the service without losing your own data.

Revision as of 23:25, 10 May 2008

The current generation of network services provide significant advantages over traditional locally installed software in ease of deployment, collaboration, and data aggregation. Many users have begun to rely on such services in preference to software provisioned by themselves or their organizations.

March 16, 2008, a workgroup convened at the FSF to discuss issues of freedom for users, given the rise of network services. We considered a number of issues, among them what impacts these services have on user freedom, how implementers of network services can help or harm their neighbors, and how users can tell which services are friendly to freedom. We believe this will be an ongoing conversation, potentially spanning many years, and our hope is that the FSF will expand its traditional role of moral and technical leadership to include this area.

We consider network services that are Free Software and which share Free Data as a good starting-point for ensuring users' freedom. Although we have not yet formally defined what might constitute a 'Free Service', we do have suggestions that developers, service providers, and users should consider:

  • Developers of network service software are encouraged to:
    • Use the Affero GPL for their software to ensure that users of services have freedoms to examine the source or implement their own instance.
    • Develop freely-licensed alternatives to existing popular but non-Free network services.
    • Develop software that can replace centralized services and data storage with distributed software and data deployment, giving control back to users.
  • Service providers are encouraged to:
    • Choose Free Software for your service.
    • Release customizations to your software under a Free Software license.
    • Make data and works of authorship available to the service's users under legal terms and in formats that enable users to move and use the data outside of the service.
      • Users should control their private data.
      • Data available to all users of the service should be available under terms approved for Open Knowledge and Free Cultural Works.
  • Users should:
    • Consider very carefully whether to use software on someone else's computer at all. While we acknowledge that such services may have substantial benefits, they also create new problems such locking in users to particular services and compromising user privacy. Many hosted applications have Free Software equivalents that run on your own computer.
    • When deciding whether to use a network service, look for services that use Free Software, provide source code, and that make their data available under a free license, so that when necessary you still have the freedom to modify or replicate the service without losing your own data.