Page MenuHomePhabricator
Create Task
Maniphest T317

"Terms of Use" must be prominently featured in the Developer Hub
Closed, DeclinedPublic
Actions

Description

From https://www.mediawiki.org/wiki/Talk:Data_%26_Developer_Hub#terms

Unlike most of the linked reference sites, we don't enforce developer behaviors through a Terms of Use. To replace that, it probably will help to have a terms page somewhere mentioning licensing, rate-limiting, etc. Doesn't have to be terribly high profile or anything, but something to think about including in the design.
Currently all we really have is a single legal page on dumps.wikimedia.org, which I'm surprisingly OK with content-wise, but is pretty hard to find. @LuisVillaWMF

Details

Reference
fl496
TitleReferenceAuthorSource BranchDest Branch
Draft: [JS] Allow instrument maintainers to tag eventsrepos/data-engineering/metrics-platform!40phuedxwork/phuedx/tagsmain
Add test case for backporting to checked-out but non-live branchrepos/releng/scap!214dancymaster-Ied68b1f040c96b7716273898d9a2c1d3941207b2master
deploy/scripts/scap-prep-mw-branches: Create old-version filerepos/releng/train-dev!34dancyreview/dancy/create-old-versions-filemain
scap backport: Enhance handling of checked-out but not live branchesrepos/releng/scap!208sandeepsmaster-I708f0ebceef31af43208ad3f9a4f6305c5fb2149master
Hide ban form if not authorizedtoolforge-repos/phab-ban!5bd808work/bd808/T317584main
Fundraising apache image: use site config from hostrepos/releng/dev-images!27ejegghostSiteConfigmain
Clean up RewriteRules in mw default site configrepos/releng/dev-images!26ejeggrewriteRulesmain
Remove load_tools_stats.py.toolforge-repos/toolviews!1andrewremoveloadmaster
Update schema.sql to support storage of unique pageviewsandrew/toolviews!2andrewuniqueipsmaster
Remove load_tools_stats.py.andrew/toolviews!1andrewremoveloadmaster
Customize query in GitLab

Related Objects
Search...

StatusSubtypeAssignedTask
 ResolvedQgilT101099 Developer Relations Roadmap
 ResolvedQgilT113030 Developer Relations quarterly review Jul-Sep 2015
 ResolvedQgilT101100 Engineering Community quarterly goals for July-September 2015
 Resolved• SpageT101441 Goal: Integrate the new Web APIs hub with mediawiki.org
 Resolved• SpageT307 Announcing the Developer Hub prototype release
 Resolved• SpageT299 Release the Developer Hub prototype
 Resolved• SpageT306 Featuring the first three APIs in the Developer Hub
 DeclinedNoneT335 Document the Content API in the Developer Hub
 DeclinedNoneT302 API sandboxes for the Developer Hub
 ResolvedNoneT300 Select the three APIs featured at the Developer Hub prototype
 DeclinedNoneT88755 Improve MediaWiki API example behavior
 ResolvedAnomieT89229 API Help should generate [try in ApiSandbox] link to Special:ApiSandbox#action=params from getExamples()
 DeclinedNoneT89318 Replace on-wiki API documentation with Special:ApiHelp transclusion
 OpenNoneT89768 Language support in Special:ApiHelp and its transclusion.
 OpenNoneT90528 Generated API Help doesn't indicate the MediaWiki versions that support a module and parameters.
 Resolved• SpageT89680 Template:ApiEx on mw.org should have a link to "[view in ApiSandbox]".
 ResolvedoriT334 Document RCStream in the Developer Hub
 ResolvedjeropbrendaT359 Document the Wikidata API in the Developer Hub
 OpenNoneT89863 [Task] Merge on-wiki Wikibase/API documentation into Wikibase apihelp strings.
 DeclinedQgilT303 Setup the Developer Hub prototype
 Resolved• SpageT305 Developer Hub homepage
 DeclinedNoneT317 "Terms of Use" must be prominently featured in the Developer Hub
 Resolved• SpageT98164 prototype Data and developer hub with Blueprint skin

Event Timeline

• flimport raised the priority of this task from to Medium.Sep 12 2014, 1:44 AM
• flimport added a project: Web-APIs-Hub.
• flimport set Reference to fl496.
• flimport added a subscriber: revi.Oct 10 2014, 9:00 PM
D_konto subscribed.EditedOct 23 2014, 9:02 PM

The recommended place to make available the Terms of Use should also depend upon the platform.

  1. Mobile: For mobile it is recommended that we provide a link to the Terms of Use on the download page in the relevant application store in case mediawiki & developers hub will be an iOS or Android app in the future.
  2. Web: It is recommended that we provide a link to the Terms of Use in the footer of the website.
Ckoerner subscribed.Nov 8 2014, 4:33 AM

One of my favorite Terms of Service (if one can have a favorite) is that of 500px. They took care in what could easily be a wall of legalese and jargon and distilled it down to easily human readable text.

https://500px.com/terms

We should take a page from their book and strive to make our terms, or other expected developer behavior, clear and readable. Not just in the sense of legibility, but make it something people want to read.

• Spage mentioned this in T104288: Blueprint skin has no footer or replacement (so no copyright).Jun 30 2015, 3:31 AM
Aklapper closed this task as Declined.Oct 7 2019, 11:17 AM
Aklapper subscribed.

The Web-APIs-Hub project is dead hence mass-declining its tasks to reflect reality. It might be superseded by a Developer Portal in the future.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL