roseleaf / labs_beta Goto Github PK

fetch from:

https://api.github.com/orgs/zendesklabs/repos(.json)
on a regular basis to compare

• only will grab public repos.
• need to convey org-wide the importance of keeping private repos private

OAuth: https://support.zendesk.com/entries/24458591-Using-OAuth-authentication-with-your-application

Apps API: http://developer.zendesk.com/documentation/apps/reference/api.html

dev version still in play in prod; increased slug size and unnecessary logging - using ember-rails, must investigate

Currently notes are static; extension controller (rb) already has a method that can fetch the readme and save it to the model, but have not decided at which point(s) to perform this as it can cause the app to hang.

Proposed ideas:

1. Throw a scheduler on Heroku that fetches all the READMEs at a specified interval, such as weekly
2. Have the labs repo admic create web hooks for updates and listen to the GH API for pushes; update the README on receipt of that notification.

Strong preference for "2" but requires team effort

framework and preliminary tests are in place, but need to test all routes

instructions at: http://isotope.metafizzy.co/docs/hash-history-jquery-bbq.html

filtered views of the /extensions page should be linkable/sharable and navigable

Design should be responsive and readable on mobile, but download links should not be visible on mobile

Hidden #overlay div already exists, text can be found in old labs site, need to trigger pop-up onclick of 'download' on the ExtensionView; clicking 'Agree' on pop-up should then trigger the linkTo the extension's zip_url

fails if not found

token protection (sorta half @$$ed) already exists on Api_V1_Extension controller for these actions, but we will need something more full fledged.

Either create a user, or implement OAuth, or temporary Basic Auth

Would like to collaboratively decide

on https://github.com/zendesklabs/ *