Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By drama on
I have question regarding template.
If I have creted theme and I put it for download for other, is possible that I wil have condition that nobody can delete link to my website? If GPL licence dont allow it, is it possible to publish this theme under another licence? Or simply not give this to download?
Comments
Links
Hi
I dont know the correct legal answer. But I know that you are using Drupal that have been contributed by a comunity of users over several years. The majority of them have no link or no reference anywhere.
Why are you so conserned about your link. You want to take and not give.
The fact is that you put somthing on the internet it is gone. You have no control anymore. That is part of life.
If you ask people not to delete your link. Some people may accept that other may not. But if you expect me to use a template that have your link on my site. I only have one thing to say.
STUFF IT!
Have a nice Weekend
Are Casilla
http://astartelecom.com - Independent VOIP Telecoms Broker. Consulting in Asterisk and Drupal
http://astbill.com - Billing, Routing and Management software for Asterisk and MySQL. Running on Drupal
AstBill DEMO: http://demo.astbill.com
"You want to take and not
"You want to take and not give." - No, he gives.
It's easy to say that "opensourcing la la la, everything must be free". He gives his time spent on that template, because sinse it's published it won't be unical any more. And small link in the bottom of the page is not a great problem.
It was mentioned somewhere on this site that theme development is completely different, cause in the most of cases you won't get new features to your work (like it is when you release a module).
I think it's easy to say what you said when you haven't done anything yourself.
I'm not sure, but AFAIK even if it is not allowed under GPL a theme is a separate product and can be released under ANY license.
Copyright notices
If you want to make it a Drupal project, you must GPL it and then anyone can change it and remove your link. Unless... it's a copyright notice. I am absolutely unsure of what and how can form a copyright notice and whether that can be removed or not. (It was me who have pointed out the stark difference between sharing a theme and a module)
--
Read my developer blog on Drupal4hu.
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
"If you want to make it a
"If you want to make it a Drupal project..."
But he also can put it on another site and just give a link in this thread.
Creative Commons
You could use a CC License http://creativecommons.org/license/
with kind regards, holger
www.ebec.net | www.stnetwork.de
License
So, is it allowed to make another license for template then GPL?
Any project hosted on
Any project hosted on Drupal.org must be GPL.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
The license of my own theme?
Hi,
I am looking for a CMS that allows me to set up a website for a customer. I would love to use drupal because it is by far my favorite cms.
For this customer I would have to implement a custom theme. The customer is not willing to license this theme. Some CMS's licenses view themes as "derived work", others do not. Unfortunately I was not able to find a clear statement (though I found many opinions in the forums) about this issue.
If there is a clear statement please tell me!
Thanks, Merlin
So, what's the problem?
You don't have to share your theme.
Until they fix the license...
All of the expert opinions that I have solicited agree that, until the Drupal licence is fixed, you cannot use Drupal for a custom theme for a client who pays for and gets a copy of the theme without making the theme GPL or less (eg. LGPL, Public Domain, etc.).
This is generally not a problem, since GPL does not force the client to distribute it, nor does it force you to distribute it, nor does it prohibit either of you from charging a fee for it.
The sticky bit is that as long as Drupal contains HTML or especially JavaScript which is contained in the output, you are required to provide the source code for the PHP of your web site to any visitor to your web site (this is the insanity that is GPL as it is currently written).
Additionally, you may not use any elements in a theme which you do not PERSONALLY hold copyright to or which is licensed in a GPL compatible manner. This is because YOU DO NOT HAVE THE RIGHT TO RELEASE THAT CODE UNDER THE GPL.
An example of code which may not be placed in a Drupal template would be Google Search or AdSense. You are specifically forbidden to re-license Google's code. Most code from third party ASPs has similar restrictions.
Style sheets may not be covered, as long as you let the browser fetch them separately (as opposed to having PHP include them). Be sure that the code specifies the sizes of all regions and images or the images may also be arguably part of the code.
lekei, please stop
lekei, please stop resurecting old threads to do this. This has been rebutted a number of times already and it's not helpful.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
not rebutted
The only rebuttals are from the same people who add "I don't know what I am talking about, but here is the way it is... if you don't agree seek legal advice".
Well the EXPERT advice that I have received is that the Drupal license is BROKEN and to keep on it until it is fixed.
The LEGAL advice, was that the risk is very low but the costs are very high.
You are wrong.
You are saying that "HTML and text that is delivered to the browser is inherently GPL'd." The expert you contacted said that this was a possible interpretation of the GPL, but that the intent of the Drupal developers obviously determined the ultimate answer.
Since the Drupal developers most passionate about keeping everything GPL'd have said explicitly that code is GPL'd while output-to-the-browser is not, the issue seems moot. Yes, clarification of the "code vs. output" issue in the Drupal license would be helpful. But your insistence that Drupal's license is a worst-case-scenerio requires that you ignore the words of the very expert you contacted.
From your past discussions, I gather that you're unhappy about Drupal's GPL status and the implications of it. Making those implications out to be more sweeping than they actually are helps no one, though.
--
Jeff Eaton | I heart Drupal.
--
Eaton — Partner at Autogram