For project safety backup your people, not just your data

The FSF was founded in 1985, Perl in 1987 (happy 30th birthday, Perl!), and Linux in 1991. The term open source and the Open Source Initiative both came into being in 1998 (and turn 20 years old in 2018). Since then, free and open source software has grown to become the default choice for software development, enabling incredible innovation.
We, the greater open source community, have come of age. Millions of open source projects exist today, and each year the GitHub Octoverse reports millions of new public repositories. We rely on these projects every day, and many of us could not operate our services or our businesses without them.
So what happens when the leaders of these projects move on? How can we help ease those transitions while ensuring that the projects thrive? By teaching and encouraging succession planning.
Also:
Dear software manager, working in the open for the very first time? Challenges (
When moving from managing software projects/teams in classic corporate environments into Open Source (FOSS) projects, there are several new challenges any front line manager will need to face.
Dear software manager, working in the open for the very first time? Face the challenges (II)
Working in the open involve new challenges that requires a different mindset to be successfully faced by front line managers moving from corporate to Open Source projects. They will need to develop new habits and the most effective way to do so, in my view, is understanding since day one that your focus will need to move towards alignment instead of insisting in autonomy, according to my mental model. With that in mind, my advice is to pay special attention to those habits that will lead you to become a servant for your managees, promoting transparency by example…
-
- Login or register to post comments
Printer-friendly version
- 945 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
Microsoft Linuxwashing and Research Openwashing
| today's howtos |
Why Everyone should know vimVim is an improved version of Vi, a known text editor available by default in UNIX distributions. Another alternative for modal editors is Emacs but they’re so different that I kind of feel they serve different purposes. Both are great, regardless.
I don’t feel vim is necessarily a geeky kind of taste or not. Vim introduced modal editing to me and that has changed my life, really. If you have ever tried vim, you may have noticed you have to press “I” or “A” (lower case) to start writing (note: I’m aware there are more ways to start editing but the purpose is not to cover Vim’s functionalities.). The fun part starts once you realize you can associate Insert and Append commands to something. And then editing text is like thinking of what you want the computer to show on the computer instead of struggling where you at before writing. The same goes for other commands which are easily converted to mnemonics and this is what helped getting comfortable with Vim. Note that Emacs does not have this kind of keybindings but they do have a Vim-like mode - Evil (Extensive Vi Layer). More often than not, I just need to think of what I want to accomplish and type the first letters. Like Replace, Visual, Delete, and so on. It is a modal editor after all, meaning it has modes for everything. This is also what increases my productivity when writing files. I just think of my intentions and Vim does the things for me.
| Graphics: Intel and Mesa 18.1 RC1 Released
|
Recent comments
8 hours 22 min ago
9 hours 32 min ago
14 hours 54 min ago
1 day 15 hours ago
2 days 21 hours ago
2 days 21 hours ago
3 days 9 hours ago
3 days 10 hours ago
4 days 5 hours ago
4 days 6 hours ago