From f7c75ddee84d764780a03e9e956009c3b2baeaa7 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Mon, 8 Jun 2020 05:01:35 +0800 Subject: [PATCH 1/5] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020200608=20How=20to?= =?UTF-8?q?=20Create=20Curve=20Text=20in=20GIMP=20in=205=20Simple=20Steps?= =?UTF-8?q?=20[GIMP=20Beginner=E2=80=99s=20Tutorial]?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20200608 How to Create Curve Text in GIMP in 5 Simple Steps -GIMP Beginner-s Tutorial.md --- ... Simple Steps -GIMP Beginner-s Tutorial.md | 118 ++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 sources/tech/20200608 How to Create Curve Text in GIMP in 5 Simple Steps -GIMP Beginner-s Tutorial.md diff --git a/sources/tech/20200608 How to Create Curve Text in GIMP in 5 Simple Steps -GIMP Beginner-s Tutorial.md b/sources/tech/20200608 How to Create Curve Text in GIMP in 5 Simple Steps -GIMP Beginner-s Tutorial.md new file mode 100644 index 0000000000..7ab1a8c98c --- /dev/null +++ b/sources/tech/20200608 How to Create Curve Text in GIMP in 5 Simple Steps -GIMP Beginner-s Tutorial.md @@ -0,0 +1,118 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (How to Create Curve Text in GIMP in 5 Simple Steps [GIMP Beginner’s Tutorial]) +[#]: via: (https://itsfoss.com/curve-text-gimp/) +[#]: author: (Dimitrios Savvopoulos https://itsfoss.com/author/dimitrios/) + +How to Create Curve Text in GIMP in 5 Simple Steps [GIMP Beginner’s Tutorial] +====== + +When you are working on a badge, poster or any other composition in GIMP and you need to bend or curve some text. The versatile [GIMP][1] tool offers several ways to create curved text. Depending on how you will use it and the curvature you want to give to your text, some methods are better than others. + +In this GIMP tutorial, I’ll show you my preferred way of creating curve texts. + +### How to create curve text in GIMP + +![][2] + +Please make sure that you have GIMP installed on your system already. + +#### Step 1: Create a path that matches the type of curve you want + +Create a new image or open an existing one. Select the paths tool and then having in mind roughly the position of the curved text, create your path by clicking once for the start and then for the end of path point. + +![Create a path][3] + +**Then give to your path a curvature.** First drag the line in the middle either up or down, and fine tune by moving the adjusting points. This will give it an arch. + +![Curving the path][4] + +#### Step 2: Create the text you want to curve + +When you are satisfied with your curved path, you can move to the next step and **create your text**. + +You may want to change the font and the font size. My selections are for demonstration purpose only. + +![Create a text][5] + +#### Step 3: Create a new layer + +I strongly suggest separating each different element of a GIMP image in different layers, in order to manipulate them easily like move, turn on/off an element etc. + +Following this rule our curved text will be placed at a new layer. It is recommended to name your new layer like “Curved Text” or something similar to easily identify it. + +![Create a new layer for the curved text][6] + +#### Step 4: Curve the text + +Now you need to click on the layer that your text is and right click on it and then click on “Text along path” to bend your text. The curved text will be placed at the newly created layer. + +![Text Along Path][7] + +You just curved the text! Let’s make the text more presentable by filling it with colour. + +### Step 5: Final touches and export + +Click on the curved text layer and then go to the path tab to select the text boundaries. + +![Path To Selection][8] + +Finally, select the bucket tool, a colour of your choice and apply your selection as per below. + +![][9] + +As the last step, turn the visibility of the layers that you don’t want and keep only the curved text. Then you are ready to export your file as your preferred image format. + +![][10] + +#### Bonus Tip: Create shade effect + +I have an additional step as an exercise/challenge if you want to go the extra mile. Let’s create a shade effect to the curved text by [outlining the text in GIMP][11]. + +I will give you some hints: + + * Turn all the layers back on + * Click on the curved text layer and the use the move tool to move the text away + * Create another layer and repeat the bucket fill procedure with a black colour + * Overlay the layers in a way that they mimic a shaded position (you may need to change the layers order) + * Turn off the auxiliary layers + + + +**The final result!** + +![][12] + +Let me know in the comments below your thoughts about this GIMP tutorial and how many of you tried the bonus step. + +Don’t forget to [subscribe to the newsletter][13] as It’s FOSS team has much more for you in the near future! + +-------------------------------------------------------------------------------- + +via: https://itsfoss.com/curve-text-gimp/ + +作者：[Dimitrios Savvopoulos][a] +选题：[lujun9972][b] +译者：[译者ID](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://itsfoss.com/author/dimitrios/ +[b]: https://github.com/lujun9972 +[1]: https://www.gimp.org/ +[2]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/05/Curve-text-in-GIMP.jpg?ssl=1 +[3]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/05/1image-1.png?fit=800%2C508&ssl=1 +[4]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/05/2.png?fit=800%2C500&ssl=1 +[5]: https://i0.wp.com/itsfoss.com/wp-content/uploads/2020/05/3.png?fit=800%2C503&ssl=1 +[6]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/05/new-layer.png?fit=800%2C637&ssl=1 +[7]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/05/text-along-path.png?fit=800%2C625&ssl=1 +[8]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/05/path-to-selection.png?ssl=1 +[9]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/05/6.png?fit=800%2C539&ssl=1 +[10]: https://i1.wp.com/itsfoss.com/wp-content/uploads/2020/05/4.png-copy.png?ssl=1 +[11]: https://itsfoss.com/gimp-text-outline/ +[12]: https://i2.wp.com/itsfoss.com/wp-content/uploads/2020/05/its-foss-curved.jpg?fit=800%2C409&ssl=1 +[13]: https://itsfoss.com/subscribe-to-newsletter/ From a509fb367c7d33315c0f85afa71a399092db6065 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Mon, 8 Jun 2020 05:01:54 +0800 Subject: [PATCH 2/5] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020200607=205=20ways?= =?UTF-8?q?=20to=20boost=20your=20Kubernetes=20knowledge?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20200607 5 ways to boost your Kubernetes knowledge.md --- ...ways to boost your Kubernetes knowledge.md | 80 +++++++++++++++++++ 1 file changed, 80 insertions(+) create mode 100644 sources/tech/20200607 5 ways to boost your Kubernetes knowledge.md diff --git a/sources/tech/20200607 5 ways to boost your Kubernetes knowledge.md b/sources/tech/20200607 5 ways to boost your Kubernetes knowledge.md new file mode 100644 index 0000000000..c2f7ad1484 --- /dev/null +++ b/sources/tech/20200607 5 ways to boost your Kubernetes knowledge.md @@ -0,0 +1,80 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (5 ways to boost your Kubernetes knowledge) +[#]: via: (https://opensource.com/article/20/6/kubernetes-anniversary) +[#]: author: (Seth Kenlon https://opensource.com/users/seth) + +5 ways to boost your Kubernetes knowledge +====== +On its anniversary, get to know Kubernetes with these deep-dives and +hands-on projects. +![Ship captain sailing the Kubernetes seas][1] + +When the cloud was still in its formative years, developers discovered that it was convenient to write applications in small, atomic, minimal Linux images that shared resources with the server they ran on. Technically based on kernel namespaces, these small environment definitions came to be called [containers][2]. As containers proliferated, sysadmins quickly realized it was becoming essential to develop a tool that could help them manage not only containers but also the virtualized infrastructure underneath. And that's when [Kubernetes][3] was born. + +Kubernetes is an extensible open source platform for wrangling containers. It helps administrators and developers manage workloads, services, and processes around containers. It facilitates declarative configuration and easy automation. In its relatively short lifespan, it has fostered a rapidly growing ecosystem with services, support, and tools from many companies and projects. + +If you're looking to get better acquainted with this important cloud technology, here are a few articles to help you dive deep and five projects to help you try out what you learn. + +### Containing container chaos + +In 2016, we published [Containing the container chaos with Kubernetes][4], an introductory article by Terry Ryan about how Kubernetes is helping admins and architects grapple with containers. If you need a ground-level introduction to what containers do and how Kubernetes makes it easy, then this is the article to read first. It assumes no prior knowledge and explains all the most important concepts, so you can get up to speed fast. + +For an advanced look into some of the magic happening at the kernel level, read Jessica Cherry's explanation of [Kubernetes namespaces][5]. + +### Kubernetes: Why does it matter? + +Kubernetes provides the benefits of an Infrastructure-as-a-Service (IaaS) solution (like OpenStack) and a full Platform as a Service (PaaS). It gives you abstractions for managing infrastructure and the tools you need to troubleshoot at the base level of bare metal. If you have the impulse to cling to a single bare-metal server, you might want to read Tim Potter's take on [why Kubernetes matters][6]. His article compares IaaS and PaaS and gives his perspective on why Kubernetes has been so widely adopted. You don't always need Kubernetes or containers, but it's important to know when you do. + +### Run it on a Raspberry Pi + +There's no better way to get familiar with Kubernetes than to run it yourself. Unfortunately, not everyone has a cloud (nor the money to rent time on one) at their disposal. Luckily, Chris Collins has provided a guide for running [Kubernetes on a Pi][7]. Combined with his equally elucidating tutorials about [Cloud-init][8] and [Cloud-init services][9] (also on a Pi), you can build whatever kind of homelab you want so that you can learn how to manage your very own open hybrid cloud. + +### Kubernetes commands + +Once you have Kubernetes up and running, take a look at Jessica Cherry's article and accompanying cheat sheet that provides you with all the [essential Kubernetes commands][10]. In her article, she explains the syntax of `kubectl` commands and provides an overview of what each command and subcommand is meant to do. + +### Fun Kubernetes projects + +Nothing's more frustrating than having access to technology but not knowing what to do with it. For instance, it's one thing to have a Raspberry Pi on your desk, but it's an entirely different matter to decide what it ought to spend its CPU cycles doing. We've published plenty of articles to give some guidance to your Kubernetes explorations: + + * [Helm][11] is a package manager for Kubernetes. Exploring it is an easy way to get comfortable with living in Kubernetes. + * Learn all about [Operator SDK][12] to get familiar with Kubernetes objects and operators. + * Provide a [network file system (NFS) on top of Kubernetes.][13] + * Learn how to route traffic with [Skipper][14] or [Traefik.][15] + + + +Most importantly, take the time to get comfortable with containers and Kubernetes. Whether you first embrace containerized apps on the server, cloud, or desktop, they're an important paradigm to understand, because they're a powerful construct that's made applications on Linux better, stronger, more robust, and easier. Invest time to learn more about them. You'll be glad you did. + +-------------------------------------------------------------------------------- + +via: https://opensource.com/article/20/6/kubernetes-anniversary + +作者：[Seth Kenlon][a] +选题：[lujun9972][b] +译者：[译者ID](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/seth +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/ship_captain_devops_kubernetes_steer.png?itok=LAHfIpek (Ship captain sailing the Kubernetes seas) +[2]: https://opensource.com/article/18/11/behind-scenes-linux-containers +[3]: https://opensource.com/resources/what-is-kubernetes +[4]: https://opensource.com/life/16/9/containing-container-chaos-kubernetes +[5]: https://opensource.com/article/19/12/kubernetes-namespaces +[6]: https://opensource.com/article/17/6/introducing-kubernetes +[7]: https://opensource.com/article/20/6/kubernetes-raspberry-pi +[8]: https://opensource.com/article/20/5/cloud-init-raspberry-pi-homelab +[9]: https://opensource.com/article/20/5/create-simple-cloud-init-service-your-homelab +[10]: https://opensource.com/article/20/5/kubectl-cheat-sheet +[11]: https://opensource.com/article/20/2/kubectl-helm-commands +[12]: https://opensource.com/article/20/3/kubernetes-operator-sdk +[13]: https://opensource.com/article/20/6/kubernetes-nfs-client-provisioning +[14]: https://opensource.com/article/20/4/http-kubernetes-skipper +[15]: https://opensource.com/article/20/3/kubernetes-traefik From 2a54ae4f2f438bb5d0da23e55860f9424c376e95 Mon Sep 17 00:00:00 2001 From: DarkSun Date: Mon, 8 Jun 2020 05:02:08 +0800 Subject: [PATCH 3/5] =?UTF-8?q?=E9=80=89=E9=A2=98:=2020200607=20Is=20your?= =?UTF-8?q?=20team=20a=20"glue=20team=3F"?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit sources/tech/20200607 Is your team a -glue team.md --- .../20200607 Is your team a -glue team.md | 121 ++++++++++++++++++ 1 file changed, 121 insertions(+) create mode 100644 sources/tech/20200607 Is your team a -glue team.md diff --git a/sources/tech/20200607 Is your team a -glue team.md b/sources/tech/20200607 Is your team a -glue team.md new file mode 100644 index 0000000000..d62fed9525 --- /dev/null +++ b/sources/tech/20200607 Is your team a -glue team.md @@ -0,0 +1,121 @@ +[#]: collector: (lujun9972) +[#]: translator: ( ) +[#]: reviewer: ( ) +[#]: publisher: ( ) +[#]: url: ( ) +[#]: subject: (Is your team a "glue team?") +[#]: via: (https://opensource.com/open-organization/20/6/glue-team) +[#]: author: (Lauri Apple https://opensource.com/users/lapple) + +Is your team a "glue team?" +====== +Glue teams help keep an organization running smoothly. Here's how to +help them do their best work and avoid burnout. +![Teamwork starts with communication amongst teams and across silos][1] + +In his book [_How to Win_][2], New York Times senior economic correspondent Neil Irwin championed the role of "glue people" in bringing about better alignment, collaboration, and organizational maturity. "There is particular value in being a 'glue person,'" [Irwin writes][3], "someone who understands how their specialty fits together with other types of technical expertise, who can ensure that teams containing people with diverse skills can work together to create something greater than the sum of its parts." + +In many organizations, "glue people" are identified by their roles—product managers, team leads, program manager, project manager, agile coach, business systems analyst. They're people like me—an agile program manager who's been developing cross-team and cross-organizational initiatives for the past seven years at large- and medium-sized companies. + +In one company, I served as program manager for a company-wide open source initiative—aligning 1,800 developers behind a common strategy and setting development practices. In another, I worked with three teams building out a self-service deployment platform based on Kubernetes and AWS. In these days of Coronavirus, I'm helping 14 delivery teams to launch an MVP offering that augments our core business. + +The subject matter has been different in each role, but the same key activities that I bring to work every day remain consistent: + + * Drive alignment + * Coordinate people, efforts, and teams + * Call out ambiguous language to drive clarity and replace assumptions with facts + * Be the neutral party or "fresh eyes" who distills detailed conversations and plans down into simple questions: "Are you doing this, or that?"; "Are you building two things or one thing?" So often, these basics go overlooked! + * Coach leaders on delegation, prioritization and strategic thinking + * Facilitate informed decision-making + * Forecast dependencies and other risks and help mitigate them + * Visualize complex packages of work in simple, clear diagrams and language to improve transparency and accountability + + + +The glue people in your organization might also be program managers, or agile coaches, scrum masters, or engineering managers. Some organizations rely on their savviest product managers and engineering managers to provide the glue; in other organizations, the CEO doubles as Chief Glue Officer. In any case, we glue people spend much of our workdays connecting the dots between people, topics, and themes, to paint the whole picture instead of little corners. + +Maybe you are a glue person. Have you ever considered the specific ways you may fulfill this role? + +### Understanding the need for coherent storytelling + +Do you ever think of yourself as a storyteller, embracing or asserting a narrative as a means of keeping your organization aligned? If so, you're fulfilling a valuable glue-person responsibility. + +Coherent storytelling essentially amounts to connecting the dots. In your average tech organization, there is lots of activity moving forward; maybe this is even documented. But does it all add up to a story anyone can follow? For example: + + * Have you ever seen a roadmap that was formatted as a to-do list, and wondered how the different items corresponded to each other? + * Have you ever seen goals stated on a vision document and wondered, "we've never fulfilled that function before, and we don't have a team set up to do it anytime soon. So what are the steps between now and that team forming? How do we get there?" + * Have you or your team ever been asked to drop what you're doing right now, even though last week it was "super-urgent," and start doing this other thing right now because it's suddenly also "super-urgent?" + * Does your product roadmap look more like spinning a bunch of plates to keep different customers happy than building increments of value to serve current and future customers? + * Does your organization try to do too much, making an extreme sport out of context-switching? + + + +I've seen all of the above. They're all pretty failsafe ways to get talented people to burn out, lose motivation, and leave your organization. These frustrated folks see their companies constantly [disrupting themselves][4] and determine that they will never get anything done. They don't know where they're headed, and no one is telling them that story in any clear, purpose-focused way. What's unfortunate is that such problems are usually not difficult to solve—the content and context are there, but no one is assembling it into the narrative or editing out the filler. + +Even the most clear-headed companies struggle to permanently bake common sense fundamentals like prioritization and evidence-based decision-making into their cultures and habits. They're aware of the importance of values like focus, clarity, and prioritization. Maybe the companies even worked hard to attain them through pragmatic-sounding values statements, objective and key results (OKR) strategies, offsites, workshops, and other common tools of the transformation trade. Nevertheless, hierarchies form, and a few teams start getting left out of decisions that affect them. Politics seep in. Inertia creeps. Docs—what are docs? Decision logs—what are decision logs? Meetings get longer and more boring. Time starts to run out, and you end up at the point where you "just have to ship something." The plot gets lost. + +> "We used to be excellent at getting work done. The more people we add, the less we're getting done." + +Some organizations lose the plot of their own story by over-reliance on oral storytelling. They hold a lot of meetings where much is said, but no one takes notes. There's no basic roadmap or vision posted; in fact, there is resistance to the idea of those things. "It takes too much time," is the usual argument. "No one will read them anyway," is another common one. Often, in these organizations, the processes they've developed rely too much on personal connections, and not enough on well-designed communication flow. Their processes are lightweight because they're nonexistent. + +From time to time, I've asked colleagues, "would you rather write this down once, or have three or four meetings where you have to clarify the same point with the same people?" Usually, they decide to write it down. But the habit of oral storytelling and hallway negotiation can take time to break. + +As a former reporter, it's not much of a stretch for me to view my role as that of a storyteller. Much of what I do on a daily basis is similar to when I was reporting: + + * Asking people questions + * Clarifying the responses + * Challenging the responses ("but what about this?") to sharpen their meaning + * Organizing the information into stories, starting with the most important details ("the lede") first + * Constantly asking, "who is going to care about this detail?" and segmenting the content by audience + * Categorizing related types of information to form sub-themes and identify sub-narratives + + + +When I give road-mapping workshops, I cover the 5 Ws—it feels like giving a Journalism 101 class to engineering managers and product teams: + + * WHO is the customer? The team/set of teams about to do the work? + * WHAT are we doing? + * WHY are we doing it? Why are we not doing this other thing instead? + * WHEN do we start? When do we hope to finish something? + * WHERE does this effort reside in the landscape of our other efforts? + * HOW do you want to do it? + + + +In leading these road-mapping sessions, I'm looking for a few key outcomes of success: + + * A story that reflects a very strict work-in-progress limit—i.e., a primary plot, and two to three related sub-plots maximum, but no more + * Stated objectives for whatever the organization is working on that are customer-agnostic and framed in a broader context (i.e., doing X will strengthen or complement Y, in these ways) + * Metrics and data points that clearly show the impact of delivering something + + + +One other similarity between being a "glue person" in a tech organization, and being a journalist, is that it's vital to ask tough questions, to get to the bottom of stories. This is to ensure that the "readers" of those stories—the teams, the departments, the C-level, and anyone else seeking the information—have all the clarity they need to follow the plot. Here some example questions from my real-life experience: + + * To a group of 15 engineering managers who have spent an hour-long meeting prioritizing a bunch of greenfield development initiatives—"How did protecting customer data from known potential leaks end up near the bottom of your list?" + * To a head of engineering, who wanted to create dashboards so he could survey team progress—"Who needs these bug-counting dashboards; the delivery teams, or you? How does this scale? Is 'number of bugs' a reliable metric?" + * To two teams who want to build their own Kubernetes cluster when one is sufficient—"Hey, what's the value of doing that?" + + + +A lot of what I'm suggesting depends on changing habits, which takes time. Unfortunately, you're in the middle of a global pandemic and don't have time to waste on getting the right teams and people assembled and a plan in motion. You probably don't have the bandwidth to do it all yourself. + +So, don't be the sole glue person in your organization. Be one of many glue people, and help other people adapt to playing this role. It's especially crucial during a crisis. + +-------------------------------------------------------------------------------- + +via: https://opensource.com/open-organization/20/6/glue-team + +作者：[Lauri Apple][a] +选题：[lujun9972][b] +译者：[译者ID](https://github.com/译者ID) +校对：[校对者ID](https://github.com/校对者ID) + +本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出 + +[a]: https://opensource.com/users/lapple +[b]: https://github.com/lujun9972 +[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/fistbump-team-teamwork.png?itok=WuSu8-wE (Teamwork starts with communication amongst teams and across silos) +[2]: https://www.neilirwin.com/how-to-win +[3]: https://www.theatlantic.com/ideas/archive/2019/06/its-a-winner-take-all-world-heres-how-to-get-ahead/591700/ +[4]: https://barryoreilly.com/when-your-startup-cant-stop-disrupting-itself/ From 57832a1acd68034968a3281d9ee9a3cda9585a39 Mon Sep 17 00:00:00 2001 From: geekpi Date: Mon, 8 Jun 2020 08:45:26 +0800 Subject: [PATCH 4/5] translating --- .../20200604 Using AppImage for Linux package management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/tech/20200604 Using AppImage for Linux package management.md b/sources/tech/20200604 Using AppImage for Linux package management.md index d57952002f..dd9a4aa8e1 100644 --- a/sources/tech/20200604 Using AppImage for Linux package management.md +++ b/sources/tech/20200604 Using AppImage for Linux package management.md @@ -1,5 +1,5 @@ [#]: collector: (lujun9972) -[#]: translator: ( ) +[#]: translator: (geekpi) [#]: reviewer: ( ) [#]: publisher: ( ) [#]: url: ( ) From 344ae33226b3469e1e49efe4ff140be4865f48d3 Mon Sep 17 00:00:00 2001 From: "Xingyu.Wang" Date: Mon, 8 Jun 2020 10:09:01 +0800 Subject: [PATCH 5/5] Rename sources/tech/20200607 Is your team a -glue team.md to sources/talk/20200607 Is your team a -glue team.md --- sources/{tech => talk}/20200607 Is your team a -glue team.md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename sources/{tech => talk}/20200607 Is your team a -glue team.md (100%) diff --git a/sources/tech/20200607 Is your team a -glue team.md b/sources/talk/20200607 Is your team a -glue team.md similarity index 100% rename from sources/tech/20200607 Is your team a -glue team.md rename to sources/talk/20200607 Is your team a -glue team.md