SEOUL The annual U.S.South Korea joint military exercises currently underway have historically been a very public demonstration of force intended, in part, to counter North Korea's aggressive nuclear and missile tests. But with looming diplomatic summits aimed at reaching a deal to end the North's nuclear program, media coverage of the drills has so far been limited. This week, the U.S. Second Infantry Division held a public tree planting ceremony at Camp Casey in South Korea, near the inter-Korean border. "It is my belief that this tree, like those that have come before it, shall symbolize the roots that bind us together, and to our past in an enduring way," said General Jon Howerton, the deputy commander of the U.S. 2nd Infantry Division, at the event. The journalists attending the tree ceremony were also permitted to watch a shooting competition to determine the best marksmen in the participating U.S. and South Korean divisions. The Camp Casey event was one of the few joint military training activities that news organizations have, so far, been allowed to cover, and it illustrates how the United States and South Korea are downplaying the offensive component of this year's combined exercises. "This is clearly in order to send a signal to North Korea that South Korea and the United States are not willing to escalate the situation any further," said Go Myong-Hyun, a North Korea analyst with the Asan Institute for Policy Studies in Seoul. This year's Foal Eagle and Key Resolve combined military exercises are similar in scale to past drills, with more than 23,000 U.S. troops and 300,000 South Korean forces engaging in joint battlefield maneuvers, and responding to computer-simulated attacks from North Korea. But the start of the drills was delayed this year at South Korea's request to set a peaceful tone for the Pyeongchang Winter Olympics in the South and to facilitate the North's participation in the games. After the end of the story, General Howerton probably is - retired - still in the same position - was promoted - not enough information
still in the same position

One of the challenges that every community faces, particularly teams inside a larger community, is the ability to coordinate what goals and ambitions the team is going to work on. Traditionally this has always been somewhat ad-hoc: people join a team and work on whatever they feel like. Ideas are ten-a-penny though. For most teams that work on larger projects (such as events, software, products and more) to actually be productive, coordinating this work can be complex: some projects require coordination across many people with different skill-sets, time-availability and resources. Something I would like us to work towards in the Ubuntu community is encouraging a culture of best-practise in how we plan our work and coordinate our awesome teams to work together on projects. I believe this kind of coordination can help our teams increase the opportunity for success in their work, feel more empowered and productive and provide greater insight to people outside those teams on what the team is doing. An effective way of doing this is to build a Roadmap for each cycle. This provides an opportunity to capture a set of goals the team will work together to achieve in each six-month period. This article outlines how to build such a Roadmap. While at first a roadmap can feel a little like a nod to the gods of bureaucracy, they actually possess many benefits: * Direction one of the biggest complaints teams often report is a lack of direction. If a team gets into the habit of creating a roadmap at the beginning of a cycle, it gives the team a sense of focus and direction for the coming cycle. * Documented commitments are more effective a common rule in Project Management training is that actions assigned to people in a shared document are more effective than ad-hoc or private commitments. By documenting who will work on what in a cycle and putting their name next to an action can help seal a sense of accountability for their contributions to the project. * Feeling of success regularly revisiting a roadmap and... What is probably true about the narrator? - He enjoys ideas that are ten-a-penny - He loves bureaucracy - He cares about open source community - not enough information
He cares about open source community

So, I worked with a friend of mine who was a playwright to put together a play to take to the Edinburgh Fringe Festival. It was a three person show, and one of the roles was written specifically for me. Many of the lines were written after we improvised the scenes in my living room as she wrote the piece. Took it to Scotland, where it was quite well received. A year or so later, it was being produced in New York in a much more prestigious setting. I auditioned, was called back a couple times, and got to the play the role again. Fantastic! THEN, it was produced by an even larger theatre. Different producer, different casting director, etc. I went to the open call for it, and the casting director treated me really poorly. It was odd. She looked at my resume and said, "It says you have already played this role." I said, "Yes, I was fortunate enough to workshop it and originate the role." She looked at me like I was lying. I mean, shuttled me out the door like I was a crazy woman. Needless to say, I was not called back. And that was okay(I mean, of course I wanted to do the show with this group of people, but hey, we can't always get what we want). Fast forward to opening night: my playwright friend invites me to see the show. The actress playing "my" role was fantastic, but they had to change lines in the script that indicated what she looked like, because she was of Hawaiian descent. Again, no big dealand she was great! What was strange was meeting the director that evening. My friend introduced me as the originator of the role, and the director asked me why I hadn't auditionedOverall, it wasn't a harsh rejection or a terrible story, it was just weird to have been treated like a liar when I was not lying What country did the actor perform the play where it was well received? - Portugal - Scotland - Spain - not enough information
Scotland

"Hon? You still awake?" Quiet. Jan pulled herself out of the bed and stood up, looking around the dark room for anything. She needed something, something that she could grab onto, and hold, hold until it hurt, hold until blood made racing red lines down her arms, until her hands were raw. She left the room and walked quietly into the now guest room that had been Rob's. Opening the closet, she found the teddy bear that Rob had once confided in and held it in her arms tight as she slumped down on the bed. A quiet sobbing rang through the house accompanied only by the chime of the grandfather clock in the living room every fifteen minutes. As Jan lay on the guest room bed she soon resorted to deep gasps, knowing that meager tears would never be forceful enough to express her worry to those that listened. "Just bring him home, bring him home, bring him home," she mumbled over and over, each time changing the tone slightly in a desperate attempt to make her pleading sound more real. She could hear the occasional snore of her husband and she hated him for it. What kind of person could find sleep at a time like this? Why wasn't he awake worrying? Why wasn't he with her? Her thoughts became dark like blood, evil little monsters eating at her sanity. If her son was crazy and not just a drug addict she could see how easy it was to fall over the line. "Please God, please God, please God, please Rob, Please Rob, Please Rob, Please Rob." Soon, a sleep came but it was peppered with demons. And as the sliver of sun peeked through the window, she held her false self-control tight and said little. How does Jan's husband feel about his son? - misses his son - worried about his son - not enough information - he does not care
not enough information