I'm not an expert and others may be able to answer your question better
than I can, but one of the main reasons for choosing the ASL is that you
can do _exactly_ what you're thinking of. As I understand it, you have
to include a copy of the ASL, and the Habari Copyright information with
your code when you distribute it, but your own code can be licensed any
way you choose.
From http://www.apache.org/licenses/LICENSE-2.0
"You may add Your own copyright statement to Your modifications and may
provide additional or different license terms and conditions for use,
reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and
distribution of the Work otherwise complies with the conditions stated
in this License."
From a community perspective, we would (of course) be very appreciative
if you come up with anything particularly useful and contribute back to
the Habari code base, but you are under no obligation to do so.
This is my understanding of the ASL. Basically, Habari's code must
remain ASL and be identified as being Habari and ASL, but your own code
is your code to do with as you please.
--
Sean T. Evans
As the local representative of the ASF, I confirm that Sean's
assessment here is 100% accurate. The ASL exists to let you do what
you describe.
It also bears mentioning, with all of the WordPress vs Thesis theme
controversy going on lately, that if you were to create a premium theme
for Habari, Habari does not insist that you license your code in any
particular way. This means you can write and potentially sell themes
under whatever license you please.
This is specifically different from WordPress, which requires that you
license your theme code under the GPL.
Owen