[development] Drupal 6.2 theme system standalone
Bob Pepin
bob.pepin at gmail.com
Fri Jun 13 18:10:43 UTC 2008
Well for now I've put GPL on it, which makes sense cause a lot of what
I have done is simply assembling the drupal functions used by the
theme system into one place. You could even create a script for
extracting those functions from the drupal codebase, which would also
make maintenance easier, maybe something like this even exists
already? Besides, I figured most of the development happening on this
will be improving compatibility with certain themes by either
importing or adding stubs for the extra drupal functions used by them,
which is something where it makes a lot of sense to share
contributions.
Anyway, I plan on layering a very thin entry point to this library
just on top of the drupal callbacks, so the idea is for example not to
implement any custom cache facility inside this but instead to provide
hooks where you can register your own routines for handling caching
from outside the library. This will hopefully prevent the GPL from
infecting your projects ;)
But besides, I'd also be interested to know if theoretically I would
be forced to use the GPL in this particular case, so if we've got any
license war veterans in here, feel free to comment.
On Fri, Jun 13, 2008 at 19:15, Ken Rickard <agentrickard at gmail.com> wrote:
> Question for the pseudo lawyers in the room. Does this mean that Bob's work
> must be GPL'd?
>
>
> On Fri, Jun 13, 2008 at 1:04 PM, Adrian Rossouw <adrian at bryght.com> wrote:
>>
>> On 13 Jun 2008, at 6:59 PM, Matt Galvin wrote:
>>
>>>
>>> Drupal is open source. Anyone is free to use it for what they wish as
>>> long as they share their derivative work. He is sharing his. It may
>>> not be useful for you but it might be for someone. Among other things
>>> Drupal takes PHPTemplate and builds on top of it for theming. What Bob
>>> is doing is not all that different.
>>
>> yeah. tbh, i wrote and tested phptemplate (and formsapi) completely
>> separately
>> from drupal before starting to integrate it.
>>
>> Some of the more recent changes in D6 might make it a bit harder to
>> separate,
>> but it should still be workable.
>>
>
>
>
> --
> Ken Rickard
> agentrickard at gmail.com
> http://ken.therickards.com
More information about the development
mailing list