[Nikidala]

Well, my personal feelings are:

If it is a "unique" idea (unique as in one that not every other forum software has, or maybe a non-major feature of say one forum), give the original hacker(s) a CHANCE to publish it themselves first (atleast). The "new" hacker could either contact the original hacker(s) to let them know that the "new" hacker coded there own and would like to share it, and ask the original hacker(s) if they plan on releasing a vb 3 version or atleast give them 2-3 months of vbulletin.org allowing vb 3 hacks (being the mainstream hack forum) to release it. AND, if you do release a hack that has already been released, give credit where credit is due. If you made the hack because the loved their vb 2 version or because you saw the title and thought "hey, I wanna try doing that one my own way", acknowledge the original hacker(s) work, imagination, and inspiration (to you) in your hack description.

I have seen many hacks with a intro saying something to the effect of "Many thanks goes to {person}. Their {original hack} was the insipiration for mine." or "My idea for the new and improved {hack} came from the great work of {person} on {original hack}." That way, they still get credit for their ingenius idea, good / great work, and original foresight inseeing that it would be a great hack... Now, don't copy their code, add a few lines, and think that adding a thank you will do, because that is even more of a slap in the face (besides being illegal in many countries, I don't know the laws in all countries)...

I see the hacks of this forum (and any other forum) as being a result of one of two options (again, personal feelings, I may be wrong):
1) The hacker saw / thought of an idea / feature that they wanted for their own forum, coded it, implemented it, loved it, and wanted to share it with the rest of the community (i.e. - major reason of hack was for personal use)
2) The hacker just wanted to create hacks that they thought people would want, but could live with or without it on their forum (i.e. - major reason was to release hack, whether for the betterment of the software, the community, or the hackers reputation )

If the "new" hacker fits into category one, then once they have it installed on their forum their appetite should be somewhat satisfied and the hack has fulfilled its reason for being. Waiting to release the hack for a few months or not releasing the hack at all should be not biggy, as releasing the hack would just be an added "benefit"...

If the "new" hacker fits into category two, then they shouldn't be coding the hacks that are already out there and created by someone else. Instead better the software, community, or especially their hacker reputation by creating a "new" hack. If the "new" hacker needs ideas as to what people want or what hack to create, they could vist my vb 3.1 feature suggestion thread on vbulletin.com. There are oodles and oodles of great suggestions in there. So of the suggestions are already hacks, but I have a feeling that a lot are not... The could find one that grabs their interest, check if a hack already exists, and if not have at it. Then, they have not only added to the software / community as a whole, but also created a name for themselves by being the FIRST to release that hack... It is not like we are at a stagnant put in the forum, where the forum contains every possible idea / feature or a hack exists for every idea / feature. Their is a virtual catalog of ideas already compiled AND desired (those are all features suggested by fellow members / forum owners) in one easy to access place...

Well, those are my personal feelings on the topic... Of course, I don't have any hacks yet, so I may think differently once I do...

On a side note, what you y'all think of (once vbulletin.org allows vb 3 hacks) me releasing my own spellchecker? I just modified my spellchecker that I created for phpBB to work for vb 3, and was hoping to release it as my very first hack (and it even works on the WYSIWYG editor, well sort of, I have a few tweaks to finish with the extra html crap the WYSIWYG creates but almost there). BUT, I don't want to step on any toes or offend anyone (I am assuming that one or several people already have spellchecker hacks for vb 2 out), so do you think I should or not? I don't mind not releasing it, but I have read several times on vbulletin.com that people have their spellcheckers working in vb 3 minus the WYSIWYG... So, yah or nah?!?