This may not work, because they've just chaned the mail config _again_...
Bryce Harrington wrote:
The book "Open Source Development with CVS" is IMHO the best source of good, solid advice about starting and running open source projects. (The odd numbered chapters talk about cvs, the even ones about open source dev.)
I will try and get this book.
Based on our discussions so far, it looks like the invariants might be:
- Full SVG compliance
Yep.
- Core coded in C/C++
Yep
- Gtk-compliant user interface
Can we go further and say Gnome (including HIGs)?
- Extensible using various scripting languages
Aiming for first-class external language access
- Open, community-oriented development processes
A Biggy
- Baseline is the Sodipodi 0.32 codebase
Yep
- Strives to use commonly available libraries
Yep, how about when ever we share some functionality with another program, share a library. That's the GnuCash fill-o-sophy, and I think the results speak volumes!
Thoughts? More? Less?
I think the first three in particular are important items to establish firmly, because they are the types of things that can get endlessly argued back and forth and back again, until months path with zero results. Establishing them as invariants allows us all to admit and agree that C and C++ suck, and lets us get down to coding in them anyway. ;-)
Indeed, and porting to another language is O(n) anyway. In this vein, I propose we prototype things in high level scripting language of choice and use that to nut out ideas for things like options dialogs. Especially when talking on jabber.
njh