Mandrake Linux Development Process Changes
joestar writes "Just found at MandrakeLinux.com: 'MandrakeSoft today announced a major evolution in the way that future Mandrake Linux distributions will be engineered and released. The purpose of this new development process is to provide the highest level of new features, as well as maximizing the quality of new products.' In short: for each release, there will be a 'Community' release, equivalent to a common Mandrake release, with all latest features. Several months later an 'Official' release - based on the 'Community' - will be available. Both of them will be released publicly and supported. The new process will start with the upcoming Mandrake 10.0."
Comment removed based on user account deletion
if the 1.0 build is supposed to be stable then Mandrake 10.0 should be 10x stable?
When anger rises, think of the consequences.
Confucius (551 BC - 479 BC)
Plain:
http://poetry.rotten.com/weightlifter/
Linked:
http://poetry.rotten.com/weightlifter/
The Jewpranks threat has been eliminated by the GNAA says Adolf Jackson X, head of GNAA counter insurgency. "Those stupid kikes are on the run" he reports, "and we'll continue operations in all sectors until the world has been rid of this threat to global nigger homosexuality"
In other news, Cowboy Kneel has lodged a Yoda doll up his ass and has beeen unable to remove it.
However I am confused as to what I should do next. Please advise!
TOTO A Distributed Annotation System for the World Wide Web TABLE OF CONTENTS INTRODUCTION 3 TEAM MEMBERS 3 PROJECT MANAGEMENT STRUCTURE 3 OVERVIEW, SCOPE AND PURPOSE OF THE SYSTEM 3 MEASURABLE ORGANIZATIONAL VALUE 4 DESCRIPTION 4 REQUIREMENTS 8 FEATURES 9 Distributed Network 9 Reputation System 9 Web User Interface 9 NON-FEATURES 9 Constraints 10 INTERFACES 10 CHANGE LOG AND EXPECTED CHANGES 11 CONTINGENCIES 13 MEASUREMENTS 13 ORIGINAL GANTT CHART 14 CURRENT GANTT CHART (AS OF 01-29-2004) 14 CURRENT QFD MEASUREMENT 14 FUNCTION POINTS 15 VALUE ADJUSTED FUNCTION POINTS 17 Value Adjustment Factor 17 COCOMO 17 PERFORMANCE MEASUREMENTS 18 Toto's Page-Serving 18 Toto's revised Page-Serving: 19 GLOSSARY 20 REFERENCES 20 Introduction Revision: 1.0 Author: Ellen C. Matchey Team Members Phil DePetro Chris Guarino Dan Kopko James Light Doug Malnati Ellen C. Matchey Jae Park Mike Postaski Asif Siddiqui Project Management Structure Overview, Scope and Purpose of the System Phil DePetro The purpose of this project is to create a distributed web-annotation system that will allow users to comment on webpage content and have this content be viewed by other users using the system (comments would be in-lined with the webpage text). A targeted use of this system is to counterbalance rightwing and leftwing bias in the media. Through the use of this system users would be able to make comments on news-websites, such as CNN.com, in an anonymous fashion if they feel the news articles are biased in some way. With this growing popularity of this system and feedback on web content, the reporters would eventually be prompted to respond to the users. On the technical side, this system seeks to create a software package that provides access to a distributed network. This package would act as a proxy server that would modify web pages to show comments presented by other users on the network. It would also allow the user to add his/her own comments into the distributed share. Comments will be displayed based on a distributed reputation as well as users personal preferences. Requests for comment/reputation information will be handled with the intent to conceal both the requester and the source of the data as much as possible. The creator of the project (the project manager) devised it as an attempt to mitigate the bias, inaccuracies, and neglect of information he saw in news coverage. The rest of the team shares the same sentiment. Measurable Organizational Value Dan Kopko To provide the Internet public with an intuitive interface by which they can make and share textual annotations and commentary for any website. Description Ellen C. Matchey Currently, Toto allows a user to change and add-to the text on web pages accessible through the user's localhost using the Mozilla browser. It also highlights unaltered text in purple and changed text in green. As shown in Figure 1, the current architecture consists of a Toto proxy that sits between the browser and the Internet listening for requests (i.e. to get a new website or to post changes). Once a request is made, an HTTP Relay thread is created to take care of the thread. If the thread is a request to view a new page (figure 2), the webpage is broken down into several components that isolate the text as shown in figure 4. Then the text in the website is checked against the database to see if any changes/comments have been added (figure 2). If changes were found the text is replaced by text in the database and highlighted with green, otherwise it is displayed unchanged highlighted in purple. If there is a request for a new change to text on a website (figure 3), a key for the text is created. Then, both the key and the changed text are stored on a mySQL database on the user's computer. Next time this website is accessed by the user, keys for the text will be generated, checked against the database, and when there is a match the original text will be replaced by the one stored in the database. Toto is being developed in Java and uses a mySQL database. The goal is to
Yet another crippling blow has struck what's left of the *BSD community, as a soon-to-be-released report by an independent commission doing a year-long study concludes: *BSD is dead and mummified. Here are some of the commission's findings:
.005% of internet servers. "It's just not reliable," said Christine McGee, VP of Technology for eBay, Inc. "Nor do we find it a very modern OS. I would recommend Linux to anyone contemplating a server OS, or maybe Windows, before I would recommend a BSD."
Fact: the *BSDs have balkanized yet again. There are now no less than twelve separate, competing *BSD projects, each of which has introduced fundamental incompatibilities with the other *BSDs, and frequently with Unix standards. Average number of developers in each project: fewer than five. Average number of users per project: there are no definitive numbers, but reports show that all projects are on the decline.
Fact: Apple is quietly changing the base kernel for OS X from *BSD to Linux. Insiders report that Apple's technical leadership has grown tired of the licensing battles and is seeking a more modern license; they find Linux's license more appealing. Many Apple technology experts -- from OS developers all the way up to Steve Jobs -- find Linux to be a more advanced OS, which will enable Apple to release a more mature product. The frequent hallway arguments and fistfights among the *BSD developers Apple has hired has also contributed to the decision.
Fact: XFree86 is dropping support for *BSD. The remaining core group believes that the *BSDs have strayed too far from Unix standards and have become too difficult to support along with Linux and Solaris x86. "It's too much trouble," said one anonymous developer. "If they want to make their own standards, let them doing the porting for us."
Fact: Many user-level applications will no longer work under *BSD, and no one is working to change this. The GIMP, a Photoshop-like application, has not worked at all under *BSD since version 1.1 (sorry, too much trouble for such a small base, developers have said). OpenOffice, a Microsoft Office clone, has never worked under *BSD and never will. ("Why would we bother?" said developer Steven Andrews, an OpenOffice team lead.)
Fact: servers running OpenBSD, which claims to focus on security, are frequently compromised. According to Jim Markham, editor of the online security forum SecurityWatch, the few OpenBSD servers that exist on the internet have become a joke among the hacker community. "They make a game out of it," he says. "(OpenBSD leader) Theo [de Raadt] will scramble to make a new patch to fix one problem, and they've already compromised a bunch of boxes with a different exploit."
Fact: NetBSD, which claims to focus on portability (whatever that is supposed to mean), is slow, and cannot take advantage of multiple CPUs. "That about drove the last nail in the coffin for BSD use here," said Michael Curry, CTO of Amazon.com. "We took our NetBSD boxes out to the backyard and shot them in the head. We're much happier running Linux."
Fact: There are almost no FreeBSD developers left, and its use, according to Netcraft, is down to a sadly crippled
Fact: DragonflyBSD, yet another offshoot of the beleaguered FreeBSD "project", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing." Netcraft notes that DragonflyBSD is run on exactly 0% of internet servers.
With these incontroverible facts staring (what's left of) the *BSD community in the face, they can only draw one conclusion: *BSD is dead and mummified.
Do you think it's a coincidence?