Checklist:
1) Date and time
Weekend. Can't really pick a particular day, because Saturday for me is Sunday for Mr. Kiwi. I can do a Friday morning, which would be Friday night for you, and Saturday morning for him. In any case, I'm sure something can be chosen using the thing he set up:
http://www.timeanddate.com/worldclock/meetingtime.html?iso=20150207&p1=22&p2=16&p3=234
2) Lay Out
Lay out should be exactly the same. Location of lane changers, pit lane (and length), borders.
I agree with your stipulations. Setting up the track continuity should be left to the host. If you're happy with no taps but your tracks are well crimped, that's fine by me. I'll probably go that route, though I do have two pieces I set up to jump power from near the bad to away from the base (though physically close) that I used for my party tracks, and would probably use.
For the layout, I can post a TrackPower file with my current stock of spare track, if anyone thinks it's helpful. It could be shared around so that each person removes stock they do NOT have, which should leave us with a file with stock we ALL have. Then we can all propose layouts from that stock?
3) Cars
My proposal Scalextric GT cars and name a few models (C-numbers)
Out of the box, no magnet, third party tyres, standard chip.
I think that pretty much covers it. I'd go with easily sourced urethane tires. They give good grip, and do not benefit from softening treatments. Allowing them to be glued and trued would get a big vote from me.
4) Event settings
Practice, Qualify
I'm not sure how this would even work? I figure, practice as much as you like. If not, then there should be a rule that one CANNOT practice until the designated time, so that the track is just as new to everyone racing.
Ideally, there should be at LEAST two cars on each track, even if one is a fixed speed pace car with random lane changing. It just wouldn't have the excitement if it were just one car running laps at each location. If there are more than one live driver on a track, let them decide where they grid. In the overall scheme, it shouldn't really matter much. In practice, unless there are 3 or more cars on the track, it won't matter at all.
Endurance (1 hr, 2hrs ?, ..)
Tyre wear (weather is random but you can use hard and soft without weather simulation)
I like the idea of weather, but we should be able to set it to 3 changes, and keep resetting until we all get the same, pre-determined pattern. The question is, will they change at the same time, or randomly?
Available sets of tyres - Depends on weather
Tyre change time - I have no preference
False start - That would be tricky, especially if we're trying to coordinate the start timing with internet lag. For RCS64, it's just a stop and go, rather than a restart like some other options, so I don't mind using false start detection.
Race end - I like it when all cars finish the lap they're on.
No track call (Marshalls). Yeah, it has to go without stopping. So that means I will definitely need a DRAWW member to participate.
Throttle profiles ( I would say no limit) - I agree. With RCS64, fuel burn is based on CAR speed, not Throttle level, so the profile should not effect fuel burn apart from giving the driver a curve that fits their style and car.
Brake setting (Dynamic/no brakes/button all allowed). For magless, I like dynamic brakes. If we go with stock Scaley GT and urethane tires, I'd want to use them. But, I have no problem letting people choose to use brakes or not. That said, with tire wear and weather and all that, I might go brakeless.
5) Racing Rules
-No contact ( we can check the new DiSCA rules, and/or the Scalextric WC rules)
Fine by me. As it's likely to be just one car (and maybe a pacer) on my track, this shouldn't have an effect on my race.
-Stop and Go (when to apply)
For contact?
I think the best would be to have at least 2 people at a track, they act as a team and switch during pit stop. When not racing, you marshall.
I agree. In this case, we also need to decide when drivers must, or may, switch. For example, ALL pit stops? After a certain number of crashes? Only refueling stops? Etc.
No limit to amount of teams on a track, however I would say 2 or 3 teams (4-6 people) per location would be good.
That would be good, but given the time constraints, unlikely to happen for most locations, and especially unlikely for mine.. unless it manages to fall on my Sunday between 2 and 6pm. ;-)
No limit to amount of locations where the racing is being held. For this first event, the limit will be teamviewer (or alternative) limit. And even than we can keep track of what is happening. A Print Screen every 5 minutes would be good in any case.
For which we'll definitely need a spare person working the computer. This could be the track marshal at the moment. Those using wireless control can crash and dash. ;-)