JJ - I did receive the newest files.
Teamwork Pattern suggestion:
Team CORE-Text (how's that? how about TCT?) - I'd like to suggest a way for us to start:
We could take one file - say the Altmark file - and work on it in this thread, event by event. JJ takes the lead. He would put out his reformatting of the first event. We then discuss it to make sure we're all on the same page with the style and so forth. Then take the next event and so on.
By the end of the file we should be quite in tune with the format and how to implement it. After that we should be able to split up the work load and work separately, without the fear of slaving over some files that will meet up with resistance or outright rejection.
Does that sound like a good idea?
Event Alterations
Further, if we want to expand any of the events by including (where applicable) an alternate option to make no decision or take no action, I think we need to contact Steel on that. Here's what I'd suggest:
We divide up the files into sections. We as a team work on one section at a time, each of us taking a few files (once we have our working pattern established). JJ should look over each section of files before we farm them out for re-working and determine which ones he thinks should have the extra option(s). I say JJ because it's not something I want to spend time on. Then forward each file to Steel with the suggested options. He'll approve, disapprove, or discuss the suggestion with JJ. Once a decision is reached, then forward that batch of approved files to the team for re-working.
So it's:
1) divide files into sections
2) take the first section and JJ should determine alternate option suggestions - forward to Steel
3) after final decision on said section of files, forward those to the team to have them re-worked
4) rinse and repeat
-PK