Python Wrapper for Yipit API - my first big open source project

Re:Python Wrapper for Yipit API - my first big open source p... by alexatkeplar on Sunday October 09, 2011 @06:42AM (#3090219)

Another couple of recommendations (sorry I think about this stuff way too much):

1. GitHub SEO is your friend. For this reason, better to name your GitHub repo something like "yipit-python-client" because that's what people will search for. And maybe change your one-line description to "A Python client library for the Yipit API"

2. On licensing - you really just want as many people to use your library as possible (it doesn't really represent intellectual property that you could one day profit from). For this reason, steer clear of (A)GPL and go with a MIT/Apache2/BSD-style license. For the exact one to choose - I normally go with either a) the same license as that used in my component libraries (e.g. DictShield is BSD), or b) the same license as the API author (in your case Yipit) uses for their own client libraries (I checked and they don't seem to have released any)

[ Parent | on HN ]

Re:Python Wrapper for Yipit API - my first big open source p... by wesleyzhao on Sunday October 09, 2011 @06:44AM (#3090224)

1. Good point. But is 'client' more searched/common than 'wrapper'?

2. Yup, they didn't have any libraries. Thus, the wrapper I created :). You're right, may go with MIT/Apache/BSD.

[ Parent | on HN ]

Re:Python Wrapper for Yipit API - my first big open source p... by alexatkeplar on Sunday October 09, 2011 @02:17PM (#3090938)

1. Yeah I'd say so. "Wrapper" describes how it works (it wraps naked HTTP calls) but not what it is (a client library for the Yipit API / web service) 2. Cool!

[ Parent | on HN ]