Team1

[adunkman]

This was the proposed solution by:
@jcavena @jeremyrsellars @mez @nickmabry @joeandaverde

Challenge: create a web page that gives a QR code, and when that code is scanned, it will link a user to an activation page specific to that code.

Please comment on both the solution as a whole and the elegance / maintainability / cleanliness of various parts of the code.

[smerchek]

I like the idea of using bitly; however, it's kind of a hindrance to need a bit.ly username and API key and having to manage those using the env variables. I do like that it provides a short url and some analytics, but the analytics are quite simple and may not even be what we want in the long run.

Perhaps this good be a better long-term solution, but right now I feel like having to get an API key would provide friction for new contributors.

[mez]

I agree with Scott here. Lets keep it simple which will allow us to iterate
much faster.

On Thu, Feb 2, 2012 at 1:38 PM, Scott Smerchek <
reply@reply.github.com

wrote:

I like the idea of using bitly; however, it's kind of a hindrance to need
a bit.ly username and API key and having to manage those using the env
variables. I do like that it provides a short url and some analytics, but
the analytics are quite simple and may not even be what we want in the long
run.

Perhaps this good be a better long-term solution, but right now I feel
like having to get an API key would provide friction for new contributors.

---

Reply to this email directly or view it on GitHub:
#1 (comment)

Meseret Gebre | MeseretGebre.com

[dynajoe]

Simply put I agree.

Unless there's a significant use case that's solved with using bitly it's just a middleman. the analytics discussed seems simple enough to perform without third party dependencies.

[nickmabry]

I agree. It was an interesting experiment, but the Google Charts solution seems much cleaner.

[jcavena]

So we kill Team1 approach and go with Team2? Is that merged into Master? What are the next steps?

[nickmabry]

Sounds good to me

[smerchek]

If the consensus is to go with branch team2 then perhaps we should head over to that pull request and make sure it's actually what we want to pull in. There are probably some things we could do with it before next meeting to harden it some.

[dynajoe]

We've decided to go with a different solution. Bitly was too complicated for a simple problem.