Open source licenses and code sharing

I’ve been swamped with a big development project of late.  It has hampered my ability to spend any time extending FrameAlbum but it does have the small benefit of covering my Starbuck’s addiction. 😉

The first item to be tackled is publishing some code!  I have to first settle on an open-source license; I’m open to any comments/suggestions folks may have on this topic.  My initial thoughts are to find a license that allows folks to use & modify it freely for their own use.  If they choose to use it in a commercial service they should be compelled to contribute something back to the project/community.

I’ve already starting putting the code into a GIT repository.  For you non-code-slingers out there GIT is a program for managing the source code (the stuff that programs are made of) of a program or website.  I am not a code-slinger by day so my git-fu is not strong however it does have a strong following among the code- slingers I know and trust.  If you are interested in contributing to FrameAlbum or just having a look at how the sausage is made then grab a copy of GIT and run it around the block a bit.

The next big feature to be added to the service is integration of Facebook photos.  Lots of people have asked for them and I’m interested in diving into Facebook’s new developer’s platform.

Beyond that, I plan to expand the informational channel types (news, weather forecasts, news, etc.), expand Picasa support to include non-public albums and add ‘tag’ filtering to all photo feeds.

Stay Calm and Carry On.

T.

One thought on “Open source licenses and code sharing”

  1. +1 to git
    I sounds like you’re leaning towords GPLv2 or v3 which are both good licenses and require code changes to be given back if they sell or publish a binary.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.