Patrick Horgan wrote:
Stewart, Robert wrote: (...but patrick has done a lot of elision...)
Bjørn Roald wrote:
I dislike the "under construction" variant. If we keep it it should be changed to "under construction for" two-liner, but I think "preliminary proposal for" cover tat use case better.
I agree that "for" is needed with "under construction," but splitting "under construction for" into two lines won't look right any way you try it.
I put up an "under construction for" for your perusal.
It looks as I imagined it would. I don't care for it.
Wouldn't it be fun to replace the graphic at left with some sort of construction equipment? I'd whip it up, but I suspect that changing the graphic rather than overlaying text as we are would legally dilute the logo.
I don't think that's a good idea since none of the others use a graphical indication of the status.
I don't like that. Until something is proposed, it isn't a proposal. How about "developing for" or "creating for?" The present participle implies ongoing work.
I would maintain that it would be a bit premature to put a boost icon on a project before it's a proposal.
That's an interesting point. Still, the problem is that boosters expect a certain form of documentation and those developing a library with the intent to submit it often try to follow boost form well before submission. They can, of course, insert some entirely different logo, but what? Perhaps they should use the "powered by" logo until it has been submitted for review.
o DESIGNED FOR - unclear what this means--designed to work with, or work using?
-1
o PROPOSAL FOR - proposed for is better
+0 based upon the above (the "proposed" change is necessary, however)
o ACCEPTED FOR - after you're accepted you could just use the boost logo.
-1
o SKETCH PROPOSAL FOR - seems unclear to native US English speakers what this means.
-1
o PRELIMINARY PROPOSAL FOR - as far as boost is concerned it's either a proposal at some stage or not and if it is you could use PROPOSED FOR.
-1
o UNDER CONSTRUCTION FOR - same arguments as PRELIMINARY PROPOSAL FOR, seems that you could just use PROPOSED FOR.
-1
I like the idea of keeping both POWERED BY and USING even though they essentially mean the same thing, because the first is more exciting and edgy, which is what some projects would want, but others would prefer to use staid old USING. I definitely prefer POWERED BY myself, but think that there would be wide variance in opinion.
I disagree with giving the choice. It opens questions of which is better.
So, that would leave the USING/POWERED BY pair, the PROPOSED FOR, and the regular boost icon which already exists and isn't part of this discussion. That's my 7 3/4 cents.
I'm leaning toward just POWERED BY and the normal logo. The former can apply to anything using Boost, as well as being developed or proposed for inclusion in Boost. (The latter are powered by Boost because of Boost.Test and configuration, if nothing else.) The normal logo applies to accepted libraries, whether part of the release distribution or not. The POWERED BY variant must obviously be distinct. It must be clear, at a glance, that the logo is for something other than an accepted Boost library. _____ Rob Stewart robert.stewart@sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.