Events

Mon 16 Dec 2002
BSUG Antwerpen, Roots
Plan: Go together by car, Reinout will not drive but he will get drunk for us.
Mon 6 Jan 2003
Amstug meeting Jan 2003
Fri 17 Jan 2003
Vrijdagmiddagsessie Amsterdam, Soops
We will have a presence, but not a booth (Reinout will inform Soops of this). We will make detailed plan on 6 Jan.
Smoking:
allowed during non-coding meetings but during worksessions smoking is only allowed outside.

Dialect-wars

Everyone is working with either VW or VA so with only two dialects we will wait until we have code exchange problems that are bigger than we are willing to bear before we are going to devote group resources to solving them. Until then everyone will publish code at least in native format and optionally in other formats too.

To Do

Job and Peter will complete the type system domain objects export (code and object files), so the objects contain all required information for type-verifying all messages. This includes encoding the tables for the messages with dynamic return types (dependent on the types of the participating objects).

Reinout will set up a web context ;-) at http://amstug.desk.org, thanks Reinout!

Everyone should feel free to edit when they feel it will improve the site.
I propose to refer to this place on the Internet as "the Amstug website".
When publishing code by uploading to the Amstug website, I propose to include author name and publication date in the file name (and of course an indication of what the code is for), plus indicate the format in the file extension, like so: reinout 1dec2002 TypeWalker.vw7parcel

Someone will approach someone at some company with a plan that will give Amstug access to the official commercial VW distribution for Amstug work. This needs to be concretized, it seems :-).

Dolphin is another dialect for which an Amstug group license would be useful.
Not only the newest versions of each dialect are relevant; we want to test older versions as well.

Money

For the foreseeable future, is has been decided that money is not a problem; it just has to be there.

Should we at some point have the opportunity to get money for Amstug products/services, we would be happy to use that to finance Amstug activities. So if some of our work will turn out to have significant commercial value, we will not see that as a problem. Remember that the code from Amstug projects will be published without usage restrictions from our side.