#11. My Second Life: Sunset

Print Friendly

My team and I have been working on our Second Life building for open source and standards. This is what the building looks like at sunset:

IBM OS&S at sunset

To be clear, this is not for every one of the thousands of IBM people involved with standards and open source, just my extended team. We’re done with the third floor and have been adding desks for folks as they get set up in SL. We have some basic infrastructure things I want to improve, but the major work will be done on the second floor where we’re starting to construct what we’re calling the Open Source and Standards Solutions Center and Library as an IBM-internal resource. I’ll talk more about it as we get closer to completion.

I think SL does sunrises and sunsets particularly well.

Next: The office
Previous: Permissions
All entries in this series


  1. hmm. How are you going to do “IBM-internal” resources? Last I checked all the SL servers were outside the blue walls… so technically you can’t really put anything “IBM internal” on them. At which point your library is limited to materials that are cleared for external release… why even bother making it exclusive to IBMers at that point?

  2. Well, look at this way, just because something is not confidential to your company, doesn’t mean you make it open for all to read. The library, for example, would have links that go inside the firewall and so would not be accessible to the general public. So while the immediate material may not be confidential it may point to something that is. If you are having a holiday party in your building you don’t necessarily want people to wander off the street and join in.

    Having this does not mean we might not do something for all to access eventually.

  3. Yeah, that’s what I thought you would do. You may wish to check with your management or whoever is supporting these SL efforts to see if they’re OK with an internal URL being posted in the public space (SL permissions aside, it’s still a “non-IBM controlled space”). I’ve been chewed out for doing that already… supposedly an internal url is considered just as internal as it’s contents, so if it points to confidential materials, they consider it confidential. (yes, this is fairly silly.)

Comments are closed