Re:How to Publish Open-Source Code
by examancer on Wednesday September 11, 2013 @01:47PM
(#6368680)
Looks cool, but was immediately turned off by the request for access to read/write private gists when logging in through github.
[ Parent
| on HN ]
Re:How to Publish Open-Source Code
by williamcotton on Wednesday September 11, 2013 @01:49PM
(#6368693)
I'll turn that off now!
I was planning on using GitHub as a data store, but since it isn't built yet, no need to scare anyone off!
Re:How to Publish Open-Source Code
by williamcotton on Wednesday September 11, 2013 @01:53PM
(#6368718)
It turns out I'll need to change some backend code related to GitHub OAuth and then redeploy.
I'll do that tonight as I'm at work and I don't have a development environment for lit on this machine.
Hopefully in the future when I've built out the features that I have planned it will offer a compelling reason to allow this access!
> Hopefully in the future when I've built out the features that I have planned it will offer a compelling reason to allow this access!
This attitude is what I want to see in our community period. Android/Git/whatever.. tell me WHY I should give you access, without assuming your intent is implicitly good.
Nice work dude. And +1 to not requiring read/write to private gists.
I was afraid I'd be the only person who was annoyed by that, but the parent post tells me otherwise.
Might I suggest using local storage rather than gists/Github as data store?
Re:How to Publish Open-Source Code
by williamcotton on Wednesday September 11, 2013 @09:29PM
(#6371410)
lit will no longer ask for private gist access:
https://github.com/williamcotton/lit/releases/tag/v0.1.2
https://github.com/williamcotton/lit/commit/06c79eb3780663d2...