This would be much better than have to pay $70 and forced to get everything (i.e. like cable or directv)

o stop supporting enterprise deployments (by rapid release, no bug fixes only)
o start an enterprise working group
o profit! (charge for support)

How much are they willing to compensate me if they lose my data? What, they won't? Don't trust themselves?

Yes, I am aware of that. Your missing my point. I wasn't trying to iterate over
everything that a test plan will cover.

Writing a test plan doesn't ensure you have met any of your requirements or
than even if your requirements are worth a crap to start with.

The point being writing a test plan does not mean you have a good plan on
how to verify your product (from unit test through deployment and maintainance).
That is what's important. If you want write a test plan which references
to requirements, great. Usually required for any contracts anyway.

But it's the plan that is important, not the document. I haven't see a
checklist item yet for a good plan/bad plan. And I've seen many
really bad test plans go by which fulfilled their process checkmark.

> However if you're likely to have millions of people depending on your code, which will
> alwso be modified by other people, then you had better have a good process as well.

A good process means nothing. Understanding why a process wants you to do something
is what's important. Checklists are bad. Making sure the right things get done is what
is important. Writing a test plan isn't important. Making sure you have good test coverage
is important.

I have been writing code professionally for over 20 years now. I have been at a handful of
different companies, and gone through a few handfuls of various processes (2167a was
the first one I had to use coming out of school). I've worked on very large projects and
very small projects.

For small to the small side of medium projects, it comes down to the people
working on the project, period.... In my experience, a standardized process doesn't
effect the success of a project either way. If you have a good project lead, and good people,
you will have a "process" or a somewhat standard way to do things. It doesn't have
to be documented in a formal document. But it will be there even if you don't realize it.

Large projects are a mess. You need a standardize process as painful as it is. One that
allows you to integrate early and often. The first thing you need to realize that the % of
incompetence rises the larger the project. It's easier to hide in a large project. It's easy to
hide in a process that generates a lot of information. You have to identify problem areas
in interfaces, and people, early and often..

> How about the real reason, stated right there in TFS. Can you read?

Because we don't believe them? If android were *really* open,
it would be developed in the open. An open drop of code after products
are already shipping it certainly not in the spirit of open source.

Personally, I think it's more about Google being threatened by amazon.com,
their app store, and their likely future tablet.. It's also been reported that google
has been threatening tablet/phone makers with using non google services. The
reason Google gave, seems the less likely reason to me.

I'm still hoping for a Ubuntu tablet. But Ubuntu doesn't seem to be that open these
days either... sigh....

> That being said, making copyright law on that basis is arguably unconstitutional.

Why do you think they are worried about that? :-) They had no problem extending the copyright
duration *retroactively* multiple times. The constitution limits the copyright duration. If you allow
it to be extended retroactively, you can not enforce that.

It's hard to argue that the Justices don't understand that concept. It seems likely (to me at least)
that they did understand they were going against the constitution and didn't care.

As long as they clearly define:
      o exactly when customers will be throttled
      o exactly how much customers will be throttled
      o allow customers to see how much they been throttled for each month
      o allow customers to opt out of their contract without penalty if they don't
            agree to the change

Seems perfectly reasonable if they did that.... Not holding my breath :-)

> What's the usability of such energy producing machinery?

It's amazing what you can do with 100+ year old technology... steam engine... generates electricity...
      http://www.alternative-energy-news.info/molten-salt-solar-plant/

I'm getting sick of Assange's promises of all this great information they are "going to leak". He has all of this info on corruption in the US banking system, on rich people evading taxes, and a bunch of other info which will be released if he disappears.

If he has information on illegal dealings, corruption, etc., release it.. Why the threats, why the talk? His current behavior is more like someone
trying to shake down folks, not someone trying to uncover the truth.

> RMS wrote the Gnu manifesto 25 years ago, one could argue it all started then

no. before GNU, there was "open source" code ;-) From http://en.wikipedia.org/wiki/Bsd
      "first Berkeley Software Distribution (1BSD), which was released on March 9, 1978"

I'm sure there was open source code before that too..

My son's Kindle has this problem... I removed the cover the other day and it has not had it sense. I just broke
out the multimeter, I was unable to get an electrical path even when scraping the paint on the hooks.

from wikipedia "Paul Buchheit is an American computer programmer and entrepreneur. He was the creator and lead developer of Gmail. He developed the original prototype of Google AdSense as part of his work on Gmail. He also suggested the company's now-famous motto "Don't be evil" in a 2000 meeting on company values.[1]"

Hmm, why the hate.. It sounds like he's done some stuff.. What have you done?

I would much rather have a Ubuntu based ARM netbook than a ChromeOS one. Just because an ARM netbook may be interesting.. Doesn't mean ChromeOS is.

by "root" I mean wait for someone to find a bug in the firmware so a program can be created to re-program the flash.

i.e. see Droid 2. It is not open.
      http://www.androidpolice.com/2010/08/25/motorola-droid-2-rooted/