Google Data Liberation Front
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Google Data Liberation Front" – news · newspapers · books · scholar · JSTOR PROD Expired+%5B%5BWP%3APROD%7CPROD%5D%5D%2C+concern+was%3A+Not+notable.+No+significant+third+party+coverage. Expired [[WP:PROD|prod]], concern was: Not notable. No significant third party coverage. Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Google Data Liberation Front|concern=Not notable. No significant third party coverage.}} ~~~~ Timestamp: 20120610014828 01:48, 10 June 2012 (UTC) Administrators: delete |

Google's Data Liberation Front is an engineering team at Google whose "goal is to make it easier for users to move their data in and out of Google products."[1] The team, which consults with other engineering teams within Google on how to "liberate" Google products, currently supports 27 products.[2] The purpose of the Data Liberation Front is to ensure that data can be migrated from Google once an individual or company stops using their services.[3]
See also
References
- ^ "the Data Liberation Front". Google. Retrieved 16 September 2010.
- ^ http://www.dataliberation.org/system/app/pages/subPages?path=/google
- ^ Kenyon, Henry (Sep 13, 2010). "Google Apps government reach grows". Retrieved 17 September 2010.
External links
![]() | This World Wide Web–related article is a stub. You can help Wikipedia by expanding it. |