> James Cradock, Jr. : Do we yet have one? Even an outline? Alain : Not yet. We are still throwing around ideas. Suggestions so far, concerning what to do first, as best as I can remember them : 1. OpenTalk Interpreter in C++ and/or Java. 2. OpenTalk Language, although I strongly suggest that we ally ourselves with the xTalk list in this regard. 3. 100% HyperCard-compatible OpenCard application, as a first step. 4. Design OpenCard as an entirely new app that is better but not necessarily compatible with HyperCard. 5. A small demo project to get the ball rolling. > James Cradock, Jr. : Let's analyze resources (coders v. testers)... Alain : That has been suggested already. We definitely must determine how much talent we have, in what, ... , availabilities, and so on. The collaboration infrastructure that I am currently developing for the OpenCard will indeed include a web-accessible database to gather info and manage this identification of our resources. > James Cradock, Jr. : ...and get working on an outline... Alain : And another web-accessible module that will allow the group to view and contribute to an outline of the who, what, where and when of the tasks that we will set ourselves. > James Cradock, Jr. : ...Heck, I'd almost be motivated to do a project > plan! Alain : Excellent idea. > James Cradock, Jr. : Alain? Alain : What I would like to see is a complete collaborative infrastructure that structures each step of the entire design & development process. That is what I am proposing to do for our group. Suggestions are welcome.
