Open Source gurus, I need your assistance.

Should I Open Source Adoppt or not?

Will it be a good idea to make the code available. Are there any ways I can continue paying my bills with OS?

Can OS be restricted to personal use only?

--Frank

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your choice.

What if you …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
 http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions without changing too much. It's all about understanding the nature of data, not …

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your choice.

What if you …

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your choice.

What if you …

Not very subtle title?

But look at databases, and applications using databases...
You've got your databases, tables and columns. Exciting? Or yawn...

Think of data, not by columns and type, but rather how it lives.

- Some data participates in "business logic" — what to show, how to show, related to other tables, etc.
- Some data changes often, some is literally static
- Some data needs to remain static, try Sarbanes-Oxley?, or J-SOX the Japanese counterpart
- Some data is small, but some is large (music, movies, pics)
- Some tables need to be transactional, some you couldn't care less

So, what — just cram it all in a database...?

Consider this — for each of the examples above, there is a penalty you pay, either in storage or performance for your …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions without changing too much. It's all about …

MySQL — or, as I was frequently instructed, you spell it My-Ess-Que-Ell?...

Something everybody learns when starting at MySQL — though few as forcefully as I learned, when staying my first few weeks with Monty.

Ok, so I'm no spring chick anymore... it took me two weeks to learn the mantra, and now I have been assimilated.
But, look at it from the lighter perspective — if that was the hardest part — then the rest is really easy.

If you can handle more Monty stories, check out the interview:
http://dev.mysql.com/tech-resources/interviews/taneli-otala-mysql.html

But, what I really want to write about in this blog is about databases, or data management — future trends, how to make some entirely new and efficient applicatiions without changing too much. It's all about …

Greg Stein, chair of the Apache Software Foundation, and an employee at Google, working on open source projects, gave a very informative and compelling talk this morning comparing the various open source (and commercial) licensing schemes and the development model of both the Apache Foundation and the Eclipse Foundation.

Some of the main points of Greg's talk were that:

• The Apache Foundation manages a community, not code.
• The trend towards commoditization in the software industry will push most software licenses towards non-copyleft licenses (more in a later post)
• A community will grow only when it is given the freedom to grow, and part of this freedom is the ability to commit code to the project

As for Apache managing a community, and not code, Greg is saying, quite rightly, that the value of the Apache Software Foundation is not in the combined quality of the project's code, but in …