Difference between revisions of "User talk:Dee"
From HashVB
m (Reverted edit of 85.255.114.132, changed back to last version by IQJunkie) |
(→Licence) |
||
(4 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
Dee rocks ! | Dee rocks ! | ||
+ | |||
+ | == Licence == | ||
+ | |||
+ | What licence applies to the content of this Wiki? If I found some code or text here that I wanted to put in the [http://en.wikibooks.org/wiki/Programming:Visual_Basic_Classic Visual_Basic_Classic] Wikibook, could I do that without violating any licence conditions? All content on Wikibooks has to be either GFDL or public domain. [http://en.wikibooks.org/wiki/User:Kwhitefoot Kevin Whitefoot] <kwhitefoot@hotmail.com> | ||
+ | : I'd say it is GFDL, but as I haven't thoguht about it until now, I will ask the other contributing authors. Does GFDL allow me/us to request a link/reference back to this site? --[[User:Dee|Dee]] 16:35, 12 Apr 2006 (BST) | ||
+ | ::I have no idea if the GFDL itself would let you ''require'' a backlink but it is generally regarded as good form to credit sources even if they are licensed under the GFDL. The book has a module specifically for credits and permission statements, see [http://en.wikibooks.org/wiki/Programming:Visual_Basic_Classic/Credits_and_Permissions Visual Basic Classic/Credits and Permissions]]. There is also a section on the contents page listing the [http://en.wikibooks.org/wiki/Programming:Visual_Basic_Classic#Authors_and_Contributors major contributors] including those who contributed indirectly by giving permission for their code and documents to be used. What I usually do is to summarize the contributors and contributions on the contents page and put the details of the credits and permissions on the Credits and Permissions page quoting email messages etc. | ||
+ | |||
+ | ::Of course if you have time you could contribute directly (I need a smiley that hints at desperation!). --[[User:Kwhitefoot|Kwhitefoot]] 20:00, 17 Apr 2006 (BST) | ||
+ | |||
+ | :::Personally, I'm happy for it to be GFDL and I'm currently checking with the other contributors are as well. | ||
+ | :::Which parts are you interested in using? :) | ||
+ | :::--[[User:Dee|Dee]] 15:29, 18 Apr 2006 (BST) | ||
+ | |||
+ | ::::No idea yet. I've been a bit lazy lately. Basically anything that looks like it could fill holes in a textbook, anything that counts as best practice, optimal coding. --[[User:193.216.134.221|193.216.134.221]] 23:01, 18 Apr 2006 (BST) |
Latest revision as of 22:01, 18 April 2006
Dee rocks !
Licence
What licence applies to the content of this Wiki? If I found some code or text here that I wanted to put in the Visual_Basic_Classic Wikibook, could I do that without violating any licence conditions? All content on Wikibooks has to be either GFDL or public domain. Kevin Whitefoot <kwhitefoot@hotmail.com>
- I'd say it is GFDL, but as I haven't thoguht about it until now, I will ask the other contributing authors. Does GFDL allow me/us to request a link/reference back to this site? --Dee 16:35, 12 Apr 2006 (BST)
- I have no idea if the GFDL itself would let you require a backlink but it is generally regarded as good form to credit sources even if they are licensed under the GFDL. The book has a module specifically for credits and permission statements, see Visual Basic Classic/Credits and Permissions]. There is also a section on the contents page listing the major contributors including those who contributed indirectly by giving permission for their code and documents to be used. What I usually do is to summarize the contributors and contributions on the contents page and put the details of the credits and permissions on the Credits and Permissions page quoting email messages etc.
- Of course if you have time you could contribute directly (I need a smiley that hints at desperation!). --Kwhitefoot 20:00, 17 Apr 2006 (BST)
- Personally, I'm happy for it to be GFDL and I'm currently checking with the other contributors are as well.
- Which parts are you interested in using? :)
- --Dee 15:29, 18 Apr 2006 (BST)
- No idea yet. I've been a bit lazy lately. Basically anything that looks like it could fill holes in a textbook, anything that counts as best practice, optimal coding. --193.216.134.221 23:01, 18 Apr 2006 (BST)