What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Developer Rules Update

Hawker

Well-Known Member
Joined
Jan 15, 2010
Messages
2,509
Reaction score
70
At the moment, a lot of projects are stalled and we are getting endless PMs from developers about re-use of code.

To encourage development of new projects and re-use of existing code that is out there, we are treating all CC/Plugins as being under the BSD licenses - Wikipedia, the free encyclopedia. What this means is that anyone can re-use code or a project provided the original developer is given full credit.

The new rules are here: http://www.thebuddyforum.com/honorb.../12433-rules-cc-plugin-development-rules.html

If you see your code re-used in another project, or even used as the foundation of another project, feel free to PM the developer and remind them that you own the copyright in your code and that the license it was released under requires you to get full credit. As an example of how its done, here is the old credit list from one of my Glider classes.

Code:
/****************************************************************************************
* 
* Pontus wrote Parrior and PShaman.  This class uses the PVP logic of Parrior and 
* the mana management logic of PShaman.  
* 
* Birt wrote Baladin based on PShamanPather.  This class uses the buff logic and some of
* the heal logic from Baladin.
* 
* The config dialog and the #define logic for Ppather is based on the work of pontus and djragect.
*  
* Please do post details of any bugs you find on this thread:
* http://vforums.mmoglider.com/showthread.php?t=152030
* 
****************************************************************************************/
 
So what this basicly means is that you could see loads of CCs that just contain small edits of another developers code?
 
So what this basicly means is that you could see loads of CCs that just contain small edits of another developers code?

Exactly. The original developer will get his credit and if someone wants to take things in a new direction, its all good.
 
As with what Hawker said, we'd like to see that "small edits" stay with the original developer's codebase. (Having an entirely new CC that only changes 3 lines, really is just clutter.)
 
Exactly. The original developer will get his credit and if someone wants to take things in a new direction, its all good.

Hmmm..
Somehow i don't agree with ya.
Basicly this means, that if someone makes a copy of a developers CC - he'll give the original CC developer the credit.
Then when the next lad comes and makes another copy, then the original CC developer will not recieve credit, but the one who made the first copy will (eventhough he might just have edited 2-3 lines)

In my oppinion, i'd say it'll make some developers less happy with making projects (personal opinion though)

As with what Hawker said, we'd like to see that "small edits" stay with the original developer's codebase. (Having an entirely new CC that only changes 3 lines, really is just clutter.)

Exactly, it is just clutter - but that's what you could risk
 
As with what Hawker said, we'd like to see that "small edits" stay with the original developer's codebase. (Having an entirely new CC that only changes 3 lines, really is just clutter.)

Sometimes those 3 lines makes all the difference in terms of improvement.
 
all coders are using the same codebase, and as i always say its a community driven idea. credit where credit is due but in fairness if you credited everyone who has used the same code previously the list would be endless.

on the other hand, just repeating a post and claiming credit should be bannable tbh its very disrespectful, and tbh a bit sad.

i do agree that edits should be in the original authors post otherwise it becomes ridiculous but the notion that people are copying your work is silly. if people do create new threads which are "tweaks" the threads should be archived and a link to it added in the original author post, if he/she objects to it it can be removed.

i think that some people need to remember that imitation is the highest form of flattery.
 
For most developers the purpose of a public release is to get free testers and to showcase their ability while making a contribution to the community.

If you get to the point where someone copies your code and credits you, you have got all 3 done. Yes there will be people who release with 1 line changed and then vanish. That doesn't matter as (a)they will not have users - you will and (b) it costs you nothing. They key issue is to give credit.

The Glider and OpenBot communities both had big development groups because code was freely shared and you could make what you want re-using work that other people did instead of re-inventing the wheel. Now that HB is over 2 years old, we should aim to have the same.

Kickazz, it applies to profiles and quest behaviours just like combat routines.
 
I agree with both Hawker and Ossirian.

Imho opinion, it should be abput helping the community.
 
