You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Alexandro Colorado <jz...@oooes.org> on 2013/08/11 07:35:01 UTC
Unnecesary filestructure on images
I think the image structure on the website is a bit messy, there has been
some cleanup done by kschenk but I think there is still a lot of clean up
work to be done.
For example, the new logo, was simply draged and drop to the AOOLogos
folder with a huge name. I understand the name was needed to identify it
between the rest of the competitive logos. But now that is selected, the
current name is unecessary long.
Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log>
At the same time we have old logos which had been untouch. I think the
webdevs have small understanding of a svn is builted so that the files are
updated without having different versions laying arround. Over this
example, ooo-logo.png and
AOO4_website_logo.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log>exist.
All these proliferation of logos, usually will built up to become
incredibly messy to work. I suggest to put the information such as author,
version, status, etc. on the comments of the commit and not on the
filename. Likewise to take the time to look for the source of the image,
since there is an SVG/ folder to link the source of them, and finally if
there are different images (sizes) to have a common convention.
If you want to review the images please go here:
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by "Marcus (OOo)" <ma...@wtnet.de>.
Am 08/11/2013 05:56 PM, schrieb Kay Schenk:
> On Sat, Aug 10, 2013 at 10:35 PM, Alexandro Colorado<jz...@oooes.org> wrote:
>
>> I think the image structure on the website is a bit messy, there has been
>> some cleanup done by kschenk but I think there is still a lot of clean up
>> work to be done.
>>
>> For example, the new logo, was simply draged and drop to the AOOLogos
>> folder with a huge name. I understand the name was needed to identify it
>> between the rest of the competitive logos. But now that is selected, the
>> current name is unecessary long.
>>
>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>
>>
>> At the same time we have old logos which had been untouch. I think the
>> webdevs have small understanding of a svn is builted so that the files are
>> updated without having different versions laying arround. Over this
>> example, ooo-logo.png and
>> AOO4_website_logo.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>> exist.
>>
>> All these proliferation of logos, usually will built up to become
>> incredibly messy to work. I suggest to put the information such as author,
>> version, status, etc. on the comments of the commit and not on the
>> filename. Likewise to take the time to look for the source of the image,
>> since there is an SVG/ folder to link the source of them, and finally if
>> there are different images (sizes) to have a common convention.
>>
>> If you want to review the images please go here:
>>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>
>
> You are correct that more work on moving/organizing the logos needs to be
> done. The new "branding" branch is really for storing sources of them (svg
> files) only. Right now it only contains 4.0 items. I don't see the long
> file names as an issue, but maybe others have an opinion about this.
Instead of search somewhere in SVN log data I prefer a "CHANGES.txt"
that explains, e.g., fileanmes.
Marcus
> The images/AOO_logos area was created/added to when we brought the website
> up under Apache so we could locate the website logo easier, but really,
> this is not needed as a separate area.
>
> Basically, it would be nice if we could get ALL real svg files for the
> logos, old and new, in the new "branding" area (some items with an .svg
> extension are not really svg source), and ALL renderings in another area.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Kay Schenk <ka...@gmail.com>.
On Sat, Aug 10, 2013 at 10:35 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> I think the image structure on the website is a bit messy, there has been
> some cleanup done by kschenk but I think there is still a lot of clean up
> work to be done.
>
> For example, the new logo, was simply draged and drop to the AOOLogos
> folder with a huge name. I understand the name was needed to identify it
> between the rest of the competitive logos. But now that is selected, the
> current name is unecessary long.
>
> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >
>
> At the same time we have old logos which had been untouch. I think the
> webdevs have small understanding of a svn is builted so that the files are
> updated without having different versions laying arround. Over this
> example, ooo-logo.png and
> AOO4_website_logo.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >exist.
>
> All these proliferation of logos, usually will built up to become
> incredibly messy to work. I suggest to put the information such as author,
> version, status, etc. on the comments of the commit and not on the
> filename. Likewise to take the time to look for the source of the image,
> since there is an SVG/ folder to link the source of them, and finally if
> there are different images (sizes) to have a common convention.
>
> If you want to review the images please go here:
>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
You are correct that more work on moving/organizing the logos needs to be
done. The new "branding" branch is really for storing sources of them (svg
files) only. Right now it only contains 4.0 items. I don't see the long
file names as an issue, but maybe others have an opinion about this.
The images/AOO_logos area was created/added to when we brought the website
up under Apache so we could locate the website logo easier, but really,
this is not needed as a separate area.
Basically, it would be nice if we could get ALL real svg files for the
logos, old and new, in the new "branding" area (some items with an .svg
extension are not really svg source), and ALL renderings in another area.
--
-------------------------------------------------------------------------------------------------
MzK
Success is falling nine times and getting up ten."
-- Jon Bon Jovi
Re: Unnecesary filestructure on images
Posted by sebb <se...@gmail.com>.
On 12 August 2013 17:05, janI <ja...@apache.org> wrote:
> On Aug 12, 2013 3:25 PM, "Rob Weir" <ro...@apache.org> wrote:
>>
>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
>> >
>> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
>> >> > I think the image structure on the website is a bit messy, there has
> been
>> >> > some cleanup done by kschenk but I think there is still a lot of
> clean up
>> >> > work to be done.
>> >> >
>> >> > For example, the new logo, was simply draged and drop to the AOOLogos
>> >> > folder with a huge name. I understand the name was needed to
> identify it
>> >> > between the rest of the competitive logos. But now that is selected,
> the
>> >> > current name is unecessary long.
>> >> >
>> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >> >
>> >> >
>> >>
>> >> Right. That work is incomplete. I checked it in originally, after
>> >> the logo vote, so we could start working on the product integration
>> >> immediately. But note that the above logo is not the one we actually
>> >> used in AOO 4.0 !!
>> >>
>> >> The one we actually used is this one:
>> >>
>> >>
>> >>
>> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> >>
>> >> This was Chris R's contest logo with some minor technical changes.
>> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
>> >> I helped check in.
>> >>
>> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
>> >>
>> >
>> > Again I think we do need a convention for a "logo.svg" as opposed to
>> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
>> > replace with the future logos as we update the SVG.
>> >
>>
>> Here's the complication: The old logos are still relevant some some
>> purposes. For example, the PMC receives ongoing requests to approve
>> use of the old OpenOffice.org logo. Why would that happen? Often it
>> is a request by publishers who are making an e-book version of an
>> older print book. If their original request did not include the
>> e-book rights then they come back to us (and owners of every other
>> image they use) to request additional permissions.
>>
>> So it may be possible, going forward, to store logos as SVN revisions
>> under the same name. But we cannot retroactively do this with
>> pre-Apache logos. And even if we could, this is harder for users of
>> the logo to access. It is much easier to have something like
>> logo-330.svg available via HTTP.
>>
>> Of course you can have a hybrid approach:
>>
>> 1) When a new logo is introduced, svn copy the old one into a
>> /old-logos directory with a new descriptive name. This preserves the
>> version history.
>>
>> 2) New logo then is checked in as a new revision of logo-master.svg.
>
> or do as I am used to
>
> new logo is checked in as
> logo-master.png
> and
> logo-4.x.png
>
> this way we have history and actual logo. and most important the links
> never change.
That's OK provided that the logo size and type (svg/png/gif etc.) don't change.
In other words, if it's a drop-in replacement ("binary compatible" in
code terms) then keeping the same name is sensible.
If either changes, this could cause incompatibilities, in which case a
name change may cause fewer issues in the long run.
And it should be more obvious that references have to change (as well
as being obvious which ones have been updated).
> rgds
> jan i
>>
>> Regards,
>>
>> -Rob
>>
>>
>> >
>> >
>> >> or something clean like that. However, I have not had any luck
>> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
>> >> errors. And I have not had any luck getting Kevin to send a version
>> >> that will load.
>> >>
>> >> So we're stuck right now with a logo that does load into Inkscape, but
>> >> is slightly different than the one we used in AOO 4.0.
>> >>
>> >
>> >> > At the same time we have old logos which had been untouch. I think
> the
>> >> > webdevs have small understanding of a svn is builted so that the
> files
>> >> are
>> >> > updated without having different versions laying arround. Over this
>> >> > example, ooo-logo.png and
>> >> > AOO4_website_logo.png<
>> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >> >exist.
>> >> >
>> >> > All these proliferation of logos, usually will built up to become
>> >> > incredibly messy to work. I suggest to put the information such as
>> >> author,
>> >> > version, status, etc. on the comments of the commit and not on the
>> >> > filename. Likewise to take the time to look for the source of the
> image,
>> >> > since there is an SVG/ folder to link the source of them, and
> finally if
>> >> > there are different images (sizes) to have a common convention.
>> >> >
>> >>
>> >> A more logical naming scheme would be good, I agree. But this has
>> >> been waiting for resolution of which SVG we should actually be using.
>> >>
>> >> Regards,
>> >>
>> >> -Rob
>> >>
>> >>
>> >> > If you want to review the images please go here:
>> >> >
>> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >> >
>> >> > --
>> >> > Alexandro Colorado
>> >> > Apache OpenOffice Contributor
>> >> > http://www.openoffice.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Alexandro Colorado
>> > Apache OpenOffice Contributor
>> > http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by janI <ja...@apache.org>.
On Aug 12, 2013 3:25 PM, "Rob Weir" <ro...@apache.org> wrote:
>
> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
wrote:
> >> > I think the image structure on the website is a bit messy, there has
been
> >> > some cleanup done by kschenk but I think there is still a lot of
clean up
> >> > work to be done.
> >> >
> >> > For example, the new logo, was simply draged and drop to the AOOLogos
> >> > folder with a huge name. I understand the name was needed to
identify it
> >> > between the rest of the competitive logos. But now that is selected,
the
> >> > current name is unecessary long.
> >> >
> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> >
> >> >
> >>
> >> Right. That work is incomplete. I checked it in originally, after
> >> the logo vote, so we could start working on the product integration
> >> immediately. But note that the above logo is not the one we actually
> >> used in AOO 4.0 !!
> >>
> >> The one we actually used is this one:
> >>
> >>
> >>
> >>
https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>
> >> This was Chris R's contest logo with some minor technical changes.
> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> >> I helped check in.
> >>
> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> >>
> >
> > Again I think we do need a convention for a "logo.svg" as opposed to
> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
> > replace with the future logos as we update the SVG.
> >
>
> Here's the complication: The old logos are still relevant some some
> purposes. For example, the PMC receives ongoing requests to approve
> use of the old OpenOffice.org logo. Why would that happen? Often it
> is a request by publishers who are making an e-book version of an
> older print book. If their original request did not include the
> e-book rights then they come back to us (and owners of every other
> image they use) to request additional permissions.
>
> So it may be possible, going forward, to store logos as SVN revisions
> under the same name. But we cannot retroactively do this with
> pre-Apache logos. And even if we could, this is harder for users of
> the logo to access. It is much easier to have something like
> logo-330.svg available via HTTP.
>
> Of course you can have a hybrid approach:
>
> 1) When a new logo is introduced, svn copy the old one into a
> /old-logos directory with a new descriptive name. This preserves the
> version history.
>
> 2) New logo then is checked in as a new revision of logo-master.svg.
or do as I am used to
new logo is checked in as
logo-master.png
and
logo-4.x.png
this way we have history and actual logo. and most important the links
never change.
rgds
jan i
>
> Regards,
>
> -Rob
>
>
> >
> >
> >> or something clean like that. However, I have not had any luck
> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> >> errors. And I have not had any luck getting Kevin to send a version
> >> that will load.
> >>
> >> So we're stuck right now with a logo that does load into Inkscape, but
> >> is slightly different than the one we used in AOO 4.0.
> >>
> >
> >> > At the same time we have old logos which had been untouch. I think
the
> >> > webdevs have small understanding of a svn is builted so that the
files
> >> are
> >> > updated without having different versions laying arround. Over this
> >> > example, ooo-logo.png and
> >> > AOO4_website_logo.png<
> >>
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> >exist.
> >> >
> >> > All these proliferation of logos, usually will built up to become
> >> > incredibly messy to work. I suggest to put the information such as
> >> author,
> >> > version, status, etc. on the comments of the commit and not on the
> >> > filename. Likewise to take the time to look for the source of the
image,
> >> > since there is an SVG/ folder to link the source of them, and
finally if
> >> > there are different images (sizes) to have a common convention.
> >> >
> >>
> >> A more logical naming scheme would be good, I agree. But this has
> >> been waiting for resolution of which SVG we should actually be using.
> >>
> >> Regards,
> >>
> >> -Rob
> >>
> >>
> >> > If you want to review the images please go here:
> >> >
> >>
http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> >
> >> > --
> >> > Alexandro Colorado
> >> > Apache OpenOffice Contributor
> >> > http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net> wrote:
> Speaking of a confusing email exchange. This is difficult for busy people
> in the last 24 hours how many messages have been posted? A lot. By how many
> people? Not many and most by one person.
>
> Did anyone create a CWiki page to outline an actual proposal and possible
> variations?
>
> I would like to know what the delta is from what we are doing now to any
> new state in order to see if I agree or have another choice.
>
I agree from what started as a webdev discussion has diverged into a
larger problem with the proliferation of repositories. Not sure if the
proposal should include the marketing-art and branding project. The issue
however are related.
I think this should be organized as:
- filename and file structure cleanup for webdev
- stablish a convention for webdev
- update the marketing-art gallery/wiki
- Organize branding
From my experience, the wiki was increasily used as a place for
storing/organizing content while the most static was on the www site.
However it seems more people are more commit-happy and more interested into
going back to the svn to perform these operations.
>
> Regards,
> Dave
>
> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
>
> > On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
> >> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
> >>
> >>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> >>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
> >>> wrote:
> >>>>
> >>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
> wrote:
> >>>>>
> >>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> >>>>> wrote:
> >>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
> >>> wrote:
> >>>>>>>
> >>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
> >>>>>>>> <jza@oooes.org
> >>>>
> >>>>>> wrote:
> >>>>>>>>> I think the image structure on the website is a bit messy,
> >>>>>>>>> there
> >>>>>>>>> has
> >>>>>> been
> >>>>>>>>> some cleanup done by kschenk but I think there is still a lot
> >>>>>>>>> of
> >>>>>> clean up
> >>>>>>>>> work to be done.
> >>>>>>>>>
> >>>>>>>>> For example, the new logo, was simply draged and drop to the
> >>>>> AOOLogos
> >>>>>>>>> folder with a huge name. I understand the name was needed to
> >>>>> identify
> >>>>>> it
> >>>>>>>>> between the rest of the competitive logos. But now that is
> >>>>>>>>> selected,
> >>>>>> the
> >>>>>>>>> current name is unecessary long.
> >>>>>>>>>
> >>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Right. That work is incomplete. I checked it in originally,
> >>>>>>>> after
> >>>>>>>> the logo vote, so we could start working on the product
> >>>>>>>> integration
> >>>>>>>> immediately. But note that the above logo is not the one we
> >>>>>>>> actually
> >>>>>>>> used in AOO 4.0 !!
> >>>>>>>>
> >>>>>>>> The one we actually used is this one:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>>>>>>>
> >>>>>>>> This was Chris R's contest logo with some minor technical
> >>>>>>>> changes.
> >>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
> >>>>>>>> which
> >>>>>>>> I helped check in.
> >>>>>>>>
> >>>>>>>> My intent was to take that SVG and rename it to
> >>> "master-logo-40.svg"
> >>>>>>>>
> >>>>>>>
> >>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
> >>>>>>> to
> >>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >>>>> incrementally
> >>>>>>> replace with the future logos as we update the SVG.
> >>>>>>>
> >>>>>>
> >>>>>> Here's the complication: The old logos are still relevant some
> >>>>>> some
> >>>>>> purposes. For example, the PMC receives ongoing requests to approve
> >>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
> >>>>>> it
> >>>>>> is a request by publishers who are making an e-book version of an
> >>>>>> older print book. If their original request did not include the
> >>>>>> e-book rights then they come back to us (and owners of every other
> >>>>>> image they use) to request additional permissions.
> >>>>>>
> >>>>>
> >>>>> I think that 'complication' is the lesser of two evils., compared to
> >>>>> having to manage a ever growing ammount of images. And beside that,
> do
> >>>>> you
> >>>>> realize the difference in objectives between ooo-site/images/
> >>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
> >>>>>
> >>>>> I dont see any reason why those issues should impact the web works of
> >>>>> ooo-site/images/. That folder is for website-design related work. It
> >>> has,
> >>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
> >>>>> description of any kind. I think website should be as lean and easy
> to
> >>>>> follow since we expect these conventions be followed by a rotating
> >>>>> community. So again K.I.S.S.
> >>>>>
> >>>>
> >>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
> >>> simply
> >>>> because to make it easier to locate it. The other images files there
> >>> belong
> >>>> to the home page. The svg sub-directory here is really the mis-placed
> >>> one.
> >>>
> >>> Actually I would like to see getting rid of the rasterize images
> >>> instead. Modern browsers already process SVG natively without issues.
> >>>
> >>
> >>
> >> Well, that's not completely true: even if not "modern" any more there
> are
> >> literally millions of people still using internet explorer 8 or even
> older
> >> versions, and SVG support was *partially* implemented only from IE9. IE8
> >> needs a plug-in for SVG rendering.
> >>
> >> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
> >
> > That's why I recomend and reference javascript libraries that take
> > care of legacy browsers additionally there are fallback techniques
> > (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
> > can just test this easily using browsershots or something similar and
> > evaluate.
> >
> >>
> >> Regards
> >> Ricardo
> >>
> >>
> >>
> >>
> >>
> >>> Also there are js libraries that ensure browser compatibility like the
> >>> svgweb.js library:
> >>> http://code.google.com/p/svgweb/
> >>>
> >>>
> >>>>
> >>>>
> >>>>> If those complications arises, send them to marketing or branding
> >>>>> workspaces.
> >>>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> So it may be possible, going forward, to store logos as SVN
> >>>>>> revisions
> >>>>>> under the same name. But we cannot retroactively do this with
> >>>>>> pre-Apache logos. And even if we could, this is harder for users of
> >>>>>> the logo to access. It is much easier to have something like
> >>>>>> logo-330.svg available via HTTP.
> >>>>>>
> >>>>>
> >>>>> svg are just like HTML files, they are markup languages, we dont hold
> >>> the
> >>>>> index.html inmaculated and hold an apache-index.html and
> >>>>> oracle-index.html,
> >>>>> so I dont see why SVG should be any different.
> >>>>
> >>>>
> >>>> I don't agree this assessment. The svg files contain branding, or
> >>>> trademark sources. These are entities which should not be changed --
> >>>> resulting in a trademark violation. If there is something wrong with
> >>>> the
> >>>> SVG files for whatever reason, this needs to undergo a justification
> >>>> discussion.
> >>>>
> >>>> The only porpouse of having
> >>>>> a source file, is for users to be able to modify it on the first
> >>>>> place.
> >>>>> Either by integrating to a bigger SVG design, or resizing it for
> print
> >>>>> work.
> >>>>>
> >>>>
> >>>> This part I do agree with. The svg files can be used to produce
> various
> >>>> sizes of the "trademarked" entities. Changing the source of that
> entity
> >>> is
> >>>> a different matter in my opinion.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Of course you can have a hybrid approach:
> >>>>>>
> >>>>>> 1) When a new logo is introduced, svn copy the old one into a
> >>>>>> /old-logos directory with a new descriptive name. This preserves
> >>>>>> the
> >>>>>> version history.
> >>>>>>
> >>>>>
> >>>>> This is not functional and just start acumulating part of the same
> >>>>> garbage
> >>>>> that svn is supposed to clean up. Again, if this was code, this would
> >>>>> be
> >>>>> totally unacceptable approach. If new logos are introduced then they
> >>>>> should
> >>>>> replace the current logo, and the old will live in anals of the svn
> >>> logs.
> >>>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> 2) New logo then is checked in as a new revision of logo-master.svg.
> >>>>>>
> >>>>>
> >>>>> People are free to disagree with me, but I think this is a messy way
> >>>>> to
> >>>>> work, and for a webdev folder is completely useless, specially when
> >>> there
> >>>>> is a whole different project specialized on archiving, developing,
> and
> >>>>> multiplying artwork inside marketing, and a whole different project
> >>>>> devoted
> >>>>> to specifying the guideliness of the brand (aka logo).
> >>>>>
> >>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> -Rob
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> or something clean like that. However, I have not had any luck
> >>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
> >>> get
> >>>>>>>> errors. And I have not had any luck getting Kevin to send a
> >>> version
> >>>>>>>> that will load.
> >>>>>>>>
> >>>>>>>> So we're stuck right now with a logo that does load into
> >>>>>>>> Inkscape,
> >>>>>>>> but
> >>>>>>>> is slightly different than the one we used in AOO 4.0.
> >>>>>>>>
> >>>>>>>
> >>>>>>>>> At the same time we have old logos which had been untouch. I
> >>> think
> >>>>> the
> >>>>>>>>> webdevs have small understanding of a svn is builted so that
> >>>>>>>>> the
> >>>>> files
> >>>>>>>> are
> >>>>>>>>> updated without having different versions laying arround. Over
> >>>>>>>>> this
> >>>>>>>>> example, ooo-logo.png and
> >>>>>>>>> AOO4_website_logo.png<
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >>>>>>>>> exist.
> >>>>>>>>>
> >>>>>>>>> All these proliferation of logos, usually will built up to
> >>>>>>>>> become
> >>>>>>>>> incredibly messy to work. I suggest to put the information such
> >>> as
> >>>>>>>> author,
> >>>>>>>>> version, status, etc. on the comments of the commit and not on
> >>> the
> >>>>>>>>> filename. Likewise to take the time to look for the source of
> >>> the
> >>>>>> image,
> >>>>>>>>> since there is an SVG/ folder to link the source of them, and
> >>>>> finally
> >>>>>> if
> >>>>>>>>> there are different images (sizes) to have a common convention.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> A more logical naming scheme would be good, I agree. But this
> >>>>>>>> has
> >>>>>>>> been waiting for resolution of which SVG we should actually be
> >>>>>>>> using.
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>>
> >>>>>>>> -Rob
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> If you want to review the images please go here:
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Alexandro Colorado
> >>>>>>>>> Apache OpenOffice Contributor
> >>>>>>>>> http://www.openoffice.org
> >>>>>>>>
> >>>>>>>>
> >>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Alexandro Colorado
> >>>>>>> Apache OpenOffice Contributor
> >>>>>>> http://www.openoffice.org
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Alexandro Colorado
> >>>>> Apache OpenOffice Contributor
> >>>>> http://www.openoffice.org
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>
> -------------------------------------------------------------------------------------------------
> >>>> MzK
> >>>>
> >>>> Success is falling nine times and getting up ten."
> >>>> -- Jon Bon Jovi
> >>>>
> >>>
> >>>
> >>> --
> >>> Alexandro Colorado
> >>> Apache OpenOffice Contributor
> >>> http://www.openoffice.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>
> >>>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/15/13, Rob Weir <ro...@apache.org> wrote:
> On Thu, Aug 15, 2013 at 3:24 PM, Andrea Pescetti <pe...@apache.org>
> wrote:
>> On 14/08/2013 Alexandro Colorado wrote:
>>>
>>> I created this page:
>>>
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
>>
>>
>> Seems reasonable as it is now. But I'm not scared that much about
>> duplication.
>>
>> The "branding" area is meant to contain reference materials: an official
>> vector version of the logo with a couple of pixel-perfect PNG exports
not really, for that reason "trademark" should hold another copy too.
Point is that it wasn't created for those porpouses, and I think the
whole community shun the active repo in art and marketing.
>> (all
>> with clearer names of course). It could also contain a reference square
>> icon
>> (with the orb), and maybe a reference favicon: anything that we use as
>> branding source on official channels.
>>
>> Unapproved variations do not belong to "branding". And probably themed
>> logos
>> do not belong there too. So the official logo would be in branding but
>> also
>> in http://www.openoffice.org/images/ ; and a themed logo would be in
>> http://www.openoffice.org/images/ only.
>>
>
> But where do the source files (SVG's) for the themed logos go?
It should have always gone to marketing/art/ either on the www-site or
on the wiki. www-site is fine to have SVG because it allow us to
modify slightly the artwork for webdev porpouses.
>
> -Rob
>
>
>> Regards,
>> Andrea.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Rob Weir <ro...@apache.org>.
On Thu, Aug 15, 2013 at 3:24 PM, Andrea Pescetti <pe...@apache.org> wrote:
> On 14/08/2013 Alexandro Colorado wrote:
>>
>> I created this page:
>>
>> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
>
>
> Seems reasonable as it is now. But I'm not scared that much about
> duplication.
>
> The "branding" area is meant to contain reference materials: an official
> vector version of the logo with a couple of pixel-perfect PNG exports (all
> with clearer names of course). It could also contain a reference square icon
> (with the orb), and maybe a reference favicon: anything that we use as
> branding source on official channels.
>
> Unapproved variations do not belong to "branding". And probably themed logos
> do not belong there too. So the official logo would be in branding but also
> in http://www.openoffice.org/images/ ; and a themed logo would be in
> http://www.openoffice.org/images/ only.
>
But where do the source files (SVG's) for the themed logos go?
-Rob
> Regards,
> Andrea.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Thu, Aug 15, 2013 at 2:24 PM, Andrea Pescetti <pe...@apache.org>wrote:
> On 14/08/2013 Alexandro Colorado wrote:
>
>> I created this page:
>> https://cwiki.apache.org/**confluence/display/OOOUSERS/**
>> File+handling+proposal+for+**logos+and+graphics<https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics>
>>
>
> Seems reasonable as it is now. But I'm not scared that much about
> duplication.
>
I am not scared of duplication either, as a matter of fact I think
sometimes duplication is necessary. The problem is when the duplication is
unplanned, then it becomes a mess, and that's the problem.
For example, someone decided it was a great idea to put the OOo Cake on the
root folder, as opposed to images. Then someone instead of duplicated it
for the blog, decided to deep link it. So even now if the ooo cake image is
obsolete, we have a legacy dependency, so we cant move it nor delete it.
This pollute the web work being done.
Point in case is that there were a lot of bad choices made by the
webmasters and this clean up round will try to revert those design
decisions.
>
> The "branding" area is meant to contain reference materials: an official
> vector version of the logo with a couple of pixel-perfect PNG exports (all
> with clearer names of course). It could also contain a reference square
> icon (with the orb), and maybe a reference favicon: anything that we use as
> branding source on official channels.
>
> Unapproved variations do not belong to "branding". And probably themed
> logos do not belong there too. So the official logo would be in branding
> but also in http://www.openoffice.org/**images/<http://www.openoffice.org/images/>; and a themed logo would be in
> http://www.openoffice.org/**images/ <http://www.openoffice.org/images/>only.
>
> Regards,
> Andrea.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<de...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Andrea Pescetti <pe...@apache.org>.
On 14/08/2013 Alexandro Colorado wrote:
> I created this page:
> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
Seems reasonable as it is now. But I'm not scared that much about
duplication.
The "branding" area is meant to contain reference materials: an
official vector version of the logo with a couple of pixel-perfect PNG
exports (all with clearer names of course). It could also contain a
reference square icon (with the orb), and maybe a reference favicon:
anything that we use as branding source on official channels.
Unapproved variations do not belong to "branding". And probably themed
logos do not belong there too. So the official logo would be in branding
but also in http://www.openoffice.org/images/ ; and a themed logo would
be in http://www.openoffice.org/images/ only.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Tue, Aug 13, 2013 at 10:34 PM, Dave Fisher <da...@comcast.net> wrote:
>
> On Aug 13, 2013, at 5:57 PM, Alexandro Colorado wrote:
>
> > On 8/13/13, Dave Fisher <da...@comcast.net> wrote:
> >>
> >> On Aug 13, 2013, at 4:07 PM, Alexandro Colorado wrote:
> >>
> >>> On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net>
> >>> wrote:
> >>>
> >>>> Speaking of a confusing email exchange. This is difficult for busy
> >>>> people
> >>>> in the last 24 hours how many messages have been posted? A lot. By how
> >>>> many
> >>>> people? Not many and most by one person.
> >>>>
> >>>> Did anyone create a CWiki page to outline an actual proposal and
> >>>> possible
> >>>> variations?
> >>>>
> >>>
> >>> I created this page:
> >>>
> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
> >>
> >> I edited the root files and made it into a table where the disposition
> of
> >> each file and folder can be developed and approved.
> >
> > ok but I do believe this proposal was for images and logo, and adding
> > all the other directories put some overhead to what the proposal is
> > about. I did include the files to identify possible conventions.
>
> We can separate the two or we can expand this into an overall ooo-site
> cleanup. Agree to the plan and then individuals can divide and conquer.
>
> I think that the tabular format is one qw should consider it will allow
> for a clear description of the plan. Redirection of old names to new could
> be helpful for name changes.
>
Can we sort the table so that al images are on the top, then the html/css
and finally the directories?
>
> Also, decisions made could easily effect various NL sites. We really need
> to be very deliberate here.
>
> Regards,
> Dave
>
>
>
> >
> >>
> >> Please don't overwrite it. Allow others to contribute. I suggest a
> similar
> >> format for other directories.
> >>
> >> Regards,
> >> Dave
> >>
> >>>
> >>>
> >>>
> >>>
> >>>>
> >>>> I would like to know what the delta is from what we are doing now to
> any
> >>>> new state in order to see if I agree or have another choice.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
> >>>>
> >>>>> On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
> >>>>>> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
> >>>>>>
> >>>>>>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> >>>>>>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <
> jza@oooes.org>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado
> >>>>>>>>>> <jz...@oooes.org>
> >>>>>>>>> wrote:
> >>>>>>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
> >>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
> >>>>>>>>>>>> <jza@oooes.org
> >>>>>>>>
> >>>>>>>>>> wrote:
> >>>>>>>>>>>>> I think the image structure on the website is a bit messy,
> >>>>>>>>>>>>> there
> >>>>>>>>>>>>> has
> >>>>>>>>>> been
> >>>>>>>>>>>>> some cleanup done by kschenk but I think there is still a lot
> >>>>>>>>>>>>> of
> >>>>>>>>>> clean up
> >>>>>>>>>>>>> work to be done.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> For example, the new logo, was simply draged and drop to the
> >>>>>>>>> AOOLogos
> >>>>>>>>>>>>> folder with a huge name. I understand the name was needed to
> >>>>>>>>> identify
> >>>>>>>>>> it
> >>>>>>>>>>>>> between the rest of the competitive logos. But now that is
> >>>>>>>>>>>>> selected,
> >>>>>>>>>> the
> >>>>>>>>>>>>> current name is unecessary long.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Right. That work is incomplete. I checked it in originally,
> >>>>>>>>>>>> after
> >>>>>>>>>>>> the logo vote, so we could start working on the product
> >>>>>>>>>>>> integration
> >>>>>>>>>>>> immediately. But note that the above logo is not the one we
> >>>>>>>>>>>> actually
> >>>>>>>>>>>> used in AOO 4.0 !!
> >>>>>>>>>>>>
> >>>>>>>>>>>> The one we actually used is this one:
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>>>>>>>>>>>
> >>>>>>>>>>>> This was Chris R's contest logo with some minor technical
> >>>>>>>>>>>> changes.
> >>>>>>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO
> 4.0,
> >>>>>>>>>>>> which
> >>>>>>>>>>>> I helped check in.
> >>>>>>>>>>>>
> >>>>>>>>>>>> My intent was to take that SVG and rename it to
> >>>>>>> "master-logo-40.svg"
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Again I think we do need a convention for a "logo.svg" as
> opposed
> >>>>>>>>>>> to
> >>>>>>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >>>>>>>>> incrementally
> >>>>>>>>>>> replace with the future logos as we update the SVG.
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Here's the complication: The old logos are still relevant some
> >>>>>>>>>> some
> >>>>>>>>>> purposes. For example, the PMC receives ongoing requests to
> >>>>>>>>>> approve
> >>>>>>>>>> use of the old OpenOffice.org logo. Why would that happen?
> Often
> >>>>>>>>>> it
> >>>>>>>>>> is a request by publishers who are making an e-book version of
> an
> >>>>>>>>>> older print book. If their original request did not include the
> >>>>>>>>>> e-book rights then they come back to us (and owners of every
> other
> >>>>>>>>>> image they use) to request additional permissions.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> I think that 'complication' is the lesser of two evils., compared
> >>>>>>>>> to
> >>>>>>>>> having to manage a ever growing ammount of images. And beside
> that,
> >>>> do
> >>>>>>>>> you
> >>>>>>>>> realize the difference in objectives between ooo-site/images/
> >>>>>>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
> >>>>>>>>>
> >>>>>>>>> I dont see any reason why those issues should impact the web
> works
> >>>>>>>>> of
> >>>>>>>>> ooo-site/images/. That folder is for website-design related work.
> >>>>>>>>> It
> >>>>>>> has,
> >>>>>>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
> >>>>>>>>> description of any kind. I think website should be as lean and
> easy
> >>>> to
> >>>>>>>>> follow since we expect these conventions be followed by a
> rotating
> >>>>>>>>> community. So again K.I.S.S.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> No, it shouldn't. The ooo-site/images areas got the logo added to
> it
> >>>>>>> simply
> >>>>>>>> because to make it easier to locate it. The other images files
> there
> >>>>>>> belong
> >>>>>>>> to the home page. The svg sub-directory here is really the
> >>>>>>>> mis-placed
> >>>>>>> one.
> >>>>>>>
> >>>>>>> Actually I would like to see getting rid of the rasterize images
> >>>>>>> instead. Modern browsers already process SVG natively without
> issues.
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Well, that's not completely true: even if not "modern" any more
> there
> >>>> are
> >>>>>> literally millions of people still using internet explorer 8 or even
> >>>> older
> >>>>>> versions, and SVG support was *partially* implemented only from IE9.
> >>>>>> IE8
> >>>>>> needs a plug-in for SVG rendering.
> >>>>>>
> >>>>>> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
> >>>>>
> >>>>> That's why I recomend and reference javascript libraries that take
> >>>>> care of legacy browsers additionally there are fallback techniques
> >>>>> (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again,
> you
> >>>>> can just test this easily using browsershots or something similar and
> >>>>> evaluate.
> >>>>>
> >>>>>>
> >>>>>> Regards
> >>>>>> Ricardo
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> Also there are js libraries that ensure browser compatibility like
> >>>>>>> the
> >>>>>>> svgweb.js library:
> >>>>>>> http://code.google.com/p/svgweb/
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> If those complications arises, send them to marketing or branding
> >>>>>>>>> workspaces.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> So it may be possible, going forward, to store logos as SVN
> >>>>>>>>>> revisions
> >>>>>>>>>> under the same name. But we cannot retroactively do this with
> >>>>>>>>>> pre-Apache logos. And even if we could, this is harder for
> users
> >>>>>>>>>> of
> >>>>>>>>>> the logo to access. It is much easier to have something like
> >>>>>>>>>> logo-330.svg available via HTTP.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> svg are just like HTML files, they are markup languages, we dont
> >>>>>>>>> hold
> >>>>>>> the
> >>>>>>>>> index.html inmaculated and hold an apache-index.html and
> >>>>>>>>> oracle-index.html,
> >>>>>>>>> so I dont see why SVG should be any different.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I don't agree this assessment. The svg files contain branding, or
> >>>>>>>> trademark sources. These are entities which should not be changed
> >>>>>>>> --
> >>>>>>>> resulting in a trademark violation. If there is something wrong
> with
> >>>>>>>> the
> >>>>>>>> SVG files for whatever reason, this needs to undergo a
> justification
> >>>>>>>> discussion.
> >>>>>>>>
> >>>>>>>> The only porpouse of having
> >>>>>>>>> a source file, is for users to be able to modify it on the first
> >>>>>>>>> place.
> >>>>>>>>> Either by integrating to a bigger SVG design, or resizing it for
> >>>> print
> >>>>>>>>> work.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> This part I do agree with. The svg files can be used to produce
> >>>> various
> >>>>>>>> sizes of the "trademarked" entities. Changing the source of that
> >>>> entity
> >>>>>>> is
> >>>>>>>> a different matter in my opinion.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Of course you can have a hybrid approach:
> >>>>>>>>>>
> >>>>>>>>>> 1) When a new logo is introduced, svn copy the old one into a
> >>>>>>>>>> /old-logos directory with a new descriptive name. This
> preserves
> >>>>>>>>>> the
> >>>>>>>>>> version history.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> This is not functional and just start acumulating part of the
> same
> >>>>>>>>> garbage
> >>>>>>>>> that svn is supposed to clean up. Again, if this was code, this
> >>>>>>>>> would
> >>>>>>>>> be
> >>>>>>>>> totally unacceptable approach. If new logos are introduced then
> >>>>>>>>> they
> >>>>>>>>> should
> >>>>>>>>> replace the current logo, and the old will live in anals of the
> svn
> >>>>>>> logs.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2) New logo then is checked in as a new revision of
> >>>>>>>>>> logo-master.svg.
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> People are free to disagree with me, but I think this is a messy
> >>>>>>>>> way
> >>>>>>>>> to
> >>>>>>>>> work, and for a webdev folder is completely useless, specially
> when
> >>>>>>> there
> >>>>>>>>> is a whole different project specialized on archiving,
> developing,
> >>>> and
> >>>>>>>>> multiplying artwork inside marketing, and a whole different
> project
> >>>>>>>>> devoted
> >>>>>>>>> to specifying the guideliness of the brand (aka logo).
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>> Regards,
> >>>>>>>>>>
> >>>>>>>>>> -Rob
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>> or something clean like that. However, I have not had any
> luck
> >>>>>>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator.
> I
> >>>>>>> get
> >>>>>>>>>>>> errors. And I have not had any luck getting Kevin to send a
> >>>>>>> version
> >>>>>>>>>>>> that will load.
> >>>>>>>>>>>>
> >>>>>>>>>>>> So we're stuck right now with a logo that does load into
> >>>>>>>>>>>> Inkscape,
> >>>>>>>>>>>> but
> >>>>>>>>>>>> is slightly different than the one we used in AOO 4.0.
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>>> At the same time we have old logos which had been untouch. I
> >>>>>>> think
> >>>>>>>>> the
> >>>>>>>>>>>>> webdevs have small understanding of a svn is builted so that
> >>>>>>>>>>>>> the
> >>>>>>>>> files
> >>>>>>>>>>>> are
> >>>>>>>>>>>>> updated without having different versions laying arround.
> Over
> >>>>>>>>>>>>> this
> >>>>>>>>>>>>> example, ooo-logo.png and
> >>>>>>>>>>>>> AOO4_website_logo.png<
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >>>>>>>>>>>>> exist.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> All these proliferation of logos, usually will built up to
> >>>>>>>>>>>>> become
> >>>>>>>>>>>>> incredibly messy to work. I suggest to put the information
> such
> >>>>>>> as
> >>>>>>>>>>>> author,
> >>>>>>>>>>>>> version, status, etc. on the comments of the commit and not
> on
> >>>>>>> the
> >>>>>>>>>>>>> filename. Likewise to take the time to look for the source
> of
> >>>>>>> the
> >>>>>>>>>> image,
> >>>>>>>>>>>>> since there is an SVG/ folder to link the source of them, and
> >>>>>>>>> finally
> >>>>>>>>>> if
> >>>>>>>>>>>>> there are different images (sizes) to have a common
> convention.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> A more logical naming scheme would be good, I agree. But this
> >>>>>>>>>>>> has
> >>>>>>>>>>>> been waiting for resolution of which SVG we should actually be
> >>>>>>>>>>>> using.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Regards,
> >>>>>>>>>>>>
> >>>>>>>>>>>> -Rob
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>>> If you want to review the images please go here:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> --
> >>>>>>>>>>>>> Alexandro Colorado
> >>>>>>>>>>>>> Apache OpenOffice Contributor
> >>>>>>>>>>>>> http://www.openoffice.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>>>>>>>> For additional commands, e-mail:
> dev-help@openoffice.apache.org
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> --
> >>>>>>>>>>> Alexandro Colorado
> >>>>>>>>>>> Apache OpenOffice Contributor
> >>>>>>>>>>> http://www.openoffice.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>> ---------------------------------------------------------------------
> >>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Alexandro Colorado
> >>>>>>>>> Apache OpenOffice Contributor
> >>>>>>>>> http://www.openoffice.org
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>>
> >>>>>>>
> >>>>
> -------------------------------------------------------------------------------------------------
> >>>>>>>> MzK
> >>>>>>>>
> >>>>>>>> Success is falling nine times and getting up ten."
> >>>>>>>> -- Jon Bon Jovi
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Alexandro Colorado
> >>>>>>> Apache OpenOffice Contributor
> >>>>>>> http://www.openoffice.org
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Alexandro Colorado
> >>>>> Apache OpenOffice Contributor
> >>>>> http://www.openoffice.org
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>
> >>>>
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Alexandro Colorado
> >>> Apache OpenOffice Contributor
> >>> http://www.openoffice.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <da...@comcast.net>.
On Aug 13, 2013, at 5:57 PM, Alexandro Colorado wrote:
> On 8/13/13, Dave Fisher <da...@comcast.net> wrote:
>>
>> On Aug 13, 2013, at 4:07 PM, Alexandro Colorado wrote:
>>
>>> On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net>
>>> wrote:
>>>
>>>> Speaking of a confusing email exchange. This is difficult for busy
>>>> people
>>>> in the last 24 hours how many messages have been posted? A lot. By how
>>>> many
>>>> people? Not many and most by one person.
>>>>
>>>> Did anyone create a CWiki page to outline an actual proposal and
>>>> possible
>>>> variations?
>>>>
>>>
>>> I created this page:
>>> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
>>
>> I edited the root files and made it into a table where the disposition of
>> each file and folder can be developed and approved.
>
> ok but I do believe this proposal was for images and logo, and adding
> all the other directories put some overhead to what the proposal is
> about. I did include the files to identify possible conventions.
We can separate the two or we can expand this into an overall ooo-site cleanup. Agree to the plan and then individuals can divide and conquer.
I think that the tabular format is one qw should consider it will allow for a clear description of the plan. Redirection of old names to new could be helpful for name changes.
Also, decisions made could easily effect various NL sites. We really need to be very deliberate here.
Regards,
Dave
>
>>
>> Please don't overwrite it. Allow others to contribute. I suggest a similar
>> format for other directories.
>>
>> Regards,
>> Dave
>>
>>>
>>>
>>>
>>>
>>>>
>>>> I would like to know what the delta is from what we are doing now to any
>>>> new state in order to see if I agree or have another choice.
>>>>
>>>> Regards,
>>>> Dave
>>>>
>>>> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
>>>>
>>>>> On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
>>>>>> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
>>>>>>
>>>>>>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>>>>>>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado
>>>>>>>>>> <jz...@oooes.org>
>>>>>>>>> wrote:
>>>>>>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>>>>>>>>>>>> <jza@oooes.org
>>>>>>>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>> I think the image structure on the website is a bit messy,
>>>>>>>>>>>>> there
>>>>>>>>>>>>> has
>>>>>>>>>> been
>>>>>>>>>>>>> some cleanup done by kschenk but I think there is still a lot
>>>>>>>>>>>>> of
>>>>>>>>>> clean up
>>>>>>>>>>>>> work to be done.
>>>>>>>>>>>>>
>>>>>>>>>>>>> For example, the new logo, was simply draged and drop to the
>>>>>>>>> AOOLogos
>>>>>>>>>>>>> folder with a huge name. I understand the name was needed to
>>>>>>>>> identify
>>>>>>>>>> it
>>>>>>>>>>>>> between the rest of the competitive logos. But now that is
>>>>>>>>>>>>> selected,
>>>>>>>>>> the
>>>>>>>>>>>>> current name is unecessary long.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Right. That work is incomplete. I checked it in originally,
>>>>>>>>>>>> after
>>>>>>>>>>>> the logo vote, so we could start working on the product
>>>>>>>>>>>> integration
>>>>>>>>>>>> immediately. But note that the above logo is not the one we
>>>>>>>>>>>> actually
>>>>>>>>>>>> used in AOO 4.0 !!
>>>>>>>>>>>>
>>>>>>>>>>>> The one we actually used is this one:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>>>>>>>>>>>>
>>>>>>>>>>>> This was Chris R's contest logo with some minor technical
>>>>>>>>>>>> changes.
>>>>>>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>>>>>>>>>>>> which
>>>>>>>>>>>> I helped check in.
>>>>>>>>>>>>
>>>>>>>>>>>> My intent was to take that SVG and rename it to
>>>>>>> "master-logo-40.svg"
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
>>>>>>>>>>> to
>>>>>>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>>>>>>>>> incrementally
>>>>>>>>>>> replace with the future logos as we update the SVG.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Here's the complication: The old logos are still relevant some
>>>>>>>>>> some
>>>>>>>>>> purposes. For example, the PMC receives ongoing requests to
>>>>>>>>>> approve
>>>>>>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
>>>>>>>>>> it
>>>>>>>>>> is a request by publishers who are making an e-book version of an
>>>>>>>>>> older print book. If their original request did not include the
>>>>>>>>>> e-book rights then they come back to us (and owners of every other
>>>>>>>>>> image they use) to request additional permissions.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> I think that 'complication' is the lesser of two evils., compared
>>>>>>>>> to
>>>>>>>>> having to manage a ever growing ammount of images. And beside that,
>>>> do
>>>>>>>>> you
>>>>>>>>> realize the difference in objectives between ooo-site/images/
>>>>>>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>>>>>>>>
>>>>>>>>> I dont see any reason why those issues should impact the web works
>>>>>>>>> of
>>>>>>>>> ooo-site/images/. That folder is for website-design related work.
>>>>>>>>> It
>>>>>>> has,
>>>>>>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
>>>>>>>>> description of any kind. I think website should be as lean and easy
>>>> to
>>>>>>>>> follow since we expect these conventions be followed by a rotating
>>>>>>>>> community. So again K.I.S.S.
>>>>>>>>>
>>>>>>>>
>>>>>>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
>>>>>>> simply
>>>>>>>> because to make it easier to locate it. The other images files there
>>>>>>> belong
>>>>>>>> to the home page. The svg sub-directory here is really the
>>>>>>>> mis-placed
>>>>>>> one.
>>>>>>>
>>>>>>> Actually I would like to see getting rid of the rasterize images
>>>>>>> instead. Modern browsers already process SVG natively without issues.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> Well, that's not completely true: even if not "modern" any more there
>>>> are
>>>>>> literally millions of people still using internet explorer 8 or even
>>>> older
>>>>>> versions, and SVG support was *partially* implemented only from IE9.
>>>>>> IE8
>>>>>> needs a plug-in for SVG rendering.
>>>>>>
>>>>>> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
>>>>>
>>>>> That's why I recomend and reference javascript libraries that take
>>>>> care of legacy browsers additionally there are fallback techniques
>>>>> (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
>>>>> can just test this easily using browsershots or something similar and
>>>>> evaluate.
>>>>>
>>>>>>
>>>>>> Regards
>>>>>> Ricardo
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Also there are js libraries that ensure browser compatibility like
>>>>>>> the
>>>>>>> svgweb.js library:
>>>>>>> http://code.google.com/p/svgweb/
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> If those complications arises, send them to marketing or branding
>>>>>>>>> workspaces.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> So it may be possible, going forward, to store logos as SVN
>>>>>>>>>> revisions
>>>>>>>>>> under the same name. But we cannot retroactively do this with
>>>>>>>>>> pre-Apache logos. And even if we could, this is harder for users
>>>>>>>>>> of
>>>>>>>>>> the logo to access. It is much easier to have something like
>>>>>>>>>> logo-330.svg available via HTTP.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> svg are just like HTML files, they are markup languages, we dont
>>>>>>>>> hold
>>>>>>> the
>>>>>>>>> index.html inmaculated and hold an apache-index.html and
>>>>>>>>> oracle-index.html,
>>>>>>>>> so I dont see why SVG should be any different.
>>>>>>>>
>>>>>>>>
>>>>>>>> I don't agree this assessment. The svg files contain branding, or
>>>>>>>> trademark sources. These are entities which should not be changed
>>>>>>>> --
>>>>>>>> resulting in a trademark violation. If there is something wrong with
>>>>>>>> the
>>>>>>>> SVG files for whatever reason, this needs to undergo a justification
>>>>>>>> discussion.
>>>>>>>>
>>>>>>>> The only porpouse of having
>>>>>>>>> a source file, is for users to be able to modify it on the first
>>>>>>>>> place.
>>>>>>>>> Either by integrating to a bigger SVG design, or resizing it for
>>>> print
>>>>>>>>> work.
>>>>>>>>>
>>>>>>>>
>>>>>>>> This part I do agree with. The svg files can be used to produce
>>>> various
>>>>>>>> sizes of the "trademarked" entities. Changing the source of that
>>>> entity
>>>>>>> is
>>>>>>>> a different matter in my opinion.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Of course you can have a hybrid approach:
>>>>>>>>>>
>>>>>>>>>> 1) When a new logo is introduced, svn copy the old one into a
>>>>>>>>>> /old-logos directory with a new descriptive name. This preserves
>>>>>>>>>> the
>>>>>>>>>> version history.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> This is not functional and just start acumulating part of the same
>>>>>>>>> garbage
>>>>>>>>> that svn is supposed to clean up. Again, if this was code, this
>>>>>>>>> would
>>>>>>>>> be
>>>>>>>>> totally unacceptable approach. If new logos are introduced then
>>>>>>>>> they
>>>>>>>>> should
>>>>>>>>> replace the current logo, and the old will live in anals of the svn
>>>>>>> logs.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2) New logo then is checked in as a new revision of
>>>>>>>>>> logo-master.svg.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> People are free to disagree with me, but I think this is a messy
>>>>>>>>> way
>>>>>>>>> to
>>>>>>>>> work, and for a webdev folder is completely useless, specially when
>>>>>>> there
>>>>>>>>> is a whole different project specialized on archiving, developing,
>>>> and
>>>>>>>>> multiplying artwork inside marketing, and a whole different project
>>>>>>>>> devoted
>>>>>>>>> to specifying the guideliness of the brand (aka logo).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> -Rob
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> or something clean like that. However, I have not had any luck
>>>>>>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
>>>>>>> get
>>>>>>>>>>>> errors. And I have not had any luck getting Kevin to send a
>>>>>>> version
>>>>>>>>>>>> that will load.
>>>>>>>>>>>>
>>>>>>>>>>>> So we're stuck right now with a logo that does load into
>>>>>>>>>>>> Inkscape,
>>>>>>>>>>>> but
>>>>>>>>>>>> is slightly different than the one we used in AOO 4.0.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>> At the same time we have old logos which had been untouch. I
>>>>>>> think
>>>>>>>>> the
>>>>>>>>>>>>> webdevs have small understanding of a svn is builted so that
>>>>>>>>>>>>> the
>>>>>>>>> files
>>>>>>>>>>>> are
>>>>>>>>>>>>> updated without having different versions laying arround. Over
>>>>>>>>>>>>> this
>>>>>>>>>>>>> example, ooo-logo.png and
>>>>>>>>>>>>> AOO4_website_logo.png<
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>>>>>>>>>>>> exist.
>>>>>>>>>>>>>
>>>>>>>>>>>>> All these proliferation of logos, usually will built up to
>>>>>>>>>>>>> become
>>>>>>>>>>>>> incredibly messy to work. I suggest to put the information such
>>>>>>> as
>>>>>>>>>>>> author,
>>>>>>>>>>>>> version, status, etc. on the comments of the commit and not on
>>>>>>> the
>>>>>>>>>>>>> filename. Likewise to take the time to look for the source of
>>>>>>> the
>>>>>>>>>> image,
>>>>>>>>>>>>> since there is an SVG/ folder to link the source of them, and
>>>>>>>>> finally
>>>>>>>>>> if
>>>>>>>>>>>>> there are different images (sizes) to have a common convention.
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> A more logical naming scheme would be good, I agree. But this
>>>>>>>>>>>> has
>>>>>>>>>>>> been waiting for resolution of which SVG we should actually be
>>>>>>>>>>>> using.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> -Rob
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> If you want to review the images please go here:
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Alexandro Colorado
>>>>>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>>>>>> http://www.openoffice.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Alexandro Colorado
>>>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>>>> http://www.openoffice.org
>>>>>>>>>>
>>>>>>>>>>
>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Alexandro Colorado
>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>> http://www.openoffice.org
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>
>>>> -------------------------------------------------------------------------------------------------
>>>>>>>> MzK
>>>>>>>>
>>>>>>>> Success is falling nine times and getting up ten."
>>>>>>>> -- Jon Bon Jovi
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Alexandro Colorado
>>>>>>> Apache OpenOffice Contributor
>>>>>>> http://www.openoffice.org
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Alexandro Colorado
>>>>> Apache OpenOffice Contributor
>>>>> http://www.openoffice.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Alexandro Colorado
>>> Apache OpenOffice Contributor
>>> http://www.openoffice.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Dave Fisher <da...@comcast.net> wrote:
>
> On Aug 13, 2013, at 4:07 PM, Alexandro Colorado wrote:
>
>> On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net>
>> wrote:
>>
>>> Speaking of a confusing email exchange. This is difficult for busy
>>> people
>>> in the last 24 hours how many messages have been posted? A lot. By how
>>> many
>>> people? Not many and most by one person.
>>>
>>> Did anyone create a CWiki page to outline an actual proposal and
>>> possible
>>> variations?
>>>
>>
>> I created this page:
>> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
>
> I edited the root files and made it into a table where the disposition of
> each file and folder can be developed and approved.
ok but I do believe this proposal was for images and logo, and adding
all the other directories put some overhead to what the proposal is
about. I did include the files to identify possible conventions.
>
> Please don't overwrite it. Allow others to contribute. I suggest a similar
> format for other directories.
>
> Regards,
> Dave
>
>>
>>
>>
>>
>>>
>>> I would like to know what the delta is from what we are doing now to any
>>> new state in order to see if I agree or have another choice.
>>>
>>> Regards,
>>> Dave
>>>
>>> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
>>>
>>>> On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
>>>>> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
>>>>>
>>>>>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>>>>>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>>>>>> wrote:
>>>>>>>
>>>>>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
>>> wrote:
>>>>>>>>
>>>>>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado
>>>>>>>>> <jz...@oooes.org>
>>>>>>>> wrote:
>>>>>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>>>>>>>>>>> <jza@oooes.org
>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>>>>> I think the image structure on the website is a bit messy,
>>>>>>>>>>>> there
>>>>>>>>>>>> has
>>>>>>>>> been
>>>>>>>>>>>> some cleanup done by kschenk but I think there is still a lot
>>>>>>>>>>>> of
>>>>>>>>> clean up
>>>>>>>>>>>> work to be done.
>>>>>>>>>>>>
>>>>>>>>>>>> For example, the new logo, was simply draged and drop to the
>>>>>>>> AOOLogos
>>>>>>>>>>>> folder with a huge name. I understand the name was needed to
>>>>>>>> identify
>>>>>>>>> it
>>>>>>>>>>>> between the rest of the competitive logos. But now that is
>>>>>>>>>>>> selected,
>>>>>>>>> the
>>>>>>>>>>>> current name is unecessary long.
>>>>>>>>>>>>
>>>>>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Right. That work is incomplete. I checked it in originally,
>>>>>>>>>>> after
>>>>>>>>>>> the logo vote, so we could start working on the product
>>>>>>>>>>> integration
>>>>>>>>>>> immediately. But note that the above logo is not the one we
>>>>>>>>>>> actually
>>>>>>>>>>> used in AOO 4.0 !!
>>>>>>>>>>>
>>>>>>>>>>> The one we actually used is this one:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>>>>>>>>>>>
>>>>>>>>>>> This was Chris R's contest logo with some minor technical
>>>>>>>>>>> changes.
>>>>>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>>>>>>>>>>> which
>>>>>>>>>>> I helped check in.
>>>>>>>>>>>
>>>>>>>>>>> My intent was to take that SVG and rename it to
>>>>>> "master-logo-40.svg"
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
>>>>>>>>>> to
>>>>>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>>>>>>>> incrementally
>>>>>>>>>> replace with the future logos as we update the SVG.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Here's the complication: The old logos are still relevant some
>>>>>>>>> some
>>>>>>>>> purposes. For example, the PMC receives ongoing requests to
>>>>>>>>> approve
>>>>>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
>>>>>>>>> it
>>>>>>>>> is a request by publishers who are making an e-book version of an
>>>>>>>>> older print book. If their original request did not include the
>>>>>>>>> e-book rights then they come back to us (and owners of every other
>>>>>>>>> image they use) to request additional permissions.
>>>>>>>>>
>>>>>>>>
>>>>>>>> I think that 'complication' is the lesser of two evils., compared
>>>>>>>> to
>>>>>>>> having to manage a ever growing ammount of images. And beside that,
>>> do
>>>>>>>> you
>>>>>>>> realize the difference in objectives between ooo-site/images/
>>>>>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>>>>>>>
>>>>>>>> I dont see any reason why those issues should impact the web works
>>>>>>>> of
>>>>>>>> ooo-site/images/. That folder is for website-design related work.
>>>>>>>> It
>>>>>> has,
>>>>>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
>>>>>>>> description of any kind. I think website should be as lean and easy
>>> to
>>>>>>>> follow since we expect these conventions be followed by a rotating
>>>>>>>> community. So again K.I.S.S.
>>>>>>>>
>>>>>>>
>>>>>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
>>>>>> simply
>>>>>>> because to make it easier to locate it. The other images files there
>>>>>> belong
>>>>>>> to the home page. The svg sub-directory here is really the
>>>>>>> mis-placed
>>>>>> one.
>>>>>>
>>>>>> Actually I would like to see getting rid of the rasterize images
>>>>>> instead. Modern browsers already process SVG natively without issues.
>>>>>>
>>>>>
>>>>>
>>>>> Well, that's not completely true: even if not "modern" any more there
>>> are
>>>>> literally millions of people still using internet explorer 8 or even
>>> older
>>>>> versions, and SVG support was *partially* implemented only from IE9.
>>>>> IE8
>>>>> needs a plug-in for SVG rendering.
>>>>>
>>>>> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
>>>>
>>>> That's why I recomend and reference javascript libraries that take
>>>> care of legacy browsers additionally there are fallback techniques
>>>> (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
>>>> can just test this easily using browsershots or something similar and
>>>> evaluate.
>>>>
>>>>>
>>>>> Regards
>>>>> Ricardo
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Also there are js libraries that ensure browser compatibility like
>>>>>> the
>>>>>> svgweb.js library:
>>>>>> http://code.google.com/p/svgweb/
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> If those complications arises, send them to marketing or branding
>>>>>>>> workspaces.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> So it may be possible, going forward, to store logos as SVN
>>>>>>>>> revisions
>>>>>>>>> under the same name. But we cannot retroactively do this with
>>>>>>>>> pre-Apache logos. And even if we could, this is harder for users
>>>>>>>>> of
>>>>>>>>> the logo to access. It is much easier to have something like
>>>>>>>>> logo-330.svg available via HTTP.
>>>>>>>>>
>>>>>>>>
>>>>>>>> svg are just like HTML files, they are markup languages, we dont
>>>>>>>> hold
>>>>>> the
>>>>>>>> index.html inmaculated and hold an apache-index.html and
>>>>>>>> oracle-index.html,
>>>>>>>> so I dont see why SVG should be any different.
>>>>>>>
>>>>>>>
>>>>>>> I don't agree this assessment. The svg files contain branding, or
>>>>>>> trademark sources. These are entities which should not be changed
>>>>>>> --
>>>>>>> resulting in a trademark violation. If there is something wrong with
>>>>>>> the
>>>>>>> SVG files for whatever reason, this needs to undergo a justification
>>>>>>> discussion.
>>>>>>>
>>>>>>> The only porpouse of having
>>>>>>>> a source file, is for users to be able to modify it on the first
>>>>>>>> place.
>>>>>>>> Either by integrating to a bigger SVG design, or resizing it for
>>> print
>>>>>>>> work.
>>>>>>>>
>>>>>>>
>>>>>>> This part I do agree with. The svg files can be used to produce
>>> various
>>>>>>> sizes of the "trademarked" entities. Changing the source of that
>>> entity
>>>>>> is
>>>>>>> a different matter in my opinion.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Of course you can have a hybrid approach:
>>>>>>>>>
>>>>>>>>> 1) When a new logo is introduced, svn copy the old one into a
>>>>>>>>> /old-logos directory with a new descriptive name. This preserves
>>>>>>>>> the
>>>>>>>>> version history.
>>>>>>>>>
>>>>>>>>
>>>>>>>> This is not functional and just start acumulating part of the same
>>>>>>>> garbage
>>>>>>>> that svn is supposed to clean up. Again, if this was code, this
>>>>>>>> would
>>>>>>>> be
>>>>>>>> totally unacceptable approach. If new logos are introduced then
>>>>>>>> they
>>>>>>>> should
>>>>>>>> replace the current logo, and the old will live in anals of the svn
>>>>>> logs.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2) New logo then is checked in as a new revision of
>>>>>>>>> logo-master.svg.
>>>>>>>>>
>>>>>>>>
>>>>>>>> People are free to disagree with me, but I think this is a messy
>>>>>>>> way
>>>>>>>> to
>>>>>>>> work, and for a webdev folder is completely useless, specially when
>>>>>> there
>>>>>>>> is a whole different project specialized on archiving, developing,
>>> and
>>>>>>>> multiplying artwork inside marketing, and a whole different project
>>>>>>>> devoted
>>>>>>>> to specifying the guideliness of the brand (aka logo).
>>>>>>>>
>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> -Rob
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> or something clean like that. However, I have not had any luck
>>>>>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
>>>>>> get
>>>>>>>>>>> errors. And I have not had any luck getting Kevin to send a
>>>>>> version
>>>>>>>>>>> that will load.
>>>>>>>>>>>
>>>>>>>>>>> So we're stuck right now with a logo that does load into
>>>>>>>>>>> Inkscape,
>>>>>>>>>>> but
>>>>>>>>>>> is slightly different than the one we used in AOO 4.0.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>> At the same time we have old logos which had been untouch. I
>>>>>> think
>>>>>>>> the
>>>>>>>>>>>> webdevs have small understanding of a svn is builted so that
>>>>>>>>>>>> the
>>>>>>>> files
>>>>>>>>>>> are
>>>>>>>>>>>> updated without having different versions laying arround. Over
>>>>>>>>>>>> this
>>>>>>>>>>>> example, ooo-logo.png and
>>>>>>>>>>>> AOO4_website_logo.png<
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>>>>>>>>>>> exist.
>>>>>>>>>>>>
>>>>>>>>>>>> All these proliferation of logos, usually will built up to
>>>>>>>>>>>> become
>>>>>>>>>>>> incredibly messy to work. I suggest to put the information such
>>>>>> as
>>>>>>>>>>> author,
>>>>>>>>>>>> version, status, etc. on the comments of the commit and not on
>>>>>> the
>>>>>>>>>>>> filename. Likewise to take the time to look for the source of
>>>>>> the
>>>>>>>>> image,
>>>>>>>>>>>> since there is an SVG/ folder to link the source of them, and
>>>>>>>> finally
>>>>>>>>> if
>>>>>>>>>>>> there are different images (sizes) to have a common convention.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> A more logical naming scheme would be good, I agree. But this
>>>>>>>>>>> has
>>>>>>>>>>> been waiting for resolution of which SVG we should actually be
>>>>>>>>>>> using.
>>>>>>>>>>>
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> -Rob
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>> If you want to review the images please go here:
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Alexandro Colorado
>>>>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>>>>> http://www.openoffice.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Alexandro Colorado
>>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>>> http://www.openoffice.org
>>>>>>>>>
>>>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Alexandro Colorado
>>>>>>>> Apache OpenOffice Contributor
>>>>>>>> http://www.openoffice.org
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>
>>> -------------------------------------------------------------------------------------------------
>>>>>>> MzK
>>>>>>>
>>>>>>> Success is falling nine times and getting up ten."
>>>>>>> -- Jon Bon Jovi
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Alexandro Colorado
>>>>>> Apache OpenOffice Contributor
>>>>>> http://www.openoffice.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Alexandro Colorado
>>>> Apache OpenOffice Contributor
>>>> http://www.openoffice.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <da...@comcast.net>.
On Aug 13, 2013, at 4:07 PM, Alexandro Colorado wrote:
> On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net> wrote:
>
>> Speaking of a confusing email exchange. This is difficult for busy people
>> in the last 24 hours how many messages have been posted? A lot. By how many
>> people? Not many and most by one person.
>>
>> Did anyone create a CWiki page to outline an actual proposal and possible
>> variations?
>>
>
> I created this page:
> https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
I edited the root files and made it into a table where the disposition of each file and folder can be developed and approved.
Please don't overwrite it. Allow others to contribute. I suggest a similar format for other directories.
Regards,
Dave
>
>
>
>
>>
>> I would like to know what the delta is from what we are doing now to any
>> new state in order to see if I agree or have another choice.
>>
>> Regards,
>> Dave
>>
>> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
>>
>>> On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
>>>> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
>>>>
>>>>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>>>>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>>>>> wrote:
>>>>>>
>>>>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
>> wrote:
>>>>>>>
>>>>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>>>>>>> wrote:
>>>>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>>>>>>>>>> <jza@oooes.org
>>>>>>
>>>>>>>> wrote:
>>>>>>>>>>> I think the image structure on the website is a bit messy,
>>>>>>>>>>> there
>>>>>>>>>>> has
>>>>>>>> been
>>>>>>>>>>> some cleanup done by kschenk but I think there is still a lot
>>>>>>>>>>> of
>>>>>>>> clean up
>>>>>>>>>>> work to be done.
>>>>>>>>>>>
>>>>>>>>>>> For example, the new logo, was simply draged and drop to the
>>>>>>> AOOLogos
>>>>>>>>>>> folder with a huge name. I understand the name was needed to
>>>>>>> identify
>>>>>>>> it
>>>>>>>>>>> between the rest of the competitive logos. But now that is
>>>>>>>>>>> selected,
>>>>>>>> the
>>>>>>>>>>> current name is unecessary long.
>>>>>>>>>>>
>>>>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Right. That work is incomplete. I checked it in originally,
>>>>>>>>>> after
>>>>>>>>>> the logo vote, so we could start working on the product
>>>>>>>>>> integration
>>>>>>>>>> immediately. But note that the above logo is not the one we
>>>>>>>>>> actually
>>>>>>>>>> used in AOO 4.0 !!
>>>>>>>>>>
>>>>>>>>>> The one we actually used is this one:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>>>>>>>>>>
>>>>>>>>>> This was Chris R's contest logo with some minor technical
>>>>>>>>>> changes.
>>>>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>>>>>>>>>> which
>>>>>>>>>> I helped check in.
>>>>>>>>>>
>>>>>>>>>> My intent was to take that SVG and rename it to
>>>>> "master-logo-40.svg"
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
>>>>>>>>> to
>>>>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>>>>>>> incrementally
>>>>>>>>> replace with the future logos as we update the SVG.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Here's the complication: The old logos are still relevant some
>>>>>>>> some
>>>>>>>> purposes. For example, the PMC receives ongoing requests to approve
>>>>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
>>>>>>>> it
>>>>>>>> is a request by publishers who are making an e-book version of an
>>>>>>>> older print book. If their original request did not include the
>>>>>>>> e-book rights then they come back to us (and owners of every other
>>>>>>>> image they use) to request additional permissions.
>>>>>>>>
>>>>>>>
>>>>>>> I think that 'complication' is the lesser of two evils., compared to
>>>>>>> having to manage a ever growing ammount of images. And beside that,
>> do
>>>>>>> you
>>>>>>> realize the difference in objectives between ooo-site/images/
>>>>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>>>>>>
>>>>>>> I dont see any reason why those issues should impact the web works of
>>>>>>> ooo-site/images/. That folder is for website-design related work. It
>>>>> has,
>>>>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
>>>>>>> description of any kind. I think website should be as lean and easy
>> to
>>>>>>> follow since we expect these conventions be followed by a rotating
>>>>>>> community. So again K.I.S.S.
>>>>>>>
>>>>>>
>>>>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
>>>>> simply
>>>>>> because to make it easier to locate it. The other images files there
>>>>> belong
>>>>>> to the home page. The svg sub-directory here is really the mis-placed
>>>>> one.
>>>>>
>>>>> Actually I would like to see getting rid of the rasterize images
>>>>> instead. Modern browsers already process SVG natively without issues.
>>>>>
>>>>
>>>>
>>>> Well, that's not completely true: even if not "modern" any more there
>> are
>>>> literally millions of people still using internet explorer 8 or even
>> older
>>>> versions, and SVG support was *partially* implemented only from IE9. IE8
>>>> needs a plug-in for SVG rendering.
>>>>
>>>> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
>>>
>>> That's why I recomend and reference javascript libraries that take
>>> care of legacy browsers additionally there are fallback techniques
>>> (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
>>> can just test this easily using browsershots or something similar and
>>> evaluate.
>>>
>>>>
>>>> Regards
>>>> Ricardo
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> Also there are js libraries that ensure browser compatibility like the
>>>>> svgweb.js library:
>>>>> http://code.google.com/p/svgweb/
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>> If those complications arises, send them to marketing or branding
>>>>>>> workspaces.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> So it may be possible, going forward, to store logos as SVN
>>>>>>>> revisions
>>>>>>>> under the same name. But we cannot retroactively do this with
>>>>>>>> pre-Apache logos. And even if we could, this is harder for users of
>>>>>>>> the logo to access. It is much easier to have something like
>>>>>>>> logo-330.svg available via HTTP.
>>>>>>>>
>>>>>>>
>>>>>>> svg are just like HTML files, they are markup languages, we dont hold
>>>>> the
>>>>>>> index.html inmaculated and hold an apache-index.html and
>>>>>>> oracle-index.html,
>>>>>>> so I dont see why SVG should be any different.
>>>>>>
>>>>>>
>>>>>> I don't agree this assessment. The svg files contain branding, or
>>>>>> trademark sources. These are entities which should not be changed --
>>>>>> resulting in a trademark violation. If there is something wrong with
>>>>>> the
>>>>>> SVG files for whatever reason, this needs to undergo a justification
>>>>>> discussion.
>>>>>>
>>>>>> The only porpouse of having
>>>>>>> a source file, is for users to be able to modify it on the first
>>>>>>> place.
>>>>>>> Either by integrating to a bigger SVG design, or resizing it for
>> print
>>>>>>> work.
>>>>>>>
>>>>>>
>>>>>> This part I do agree with. The svg files can be used to produce
>> various
>>>>>> sizes of the "trademarked" entities. Changing the source of that
>> entity
>>>>> is
>>>>>> a different matter in my opinion.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Of course you can have a hybrid approach:
>>>>>>>>
>>>>>>>> 1) When a new logo is introduced, svn copy the old one into a
>>>>>>>> /old-logos directory with a new descriptive name. This preserves
>>>>>>>> the
>>>>>>>> version history.
>>>>>>>>
>>>>>>>
>>>>>>> This is not functional and just start acumulating part of the same
>>>>>>> garbage
>>>>>>> that svn is supposed to clean up. Again, if this was code, this would
>>>>>>> be
>>>>>>> totally unacceptable approach. If new logos are introduced then they
>>>>>>> should
>>>>>>> replace the current logo, and the old will live in anals of the svn
>>>>> logs.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> 2) New logo then is checked in as a new revision of logo-master.svg.
>>>>>>>>
>>>>>>>
>>>>>>> People are free to disagree with me, but I think this is a messy way
>>>>>>> to
>>>>>>> work, and for a webdev folder is completely useless, specially when
>>>>> there
>>>>>>> is a whole different project specialized on archiving, developing,
>> and
>>>>>>> multiplying artwork inside marketing, and a whole different project
>>>>>>> devoted
>>>>>>> to specifying the guideliness of the brand (aka logo).
>>>>>>>
>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> -Rob
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> or something clean like that. However, I have not had any luck
>>>>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
>>>>> get
>>>>>>>>>> errors. And I have not had any luck getting Kevin to send a
>>>>> version
>>>>>>>>>> that will load.
>>>>>>>>>>
>>>>>>>>>> So we're stuck right now with a logo that does load into
>>>>>>>>>> Inkscape,
>>>>>>>>>> but
>>>>>>>>>> is slightly different than the one we used in AOO 4.0.
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>> At the same time we have old logos which had been untouch. I
>>>>> think
>>>>>>> the
>>>>>>>>>>> webdevs have small understanding of a svn is builted so that
>>>>>>>>>>> the
>>>>>>> files
>>>>>>>>>> are
>>>>>>>>>>> updated without having different versions laying arround. Over
>>>>>>>>>>> this
>>>>>>>>>>> example, ooo-logo.png and
>>>>>>>>>>> AOO4_website_logo.png<
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>>>>>>>>>> exist.
>>>>>>>>>>>
>>>>>>>>>>> All these proliferation of logos, usually will built up to
>>>>>>>>>>> become
>>>>>>>>>>> incredibly messy to work. I suggest to put the information such
>>>>> as
>>>>>>>>>> author,
>>>>>>>>>>> version, status, etc. on the comments of the commit and not on
>>>>> the
>>>>>>>>>>> filename. Likewise to take the time to look for the source of
>>>>> the
>>>>>>>> image,
>>>>>>>>>>> since there is an SVG/ folder to link the source of them, and
>>>>>>> finally
>>>>>>>> if
>>>>>>>>>>> there are different images (sizes) to have a common convention.
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> A more logical naming scheme would be good, I agree. But this
>>>>>>>>>> has
>>>>>>>>>> been waiting for resolution of which SVG we should actually be
>>>>>>>>>> using.
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> -Rob
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> If you want to review the images please go here:
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Alexandro Colorado
>>>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>>>> http://www.openoffice.org
>>>>>>>>>>
>>>>>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Alexandro Colorado
>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>> http://www.openoffice.org
>>>>>>>>
>>>>>>>>
>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Alexandro Colorado
>>>>>>> Apache OpenOffice Contributor
>>>>>>> http://www.openoffice.org
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>
>> -------------------------------------------------------------------------------------------------
>>>>>> MzK
>>>>>>
>>>>>> Success is falling nine times and getting up ten."
>>>>>> -- Jon Bon Jovi
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Alexandro Colorado
>>>>> Apache OpenOffice Contributor
>>>>> http://www.openoffice.org
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Alexandro Colorado
>>> Apache OpenOffice Contributor
>>> http://www.openoffice.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Tue, Aug 13, 2013 at 5:04 PM, Dave Fisher <da...@comcast.net> wrote:
> Speaking of a confusing email exchange. This is difficult for busy people
> in the last 24 hours how many messages have been posted? A lot. By how many
> people? Not many and most by one person.
>
> Did anyone create a CWiki page to outline an actual proposal and possible
> variations?
>
I created this page:
https://cwiki.apache.org/confluence/display/OOOUSERS/File+handling+proposal+for+logos+and+graphics
>
> I would like to know what the delta is from what we are doing now to any
> new state in order to see if I agree or have another choice.
>
> Regards,
> Dave
>
> On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
>
> > On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
> >> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
> >>
> >>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> >>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
> >>> wrote:
> >>>>
> >>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org>
> wrote:
> >>>>>
> >>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> >>>>> wrote:
> >>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
> >>> wrote:
> >>>>>>>
> >>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
> >>>>>>>> <jza@oooes.org
> >>>>
> >>>>>> wrote:
> >>>>>>>>> I think the image structure on the website is a bit messy,
> >>>>>>>>> there
> >>>>>>>>> has
> >>>>>> been
> >>>>>>>>> some cleanup done by kschenk but I think there is still a lot
> >>>>>>>>> of
> >>>>>> clean up
> >>>>>>>>> work to be done.
> >>>>>>>>>
> >>>>>>>>> For example, the new logo, was simply draged and drop to the
> >>>>> AOOLogos
> >>>>>>>>> folder with a huge name. I understand the name was needed to
> >>>>> identify
> >>>>>> it
> >>>>>>>>> between the rest of the competitive logos. But now that is
> >>>>>>>>> selected,
> >>>>>> the
> >>>>>>>>> current name is unecessary long.
> >>>>>>>>>
> >>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> Right. That work is incomplete. I checked it in originally,
> >>>>>>>> after
> >>>>>>>> the logo vote, so we could start working on the product
> >>>>>>>> integration
> >>>>>>>> immediately. But note that the above logo is not the one we
> >>>>>>>> actually
> >>>>>>>> used in AOO 4.0 !!
> >>>>>>>>
> >>>>>>>> The one we actually used is this one:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>>>>>>>
> >>>>>>>> This was Chris R's contest logo with some minor technical
> >>>>>>>> changes.
> >>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
> >>>>>>>> which
> >>>>>>>> I helped check in.
> >>>>>>>>
> >>>>>>>> My intent was to take that SVG and rename it to
> >>> "master-logo-40.svg"
> >>>>>>>>
> >>>>>>>
> >>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
> >>>>>>> to
> >>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >>>>> incrementally
> >>>>>>> replace with the future logos as we update the SVG.
> >>>>>>>
> >>>>>>
> >>>>>> Here's the complication: The old logos are still relevant some
> >>>>>> some
> >>>>>> purposes. For example, the PMC receives ongoing requests to approve
> >>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
> >>>>>> it
> >>>>>> is a request by publishers who are making an e-book version of an
> >>>>>> older print book. If their original request did not include the
> >>>>>> e-book rights then they come back to us (and owners of every other
> >>>>>> image they use) to request additional permissions.
> >>>>>>
> >>>>>
> >>>>> I think that 'complication' is the lesser of two evils., compared to
> >>>>> having to manage a ever growing ammount of images. And beside that,
> do
> >>>>> you
> >>>>> realize the difference in objectives between ooo-site/images/
> >>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
> >>>>>
> >>>>> I dont see any reason why those issues should impact the web works of
> >>>>> ooo-site/images/. That folder is for website-design related work. It
> >>> has,
> >>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
> >>>>> description of any kind. I think website should be as lean and easy
> to
> >>>>> follow since we expect these conventions be followed by a rotating
> >>>>> community. So again K.I.S.S.
> >>>>>
> >>>>
> >>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
> >>> simply
> >>>> because to make it easier to locate it. The other images files there
> >>> belong
> >>>> to the home page. The svg sub-directory here is really the mis-placed
> >>> one.
> >>>
> >>> Actually I would like to see getting rid of the rasterize images
> >>> instead. Modern browsers already process SVG natively without issues.
> >>>
> >>
> >>
> >> Well, that's not completely true: even if not "modern" any more there
> are
> >> literally millions of people still using internet explorer 8 or even
> older
> >> versions, and SVG support was *partially* implemented only from IE9. IE8
> >> needs a plug-in for SVG rendering.
> >>
> >> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
> >
> > That's why I recomend and reference javascript libraries that take
> > care of legacy browsers additionally there are fallback techniques
> > (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
> > can just test this easily using browsershots or something similar and
> > evaluate.
> >
> >>
> >> Regards
> >> Ricardo
> >>
> >>
> >>
> >>
> >>
> >>> Also there are js libraries that ensure browser compatibility like the
> >>> svgweb.js library:
> >>> http://code.google.com/p/svgweb/
> >>>
> >>>
> >>>>
> >>>>
> >>>>> If those complications arises, send them to marketing or branding
> >>>>> workspaces.
> >>>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> So it may be possible, going forward, to store logos as SVN
> >>>>>> revisions
> >>>>>> under the same name. But we cannot retroactively do this with
> >>>>>> pre-Apache logos. And even if we could, this is harder for users of
> >>>>>> the logo to access. It is much easier to have something like
> >>>>>> logo-330.svg available via HTTP.
> >>>>>>
> >>>>>
> >>>>> svg are just like HTML files, they are markup languages, we dont hold
> >>> the
> >>>>> index.html inmaculated and hold an apache-index.html and
> >>>>> oracle-index.html,
> >>>>> so I dont see why SVG should be any different.
> >>>>
> >>>>
> >>>> I don't agree this assessment. The svg files contain branding, or
> >>>> trademark sources. These are entities which should not be changed --
> >>>> resulting in a trademark violation. If there is something wrong with
> >>>> the
> >>>> SVG files for whatever reason, this needs to undergo a justification
> >>>> discussion.
> >>>>
> >>>> The only porpouse of having
> >>>>> a source file, is for users to be able to modify it on the first
> >>>>> place.
> >>>>> Either by integrating to a bigger SVG design, or resizing it for
> print
> >>>>> work.
> >>>>>
> >>>>
> >>>> This part I do agree with. The svg files can be used to produce
> various
> >>>> sizes of the "trademarked" entities. Changing the source of that
> entity
> >>> is
> >>>> a different matter in my opinion.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> Of course you can have a hybrid approach:
> >>>>>>
> >>>>>> 1) When a new logo is introduced, svn copy the old one into a
> >>>>>> /old-logos directory with a new descriptive name. This preserves
> >>>>>> the
> >>>>>> version history.
> >>>>>>
> >>>>>
> >>>>> This is not functional and just start acumulating part of the same
> >>>>> garbage
> >>>>> that svn is supposed to clean up. Again, if this was code, this would
> >>>>> be
> >>>>> totally unacceptable approach. If new logos are introduced then they
> >>>>> should
> >>>>> replace the current logo, and the old will live in anals of the svn
> >>> logs.
> >>>>>
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> 2) New logo then is checked in as a new revision of logo-master.svg.
> >>>>>>
> >>>>>
> >>>>> People are free to disagree with me, but I think this is a messy way
> >>>>> to
> >>>>> work, and for a webdev folder is completely useless, specially when
> >>> there
> >>>>> is a whole different project specialized on archiving, developing,
> and
> >>>>> multiplying artwork inside marketing, and a whole different project
> >>>>> devoted
> >>>>> to specifying the guideliness of the brand (aka logo).
> >>>>>
> >>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> -Rob
> >>>>>>
> >>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>> or something clean like that. However, I have not had any luck
> >>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
> >>> get
> >>>>>>>> errors. And I have not had any luck getting Kevin to send a
> >>> version
> >>>>>>>> that will load.
> >>>>>>>>
> >>>>>>>> So we're stuck right now with a logo that does load into
> >>>>>>>> Inkscape,
> >>>>>>>> but
> >>>>>>>> is slightly different than the one we used in AOO 4.0.
> >>>>>>>>
> >>>>>>>
> >>>>>>>>> At the same time we have old logos which had been untouch. I
> >>> think
> >>>>> the
> >>>>>>>>> webdevs have small understanding of a svn is builted so that
> >>>>>>>>> the
> >>>>> files
> >>>>>>>> are
> >>>>>>>>> updated without having different versions laying arround. Over
> >>>>>>>>> this
> >>>>>>>>> example, ooo-logo.png and
> >>>>>>>>> AOO4_website_logo.png<
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >>>>>>>>> exist.
> >>>>>>>>>
> >>>>>>>>> All these proliferation of logos, usually will built up to
> >>>>>>>>> become
> >>>>>>>>> incredibly messy to work. I suggest to put the information such
> >>> as
> >>>>>>>> author,
> >>>>>>>>> version, status, etc. on the comments of the commit and not on
> >>> the
> >>>>>>>>> filename. Likewise to take the time to look for the source of
> >>> the
> >>>>>> image,
> >>>>>>>>> since there is an SVG/ folder to link the source of them, and
> >>>>> finally
> >>>>>> if
> >>>>>>>>> there are different images (sizes) to have a common convention.
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> A more logical naming scheme would be good, I agree. But this
> >>>>>>>> has
> >>>>>>>> been waiting for resolution of which SVG we should actually be
> >>>>>>>> using.
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>>
> >>>>>>>> -Rob
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> If you want to review the images please go here:
> >>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Alexandro Colorado
> >>>>>>>>> Apache OpenOffice Contributor
> >>>>>>>>> http://www.openoffice.org
> >>>>>>>>
> >>>>>>>>
> >>> ---------------------------------------------------------------------
> >>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> Alexandro Colorado
> >>>>>>> Apache OpenOffice Contributor
> >>>>>>> http://www.openoffice.org
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Alexandro Colorado
> >>>>> Apache OpenOffice Contributor
> >>>>> http://www.openoffice.org
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>
> -------------------------------------------------------------------------------------------------
> >>>> MzK
> >>>>
> >>>> Success is falling nine times and getting up ten."
> >>>> -- Jon Bon Jovi
> >>>>
> >>>
> >>>
> >>> --
> >>> Alexandro Colorado
> >>> Apache OpenOffice Contributor
> >>> http://www.openoffice.org
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>
> >>>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <da...@comcast.net>.
Speaking of a confusing email exchange. This is difficult for busy people in the last 24 hours how many messages have been posted? A lot. By how many people? Not many and most by one person.
Did anyone create a CWiki page to outline an actual proposal and possible variations?
I would like to know what the delta is from what we are doing now to any new state in order to see if I agree or have another choice.
Regards,
Dave
On Aug 13, 2013, at 2:04 PM, Alexandro Colorado wrote:
> On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
>> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
>>
>>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>>>> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>>> wrote:
>>>>
>>>>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>>>>>
>>>>>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>>>>> wrote:
>>>>>>> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>>> wrote:
>>>>>>>
>>>>>>>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>>>>>>>> <jza@oooes.org
>>>>
>>>>>> wrote:
>>>>>>>>> I think the image structure on the website is a bit messy,
>>>>>>>>> there
>>>>>>>>> has
>>>>>> been
>>>>>>>>> some cleanup done by kschenk but I think there is still a lot
>>>>>>>>> of
>>>>>> clean up
>>>>>>>>> work to be done.
>>>>>>>>>
>>>>>>>>> For example, the new logo, was simply draged and drop to the
>>>>> AOOLogos
>>>>>>>>> folder with a huge name. I understand the name was needed to
>>>>> identify
>>>>>> it
>>>>>>>>> between the rest of the competitive logos. But now that is
>>>>>>>>> selected,
>>>>>> the
>>>>>>>>> current name is unecessary long.
>>>>>>>>>
>>>>>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>>>>>>>>
>>>>>>
>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> Right. That work is incomplete. I checked it in originally,
>>>>>>>> after
>>>>>>>> the logo vote, so we could start working on the product
>>>>>>>> integration
>>>>>>>> immediately. But note that the above logo is not the one we
>>>>>>>> actually
>>>>>>>> used in AOO 4.0 !!
>>>>>>>>
>>>>>>>> The one we actually used is this one:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>>>>>>>>
>>>>>>>> This was Chris R's contest logo with some minor technical
>>>>>>>> changes.
>>>>>>>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>>>>>>>> which
>>>>>>>> I helped check in.
>>>>>>>>
>>>>>>>> My intent was to take that SVG and rename it to
>>> "master-logo-40.svg"
>>>>>>>>
>>>>>>>
>>>>>>> Again I think we do need a convention for a "logo.svg" as opposed
>>>>>>> to
>>>>>>> ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>>>>> incrementally
>>>>>>> replace with the future logos as we update the SVG.
>>>>>>>
>>>>>>
>>>>>> Here's the complication: The old logos are still relevant some
>>>>>> some
>>>>>> purposes. For example, the PMC receives ongoing requests to approve
>>>>>> use of the old OpenOffice.org logo. Why would that happen? Often
>>>>>> it
>>>>>> is a request by publishers who are making an e-book version of an
>>>>>> older print book. If their original request did not include the
>>>>>> e-book rights then they come back to us (and owners of every other
>>>>>> image they use) to request additional permissions.
>>>>>>
>>>>>
>>>>> I think that 'complication' is the lesser of two evils., compared to
>>>>> having to manage a ever growing ammount of images. And beside that, do
>>>>> you
>>>>> realize the difference in objectives between ooo-site/images/
>>>>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>>>>
>>>>> I dont see any reason why those issues should impact the web works of
>>>>> ooo-site/images/. That folder is for website-design related work. It
>>> has,
>>>>> or shouldnt hold any porpouse to archieve past work, nor to hold
>>>>> description of any kind. I think website should be as lean and easy to
>>>>> follow since we expect these conventions be followed by a rotating
>>>>> community. So again K.I.S.S.
>>>>>
>>>>
>>>> No, it shouldn't. The ooo-site/images areas got the logo added to it
>>> simply
>>>> because to make it easier to locate it. The other images files there
>>> belong
>>>> to the home page. The svg sub-directory here is really the mis-placed
>>> one.
>>>
>>> Actually I would like to see getting rid of the rasterize images
>>> instead. Modern browsers already process SVG natively without issues.
>>>
>>
>>
>> Well, that's not completely true: even if not "modern" any more there are
>> literally millions of people still using internet explorer 8 or even older
>> versions, and SVG support was *partially* implemented only from IE9. IE8
>> needs a plug-in for SVG rendering.
>>
>> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
>
> That's why I recomend and reference javascript libraries that take
> care of legacy browsers additionally there are fallback techniques
> (http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
> can just test this easily using browsershots or something similar and
> evaluate.
>
>>
>> Regards
>> Ricardo
>>
>>
>>
>>
>>
>>> Also there are js libraries that ensure browser compatibility like the
>>> svgweb.js library:
>>> http://code.google.com/p/svgweb/
>>>
>>>
>>>>
>>>>
>>>>> If those complications arises, send them to marketing or branding
>>>>> workspaces.
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> So it may be possible, going forward, to store logos as SVN
>>>>>> revisions
>>>>>> under the same name. But we cannot retroactively do this with
>>>>>> pre-Apache logos. And even if we could, this is harder for users of
>>>>>> the logo to access. It is much easier to have something like
>>>>>> logo-330.svg available via HTTP.
>>>>>>
>>>>>
>>>>> svg are just like HTML files, they are markup languages, we dont hold
>>> the
>>>>> index.html inmaculated and hold an apache-index.html and
>>>>> oracle-index.html,
>>>>> so I dont see why SVG should be any different.
>>>>
>>>>
>>>> I don't agree this assessment. The svg files contain branding, or
>>>> trademark sources. These are entities which should not be changed --
>>>> resulting in a trademark violation. If there is something wrong with
>>>> the
>>>> SVG files for whatever reason, this needs to undergo a justification
>>>> discussion.
>>>>
>>>> The only porpouse of having
>>>>> a source file, is for users to be able to modify it on the first
>>>>> place.
>>>>> Either by integrating to a bigger SVG design, or resizing it for print
>>>>> work.
>>>>>
>>>>
>>>> This part I do agree with. The svg files can be used to produce various
>>>> sizes of the "trademarked" entities. Changing the source of that entity
>>> is
>>>> a different matter in my opinion.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> Of course you can have a hybrid approach:
>>>>>>
>>>>>> 1) When a new logo is introduced, svn copy the old one into a
>>>>>> /old-logos directory with a new descriptive name. This preserves
>>>>>> the
>>>>>> version history.
>>>>>>
>>>>>
>>>>> This is not functional and just start acumulating part of the same
>>>>> garbage
>>>>> that svn is supposed to clean up. Again, if this was code, this would
>>>>> be
>>>>> totally unacceptable approach. If new logos are introduced then they
>>>>> should
>>>>> replace the current logo, and the old will live in anals of the svn
>>> logs.
>>>>>
>>>>>
>>>>>
>>>>>>
>>>>>> 2) New logo then is checked in as a new revision of logo-master.svg.
>>>>>>
>>>>>
>>>>> People are free to disagree with me, but I think this is a messy way
>>>>> to
>>>>> work, and for a webdev folder is completely useless, specially when
>>> there
>>>>> is a whole different project specialized on archiving, developing, and
>>>>> multiplying artwork inside marketing, and a whole different project
>>>>> devoted
>>>>> to specifying the guideliness of the brand (aka logo).
>>>>>
>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> -Rob
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> or something clean like that. However, I have not had any luck
>>>>>>>> getting this logo to load into Inkscape or Adobe Illustrator. I
>>> get
>>>>>>>> errors. And I have not had any luck getting Kevin to send a
>>> version
>>>>>>>> that will load.
>>>>>>>>
>>>>>>>> So we're stuck right now with a logo that does load into
>>>>>>>> Inkscape,
>>>>>>>> but
>>>>>>>> is slightly different than the one we used in AOO 4.0.
>>>>>>>>
>>>>>>>
>>>>>>>>> At the same time we have old logos which had been untouch. I
>>> think
>>>>> the
>>>>>>>>> webdevs have small understanding of a svn is builted so that
>>>>>>>>> the
>>>>> files
>>>>>>>> are
>>>>>>>>> updated without having different versions laying arround. Over
>>>>>>>>> this
>>>>>>>>> example, ooo-logo.png and
>>>>>>>>> AOO4_website_logo.png<
>>>>>>>>
>>>>>>
>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>>>>>>>> exist.
>>>>>>>>>
>>>>>>>>> All these proliferation of logos, usually will built up to
>>>>>>>>> become
>>>>>>>>> incredibly messy to work. I suggest to put the information such
>>> as
>>>>>>>> author,
>>>>>>>>> version, status, etc. on the comments of the commit and not on
>>> the
>>>>>>>>> filename. Likewise to take the time to look for the source of
>>> the
>>>>>> image,
>>>>>>>>> since there is an SVG/ folder to link the source of them, and
>>>>> finally
>>>>>> if
>>>>>>>>> there are different images (sizes) to have a common convention.
>>>>>>>>>
>>>>>>>>
>>>>>>>> A more logical naming scheme would be good, I agree. But this
>>>>>>>> has
>>>>>>>> been waiting for resolution of which SVG we should actually be
>>>>>>>> using.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> -Rob
>>>>>>>>
>>>>>>>>
>>>>>>>>> If you want to review the images please go here:
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Alexandro Colorado
>>>>>>>>> Apache OpenOffice Contributor
>>>>>>>>> http://www.openoffice.org
>>>>>>>>
>>>>>>>>
>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Alexandro Colorado
>>>>>>> Apache OpenOffice Contributor
>>>>>>> http://www.openoffice.org
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Alexandro Colorado
>>>>> Apache OpenOffice Contributor
>>>>> http://www.openoffice.org
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>> -------------------------------------------------------------------------------------------------
>>>> MzK
>>>>
>>>> Success is falling nine times and getting up ten."
>>>> -- Jon Bon Jovi
>>>>
>>>
>>>
>>> --
>>> Alexandro Colorado
>>> Apache OpenOffice Contributor
>>> http://www.openoffice.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>>
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Ricardo Berlasso <rg...@gmail.com> wrote:
> 2013/8/13 Alexandro Colorado <jz...@oooes.org>
>
>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>> > On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> >
>> >> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>> >>
>> >> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> >> wrote:
>> >> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>> wrote:
>> >> > >
>> >> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>> >> > >> <jza@oooes.org
>> >
>> >> > wrote:
>> >> > >> > I think the image structure on the website is a bit messy,
>> >> > >> > there
>> >> > >> > has
>> >> > been
>> >> > >> > some cleanup done by kschenk but I think there is still a lot
>> >> > >> > of
>> >> > clean up
>> >> > >> > work to be done.
>> >> > >> >
>> >> > >> > For example, the new logo, was simply draged and drop to the
>> >> AOOLogos
>> >> > >> > folder with a huge name. I understand the name was needed to
>> >> identify
>> >> > it
>> >> > >> > between the rest of the competitive logos. But now that is
>> >> > >> > selected,
>> >> > the
>> >> > >> > current name is unecessary long.
>> >> > >> >
>> >> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >> > >> >
>> >> > >> >
>> >> > >>
>> >> > >> Right. That work is incomplete. I checked it in originally,
>> >> > >> after
>> >> > >> the logo vote, so we could start working on the product
>> >> > >> integration
>> >> > >> immediately. But note that the above logo is not the one we
>> >> > >> actually
>> >> > >> used in AOO 4.0 !!
>> >> > >>
>> >> > >> The one we actually used is this one:
>> >> > >>
>> >> > >>
>> >> > >>
>> >> > >>
>> >> >
>> >>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> >> > >>
>> >> > >> This was Chris R's contest logo with some minor technical
>> >> > >> changes.
>> >> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>> >> > >> which
>> >> > >> I helped check in.
>> >> > >>
>> >> > >> My intent was to take that SVG and rename it to
>> "master-logo-40.svg"
>> >> > >>
>> >> > >
>> >> > > Again I think we do need a convention for a "logo.svg" as opposed
>> >> > > to
>> >> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> >> incrementally
>> >> > > replace with the future logos as we update the SVG.
>> >> > >
>> >> >
>> >> > Here's the complication: The old logos are still relevant some
>> >> > some
>> >> > purposes. For example, the PMC receives ongoing requests to approve
>> >> > use of the old OpenOffice.org logo. Why would that happen? Often
>> >> > it
>> >> > is a request by publishers who are making an e-book version of an
>> >> > older print book. If their original request did not include the
>> >> > e-book rights then they come back to us (and owners of every other
>> >> > image they use) to request additional permissions.
>> >> >
>> >>
>> >> I think that 'complication' is the lesser of two evils., compared to
>> >> having to manage a ever growing ammount of images. And beside that, do
>> >> you
>> >> realize the difference in objectives between ooo-site/images/
>> >> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>> >>
>> >> I dont see any reason why those issues should impact the web works of
>> >> ooo-site/images/. That folder is for website-design related work. It
>> has,
>> >> or shouldnt hold any porpouse to archieve past work, nor to hold
>> >> description of any kind. I think website should be as lean and easy to
>> >> follow since we expect these conventions be followed by a rotating
>> >> community. So again K.I.S.S.
>> >>
>> >
>> > No, it shouldn't. The ooo-site/images areas got the logo added to it
>> simply
>> > because to make it easier to locate it. The other images files there
>> belong
>> > to the home page. The svg sub-directory here is really the mis-placed
>> one.
>>
>> Actually I would like to see getting rid of the rasterize images
>> instead. Modern browsers already process SVG natively without issues.
>>
>
>
> Well, that's not completely true: even if not "modern" any more there are
> literally millions of people still using internet explorer 8 or even older
> versions, and SVG support was *partially* implemented only from IE9. IE8
> needs a plug-in for SVG rendering.
>
> http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
That's why I recomend and reference javascript libraries that take
care of legacy browsers additionally there are fallback techniques
(http://dbushell.com/2012/04/03/svg-use-it-already/). Then again, you
can just test this easily using browsershots or something similar and
evaluate.
>
> Regards
> Ricardo
>
>
>
>
>
>> Also there are js libraries that ensure browser compatibility like the
>> svgweb.js library:
>> http://code.google.com/p/svgweb/
>>
>>
>> >
>> >
>> >> If those complications arises, send them to marketing or branding
>> >> workspaces.
>> >>
>> >>
>> >>
>> >> >
>> >> > So it may be possible, going forward, to store logos as SVN
>> >> > revisions
>> >> > under the same name. But we cannot retroactively do this with
>> >> > pre-Apache logos. And even if we could, this is harder for users of
>> >> > the logo to access. It is much easier to have something like
>> >> > logo-330.svg available via HTTP.
>> >> >
>> >>
>> >> svg are just like HTML files, they are markup languages, we dont hold
>> the
>> >> index.html inmaculated and hold an apache-index.html and
>> >> oracle-index.html,
>> >> so I dont see why SVG should be any different.
>> >
>> >
>> > I don't agree this assessment. The svg files contain branding, or
>> > trademark sources. These are entities which should not be changed --
>> > resulting in a trademark violation. If there is something wrong with
>> > the
>> > SVG files for whatever reason, this needs to undergo a justification
>> > discussion.
>> >
>> > The only porpouse of having
>> >> a source file, is for users to be able to modify it on the first
>> >> place.
>> >> Either by integrating to a bigger SVG design, or resizing it for print
>> >> work.
>> >>
>> >
>> > This part I do agree with. The svg files can be used to produce various
>> > sizes of the "trademarked" entities. Changing the source of that entity
>> is
>> > a different matter in my opinion.
>> >
>> >
>> >
>> >
>> >
>> >>
>> >>
>> >> >
>> >> > Of course you can have a hybrid approach:
>> >> >
>> >> > 1) When a new logo is introduced, svn copy the old one into a
>> >> > /old-logos directory with a new descriptive name. This preserves
>> >> > the
>> >> > version history.
>> >> >
>> >>
>> >> This is not functional and just start acumulating part of the same
>> >> garbage
>> >> that svn is supposed to clean up. Again, if this was code, this would
>> >> be
>> >> totally unacceptable approach. If new logos are introduced then they
>> >> should
>> >> replace the current logo, and the old will live in anals of the svn
>> logs.
>> >>
>> >>
>> >>
>> >> >
>> >> > 2) New logo then is checked in as a new revision of logo-master.svg.
>> >> >
>> >>
>> >> People are free to disagree with me, but I think this is a messy way
>> >> to
>> >> work, and for a webdev folder is completely useless, specially when
>> there
>> >> is a whole different project specialized on archiving, developing, and
>> >> multiplying artwork inside marketing, and a whole different project
>> >> devoted
>> >> to specifying the guideliness of the brand (aka logo).
>> >>
>> >>
>> >> > Regards,
>> >> >
>> >> > -Rob
>> >> >
>> >> >
>> >> > >
>> >> > >
>> >> > >> or something clean like that. However, I have not had any luck
>> >> > >> getting this logo to load into Inkscape or Adobe Illustrator. I
>> get
>> >> > >> errors. And I have not had any luck getting Kevin to send a
>> version
>> >> > >> that will load.
>> >> > >>
>> >> > >> So we're stuck right now with a logo that does load into
>> >> > >> Inkscape,
>> >> > >> but
>> >> > >> is slightly different than the one we used in AOO 4.0.
>> >> > >>
>> >> > >
>> >> > >> > At the same time we have old logos which had been untouch. I
>> think
>> >> the
>> >> > >> > webdevs have small understanding of a svn is builted so that
>> >> > >> > the
>> >> files
>> >> > >> are
>> >> > >> > updated without having different versions laying arround. Over
>> >> > >> > this
>> >> > >> > example, ooo-logo.png and
>> >> > >> > AOO4_website_logo.png<
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >> > >> >exist.
>> >> > >> >
>> >> > >> > All these proliferation of logos, usually will built up to
>> >> > >> > become
>> >> > >> > incredibly messy to work. I suggest to put the information such
>> as
>> >> > >> author,
>> >> > >> > version, status, etc. on the comments of the commit and not on
>> the
>> >> > >> > filename. Likewise to take the time to look for the source of
>> the
>> >> > image,
>> >> > >> > since there is an SVG/ folder to link the source of them, and
>> >> finally
>> >> > if
>> >> > >> > there are different images (sizes) to have a common convention.
>> >> > >> >
>> >> > >>
>> >> > >> A more logical naming scheme would be good, I agree. But this
>> >> > >> has
>> >> > >> been waiting for resolution of which SVG we should actually be
>> >> > >> using.
>> >> > >>
>> >> > >> Regards,
>> >> > >>
>> >> > >> -Rob
>> >> > >>
>> >> > >>
>> >> > >> > If you want to review the images please go here:
>> >> > >> >
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >> > >> >
>> >> > >> > --
>> >> > >> > Alexandro Colorado
>> >> > >> > Apache OpenOffice Contributor
>> >> > >> > http://www.openoffice.org
>> >> > >>
>> >> > >>
>> ---------------------------------------------------------------------
>> >> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >> > >>
>> >> > >>
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Alexandro Colorado
>> >> > > Apache OpenOffice Contributor
>> >> > > http://www.openoffice.org
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> > For additional commands, e-mail: dev-help@openoffice.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> Alexandro Colorado
>> >> Apache OpenOffice Contributor
>> >> http://www.openoffice.org
>> >>
>> >
>> >
>> >
>> > --
>> >
>> -------------------------------------------------------------------------------------------------
>> > MzK
>> >
>> > Success is falling nine times and getting up ten."
>> > -- Jon Bon Jovi
>> >
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Ricardo Berlasso <rg...@gmail.com>.
2013/8/13 Alexandro Colorado <jz...@oooes.org>
> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> > On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> >
> >> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
> >>
> >> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> >> wrote:
> >> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
> wrote:
> >> > >
> >> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jza@oooes.org
> >
> >> > wrote:
> >> > >> > I think the image structure on the website is a bit messy, there
> >> > >> > has
> >> > been
> >> > >> > some cleanup done by kschenk but I think there is still a lot of
> >> > clean up
> >> > >> > work to be done.
> >> > >> >
> >> > >> > For example, the new logo, was simply draged and drop to the
> >> AOOLogos
> >> > >> > folder with a huge name. I understand the name was needed to
> >> identify
> >> > it
> >> > >> > between the rest of the competitive logos. But now that is
> >> > >> > selected,
> >> > the
> >> > >> > current name is unecessary long.
> >> > >> >
> >> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> > >> >
> >> > >> >
> >> > >>
> >> > >> Right. That work is incomplete. I checked it in originally, after
> >> > >> the logo vote, so we could start working on the product integration
> >> > >> immediately. But note that the above logo is not the one we
> >> > >> actually
> >> > >> used in AOO 4.0 !!
> >> > >>
> >> > >> The one we actually used is this one:
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> >
> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >> > >>
> >> > >> This was Chris R's contest logo with some minor technical changes.
> >> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
> >> > >> which
> >> > >> I helped check in.
> >> > >>
> >> > >> My intent was to take that SVG and rename it to
> "master-logo-40.svg"
> >> > >>
> >> > >
> >> > > Again I think we do need a convention for a "logo.svg" as opposed to
> >> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >> incrementally
> >> > > replace with the future logos as we update the SVG.
> >> > >
> >> >
> >> > Here's the complication: The old logos are still relevant some some
> >> > purposes. For example, the PMC receives ongoing requests to approve
> >> > use of the old OpenOffice.org logo. Why would that happen? Often it
> >> > is a request by publishers who are making an e-book version of an
> >> > older print book. If their original request did not include the
> >> > e-book rights then they come back to us (and owners of every other
> >> > image they use) to request additional permissions.
> >> >
> >>
> >> I think that 'complication' is the lesser of two evils., compared to
> >> having to manage a ever growing ammount of images. And beside that, do
> >> you
> >> realize the difference in objectives between ooo-site/images/
> >> ooo-site/marketing/art/images/ and ooo-site/branding/images.
> >>
> >> I dont see any reason why those issues should impact the web works of
> >> ooo-site/images/. That folder is for website-design related work. It
> has,
> >> or shouldnt hold any porpouse to archieve past work, nor to hold
> >> description of any kind. I think website should be as lean and easy to
> >> follow since we expect these conventions be followed by a rotating
> >> community. So again K.I.S.S.
> >>
> >
> > No, it shouldn't. The ooo-site/images areas got the logo added to it
> simply
> > because to make it easier to locate it. The other images files there
> belong
> > to the home page. The svg sub-directory here is really the mis-placed
> one.
>
> Actually I would like to see getting rid of the rasterize images
> instead. Modern browsers already process SVG natively without issues.
>
Well, that's not completely true: even if not "modern" any more there are
literally millions of people still using internet explorer 8 or even older
versions, and SVG support was *partially* implemented only from IE9. IE8
needs a plug-in for SVG rendering.
http://en.wikipedia.org/wiki/Scalable_Vector_Graphics#Compatibility
Regards
Ricardo
> Also there are js libraries that ensure browser compatibility like the
> svgweb.js library:
> http://code.google.com/p/svgweb/
>
>
> >
> >
> >> If those complications arises, send them to marketing or branding
> >> workspaces.
> >>
> >>
> >>
> >> >
> >> > So it may be possible, going forward, to store logos as SVN revisions
> >> > under the same name. But we cannot retroactively do this with
> >> > pre-Apache logos. And even if we could, this is harder for users of
> >> > the logo to access. It is much easier to have something like
> >> > logo-330.svg available via HTTP.
> >> >
> >>
> >> svg are just like HTML files, they are markup languages, we dont hold
> the
> >> index.html inmaculated and hold an apache-index.html and
> >> oracle-index.html,
> >> so I dont see why SVG should be any different.
> >
> >
> > I don't agree this assessment. The svg files contain branding, or
> > trademark sources. These are entities which should not be changed --
> > resulting in a trademark violation. If there is something wrong with the
> > SVG files for whatever reason, this needs to undergo a justification
> > discussion.
> >
> > The only porpouse of having
> >> a source file, is for users to be able to modify it on the first place.
> >> Either by integrating to a bigger SVG design, or resizing it for print
> >> work.
> >>
> >
> > This part I do agree with. The svg files can be used to produce various
> > sizes of the "trademarked" entities. Changing the source of that entity
> is
> > a different matter in my opinion.
> >
> >
> >
> >
> >
> >>
> >>
> >> >
> >> > Of course you can have a hybrid approach:
> >> >
> >> > 1) When a new logo is introduced, svn copy the old one into a
> >> > /old-logos directory with a new descriptive name. This preserves the
> >> > version history.
> >> >
> >>
> >> This is not functional and just start acumulating part of the same
> >> garbage
> >> that svn is supposed to clean up. Again, if this was code, this would be
> >> totally unacceptable approach. If new logos are introduced then they
> >> should
> >> replace the current logo, and the old will live in anals of the svn
> logs.
> >>
> >>
> >>
> >> >
> >> > 2) New logo then is checked in as a new revision of logo-master.svg.
> >> >
> >>
> >> People are free to disagree with me, but I think this is a messy way to
> >> work, and for a webdev folder is completely useless, specially when
> there
> >> is a whole different project specialized on archiving, developing, and
> >> multiplying artwork inside marketing, and a whole different project
> >> devoted
> >> to specifying the guideliness of the brand (aka logo).
> >>
> >>
> >> > Regards,
> >> >
> >> > -Rob
> >> >
> >> >
> >> > >
> >> > >
> >> > >> or something clean like that. However, I have not had any luck
> >> > >> getting this logo to load into Inkscape or Adobe Illustrator. I
> get
> >> > >> errors. And I have not had any luck getting Kevin to send a
> version
> >> > >> that will load.
> >> > >>
> >> > >> So we're stuck right now with a logo that does load into Inkscape,
> >> > >> but
> >> > >> is slightly different than the one we used in AOO 4.0.
> >> > >>
> >> > >
> >> > >> > At the same time we have old logos which had been untouch. I
> think
> >> the
> >> > >> > webdevs have small understanding of a svn is builted so that the
> >> files
> >> > >> are
> >> > >> > updated without having different versions laying arround. Over
> >> > >> > this
> >> > >> > example, ooo-logo.png and
> >> > >> > AOO4_website_logo.png<
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> > >> >exist.
> >> > >> >
> >> > >> > All these proliferation of logos, usually will built up to become
> >> > >> > incredibly messy to work. I suggest to put the information such
> as
> >> > >> author,
> >> > >> > version, status, etc. on the comments of the commit and not on
> the
> >> > >> > filename. Likewise to take the time to look for the source of
> the
> >> > image,
> >> > >> > since there is an SVG/ folder to link the source of them, and
> >> finally
> >> > if
> >> > >> > there are different images (sizes) to have a common convention.
> >> > >> >
> >> > >>
> >> > >> A more logical naming scheme would be good, I agree. But this has
> >> > >> been waiting for resolution of which SVG we should actually be
> >> > >> using.
> >> > >>
> >> > >> Regards,
> >> > >>
> >> > >> -Rob
> >> > >>
> >> > >>
> >> > >> > If you want to review the images please go here:
> >> > >> >
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> > >> >
> >> > >> > --
> >> > >> > Alexandro Colorado
> >> > >> > Apache OpenOffice Contributor
> >> > >> > http://www.openoffice.org
> >> > >>
> >> > >>
> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> > > --
> >> > > Alexandro Colorado
> >> > > Apache OpenOffice Contributor
> >> > > http://www.openoffice.org
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Alexandro Colorado
> >> Apache OpenOffice Contributor
> >> http://www.openoffice.org
> >>
> >
> >
> >
> > --
> >
> -------------------------------------------------------------------------------------------------
> > MzK
> >
> > Success is falling nine times and getting up ten."
> > -- Jon Bon Jovi
> >
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>
>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>>
>> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
>> > >
>> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
>> > wrote:
>> > >> > I think the image structure on the website is a bit messy, there
>> > >> > has
>> > been
>> > >> > some cleanup done by kschenk but I think there is still a lot of
>> > clean up
>> > >> > work to be done.
>> > >> >
>> > >> > For example, the new logo, was simply draged and drop to the
>> AOOLogos
>> > >> > folder with a huge name. I understand the name was needed to
>> identify
>> > it
>> > >> > between the rest of the competitive logos. But now that is
>> > >> > selected,
>> > the
>> > >> > current name is unecessary long.
>> > >> >
>> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> > >> >
>> > >> >
>> > >>
>> > >> Right. That work is incomplete. I checked it in originally, after
>> > >> the logo vote, so we could start working on the product integration
>> > >> immediately. But note that the above logo is not the one we
>> > >> actually
>> > >> used in AOO 4.0 !!
>> > >>
>> > >> The one we actually used is this one:
>> > >>
>> > >>
>> > >>
>> > >>
>> >
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> > >>
>> > >> This was Chris R's contest logo with some minor technical changes.
>> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>> > >> which
>> > >> I helped check in.
>> > >>
>> > >> My intent was to take that SVG and rename it to "master-logo-40.svg"
>> > >>
>> > >
>> > > Again I think we do need a convention for a "logo.svg" as opposed to
>> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> incrementally
>> > > replace with the future logos as we update the SVG.
>> > >
>> >
>> > Here's the complication: The old logos are still relevant some some
>> > purposes. For example, the PMC receives ongoing requests to approve
>> > use of the old OpenOffice.org logo. Why would that happen? Often it
>> > is a request by publishers who are making an e-book version of an
>> > older print book. If their original request did not include the
>> > e-book rights then they come back to us (and owners of every other
>> > image they use) to request additional permissions.
>> >
>>
>> I think that 'complication' is the lesser of two evils., compared to
>> having to manage a ever growing ammount of images. And beside that, do
>> you
>> realize the difference in objectives between ooo-site/images/
>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>
>> I dont see any reason why those issues should impact the web works of
>> ooo-site/images/. That folder is for website-design related work. It has,
>> or shouldnt hold any porpouse to archieve past work, nor to hold
>> description of any kind. I think website should be as lean and easy to
>> follow since we expect these conventions be followed by a rotating
>> community. So again K.I.S.S.
>>
>
> No, it shouldn't. The ooo-site/images areas got the logo added to it simply
> because to make it easier to locate it. The other images files there belong
> to the home page. The svg sub-directory here is really the mis-placed one.
Actually I would like to see getting rid of the rasterize images
instead. Modern browsers already process SVG natively without issues.
Also there are js libraries that ensure browser compatibility like the
svgweb.js library:
http://code.google.com/p/svgweb/
>
>
>> If those complications arises, send them to marketing or branding
>> workspaces.
>>
>>
>>
>> >
>> > So it may be possible, going forward, to store logos as SVN revisions
>> > under the same name. But we cannot retroactively do this with
>> > pre-Apache logos. And even if we could, this is harder for users of
>> > the logo to access. It is much easier to have something like
>> > logo-330.svg available via HTTP.
>> >
>>
>> svg are just like HTML files, they are markup languages, we dont hold the
>> index.html inmaculated and hold an apache-index.html and
>> oracle-index.html,
>> so I dont see why SVG should be any different.
>
>
> I don't agree this assessment. The svg files contain branding, or
> trademark sources. These are entities which should not be changed --
> resulting in a trademark violation. If there is something wrong with the
> SVG files for whatever reason, this needs to undergo a justification
> discussion.
>
> The only porpouse of having
>> a source file, is for users to be able to modify it on the first place.
>> Either by integrating to a bigger SVG design, or resizing it for print
>> work.
>>
>
> This part I do agree with. The svg files can be used to produce various
> sizes of the "trademarked" entities. Changing the source of that entity is
> a different matter in my opinion.
>
>
>
>
>
>>
>>
>> >
>> > Of course you can have a hybrid approach:
>> >
>> > 1) When a new logo is introduced, svn copy the old one into a
>> > /old-logos directory with a new descriptive name. This preserves the
>> > version history.
>> >
>>
>> This is not functional and just start acumulating part of the same
>> garbage
>> that svn is supposed to clean up. Again, if this was code, this would be
>> totally unacceptable approach. If new logos are introduced then they
>> should
>> replace the current logo, and the old will live in anals of the svn logs.
>>
>>
>>
>> >
>> > 2) New logo then is checked in as a new revision of logo-master.svg.
>> >
>>
>> People are free to disagree with me, but I think this is a messy way to
>> work, and for a webdev folder is completely useless, specially when there
>> is a whole different project specialized on archiving, developing, and
>> multiplying artwork inside marketing, and a whole different project
>> devoted
>> to specifying the guideliness of the brand (aka logo).
>>
>>
>> > Regards,
>> >
>> > -Rob
>> >
>> >
>> > >
>> > >
>> > >> or something clean like that. However, I have not had any luck
>> > >> getting this logo to load into Inkscape or Adobe Illustrator. I get
>> > >> errors. And I have not had any luck getting Kevin to send a version
>> > >> that will load.
>> > >>
>> > >> So we're stuck right now with a logo that does load into Inkscape,
>> > >> but
>> > >> is slightly different than the one we used in AOO 4.0.
>> > >>
>> > >
>> > >> > At the same time we have old logos which had been untouch. I think
>> the
>> > >> > webdevs have small understanding of a svn is builted so that the
>> files
>> > >> are
>> > >> > updated without having different versions laying arround. Over
>> > >> > this
>> > >> > example, ooo-logo.png and
>> > >> > AOO4_website_logo.png<
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> > >> >exist.
>> > >> >
>> > >> > All these proliferation of logos, usually will built up to become
>> > >> > incredibly messy to work. I suggest to put the information such as
>> > >> author,
>> > >> > version, status, etc. on the comments of the commit and not on the
>> > >> > filename. Likewise to take the time to look for the source of the
>> > image,
>> > >> > since there is an SVG/ folder to link the source of them, and
>> finally
>> > if
>> > >> > there are different images (sizes) to have a common convention.
>> > >> >
>> > >>
>> > >> A more logical naming scheme would be good, I agree. But this has
>> > >> been waiting for resolution of which SVG we should actually be
>> > >> using.
>> > >>
>> > >> Regards,
>> > >>
>> > >> -Rob
>> > >>
>> > >>
>> > >> > If you want to review the images please go here:
>> > >> >
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> > >> >
>> > >> > --
>> > >> > Alexandro Colorado
>> > >> > Apache OpenOffice Contributor
>> > >> > http://www.openoffice.org
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> > >>
>> > >>
>> > >
>> > >
>> > > --
>> > > Alexandro Colorado
>> > > Apache OpenOffice Contributor
>> > > http://www.openoffice.org
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> > For additional commands, e-mail: dev-help@openoffice.apache.org
>> >
>> >
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>
>
>
> --
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> On Tue, Aug 13, 2013 at 12:51 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>
>> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
>> > On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> >
>> >> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>> >>
>> >> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> >> wrote:
>> >> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>> wrote:
>> >> > >
>> >> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado
>> >> > >> <jza@oooes.org
>> >
>> >> > wrote:
>> >> > >> > I think the image structure on the website is a bit messy,
>> >> > >> > there
>> >> > >> > has
>> >> > been
>> >> > >> > some cleanup done by kschenk but I think there is still a lot
>> >> > >> > of
>> >> > clean up
>> >> > >> > work to be done.
>> >> > >> >
>> >> > >> > For example, the new logo, was simply draged and drop to the
>> >> AOOLogos
>> >> > >> > folder with a huge name. I understand the name was needed to
>> >> identify
>> >> > it
>> >> > >> > between the rest of the competitive logos. But now that is
>> >> > >> > selected,
>> >> > the
>> >> > >> > current name is unecessary long.
>> >> > >> >
>> >> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >> > >> >
>> >> > >> >
>> >> > >>
>> >> > >> Right. That work is incomplete. I checked it in originally,
>> >> > >> after
>> >> > >> the logo vote, so we could start working on the product
>> >> > >> integration
>> >> > >> immediately. But note that the above logo is not the one we
>> >> > >> actually
>> >> > >> used in AOO 4.0 !!
>> >> > >>
>> >> > >> The one we actually used is this one:
>> >> > >>
>> >> > >>
>> >> > >>
>> >> > >>
>> >> >
>> >>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> >> > >>
>> >> > >> This was Chris R's contest logo with some minor technical
>> >> > >> changes.
>> >> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>> >> > >> which
>> >> > >> I helped check in.
>> >> > >>
>> >> > >> My intent was to take that SVG and rename it to
>> "master-logo-40.svg"
>> >> > >>
>> >> > >
>> >> > > Again I think we do need a convention for a "logo.svg" as opposed
>> >> > > to
>> >> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> >> incrementally
>> >> > > replace with the future logos as we update the SVG.
>> >> > >
>> >> >
>> >> > Here's the complication: The old logos are still relevant some
>> >> > some
>> >> > purposes. For example, the PMC receives ongoing requests to approve
>> >> > use of the old OpenOffice.org logo. Why would that happen? Often
>> >> > it
>> >> > is a request by publishers who are making an e-book version of an
>> >> > older print book. If their original request did not include the
>> >> > e-book rights then they come back to us (and owners of every other
>> >> > image they use) to request additional permissions.
>> >> >
>> >>
>> >> I think that 'complication' is the lesser of two evils., compared to
>> >> having to manage a ever growing ammount of images. And beside that, do
>> >> you
>> >> realize the difference in objectives between ooo-site/images/
>> >> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>> >>
>> >> I dont see any reason why those issues should impact the web works of
>> >> ooo-site/images/. That folder is for website-design related work. It
>> has,
>> >> or shouldnt hold any porpouse to archieve past work, nor to hold
>> >> description of any kind. I think website should be as lean and easy to
>> >> follow since we expect these conventions be followed by a rotating
>> >> community. So again K.I.S.S.
>> >>
>> >
>> > No, it shouldn't. The ooo-site/images areas got the logo added to it
>> simply
>> > because to make it easier to locate it. The other images files there
>> belong
>> > to the home page. The svg sub-directory here is really the mis-placed
>> one.
>>
>> Then there is also no need for multiple versions of the logo either,
>> like is currently loaded including the current long filename.
>>
>> >
>> >
>> >> If those complications arises, send them to marketing or branding
>> >> workspaces.
>> >>
>> >>
>> >>
>> >> >
>> >> > So it may be possible, going forward, to store logos as SVN
>> >> > revisions
>> >> > under the same name. But we cannot retroactively do this with
>> >> > pre-Apache logos. And even if we could, this is harder for users of
>> >> > the logo to access. It is much easier to have something like
>> >> > logo-330.svg available via HTTP.
>> >> >
>> >>
>> >> svg are just like HTML files, they are markup languages, we dont hold
>> the
>> >> index.html inmaculated and hold an apache-index.html and
>> >> oracle-index.html,
>> >> so I dont see why SVG should be any different.
>> >
>> >
>> > I don't agree this assessment. The svg files contain branding, or
>> > trademark sources. These are entities which should not be changed --
>> > resulting in a trademark violation. If there is something wrong with
>> > the
>> > SVG files for whatever reason, this needs to undergo a justification
>> > discussion.
>>
>> If we go by that scenario, every footer, about page also contain
>> trademark information, that shouldnt be modified.
>>
>
> True enough and we generally discuss anything like that before making
> changes.
AFAIK we are doing this right now, and you are already making changes.
>
>
>>
>>
>> >
>> > The only porpouse of having
>> >> a source file, is for users to be able to modify it on the first
>> >> place.
>> >> Either by integrating to a bigger SVG design, or resizing it for print
>> >> work.
>> >>
>> >
>> > This part I do agree with. The svg files can be used to produce various
>> > sizes of the "trademarked" entities. Changing the source of that entity
>> is
>> > a different matter in my opinion.
>> >
>> >
>> >
>> >
>> >
>> >>
>> >>
>> >> >
>> >> > Of course you can have a hybrid approach:
>> >> >
>> >> > 1) When a new logo is introduced, svn copy the old one into a
>> >> > /old-logos directory with a new descriptive name. This preserves
>> >> > the
>> >> > version history.
>> >> >
>> >>
>> >> This is not functional and just start acumulating part of the same
>> >> garbage
>> >> that svn is supposed to clean up. Again, if this was code, this would
>> >> be
>> >> totally unacceptable approach. If new logos are introduced then they
>> >> should
>> >> replace the current logo, and the old will live in anals of the svn
>> logs.
>> >>
>> >>
>> >>
>> >> >
>> >> > 2) New logo then is checked in as a new revision of logo-master.svg.
>> >> >
>> >>
>> >> People are free to disagree with me, but I think this is a messy way
>> >> to
>> >> work, and for a webdev folder is completely useless, specially when
>> there
>> >> is a whole different project specialized on archiving, developing, and
>> >> multiplying artwork inside marketing, and a whole different project
>> >> devoted
>> >> to specifying the guideliness of the brand (aka logo).
>> >>
>> >>
>> >> > Regards,
>> >> >
>> >> > -Rob
>> >> >
>> >> >
>> >> > >
>> >> > >
>> >> > >> or something clean like that. However, I have not had any luck
>> >> > >> getting this logo to load into Inkscape or Adobe Illustrator. I
>> get
>> >> > >> errors. And I have not had any luck getting Kevin to send a
>> version
>> >> > >> that will load.
>> >> > >>
>> >> > >> So we're stuck right now with a logo that does load into
>> >> > >> Inkscape,
>> >> > >> but
>> >> > >> is slightly different than the one we used in AOO 4.0.
>> >> > >>
>> >> > >
>> >> > >> > At the same time we have old logos which had been untouch. I
>> think
>> >> the
>> >> > >> > webdevs have small understanding of a svn is builted so that
>> >> > >> > the
>> >> files
>> >> > >> are
>> >> > >> > updated without having different versions laying arround. Over
>> >> > >> > this
>> >> > >> > example, ooo-logo.png and
>> >> > >> > AOO4_website_logo.png<
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >> > >> >exist.
>> >> > >> >
>> >> > >> > All these proliferation of logos, usually will built up to
>> >> > >> > become
>> >> > >> > incredibly messy to work. I suggest to put the information such
>> as
>> >> > >> author,
>> >> > >> > version, status, etc. on the comments of the commit and not on
>> the
>> >> > >> > filename. Likewise to take the time to look for the source of
>> the
>> >> > image,
>> >> > >> > since there is an SVG/ folder to link the source of them, and
>> >> finally
>> >> > if
>> >> > >> > there are different images (sizes) to have a common convention.
>> >> > >> >
>> >> > >>
>> >> > >> A more logical naming scheme would be good, I agree. But this
>> >> > >> has
>> >> > >> been waiting for resolution of which SVG we should actually be
>> >> > >> using.
>> >> > >>
>> >> > >> Regards,
>> >> > >>
>> >> > >> -Rob
>> >> > >>
>> >> > >>
>> >> > >> > If you want to review the images please go here:
>> >> > >> >
>> >> > >>
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >> > >> >
>> >> > >> > --
>> >> > >> > Alexandro Colorado
>> >> > >> > Apache OpenOffice Contributor
>> >> > >> > http://www.openoffice.org
>> >> > >>
>> >> > >>
>> ---------------------------------------------------------------------
>> >> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >> > >>
>> >> > >>
>> >> > >
>> >> > >
>> >> > > --
>> >> > > Alexandro Colorado
>> >> > > Apache OpenOffice Contributor
>> >> > > http://www.openoffice.org
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> > For additional commands, e-mail: dev-help@openoffice.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >> --
>> >> Alexandro Colorado
>> >> Apache OpenOffice Contributor
>> >> http://www.openoffice.org
>> >>
>> >
>> >
>> >
>> > --
>> >
>> -------------------------------------------------------------------------------------------------
>> > MzK
>> >
>> > Success is falling nine times and getting up ten."
>> > -- Jon Bon Jovi
>> >
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Kay Schenk <ka...@gmail.com>.
On Tue, Aug 13, 2013 at 12:51 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> > On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> >
> >> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
> >>
> >> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> >> wrote:
> >> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
> wrote:
> >> > >
> >> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jza@oooes.org
> >
> >> > wrote:
> >> > >> > I think the image structure on the website is a bit messy, there
> >> > >> > has
> >> > been
> >> > >> > some cleanup done by kschenk but I think there is still a lot of
> >> > clean up
> >> > >> > work to be done.
> >> > >> >
> >> > >> > For example, the new logo, was simply draged and drop to the
> >> AOOLogos
> >> > >> > folder with a huge name. I understand the name was needed to
> >> identify
> >> > it
> >> > >> > between the rest of the competitive logos. But now that is
> >> > >> > selected,
> >> > the
> >> > >> > current name is unecessary long.
> >> > >> >
> >> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> > >> >
> >> > >> >
> >> > >>
> >> > >> Right. That work is incomplete. I checked it in originally, after
> >> > >> the logo vote, so we could start working on the product integration
> >> > >> immediately. But note that the above logo is not the one we
> >> > >> actually
> >> > >> used in AOO 4.0 !!
> >> > >>
> >> > >> The one we actually used is this one:
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> >
> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >> > >>
> >> > >> This was Chris R's contest logo with some minor technical changes.
> >> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
> >> > >> which
> >> > >> I helped check in.
> >> > >>
> >> > >> My intent was to take that SVG and rename it to
> "master-logo-40.svg"
> >> > >>
> >> > >
> >> > > Again I think we do need a convention for a "logo.svg" as opposed to
> >> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >> incrementally
> >> > > replace with the future logos as we update the SVG.
> >> > >
> >> >
> >> > Here's the complication: The old logos are still relevant some some
> >> > purposes. For example, the PMC receives ongoing requests to approve
> >> > use of the old OpenOffice.org logo. Why would that happen? Often it
> >> > is a request by publishers who are making an e-book version of an
> >> > older print book. If their original request did not include the
> >> > e-book rights then they come back to us (and owners of every other
> >> > image they use) to request additional permissions.
> >> >
> >>
> >> I think that 'complication' is the lesser of two evils., compared to
> >> having to manage a ever growing ammount of images. And beside that, do
> >> you
> >> realize the difference in objectives between ooo-site/images/
> >> ooo-site/marketing/art/images/ and ooo-site/branding/images.
> >>
> >> I dont see any reason why those issues should impact the web works of
> >> ooo-site/images/. That folder is for website-design related work. It
> has,
> >> or shouldnt hold any porpouse to archieve past work, nor to hold
> >> description of any kind. I think website should be as lean and easy to
> >> follow since we expect these conventions be followed by a rotating
> >> community. So again K.I.S.S.
> >>
> >
> > No, it shouldn't. The ooo-site/images areas got the logo added to it
> simply
> > because to make it easier to locate it. The other images files there
> belong
> > to the home page. The svg sub-directory here is really the mis-placed
> one.
>
> Then there is also no need for multiple versions of the logo either,
> like is currently loaded including the current long filename.
>
> >
> >
> >> If those complications arises, send them to marketing or branding
> >> workspaces.
> >>
> >>
> >>
> >> >
> >> > So it may be possible, going forward, to store logos as SVN revisions
> >> > under the same name. But we cannot retroactively do this with
> >> > pre-Apache logos. And even if we could, this is harder for users of
> >> > the logo to access. It is much easier to have something like
> >> > logo-330.svg available via HTTP.
> >> >
> >>
> >> svg are just like HTML files, they are markup languages, we dont hold
> the
> >> index.html inmaculated and hold an apache-index.html and
> >> oracle-index.html,
> >> so I dont see why SVG should be any different.
> >
> >
> > I don't agree this assessment. The svg files contain branding, or
> > trademark sources. These are entities which should not be changed --
> > resulting in a trademark violation. If there is something wrong with the
> > SVG files for whatever reason, this needs to undergo a justification
> > discussion.
>
> If we go by that scenario, every footer, about page also contain
> trademark information, that shouldnt be modified.
>
True enough and we generally discuss anything like that before making
changes.
>
>
> >
> > The only porpouse of having
> >> a source file, is for users to be able to modify it on the first place.
> >> Either by integrating to a bigger SVG design, or resizing it for print
> >> work.
> >>
> >
> > This part I do agree with. The svg files can be used to produce various
> > sizes of the "trademarked" entities. Changing the source of that entity
> is
> > a different matter in my opinion.
> >
> >
> >
> >
> >
> >>
> >>
> >> >
> >> > Of course you can have a hybrid approach:
> >> >
> >> > 1) When a new logo is introduced, svn copy the old one into a
> >> > /old-logos directory with a new descriptive name. This preserves the
> >> > version history.
> >> >
> >>
> >> This is not functional and just start acumulating part of the same
> >> garbage
> >> that svn is supposed to clean up. Again, if this was code, this would be
> >> totally unacceptable approach. If new logos are introduced then they
> >> should
> >> replace the current logo, and the old will live in anals of the svn
> logs.
> >>
> >>
> >>
> >> >
> >> > 2) New logo then is checked in as a new revision of logo-master.svg.
> >> >
> >>
> >> People are free to disagree with me, but I think this is a messy way to
> >> work, and for a webdev folder is completely useless, specially when
> there
> >> is a whole different project specialized on archiving, developing, and
> >> multiplying artwork inside marketing, and a whole different project
> >> devoted
> >> to specifying the guideliness of the brand (aka logo).
> >>
> >>
> >> > Regards,
> >> >
> >> > -Rob
> >> >
> >> >
> >> > >
> >> > >
> >> > >> or something clean like that. However, I have not had any luck
> >> > >> getting this logo to load into Inkscape or Adobe Illustrator. I
> get
> >> > >> errors. And I have not had any luck getting Kevin to send a
> version
> >> > >> that will load.
> >> > >>
> >> > >> So we're stuck right now with a logo that does load into Inkscape,
> >> > >> but
> >> > >> is slightly different than the one we used in AOO 4.0.
> >> > >>
> >> > >
> >> > >> > At the same time we have old logos which had been untouch. I
> think
> >> the
> >> > >> > webdevs have small understanding of a svn is builted so that the
> >> files
> >> > >> are
> >> > >> > updated without having different versions laying arround. Over
> >> > >> > this
> >> > >> > example, ooo-logo.png and
> >> > >> > AOO4_website_logo.png<
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> > >> >exist.
> >> > >> >
> >> > >> > All these proliferation of logos, usually will built up to become
> >> > >> > incredibly messy to work. I suggest to put the information such
> as
> >> > >> author,
> >> > >> > version, status, etc. on the comments of the commit and not on
> the
> >> > >> > filename. Likewise to take the time to look for the source of
> the
> >> > image,
> >> > >> > since there is an SVG/ folder to link the source of them, and
> >> finally
> >> > if
> >> > >> > there are different images (sizes) to have a common convention.
> >> > >> >
> >> > >>
> >> > >> A more logical naming scheme would be good, I agree. But this has
> >> > >> been waiting for resolution of which SVG we should actually be
> >> > >> using.
> >> > >>
> >> > >> Regards,
> >> > >>
> >> > >> -Rob
> >> > >>
> >> > >>
> >> > >> > If you want to review the images please go here:
> >> > >> >
> >> > >>
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> > >> >
> >> > >> > --
> >> > >> > Alexandro Colorado
> >> > >> > Apache OpenOffice Contributor
> >> > >> > http://www.openoffice.org
> >> > >>
> >> > >>
> ---------------------------------------------------------------------
> >> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> > > --
> >> > > Alexandro Colorado
> >> > > Apache OpenOffice Contributor
> >> > > http://www.openoffice.org
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >> >
> >> >
> >>
> >>
> >> --
> >> Alexandro Colorado
> >> Apache OpenOffice Contributor
> >> http://www.openoffice.org
> >>
> >
> >
> >
> > --
> >
> -------------------------------------------------------------------------------------------------
> > MzK
> >
> > Success is falling nine times and getting up ten."
> > -- Jon Bon Jovi
> >
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
-------------------------------------------------------------------------------------------------
MzK
Success is falling nine times and getting up ten."
-- Jon Bon Jovi
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>
>> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>>
>> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
>> > >
>> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
>> > wrote:
>> > >> > I think the image structure on the website is a bit messy, there
>> > >> > has
>> > been
>> > >> > some cleanup done by kschenk but I think there is still a lot of
>> > clean up
>> > >> > work to be done.
>> > >> >
>> > >> > For example, the new logo, was simply draged and drop to the
>> AOOLogos
>> > >> > folder with a huge name. I understand the name was needed to
>> identify
>> > it
>> > >> > between the rest of the competitive logos. But now that is
>> > >> > selected,
>> > the
>> > >> > current name is unecessary long.
>> > >> >
>> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> > >> >
>> > >> >
>> > >>
>> > >> Right. That work is incomplete. I checked it in originally, after
>> > >> the logo vote, so we could start working on the product integration
>> > >> immediately. But note that the above logo is not the one we
>> > >> actually
>> > >> used in AOO 4.0 !!
>> > >>
>> > >> The one we actually used is this one:
>> > >>
>> > >>
>> > >>
>> > >>
>> >
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> > >>
>> > >> This was Chris R's contest logo with some minor technical changes.
>> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>> > >> which
>> > >> I helped check in.
>> > >>
>> > >> My intent was to take that SVG and rename it to "master-logo-40.svg"
>> > >>
>> > >
>> > > Again I think we do need a convention for a "logo.svg" as opposed to
>> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> incrementally
>> > > replace with the future logos as we update the SVG.
>> > >
>> >
>> > Here's the complication: The old logos are still relevant some some
>> > purposes. For example, the PMC receives ongoing requests to approve
>> > use of the old OpenOffice.org logo. Why would that happen? Often it
>> > is a request by publishers who are making an e-book version of an
>> > older print book. If their original request did not include the
>> > e-book rights then they come back to us (and owners of every other
>> > image they use) to request additional permissions.
>> >
>>
>> I think that 'complication' is the lesser of two evils., compared to
>> having to manage a ever growing ammount of images. And beside that, do
>> you
>> realize the difference in objectives between ooo-site/images/
>> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>>
>> I dont see any reason why those issues should impact the web works of
>> ooo-site/images/. That folder is for website-design related work. It has,
>> or shouldnt hold any porpouse to archieve past work, nor to hold
>> description of any kind. I think website should be as lean and easy to
>> follow since we expect these conventions be followed by a rotating
>> community. So again K.I.S.S.
>>
>
> No, it shouldn't. The ooo-site/images areas got the logo added to it simply
> because to make it easier to locate it. The other images files there belong
> to the home page. The svg sub-directory here is really the mis-placed one.
Then there is also no need for multiple versions of the logo either,
like is currently loaded including the current long filename.
>
>
>> If those complications arises, send them to marketing or branding
>> workspaces.
>>
>>
>>
>> >
>> > So it may be possible, going forward, to store logos as SVN revisions
>> > under the same name. But we cannot retroactively do this with
>> > pre-Apache logos. And even if we could, this is harder for users of
>> > the logo to access. It is much easier to have something like
>> > logo-330.svg available via HTTP.
>> >
>>
>> svg are just like HTML files, they are markup languages, we dont hold the
>> index.html inmaculated and hold an apache-index.html and
>> oracle-index.html,
>> so I dont see why SVG should be any different.
>
>
> I don't agree this assessment. The svg files contain branding, or
> trademark sources. These are entities which should not be changed --
> resulting in a trademark violation. If there is something wrong with the
> SVG files for whatever reason, this needs to undergo a justification
> discussion.
If we go by that scenario, every footer, about page also contain
trademark information, that shouldnt be modified.
>
> The only porpouse of having
>> a source file, is for users to be able to modify it on the first place.
>> Either by integrating to a bigger SVG design, or resizing it for print
>> work.
>>
>
> This part I do agree with. The svg files can be used to produce various
> sizes of the "trademarked" entities. Changing the source of that entity is
> a different matter in my opinion.
>
>
>
>
>
>>
>>
>> >
>> > Of course you can have a hybrid approach:
>> >
>> > 1) When a new logo is introduced, svn copy the old one into a
>> > /old-logos directory with a new descriptive name. This preserves the
>> > version history.
>> >
>>
>> This is not functional and just start acumulating part of the same
>> garbage
>> that svn is supposed to clean up. Again, if this was code, this would be
>> totally unacceptable approach. If new logos are introduced then they
>> should
>> replace the current logo, and the old will live in anals of the svn logs.
>>
>>
>>
>> >
>> > 2) New logo then is checked in as a new revision of logo-master.svg.
>> >
>>
>> People are free to disagree with me, but I think this is a messy way to
>> work, and for a webdev folder is completely useless, specially when there
>> is a whole different project specialized on archiving, developing, and
>> multiplying artwork inside marketing, and a whole different project
>> devoted
>> to specifying the guideliness of the brand (aka logo).
>>
>>
>> > Regards,
>> >
>> > -Rob
>> >
>> >
>> > >
>> > >
>> > >> or something clean like that. However, I have not had any luck
>> > >> getting this logo to load into Inkscape or Adobe Illustrator. I get
>> > >> errors. And I have not had any luck getting Kevin to send a version
>> > >> that will load.
>> > >>
>> > >> So we're stuck right now with a logo that does load into Inkscape,
>> > >> but
>> > >> is slightly different than the one we used in AOO 4.0.
>> > >>
>> > >
>> > >> > At the same time we have old logos which had been untouch. I think
>> the
>> > >> > webdevs have small understanding of a svn is builted so that the
>> files
>> > >> are
>> > >> > updated without having different versions laying arround. Over
>> > >> > this
>> > >> > example, ooo-logo.png and
>> > >> > AOO4_website_logo.png<
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> > >> >exist.
>> > >> >
>> > >> > All these proliferation of logos, usually will built up to become
>> > >> > incredibly messy to work. I suggest to put the information such as
>> > >> author,
>> > >> > version, status, etc. on the comments of the commit and not on the
>> > >> > filename. Likewise to take the time to look for the source of the
>> > image,
>> > >> > since there is an SVG/ folder to link the source of them, and
>> finally
>> > if
>> > >> > there are different images (sizes) to have a common convention.
>> > >> >
>> > >>
>> > >> A more logical naming scheme would be good, I agree. But this has
>> > >> been waiting for resolution of which SVG we should actually be
>> > >> using.
>> > >>
>> > >> Regards,
>> > >>
>> > >> -Rob
>> > >>
>> > >>
>> > >> > If you want to review the images please go here:
>> > >> >
>> > >>
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> > >> >
>> > >> > --
>> > >> > Alexandro Colorado
>> > >> > Apache OpenOffice Contributor
>> > >> > http://www.openoffice.org
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> > >>
>> > >>
>> > >
>> > >
>> > > --
>> > > Alexandro Colorado
>> > > Apache OpenOffice Contributor
>> > > http://www.openoffice.org
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> > For additional commands, e-mail: dev-help@openoffice.apache.org
>> >
>> >
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>
>
>
> --
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Kay Schenk <ka...@gmail.com>.
On Tue, Aug 13, 2013 at 2:04 AM, Alexandro Colorado <jz...@oooes.org> wrote:
> On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
>
> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> > >
> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> > wrote:
> > >> > I think the image structure on the website is a bit messy, there has
> > been
> > >> > some cleanup done by kschenk but I think there is still a lot of
> > clean up
> > >> > work to be done.
> > >> >
> > >> > For example, the new logo, was simply draged and drop to the
> AOOLogos
> > >> > folder with a huge name. I understand the name was needed to
> identify
> > it
> > >> > between the rest of the competitive logos. But now that is selected,
> > the
> > >> > current name is unecessary long.
> > >> >
> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> > >> >
> > >> >
> > >>
> > >> Right. That work is incomplete. I checked it in originally, after
> > >> the logo vote, so we could start working on the product integration
> > >> immediately. But note that the above logo is not the one we actually
> > >> used in AOO 4.0 !!
> > >>
> > >> The one we actually used is this one:
> > >>
> > >>
> > >>
> > >>
> >
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> > >>
> > >> This was Chris R's contest logo with some minor technical changes.
> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> > >> I helped check in.
> > >>
> > >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> > >>
> > >
> > > Again I think we do need a convention for a "logo.svg" as opposed to
> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> incrementally
> > > replace with the future logos as we update the SVG.
> > >
> >
> > Here's the complication: The old logos are still relevant some some
> > purposes. For example, the PMC receives ongoing requests to approve
> > use of the old OpenOffice.org logo. Why would that happen? Often it
> > is a request by publishers who are making an e-book version of an
> > older print book. If their original request did not include the
> > e-book rights then they come back to us (and owners of every other
> > image they use) to request additional permissions.
> >
>
> I think that 'complication' is the lesser of two evils., compared to
> having to manage a ever growing ammount of images. And beside that, do you
> realize the difference in objectives between ooo-site/images/
> ooo-site/marketing/art/images/ and ooo-site/branding/images.
>
> I dont see any reason why those issues should impact the web works of
> ooo-site/images/. That folder is for website-design related work. It has,
> or shouldnt hold any porpouse to archieve past work, nor to hold
> description of any kind. I think website should be as lean and easy to
> follow since we expect these conventions be followed by a rotating
> community. So again K.I.S.S.
>
No, it shouldn't. The ooo-site/images areas got the logo added to it simply
because to make it easier to locate it. The other images files there belong
to the home page. The svg sub-directory here is really the mis-placed one.
> If those complications arises, send them to marketing or branding
> workspaces.
>
>
>
> >
> > So it may be possible, going forward, to store logos as SVN revisions
> > under the same name. But we cannot retroactively do this with
> > pre-Apache logos. And even if we could, this is harder for users of
> > the logo to access. It is much easier to have something like
> > logo-330.svg available via HTTP.
> >
>
> svg are just like HTML files, they are markup languages, we dont hold the
> index.html inmaculated and hold an apache-index.html and oracle-index.html,
> so I dont see why SVG should be any different.
I don't agree this assessment. The svg files contain branding, or
trademark sources. These are entities which should not be changed --
resulting in a trademark violation. If there is something wrong with the
SVG files for whatever reason, this needs to undergo a justification
discussion.
The only porpouse of having
> a source file, is for users to be able to modify it on the first place.
> Either by integrating to a bigger SVG design, or resizing it for print
> work.
>
This part I do agree with. The svg files can be used to produce various
sizes of the "trademarked" entities. Changing the source of that entity is
a different matter in my opinion.
>
>
> >
> > Of course you can have a hybrid approach:
> >
> > 1) When a new logo is introduced, svn copy the old one into a
> > /old-logos directory with a new descriptive name. This preserves the
> > version history.
> >
>
> This is not functional and just start acumulating part of the same garbage
> that svn is supposed to clean up. Again, if this was code, this would be
> totally unacceptable approach. If new logos are introduced then they should
> replace the current logo, and the old will live in anals of the svn logs.
>
>
>
> >
> > 2) New logo then is checked in as a new revision of logo-master.svg.
> >
>
> People are free to disagree with me, but I think this is a messy way to
> work, and for a webdev folder is completely useless, specially when there
> is a whole different project specialized on archiving, developing, and
> multiplying artwork inside marketing, and a whole different project devoted
> to specifying the guideliness of the brand (aka logo).
>
>
> > Regards,
> >
> > -Rob
> >
> >
> > >
> > >
> > >> or something clean like that. However, I have not had any luck
> > >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> > >> errors. And I have not had any luck getting Kevin to send a version
> > >> that will load.
> > >>
> > >> So we're stuck right now with a logo that does load into Inkscape, but
> > >> is slightly different than the one we used in AOO 4.0.
> > >>
> > >
> > >> > At the same time we have old logos which had been untouch. I think
> the
> > >> > webdevs have small understanding of a svn is builted so that the
> files
> > >> are
> > >> > updated without having different versions laying arround. Over this
> > >> > example, ooo-logo.png and
> > >> > AOO4_website_logo.png<
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> > >> >exist.
> > >> >
> > >> > All these proliferation of logos, usually will built up to become
> > >> > incredibly messy to work. I suggest to put the information such as
> > >> author,
> > >> > version, status, etc. on the comments of the commit and not on the
> > >> > filename. Likewise to take the time to look for the source of the
> > image,
> > >> > since there is an SVG/ folder to link the source of them, and
> finally
> > if
> > >> > there are different images (sizes) to have a common convention.
> > >> >
> > >>
> > >> A more logical naming scheme would be good, I agree. But this has
> > >> been waiting for resolution of which SVG we should actually be using.
> > >>
> > >> Regards,
> > >>
> > >> -Rob
> > >>
> > >>
> > >> > If you want to review the images please go here:
> > >> >
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> > >> >
> > >> > --
> > >> > Alexandro Colorado
> > >> > Apache OpenOffice Contributor
> > >> > http://www.openoffice.org
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Alexandro Colorado
> > > Apache OpenOffice Contributor
> > > http://www.openoffice.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
--
-------------------------------------------------------------------------------------------------
MzK
Success is falling nine times and getting up ten."
-- Jon Bon Jovi
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Mon, Aug 12, 2013 at 8:25 AM, Rob Weir <ro...@apache.org> wrote:
> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> >> > I think the image structure on the website is a bit messy, there has
> been
> >> > some cleanup done by kschenk but I think there is still a lot of
> clean up
> >> > work to be done.
> >> >
> >> > For example, the new logo, was simply draged and drop to the AOOLogos
> >> > folder with a huge name. I understand the name was needed to identify
> it
> >> > between the rest of the competitive logos. But now that is selected,
> the
> >> > current name is unecessary long.
> >> >
> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> >
> >> >
> >>
> >> Right. That work is incomplete. I checked it in originally, after
> >> the logo vote, so we could start working on the product integration
> >> immediately. But note that the above logo is not the one we actually
> >> used in AOO 4.0 !!
> >>
> >> The one we actually used is this one:
> >>
> >>
> >>
> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>
> >> This was Chris R's contest logo with some minor technical changes.
> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> >> I helped check in.
> >>
> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> >>
> >
> > Again I think we do need a convention for a "logo.svg" as opposed to
> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
> > replace with the future logos as we update the SVG.
> >
>
> Here's the complication: The old logos are still relevant some some
> purposes. For example, the PMC receives ongoing requests to approve
> use of the old OpenOffice.org logo. Why would that happen? Often it
> is a request by publishers who are making an e-book version of an
> older print book. If their original request did not include the
> e-book rights then they come back to us (and owners of every other
> image they use) to request additional permissions.
>
I think that 'complication' is the lesser of two evils., compared to
having to manage a ever growing ammount of images. And beside that, do you
realize the difference in objectives between ooo-site/images/
ooo-site/marketing/art/images/ and ooo-site/branding/images.
I dont see any reason why those issues should impact the web works of
ooo-site/images/. That folder is for website-design related work. It has,
or shouldnt hold any porpouse to archieve past work, nor to hold
description of any kind. I think website should be as lean and easy to
follow since we expect these conventions be followed by a rotating
community. So again K.I.S.S.
If those complications arises, send them to marketing or branding
workspaces.
>
> So it may be possible, going forward, to store logos as SVN revisions
> under the same name. But we cannot retroactively do this with
> pre-Apache logos. And even if we could, this is harder for users of
> the logo to access. It is much easier to have something like
> logo-330.svg available via HTTP.
>
svg are just like HTML files, they are markup languages, we dont hold the
index.html inmaculated and hold an apache-index.html and oracle-index.html,
so I dont see why SVG should be any different. The only porpouse of having
a source file, is for users to be able to modify it on the first place.
Either by integrating to a bigger SVG design, or resizing it for print
work.
>
> Of course you can have a hybrid approach:
>
> 1) When a new logo is introduced, svn copy the old one into a
> /old-logos directory with a new descriptive name. This preserves the
> version history.
>
This is not functional and just start acumulating part of the same garbage
that svn is supposed to clean up. Again, if this was code, this would be
totally unacceptable approach. If new logos are introduced then they should
replace the current logo, and the old will live in anals of the svn logs.
>
> 2) New logo then is checked in as a new revision of logo-master.svg.
>
People are free to disagree with me, but I think this is a messy way to
work, and for a webdev folder is completely useless, specially when there
is a whole different project specialized on archiving, developing, and
multiplying artwork inside marketing, and a whole different project devoted
to specifying the guideliness of the brand (aka logo).
> Regards,
>
> -Rob
>
>
> >
> >
> >> or something clean like that. However, I have not had any luck
> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> >> errors. And I have not had any luck getting Kevin to send a version
> >> that will load.
> >>
> >> So we're stuck right now with a logo that does load into Inkscape, but
> >> is slightly different than the one we used in AOO 4.0.
> >>
> >
> >> > At the same time we have old logos which had been untouch. I think the
> >> > webdevs have small understanding of a svn is builted so that the files
> >> are
> >> > updated without having different versions laying arround. Over this
> >> > example, ooo-logo.png and
> >> > AOO4_website_logo.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> >exist.
> >> >
> >> > All these proliferation of logos, usually will built up to become
> >> > incredibly messy to work. I suggest to put the information such as
> >> author,
> >> > version, status, etc. on the comments of the commit and not on the
> >> > filename. Likewise to take the time to look for the source of the
> image,
> >> > since there is an SVG/ folder to link the source of them, and finally
> if
> >> > there are different images (sizes) to have a common convention.
> >> >
> >>
> >> A more logical naming scheme would be good, I agree. But this has
> >> been waiting for resolution of which SVG we should actually be using.
> >>
> >> Regards,
> >>
> >> -Rob
> >>
> >>
> >> > If you want to review the images please go here:
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> >
> >> > --
> >> > Alexandro Colorado
> >> > Apache OpenOffice Contributor
> >> > http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/13/13, Kay Schenk <ka...@gmail.com> wrote:
> On Tue, Aug 13, 2013 at 1:29 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>
>> On 8/12/13, Kay Schenk <ka...@gmail.com> wrote:
>> > On Mon, Aug 12, 2013 at 6:25 AM, Rob Weir <ro...@apache.org> wrote:
>> >
>> >> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> >> wrote:
>> >> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org>
>> >> > wrote:
>> >> >
>> >> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
>> >> wrote:
>> >> >> > I think the image structure on the website is a bit messy, there
>> has
>> >> been
>> >> >> > some cleanup done by kschenk but I think there is still a lot of
>> >> clean up
>> >> >> > work to be done.
>> >> >> >
>> >> >> > For example, the new logo, was simply draged and drop to the
>> >> >> > AOOLogos
>> >> >> > folder with a huge name. I understand the name was needed to
>> >> >> > identify
>> >> it
>> >> >> > between the rest of the competitive logos. But now that is
>> selected,
>> >> the
>> >> >> > current name is unecessary long.
>> >> >> >
>> >> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> >> >>
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> Right. That work is incomplete. I checked it in originally, after
>> >> >> the logo vote, so we could start working on the product integration
>> >> >> immediately. But note that the above logo is not the one we
>> >> >> actually
>> >> >> used in AOO 4.0 !!
>> >> >>
>> >> >> The one we actually used is this one:
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> >> >>
>> >> >> This was Chris R's contest logo with some minor technical changes.
>> >> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0,
>> >> >> which
>> >> >> I helped check in.
>> >> >>
>> >> >> My intent was to take that SVG and rename it to
>> >> >> "master-logo-40.svg"
>> >> >>
>> >> >
>> >> > Again I think we do need a convention for a "logo.svg" as opposed to
>> >> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> >> > incrementally
>> >> > replace with the future logos as we update the SVG.
>> >> >
>> >>
>> >> Here's the complication: The old logos are still relevant some some
>> >> purposes. For example, the PMC receives ongoing requests to approve
>> >> use of the old OpenOffice.org logo. Why would that happen? Often it
>> >> is a request by publishers who are making an e-book version of an
>> >> older print book. If their original request did not include the
>> >> e-book rights then they come back to us (and owners of every other
>> >> image they use) to request additional permissions.
>> >>
>> >> So it may be possible, going forward, to store logos as SVN revisions
>> >> under the same name. But we cannot retroactively do this with
>> >> pre-Apache logos. And even if we could, this is harder for users of
>> >> the logo to access. It is much easier to have something like
>> >> logo-330.svg available via HTTP.
>> >>
>> >> Of course you can have a hybrid approach:
>> >>
>> >> 1) When a new logo is introduced, svn copy the old one into a
>> >> /old-logos directory with a new descriptive name. This preserves the
>> >> version history.
>> >>
>> >> 2) New logo then is checked in as a new revision of logo-master.svg.
>> >>
>> >
>> > I like this idea or something akin to it. We should definitely preserve
>> > svgs for old logos in my opinion. The new "branding" repository can be
>>
>> Why are you multiplicating image repositories, where Art already has
>> one with the whole image structure clasified and versioned?
>>
>
> I'm putting the sources into the "branding source" area, We had already
> discussed this. Soon we will probably discuss deleting them *from* the
> marketing/art area. The biggest problem right now is actually FINDING all
> these.
Like I mentioned before, branding is not a place to store images, is
the analog of building a warehouse in your lawyer office. Branding was
builted for documenting the specs of the logo. Certainly no need for
long filenames, nor useless conventions like 'selected' referencing a
marketing contest.
>
> For now, there will be some duplications.
>
No need for that if we follow the convention already in place.
> Apache OpenOffice does not have the same structure as the old
Why not? There is already a body of work builted that has been proved
with a filename convention and is easy to identify the artwork, logo
and other type of work.
> OpenOffice.org with defined project areas, project area leaders, project
> area committers etc. So setting up the separate branding area was
> discussed and these files are now being put there.
I am not sure branding is a right place to put and hold the artwork,
this just create unnecesary "triplication" with 'web', 'marketing/art'
and NOW 'branding'.
>
>>
>> > used for this, and given some additional structure. I'm also finding
>> some
>> > svg masters for items that are not really logos, like "Get It Here",
>> > that
>> > probably need to be moved to "branding" even though they are not really
>> > logos.
>> >
>> > And, because there are quite a few sites using old logo versions, I
>> > don't
>> > really think we should track them all down and require them to upgrade.
>> >
>> > Again, I am only referring to svg for these. Renderings, png files, as
>> far
>> > as I'm concerned, can be renamed and kept anywhere. The new logo used
>> > on
>> > the website now, for example, is not a drop in replacement for the old
>> > one, because the size is slightly larger due to design considerations.
>> So,
>> > it's conceivable, depending on use, the even within the Apache
>> > OpenOffice
>> > site, etc., different renderings might be used. But maybe this is in
>> > opposition to what marketing folks mean by a "logo" with a specific
>> > size,
>> > etc., I don't know.
>> >
>> >
>> >
>> >> Regards,
>> >>
>> >> -Rob
>> >>
>> >>
>> >> >
>> >> >
>> >> >> or something clean like that. However, I have not had any luck
>> >> >> getting this logo to load into Inkscape or Adobe Illustrator. I
>> >> >> get
>> >> >> errors. And I have not had any luck getting Kevin to send a
>> >> >> version
>> >> >> that will load.
>> >> >>
>> >> >> So we're stuck right now with a logo that does load into Inkscape,
>> but
>> >> >> is slightly different than the one we used in AOO 4.0.
>> >> >>
>> >> >
>> >> >> > At the same time we have old logos which had been untouch. I
>> >> >> > think
>> >> >> > the
>> >> >> > webdevs have small understanding of a svn is builted so that the
>> >> >> > files
>> >> >> are
>> >> >> > updated without having different versions laying arround. Over
>> >> >> > this
>> >> >> > example, ooo-logo.png and
>> >> >> > AOO4_website_logo.png<
>> >> >>
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >> >> >exist.
>> >> >> >
>> >> >> > All these proliferation of logos, usually will built up to become
>> >> >> > incredibly messy to work. I suggest to put the information such
>> >> >> > as
>> >> >> author,
>> >> >> > version, status, etc. on the comments of the commit and not on
>> >> >> > the
>> >> >> > filename. Likewise to take the time to look for the source of
>> >> >> > the
>> >> image,
>> >> >> > since there is an SVG/ folder to link the source of them, and
>> >> >> > finally
>> >> if
>> >> >> > there are different images (sizes) to have a common convention.
>> >> >> >
>> >> >>
>> >> >> A more logical naming scheme would be good, I agree. But this has
>> >> >> been waiting for resolution of which SVG we should actually be
>> >> >> using.
>> >> >>
>> >> >> Regards,
>> >> >>
>> >> >> -Rob
>> >> >>
>> >> >>
>> >> >> > If you want to review the images please go here:
>> >> >> >
>> >> >>
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >> >> >
>> >> >> > --
>> >> >> > Alexandro Colorado
>> >> >> > Apache OpenOffice Contributor
>> >> >> > http://www.openoffice.org
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Alexandro Colorado
>> >> > Apache OpenOffice Contributor
>> >> > http://www.openoffice.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> >
>> -------------------------------------------------------------------------------------------------
>> > MzK
>> >
>> > Success is falling nine times and getting up ten."
>> > -- Jon Bon Jovi
>> >
>>
>>
>> --
>> Alexandro Colorado
>> Apache OpenOffice Contributor
>> http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Kay Schenk <ka...@gmail.com>.
On Tue, Aug 13, 2013 at 1:29 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> On 8/12/13, Kay Schenk <ka...@gmail.com> wrote:
> > On Mon, Aug 12, 2013 at 6:25 AM, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> >> wrote:
> >> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> >> >
> >> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> >> wrote:
> >> >> > I think the image structure on the website is a bit messy, there
> has
> >> been
> >> >> > some cleanup done by kschenk but I think there is still a lot of
> >> clean up
> >> >> > work to be done.
> >> >> >
> >> >> > For example, the new logo, was simply draged and drop to the
> >> >> > AOOLogos
> >> >> > folder with a huge name. I understand the name was needed to
> >> >> > identify
> >> it
> >> >> > between the rest of the competitive logos. But now that is
> selected,
> >> the
> >> >> > current name is unecessary long.
> >> >> >
> >> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >> >>
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> >> >
> >> >> >
> >> >>
> >> >> Right. That work is incomplete. I checked it in originally, after
> >> >> the logo vote, so we could start working on the product integration
> >> >> immediately. But note that the above logo is not the one we actually
> >> >> used in AOO 4.0 !!
> >> >>
> >> >> The one we actually used is this one:
> >> >>
> >> >>
> >> >>
> >> >>
> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >> >>
> >> >> This was Chris R's contest logo with some minor technical changes.
> >> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> >> >> I helped check in.
> >> >>
> >> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> >> >>
> >> >
> >> > Again I think we do need a convention for a "logo.svg" as opposed to
> >> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> >> > incrementally
> >> > replace with the future logos as we update the SVG.
> >> >
> >>
> >> Here's the complication: The old logos are still relevant some some
> >> purposes. For example, the PMC receives ongoing requests to approve
> >> use of the old OpenOffice.org logo. Why would that happen? Often it
> >> is a request by publishers who are making an e-book version of an
> >> older print book. If their original request did not include the
> >> e-book rights then they come back to us (and owners of every other
> >> image they use) to request additional permissions.
> >>
> >> So it may be possible, going forward, to store logos as SVN revisions
> >> under the same name. But we cannot retroactively do this with
> >> pre-Apache logos. And even if we could, this is harder for users of
> >> the logo to access. It is much easier to have something like
> >> logo-330.svg available via HTTP.
> >>
> >> Of course you can have a hybrid approach:
> >>
> >> 1) When a new logo is introduced, svn copy the old one into a
> >> /old-logos directory with a new descriptive name. This preserves the
> >> version history.
> >>
> >> 2) New logo then is checked in as a new revision of logo-master.svg.
> >>
> >
> > I like this idea or something akin to it. We should definitely preserve
> > svgs for old logos in my opinion. The new "branding" repository can be
>
> Why are you multiplicating image repositories, where Art already has
> one with the whole image structure clasified and versioned?
>
I'm putting the sources into the "branding source" area, We had already
discussed this. Soon we will probably discuss deleting them *from* the
marketing/art area. The biggest problem right now is actually FINDING all
these.
For now, there will be some duplications.
Apache OpenOffice does not have the same structure as the old
OpenOffice.org with defined project areas, project area leaders, project
area committers etc. So setting up the separate branding area was
discussed and these files are now being put there.
>
> > used for this, and given some additional structure. I'm also finding
> some
> > svg masters for items that are not really logos, like "Get It Here", that
> > probably need to be moved to "branding" even though they are not really
> > logos.
> >
> > And, because there are quite a few sites using old logo versions, I don't
> > really think we should track them all down and require them to upgrade.
> >
> > Again, I am only referring to svg for these. Renderings, png files, as
> far
> > as I'm concerned, can be renamed and kept anywhere. The new logo used on
> > the website now, for example, is not a drop in replacement for the old
> > one, because the size is slightly larger due to design considerations.
> So,
> > it's conceivable, depending on use, the even within the Apache OpenOffice
> > site, etc., different renderings might be used. But maybe this is in
> > opposition to what marketing folks mean by a "logo" with a specific size,
> > etc., I don't know.
> >
> >
> >
> >> Regards,
> >>
> >> -Rob
> >>
> >>
> >> >
> >> >
> >> >> or something clean like that. However, I have not had any luck
> >> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> >> >> errors. And I have not had any luck getting Kevin to send a version
> >> >> that will load.
> >> >>
> >> >> So we're stuck right now with a logo that does load into Inkscape,
> but
> >> >> is slightly different than the one we used in AOO 4.0.
> >> >>
> >> >
> >> >> > At the same time we have old logos which had been untouch. I think
> >> >> > the
> >> >> > webdevs have small understanding of a svn is builted so that the
> >> >> > files
> >> >> are
> >> >> > updated without having different versions laying arround. Over this
> >> >> > example, ooo-logo.png and
> >> >> > AOO4_website_logo.png<
> >> >>
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> >> >exist.
> >> >> >
> >> >> > All these proliferation of logos, usually will built up to become
> >> >> > incredibly messy to work. I suggest to put the information such as
> >> >> author,
> >> >> > version, status, etc. on the comments of the commit and not on the
> >> >> > filename. Likewise to take the time to look for the source of the
> >> image,
> >> >> > since there is an SVG/ folder to link the source of them, and
> >> >> > finally
> >> if
> >> >> > there are different images (sizes) to have a common convention.
> >> >> >
> >> >>
> >> >> A more logical naming scheme would be good, I agree. But this has
> >> >> been waiting for resolution of which SVG we should actually be using.
> >> >>
> >> >> Regards,
> >> >>
> >> >> -Rob
> >> >>
> >> >>
> >> >> > If you want to review the images please go here:
> >> >> >
> >> >>
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> >> >
> >> >> > --
> >> >> > Alexandro Colorado
> >> >> > Apache OpenOffice Contributor
> >> >> > http://www.openoffice.org
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Alexandro Colorado
> >> > Apache OpenOffice Contributor
> >> > http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> >
> -------------------------------------------------------------------------------------------------
> > MzK
> >
> > Success is falling nine times and getting up ten."
> > -- Jon Bon Jovi
> >
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
-------------------------------------------------------------------------------------------------
MzK
Success is falling nine times and getting up ten."
-- Jon Bon Jovi
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On 8/12/13, Kay Schenk <ka...@gmail.com> wrote:
> On Mon, Aug 12, 2013 at 6:25 AM, Rob Weir <ro...@apache.org> wrote:
>
>> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
>> >
>> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
>> wrote:
>> >> > I think the image structure on the website is a bit messy, there has
>> been
>> >> > some cleanup done by kschenk but I think there is still a lot of
>> clean up
>> >> > work to be done.
>> >> >
>> >> > For example, the new logo, was simply draged and drop to the
>> >> > AOOLogos
>> >> > folder with a huge name. I understand the name was needed to
>> >> > identify
>> it
>> >> > between the rest of the competitive logos. But now that is selected,
>> the
>> >> > current name is unecessary long.
>> >> >
>> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >> >
>> >> >
>> >>
>> >> Right. That work is incomplete. I checked it in originally, after
>> >> the logo vote, so we could start working on the product integration
>> >> immediately. But note that the above logo is not the one we actually
>> >> used in AOO 4.0 !!
>> >>
>> >> The one we actually used is this one:
>> >>
>> >>
>> >>
>> >>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>> >>
>> >> This was Chris R's contest logo with some minor technical changes.
>> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
>> >> I helped check in.
>> >>
>> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
>> >>
>> >
>> > Again I think we do need a convention for a "logo.svg" as opposed to
>> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
>> > incrementally
>> > replace with the future logos as we update the SVG.
>> >
>>
>> Here's the complication: The old logos are still relevant some some
>> purposes. For example, the PMC receives ongoing requests to approve
>> use of the old OpenOffice.org logo. Why would that happen? Often it
>> is a request by publishers who are making an e-book version of an
>> older print book. If their original request did not include the
>> e-book rights then they come back to us (and owners of every other
>> image they use) to request additional permissions.
>>
>> So it may be possible, going forward, to store logos as SVN revisions
>> under the same name. But we cannot retroactively do this with
>> pre-Apache logos. And even if we could, this is harder for users of
>> the logo to access. It is much easier to have something like
>> logo-330.svg available via HTTP.
>>
>> Of course you can have a hybrid approach:
>>
>> 1) When a new logo is introduced, svn copy the old one into a
>> /old-logos directory with a new descriptive name. This preserves the
>> version history.
>>
>> 2) New logo then is checked in as a new revision of logo-master.svg.
>>
>
> I like this idea or something akin to it. We should definitely preserve
> svgs for old logos in my opinion. The new "branding" repository can be
Why are you multiplicating image repositories, where Art already has
one with the whole image structure clasified and versioned?
> used for this, and given some additional structure. I'm also finding some
> svg masters for items that are not really logos, like "Get It Here", that
> probably need to be moved to "branding" even though they are not really
> logos.
>
> And, because there are quite a few sites using old logo versions, I don't
> really think we should track them all down and require them to upgrade.
>
> Again, I am only referring to svg for these. Renderings, png files, as far
> as I'm concerned, can be renamed and kept anywhere. The new logo used on
> the website now, for example, is not a drop in replacement for the old
> one, because the size is slightly larger due to design considerations. So,
> it's conceivable, depending on use, the even within the Apache OpenOffice
> site, etc., different renderings might be used. But maybe this is in
> opposition to what marketing folks mean by a "logo" with a specific size,
> etc., I don't know.
>
>
>
>> Regards,
>>
>> -Rob
>>
>>
>> >
>> >
>> >> or something clean like that. However, I have not had any luck
>> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
>> >> errors. And I have not had any luck getting Kevin to send a version
>> >> that will load.
>> >>
>> >> So we're stuck right now with a logo that does load into Inkscape, but
>> >> is slightly different than the one we used in AOO 4.0.
>> >>
>> >
>> >> > At the same time we have old logos which had been untouch. I think
>> >> > the
>> >> > webdevs have small understanding of a svn is builted so that the
>> >> > files
>> >> are
>> >> > updated without having different versions laying arround. Over this
>> >> > example, ooo-logo.png and
>> >> > AOO4_website_logo.png<
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >> >exist.
>> >> >
>> >> > All these proliferation of logos, usually will built up to become
>> >> > incredibly messy to work. I suggest to put the information such as
>> >> author,
>> >> > version, status, etc. on the comments of the commit and not on the
>> >> > filename. Likewise to take the time to look for the source of the
>> image,
>> >> > since there is an SVG/ folder to link the source of them, and
>> >> > finally
>> if
>> >> > there are different images (sizes) to have a common convention.
>> >> >
>> >>
>> >> A more logical naming scheme would be good, I agree. But this has
>> >> been waiting for resolution of which SVG we should actually be using.
>> >>
>> >> Regards,
>> >>
>> >> -Rob
>> >>
>> >>
>> >> > If you want to review the images please go here:
>> >> >
>> >>
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >> >
>> >> > --
>> >> > Alexandro Colorado
>> >> > Apache OpenOffice Contributor
>> >> > http://www.openoffice.org
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> >> For additional commands, e-mail: dev-help@openoffice.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Alexandro Colorado
>> > Apache OpenOffice Contributor
>> > http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Mon, Aug 12, 2013 at 11:37 AM, Kay Schenk <ka...@gmail.com> wrote:
> On Mon, Aug 12, 2013 at 6:25 AM, Rob Weir <ro...@apache.org> wrote:
>
> > On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> > > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> > >
> > >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> > wrote:
> > >> > I think the image structure on the website is a bit messy, there has
> > been
> > >> > some cleanup done by kschenk but I think there is still a lot of
> > clean up
> > >> > work to be done.
> > >> >
> > >> > For example, the new logo, was simply draged and drop to the
> AOOLogos
> > >> > folder with a huge name. I understand the name was needed to
> identify
> > it
> > >> > between the rest of the competitive logos. But now that is selected,
> > the
> > >> > current name is unecessary long.
> > >> >
> > >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> > >> >
> > >> >
> > >>
> > >> Right. That work is incomplete. I checked it in originally, after
> > >> the logo vote, so we could start working on the product integration
> > >> immediately. But note that the above logo is not the one we actually
> > >> used in AOO 4.0 !!
> > >>
> > >> The one we actually used is this one:
> > >>
> > >>
> > >>
> > >>
> >
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> > >>
> > >> This was Chris R's contest logo with some minor technical changes.
> > >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> > >> I helped check in.
> > >>
> > >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> > >>
> > >
> > > Again I think we do need a convention for a "logo.svg" as opposed to
> > > ending with a logo-30.svg logo-40.svg logo-50.svg. An just
> incrementally
> > > replace with the future logos as we update the SVG.
> > >
> >
> > Here's the complication: The old logos are still relevant some some
> > purposes. For example, the PMC receives ongoing requests to approve
> > use of the old OpenOffice.org logo. Why would that happen? Often it
> > is a request by publishers who are making an e-book version of an
> > older print book. If their original request did not include the
> > e-book rights then they come back to us (and owners of every other
> > image they use) to request additional permissions.
> >
> > So it may be possible, going forward, to store logos as SVN revisions
> > under the same name. But we cannot retroactively do this with
> > pre-Apache logos. And even if we could, this is harder for users of
> > the logo to access. It is much easier to have something like
> > logo-330.svg available via HTTP.
> >
> > Of course you can have a hybrid approach:
> >
> > 1) When a new logo is introduced, svn copy the old one into a
> > /old-logos directory with a new descriptive name. This preserves the
> > version history.
> >
> > 2) New logo then is checked in as a new revision of logo-master.svg.
> >
>
> I like this idea or something akin to it. We should definitely preserve
> svgs for old logos in my opinion. The new "branding" repository can be
> used for this, and given some additional structure. I'm also finding some
> svg masters for items that are not really logos, like "Get It Here", that
> probably need to be moved to "branding" even though they are not really
> logos.
>
That is because branding original intention was to document/create the
guidelines, it was 100% documentation project. ART (inside marketing) is
the one that hold the logos, banners, artwork, design elements,
microbanners, and 3d work, etc.
http://www.openoffice.org/marketing/art/
As well as other type of design like Business card templates, OOoCon
Impress templates, and such. Branding basically was just a branch on the
wiki. Eventually this was moved to the wiki.
We soon realize that managing the repository on the wiki would be a faster
and easier way since the wiki is much easier to make commits and updates to
it. Example, the splashscreen contest:
http://wiki.openoffice.org/wiki/Art/Gallery
>
> And, because there are quite a few sites using old logo versions, I don't
> really think we should track them all down and require them to upgrade.
>
Some groups clone the 'master' logo and this makes it a bit harder to
track, there are still some abandoned NL projects with the design from OOo
3.0 (2008/9)
>
> Again, I am only referring to svg for these. Renderings, png files, as far
> as I'm concerned, can be renamed and kept anywhere. The new logo used on
> the website now, for example, is not a drop in replacement for the old
> one, because the size is slightly larger due to design considerations. So,
>
AFAIK the new logo is exactly the same approach of the old logo (Apache on
top of OpenOffice and an Orb to the left). Can you explain further?
> it's conceivable, depending on use, the even within the Apache OpenOffice
> site, etc., different renderings might be used. But maybe this is in
> opposition to what marketing folks mean by a "logo" with a specific size,
> etc., I don't know.
>
>
>
> > Regards,
> >
> > -Rob
> >
> >
> > >
> > >
> > >> or something clean like that. However, I have not had any luck
> > >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> > >> errors. And I have not had any luck getting Kevin to send a version
> > >> that will load.
> > >>
> > >> So we're stuck right now with a logo that does load into Inkscape, but
> > >> is slightly different than the one we used in AOO 4.0.
> > >>
> > >
> > >> > At the same time we have old logos which had been untouch. I think
> the
> > >> > webdevs have small understanding of a svn is builted so that the
> files
> > >> are
> > >> > updated without having different versions laying arround. Over this
> > >> > example, ooo-logo.png and
> > >> > AOO4_website_logo.png<
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> > >> >exist.
> > >> >
> > >> > All these proliferation of logos, usually will built up to become
> > >> > incredibly messy to work. I suggest to put the information such as
> > >> author,
> > >> > version, status, etc. on the comments of the commit and not on the
> > >> > filename. Likewise to take the time to look for the source of the
> > image,
> > >> > since there is an SVG/ folder to link the source of them, and
> finally
> > if
> > >> > there are different images (sizes) to have a common convention.
> > >> >
> > >>
> > >> A more logical naming scheme would be good, I agree. But this has
> > >> been waiting for resolution of which SVG we should actually be using.
> > >>
> > >> Regards,
> > >>
> > >> -Rob
> > >>
> > >>
> > >> > If you want to review the images please go here:
> > >> >
> > >>
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> > >> >
> > >> > --
> > >> > Alexandro Colorado
> > >> > Apache OpenOffice Contributor
> > >> > http://www.openoffice.org
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > >> For additional commands, e-mail: dev-help@openoffice.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > Alexandro Colorado
> > > Apache OpenOffice Contributor
> > > http://www.openoffice.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> > For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
>
>
> --
>
> -------------------------------------------------------------------------------------------------
> MzK
>
> Success is falling nine times and getting up ten."
> -- Jon Bon Jovi
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Kay Schenk <ka...@gmail.com>.
On Mon, Aug 12, 2013 at 6:25 AM, Rob Weir <ro...@apache.org> wrote:
> On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> > On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> >
> >> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> >> > I think the image structure on the website is a bit messy, there has
> been
> >> > some cleanup done by kschenk but I think there is still a lot of
> clean up
> >> > work to be done.
> >> >
> >> > For example, the new logo, was simply draged and drop to the AOOLogos
> >> > folder with a huge name. I understand the name was needed to identify
> it
> >> > between the rest of the competitive logos. But now that is selected,
> the
> >> > current name is unecessary long.
> >> >
> >> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >> >
> >> >
> >>
> >> Right. That work is incomplete. I checked it in originally, after
> >> the logo vote, so we could start working on the product integration
> >> immediately. But note that the above logo is not the one we actually
> >> used in AOO 4.0 !!
> >>
> >> The one we actually used is this one:
> >>
> >>
> >>
> >>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
> >>
> >> This was Chris R's contest logo with some minor technical changes.
> >> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> >> I helped check in.
> >>
> >> My intent was to take that SVG and rename it to "master-logo-40.svg"
> >>
> >
> > Again I think we do need a convention for a "logo.svg" as opposed to
> > ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
> > replace with the future logos as we update the SVG.
> >
>
> Here's the complication: The old logos are still relevant some some
> purposes. For example, the PMC receives ongoing requests to approve
> use of the old OpenOffice.org logo. Why would that happen? Often it
> is a request by publishers who are making an e-book version of an
> older print book. If their original request did not include the
> e-book rights then they come back to us (and owners of every other
> image they use) to request additional permissions.
>
> So it may be possible, going forward, to store logos as SVN revisions
> under the same name. But we cannot retroactively do this with
> pre-Apache logos. And even if we could, this is harder for users of
> the logo to access. It is much easier to have something like
> logo-330.svg available via HTTP.
>
> Of course you can have a hybrid approach:
>
> 1) When a new logo is introduced, svn copy the old one into a
> /old-logos directory with a new descriptive name. This preserves the
> version history.
>
> 2) New logo then is checked in as a new revision of logo-master.svg.
>
I like this idea or something akin to it. We should definitely preserve
svgs for old logos in my opinion. The new "branding" repository can be
used for this, and given some additional structure. I'm also finding some
svg masters for items that are not really logos, like "Get It Here", that
probably need to be moved to "branding" even though they are not really
logos.
And, because there are quite a few sites using old logo versions, I don't
really think we should track them all down and require them to upgrade.
Again, I am only referring to svg for these. Renderings, png files, as far
as I'm concerned, can be renamed and kept anywhere. The new logo used on
the website now, for example, is not a drop in replacement for the old
one, because the size is slightly larger due to design considerations. So,
it's conceivable, depending on use, the even within the Apache OpenOffice
site, etc., different renderings might be used. But maybe this is in
opposition to what marketing folks mean by a "logo" with a specific size,
etc., I don't know.
> Regards,
>
> -Rob
>
>
> >
> >
> >> or something clean like that. However, I have not had any luck
> >> getting this logo to load into Inkscape or Adobe Illustrator. I get
> >> errors. And I have not had any luck getting Kevin to send a version
> >> that will load.
> >>
> >> So we're stuck right now with a logo that does load into Inkscape, but
> >> is slightly different than the one we used in AOO 4.0.
> >>
> >
> >> > At the same time we have old logos which had been untouch. I think the
> >> > webdevs have small understanding of a svn is builted so that the files
> >> are
> >> > updated without having different versions laying arround. Over this
> >> > example, ooo-logo.png and
> >> > AOO4_website_logo.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >> >exist.
> >> >
> >> > All these proliferation of logos, usually will built up to become
> >> > incredibly messy to work. I suggest to put the information such as
> >> author,
> >> > version, status, etc. on the comments of the commit and not on the
> >> > filename. Likewise to take the time to look for the source of the
> image,
> >> > since there is an SVG/ folder to link the source of them, and finally
> if
> >> > there are different images (sizes) to have a common convention.
> >> >
> >>
> >> A more logical naming scheme would be good, I agree. But this has
> >> been waiting for resolution of which SVG we should actually be using.
> >>
> >> Regards,
> >>
> >> -Rob
> >>
> >>
> >> > If you want to review the images please go here:
> >> >
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >> >
> >> > --
> >> > Alexandro Colorado
> >> > Apache OpenOffice Contributor
> >> > http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>
> >>
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
-------------------------------------------------------------------------------------------------
MzK
Success is falling nine times and getting up ten."
-- Jon Bon Jovi
Re: Unnecesary filestructure on images
Posted by Rob Weir <ro...@apache.org>.
On Sun, Aug 11, 2013 at 7:49 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
>
>> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>> > I think the image structure on the website is a bit messy, there has been
>> > some cleanup done by kschenk but I think there is still a lot of clean up
>> > work to be done.
>> >
>> > For example, the new logo, was simply draged and drop to the AOOLogos
>> > folder with a huge name. I understand the name was needed to identify it
>> > between the rest of the competitive logos. But now that is selected, the
>> > current name is unecessary long.
>> >
>> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>> >
>> >
>>
>> Right. That work is incomplete. I checked it in originally, after
>> the logo vote, so we could start working on the product integration
>> immediately. But note that the above logo is not the one we actually
>> used in AOO 4.0 !!
>>
>> The one we actually used is this one:
>>
>>
>>
>> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>>
>> This was Chris R's contest logo with some minor technical changes.
>> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
>> I helped check in.
>>
>> My intent was to take that SVG and rename it to "master-logo-40.svg"
>>
>
> Again I think we do need a convention for a "logo.svg" as opposed to
> ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
> replace with the future logos as we update the SVG.
>
Here's the complication: The old logos are still relevant some some
purposes. For example, the PMC receives ongoing requests to approve
use of the old OpenOffice.org logo. Why would that happen? Often it
is a request by publishers who are making an e-book version of an
older print book. If their original request did not include the
e-book rights then they come back to us (and owners of every other
image they use) to request additional permissions.
So it may be possible, going forward, to store logos as SVN revisions
under the same name. But we cannot retroactively do this with
pre-Apache logos. And even if we could, this is harder for users of
the logo to access. It is much easier to have something like
logo-330.svg available via HTTP.
Of course you can have a hybrid approach:
1) When a new logo is introduced, svn copy the old one into a
/old-logos directory with a new descriptive name. This preserves the
version history.
2) New logo then is checked in as a new revision of logo-master.svg.
Regards,
-Rob
>
>
>> or something clean like that. However, I have not had any luck
>> getting this logo to load into Inkscape or Adobe Illustrator. I get
>> errors. And I have not had any luck getting Kevin to send a version
>> that will load.
>>
>> So we're stuck right now with a logo that does load into Inkscape, but
>> is slightly different than the one we used in AOO 4.0.
>>
>
>> > At the same time we have old logos which had been untouch. I think the
>> > webdevs have small understanding of a svn is builted so that the files
>> are
>> > updated without having different versions laying arround. Over this
>> > example, ooo-logo.png and
>> > AOO4_website_logo.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>> >exist.
>> >
>> > All these proliferation of logos, usually will built up to become
>> > incredibly messy to work. I suggest to put the information such as
>> author,
>> > version, status, etc. on the comments of the commit and not on the
>> > filename. Likewise to take the time to look for the source of the image,
>> > since there is an SVG/ folder to link the source of them, and finally if
>> > there are different images (sizes) to have a common convention.
>> >
>>
>> A more logical naming scheme would be good, I agree. But this has
>> been waiting for resolution of which SVG we should actually be using.
>>
>> Regards,
>>
>> -Rob
>>
>>
>> > If you want to review the images please go here:
>> >
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>> >
>> > --
>> > Alexandro Colorado
>> > Apache OpenOffice Contributor
>> > http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Sun, Aug 11, 2013 at 6:33 PM, Rob Weir <ro...@apache.org> wrote:
> On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
> > I think the image structure on the website is a bit messy, there has been
> > some cleanup done by kschenk but I think there is still a lot of clean up
> > work to be done.
> >
> > For example, the new logo, was simply draged and drop to the AOOLogos
> > folder with a huge name. I understand the name was needed to identify it
> > between the rest of the competitive logos. But now that is selected, the
> > current name is unecessary long.
> >
> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >
> >
>
> Right. That work is incomplete. I checked it in originally, after
> the logo vote, so we could start working on the product integration
> immediately. But note that the above logo is not the one we actually
> used in AOO 4.0 !!
>
> The one we actually used is this one:
>
>
>
> https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
>
> This was Chris R's contest logo with some minor technical changes.
> Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
> I helped check in.
>
> My intent was to take that SVG and rename it to "master-logo-40.svg"
>
Again I think we do need a convention for a "logo.svg" as opposed to
ending with a logo-30.svg logo-40.svg logo-50.svg. An just incrementally
replace with the future logos as we update the SVG.
> or something clean like that. However, I have not had any luck
> getting this logo to load into Inkscape or Adobe Illustrator. I get
> errors. And I have not had any luck getting Kevin to send a version
> that will load.
>
> So we're stuck right now with a logo that does load into Inkscape, but
> is slightly different than the one we used in AOO 4.0.
>
> > At the same time we have old logos which had been untouch. I think the
> > webdevs have small understanding of a svn is builted so that the files
> are
> > updated without having different versions laying arround. Over this
> > example, ooo-logo.png and
> > AOO4_website_logo.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >exist.
> >
> > All these proliferation of logos, usually will built up to become
> > incredibly messy to work. I suggest to put the information such as
> author,
> > version, status, etc. on the comments of the commit and not on the
> > filename. Likewise to take the time to look for the source of the image,
> > since there is an SVG/ folder to link the source of them, and finally if
> > there are different images (sizes) to have a common convention.
> >
>
> A more logical naming scheme would be good, I agree. But this has
> been waiting for resolution of which SVG we should actually be using.
>
> Regards,
>
> -Rob
>
>
> > If you want to review the images please go here:
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Rob Weir <ro...@apache.org>.
On Sun, Aug 11, 2013 at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
> I think the image structure on the website is a bit messy, there has been
> some cleanup done by kschenk but I think there is still a lot of clean up
> work to be done.
>
> For example, the new logo, was simply draged and drop to the AOOLogos
> folder with a huge name. I understand the name was needed to identify it
> between the rest of the competitive logos. But now that is selected, the
> current name is unecessary long.
>
> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log>
>
Right. That work is incomplete. I checked it in originally, after
the logo vote, so we could start working on the product integration
immediately. But note that the above logo is not the one we actually
used in AOO 4.0 !!
The one we actually used is this one:
https://svn.apache.org/repos/asf/openoffice/branding/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_Inkscape_kg.svg
This was Chris R's contest logo with some minor technical changes.
Kevin G. used this and generated the PNG/JPG files for AOO 4.0, which
I helped check in.
My intent was to take that SVG and rename it to "master-logo-40.svg"
or something clean like that. However, I have not had any luck
getting this logo to load into Inkscape or Adobe Illustrator. I get
errors. And I have not had any luck getting Kevin to send a version
that will load.
So we're stuck right now with a logo that does load into Inkscape, but
is slightly different than the one we used in AOO 4.0.
> At the same time we have old logos which had been untouch. I think the
> webdevs have small understanding of a svn is builted so that the files are
> updated without having different versions laying arround. Over this
> example, ooo-logo.png and
> AOO4_website_logo.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log>exist.
>
> All these proliferation of logos, usually will built up to become
> incredibly messy to work. I suggest to put the information such as author,
> version, status, etc. on the comments of the commit and not on the
> filename. Likewise to take the time to look for the source of the image,
> since there is an SVG/ folder to link the source of them, and finally if
> there are different images (sizes) to have a common convention.
>
A more logical naming scheme would be good, I agree. But this has
been waiting for resolution of which SVG we should actually be using.
Regards,
-Rob
> If you want to review the images please go here:
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Sun, Aug 11, 2013 at 4:30 PM, Dave Fisher <wa...@apache.org> wrote:
>
>
> Sent from my iPhone
>
> On Aug 11, 2013, at 3:52 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>
> > On Sun, Aug 11, 2013 at 2:58 PM, Dave Fisher <wa...@apache.org> wrote:
> >
> >>
> >>
> >> Sent from my iPhone
> >>
> >> On Aug 11, 2013, at 2:26 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> >>
> >>> On Sun, Aug 11, 2013 at 11:22 AM, Dave Fisher <wa...@apache.org> wrote:
> >>>
> >>>>
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>> On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org>
> wrote:
> >>>>
> >>>>> I think the image structure on the website is a bit messy, there has
> >> been
> >>>>> some cleanup done by kschenk but I think there is still a lot of
> clean
> >> up
> >>>>> work to be done.
> >>>>>
> >>>>> For example, the new logo, was simply draged and drop to the AOOLogos
> >>>>> folder with a huge name. I understand the name was needed to identify
> >> it
> >>>>> between the rest of the competitive logos. But now that is selected,
> >> the
> >>>>> current name is unecessary long.
> >>>>>
> >>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >>>>>
> >>>>>
> >>>>> At the same time we have old logos which had been untouch. I think
> the
> >>>>> webdevs have small understanding of a svn is builted so that the
> files
> >>>> are
> >>>>> updated without having different versions laying arround.
> >>>>
> >>>> This is not so. I can assure you that I completely understand SVN and
> >> VCS.
> >>>>
> >>>> Choices were made to be non disruptive. Changing logos for the site is
> >>>> handled in exactly one spot. This means different names for different
> >>>> versions is entirely appropriate.
> >>>
> >>> I can't imagine this 'non disruptive' happening in code as well and
> >> having
> >>> different librarries with different classes and different names
> attached
> >> to
> >>> the libraries. Like all of the sudden you have 5
> ColumnControlWindow.cxx
> >> it
> >>> would now be ColumnControlWindow_joes_selected_20130218.cxx attached to
> >>> previous 5 different alternatives of the .cxx file.
> >>
> >> We are discussing the website and the work that Kay and I did during the
> >> move to Apache. Remember you referred to webdevs not understanding svn.
> >
> > Ok I understand how this came to be now, and I can see the point on
> legacy
> > files. However this practice would eventually need some reorganization.
> > Hopefully this reorganization is today.
> >
> >
> >>
> >>>
> >>>
> >>>>
> >>>>> Over this
> >>>>> example, ooo-logo.png and
> >>>>> AOO4_website_logo.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >>>>> exist.
> >>>>
> >>>> The logos differ. The names differ.
> >>>
> >>> The logos are outdated and obosolete, they should only exist in the
> >>> revsion history, and maybe on a different archieved section with a more
> >>> detailed metadata instead of cludgy filename. Something like:
> >>>
> >>> svn log:
> >>> logo.png rev123222 AOO 4 for website selected from contest...
> >>> rev123221 AOO logo 3.4.1 under apache brand
> >>> rev123220 OOo Oracle branding for ..
> >>
> >> Kay has proposed and created a canonical location for logos and original
> >> art. You suggested that some standards for sizes and names be applied,
> we
> >> await a concrete proposal.
> >
> > There are two different locations for the logos at the moment afaik,
> > $root/images/ and $root/marketing/art/galleries/logos/aoo-working/
> >
> > The second one is for art-related activities, and I can see how handling
> > multiple work would make use of a large file name.
> >
> > For the first one, which are webdev related, I don't see the benefit of
> > holding such filenames or even multiple filenames. So yes, a cannonical
> > location and standarized convention for the different rasterize images
> as
> > well as a clear distinction to the source file.
> >
> > for unknown reasons, I am unable to access cwiki, getting a permission
> > error to even see my own profile in confluence. I dont see a component
> for
> > infra on bugzilla, should it go on Jira?
> >
>
> There may be a Apache infra wiki upgrade in progress. I'm traveling and
> will check later.
>
> Or you can on irc.
>
I am on the #dev.openoffice.org which channel should I go.
Freenode server I guess.
>
> Regards,
> Dave
>
> >
> >
> >>
> >>
> >>>
> >>>
> >>>>
> >>>> If we are looking to provide a canonical path to a single current logo
> >> for
> >>>> third party use then that is a different question
> >>>>
> >>>>> All these proliferation of logos, usually will built up to become
> >>>>> incredibly messy to work. I suggest to put the information such as
> >>>> author,
> >>>>> version, status, etc. on the comments of the commit and not on the
> >>>>> filename.
> >>>>
> >>>> I agree that the name is long, changing it would be simple, but to
> what?
> >>>
> >>> Is unnecesary long. K.I.S.S. PNG and SVG have metadata exactly for
> >> issues
> >>> like this. Imagemagic can just do something like
> >>>
> >>> convert logo.png -set Title "Apache OpenOffice 4" -set Author "ChrisR"
> >> logo.png
> >>>
> >>> identify -verbose logo.png |grep Title
> >>>
> >>> Title: Apache OpenOffice 4
> >>
> http://blog.client9.com/2007/08/editing-png-metadata-from-command-line.html
> >>
> >> Add it to a list of proposed actions to be discussed.
> >>
> >> The cwiki is provided for this purpose.
> >>
> >> I don't disagree, but it is absolutely necessary to proceed in an open
> >> manner.
> >>
> >> Regards,
> >> Dave
> >>
> >>
> >>>
> >>>
> >>>>
> >>>> Author is the committer and if they are representing others
> contribution
> >>>> then they can easily indicate that is so.
> >>>>
> >>>> If creating a PNG based on an SVG then include the SVG path in the
> >> comment.
> >>>>
> >>>>> Likewise to take the time to look for the source of the image,
> >>>>> since there is an SVG/ folder to link the source of them, and finally
> >> if
> >>>>> there are different images (sizes) to have a common convention.
> >>>>
> >>>> If you would like to discuss common conventions and sizes then please
> >>>> create a cwiki page and start a new thread.
> >>>>
> >>>>>
> >>>>> If you want to review the images please go here:
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>>
> >>>>> --
> >>>>> Alexandro Colorado
> >>>>> Apache OpenOffice Contributor
> >>>>> http://www.openoffice.org
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >>>> For additional commands, e-mail: dev-help@openoffice.apache.org
> >>>
> >>>
> >>> --
> >>> Alexandro Colorado
> >>> Apache OpenOffice Contributor
> >>> http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <wa...@apache.org>.
Sent from my iPhone
On Aug 11, 2013, at 3:52 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> On Sun, Aug 11, 2013 at 2:58 PM, Dave Fisher <wa...@apache.org> wrote:
>
>>
>>
>> Sent from my iPhone
>>
>> On Aug 11, 2013, at 2:26 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>>
>>> On Sun, Aug 11, 2013 at 11:22 AM, Dave Fisher <wa...@apache.org> wrote:
>>>
>>>>
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>>>>
>>>>> I think the image structure on the website is a bit messy, there has
>> been
>>>>> some cleanup done by kschenk but I think there is still a lot of clean
>> up
>>>>> work to be done.
>>>>>
>>>>> For example, the new logo, was simply draged and drop to the AOOLogos
>>>>> folder with a huge name. I understand the name was needed to identify
>> it
>>>>> between the rest of the competitive logos. But now that is selected,
>> the
>>>>> current name is unecessary long.
>>>>>
>>>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>>>
>>>>>
>>>>> At the same time we have old logos which had been untouch. I think the
>>>>> webdevs have small understanding of a svn is builted so that the files
>>>> are
>>>>> updated without having different versions laying arround.
>>>>
>>>> This is not so. I can assure you that I completely understand SVN and
>> VCS.
>>>>
>>>> Choices were made to be non disruptive. Changing logos for the site is
>>>> handled in exactly one spot. This means different names for different
>>>> versions is entirely appropriate.
>>>
>>> I can't imagine this 'non disruptive' happening in code as well and
>> having
>>> different librarries with different classes and different names attached
>> to
>>> the libraries. Like all of the sudden you have 5 ColumnControlWindow.cxx
>> it
>>> would now be ColumnControlWindow_joes_selected_20130218.cxx attached to
>>> previous 5 different alternatives of the .cxx file.
>>
>> We are discussing the website and the work that Kay and I did during the
>> move to Apache. Remember you referred to webdevs not understanding svn.
>
> Ok I understand how this came to be now, and I can see the point on legacy
> files. However this practice would eventually need some reorganization.
> Hopefully this reorganization is today.
>
>
>>
>>>
>>>
>>>>
>>>>> Over this
>>>>> example, ooo-logo.png and
>>>>> AOO4_website_logo.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>>>> exist.
>>>>
>>>> The logos differ. The names differ.
>>>
>>> The logos are outdated and obosolete, they should only exist in the
>>> revsion history, and maybe on a different archieved section with a more
>>> detailed metadata instead of cludgy filename. Something like:
>>>
>>> svn log:
>>> logo.png rev123222 AOO 4 for website selected from contest...
>>> rev123221 AOO logo 3.4.1 under apache brand
>>> rev123220 OOo Oracle branding for ..
>>
>> Kay has proposed and created a canonical location for logos and original
>> art. You suggested that some standards for sizes and names be applied, we
>> await a concrete proposal.
>
> There are two different locations for the logos at the moment afaik,
> $root/images/ and $root/marketing/art/galleries/logos/aoo-working/
>
> The second one is for art-related activities, and I can see how handling
> multiple work would make use of a large file name.
>
> For the first one, which are webdev related, I don't see the benefit of
> holding such filenames or even multiple filenames. So yes, a cannonical
> location and standarized convention for the different rasterize images as
> well as a clear distinction to the source file.
>
> for unknown reasons, I am unable to access cwiki, getting a permission
> error to even see my own profile in confluence. I dont see a component for
> infra on bugzilla, should it go on Jira?
>
There may be a Apache infra wiki upgrade in progress. I'm traveling and will check later.
Or you can on irc.
Regards,
Dave
>
>
>>
>>
>>>
>>>
>>>>
>>>> If we are looking to provide a canonical path to a single current logo
>> for
>>>> third party use then that is a different question
>>>>
>>>>> All these proliferation of logos, usually will built up to become
>>>>> incredibly messy to work. I suggest to put the information such as
>>>> author,
>>>>> version, status, etc. on the comments of the commit and not on the
>>>>> filename.
>>>>
>>>> I agree that the name is long, changing it would be simple, but to what?
>>>
>>> Is unnecesary long. K.I.S.S. PNG and SVG have metadata exactly for
>> issues
>>> like this. Imagemagic can just do something like
>>>
>>> convert logo.png -set Title "Apache OpenOffice 4" -set Author "ChrisR"
>> logo.png
>>>
>>> identify -verbose logo.png |grep Title
>>>
>>> Title: Apache OpenOffice 4
>> http://blog.client9.com/2007/08/editing-png-metadata-from-command-line.html
>>
>> Add it to a list of proposed actions to be discussed.
>>
>> The cwiki is provided for this purpose.
>>
>> I don't disagree, but it is absolutely necessary to proceed in an open
>> manner.
>>
>> Regards,
>> Dave
>>
>>
>>>
>>>
>>>>
>>>> Author is the committer and if they are representing others contribution
>>>> then they can easily indicate that is so.
>>>>
>>>> If creating a PNG based on an SVG then include the SVG path in the
>> comment.
>>>>
>>>>> Likewise to take the time to look for the source of the image,
>>>>> since there is an SVG/ folder to link the source of them, and finally
>> if
>>>>> there are different images (sizes) to have a common convention.
>>>>
>>>> If you would like to discuss common conventions and sizes then please
>>>> create a cwiki page and start a new thread.
>>>>
>>>>>
>>>>> If you want to review the images please go here:
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>>>
>>>> Regards,
>>>> Dave
>>>>>
>>>>> --
>>>>> Alexandro Colorado
>>>>> Apache OpenOffice Contributor
>>>>> http://www.openoffice.org
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>>>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>>
>>>
>>> --
>>> Alexandro Colorado
>>> Apache OpenOffice Contributor
>>> http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
hi, yeah I did, the problem is solved now. Thanks.
On Mon, Aug 12, 2013 at 1:14 AM, Andrea Pescetti <pe...@apache.org>wrote:
> On 11/08/2013 Alexandro Colorado wrote:
>
>> for unknown reasons, I am unable to access cwiki, getting a permission
>> error to even see my own profile in confluence.
>>
>
> Happened to me too. Reason: my profile contained my (retired)
> openoffice.org e-mail address instead of the Apache one. Resolution: get
> in contact with Infra on #asfinra or e-mail infrastructure@apache.org and
> ask them to update your e-mail address from jzaATopenoffice.org to
> jzaATapache.org (or whatever).
>
> Regards,
> Andrea.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<de...@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Andrea Pescetti <pe...@apache.org>.
On 11/08/2013 Alexandro Colorado wrote:
> for unknown reasons, I am unable to access cwiki, getting a permission
> error to even see my own profile in confluence.
Happened to me too. Reason: my profile contained my (retired)
openoffice.org e-mail address instead of the Apache one. Resolution: get
in contact with Infra on #asfinra or e-mail infrastructure@apache.org
and ask them to update your e-mail address from jzaATopenoffice.org to
jzaATapache.org (or whatever).
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Sun, Aug 11, 2013 at 2:58 PM, Dave Fisher <wa...@apache.org> wrote:
>
>
> Sent from my iPhone
>
> On Aug 11, 2013, at 2:26 PM, Alexandro Colorado <jz...@oooes.org> wrote:
>
> > On Sun, Aug 11, 2013 at 11:22 AM, Dave Fisher <wa...@apache.org> wrote:
> >
> >>
> >>
> >> Sent from my iPhone
> >>
> >> On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
> >>
> >>> I think the image structure on the website is a bit messy, there has
> been
> >>> some cleanup done by kschenk but I think there is still a lot of clean
> up
> >>> work to be done.
> >>>
> >>> For example, the new logo, was simply draged and drop to the AOOLogos
> >>> folder with a huge name. I understand the name was needed to identify
> it
> >>> between the rest of the competitive logos. But now that is selected,
> the
> >>> current name is unecessary long.
> >>>
> >>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >>>
> >>>
> >>> At the same time we have old logos which had been untouch. I think the
> >>> webdevs have small understanding of a svn is builted so that the files
> >> are
> >>> updated without having different versions laying arround.
> >>
> >> This is not so. I can assure you that I completely understand SVN and
> VCS.
> >>
> >> Choices were made to be non disruptive. Changing logos for the site is
> >> handled in exactly one spot. This means different names for different
> >> versions is entirely appropriate.
> >
> > I can't imagine this 'non disruptive' happening in code as well and
> having
> > different librarries with different classes and different names attached
> to
> > the libraries. Like all of the sudden you have 5 ColumnControlWindow.cxx
> it
> > would now be ColumnControlWindow_joes_selected_20130218.cxx attached to
> > previous 5 different alternatives of the .cxx file.
>
> We are discussing the website and the work that Kay and I did during the
> move to Apache. Remember you referred to webdevs not understanding svn.
>
Ok I understand how this came to be now, and I can see the point on legacy
files. However this practice would eventually need some reorganization.
Hopefully this reorganization is today.
>
> >
> >
> >>
> >>> Over this
> >>> example, ooo-logo.png and
> >>> AOO4_website_logo.png<
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >>> exist.
> >>
> >> The logos differ. The names differ.
> >
> > The logos are outdated and obosolete, they should only exist in the
> > revsion history, and maybe on a different archieved section with a more
> > detailed metadata instead of cludgy filename. Something like:
> >
> > svn log:
> > logo.png rev123222 AOO 4 for website selected from contest...
> > rev123221 AOO logo 3.4.1 under apache brand
> > rev123220 OOo Oracle branding for ..
> >
>
> Kay has proposed and created a canonical location for logos and original
> art. You suggested that some standards for sizes and names be applied, we
> await a concrete proposal.
>
There are two different locations for the logos at the moment afaik,
$root/images/ and $root/marketing/art/galleries/logos/aoo-working/
The second one is for art-related activities, and I can see how handling
multiple work would make use of a large file name.
For the first one, which are webdev related, I don't see the benefit of
holding such filenames or even multiple filenames. So yes, a cannonical
location and standarized convention for the different rasterize images as
well as a clear distinction to the source file.
for unknown reasons, I am unable to access cwiki, getting a permission
error to even see my own profile in confluence. I dont see a component for
infra on bugzilla, should it go on Jira?
>
>
> >
> >
> >>
> >> If we are looking to provide a canonical path to a single current logo
> for
> >> third party use then that is a different question
> >>
> >>> All these proliferation of logos, usually will built up to become
> >>> incredibly messy to work. I suggest to put the information such as
> >> author,
> >>> version, status, etc. on the comments of the commit and not on the
> >>> filename.
> >>
> >> I agree that the name is long, changing it would be simple, but to what?
> >
> > Is unnecesary long. K.I.S.S. PNG and SVG have metadata exactly for
> issues
> > like this. Imagemagic can just do something like
> >
> > convert logo.png -set Title "Apache OpenOffice 4" -set Author "ChrisR"
> logo.png
> >
> > identify -verbose logo.png |grep Title
> >
> > Title: Apache OpenOffice 4
> >
> >
> >
> >
> http://blog.client9.com/2007/08/editing-png-metadata-from-command-line.html
>
> Add it to a list of proposed actions to be discussed.
>
> The cwiki is provided for this purpose.
>
> I don't disagree, but it is absolutely necessary to proceed in an open
> manner.
>
> Regards,
> Dave
>
>
> >
> >
> >>
> >> Author is the committer and if they are representing others contribution
> >> then they can easily indicate that is so.
> >>
> >> If creating a PNG based on an SVG then include the SVG path in the
> comment.
> >>
> >>> Likewise to take the time to look for the source of the image,
> >>> since there is an SVG/ folder to link the source of them, and finally
> if
> >>> there are different images (sizes) to have a common convention.
> >>
> >> If you would like to discuss common conventions and sizes then please
> >> create a cwiki page and start a new thread.
> >>
> >>>
> >>> If you want to review the images please go here:
> >>
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
> >>
> >> Regards,
> >> Dave
> >>>
> >>> --
> >>> Alexandro Colorado
> >>> Apache OpenOffice Contributor
> >>> http://www.openoffice.org
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> >> For additional commands, e-mail: dev-help@openoffice.apache.org
> >
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <wa...@apache.org>.
Sent from my iPhone
On Aug 11, 2013, at 2:26 PM, Alexandro Colorado <jz...@oooes.org> wrote:
> On Sun, Aug 11, 2013 at 11:22 AM, Dave Fisher <wa...@apache.org> wrote:
>
>>
>>
>> Sent from my iPhone
>>
>> On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>>
>>> I think the image structure on the website is a bit messy, there has been
>>> some cleanup done by kschenk but I think there is still a lot of clean up
>>> work to be done.
>>>
>>> For example, the new logo, was simply draged and drop to the AOOLogos
>>> folder with a huge name. I understand the name was needed to identify it
>>> between the rest of the competitive logos. But now that is selected, the
>>> current name is unecessary long.
>>>
>>> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
>>>
>>>
>>> At the same time we have old logos which had been untouch. I think the
>>> webdevs have small understanding of a svn is builted so that the files
>> are
>>> updated without having different versions laying arround.
>>
>> This is not so. I can assure you that I completely understand SVN and VCS.
>>
>> Choices were made to be non disruptive. Changing logos for the site is
>> handled in exactly one spot. This means different names for different
>> versions is entirely appropriate.
>
> I can't imagine this 'non disruptive' happening in code as well and having
> different librarries with different classes and different names attached to
> the libraries. Like all of the sudden you have 5 ColumnControlWindow.cxx it
> would now be ColumnControlWindow_joes_selected_20130218.cxx attached to
> previous 5 different alternatives of the .cxx file.
We are discussing the website and the work that Kay and I did during the move to Apache. Remember you referred to webdevs not understanding svn.
>
>
>>
>>> Over this
>>> example, ooo-logo.png and
>>> AOO4_website_logo.png<
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
>>> exist.
>>
>> The logos differ. The names differ.
>
> The logos are outdated and obosolete, they should only exist in the
> revsion history, and maybe on a different archieved section with a more
> detailed metadata instead of cludgy filename. Something like:
>
> svn log:
> logo.png rev123222 AOO 4 for website selected from contest...
> rev123221 AOO logo 3.4.1 under apache brand
> rev123220 OOo Oracle branding for ..
>
Kay has proposed and created a canonical location for logos and original art. You suggested that some standards for sizes and names be applied, we await a concrete proposal.
>
>
>>
>> If we are looking to provide a canonical path to a single current logo for
>> third party use then that is a different question
>>
>>> All these proliferation of logos, usually will built up to become
>>> incredibly messy to work. I suggest to put the information such as
>> author,
>>> version, status, etc. on the comments of the commit and not on the
>>> filename.
>>
>> I agree that the name is long, changing it would be simple, but to what?
>
> Is unnecesary long. K.I.S.S. PNG and SVG have metadata exactly for issues
> like this. Imagemagic can just do something like
>
> convert logo.png -set Title "Apache OpenOffice 4" -set Author "ChrisR" logo.png
>
> identify -verbose logo.png |grep Title
>
> Title: Apache OpenOffice 4
>
>
>
> http://blog.client9.com/2007/08/editing-png-metadata-from-command-line.html
Add it to a list of proposed actions to be discussed.
The cwiki is provided for this purpose.
I don't disagree, but it is absolutely necessary to proceed in an open manner.
Regards,
Dave
>
>
>>
>> Author is the committer and if they are representing others contribution
>> then they can easily indicate that is so.
>>
>> If creating a PNG based on an SVG then include the SVG path in the comment.
>>
>>> Likewise to take the time to look for the source of the image,
>>> since there is an SVG/ folder to link the source of them, and finally if
>>> there are different images (sizes) to have a common convention.
>>
>> If you would like to discuss common conventions and sizes then please
>> create a cwiki page and start a new thread.
>>
>>>
>>> If you want to review the images please go here:
>> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>>
>> Regards,
>> Dave
>>>
>>> --
>>> Alexandro Colorado
>>> Apache OpenOffice Contributor
>>> http://www.openoffice.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Unnecesary filestructure on images
Posted by Alexandro Colorado <jz...@oooes.org>.
On Sun, Aug 11, 2013 at 11:22 AM, Dave Fisher <wa...@apache.org> wrote:
>
>
> Sent from my iPhone
>
> On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
>
> > I think the image structure on the website is a bit messy, there has been
> > some cleanup done by kschenk but I think there is still a lot of clean up
> > work to be done.
> >
> > For example, the new logo, was simply draged and drop to the AOOLogos
> > folder with a huge name. I understand the name was needed to identify it
> > between the rest of the competitive logos. But now that is selected, the
> > current name is unecessary long.
> >
> > Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log
> >
> >
> > At the same time we have old logos which had been untouch. I think the
> > webdevs have small understanding of a svn is builted so that the files
> are
> > updated without having different versions laying arround.
>
> This is not so. I can assure you that I completely understand SVN and VCS.
>
> Choices were made to be non disruptive. Changing logos for the site is
> handled in exactly one spot. This means different names for different
> versions is entirely appropriate.
>
I can't imagine this 'non disruptive' happening in code as well and having
different librarries with different classes and different names attached to
the libraries. Like all of the sudden you have 5 ColumnControlWindow.cxx it
would now be ColumnControlWindow_joes_selected_20130218.cxx attached to
previous 5 different alternatives of the .cxx file.
>
> > Over this
> > example, ooo-logo.png and
> > AOO4_website_logo.png<
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log
> >exist.
> >
>
> The logos differ. The names differ.
>
The logos are outdated and obosolete, they should only exist in the
revsion history, and maybe on a different archieved section with a more
detailed metadata instead of cludgy filename. Something like:
svn log:
logo.png rev123222 AOO 4 for website selected from contest...
rev123221 AOO logo 3.4.1 under apache brand
rev123220 OOo Oracle branding for ..
>
> If we are looking to provide a canonical path to a single current logo for
> third party use then that is a different question
>
> > All these proliferation of logos, usually will built up to become
> > incredibly messy to work. I suggest to put the information such as
> author,
> > version, status, etc. on the comments of the commit and not on the
> > filename.
>
> I agree that the name is long, changing it would be simple, but to what?
>
Is unnecesary long. K.I.S.S. PNG and SVG have metadata exactly for issues
like this. Imagemagic can just do something like
convert logo.png -set Title "Apache OpenOffice 4" -set Author "ChrisR" logo.png
identify -verbose logo.png |grep Title
Title: Apache OpenOffice 4
http://blog.client9.com/2007/08/editing-png-metadata-from-command-line.html
>
> Author is the committer and if they are representing others contribution
> then they can easily indicate that is so.
>
> If creating a PNG based on an SVG then include the SVG path in the comment.
>
> > Likewise to take the time to look for the source of the image,
> > since there is an SVG/ folder to link the source of them, and finally if
> > there are different images (sizes) to have a common convention.
>
> If you would like to discuss common conventions and sizes then please
> create a cwiki page and start a new thread.
>
> >
> > If you want to review the images please go here:
> >
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
>
> Regards,
> Dave
> >
> > --
> > Alexandro Colorado
> > Apache OpenOffice Contributor
> > http://www.openoffice.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
--
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
Re: Unnecesary filestructure on images
Posted by Dave Fisher <wa...@apache.org>.
Sent from my iPhone
On Aug 11, 2013, at 1:35 AM, Alexandro Colorado <jz...@oooes.org> wrote:
> I think the image structure on the website is a bit messy, there has been
> some cleanup done by kschenk but I think there is still a lot of clean up
> work to be done.
>
> For example, the new logo, was simply draged and drop to the AOOLogos
> folder with a huge name. I understand the name was needed to identify it
> between the rest of the competitive logos. But now that is selected, the
> current name is unecessary long.
>
> Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/Apache_OpenOffice_Logo_ChrisR_selected_2013-06_optim_300w.png?view=log>
>
> At the same time we have old logos which had been untouch. I think the
> webdevs have small understanding of a svn is builted so that the files are
> updated without having different versions laying arround.
This is not so. I can assure you that I completely understand SVN and VCS.
Choices were made to be non disruptive. Changing logos for the site is handled in exactly one spot. This means different names for different versions is entirely appropriate.
> Over this
> example, ooo-logo.png and
> AOO4_website_logo.png<http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/AOO4_website_logo.png?view=log>exist.
>
The logos differ. The names differ.
If we are looking to provide a canonical path to a single current logo for third party use then that is a different question
> All these proliferation of logos, usually will built up to become
> incredibly messy to work. I suggest to put the information such as author,
> version, status, etc. on the comments of the commit and not on the
> filename.
I agree that the name is long, changing it would be simple, but to what?
Author is the committer and if they are representing others contribution then they can easily indicate that is so.
If creating a PNG based on an SVG then include the SVG path in the comment.
> Likewise to take the time to look for the source of the image,
> since there is an SVG/ folder to link the source of them, and finally if
> there are different images (sizes) to have a common convention.
If you would like to discuss common conventions and sizes then please create a cwiki page and start a new thread.
>
> If you want to review the images please go here:
> http://svn.apache.org/viewvc/openoffice/ooo-site/trunk/content/images/AOO_logos/
Regards,
Dave
>
> --
> Alexandro Colorado
> Apache OpenOffice Contributor
> http://www.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org