28 March 2011

Options for an open-source project

I'm nearing completion of the next generation of xSiteable, which used to be a "website generator in XSLT using Topic Maps" but has evolved over the last 10 years into "RESTful SOA, event-driven developer-focused, less-is-more PHP framework and super-cool XSLT templating layer, with a Topic Maps engine, full-stack plugin architecture, life-cycle-based event model, shaped around HTML5, CSS and JQuery" kinda framework, a little something I've tinkered with to fit all my many needs over the years.

Now, in my current job I'm creating a document-control, intranet, social web app thingy for a health-care organisation, and we've agreed to open-source the lot. So, I could use some advice, but here's the current plan ;

  • xSiteable is BSD licensed, and consists of the framework itself
  • a yet unnamed application written using xSiteable is released with BSD license as well

How should I distribute the two? Are the licenses ok? What source repository to use? Google Code, GitHub, what? (We've got both in subversion on a local server right now) xSiteable is really a collection of reusable classes where some are dependent on others, but not completely. Where to document the API's? Where to document examples and guides? How to attract users? Should I create a blog for it? And on and on.

Thoughts or ideas?

1 comment:

  1. Will just say that I think github is vastly better than the alternatives for distribution and collaboration.