Let me see if I understand this...

If I spend several weeks with countless late nights and every spare moment of my weekend developing a project; as soon as I release it anyone can come along and copy my entire project, change a few (or more) lines of code relabel it and call it whatever they want as long as they give the original developer credit?

Case in point, DayWalker this is my Warlock CC that has been taken without my permission and has been renamed and rebranded to appear as though it were from another developer. Previous to today the only acknowledgement of my work was a simple statement saying some parts of the code where by Fpsware. When in actual fact the entire project is by me and he has made some modifications.

So to surmise ... There is no longer a requirement for the original developer to grant permission to allow someone to use their code or entire project? As long as someone gives credit to the original developer they have carte blanche to do what they want with the code or the entire project?


EDIT: added case in point.
 
Last edited:
I just developed for my own so far and I'm not really planing to make something public.
But I have to agree with fpsware.
 
You know, when you (FPS) put it like that, it's hard to disagree.
Can you guys maybe change it to be able to share code, but not be able to take a whole project, change a few lines and rename it?

EDIT: This seems like it'll be discouraging to the people that put in hundreds of hours into doing quality work.
The only people that benefit is the people that just make simple things, that would be able to take stuff from the really knowledgeable folks.

I think things are fine the way they are now. If anyone wants to use code that someone else made, they can ask for it, and the author should have the right to say no.

My 2 cents.

EDIT 2: @ FPS: WOW man, did someone that was supposed to beta test your CC just took it as his own!?
 
Last edited:
EDIT 2: @ FPS: WOW man, did someone that was supposed to beta test your CC just took it as his own!?

Not my recent work, not the project I'm currently developing. It was my currently released one.
 
I guess the change in rule can be linked directly to one of our members going mental because different people "lend" hes code? whom also are on a "timeout"?

If I spendt my freetime coding for others I would just exclude any "competition" simply by:

1. Make a good base.
2. Lisiten to the feedback from the users.
3. Update my code.

If I were to release a CC that the community requested, and released a "beta" that I was suppose to update, but didn't, I would never care who took the code for them self.
 
Just have a seperate sub forum called "Modified CCs" or something.
Only ones allowed in there would be full CC copy/paste with minor code edits. Fanedits if you like.
Also only allow CCs that are stated by the author to be allowed to be improved upon and reposted in said forum.

I mean seriously. If the original CC author gets full credit in those situations would there be an issue? If anything it should improve the size of coders E-peens by the fact they coded something that someone else built upon. Again, as long as due credit is given.

Case and point:

http://www.thebuddyforum.com/honorb...al/49130-cenarion-circle-text-quest-turn.html

All i did was add a couple of profiles and added a few things. I didn't write the whole logic or Hotspots but i did give credit to the people that did. And yes i do consider Profiles as 'code' aswell.
 
I guess the change in rule can be linked directly to one of our members going mental because different people "lend" hes code? whom also are on a "timeout"?

If I spendt my freetime coding for others I would just exclude any "competition" simply by:

1. Make a good base.
2. Lisiten to the feedback from the users.
3. Update my code.

If I were to release a CC that the community requested, and released a "beta" that I was suppose to update, but didn't, I would never care who took the code for them self.
there where multiple problems from multiple developers. not just one person.
 
Maybe if the code had turned abandonware this could work but with both the original developer and the modders in the mix it will probably get messy. Fps wasn't too happy and he wasn't even maintaining the CC at the time. Think about how furious someone actively working on a project would be.

Imagine someone just altering a few hotspots and then releasing Kick's questing profiles as his own...
 
I am not a developer but I would hate to have some of the CC developers leave the forums because of something like this. I think a good option would be to allow active developers release cc's as a dll so their active work won't be taken without permission. I feel this would allow people to actively develop their own work. Also after (x) months/days of no response from the developer the CC could be released to the community to continue as they wish. Just my 2 cents, and I'm not even sure if it is possible.

Saif
 
Back
Top