mirror of
https://github.com/LCTT/TranslateProject.git
synced 2026-08-23 04:03:29 +08:00
清除部分过期文章
This commit is contained in:
wxy
@@ -1,27 +0,0 @@
|
||||
France's Ministry of the Interior achieved 5-"10 times less expensive" with open-source software
|
||||
================================================================================
|
||||
By looking at the world, the observer is to perceive a massive amount of nationalities, languages, habits, tastes, political structures, as well as differently-developed countries spanning from poverty to wealthy regions.
|
||||
|
||||
Yet, perhaps rather strange and non-intelligent, all countries,--more or less--, are characterized by the usage of proprietary software, proprietary software spreading its tentacles across the globe, where it has managed to solidify a monopoly rooted into one goal: the maintenance of monopoly.
|
||||
|
||||
Yet, definitely exciting, various countries have started to identify the benefits of the open-source software, perception that instantly reveals the years-and-years of non-productive usage of proprietary software: operating systems, email applications, office suites.
|
||||
|
||||
Moreover, adopting open-source software, even in small percentages, has the capacity of resurrecting state departments and companies, schools and city administrations, resurrection happening in steps and extremely visible: first, there are massive decreases in money used for software, second, the entities adopting open-source software are independent from the proprietary companies and, thus, are able to much more accurately, precisely and sanely conduct their computing lives, essentially, becoming completely new highly-empowered entities.
|
||||
|
||||
The **Open source observatory** has [published][1] an interesting article, talking about the conclusion reached by **France's Ministry of the Interior** after using open-source software on 200,000 PCs since 2008, namely, achieving five times cheaper money-spending on software.
|
||||
|
||||
|
||||
|
||||
The five-times-cheaper achievement has been reached with the open-source Thunderbird email-application, while using GLPI and OCS,-- free software tools useful to manage computer assets--, has decreased the costs up to 10 times less, "**this is 10 times less expensive than the previous proprietary tool**".
|
||||
|
||||
As related to servers, the ministry has adopted open-source software, too, software that, packed with open-source databases and office tools, is "leading to substantial savings".
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://iloveubuntu.net/frances-ministry-interior-achieved-5-10-times-decreases-costs-open-source-software
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://joinup.ec.europa.eu/community/osor/news/french-interior-ministry-open-source-5-10-times-cheaper
|
||||
@@ -1,44 +0,0 @@
|
||||
Here’s How To Enable DVD Playback In Ubuntu 13.10
|
||||
================================================================================
|
||||
If you find yourself struggling to play DVDs in Ubuntu 13.10 after installing, here’s the reason why. You see, Ubuntu is always shipped with some limitations when it comes to playing DVDs and other media. For legal reasons, Canonical, the parent company of Ubuntu leaves out these packages and programs that are required to play DVDs and most media in Ubuntu.
|
||||
|
||||
I am not going to tell you what the reasons are, but here’s how to get these packages in Ubuntu so you can play and watch commercial DVD as well as other encrypted media.
|
||||
|
||||
There are many options available to you. You could install free versions of these packages or get some paid versions if you want to help those behind the efforts of making Ubuntu media friendly.
|
||||
|
||||
Another method that’s no longer available was to use Medibuntu repositories to install these packages which will allow you play DVDs. Now, Medibuntu has [stopped support][1] for Ubuntu 12.10 and up.
|
||||
|
||||
So, to play DVDs again in Ubuntu, follow the steps below.
|
||||
|
||||
[Purchase Fluendo DVD Player][2] – this program is designed to help Ubuntu users play commercial DVDs. It supports full DVD playback, full screen and support for subtitles.
|
||||
|
||||
If you don’t want to buy software that allows you to play DVDs, install these free tools.
|
||||
|
||||
Press **Ctrl – Alt – T** on your keyboard to open the terminal. When it opens, run the commands below.
|
||||
|
||||
sudo apt-get install ubuntu-restricted-extras
|
||||
|
||||
Next, run the commands below.
|
||||
|
||||
sudo apt-get install libavformat-extra-53 libavcodec-extra-53 libdvdread4
|
||||
|
||||
Finally, run the commands below and you’re done.
|
||||
|
||||
sudo /usr/share/doc/libdvdread4/install-css.sh
|
||||
|
||||
You may have to restart your computer. After that, insert your DVD and try again. If all of the above steps fail, run the commands below to install VLC Player.
|
||||
|
||||
sudo apt-get install vlc
|
||||
|
||||
Enjoy!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.liberiangeek.net/2013/10/heres-enable-dvd-playback-ubuntu-13-10/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://gauvain.pocentek.net/node/61
|
||||
[2]:https://apps.ubuntu.com/cat/applications/fluendo-dvd/
|
||||
@@ -1,36 +0,0 @@
|
||||
How to observe system components' usage in Ubuntu 13.10 via System Load Indicator
|
||||
================================================================================
|
||||
[System Load Indicator][1] is a lightweight yet powerful and handy manner of displaying the user's usage of system components on the easiness of the Unity panel.
|
||||
|
||||
Basically, System Load Indicator is an appindicator located on the Unity panel that exposes graphs for relevant computer components, such as **CPU**, **RAM**, swap, harddisk, network traffic, etc, permitting a hassle-free observation of the usage of the mentioned components in real time.
|
||||
|
||||
System Load Indicator does not require additional efforts or configuration, directly,--after its launch--, presenting the graphs on the Unity panel.
|
||||
|
||||
Installing and launching `System Load Indicator` (via the Dash by typing system load indicator in the search area), pushes a single block on the Unity panel, block housing constantly-updated graphs of CPU, component monitored and displayed accordingly by default.
|
||||
|
||||
Yet, clicking on `System Load Indicator appindicator-->Preferences` summons a window from where other components can be 1-click away enabled; meaning, (for example) checking `Memory` and `Harddisk`, adds two new blocks on the Unity panel, thus there are now three components monitored by System Load Indicator: CPU, RAM and harddisk.
|
||||
|
||||
|
||||
|
||||
Under Colors, the user is able to select custom colors for the graphs-enabled blocks, meaning, changing the blue and dark colors to green and orange, renders the CPU's block with green and orange.
|
||||
|
||||
|
||||
|
||||
Moreover, System Load Indicator pairs its visual-based monitoring with accurate text-based values, clicking on System Load Indicator appindicator, opens its menu where the user is to digest the accurate text-based values of monitored components, values updated in real time.
|
||||
|
||||
|
||||
|
||||
Recently, Ubuntu 13.10 was released, version containing System Load Indicator in its Ubuntu Software Center, permitting to the user to easily install the versatile tool.
|
||||
|
||||
System Load Indicator 0.3 is [available][2] via Ubuntu 13.10's Ubuntu Software Center (Ubuntu 13.04 and Ubuntu 14.04, too).
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://iloveubuntu.net/how-observe-system-components-usage-ubuntu-1310-system-load-indicator
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://launchpad.net/indicator-multiload
|
||||
[2]:apt://indicator-multiload
|
||||
@@ -1,35 +0,0 @@
|
||||
Linux Top 3: RHEL 6.5, Debian 7.2 and EOL for Linux 3.0.x
|
||||
================================================================================
|
||||
**Linux 3.0.100 Released**
|
||||
|
||||
Though it might seem like Linux 3.0 was released just yesterday, the truth is that it was [released back in July of 2011][1].
|
||||
|
||||
Since then some 100 milestone update have been released fixing bugs and providing some security updates. The Linux 3.0.x kernel had been selected as a Long Term Support kernel, meaning that it is maintained for up to two years.
|
||||
|
||||
In August of this year, Linux kernel developer, Greg Kroah-Hartman [declared][2] that the 3.10 Linux kernel would be a longterm support release. That release now supersedes the longterm 3.0.x kernel
|
||||
|
||||
"Linux stable kernel 3.0.100 is now released, please move to 3.4.x or 3.10.x as this might be the last release of 3.0.x," Kroah-Hartman wrote on October 13th.
|
||||
|
||||
**Red Hat Enterprise Linux 6.5 Beta**
|
||||
|
||||
Barely a week after Red Hat released Red Hat Enterprise Linux 5.10, the Linux vendor is now out with a beta release for its next generation platform.
|
||||
|
||||
RHEL 6.5 beta provides support for the precision timing protocol, as an improvement of the traditional network timing protocol (NTP). Precision Time Protocol (PTP) is important to users who require sub-microsecond time stamping of transactions.
|
||||
|
||||
**Debian 7.2**
|
||||
|
||||
Debian is also out with an update. The Debian 7.2 update is the second since Debian 7.x aka Wheezy was released earlier this year.
|
||||
|
||||
"This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems," The Debian project [stated][3]. "Security advisories were already published separately and are referenced where available. Please note that this update does not constitute a new version of Debian 7 but only updates some of the packages included."
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxplanet.com/news/linux-top-3-rhel-6-5-debian-7-2-and-eol-for-linux-3.html
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:http://www.datamation.com/open-source/linux-3.0-debuts-with-xen-integration.html
|
||||
[2]:http://www.eweek.com/developer/linux-3.10-goes-long-term-why-it-matters-for-the-enterprise-consumers/
|
||||
[3]:http://www.debian.org/News/2013/20131012
|
||||
@@ -1,53 +0,0 @@
|
||||
Mark Shuttleworth Brands Mir Opponents “The Open Source Tea Party”
|
||||
================================================================================
|
||||
**The free software community has been rocked by recent comments made by Ubuntu founder Mark Shuttleworth.**
|
||||
|
||||
> ‘At least we know now who belongs to the Open Source Tea Party’
|
||||
|
||||
In a blog post announcing the codename of Ubuntu 14.04 LTS, the multi-millionaire space tourist describes opponents of Ubuntu’s new display server ‘Mir’ as “The Open Source Tea Party”.
|
||||
|
||||
These “outraged individuals” are, he argues, attacking the project “on purely political grounds”, explaining:
|
||||
|
||||
> “When a project says “we will not accept a patch to enable support for Mir” they are saying you should not have the option. When that’s typically a project which goes to great lengths to give its users every option, again, I suggest there is a political motive.”
|
||||
|
||||
His accusations haven’t gone over well in the wider free software community.
|
||||
|
||||
### “Debate” ###
|
||||
|
||||
In one of the more level-headed responses to the remarks, prominent KDE developer Aaron Seigo [has invited Mark to join a live, public debate][1] on “*the merits of Mir, Wayland and their implications vis-à-vis Free software.*”
|
||||
|
||||
A public airing would, Seigo feels, help show that the arguments against Mir are technically, as opposed to politically, motivated.
|
||||
|
||||
Ubuntu Community Manager Jono Bacon, in response to Seigo’s offer, has described the fallout from Shuttleworth’s comments “yet another pointless Open Source bickering match”, suggesting that parties on both sides of the argument should ”*stop biting at each other’s ankles about their respective projects.*”
|
||||
|
||||
### “Tensions” ###
|
||||
|
||||
|
||||
|
||||
Tensions between Mir proponents and those who see Wayland as the afforded successor to X have been building ever since Canonical announced plans to roll with their own solution earlier this year.
|
||||
|
||||
The decision came as a surprise to many as, in 2010, Mark Shuttleworth had been explicit about the need to work with Wayland developers rather than against them. He wrote at the time:
|
||||
|
||||
> “We evaluated the cost of building a new display manager, informed by the lessons learned in Wayland. We came to the conclusion that any such effort would only create a hard split in the world which wasn’t worth the cost of having done it. There are issues with Wayland, but they seem to be solvable, we’d rather be part of solving them than chasing a better alternative.”
|
||||
|
||||
This sudden u-turn was not helped by Canonical allegedly making ‘inaccurate and erroneous assumptions’ about Wayland in initial statements explaining their decision to not use it. Canonical later retracted and amended their claims.
|
||||
|
||||
> The grievances felt by parties on both sides of the divide show no signs of abating.
|
||||
|
||||
Shuttleworth has also risked raising further ire by describing systemd – a modern replacement for the ‘init’ daemon - as “invasive” and “hardly justified”.
|
||||
|
||||
Canonical’s own init replacement, *Upstart*, is most notably used in Ubuntu and Ubuntu-based derivatives, as well as in Chrome OS. Systemd, created some four years after upstart, is used by default in a growing number of Linux distributions, including *Arch, Fedora, Mageia, and openSUSE*.
|
||||
|
||||
While the grievances felt by parties on both sides of the divide show no signs of abating, the technologies they surround continue to progress.
|
||||
|
||||
Mir, which includes a compatibility layer for running legacy ‘xserver’ applications and input devices, was held back from shipping as default in Ubuntu 13.10 due to ‘technical difficulties’, though recent benchmarks are showing only negligible performance hits compared to the traditional X server.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2013/10/mark-shuttleworth-brands-mir-opponents-open-source-tea-party
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:https://plus.google.com/107555540696571114069/posts/76Nd9RSTZWp
|
||||
@@ -1,27 +0,0 @@
|
||||
Mark Shuttleworth to speak at GMIC about "the future of the open source mobile platform movement" and about "Open Mobile Platforms" at Mobile Monday (October 22nd and October 28th 2013)
|
||||
================================================================================
|
||||
Solid desktop, cutting-edge cloud technologies and the recently-released Ubuntu for phones are among the software pushed forward by Canonical, professional company setting itself as a serious player at a planetary scale.
|
||||
|
||||
[Canonical][1] has been characterized by determination and constant participation to important public events, latter rooting Canonical into the now's IT demands, requirements and state, as well as adding a layer of up-to-date to Canonical's expressing Ubuntu and related software.
|
||||
|
||||
**GMIC** and **Mobile Monday** are important IT events, presenting themselves as conferences and expos, where relevant computing persons, companies and experts are gathered into discussions, keynotes and topics about recent achievements in technology, cutting-edge software and the latest trends in the IT world.
|
||||
|
||||
Canonical will attend both GMIC and Mobile Monday, being represented by solid persons, including Mark Shuttleworth.
|
||||
|
||||
**Mark Shuttleworth** will talk about "**the future of the open source mobile platform movement**" [at GMIC][2] on October 22nd 11:15 AM, exciting presentation followed by Mark Shuttleworth actively joining a panel of experts in discussing the future of "[Open Mobile Platforms][3]", latter event to happen on October 28th 2013.
|
||||
|
||||
|
||||
|
||||
Moreover, a Canonical team will demo the latest version of Ubuntu for phones, **Canonical** that is to **co-host** Mobile Monday, taking serious responsibilities in the happening of the mobile-oriented event.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://iloveubuntu.net/mark-shuttleworth-speak-gmic-about-future-open-source-mobile-platform-movement-and-about-open-mobile
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.canonical.com/
|
||||
[2]:http://sv.thegmic.com/thought-leader-track/
|
||||
[3]:http://www.meetup.com/Mobile-Monday-Silicon-Valley/events/115663362/
|
||||
@@ -1,29 +0,0 @@
|
||||
Multi-Master Database Replication Software SymmetricDS 3.5.10 Released
|
||||
================================================================================
|
||||
**SymmetricDS, an open source software for multi-master database replication, filtered synchronization, or transformation across the network in a heterogeneous environment, is now at version 3.5.10.**
|
||||
|
||||
|
||||
|
||||
SymmetricDS 3.5.10 supports multiple subscribers with one-direction or bi-directional asynchronous data replication and uses technologies to replicate tables between relational databases.
|
||||
|
||||
### Highlights of SymmetricDS 3.5.10: ###
|
||||
|
||||
• sym_pkg is hard coded in the Oracle dialect, but the prefix parameter now works on Oracle;
|
||||
• The memory footprint usage is now improved when big lobs are in flight;
|
||||
• Statements are no longer being prepared too often and the data loading performance on Firebird has been improved;
|
||||
• The error message provided if a batch fails to transport because of an EOF error is now a lot more intuitive.
|
||||
|
||||
Check out the official [changelog][1] for more details about this release.
|
||||
|
||||
- [Download SymmetricDS 3.5.10 zip][2] [sources] [26.60 MB]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.softpedia.com/news/Multi-Master-Database-Replication-Software-SymmetricDS-3-5-10-Released-393078.shtml
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.symmetricds.org/issues/changelog_page.php
|
||||
[2]:http://sourceforge.net/projects/symmetricds/files/symmetricds/symmetricds-3.5/symmetric-3.5.10-server.zip/download
|
||||
@@ -1,30 +0,0 @@
|
||||
Open Virtualization Alliance joins the Linux Foundation
|
||||
================================================================================
|
||||
> But the developer community for OVA's Kernel-based Virtual Machine hypervisor project will remain separate and independent
|
||||
|
||||
IDG News Service - The Open Virtualization Alliance has joined the Linux Foundation as a collaborative project to deepen its ties with the Linux community.
|
||||
|
||||
The organizations announced their collaboration during the LinuxCon Europe conference in Edinburgh on Monday.
|
||||
|
||||
The Open Virtualization Alliance (OVA) has more than 250 member companies, including IBM, Red Hat, Intel and NetApp. It aims to raise awareness and drive adoption of the Kernel-based Virtual Machine (KVM) hypervisor, a full open source virtualization platform for Linux on x86 hardware that allows users to run multiple virtual machines unmodified on Linux or Windows images. KVM can be 60% to 90% cheaper than other virtualization platforms, while offering the same core functionality, according to the Alliance.
|
||||
|
||||
By joining the Linux Foundation as a collaborative project, the OVA seeks to deepen its ties with the broader Linux community, said Chuck Dubuque, the board chair for Open Virtualization Alliance and director of product marketing Red Hat-s Virtualization Business Unit, in an email. Together, they will work on KVM marketing and awareness and the Linux Foundation will increase its investments in KVM by hosting events such as the KVM Forum that started in Edinburgh on Monday, he added.
|
||||
|
||||
OVA joined the Foundation because of its track record of engaging the user and commercial communities associated with open source projects and its strong ties to the development community, making it the logical choice for a collaborative partner, said Dubuque. The KVM project itself however remains a separate and independent developer community, Dubuque added.
|
||||
|
||||
The Linux Foundation is happy to provide guidance to organizations that want to reduce operating costs, maximize promotional reach and increase participation in addition to its other activities, the Foundation said in a news release.
|
||||
|
||||
Advances in virtualization technologies are key to the growth of Linux in the enterprise and cloud computing, the Foundation said. In addition to hosting OVA, the Linux Foundation also hosts the Xen Project, an open source hypervisor that was [donated][1]. A to the Linux Foundation by Citrix in April to get input from a wider, more diverse group of contributors.
|
||||
|
||||
Loek is Amsterdam Correspondent and covers online privacy, intellectual property, open-source and online payment issues for the IDG News Service. Follow him on Twitter at [@loekessers][2] or email tips and comments to loek_essers@idg.com
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.computerworld.com/s/article/9243373/Open_Virtualization_Alliance_joins_the_Linux_Foundation?taxonomyId=122
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.pcworld.com/article/2034663/citrix-bequeaths-xen-to-the-linux-foundation.html
|
||||
[2]:http://www.twitter.com/loekessers
|
||||
@@ -1,97 +1,97 @@
|
||||
+Personality Traits of the Best Software Developers
|
||||
+================================================================================
|
||||
+I come from the world of corporate software development. It may not be the most glamorous side of software (it’s nowhere near as interesting as [shrinkwrap startups][1] or those fancy-dancy [Web 2.0][2] companies that show up in your browser every time you mistype a domain name), but it’s stable, pays well, and has its own set of challenges that other types of software development know nothing about.
|
||||
+
|
||||
+For example, when was the last time someone working on the next version of Halo spent three weeks trying to gather people from accounting, marketing, product management, and their call center in order to nail down requirements that would likely change in 2 months once they’ve delivered the software?
|
||||
+
|
||||
+Or when was the last time someone at [37Signals][3] sat through back to back weeks of [JAD sessions][4]?
|
||||
+
|
||||
+In this world of corporate development I’ve known a few phenomenal developers. I’m talking about those A+ people whom you would quit your job for to go start a company. And the the more I looked at what makes them so good, the more I realized they all share a handful of personality traits. Well, not exactly a handful, more like four.
|
||||
+
|
||||
+
|
||||
+
|
||||
+### Pessimistic ###
|
||||
+
|
||||
+Admiral Jim Stockdale was the highest ranking US military officer imprisoned in Vietnam. He was held in the “Hanoi Hilton” and repeatedly tortured over 8 years. Stockdale told Jim Collins, author of [Good to Great][5], “You must never confuse faith that you will prevail in the end, which you can never afford to lose, with the discipline to confront the most brutal facts of your current reality, whatever they might be.”
|
||||
+
|
||||
+After his release, Stockdale became the first three-star officer in the history of the navy to wear both aviator wings and the Congressional Medal of Honor.
|
||||
+
|
||||
+Stockdale was a pessimist in the short-term because he faced the brutal facts of his reality, but was an optimist in the long-term because of his confidence that he would prevail in the end.
|
||||
+
|
||||
+No one anticipates a catastrophic system failure by looking on the bright side. The best developers I know are experts at finding points of failure. You’ll often hear them quipping “What could possibly go wrong?” after someone makes a suggestion to handle a critical data transfer via nightly FTP over a dial-up connection. The best developers anticipate headaches that other developers never think of, and do everything within their power to avoid them.
|
||||
+
|
||||
+On the flip side, great developers are optimistic, even downright confident, about their overall success. They know that by being a pessimist in the short-term, their long-term success is ensured. Just like Jim Stockdale, they realize that by confronting the brutal facts of their current reality they will prevail in the end.
|
||||
+
|
||||
+### Angered By Sloppy Code ###
|
||||
+
|
||||
+Paul Graham nailed it when [he said][6] “…people who are great at something are not so much convinced of their own greatness as mystified at why everyone else seems so incompetent.”
|
||||
+
|
||||
+The worst nightmare for a great developer is to see someone else’s software gasping for air while bringing the rest of the system to its knees. It’s downright infuriating. And this isn’t limited to code; it can be bad installation packages, sloppy deployments, or a misspelled column name.
|
||||
+
|
||||
+
|
||||
+
|
||||
+Due to the life and death nature of their products, NASA designs zero-defect software systems using a process that has nearly eliminated the possibility for human error. They’ve added layer after layer of checks and balances that have resulted from years of finding mistakes and figuring out the best way to eliminate them. NASA is the poster child for discovering the source of a mistake and modifying their process to eliminate the possibility of that mistake ever happening again. And it works. A quote from [this Fast Company article][7] on NASA’s development process says
|
||||
+
|
||||
+“What makes it remarkable is how well the software works. This software never crashes. It never needs to be re-booted. This software is bug-free. It is perfect, as perfect as human beings have achieved. Consider these stats: the last three versions of the program — each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors.”
|
||||
+
|
||||
+I’m not saying we have to develop to this standard, but NASA knows how to find and fix bugs, and the way they do it is to find the source of every problem.
|
||||
+
|
||||
+Someone who fixes a problem but doesn’t take the time to find out what caused it is doomed to never become an expert in their field. Experience is not years on the job, it’s learning to recognize a problem before it occurs, which can only be done by knowing what causes it in the first place.
|
||||
+
|
||||
+Developers who don’t take the time to find the source often create sloppy solutions. For hundreds of examples of sloppy solutions visit [The Daily WTF][8]. Here are a few I’ve seen in my career:
|
||||
+
|
||||
+- An assembly is deleted from a server each time it’s rebooted. You could create a custom script to re-copy that assembly to the server after each reboot, or find out why the assembly is being deleted in the first place.
|
||||
+- An image-manipulation script is hogging processor power for minutes at a time when it should run in under 10 seconds. You could make the script run at 2am when no one will notice, or you can take the time to step through the code and figure out where the real problem is.
|
||||
+- A shared XML file is being locked by a process, causing other processes to fail when they try to open it. You could make several copies of the XML file so each process has its own, or you could troubleshoot the file access code to find out why it’s locking the file.
|
||||
+- And on and on…
|
||||
+
|
||||
+### Long Term Life Planners ###
|
||||
+
|
||||
+This one was a little puzzling for the longest time, but I think I’ve finally put it together.
|
||||
+
|
||||
+
|
||||
+
|
||||
+People who think many years down the road in their personal life have the gift to think down the road during development. Being able to see the impacts of present-day decisions is paramount to building great software. The best developers I know have stable family lives, save for retirement, own their own home, and eat an apple a day (ok, maybe not that last one). People who have spastic home-lives and live paycheck to paycheck can certainly be good developers, but what they lack in life they tend to lack in the office: the ability to be disciplined, and to develop and adhere to a long-term plan.
|
||||
+
|
||||
+### Attention to Detail ###
|
||||
+
|
||||
+I’ve known smart developers who don’t pay attention to detail. The result is misspelled database columns, uncommented code, projects that aren’t checked into source control, software that’s not unit tested, unimplemented features, and so on. All of these can be easily dealt with if you’re building a Google mash-up or a five page website. But in corporate development each of these screw-ups is a death knell.
|
||||
+
|
||||
+So I’ll say it very loud, but I promise I’ll only say it once:
|
||||
+
|
||||
+**I have never, ever, ever seen a great software developer who does not have amazing attention to detail.**
|
||||
+
|
||||
+I worked with a programmer back in school who forced anyone working with him to indent using two spaces instead of tabs. If you gave him code that didn’t use two spaces he would go through it line-by-line and replace your tabs with his spaces. While the value of tabs is not even a question, (I’ve long-chided him for this anal behavior) his attention to such a small detail has served him well in his many years designing chips at Intel.
|
||||
+
|
||||
+### So There You Have It ###
|
||||
+
|
||||
+The next time you’re interviewing a potential developer, determine if she has the four personality traits I’ve listed above. Here are a few methods I’ve found useful:
|
||||
+
|
||||
+- Ask if they’re an optimist or a pessimist
|
||||
+- Ask about a time when they found the source of a problem
|
||||
+- Find out if they save for retirement (you can work this in during discussions of your company’s retirement plan)
|
||||
+- Make an obvious misspelling in a short code sample and ask if they see anything wrong
|
||||
+
|
||||
+We know from [Facts and Fallacies of Software Engineering][9] that the best programmers are up to [28 times better][10] than the worst programmers, making them the best bargains in software. Take these four traits and go find a bargain (or better yet, make yourself into one).
|
||||
+
|
||||
+If you liked this article you’ll also like my article [Timeline and Risk: How to Piss off Your Software Developers][11].
|
||||
+
|
||||
+--------------------------------------------------------------------------------
|
||||
+
|
||||
+via: http://www.softwarebyrob.com/2006/08/20/personality-traits-of-the-best-software-developers/
|
||||
+
|
||||
+译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
+
|
||||
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
+
|
||||
+[1]:http://www.joelonsoftware.com/
|
||||
+[2]:http://www.econsultant.com/web2/
|
||||
+[3]:http://www.37signals.com/
|
||||
+[4]:http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci986072,00.html
|
||||
+[5]:http://www.amazon.com/gp/redirect.html?link_code=ur2&tag=softwarbyrob-20&camp=1789&creative=9325&location=%2Fgp%2Fproduct%2F0060794410%2Fsr%3D8-3%2Fqid%3D1155789849%2Fref%3Dpd_bbs_3%3Fie%3DUTF8
|
||||
+[6]:http://www.paulgraham.com/gh.html
|
||||
+[7]:http://www.fastcompany.com/online/06/writestuff.html
|
||||
+[8]:http://www.thedailywtf.com/
|
||||
+[9]:http://www.amazon.com/gp/redirect.html?link_code=ur2&tag=softwarbyrob-20&camp=1789&creative=9325&location=http%3A%2F%2Fwww.amazon.com%2Fgp%2Fproduct%2F0321117425%2Fsr%3D8-1%2Fqid%3D1154642314%2Fref%3Dpd_bbs_1%3Fie%3DUTF8
|
||||
+[10]:http://safari.oreilly.com/0321117425/ch01lev1sec1
|
||||
+[11]:http://www.softwarebyrob.com/articles/Timeline_and_Risk_Piss_Off_Your_Software_Developers.aspx
|
||||
Personality Traits of the Best Software Developers
|
||||
================================================================================
|
||||
I come from the world of corporate software development. It may not be the most glamorous side of software (it’s nowhere near as interesting as [shrinkwrap startups][1] or those fancy-dancy [Web 2.0][2] companies that show up in your browser every time you mistype a domain name), but it’s stable, pays well, and has its own set of challenges that other types of software development know nothing about.
|
||||
|
||||
For example, when was the last time someone working on the next version of Halo spent three weeks trying to gather people from accounting, marketing, product management, and their call center in order to nail down requirements that would likely change in 2 months once they’ve delivered the software?
|
||||
|
||||
Or when was the last time someone at [37Signals][3] sat through back to back weeks of [JAD sessions][4]?
|
||||
|
||||
In this world of corporate development I’ve known a few phenomenal developers. I’m talking about those A people whom you would quit your job for to go start a company. And the the more I looked at what makes them so good, the more I realized they all share a handful of personality traits. Well, not exactly a handful, more like four.
|
||||
|
||||
|
||||
|
||||
### Pessimistic ###
|
||||
|
||||
Admiral Jim Stockdale was the highest ranking US military officer imprisoned in Vietnam. He was held in the “Hanoi Hilton” and repeatedly tortured over 8 years. Stockdale told Jim Collins, author of [Good to Great][5], “You must never confuse faith that you will prevail in the end, which you can never afford to lose, with the discipline to confront the most brutal facts of your current reality, whatever they might be.”
|
||||
|
||||
After his release, Stockdale became the first three-star officer in the history of the navy to wear both aviator wings and the Congressional Medal of Honor.
|
||||
|
||||
Stockdale was a pessimist in the short-term because he faced the brutal facts of his reality, but was an optimist in the long-term because of his confidence that he would prevail in the end.
|
||||
|
||||
No one anticipates a catastrophic system failure by looking on the bright side. The best developers I know are experts at finding points of failure. You’ll often hear them quipping “What could possibly go wrong?” after someone makes a suggestion to handle a critical data transfer via nightly FTP over a dial-up connection. The best developers anticipate headaches that other developers never think of, and do everything within their power to avoid them.
|
||||
|
||||
On the flip side, great developers are optimistic, even downright confident, about their overall success. They know that by being a pessimist in the short-term, their long-term success is ensured. Just like Jim Stockdale, they realize that by confronting the brutal facts of their current reality they will prevail in the end.
|
||||
|
||||
### Angered By Sloppy Code ###
|
||||
|
||||
Paul Graham nailed it when [he said][6] “…people who are great at something are not so much convinced of their own greatness as mystified at why everyone else seems so incompetent.”
|
||||
|
||||
The worst nightmare for a great developer is to see someone else’s software gasping for air while bringing the rest of the system to its knees. It’s downright infuriating. And this isn’t limited to code; it can be bad installation packages, sloppy deployments, or a misspelled column name.
|
||||
|
||||
|
||||
|
||||
Due to the life and death nature of their products, NASA designs zero-defect software systems using a process that has nearly eliminated the possibility for human error. They’ve added layer after layer of checks and balances that have resulted from years of finding mistakes and figuring out the best way to eliminate them. NASA is the poster child for discovering the source of a mistake and modifying their process to eliminate the possibility of that mistake ever happening again. And it works. A quote from [this Fast Company article][7] on NASA’s development process says
|
||||
|
||||
“What makes it remarkable is how well the software works. This software never crashes. It never needs to be re-booted. This software is bug-free. It is perfect, as perfect as human beings have achieved. Consider these stats: the last three versions of the program — each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors. Commercial programs of equivalent complexity would have 5,000 errors.”
|
||||
|
||||
I’m not saying we have to develop to this standard, but NASA knows how to find and fix bugs, and the way they do it is to find the source of every problem.
|
||||
|
||||
Someone who fixes a problem but doesn’t take the time to find out what caused it is doomed to never become an expert in their field. Experience is not years on the job, it’s learning to recognize a problem before it occurs, which can only be done by knowing what causes it in the first place.
|
||||
|
||||
Developers who don’t take the time to find the source often create sloppy solutions. For hundreds of examples of sloppy solutions visit [The Daily WTF][8]. Here are a few I’ve seen in my career:
|
||||
|
||||
- An assembly is deleted from a server each time it’s rebooted. You could create a custom script to re-copy that assembly to the server after each reboot, or find out why the assembly is being deleted in the first place.
|
||||
- An image-manipulation script is hogging processor power for minutes at a time when it should run in under 10 seconds. You could make the script run at 2am when no one will notice, or you can take the time to step through the code and figure out where the real problem is.
|
||||
- A shared XML file is being locked by a process, causing other processes to fail when they try to open it. You could make several copies of the XML file so each process has its own, or you could troubleshoot the file access code to find out why it’s locking the file.
|
||||
- And on and on…
|
||||
|
||||
### Long Term Life Planners ###
|
||||
|
||||
This one was a little puzzling for the longest time, but I think I’ve finally put it together.
|
||||
|
||||
|
||||
|
||||
People who think many years down the road in their personal life have the gift to think down the road during development. Being able to see the impacts of present-day decisions is paramount to building great software. The best developers I know have stable family lives, save for retirement, own their own home, and eat an apple a day (ok, maybe not that last one). People who have spastic home-lives and live paycheck to paycheck can certainly be good developers, but what they lack in life they tend to lack in the office: the ability to be disciplined, and to develop and adhere to a long-term plan.
|
||||
|
||||
### Attention to Detail ###
|
||||
|
||||
I’ve known smart developers who don’t pay attention to detail. The result is misspelled database columns, uncommented code, projects that aren’t checked into source control, software that’s not unit tested, unimplemented features, and so on. All of these can be easily dealt with if you’re building a Google mash-up or a five page website. But in corporate development each of these screw-ups is a death knell.
|
||||
|
||||
So I’ll say it very loud, but I promise I’ll only say it once:
|
||||
|
||||
**I have never, ever, ever seen a great software developer who does not have amazing attention to detail.**
|
||||
|
||||
I worked with a programmer back in school who forced anyone working with him to indent using two spaces instead of tabs. If you gave him code that didn’t use two spaces he would go through it line-by-line and replace your tabs with his spaces. While the value of tabs is not even a question, (I’ve long-chided him for this anal behavior) his attention to such a small detail has served him well in his many years designing chips at Intel.
|
||||
|
||||
### So There You Have It ###
|
||||
|
||||
The next time you’re interviewing a potential developer, determine if she has the four personality traits I’ve listed above. Here are a few methods I’ve found useful:
|
||||
|
||||
- Ask if they’re an optimist or a pessimist
|
||||
- Ask about a time when they found the source of a problem
|
||||
- Find out if they save for retirement (you can work this in during discussions of your company’s retirement plan)
|
||||
- Make an obvious misspelling in a short code sample and ask if they see anything wrong
|
||||
|
||||
We know from [Facts and Fallacies of Software Engineering][9] that the best programmers are up to [28 times better][10] than the worst programmers, making them the best bargains in software. Take these four traits and go find a bargain (or better yet, make yourself into one).
|
||||
|
||||
If you liked this article you’ll also like my article [Timeline and Risk: How to Piss off Your Software Developers][11].
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.softwarebyrob.com/2006/08/20/personality-traits-of-the-best-software-developers/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://www.joelonsoftware.com/
|
||||
[2]:http://www.econsultant.com/web2/
|
||||
[3]:http://www.37signals.com/
|
||||
[4]:http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci986072,00.html
|
||||
[5]:http://www.amazon.com/gp/redirect.html?link_code=ur2&tag=softwarbyrob-20&camp=1789&creative=9325&location=%2Fgp%2Fproduct%2F0060794410%2Fsr%3D8-3%2Fqid%3D1155789849%2Fref%3Dpd_bbs_3%3Fie%3DUTF8
|
||||
[6]:http://www.paulgraham.com/gh.html
|
||||
[7]:http://www.fastcompany.com/online/06/writestuff.html
|
||||
[8]:http://www.thedailywtf.com/
|
||||
[9]:http://www.amazon.com/gp/redirect.html?link_code=ur2&tag=softwarbyrob-20&camp=1789&creative=9325&location=http%3A%2F%2Fwww.amazon.com%2Fgp%2Fproduct%2F0321117425%2Fsr%3D8-1%2Fqid%3D1154642314%2Fref%3Dpd_bbs_1%3Fie%3DUTF8
|
||||
[10]:http://safari.oreilly.com/0321117425/ch01lev1sec1
|
||||
[11]:http://www.softwarebyrob.com/articles/Timeline_and_Risk_Piss_Off_Your_Software_Developers.aspx
|
||||
|
||||
@@ -1,37 +0,0 @@
|
||||
Thoughts on Mir and the community
|
||||
================================================================================
|
||||
I realized this week I needed a break from sampling distributions. I love technology, especially when it involves open source software, but this past week I realized I'd had too much of a good thing. As I scrolled through the list of distributions released over the previous two weeks and combed my inbox for suggestions I realized few of the distributions jumped out at me. My reaction to reading descriptions such as "The last distribution you will ever try" or "Just works" was skepticism. Most of the releases announced over these past two weeks have been niche players and beta releases anyway, so this seemed like a good time to take a break, to take a week off from installing open source operating systems, to have a week off from taking notes on the Linux community's latest and greatest. This week I would like to turn my focus (and yours, if you will indulge me) on Canonical's new display server, [Mir][1].
|
||||
|
||||
Mir, for those of you who are not familiar, is a display server designed to replace the X graphics software common to most Linux (and UNIX) operating systems. The Mir software is designed to work on desktops, laptops, tablets and phones. If all goes as planned, Mir will provide better performance and use less energy than X. The name Mir is a Russian term meaning community or the world (as well as "peace") and fits the naming pattern of other Canonical projects which include Ubuntu and Unity.
|
||||
|
||||
Right from the start Mir generated some controversy. Originally Canonical (and several other open source contributors) had been putting their development efforts into a new display server technology called [Wayland][2]. Wayland was also supposed to be a faster, lighter, less cumbersome display technology that would someday replace X on most devices. However, development on Wayland was slow and not going in quite the direction Canonical had hoped and thus Mir was born. Right away many people expressed concern that Canonical was dividing the Linux ecosystem by introducing a new display server, a technology which would use different drivers than Wayland and, therefore, possibly divide development efforts. There were also questions as to why Canonical needed to make their own display server rather than influencing Wayland's development, questions Canonical kindly [answered][3].
|
||||
|
||||
For a while all seemed quiet, but then, during the month of September, Intel (a Wayland contributor) [rejected software patches][4] provided by Canonical which would allow Intel's drivers to work with Mir. This was a reversal of Intel's earlier [apparent support][5] for Canonical's new display server. The reasoning was not clear, but it seemed as though Intel was unwilling to continue support for Mir, either in an effort to avoid cluttering up their own driver code or because Intel's focus was on Wayland. Either way, it meant more work for the Canonical developers who will need to maintain the driver code themselves. Then, at the start of October, Canonical [announced][6] Mir would not ship by default in the upcoming release of Ubuntu 13.10. The developers had decided there were still bugs to work through, features to complete, and it was decided Mir would be delayed for a release cycle.
|
||||
|
||||
Given Mir's status this seemed like a reasonable move, at least to me. In the past Canonical has released buggy code into its products (PulseAudio and the Unity desktop spring to mind) and it seemed as though the company was taking a more conservative approach, protecting its users from experimental code, trying to insure a better user experience. Yet, for some reason, people's reactions have been mostly [negative][7]. Mir's temporary delay seems to be blood in the water for critics of the display server. Commentators are taking the opportunity to claim the project was poorly planned, that the technology is under-supported, that it won't be able to complete with Wayland, which has recently been [gaining][8] [momentum][9].
|
||||
|
||||
As someone who does not have a horse in this race, as someone who does not care if his desktop is running Mir, Wayland or X, it has been a puzzling few weeks. It seems as though the community at large, not just a vocal minority of idle commentators, but active developers, are betting against Mir before the software gets a trial run. Intel's move, for example, of not only refusing to assist in driver development, but actively blocking support, is troublesome. Former Red Hat employee, Matthew Garrett, taking shots at Mir also strikes me as a poor use of time and energy. Critics claiming Ubuntu being the only distribution to currently adopt Mir is [a sign Mir won't be successful][10] seems to me to be an odd and unrealistic viewpoint. Wayland has yet to be included as the default display server in any mainstream distributions and critics are not complaining about its delay.
|
||||
|
||||
Most of us see the open source world as a place where anybody can scratch an itch, develop a new idea and release it into the wild. It doesn't need to have mass appeal, it does not need to sell a certain number of units, developers are able to create their visions and share them freely. At least it seems as though developers can do this as long as they do not work for commercial companies. The more feedback I hear about Mir (especially negative feedback) the more I get the impression critics are opposed to Mir not on the technology's merits, but because Canonical is behind its development. Ubuntu is a widely used and popular distribution and, when one is king of the hill, everyone wants to push you. The development of Mir isn't hurting anyone, it isn't being forced on other distributions (even Ubuntu community distributions can use Mir or ignore it as they like), and [Mir is open source][11]. Mir represents a fresh solution to a long-standing concern -- the imperfections in X -- and Canonical has shown a willingness to develop and even maintain drivers to prevent diluting efforts from third-party coders. Canonical has basically said they want to try something new, do not expect any help or cooperation and will not push their technology out to the public before it is ready. Despite their best efforts many people in the open source community appear to want them to fail.
|
||||
|
||||
Earlier I mentioned that my review options were limited this week as many recent distribution releases have been beta tests rather than full releases. My point of view is that developers should be given the time to get their projects to a stable release before the software is judged. When I review a distribution I try to focus on stable releases and I attempt to avoid reading other reviews of the same project and anything about the developers' personal lives. I want to evaluate a project based on its strengths and problems, as free as possible from the taint of public opinion or past releases. It's not always possible, I am human and flawed, prone to being subjective. Still, I feel the community at large should take the same approach when it comes to Mir. Perhaps the technology will always be buggy or maybe it will be stellar. In either case no one is forcing Mir onto the open source community as a whole, it is Canonical's pet project, and I think the community should be cheering them on for trying something new. Canonical, as with any other open source developer, is free to dedicate its resources to scratching its own itch and seeing what comes about as a result. I, for one, am looking forward to comparing Wayland, Mir and X over the coming year to see which one best serves my needs. When we have options we all win.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://distrowatch.com/weekly.php?issue=20131014
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:https://wiki.ubuntu.com/Mir/
|
||||
[2]:http://wayland.freedesktop.org/
|
||||
[3]:https://wiki.ubuntu.com/Mir/Spec?action=show&redirect=MirSpec#Why_Not_Wayland_.2BAC8_Weston.3F
|
||||
[4]:http://arstechnica.com/information-technology/2013/09/intel-rejection-of-ubuntus-mir-patch-forces-canonical-to-go-own-way/
|
||||
[5]:http://www.phoronix.com/scan.php?page=news_item&px=MTQ1MzU
|
||||
[6]:http://fridge.ubuntu.com/2013/10/01/xmir-update-for-ubuntu-13-10/
|
||||
[7]:http://mjg59.dreamwidth.org/28032.html
|
||||
[8]:http://wayland.freedesktop.org/toolkits.html
|
||||
[9]:http://sourceforge.net/projects/rebeccablackos/
|
||||
[10]:http://lwn.net/Articles/556591/
|
||||
[11]:https://wiki.ubuntu.com/Mir/License
|
||||
@@ -1,43 +0,0 @@
|
||||
openSUSE Summit Schedule Ready!
|
||||
================================================================================
|
||||
As you may well know, [Disney’s Coronado Springs Resort][1] in beautiful Florida will welcome all Geekos to this year’s openSUSE Summit from November 15 to 17. This will be a great event, if the brand new schedule is any indication! It has just been made public, together with information about our keynote speakers.
|
||||
|
||||
|
||||
|
||||
### The keynotes ###
|
||||
|
||||
We are very excited to announce our keynote speaker for the keynote on Saturday. [Mykel Alvis][2] will speak to us about fostering better communication, a topic that is very important within openSUSE and any open source project. Mykel’s current interest lie in IT automation and he has a plethora of experience in the enterprise and open source realms as developer and consultant. Mykel has spoken at many events, including this year’s South East Linux Fest and Puppet Camp.
|
||||
|
||||
[][3]
|
||||
|
||||
### The schedule ###
|
||||
|
||||
Thanks to those interested in sharing their knowledge we were able to compile a great schedule with presentations and workshops. The presentation and workshop schedule is now posted on the [openSUSE Summit web site][4]. There will be systemd and image building workshops, talks about technical subjects like virtualization or building scalable web apps to more social subjects like marketing and advocacy.
|
||||
|
||||
We will also have a fun game or two going on during the summit, and don’t forget if you [purchase a ticket][5] in support of the event ([registration][6] and attendance is free, of course) you will receive a very nice backpack as welcome gift.
|
||||
|
||||
[][7]
|
||||
|
||||
### Help promote the Summit! ###
|
||||
|
||||
We’ve been working on some promotional materials for the openSUSE summit. The flyer on the right you can click – and then get the source in a format you can print and hand out!!! We also have some pics you might want to put on your site, linking to the event, like the logo on the top of this article. Find it all in github.
|
||||
|
||||
### Be there and have fun! ###
|
||||
|
||||
We’re looking forward to the Summit. Getting to know one another, learning new technologies, getting hands-on in workshops – it’s fun and useful. Be there!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://news.opensuse.org/2013/10/21/opensuse-summit-schedule-ready/
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
[1]:http://summit.opensuse.org/#location
|
||||
[2]:https://plus.google.com/117207740852943355900/posts
|
||||
[3]:http://summit.opensuse.org/
|
||||
[4]:http://summit.opensuse.org/#program
|
||||
[5]:https://buy.suse.com/store/suse/en_US/buy/productID.264835100
|
||||
[6]:https://conference.opensuse.org/osem/conference/summit13/register
|
||||
[7]:https://github.com/openSUSE/artwork/tree/master/Marketing%20Materials/Events/openSUSE%20Summit/Summit%202013/Flyers
|
||||
Reference in New Issue
Block a user