IBM
- IBM has canceled its biggest developer conference of the year over coronavirus concerns.
- IBM Think was set to be held in San Francisco in May, but it will instead it will hold a digital event.
- IBM also placed restrictions on employee travel, including limits on domestic work travel and a ban on attending events with more than 1,000 people.
- In a statement, IBM said: "The health of IBM's clients, employees and partners is our primary concern. In light of global precautions for the COVID-19 Coronavirus, and building upon recommendations from the World Health Organization (WHO), IBM is taking a new approach to its signature events and adopting new travel policies."
- Visit Business Insider's homepage for more stories.
As the coronavirus continues to spread around the globe, IBM is canceling its biggest developer conference, limiting employee travel, and restricting employees from participating in events with more than 1,000 attendees.
IBM's client and developer conference IBM Think, which brought 30,000 attendees last year, was supposed to take place May 5-7 in San Francisco. Instead, IBM announced Wednesday that it will now hold a digital event with "live streamed content, interactive sessions and certifications and locally hosted events, which will highlight IBM's technology and industry expertise for developers and clients without the risk of travel."
See the rest of the story at Business Insider
NOW WATCH: Most maps of Louisiana aren't entirely right. Here's what the state really looks like.
See Also:
- Microsoft says it's open to some staff working from home after employees criticized the company's response to coronavirus concerns as weak
- A false rumor about an Austin tech worker with coronavirus keeps spreading, and it shows a big challenge facing modern companies when information moves at viral speed
- Google Cloud cancels its biggest conference of the year over coronavirus fears
SEE ALSO: Google Cloud cancels its biggest conference of the year over coronavirus fears
from Feedburner https://ift.tt/2VJiAkn
No comments:
Post a Comment