Canonical To Develop Some Ubuntu Features In Private

[Figueiredo]

Canonical announced that 3.5 years ago: http://arstechnica.com/gadgets/2009/...run-on-ubuntu/
As with most of Canonical's stuff: Big words, little substance.

Well, i hope this is one of those things not being openly developed according to the OP.

[bug77]

I'm sorry but you're wrong. Actually most successful FOSS projects are developed in an openly accessible repo, even though they are not advertised, yet. Even in case of Ubuntu you can usually browse on launchpad.net and find such projects – or at least you could.

http://en.wikipedia.org/wiki/Branching_%28software%29
Yes, you can browse the project. Doesn't mean you can browse all branches.

[Awesomeness]

http://en.wikipedia.org/wiki/Branching_%28software%29
Yes, you can browse the project. Doesn't mean you can browse all branches.

In most successful FOSS projects you can browse all branches. GNOME Shell was developed that way. From early mockups until final release: Everything was accessible from the outside.
KDE even has a policy against private branches.

[Figueiredo]

Well, i hope this is one of those things not being openly developed according to the OP.

"The source code of the execution environment isn't available yet, but the developers plan to publish it soon. They hope that making it available and inviting the community to participate will help build momentum around the project and accelerate development."

Canonical might be learning something from valve...

If canonical play it's card right, we could have homebuild "consoles" playing Steam, as well as OUYA games, that would put any other gaming platform to shame.

[curaga]

KDE even has a policy against private branches.

Where? I don't see such on the SVN commit policy page:
http://techbase.kde.org/Policies

[Pallidus]

"some sexy 13.04 surprises"

[liam]

"some sexy 13.04 surprises"

That's extremely offensive.

[Awesomeness]

Where? I don't see such on the SVN commit policy page:
http://techbase.kde.org/Policies

I have no idea where. I've only read about it in a mailing list message quite a while ago. The dev of some KDE app had a private branch on his home PC and his merges to master/trunk overwrote changes that other devs did. That in turn broke translations which is why it came to light.
The dev got an explanation that his development stye was against KDE policy.

[Pallidus]

offensive is having your operating system dial to X or Y when you perform a search (on your freaking drive)

offensive is seeing a company so desperate to monetize they will allow their system to be 1. compromised 2. amazon's bitch.


fuck canonical and fuck amazon, vive linux libre free of money grabbing parasites.

[bug77]

I have no idea where. I've only read about it in a mailing list message quite a while ago. The dev of some KDE app had a private branch on his home PC and his merges to master/trunk overwrote changes that other devs did. That in turn broke translations which is why it came to light.
The dev got an explanation that his development stye was against KDE policy.

First, if it's not on their web site, it's not a policy. It's a recommendation, at best.
Second, it doesn't sound like they have anything agaist private branches, but something against not rebasing before committing. And that's VCS 101.
Third, easy branching for personal use us one of the chief reasons Linus bothered to write git.