[opensuse-artwork] openSUSE 12.3 ToDo Suggestions - Revised!
Given some of our member's suggestions, I have reviewed the list of do's for 12.3. Please read carefully and give a vote if you agree with the steps. If a majority agrees, we will start making the arrangements for these tasks to see the light. 1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily 2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art 3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc) 4 Change default font to OPEN SANS on KDE. (This font family is extensive and looks extra sharp on both KDE and GNOME, use full rgb subpixel rendering on KDE by default) Start with KDE first and then decide if it will work properly on Gnome 5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come) 6. Change/improve styling on YAST 7 Change KDE splash screen to match Plymouth 8 Keep default splash screens for applications Thank you Andy (anditosan) -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
Hi all, Comments on the flickr contest inline below: On Oct 3, 2012, at 4:28 AM, Andres Silva wrote:
Given some of our member's suggestions, I have reviewed the list of do's for 12.3. Please read carefully and give a vote if you agree with the steps. If a majority agrees, we will start making the arrangements for these tasks to see the light.
1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily
I agree that flickr is definitely better suited to raster images (i.e. photos). However, I would not forbid vector. Someone could make a very nice vector image as wallpaper. Most likely, that vector would be rendered to a raster format for actual use (due to rendering time, quality and use of effects like shadows, etc.). The best reason for using flickr is that we can draw new talent to it through its existing user-base. In order for this to work we need to get the word out to a wider audience which means blogging about it, putting it on the website, the topic of the irc channel, etc. Without this, our flickr page would end up just being a place where existing talent uploads the same stuff they have been so far. That does't seem like the reason behind the effort :-)
2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art
Yes, it needs to be very clearly stated that all uploaded images need to use the correct license. If someone uploads something that does not use the right license we need to contact them and ask them to please use the right one - if they refuse their image cannot be considered for inclusion. I would suggest have a panel of "judges" to decide which images are selected. Having the whole community vote on something like this simply won't work well - trust me on this one, I have been down that road several times with teams much larger than ours and it simply leads to too much useless discussion and lowers the quality of the images selected. The judges would rank each picture. The ranking should be private and each judge would not be allowed to rank their own images. Also, we should rotate the judges every release.
3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc)
Copyright stays with the artist, it only needs to be freely licensed for all usage. In my experience the best photographers will not want to give others the right to edit their photos - we should handle this issue case by case. As for guidelines, here is what I would include: • No brand names or trademarks of any kind. • No illustrations some may consider inappropriate, offensive, hateful, tortuous, defamatory, slanderous or libelous. • No sexually explicit or provocative images. • No images of weapons or violence. • No alcohol, tobacco, or drug use imagery. • No designs which promotes bigotry, racism, hatred or harm against groups or individuals; or promotes discrimination based on race, gender, religion, nationality, disability, sexual orientation or age. • No religious, political, or nationalist imagery. • No branding assets or text to permit use by derivative distributions. • Your image should strive for subtlety and poetry. • Regardless of the role or inspiration, the desired result of the successful submissions will render feelings which may be described as light, bright, or cheerful. • Avoid high frequency images. ( A soft focus is one way to achieve this ) • As the name suggests, visually, it should settle into the “background” of the activity scene. • Design must accommodate the pieces of both the gnome and kde desktop (panels, etc.) • The final dimension should be at least 2560 x 1600 pixels so that we can crop and edit where necessary (we might want to discuss this detail) • Submissions must adhere to the Creative Commons ShareAlike 3.0 license (or another free OS license) • Attribution must be declared if the submission is based on another design (this helps avoid possible legal problems down the road) • Avoid prominent use of the openSUSE logo. It appears in enough places already. • No version numbers. Some individuals may desire to use an older theme, or use the latest theme in their older version of openSUSE. Let your submission be about choice and do not use version numbers in your artwork. • Avoid text, it calls for attention too much and will likely look bad when scaled. Plus it can't be translated easily. • Be careful with small patterns, they might become uneven when scaled. • Consider how the wallpaper will interact with the panels, icons and windows. • Show restraint in your use of color tone and contrast. The wallpaper sets the scene for other elements, it is not the main act. • Use PNG format for bitmap files (ie any files in which fewer colors are repeated throughout, especially when the colors are in large blocks). Use JPGs for photos and final images in order to reduce the file size, as this format can cause visible compression artefacts. • Make the XCF source files available, if you happen to work with GIMP • Use SVG for vector art. • Work generated with proprietary applications like Photoshop and Illustrator is acceptable, but files in their formats are useless for many of us.
4 Change default font to OPEN SANS on KDE. (This font family is extensive and looks extra sharp on both KDE and GNOME, use full rgb subpixel rendering on KDE by default) Start with KDE first and then decide if it will work properly on Gnome
5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come)
6. Change/improve styling on YAST
7 Change KDE splash screen to match Plymouth
8 Keep default splash screens for applications
Thank you Andy (anditosan)
Kenneth Wimer -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
I have some grave concerns about the direction here, but also, I disagree that what is outlined here is actually about "12.3." This seems to be about a broader initiative that isn't 12.3 specific. More below: On Tue, 2012-10-02 at 20:28 -0600, Andres Silva wrote:
Given some of our member's suggestions, I have reviewed the list of do's for 12.3. Please read carefully and give a vote if you agree with the steps. If a majority agrees, we will start making the arrangements for these tasks to see the light.
1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily
This direction, as phrased, concerns me, but I think others have already addressed their concerns and I'd just be repeating...
2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art
I personally dislike Flickr. And its size limitations per account have given some of us already a hard wall that we couldn't get out of without shelling some money out of our pocket. And because of the size limitations, posters will feel obligated to post a lesser-quality resolution in order to not run out of space. But more importantly, I think we should use Flickr, and all other social network outlets as a place of recruitment, not as a repository. We should engage these artists when we see their works (whether on Flickr or Facebook or elsewhere) and encourage/mentor them how to be more directly active as a contributor to the Project. Having the Project function *outside* of its infrastructure is a good way to actually lose control in the long run. And people *will* come when they have a place they can feel they belong.
3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc)
Unless you specifically hand it over to another entity, all works are automatically owned by the creator. So copyrights aren't really the concern here. And unlike some other projects, we don't really encourage copyright assignment. It is anathema, really. What is more important is to understand sources within the artwork. We've had some cases where we thought the contributor completely created a piece, only to find out it was a compilation of components from other places. Contributors need to provide some kind of a trail so when artwork is selected to represent openSUSE, we know the actual history behind it. We need a way to inspect and verify, just like our OBS has an inspection process to ensure proper licensing. It would be serious egg in our face if someone created a wallpaper that we all loved and selected as our default, only to find out after release someone shouting "Hey!!! That image is from another place, you guys aren't orginal at all!" Even if that component was completely open-licensed, not knowing that a piece isn't original makes a world of difference.
4 Change default font to OPEN SANS on KDE. (This font family is extensive and looks extra sharp on both KDE and GNOME, use full rgb subpixel rendering on KDE by default) Start with KDE first and then decide if it will work properly on Gnome
As already mentioned by others, I hope this is something you intend to discuss directly with those teams. We've already encountered in the past where members of those teams were upset with artwork team intruding on work that was already put into this and not even any prior dialogue before attempting to throw out their work for the artwork team's. Some important political diplomacy is needed here before setting out on such initiatives.
5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come)
I must have missed this discussion. The one I recall is the one Jos started with how to retain our beloved seasonal grub screen change. (The one where the Penguins are like lemmings across the top of the menu.) That is a very popular feature, and as Eugene pointed out, it is possible to restore that and even more, to provide *MORE* seasonal options. I would suggest make sure this popular feature is put back in before moving on to other ideas. There is an accessibility problem with the basic screen we have now, and that should also be addressed. Providing some usability testing for important screens is something that needs to be considered. While I respect an artist's right to be creative wrt to their creations, the artwork team primarily functions as a service enhancement to the openSUSE product line. What that means is while artwork should be awesome and beautiful, it should not interfere with the actual usage of the underlying product for our users, regardless of accessibility needs or otherwise.
6. Change/improve styling on YAST
This isn't a 12.3-related subject. Unless you are proposing to do a restyling for every release? If so, that's a huge outlay of resources to reinvent the wheel every time. But bottom line, I don't think this should be a team "TODO" but rather a "Just Do It." I'm not a 100% fan of that slogan, tbh, but in this case it is apropos. The biggest problem we have historically in communities like ours is everyone getting into a discussion "Oh, this should be changed, that should be changed, blah blah blah" and in the end, nothing ever gets done. A few months later, same discussion pops up. Same endless quicksand cycle. Year after year... We end up in quicksands with these kinds of myriad discussions. The best results in any and every case I've seen is when someone simply has a vision and just DOES it! Then says to the team "Whaddya think?" You get good feedback on concrete things to discuss rather than hypotheticals. You've mentioned this idea for a long time. Surely, by now you have an actual vision in mind. Show the team your vision even if its just mockups. That's the surefire way to move this forward. People want something tangible they can look at and comment on.
7 Change KDE splash screen to match Plymouth
I don't like things that match from bootup to desktop. You stare at the screen wondering if your desktop is ready and then moments later go "oh, it is ready, I didn't notice the change." I prefer that each stage have its own unique look and give truer distinction. And I know I'm not the only one who has felt this. Many people have expressed confusion.
8 Keep default splash screens for applications
This is good. 9. Yes I'm adding one here. The most important thing in the TODO list that didn't get mentioned. Creating a checklist of what needs to be done before release of 12.3. Sorry but, this past 12.2 release, was really bad in terms of timely artwork delivery. While several of us mentioned what needs to be done, no one responded and then at the last minute everyone scrambled. This checklist is the most important fundamental thing you need in order to plan and schedule tasks. And it should carry over to be re-used in future releases to refer to. As long as such a list is present, people can go in and check out do-able tasks. And contributors are frequently much more likely to respond to specific tasks rather than broad strategic discussions. Leaving out the list severely disenfranchises such contributors when we need them the most. 10. And one more... Focus on more results-oriented goals and deliverables. To be honest with you, my go-to guys to get some request filled out are Marcel, Richard and Victor. Those are the guys I know I can reliably count on to approach, hand in a concept to them, they'll work through it and usually in a few hours come back with an initial design which we can further tweak. That ability to respond and to understand the requestor's needs and deliver is a key component that will help make this team grow. There are lots and lots of artists worldwide who are not interested in strategic discussions. They just want to create. You make the team more inviting and easy-entry, and you'll get a LOT more Marcel's, Richard's and Victor's, I guarantee you that. Because people will want to go where their work is appreciated and desired. There's a huge amount of requests over the years that have gone unanswered because we simply don't have the broad breadth of talent we need to address various needs. That's something that needs to be worked on. Some of those that we get in the door may eventually evolve to handle bigger tasks and goals like the ones you have mentioned. But you gotta get them in the door first. :-) Bryen
Thank you Andy (anditosan)
-- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
On Oct 3, 2012, at 3:08 PM, Bryen M Yunashko wrote:
I have some grave concerns about the direction here, but also, I disagree that what is outlined here is actually about "12.3." This seems to be about a broader initiative that isn't 12.3 specific.
More below:
On Tue, 2012-10-02 at 20:28 -0600, Andres Silva wrote:
Given some of our member's suggestions, I have reviewed the list of do's for 12.3. Please read carefully and give a vote if you agree with the steps. If a majority agrees, we will start making the arrangements for these tasks to see the light.
1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily
This direction, as phrased, concerns me, but I think others have already addressed their concerns and I'd just be repeating…
Right, I do not think it is necessary to define such rules. Most important is that the format fits the type of images created (photos in raw or jpeg, drawn images in gimp, vector, or even large png's, etc.). Most everything will be cropped, edited somehow or converted in the end. It is very important that the final file use the right format and fulfill the technical needs of where it is to be displayed.
2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art
I personally dislike Flickr. And its size limitations per account have given some of us already a hard wall that we couldn't get out of without shelling some money out of our pocket. And because of the size limitations, posters will feel obligated to post a lesser-quality resolution in order to not run out of space.
But more importantly, I think we should use Flickr, and all other social network outlets as a place of recruitment, not as a repository. We should engage these artists when we see their works (whether on Flickr or Facebook or elsewhere) and encourage/mentor them how to be more directly active as a contributor to the Project. Having the Project function *outside* of its infrastructure is a good way to actually lose control in the long run. And people *will* come when they have a place they can feel they belong.
Naturally the flickr page is not a repository. It is only one source of contribution as well as a place for recruitment. The size limitations, in the end, do need play a role because we will define the necessary size needed for inclusion. Each pic will need to be checked before it is judged, asking the author directly if there is a larger size when necessary. Several years ago I started the flickr contest for Ubuntu. Look at what has come out of that and then try to find criticism - the results have been amazing and continue to be without any help. I do not understand your comment on how this is a way to lose control of the project. I do not see any risk nor have I experienced it in the many years I led the ubuntu art community. I will admit that many adamant open source folks would prefer an open platform - you can have that, or you can have a platform that can draw on many thousands of highly skilled artists. The choice seems simple.
3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc)
Unless you specifically hand it over to another entity, all works are automatically owned by the creator. So copyrights aren't really the concern here. And unlike some other projects, we don't really encourage copyright assignment. It is anathema, really.
What is more important is to understand sources within the artwork. We've had some cases where we thought the contributor completely created a piece, only to find out it was a compilation of components from other places. Contributors need to provide some kind of a trail so when artwork is selected to represent openSUSE, we know the actual history behind it. We need a way to inspect and verify, just like our OBS has an inspection process to ensure proper licensing.
I can understand your worries but in the end this will always be a risk no matter where the images come from. A picture search, asking for the original files and perhaps even making them sign some kind of code of conduct in which they promise not to "do bad things" can all help in mediating any legal issues for openSUSE. Again, I think that a good team and a solid leader would help solve these problems.
It would be serious egg in our face if someone created a wallpaper that we all loved and selected as our default, only to find out after release someone shouting "Hey!!! That image is from another place, you guys aren't orginal at all!" Even if that component was completely open-licensed, not knowing that a piece isn't original makes a world of difference.
Yes, I agree. That is why everything needs to be thoroughly checked in advance.
4 Change default font to OPEN SANS on KDE. (This font family is extensive and looks extra sharp on both KDE and GNOME, use full rgb subpixel rendering on KDE by default) Start with KDE first and then decide if it will work properly on Gnome
As already mentioned by others, I hope this is something you intend to discuss directly with those teams. We've already encountered in the past where members of those teams were upset with artwork team intruding on work that was already put into this and not even any prior dialogue before attempting to throw out their work for the artwork team's.
Some important political diplomacy is needed here before setting out on such initiatives.
I agree with this. It is not simply a matter of which font I think is best, there are other considerations such as how many scripts it supports. As for subpixel rendering, the display type defines what is best, not the font itself.
5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come)
I must have missed this discussion. The one I recall is the one Jos started with how to retain our beloved seasonal grub screen change. (The one where the Penguins are like lemmings across the top of the menu.) That is a very popular feature, and as Eugene pointed out, it is possible to restore that and even more, to provide *MORE* seasonal options. I would suggest make sure this popular feature is put back in before moving on to other ideas.
There is an accessibility problem with the basic screen we have now, and that should also be addressed. Providing some usability testing for important screens is something that needs to be considered. While I respect an artist's right to be creative wrt to their creations, the artwork team primarily functions as a service enhancement to the openSUSE product line.
What that means is while artwork should be awesome and beautiful, it should not interfere with the actual usage of the underlying product for our users, regardless of accessibility needs or otherwise.
I agree. Accessibility is always an important issue. What is shown on each step of getting to, and on the desktop needs to fulfill it's technical goal (showing boot progress, etc.) and be amazingly beautiful. I do not think that we can, at this time, determine how it should look or what design principles it should embody.
6. Change/improve styling on YAST
This isn't a 12.3-related subject. Unless you are proposing to do a restyling for every release? If so, that's a huge outlay of resources to reinvent the wheel every time.
But bottom line, I don't think this should be a team "TODO" but rather a "Just Do It." I'm not a 100% fan of that slogan, tbh, but in this case it is apropos. The biggest problem we have historically in communities like ours is everyone getting into a discussion "Oh, this should be changed, that should be changed, blah blah blah" and in the end, nothing ever gets done. A few months later, same discussion pops up. Same endless quicksand cycle. Year after year...
We end up in quicksands with these kinds of myriad discussions. The best results in any and every case I've seen is when someone simply has a vision and just DOES it! Then says to the team "Whaddya think?" You get good feedback on concrete things to discuss rather than hypotheticals.
You've mentioned this idea for a long time. Surely, by now you have an actual vision in mind. Show the team your vision even if its just mockups. That's the surefire way to move this forward. People want something tangible they can look at and comment on.
7 Change KDE splash screen to match Plymouth
I don't like things that match from bootup to desktop. You stare at the screen wondering if your desktop is ready and then moments later go "oh, it is ready, I didn't notice the change." I prefer that each stage have its own unique look and give truer distinction. And I know I'm not the only one who has felt this. Many people have expressed confusion.
Years ago, I tried to make suse use one look and feel throughout the entire system. I now think it is more important that every piece fits together somehow but not necessarily be "the same".
8 Keep default splash screens for applications
This is good.
Yes, I agree as well.
9. Yes I'm adding one here. The most important thing in the TODO list that didn't get mentioned. Creating a checklist of what needs to be done before release of 12.3. Sorry but, this past 12.2 release, was really bad in terms of timely artwork delivery. While several of us mentioned what needs to be done, no one responded and then at the last minute everyone scrambled. This checklist is the most important fundamental thing you need in order to plan and schedule tasks. And it should carry over to be re-used in future releases to refer to. As long as such a list is present, people can go in and check out do-able tasks.
And contributors are frequently much more likely to respond to specific tasks rather than broad strategic discussions. Leaving out the list severely disenfranchises such contributors when we need them the most.
10. And one more... Focus on more results-oriented goals and deliverables. To be honest with you, my go-to guys to get some request filled out are Marcel, Richard and Victor. Those are the guys I know I can reliably count on to approach, hand in a concept to them, they'll work through it and usually in a few hours come back with an initial design which we can further tweak.
That ability to respond and to understand the requestor's needs and deliver is a key component that will help make this team grow. There are lots and lots of artists worldwide who are not interested in strategic discussions. They just want to create. You make the team more inviting and easy-entry, and you'll get a LOT more Marcel's, Richard's and Victor's, I guarantee you that. Because people will want to go where their work is appreciated and desired.
There's a huge amount of requests over the years that have gone unanswered because we simply don't have the broad breadth of talent we need to address various needs. That's something that needs to be worked on.
Some of those that we get in the door may eventually evolve to handle bigger tasks and goals like the ones you have mentioned. But you gotta get them in the door first. :-)
-- Kenneth Wimer -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
First I'd like to say that I give Andy a lot of credit for sticking his neck out there and making an effort at starting a set of usable guidelines. We have some in place already and they could use a little work which I think he is getting a good start on.
1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily
I believe that submission for consideration can be in a raster format if the artist is comfortable with that however it is not a requirement. If the wallpaper needs to be in that format to be useful to the project then it is necessary to let the artists know that we appreciate all their contributions but they must know that any images to be usable as the default desktop will eventually need to be in this format or someone from the art team can convert the file for them with their permission if necessary.
2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art
The Flickr page is fine for people to have a place to submit their creations and the site itself is a good place to get publicity showing how we all contribute and work together as unified teams. This in itself is good publicity and draws attention for more contributors to want to get involved and contribute their own creations. Therefore I think Flickr definitely has its place. As a place for potential submission of release wallpaper? It can work for that if people choose to submit their work there, however I think these submissions should be separated into a page within openSUSE as Andy had done already http://en.opensuse.org/openSUSE:Wallpapers_12.2. If something is found on Flickr that another person "thinks" should be considered, write a comment to the artist asking if they will submit it to the wiki page for consideration if the work meets all the licensing and originality requirements. If the artist needs help with that then make every effort to help them or even do it for them.
Kenneth Wimer said I would suggest have a panel of "judges" to decide which images are selected. Having the whole community vote on something like this simply won't work well - trust me on this one, I have been >down that road several times with teams much larger than ours and it simply leads to too much useless discussion and lowers the quality of the images selected. The judges would rank each >picture. The ranking should be private and each judge would not be allowed to rank their own images. Also, we should rotate the judges every release.
I like this idea and would say that the judges should be no one from the art team as their opinion may be biased in one direction or another.
3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc)
This I totally agree on and believe that it should be very well explained and offer screenshot images of the licensing selection from each of the various image collection sites that we currently manage. Example would be a screenshot image of the licensing selection as would be appropriate on Flickr. If people can see exactly what radio button they should be selecting then there is little room for misunderstanding the first time around. We have to keep in mind that we are appealing to the world population which means the young to old and uneducated to genius.
5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come)
I think this idea is really cool since the circling balls during boot
has been well received. Or we could have a lizard that runs across the
screen as the loading bar, I don't know, I'm just throwing things out
there.
Ideally we want to make sure that the necessary information is made
available to anyone wishing to contribute in any way they wish. On the
other hand we don't want to come across as so restrictive no one wants
to get involved because we create such a "fine line" the process
required to contribute is no longer fun but overly restrictive and
confining.
On Tue, Oct 2, 2012 at 7:28 PM, Andres Silva
Given some of our member's suggestions, I have reviewed the list of do's for 12.3. Please read carefully and give a vote if you agree with the steps. If a majority agrees, we will start making the arrangements for these tasks to see the light.
1 Encourage the use of raster images for wallpaper (Using Flickr artwork pool to draw images) Add more places for submissions (email, social networks, etc) Use raster for the final wallpaper and not for its creation necessarily
2 Flickr is used, make sure that the uploader is responsible for the correct liscensing of the image (Provide information about branding people's artwork) Provide links for licensing images Follow up with creators for their work and how they licensed it Make a decision on what license works best for digital art
3 Create upload guidelines for artwork contributors (Although there are some guidelines about this, there is no specific place for copyright in the wiki) Create a wiki page for explaining licensing Promote licensing on our submission areas (Flickr, social networks, etc)
4 Change default font to OPEN SANS on KDE. (This font family is extensive and looks extra sharp on both KDE and GNOME, use full rgb subpixel rendering on KDE by default) Start with KDE first and then decide if it will work properly on Gnome
5 Change Plymouth to a progress bar with a sparkling end (per request of some contributors and to keep a simple elegant understanding of the boot process, more details to come)
6. Change/improve styling on YAST
7 Change KDE splash screen to match Plymouth
8 Keep default splash screens for applications
Thank you Andy (anditosan) -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
-- God bless ! Scott DuBois www.ROGUEHORSE.com openSUSE -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
participants (4)
-
Andres Silva -
Bryen M Yunashko -
DuBois, Scott L. -
Kenneth Wimer