There's a proposal about integrating this type of feature into the Bugzilla bug tracking system. The idea is that there would be an extra field on each bug page that would allow anyone to bid on that bug. One would think that the ones bidded the highest would be fixed first (after being superseded by critical bugs and the like, of course).
Yes, but it's not quite "build us a front-end and get $500". It's "be the first to build us a front-end and get $500". If you come in second, or miss the feature set and get delayed, you very well may get nothing for your effort.
You can do OSS work on Rent-A-Coder? I've looked at a bunch of offers on there, and they all say at the bottom that any work done is "for-hire", owned by the person paying you.
Public companies are required to maximize the value of the company, not profits. Doing good things while making a decent profit is certainly more valuable than making a massive profit off of lies and extortion (see Enron).
While it's true that you don't have to compile nearly as much as with a Stage 1 install, it's not true that you can install Gentoo without compiling anything.
If you follow the manual, there's a few things you need to emerge before you copy over the binary packages (kernel, grub, cron, syslog, etc.).
Sounds like a personnel/cultural problem. Because a set of people abuse the paperwork doesn't mean the paperwork should be done away with altogether.
In a large enterprise like NASA, there needs to be documentation that certain actions are performed. If that documentation is false, well, you've got another problem on your hands.
You know, having every distro package its own version of every piece of software sounds like an aweful lot of redundant effort. The holy grail would be one package repository with packages that work on every distro out there. And standards like FHS and LSB contribute toward that goal.
(a) Except as otherwise provided in this title, whoever without
authority makes, uses, offers to sell, or sells any patented
invention, within the United States or imports into the United
States any patented invention during the term of the patent
therefor, infringes the patent.
Notice it includes "use" as a patent violation. The likelihood that a patent owner would sue an individual for the use of something that infringes a patent is slim to none, but technically, I believe it is infringement.
This view is upheld by a Canadian court case I found: http://www.dww.com/newsletter/may26_04.htm. Canadian law has a similar "use" provision, so I have no reason to believe it would be any different in this country.
You obviously didn't even read the summary. This article is about other people hosting a website for a prisoner, and posting content at his/her behest. No, prisoners can't host their own websites.
I would consider things somewhat 'edgy' that I wouldn't want to watch with a relative. I have no problem watching The Simpsons or Futurama at home with the 'rents around, but I turn off Family Guy and South Park. There were just one too many embarrassed feelings after faked orgasms or 'women really like sexual abuse' jokes.
(a) Except as otherwise provided in this title, whoever without
authority makes, uses, offers to sell, or sells any patented
invention, within the United States or imports into the United
States any patented invention during the term of the patent
therefor, infringes the patent.
The VLC guys "make", and any downloader "uses", so we all infringe in the US.
Testing also doesn't have a proper security team. For a package with a security update, the package must be updated to the new version, make its way through Unstable, then get moved to Testing. Stable gets it the first day.
Slashdot Mirror
It also creates a mess of your Add/Remove Programs list (multiple entries).
It's called taking a stand on principle versus taking the pragmatic approach. It comes up every day on this forum.
If there were a choice between the two, it seems to me that the geek crowd would prefer the former.
Like this?
Don't forget http://www.opensourcexperts.com/
There's a proposal about integrating this type of feature into the Bugzilla bug tracking system. The idea is that there would be an extra field on each bug page that would allow anyone to bid on that bug. One would think that the ones bidded the highest would be fixed first (after being superseded by critical bugs and the like, of course).
Yes, but it's not quite "build us a front-end and get $500". It's "be the first to build us a front-end and get $500". If you come in second, or miss the feature set and get delayed, you very well may get nothing for your effort.
You can do OSS work on Rent-A-Coder? I've looked at a bunch of offers on there, and they all say at the bottom that any work done is "for-hire", owned by the person paying you.
What makes you think that going public equals evil? Because you consider certain public companies evil, so it must be a trait of the entire system?
Public companies are required to maximize the value of the company, not profits. Doing good things while making a decent profit is certainly more valuable than making a massive profit off of lies and extortion (see Enron).
What does -Os do, compared to -O2 or -O3? Absolutely nothing?
While it's true that you don't have to compile nearly as much as with a Stage 1 install, it's not true that you can install Gentoo without compiling anything.
If you follow the manual, there's a few things you need to emerge before you copy over the binary packages (kernel, grub, cron, syslog, etc.).
I got my number from Wikipedia. I'll admit I didn't dig any deeper, but their chart looks convincing.
Except Soyuz doesn't have the same capabilities as the Shuttle. It's not like you can just replace the Shuttle with Soyuz and do the same things.
Sounds like a personnel/cultural problem. Because a set of people abuse the paperwork doesn't mean the paperwork should be done away with altogether.
In a large enterprise like NASA, there needs to be documentation that certain actions are performed. If that documentation is false, well, you've got another problem on your hands.
Just for the record, the shuttles have collectively flown 113 missions so far.
You know, having every distro package its own version of every piece of software sounds like an aweful lot of redundant effort. The holy grail would be one package repository with packages that work on every distro out there. And standards like FHS and LSB contribute toward that goal.
The LSB just mandates that your distro be able to use RPMs, not that it be an RPM-based distro. Both Gentoo and Debian offer rpm as a package.
Who are the two big players? Red Hat and Novell?
You may be interested to learn that RHEL 3 and SUSE 9.2 are LSB-compliant.
The original complaint of the article submitter seems to be that the two big players are the only ones that conform to the standards.
This view is upheld by a Canadian court case I found: http://www.dww.com/newsletter/may26_04.htm. Canadian law has a similar "use" provision, so I have no reason to believe it would be any different in this country.
FYI, I believe it's already illegal in the US.
The description is misleading. 9.3 includes Firefox 1.0.1. I would assume that 1.0.3 will be released as a security update.
You obviously didn't even read the summary. This article is about other people hosting a website for a prisoner, and posting content at his/her behest. No, prisoners can't host their own websites.
I would consider things somewhat 'edgy' that I wouldn't want to watch with a relative. I have no problem watching The Simpsons or Futurama at home with the 'rents around, but I turn off Family Guy and South Park. There were just one too many embarrassed feelings after faked orgasms or 'women really like sexual abuse' jokes.
Testing also doesn't have a proper security team. For a package with a security update, the package must be updated to the new version, make its way through Unstable, then get moved to Testing. Stable gets it the first day.