Recently we've had some requests from the community as to how they could contribute various pieces of design, artwork or wallpaper.
In order to make it more convenient for such contributions, I've moved the legacy artwork git instance to https://git.centos.org/summary/sig-core!artwork-archive.git. This should be considered legacy and reference only.
To facilitate new artwork contributions, I've created https://github.com/CentOS/Artwork which will be mirrored at https://git.centos.org/summary/sig-core!Artwork.git
This will be the authoritative repository for logos, branding, design, etc. It will also allow contributors to submit pull requests for their contributions, such as backgrounds and other creative artwork.
Right now, both these repositories are bare because we need to have a bit of a discussion around the layout within them. I don't claim to be an artist in any sense of the term, so I'm not going to dictate a structure that might impede the work from people who actually know what they're doing.
The two possible layouts I have in mind are:
1. exploded directory structure for the various source tarballs related to distro artwork such as centos-logos.
2. Named directory structures for the various image types. logos/{svg,png}, desktop/<resolution>/png, etc.
Comments, suggestions and pull requests are very much welcomed from those of you with artistic tendencies.
On 08/12/2014 09:06 AM, Jim Perrin wrote:
Recently we've had some requests from the community as to how they could contribute various pieces of design, artwork or wallpaper.
In order to make it more convenient for such contributions, I've moved the legacy artwork git instance to https://git.centos.org/summary/sig-core!artwork-archive.git. This should be considered legacy and reference only.
To facilitate new artwork contributions, I've created https://github.com/CentOS/Artwork which will be mirrored at https://git.centos.org/summary/sig-core!Artwork.git
This will be the authoritative repository for logos, branding, design, etc. It will also allow contributors to submit pull requests for their contributions, such as backgrounds and other creative artwork.
Right now, both these repositories are bare because we need to have a bit of a discussion around the layout within them. I don't claim to be an artist in any sense of the term, so I'm not going to dictate a structure that might impede the work from people who actually know what they're doing.
The two possible layouts I have in mind are:
- exploded directory structure for the various source tarballs related
to distro artwork such as centos-logos.
- Named directory structures for the various image types.
logos/{svg,png}, desktop/<resolution>/png, etc.
Comments, suggestions and pull requests are very much welcomed from those of you with artistic tendencies.
I'd consider requiring SVG for the artwork, you can always convert SVG into whatever format your tools require (.xpm for grub, for example). SVG is also sorta 'text' which may make revision tracking easier....
Pat
On 08/12/2014 09:21 AM, Pat Riehecky wrote:
I'd consider requiring SVG for the artwork, you can always convert SVG into whatever format your tools require (.xpm for grub, for example). SVG is also sorta 'text' which may make revision tracking easier....
Agreed. The idea here is that any artwork contributed should contain any/all source material that may be required to regenerate or scale the image in an open format with gimp/inkscape etc.
I'd also like the commonly required rendered images as well so that we can point folks to that image as the authoritative source for things. Hopefully this will also allow us to finally murder the older pink-ish 3d font logo that folks seem intent on using...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 08/12/2014 07:28 AM, Jim Perrin wrote:
Agreed. The idea here is that any artwork contributed should contain any/all source material that may be required to regenerate or scale the image in an open format with gimp/inkscape etc.
Also note that all the source material (including original images such as photos) need to be properly licensed. Just being able to redistribute is likely not enough, people need to be able to remix images, etc. People need to be careful not to start with unlicensed stock photos, for example.
- -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41
On 8/12/14, Jim Perrin jperrin@centos.org wrote:
I'd also like the commonly required rendered images as well so that we can point folks to that image as the authoritative source for things. Hopefully this will also allow us to finally murder the older pink-ish 3d font logo that folks seem intent on using...
That would be very good for CentOS brand reproduction sake.
In the layout I proposed in a mail earlier there would be a Models/Branding directory inside the repository where all brands would be stored in SVG format. Automation scripts are conceived to take this information at runtime and marking images with them. There is no need to create the CentOS brand on each single image we need to produce. Instead, we use configuration files to intrude automation scripts what brand to take and where to apply it.
This way, it is possible to introduce changes to CentOS brand and propagate them quickly to all affected images, by running a single command.
Regards, al.
On 8/12/14, Jim Perrin jperrin@centos.org wrote:
Recently we've had some requests from the community as to how they could contribute various pieces of design, artwork or wallpaper.
In order to make it more convenient for such contributions, I've moved the legacy artwork git instance to https://git.centos.org/summary/sig-core!artwork-archive.git. This should be considered legacy and reference only.
Yes. But, for the record, this work is not dead. I continue developing it under very difficult circumstances, so the reason of my apparent absence.
The main goal of this work is to provide a framework for The CentOS Community to produce The CentOS Project visual identity with a single command based on their own artistic motifs and specifications. This is necessary in order to automate the process of consistently releasing one unique visual identity for The CentOS Project each time a new major release of CentOS distribution is published.
Jim, if possible, I would like to have this site available for pushing recent changes in case it be possible for me to do so, at some point.
To facilitate new artwork contributions, I've created https://github.com/CentOS/Artwork which will be mirrored at https://git.centos.org/summary/sig-core!Artwork.git
This will be the authoritative repository for logos, branding, design, etc. It will also allow contributors to submit pull requests for their contributions, such as backgrounds and other creative artwork.
Nice.
Right now, both these repositories are bare because we need to have a bit of a discussion around the layout within them. I don't claim to be an artist in any sense of the term, so I'm not going to dictate a structure that might impede the work from people who actually know what they're doing.
The two possible layouts I have in mind are:
- exploded directory structure for the various source tarballs related
to distro artwork such as centos-logos.
- Named directory structures for the various image types.
logos/{svg,png}, desktop/<resolution>/png, etc.
Comments, suggestions and pull requests are very much welcomed from those of you with artistic tendencies.
I would suggest a layout to cover The CentOS Project visual identity, not just The CentOS distribution visual manifestation which is just one part of The CentOS Project visual identity.
Presently, I am trying to implement a layout where there are "design models", "artistic motifs" and "automation scripts". In such a layout:
- The CentOS Project provides design models (SVG files mainly) to define The CentOS Project visual manifestations (e.g., branding, distribution, marketing, etc.).
- The CentOS Community provides artistic motifs to define the visual style of visual manifestations (e.g., PNG images mainly).
- The CentOS Project provides automation scripts to automate the process of combining design models and artistic motifs arbitrarily into final images for final release (e.g., Tar.gz, RPM, etc.).
In this layout, we try to avoid the inclusion of binary files as much as possible. Instead, we try to render them from their source files. Nevertheless, when we create design models for src.rpm packages, we include the content exactly as it is and remove any binary file that can be rebuilt from source files in the repository. In this context, if there is any binary file that don't need to be rebuild (e.g., it doesn't have any brand or artistic motif) it remains untouched.
Basically, the layout would look as follows:
./ |-- Models/ | `-- ${VISUAL_MANIFESTATION} `-- Scripts/
To produce final images for final release, the repository would be available for installation through RPM. This make design models and automation scripts available in your workstation. At this point, you use automation scripts to prepare a working directory which is use, in turn, to store the artistic motifs and the final content you release.
Design models and automation scripts are under version control but artistic motifs aren't. To share artistic motifs, we could use the CentOS wiki or other public site online useful to share images.
Suggestions and comments are very much appreciated.
Regards, al.
On 08/12/2014 11:15 AM, Alain Reguera Delgado wrote:
On 8/12/14, Jim Perrin jperrin@centos.org wrote:
Recently we've had some requests from the community as to how they could contribute various pieces of design, artwork or wallpaper.
In order to make it more convenient for such contributions, I've moved the legacy artwork git instance to https://git.centos.org/summary/sig-core!artwork-archive.git. This should be considered legacy and reference only.
Yes. But, for the record, this work is not dead. I continue developing it under very difficult circumstances, so the reason of my apparent absence.
Correct. However it wasn't used for the c7 builds for artwork or logos packages either. You had updated the images to the wiki instead. I'm in no way trying to downplay the importance of the work you've done. Please don't take this change as an attempt to do that.
The main goal of this work is to provide a framework for The CentOS Community to produce The CentOS Project visual identity with a single command based on their own artistic motifs and specifications. This is necessary in order to automate the process of consistently releasing one unique visual identity for The CentOS Project each time a new major release of CentOS distribution is published.
The existing structure has been complex for new users who simply want to contribute an svg or similar artwork. This was the primary motivation for the change. The existing structure in git is valuable (which is why we didn't alter it, but simply changed the repo location) but since it's not used for the current logo/artwork, and it was presenting a bit of a barrier to new contributors we decided it would be beneficial to restructure from the ground up to make it easier to consume all the way around.
Jim, if possible, I would like to have this site available for pushing recent changes in case it be possible for me to do so, at some point.
All we did was change the location. I would prefer to have new submissions in the new structure, but everything is still in place for the old one.
Presently, I am trying to implement a layout where there are "design models", "artistic motifs" and "automation scripts". In such a layout:
- The CentOS Project provides design models (SVG files mainly) to
define The CentOS Project visual manifestations (e.g., branding, distribution, marketing, etc.).
- The CentOS Community provides artistic motifs to define the visual
style of visual manifestations (e.g., PNG images mainly).
- The CentOS Project provides automation scripts to automate the
process of combining design models and artistic motifs arbitrarily into final images for final release (e.g., Tar.gz, RPM, etc.).
In this layout, we try to avoid the inclusion of binary files as much as possible. Instead, we try to render them from their source files. Nevertheless, when we create design models for src.rpm packages, we include the content exactly as it is and remove any binary file that can be rebuilt from source files in the repository. In this context, if there is any binary file that don't need to be rebuild (e.g., it doesn't have any brand or artistic motif) it remains untouched.
Basically, the layout would look as follows:
./ |-- Models/ | `-- ${VISUAL_MANIFESTATION} `-- Scripts/
This is reasonably similar to what was there to begin with, correct? That's part of the complexity that we're trying to avoid. If you and Tuomas (the two doing the most at present) agree on how to structure things, then I'll support that. It needs to be easy to consume, and easy to contribute.
----- Original Message -----
From: "Jim Perrin" jperrin@centos.org To: "The CentOS developers mailing list." centos-devel@centos.org Sent: Tuesday, August 12, 2014 5:06:18 PM Subject: [CentOS-devel] Distribution Artwork and logos.
The two possible layouts I have in mind are:
- exploded directory structure for the various source tarballs related
to distro artwork such as centos-logos.
- Named directory structures for the various image types.
logos/{svg,png}, desktop/<resolution>/png, etc.
I am leaning towards splitting things up into separate repositories or folders, maybe?
1. CentOS visual identity and logos have the authoritative source files and colors etc defined in a separate repository, in SVG format and perhaps certain bitmaps for most common uses. These files are used for everything: distro artwork and any other promotional material.
.------------------------------------------------------------. | I would keep this small, clear and logical so it's easy to | | point people to the official logo files. | `------------------------------------------------------------'
2. CentOS distro graphics, things that Alain has been working on.
Maybe these should be organized per release, because things might change between them, and scripts can evolve over time. These folders would contain any release-specific artwork like wallpapers and the motifs that might be used by the scripts. Also some files might be just there as-is (like a custom wallpaper etc), while others will be rendered by the scripts - depends on the case.
3. CentOS promotional material repository, tshirts, stickers and everything else.
By splitting these up we can avoid pointing people into a huge repository with a lot of files, which is confusing, takes more time to clone, and can lead to people using the wrong graphics even.
I will need to think a bit to ponder the structure of each repository, but my initial hunch is that it would make sense to split them by use:
promotional -> brochures -> centos_for_the_win/ promotional -> t-shirt -> 10-years/ distribution -> seven -> common/flowertexture.png distribution -> seven -> installer
But lets see. We can of course do something first and change things when we realize it doesnt work :-)
//Tuomas
On 08/12/2014 12:09 PM, Tuomas Kuosmanen wrote:
----- Original Message -----
From: "Jim Perrin" jperrin@centos.org To: "The CentOS developers mailing list." centos-devel@centos.org Sent: Tuesday, August 12, 2014 5:06:18 PM Subject: [CentOS-devel] Distribution Artwork and logos.
The two possible layouts I have in mind are:
- exploded directory structure for the various source tarballs related
to distro artwork such as centos-logos.
- Named directory structures for the various image types.
logos/{svg,png}, desktop/<resolution>/png, etc.
I am leaning towards splitting things up into separate repositories or folders, maybe?
CentOS visual identity and logos have the authoritative source files and colors etc defined in a separate repository, in SVG format and perhaps certain bitmaps for most common uses. These files are used for everything: distro artwork and any other promotional material.
.------------------------------------------------------------. | I would keep this small, clear and logical so it's easy to | | point people to the official logo files. | `------------------------------------------------------------'
CentOS distro graphics, things that Alain has been working on.
Maybe these should be organized per release, because things might change between them, and scripts can evolve over time. These folders would contain any release-specific artwork like wallpapers and the motifs that might be used by the scripts. Also some files might be just there as-is (like a custom wallpaper etc), while others will be rendered by the scripts - depends on the case.
CentOS promotional material repository, tshirts, stickers and everything else.
By splitting these up we can avoid pointing people into a huge repository with a lot of files, which is confusing, takes more time to clone, and can lead to people using the wrong graphics even.
I will need to think a bit to ponder the structure of each repository, but my initial hunch is that it would make sense to split them by use:
promotional -> brochures -> centos_for_the_win/ promotional -> t-shirt -> 10-years/ distribution -> seven -> common/flowertexture.png distribution -> seven -> installer
But lets see. We can of course do something first and change things when we realize it doesnt work :-)
This makes sense. Would you structure the 'seven' bits of the distribution as a branch in git, or would you prefer to keep releases as directories within the tree?
Alain, is this a structure you could work with?
On 8/12/14, Jim Perrin jperrin@centos.org wrote:
On 08/12/2014 12:09 PM, Tuomas Kuosmanen wrote:
...
CentOS visual identity and logos have the authoritative source files and colors etc defined in a separate repository, in SVG format and perhaps certain bitmaps for most common uses. These files are used for everything: distro artwork and any other promotional material.
.------------------------------------------------------------. | I would keep this small, clear and logical so it's easy to | | point people to the official logo files. | `------------------------------------------------------------'
This is the exact purpose of Models/Branding directory in the layout I am proposing.
CentOS distro graphics, things that Alain has been working on.
Maybe these should be organized per release, because things might change between them, and scripts can evolve over time. These folders would contain any release-specific artwork like wallpapers and the motifs that might be used by the scripts. Also some files might be just there as-is (like a custom wallpaper etc), while others will be rendered by the scripts - depends on the case.
This is the purpose of Models/Distribution directory in the layout I am proposing. Inside it we have content organized by major release. For example:
./Models/Distribution |-- 6 | |-- centos-logos | `-- centos-indexhtml |-- 7 | |-- centos-logos | `-- centos-indexhtml `-- ...
The centos-logos directory would contain the modified source files taken from the last release of redhat-logos we would use to initiate the CentOS rebuild.
The centos-logos directory wouldn't include any wallpaper in binary form. Instead, it would include a configuration file for automation scripts to describe where the wallpaper in binary form would be retrieved from.
When the visual manifestation is ready (e.g., it includes the source files and the configuration file needed to build using automation scripts), the repository is released to the public using RPM, so graphic designers can install it in their workstations. At this point graphic designers count with a read-only directory structure holding the information they need to build the centos-logos package.
The only component missing so far is the artistic motif. So, graphic designers use automation scripts to create a working directory and fill it with artistic motifs which are later used by automation scripts to render visual manifestations using The CentOS Project specification and the graphic designer's artistic motif.
Such working environment makes possible to combine The CentOS Project specifications (e.g., how visual manifestations should be built) and The CentOS Community artistic motifs (e.g., how visual manifestations would look and feel) to achieve multiple results.
Having artistic motifs (e.g., wallpapers) inside the centos-logos directory would prevent the centos-logo package from being reproduced in different visual styles (e.g., it would be rendered with the wallpaper provided in the repository only). Nevertheless, if we separate contexts, it is possible to let the community to render the centos-logos package with different artistic motifs but exact specifications (e.g., where the CentOS brand goes, image size, etc.). Graphic designers would only need to design a bunch of images and run a command to propose its own version of centos-logos package.
Having custom motifs (bunch of images in PNG, SVG and XCF formats) in the repository could be an option. However, they consume a lot of space based on the number of resolutions and color variations you produce. An online web application which let to comment each file posted would be a better place, I guess. So, it is possible to accelerate graphic design interactions.
- CentOS promotional material repository, tshirts, stickers and everything else.
This is the exact purpose of Models/Marketing directory in the layout I propose. Inside this directory there is one sub-directory for each related component (e.g., CD-labels, CD-sleeves, caps, t-shirts, etc.)
By splitting these up we can avoid pointing people into a huge repository with a lot of files, which is confusing, takes more time to clone, and can lead to people using the wrong graphics even.
I agree. Separate repositories and git branches are very attractive.
I will need to think a bit to ponder the structure of each repository, but my initial hunch is that it would make sense to split them by use:
promotional -> brochures -> centos_for_the_win/ promotional -> t-shirt -> 10-years/ distribution -> seven -> common/flowertexture.png distribution -> seven -> installer
Alain, is this a structure you could work with?
Well, I need to rethink everything again to see how this structure fits on what I have so far. It looks attractive.
Regards, al.
----- Original Message -----
From: "Jim Perrin" jperrin@centos.org
To facilitate new artwork contributions, I've created https://github.com/CentOS/Artwork which will be mirrored at https://git.centos.org/summary/sig-core!Artwork.git
Actually, should we also have CentOS/Promo -repository for the tshirt/sticker/poster etc designs in github as well?
Would make easier for people to contribute and to see what's going on?
//Tuomas
On 08/13/2014 03:59 AM, Tuomas Kuosmanen wrote:
----- Original Message -----
From: "Jim Perrin" jperrin@centos.org
To facilitate new artwork contributions, I've created https://github.com/CentOS/Artwork which will be mirrored at https://git.centos.org/summary/sig-core!Artwork.git
Actually, should we also have CentOS/Promo -repository for the tshirt/sticker/poster etc designs in github as well?
Would make easier for people to contribute and to see what's going on?
Should this be Promo as suggested or Promo-Artwork? Is that being too pedantic?
On 08/13/2014 08:57 AM, Tuomas Kuosmanen wrote:
Should this be Promo as suggested or Promo-Artwork? Is that being too pedantic?
Promo-Artwork should be fine. If it starts to bug us, let's change it :P
Created. https://github.com/CentOS/Promo-Artwork
Would you mind pushing a sample structure (maybe with the 10 years tshirt design)?
-
Alain Reguera Delgado -
Jim Perrin -
Karsten Wade -
Pat Riehecky -
Tuomas Kuosmanen