New policy for the Community Prefix List, We need your feedback Options

[Baronius]

We had a discussion about the Prefix List with SConrad. He assured BWL that their intention isn't to boycott the Prefix Reservations list, and he offered a suggestion.

There are several registered prefixes which have never used to release any Infinity Engine game mod. Many prefix owners haven't informed the community that they have a mod under development. On the other hand, sometimes mod developers return to the community to release a mod for the public, which development they started earlier with a registered prefix.

It also seems to be true that many mod developers like to choose prefixes that they favour for some reason (monogram, initial mod name abbreviation etc.). I'm not really convinced that this should be an important aspect (as the problem is purely technical: identifiers, filenames shouldn't collide), but I have no right to decide this (neither the BWL Council or any department of BWL). If you believe it's an important aspect (or the opposite), please do post your opinion in this topic.

The Prefix List originally supported prefixes of any length, but since this easily leads to collisions, BWL decided to fix the length of 2 characters. I don't think this needs to be changed (especially because there are already very many two-character long registrations). On the other hand, due to the high number of prefixes (which include many apparently abandoned registrations), it's not easy for those to choose a prefix who want some typical, favoured prefix (monogram etc.) -- many variations are already registered by others, and often abandoned. To improve the situation, the best way would be to estabilish a new policy for registrations.

The new policy would assign a time limit for each registered prefix, and if no mod is released with that prefix for the specified time limit, the prefix would be moved to second list, and its place would be freed on the primary list. This means that it becomes available again for others' to register, and if someone registers it, the original owner would lose it. If no one registers it before the original owner returns, the original owner can re-register it (i.e. extend the time limit, but the added time limit would be much shorter than the base limit for prefixes). The number of such time limit extensions for prefixes which aren't used in any released mod could also be limited (for example, after all extensions are used, the prefix would remain in the second list and could be registered by anyone, and if it's not registered by anyone else and the original owner would release a mod with it, then it would return to its original owner; but these details require more examination than what I've done here).

If a mod is released with a registered prefix, it would be reasonable to allow the prefix to be valid for an unlimited time. On the other hand, it's important to deal with the situation when a single project with a prefix is released, the author leaves the community and there are no releases for years -- while the prefix is taken. In such an extreme case, I think it's enough to free the prefix for the public again, and simply designate the original (and old) project as incompatible with those mods who use the re-registered prefix (but "designation" probably wouldn't be the duty of the Prefix List maintainers).

I also have an idea about a restriction for registrations: a mod developer who registers a prefix will have to specify an Infinity Engine game where he or she intends to use the prefix. However, I am not convinced that this is necessary -- it might make things more complex, while wouldn't offer much additional advantage (most mods are for BG2 and BGTutu/EasyTutu anyway).

Assuming that the majority will support the initiative detailed above, it's important to emphasize that this requires technical changes on the management system of the Community Prefix List. As far as the implemenation changes are concerned, neither the Department of Graphics nor the Department of Mod Development of BWL has any free capacity (i.e. member who would volunteer) to my knowledge. I also don't have the time, however, someone will have to do it, if the initiative gets approved and accepted in this topic. If it's accepted, I will try to contact drake127, the developer of the current system, and ask him to extend the system. I suspect that the database scheme will have to be modified too.

Please note that the above descriptions (about new policies) are just based on quick ideas I had while writing this post, so feel free to suggest different or modified versions for them.

If you believe you have anything constructive to say (or you have any questions), please don't hesitate to send a reply to this topic!

I said to SConrad that this matter requires public discussion, and (more importantly) public approval. BWL has always taken the fact into consideration that not all mod developers (who may release public mods) are active in the message boards of the community, so the approving feedback of active forum members should not be considered as authoritative in all cases, but in this case, I think it is. The Community Prefix List has been estabilished and maintained by active IE mod developers (active in the respect of community forums as well), so making a common decision here is justified in my opinion.

[plainab]

What kind of time frame are you talking about before you take away a mod developers rights to a certain prefix? A couple months, a year or two? Some mods can take years to work on before it ever becomes public. This is specially true if they want to release a mod that is as bug free and compatible with as many other mods as possible. By forcing a time frame to release a mod, you will be potentially causing more bugs and problems to be introduced. This is something that you wouldn't like, no one would like it in fact.

If you were to proceed with this idea, you will need to make some things clearer. You will also need to allow for the events of real life getting in the way of making a mod. One person might make a small mod relatively quickly, but a group may take years to do a large scale mod.

Here is a suggestion which may work within your ideas.

1) All EXISTING prefixes remain assigned and cannot be revoked. No matter whether there has been a mod produced or not.
2) All NEW prefixes can be given a two year reservation lease.
3) Mod developer must return any time before or within one month after their two year reservation lease has expired to give a status update, mod release announcement, or some other proof that they are still working on the mod.
4) If public release of mod has been announced their leased prefix becomes permanent.
5) If their mod is in any other status, they get two more years where steps 3 and 4 will apply.
6) Should the mod developer fail to report after one month of either the two year renewal points, the prefix will be given a pending status for one year.
7) After that one year, the prefix will be released back into the pool of available prefixes.
8) During pending status, the original mod developer can ask to retain the prefix registration. However they must provide proof of the mod they are working on. i.e. zip package of current mod files; links to current forum posts where they have asked, received help, and tried it out on their work; any other source of proof so deemed reliable by the maintainers of the prefix list.
9) Should the mod developer have retrieved their prefix from within the one year pending status, they will follow the same procedures as above except that their leases will be limited to one year and a pending status of six months.
10) One month prior to any renewal the maintainers will send an e-mail to the address on file reminding the mod developer of their upcoming prefix renewal date.

Basically under the above suggestion:
Anytime modder reports a release of their mod the prefix becomes permanent.
As long as modder reports progress they will retain their prefix.
If modder fails to report within a timely period but reports, the will retain their prefix but for shorter time periods.
If modder fails to report at all they will eventually loose their rights to the prefix.

Shortest time to loss of prefix
(2 years + fail to report) + (1 year pending + failure to report) = 3 years

Shortest time to permanent prefix status
Mod is announced < 2years from prefix reservation


But in the long run, I'm siding with Kulyok. We reserved the prefixes so that there would be no overwriting of custom files. Who knows, someone may have made a personal mod and wanted to reserve the prefix so that public mods wouldn't overwrite their custom files....

[The Bigg]

What kind of time frame are you talking about before you take away a mod developers rights to a certain prefix? A couple months, a year or two? Some mods can take years to work on before it ever becomes public. This is specially true if they want to release a mod that is as bug free and compatible with as many other mods as possible. By forcing a time frame to release a mod, you will be potentially causing more bugs and problems to be introduced. This is something that you wouldn't like, no one would like it in fact.

You don't need to release a mod IMHO, it's better to prove you're working on the short term rather than vaguely promising to completing long term.