Calling all developers! Help build the Snipt API.
The following was just posted on api.snipt.net.
A call for helpHouston, we have a problem. We've hit the limit as far as time resources are concerned. We're looking to the development community to help us build a stable, robust, and open-source RESTful API for Snipt.
A little background noiseLion Burger is the group behind Snipt. Lion Burger is a side project of Nick Sergeant and Pete Karl. We primarily build apps and sites for clients, and have a few on our plate right now.
Snipt is a side project quickly gaining momentum among developers. In order to keep up with the community's demands, and foster Snipt's growth, we need to provide an open, public API.
What we needThe aim of this call for help is to organize a group of developers interested in helping build the official Snipt API. While Snipt itself will remain closed-source, the API will be open-sourced on GitHub.
What's been done so farWe've taken a long, hard look at what we want for an API. We have a very clear high-level vision of what needs to be done, but lack the resources needed to pull it off in a timely manner. We've made public some conversation notes we put together.
Also, as a show of how badly an API is wanted, Michael Boutros actually wrote a pseudo-API in Ruby using screen-scraping libraries.
Why it mattersIt matters because, as users of Snipt, we want to see it succeed in platforms and environments that are not penetrable by the current website-only technology (eg. desktop apps, text editors, CLIs, etc).
How to helpIf you're interested in helping, or have any questions or comments, contact Nick Sergeant.
- Picked up an '03 Strat (Midnight Wine) http://twitpic.com/187hwh
- So Verizon phones can not place a call to @ashleytaylor's iPhone. They get the message "this line has been disconnected." WTF, AT&T?
- @frankpiacitelli yeah, pretty nuts.
- @steyblind Congrats! (inbox zero, right?)
- @mikesusz meh. Friday is not for productivity ;)
- Afternoon of champions. http://twitpic.com/18532o
- What a steal. http://bit.ly/cTV218
- @mikesusz Ah, yes. Good ol' Phin & Matt's :) Love that stuff.
- Great Lakes Sampler Pack for beer Friday. Thuper.
- @rufo Ah, gotcha. Makes sense.
9 Comments
Lol, stop being a cheap bastard and hire a developer, man. You're asking people to work FOR YOU for free, getting nothing in return.
I'm with LLuis actually - if snipt was open source, and this was a call for action on that, it would be one thing, because then people could run with it on their own. Since it's not, you're basically asking the community at large to contribute a huge value-add for nothing. That the value-add would be open doesn't mean anything.
If it's not important enough to you to do yourselves, then let the community of people that love the product generate it. It'll happen on it's own, as the api you linked to proves. If it doesn't, and you think you need it to get users, then it's on you to provide.
I'm on the fence here. While Snipt does provide a free resource for developers -- and a good one at that -- I think the code needs to be made open source before folks commit their time towards improving it.
Or better yet: Keep it closed, and provide a rev-share model for those that improve the API. :)
So, What you are asking is, for competent developers to stop what they are doing. And to pitch in on your closed source project for ABSOLUTELY nothing in return?
Jon:
For us, this isn't a question of importance. We have limited time, and with that, we do what we can to respond to users, and enhance Snipt.net.
An API to Snipt has come to the forefront of user demands. We don't have the skills, or the time for such an undertaking, and so we thought that an open source project was a good banner to fly api.snipt.net under.
Is it a huge value-add if it's unreliable, and poorly written? The quality only comes with community input, and if in return we have to gut & and open up an already functioning web app, then it's not in the cards. That said, read on:
Patrick, Jon:
I'm convinced by your arguments that open-sourcing the API isn't enough of a reward for the work on it.
Specifically, keeping it closed, and offering a profit share (which still could be nothing), offers more motivation for developers to dedicate themselves.
I've watched Pete and Nick build Snipt (a free tool to help developers save time) over the past several months, during which they have each invested many many hours. I personally find myself getting good use out of it 2-3 times per week, and I'm very grateful for their efforts here.
If I had more experience building APIs, I'd happily help them out here because they've spent well over 100 hours doing the same for me and every other developer out there, while asking nothing in return.
I understand where developers are coming from. I think I should explain our intentions a bit more.
We're looking for developers who are Snipt users, and Snipt enthusiasts. The work that will result in this open source project will greatly benefit anyone who uses Snipt.
At the end of the day, this project will be open source. Just because the main project is not open source does not mean it detracts from the API's open source nature. The developers who decide to work on the API will be allowed to view and run their own Snipt project for development purposes with the actual Snipt source code. It just won't be open source.
We're not making money on Snipt, and don't really care if we ever do. We simply want to make Snipt the best code-sharing and storage service out there.
We are passionate about quality code, and quality user interfaces. We want to partner with developers who share our love for this industry, and those who truly enjoy using Snipt and want to see it exceed in areas other code-sharing sites have not.
Nick
@Nick
Thanks for the follow-up. Please don't misread my comment as a complaint.
I think what ya'll have built is a great app and a great service. I'll continue to promote it among my contacts.
Patrick,
No worries - I completely understand. I just wanted to clarify where we're coming from.
We've got a few devs interested in working with us to put together a strong API, so hopefully we'll get this thing moving soon!
Thanks,
Nick
Post new comment