logos in boost image

Hi all, I really wonder who is interested in shipping the images of the boost logo contest (in the more subdir). This increases the size of the boost by about 2 megs and is of no use for most of the boost users! Stefan

Stefan Slapeta wrote:
I really wonder who is interested in shipping the images of the boost logo contest (in the more subdir). This increases the size of the boost by about 2 megs and is of no use for most of the boost users!
And also poses some interesting copyright issues. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

Stefan Slapeta wrote:
Hi all,
I really wonder who is interested in shipping the images of the boost logo contest (in the more subdir). This increases the size of the boost by about 2 megs and is of no use for most of the boost users!
No. The logo contest will not be a part of the distribution. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

John Maddock wrote:
Why didn't you put the images in a separate branch then?
They're not in *any* branch (just on the web site).
I'm afraid they are on the HEAD branch.. http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/ Which is why Stefan asked. Perhaps it was an unintentional commit? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org

Rene Rivera wrote:
John Maddock wrote:
Why didn't you put the images in a separate branch then?
They're not in *any* branch (just on the web site).
I'm afraid they are on the HEAD branch..
http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/
Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch whenever we get to it, so I do not see why there's a big fuss. If it's the size of the CVS update you are concerned with, then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure. Cheers, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

I'm afraid they are on the HEAD branch..
http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/
Oh, shucks.
Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html
It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch whenever we get to it, so I do not see why there's a big fuss. If it's the size of the CVS update you are concerned with, then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure.
I see what you mean, I guess this was a special case when the rules should have been broken :-) Maybe we could move the logos into a cvs branch, and remove them from cvs-HEAD: there's no real reason why folks should download them if they just want a cvs copy (Boost's big enough as it is). John.

John Maddock wrote:
I'm afraid they are on the HEAD branch..
http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/
Oh, shucks.
Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html
It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch whenever we get to it, so I do not see why there's a big fuss. If it's the size of the CVS update you are concerned with, then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure.
I see what you mean, I guess this was a special case when the rules should have been broken :-)
Sorry. I'm not good at breaking the rules.
Maybe we could move the logos into a cvs branch, and remove them from cvs-HEAD: there's no real reason why folks should download them if they just want a cvs copy (Boost's big enough as it is).
Done. It's been removed from the HEAD. I also removed all the accompanying files and stuff. It's been placed in a separate branch. I also made the link to it absolute so the entry in the news section will point to http://www.boost.org/more/logo_contest.htm instead of relative to the html page. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

Joel <joel@boost-consulting.com> writes:
John Maddock wrote:
I'm afraid they are on the HEAD branch..
http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/ Oh, shucks.
Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html
It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch whenever we get to it, so I do not see why there's a big fuss. If it's the size of the CVS update you are concerned with, then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure. I see what you mean, I guess this was a special case when the rules should have been broken :-)
Sorry. I'm not good at breaking the rules.
Just to be clear, the procedure isn't a set of rules, it's just a procedure. That is, it has no legal weight; it's just a prescription that's only optimal for the common case. -- Dave Abrahams Boost Consulting www.boost-consulting.com

David Abrahams wrote:
Joel <joel@boost-consulting.com> writes:
John Maddock wrote:
I'm afraid they are on the HEAD branch..
http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/
Oh, shucks.
Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html
It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch whenever we get to it, so I do not see why there's a big fuss. If it's the size of the CVS update you are concerned with, then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure.
I see what you mean, I guess this was a special case when the rules should have been broken :-)
Sorry. I'm not good at breaking the rules.
Just to be clear, the procedure isn't a set of rules, it's just a procedure. That is, it has no legal weight; it's just a prescription that's only optimal for the common case.
Understood. Next time, I'll think more about the intent and use my better judgement. Sorry. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net

"John Maddock" <john@johnmaddock.co.uk> writes:
I see what you mean, I guess this was a special case when the rules should have been broken :-)
Maybe we could move the logos into a cvs branch, and remove them from cvs-HEAD: there's no real reason why folks should download them if they just want a cvs copy (Boost's big enough as it is).
Why should they be in the CVS at all? -- Dave Abrahams Boost Consulting www.boost-consulting.com

Joel <joel@boost-consulting.com> writes:
Rene Rivera wrote:
John Maddock wrote:
Why didn't you put the images in a separate branch then?
They're not in *any* branch (just on the web site). I'm afraid they are on the HEAD branch.. http://cvs.sourceforge.net/viewcvs.py/boost/boost/more/logo_images/ Which is why Stefan asked. Perhaps it was an unintentional commit?
I was just following procedure here: http://www.boost.org/more/updating_the_website.html
It's not clear what one should do if something needs to be placed in the website but not intended to be released. Ultimately, I can simply remove it from the RC branch
For this release, that's the HEAD.
whenever we get to it, so I do not see why there's a big fuss.
The bigger the CVS repository gets, the worse its performance whether or not you are actually using all the parts.
If it's the size of the CVS update you are concerned with
That too.
Then probably the right thing to do is to clarify the procedure for making updates to the boost website content. Again, I am just following procedure.
Done. But honestly, this seems like a case where a little thought might've served better than blind obedience. There are still cases that the procedure can't adequately cover, and there always will be. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (5)
-
David Abrahams
-
Joel
-
John Maddock
-
Rene Rivera
-
Stefan Slapeta