Hmm, maybe I'm missing something, so if I may someone please clue me in, but what are we discussing here?
I mean if what you're asking is are you allowed to make a theme? Sure, feel free, I mean not as if anyone is stopping you - anyone can make a theme. If the said theme is "shit-hot" as you say, who knows, if everyone likes it maybe it'll even be included in core. But if you're expecting that whatever you make will be automatically included... yeah, can't really say I'm up for that... On Jul 14, 8:52 pm, luke <[email protected]> wrote: > Wow. What an amazing response! I'll try to address the points raised > as best I can, if I miss anything important please let me know and > I'll try to address it as well. I'm only human :) > > These are the responses to the theme contribution questions. Please > see the other posts for responses to sponsorship and hp.o. > > > Indeed of we had them create a new theme for inclusion with the download, > > it would have to asl licensed which means the credit would have to be > > removable. > > Ahh. Cool. This is something I did not know. Just to quote the bit > that i thought was pertinent [1]: > > Section 4: Redistribution. Clause 3: "You must retain, in the Source > form of any Derivative Works that You distribute, all copyright, > patent, trademark, and _attribution_ notices from the Source form of > the Work, excluding those notices that do not pertain to any part of > the Derivative Works; and " (emphasis mine) > > Not sure how this sits? Obviously part of what we doing is to increase > Squareweave's profile. The attribution is a bit important. I think > it's also important to distinguish between attribution in the theme > xml, from attribution in the client side output. We would like both. > As far as i understand the ASL and the Habari policy as defined here > [2], others shouldn't change the attribution in the XML, but anyone > can change the attribution in the footer. I'm not sure why you would, > except to customise it for your own use (which is fine, and wouldn't > require committing back to -extras). Just thinking out loud a bit > here. > > > First, any theme has potential to be elevated (to use a loaded word) to > > core status. It's just a matter of getting community consensus. I know > > there has been some opinion to drop k2 from core, and a new Habari-specific > > theme would be a good replacement. > > Sure. We would want it to get there because it's shit-hot. Not for any > other reason. > > Cheers! > > [1]http://www.apache.org/licenses/LICENSE-2.0.html > [2]http://wiki.habariproject.org/en/Extras_Repository#Attribution --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
