Re: Minutes of the Board meeting of October 29th, 2013

[Andreas Nilsson <lists andreasn se>]

On 11/21/2013 11:58 AM, Dave Neary wrote:
> Hi Allan,
>
> On 11/21/2013 11:04 AM, Allan Day wrote:
> > That page is pretty new. The intention was to consolidate the
> > pre-existing guidelines, but there's a chance that some of the issues
> > you mention are simply bugs that need to be ironed out.
> This raises a very important point.
>
> Mairin worked on logo & brand guidelines back in 2006. That was the work
> (I believe that you based this page off. And all of the links to her
> work are now broken and point at this page. The archive is gone. The
> history is gone.
>
> We are losing collected collective wisdom at al alarming rate in the
> GNOME project as people (like myself) become less active and old wiki
> pages get deleted wholesale as we move to new infrastructure and the
> content gets "refreshed".
>
> I don't think this is a good thing, but if it's a conscious decision
> that's one thing. If it's collateral damage and is happening unawares,
> then it's more serious (and consider this to be calling attention to it).

Mairin's work was excellent. I'm very, very thankful for having the 
vertical logo as a direct outcome of that work. Thank you Mairin!
However, as one of the people making most use of the logo in various 
printed and web materials, I really appreciate the newer, shorter 
guidelines (that built upon the old guidelines, so no history is lost 
per se).
One thing that the new guidelines makes away with is the internal 
spacing of the logo itself. As that is included in the logo svg file 
anyway, I think that's ok to skip if it makes the document easier to 
access. I really never made use of the color variations, but that is 
just me. Others might have different experiences.

I also appreciate having some history in the wiki, but at the same time 
there is a lot of old and outdated stuff in the wiki to the point where 
I have a very hard time finding stuff. I'm sometimes too afraid to 
delete stuff, because someone might find it useful, even though it 
conflicts with other stuff. What is best practice here? How would you do it?

- Andreas