We would like to give high priority "to connecting people problems to present expertise". To do that, we propose to avoid in a first step a strong defacto per-category decomposition coming from the top for both plenary and parallel sessions.
Plenaries will be organized according to what coming people have to say or want to submit for discussions and brain-stormings. A priori, these sessions will be handled in mornings. If you have something to present or want debated, submit an abstract or a debate subject to the geant4-2000@lal.in2p3.fr mailing list. In order to help the local organizing people to select mails, have "abstract" in the mail subject for abstracts and "debate" for debate proposals. Plenary sessions will be organized in the next weeks according the incoming materials. A per-category organization could emerge, but not necessarily.
For the rest of the time, afternoons and time left in the mornings, we would like to give priority to concrete work at keyboards. The idea is to do at Orsay concrete "connection work", that is to say profit of presence of others (and of their expertise) to shoot problems or explore ways that you don't have time to spent on in your labs.
Things to solve are not necessary deep fundamental problems (like redesigning everything) ; it could be a nasty postponed debugging, an installation problem (number one problem with visualization and interactivity), a work on some doc, an improvement of the training-kit, a blocking point on a tricky geometry, connecting an analysis tool,...
To help organize in this way, we propose that each registered person prepares a "wish joblist" of "connecting problems" that you want to solve or move-on during the workshop. Send this list in the geant4-2000@lal.in2p3.fr mailing list (with "joblist" in the subject). All lists will be gathereed in the wish-job-list page.
One fundamental step will be that you look at other people lists and see what you can do for them. When a match is done and an "intention of work" is around, we suggest to put it also on the web (send the info in the geant4-2000 mailbox, we will compleete the item in your list) ; it could interest other people that could join the effort or be client of the effort. If there is a match, you will probably have to prepare the ground with people before coming at Orsay.
This being said, the organization of the "keyboard" sessions is obviously not clear yet. What is sure is that category coordinators could play a very important "gluing" role, then we ask them to survey the wish-job-list page.
In the list of things to do, we have also to help boosting "Geant4 clients" in their Geant4 implementations. Here comes the "comparison projects" but also other well defined projects using Geant4. In fact working on "projects" during the workshop enter in the schema very naturally. They could enter as status-reports in the morning sessions, but most important, they could enter naturaly in the afternoon threads of "connecting work" through the joblist of their representatives. Thinking in this way will avoid to lock everybody one full day on particular projects, and will permit to project responsibles to planify some concrete activity with the right persons at hand all along the week.
To finish the workshop, we suggest to reserve some time on Thursday afternoon for plenary demos for people that wants to show some realizations done in the week (others are welcome but with a lower priority). It is not clear that a "per-category summaries" on Friday make sense if things are not organized by categories. We can plan some summaries for the plenaries, but it could be interesting to conlude the keyboard sessions by a roundtrip-table by letting people have some 5-10mn summary of their week activity.
Your job now is to think for submissions for abstracts, debate-proposals and your wish-job-list. Then submit in geant4-2000@lal.in2p3.fr with in the subject :