Make posts page show only an excerpt, correct datetime

1 files changed, 2 insertions, 0 deletions

diff --git a/_posts/2014-10-10-open-bug-tracking-empowers-users.markdown b/_posts/2014-10-10-open-bug-tracking-empowers-users.markdown
index c627add..99493dd 100644
--- a/_posts/2014-10-10-open-bug-tracking-empowers-users.markdown
+++ b/_posts/2014-10-10-open-bug-tracking-empowers-users.markdown
@@ -11,6 +11,8 @@ redirect_from: "/writing/open-bug-tracking-empowers-users/"
 
 The rise of networked information economy described by Yochai Benkler has both enabled and been enabled by the free software movement. A central facet of this emerging culture is its [participatory nature](http://www.benkler.org/Benkler_Wealth_Of_Networks.pdf). This is reflected in the flagships of the free culture movement such as Wikipedia, where the time and expertise of many is combined to create a competitive alternative to commercial offerings. Though free software aims to be a participatory medium, due to the highly technical and often specialized nature, the barriers to entry for the average “netizen” are often relatively high.
 
+<!--more-->
+
 In order to organize any software project a separate program called a bug or issue tracker is often used to categorize and track the progress of bugs in the code, almost like a giant and detailed to-do list. A bug tracker could be anything from a spreadsheet to a sophisticated routing and tracking system that integrates with help desk software and documentation. The larger a project is, the more [crucial it becomes to use a bug tracker](http://www.joelonsoftware.com/articles/fog0000000029.html), as it facilitates the necessary communication between developers and testers as to who is working on what at any given time. Often, bug trackers are accessed by members of the software team through a web browser, as this is an easy and efficient way to collaborate. However, with traditional commercial software, the contents of the bug tracker tends to be considered highly sensitive, proprietary information that should not be disclosed in order to protect the company’s competitive advantage. After all, exposing to the public issues with the software might result in them switching to a competitor. However, for free or open source software projects, using a publicly available bug tracker that is open to anyone who wants to see it is the de-facto standard, and rightfully so.
 
 There are fundamentally two ways that using an open bug tracker benefits an open source project. First and foremost, as Benkler points out, free software projects tend to have a wide variety of contributors. From gurus who know the code base inside and out, to casual hackers, every contributor brings a different level of skill and expertise to the project. In software engineering, it is commonly understood that you cannot expect everyone to have identical skills such that their role in the team is totally flexible. To maximize the team’s productivity, it is best to take into account each member’s skill set and expertise. For example, if one of the gurus of a mature open-source project finds an error in some of the help files, it would probably be a waste of time to go and fix it when they could be spending their time addressing a highly complex and sophisticated bug or issue with the code. Rather, filing a bug report would allow a newcomer to the project who has not yet accumulated the technical sophistication to address the documentation. In free and open source software, the bug tracker is how this organization and self-assignment of tasks takes place.