The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#41
|
|||
|
|||
![]()
Thanks for the clarification on GPL Wayne.
The general point of my post still stands. It is about choice and attempting to (1) build a stronger community with the interest of all stakeholders at heart and (2) getting vbookie updated significantly. It's all about me. ![]() Cheers, ~Regs. |
#42
|
|||
|
|||
![]()
hi folks,
I wouldn't have a problem if somebody updates or modifies anything i made as long as they not claimn my work to be there's i hate that and i will do anything i can do p*** them.As long as you ask you can.I Also agree with the checkbox option mentioned earlier that would be cool ... |
#43
|
||||
|
||||
![]()
This thread has jumped off topic from the original question. If you post up code that fixes a problem in the author's mod is that against vb rules or not? You are not redistrubuting, selling or posting anywhere but within the authors mod nor claiming ownership of anything just helping other members to fix coding issues with abandoned hacks.
|
#44
|
||||
|
||||
![]()
That isn't what the OP asked, he wants to release a new version, not post some fixes.
|
#45
|
||||
|
||||
![]()
Sorry Paul, you are correct I must have overlooked the re-release part.
|
#46
|
||||
|
||||
![]()
More or less relevantly...the thought occurs that it would be nice that for modifications where support is marked as provided, it should be in exchange for clicking install. Not forcibly necessarily, but perhaps a message could be displayed when creating a post that the user should have marked a modification as installed before they request support.
Of all the times I've asked people to do so I've never seen a single person mind doing so, which makes me think that marking as installed is not necessarily thought to be as something that should be done for the mod author as well as for themselves, or that marking as installed is just not highlighted enough in general. |
#47
|
||||
|
||||
![]()
I don't think we could highlight it much more really, esp as most authors point it out in the first post again as well.
One of the things that was planned as part of the upgraded/downloaded/installed tracking system added this year was to send people a PM once a month, highlighting the mods they have (newly) downloaded that month, but haven't marked as installed. This has not yet been implemented. |
#48
|
||||
|
||||
![]()
Why not send all coders a agreement in which they agree to allow their hack to be ported/upgraded, if they don't support it/port it (or plan to do so) in an X amount of months.
It's a shame that so many good hacks are leaking from the value of vb.org Also related: Which inactive add-on would you like to see revived? Official vb.org hack revival request list |
#49
|
||||
|
||||
![]()
Well, people could port the hacks, but not take ownership upon it. The ownership of the code is still of the creator.
|
![]() |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|