One of the most important functions of the JMS is to push the Amiga platform forwards. This will be achieved by taking our short, medium and long term strategies and dividing them into development domains. A development domain is an area of hardware of software that needs to be moved forward. Where private individuals and developers are pushing forwards in a domain, we will offer them whatever support we can; where there is no development, we will draw up our own projects to advertise among members and possibly outside the society. With this marriage of user talent, Society guidance and organisation (and hopefully funding), we will be able to benefit all Amiga users.
In pursuing our policy of complete openess, all projects will be fully documented as they progress by the individual Project Managers. This will become the place to see suggested projects, pending projects, projects that may receive funding and projects in progress. Any member can propose a project - an individual, a committee, or a member of the web team. We will also work together with the Industry Council. Projects may be anything from a consultative document, through datatypes and plug-ins to major tools such as a Project Management system. Quite what we do with the results of these projects afterwards is under discusison - we might release them as articles, shareware, or maybe CD-ROM collections. We need to make a bit of money for the Society since membership fees probably won't cover everything we would like to do.
Anyone interested in taking up a project should read the project guidelines and project template and perhaps take a look at a few of the projects currently being worked upon. Each Project Manager must adhere to these two documents as a minimum, but the style of their "project rooms", their project icons, and their whole approach to the project can be as unique and individual as they like. We want even the work to be fun!
Note: Most of these project descriptions were written by Fleecy in typically enthusiastic mode, several months ago, rather quickly. Some of them may seem to verge on the impossible and some points may have become moot or no longer accurate in this time. Don't consider them hard and fast rules; as a project manager you should be able to adapt or reinterpret your briefing before you begin.
|Project No.||Project Name||Status||Last Updated||Project Manager||Description|
|15||Toolbar Gfx||Open||23 April 1997||A few little graphics|
|14||Projects||Open||14 April 1997||How to "do" projects|
|13||Database||Assigned||16 April 1997||John J Karcher||Proper DB assessment|
|12||VRML||Open||12 April 1997||VRML assessment|
|11||Summary||Open||12 April 1997||Mailing list summaries|
|10||U.N.C.L.E.||Assigned||25 March 1998||Mario Saitti||UNiversal Client for cyberLife Extension|
|9||Multi-linguarity||Assigned||23 April 1997||Rudi Chiarito||One message in many voices|
|8||The Bazaar||Open||10 April 1997||Our very own market-place|
|7||Project Entry||Open||10 April 1997||The beginnings of a project management tool|
|6||Articles||Assigned||18 September 1997||Cade Hannan||Present the Articles and manifesto|
|5||Security System||Assigned||24 April 1997||Sam Stickland||Secure the site and functions within it|
|4||Member List||Assigned||20 April 1997||Sam Stickland||Membership and resource subsystem|
|3||Virtual Ledger||Assigned||10 April 1997||Paul Kenneth Egell-Johnsen||Entry and analysis subsystem|
|2||Graphics||Open||25 March 1998||List of graphics to be done by members|
|1||Text skeleton||Completed||9 April 1997||Fleecy Moss||Set up skeleton, links, write phase 1 project specs|
All pages on this web site are copyright 1998 Jay Miner Society.