Switching to the New Module Library

Module Discussion
255

About whether there’s any instructions: Only this thread, the welcome page and a recent post.

I’m sorry if the a recent post recent post is very technical - I did try to make it as accessible has I could. Please tell us which parts are hard to get, and I’ll try to do something about it.

I think your problem stems from an expectation that comes from the old wiki pages, and which I probably didn’t address well enough.

  • In the old Wiki pages, each module page was the sole entry for modules of a specific game - that is what I mean by a one-to-one relationship between wiki-pages and games. One Game, one wiki page.

    • The Wiki pages were owned by the vassalengine.org administrators (Joel and Tim). They, and they alone had the power to accept edits into those pages, including adding modules made by other users than those that already had modules on the page.
    • The users that had uploaded a module to a wiki-page had no special privileges tham those afforded by the administrators in an ad hoc fashion.

  • In the new game library, each game may be implemented by multiple projects. That is, game X may be implemented by project a, b, c, etc. and each project has it’s own page. That’s what I mean by a one-to-many relation between games and projects. One game, multiple projects (and even One-project, multiple games).

    • Projects are owned by one or more users. The administrators has no special privileges (unless they take them) over the pages.
    • Project owners can decide, without any administrative intervention, whether they want to
      • add a new owner to the project, or remove an owner (including themselves) from the project
      • add a new package (but they cannot currently remove a package)
      • add a new release to a package (but they cannot currently remove a release)

Hopefully, this clarifies the situation a bit. Pages (projects)

  • represent one implementation of a game as a module (but there may be others)
  • under the auspice of its owners.

In your case, you are not an owner of Waterloo, so you cannot add any release or package to that project. That means you have two options:

  • You can contact the current owners of the project and ask if they will add you as an owner. State what your intentions are, and also let them see a preview of your module so that they can access if it fits in with the current project (their decision - not anyone elses).
  • You can create a new project - say waterloo_woody8297 of which you will be the owner, and you have sovereignty over. You can set the game title to be “Waterloo” - there’s no clash - or even “SuperDuper Waterloo - much better than the old one” - it is entirely up to you.

I can see how coming from the older wiki-based system that this can be confusing, and I think we should try to explain this better - any suggestions are welcome.

Yours,
Christian

1 Like