I think that including a meerkat would be cool, but the aren't supposed to
be seen by the end user. *Most* users don't use PPAs or edit the
sources.list file. Even if the did they would be seeing *maverick* and not *
meerkat*.
On Tue, Aug 31, 2010 at 3:39 PM, Yorvyk wrote:
> On Tue, 31 Aug 2010 2
I totally agree with you. A different cover each release would be much
cooler, but may not be feasible. If we do decide to keep the same cover, it
a few tweaks should be made - not identical but similar. For every LTS the
cover should be completely redesigned *from scratch*.
On Tue, Aug 31, 2010 a
On Tue, 2010-08-31 at 20:08 +0100, Denise N. Wood wrote:
> On the wiki page that Thorston linked has a bit about consistency:
> https://wiki.ubuntu.com/ubuntu-manual/Artwork#Consistency
>
> It mentions changing it every 3 releases -- but three seems like such
> an arbitrary number.
No, it does no
On Tue, 31 Aug 2010 23:47:27 +1200
Benjamin Humphrey wrote:
> Sayantan,
>
> We don't want to use references to the code names anywhere in the manual, as
> they're just development names and the user isn't meant to see them.
>
> I know Ubuntu versions are often referred to by their development n
I think this is a good idea. It might be difficult reinventing the cover
each release. Perhaps pick a design like [1] each LTS then just change
the wallpaper and make little tweaks. Personally, I think a new cover
every release would be cooler, but I'm not sure how feasible it is.
[1]
http://www.a
On the wiki page that Thorston linked has a bit about consistency:
https://wiki.ubuntu.com/ubuntu-manual/Artwork#Consistency
It mentions changing it every 3 releases -- but three seems like such
an arbitrary number.
Why not change the cover to coincide it with each LTS and have the
in-between rel
Aha! Understood!
Regards,
Sayantan Das
--
http://computergyan.wordpress.com
On 31 August 2010 12:47, Benjamin Humphrey wrote:
> Sayantan,
>
> We don't want to use references to the code names anywhere in the manual,
> as they're just development names and the
Sayantan,
We don't want to use references to the code names anywhere in the manual, as
they're just development names and the user isn't meant to see them.
I know Ubuntu versions are often referred to by their development name, and
unfortunately even end users seem to have picked this up too - bu
Can we add a picture of the meerkat on the cover? . It wont be a picture per
say, but more like a watermark. It can be done for every new release
symbolising the release codename.
Just a thought!
Regards,
Sayantan Das
--
http://computergyan.wordpress.com
On 31 A
On Tue, 2010-08-31 at 20:40 +1200, Benjamin Humphrey wrote:
> We need to figure out whether we want to design a new cover page for
> each cycle, or just update the same one each time. My personal opinion
> and original vision was to have a new cover each time, to
> differentiate the separate books,
I completely agree that we need a new cover for a new cycle. Orange is
good as being the prominent colour of this release of UM
Bilal Akhtar.
On Tue, 2010-08-31 at 20:40 +1200, Benjamin Humphrey wrote:
> We need to figure out whether we want to design a new cover page for
> each cycle, or just u
We need to figure out whether we want to design a new cover page for each
cycle, or just update the same one each time. My personal opinion and
original vision was to have a new cover each time, to differentiate the
separate books, keep the style updated as the Ubuntu theme and branding
develops an
12 matches
Mail list logo
