Things to ponder on:
1) Primary and Secondary UPS/Generator to ensure good clean supply at all times. Depending on your power source and and stability, you may or may not need this. If you have a budget, go for it.
2) Primary and Secondary Temperature/Humidity Control to ensure a stable environment. Can get pretty hot in a Telecom room when AC is not working. Depending on your geo-location, you may or may not need this.
3) Raised Floor/Ceiling space to run cables. If budget allows, Cable Trays to run cables from one side of the room to another....could be done neatly and on a budget.
5) Position of Racks to ensure Accessibility....especially cable racks. You never know when you need to punchdown new cables and getting behind the little space behind a rack can be a pain. Make sure you can easily work around your server/cable racks.
6) Proper electrical grounding for all equipment. Ground the racks properly...equipment can thus be grounded via racks.
7) Physical separation of Electrical cabling and Data cabling as much as possible.
9) Physical Security to the room and building room is in. - Fire/Water Alarms. Temperature sensor if budget allows. Break-in protection...etc.
10) Position of Telephone - During remote support this can be a pain unless you have a cordless phone.
11) Consider how many people will be in room at same time.
Best way to start is plan a layout using some software. Position everything. AC/ UPS/ RACKS/ TELEPHONE/ PEOPLE IN ROOM.
Just some basic considerations....among others...
All the best!
Seem like they recommending it only for "critical vulnerabilities under active exploitation". For vulnerabilities where exploits increase as each day passes because of non-disclosure, I would want quick notification.
FTA and not quite in the summary:
“Our standing recommendation is that companies should fix critical vulnerabilities within 60 days — or, if a fix is not possible, they should notify the public about the risk and offer workarounds,” the two said in a blog post today. “We encourage researchers to publish their findings if reported issues will take longer to patch. Based on our experience, however, we believe that more urgent action — within seven days — is appropriate for critical vulnerabilities under active exploitation. The reason for this special designation is that each day an actively exploited vulnerability remains undisclosed to the public and unpatched, more computers will be compromised.”
Not Dutch but available in German, English and Vietnamese!
Here is the main page
It uses Blockly, a visual programming editor...
Its browser based and I think with your help initially, she can play around by herself eventually...
Here are some examples of what can be done:
If she likes drawing..you can use that as a relation to see if she likes this as well....
Here is one that someone did that creates a random pattern everytime....
Was not able to access the article linked btw. (or parent site for that matter).
Why not work with the good folks at archive.org and their Internet wayback machine?
Is it not a similar idea?
The Internet Wayback Machine folks could use the funding and would be achieving the same purpose, albeit not in a format that the library folks might want....but they could come to agreement.
There is an update on MVP Bill Reiss's blog now.
Seems like he changed his mind. He is now against the idea and has instead suggested allow Win mobile devices to be allowed to change their default browser.
Sounds like a good idea, effectively making IE, a tool used by the OS that has browsing functionality.
Effectively what he is saying is that the other browsers, can serve as browsers while IE is now reduced to a tool!
If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy.