# Suggestion

**URL:** <https://forum.vassalengine.org/t/suggestion/235>\
**Category:** General Discussion\
**Created:** [February 4, 2008, 7:51am UTC](https://forum.vassalengine.org/t/suggestion/235 "2008-02-04T07:51:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![bsmith](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/bsmith/32/1_2.png) [@bsmith](https://forum.vassalengine.org/u/bsmith)\
**Post date:** [February 4, 2008, 7:51am UTC](https://forum.vassalengine.org/t/suggestion/235/1 "2008-02-04T07:51:13Z")

</div>

We should put a disclaimer (in red) on the “New Module” page of the website, something along the lines of:

“NOTE: When you submit an entry here, you are making the commitment to complete the module in a timely manner; This means you must be reasonably certain there will be a playable version available inside three months. If you are unable to complete the module yourself, you are expected to actively seek someone to take over.”

I know there are better solutions, but this one is quick and effective. It’s not worth a 100 message thread or hours of dev work. 🙂

Ben

---

<div class="post-metadata">

**Author:** ![rk1](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/r/9f8e36/32.png) [@rk1](https://forum.vassalengine.org/u/rk1)\
**Post date:** [February 4, 2008, 9:05pm UTC](https://forum.vassalengine.org/t/suggestion/235/2 "2008-02-04T21:05:13Z")

</div>

> [@](#):
>
> "NOTE: When you submit an entry here, you are making the commitment to complete the module in a timely manner

Why? Usually if a module appears to have been abandoned, someone can ask me to add them as a contributor. Or you can always make a new module. More effective would be something that cleans up old modules, or marks them as somehow inactive.

rk

Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [February 4, 2008, 9:42pm UTC](https://forum.vassalengine.org/t/suggestion/235/3 "2008-02-04T21:42:31Z")

</div>

Thus spake Jeffrey Brent McBeth:

> [@](#):
>
> Warning, I’m talking off the cuff, but would be willing to help. It seems  
> to me that it would make sense to have somewhere that modules were stored  
> unzipped, and committed to a revision control system with some scripts that  
> could rezip things into modules. Once that is in place, we could get more  
> explicit licensing declarations in place (probably one for the module/custom  
> code and one for the art), and require contact information for the submitte=  
> r.  
> The combination of those three would probably help change the culture a bit  
> more away from “ooh, someone is working on this, so hands off”, and more  
> toward more sharing (I hope).
> 
> Jeff

I agree, it would be nice to have more support infrastructure for modules.

On that note:

1. I wish we could get people to do something like GPL modules by default.  
That way, these issues would go away. (Yes, I’m aware that module authors  
might not own the copyright to all parts of a module, but what I’d like to  
see is people GPL-ing the parts of the module to which they do have  
copyright.)

2. The module pages currently on the site aren’t well suited for displaying  
information. I have something particular in mind here—I’ll create a  
mockup soon, but probably not before the feature freeze on Friday. What I’m  
imagining is having all of the info that’s currently under the four “tabs”  
be on one single page, along with some version compatibility information.  
(I think it’s important that we mark which modules are compatibile with  
which verisons of VASSAL.)

–  
J.

* * *

Messages mailing list  
[Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org)  
[forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org)

Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))

---

<div class="post-metadata">

**Author:** ![bsmith](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/bsmith/32/1_2.png) [@bsmith](https://forum.vassalengine.org/u/bsmith)\
**Post date:** [February 4, 2008, 9:54pm UTC](https://forum.vassalengine.org/t/suggestion/235/4 "2008-02-04T21:54:56Z")

</div>

> [@rk](#):
>
> Why? Usually if a module appears to have been abandoned, someone can ask me to add them as a contributor. Or you can always make a new module. More effective would be something that cleans up old modules, or marks them as somehow inactive.
> 
> rk

The problem is old modules which do not yet have any files attached, but appear to be active works in progress, like EuroFront. I’ve tried contacting the designer to no avail. If the game entry had not been there, someone else may have already had a module completed a year ago (like me). It’s a real shame to make it appear something is being worked on when it isn’t, it means players are left in the lurch.

I agree, there are better solutions, I just didn’t want to create more work for you guys or turn it into a big debate!

---

<div class="post-metadata">

**Author:** ![Brent\_Easton](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/brent_easton/32/10_2.png) [@Brent\_Easton](https://forum.vassalengine.org/u/Brent_Easton)\
**Post date:** [February 5, 2008, 9:07pm UTC](https://forum.vassalengine.org/t/suggestion/235/5 "2008-02-05T21:07:29Z")

</div>

> [@](#):
>
> 1. The module pages currently on the site aren’t well suited for displaying  
> information. I have something particular in mind here—I’ll create a  
> mockup soon, but probably not before the feature freeze on Friday. What I’m  
> imagining is having all of the info that’s currently under the four “tabs”  
> be on one single page, along with some version compatibility information.  
> (I think it’s important that we mark which modules are compatibile with  
> which verisons of VASSAL.)

Some thing I would really like to see is the ability to add modules into ‘categories’ like you have on Mediawiki, so we could group modules by genre, period, publisher, number of players etc.

* * *

Brent Easton  
Analyst/Programmer  
University of Western Sydney  
Email: [b.easton@uws.edu.au](mailto:b.easton@uws.edu.au)

* * *

Messages mailing list  
[Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org)  
[forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org)

Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))

---

<div class="post-metadata">

**Author:** ![uckelman](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/uckelman/32/10020_2.png) [@uckelman](https://forum.vassalengine.org/u/uckelman)\
**Post date:** [February 6, 2008, 11:22am UTC](https://forum.vassalengine.org/t/suggestion/235/6 "2008-02-06T11:22:28Z")

</div>

Thus spake “Brent Easton”:

> [@](#):
>
> Some thing I would really like to see is the ability to add modules into ‘cat  
> egories’ like you have on Mediawiki, so we could group modules by genre, peri  
> od, publisher, number of players etc.

That would be really easy if we were using MediaWiki.

–  
J.

* * *

Messages mailing list  
[Messages@forums.vassalengine.org](mailto:Messages@forums.vassalengine.org)  
[forums.vassalengine.org/mailman/ … engine.org](http://forums.vassalengine.org/mailman/listinfo/messages_forums.vassalengine.org)

Post generated using Mail2Forum ([mail2forum.com](http://www.mail2forum.com))
