Re: [opensuse-artwork] 12.3 (and beyond) To-Do list (was Re: Regular Meetings Proposal)
1 Jan
2013
1 Jan
'13
20:34
>>> Andres Silva 01/01/13 6:39 PM >>> >> 5. SUSEgreeter - Still using 12.2 design in factory. Needs to be updated. (Might be derived from something else as I see it in my working folder but not in github) > >I do not know how to package or get sources ready for this particular >package but I am working on a design mockup for it taking influences >from the grow design. (Posting soon) I am going to try and say this in the most delicate way possible. If you don't know how to package or get sources ready, then I'd suggest you learn. Without those skills, you are going to be hindered in two regards. Firstly, you are going to be reliant on the generosity of others to turn your ideas into reality, and this is both to the misfortune of yourself (who will therefore be less likely to see those ideas become reality) and those helping you (it's always much harder turning someone elses ideas into production than your own) Secondly, without an understanding of what the distribution requires, you will not be producing anything we can actually use.. and it's problems like that which have concerned me greatly over the last 12 months and something we really need to put an end to if this 'Artwork Team' are going to evolve into a productive unit, rather than a discussive one. On Tue, Jan 1, 2013 at 7:11PM, Andres Silva wrote: >http://i1108.photobucket.com/albums/h414/anditosan/SUSE-Greeter_zps0029edf5.png And this is what I'm talking about..how does this flat PNG help us exactly? The SUSEgreeter componant in the main branding package is an svg of the *background* https://github.com/openSUSE/branding/tree/12.3/kde-workspace/SUSEgreeter (Yes, I didn't know this earlier today, I learned by poking around parts of that github tree I normally avoid) Your PNG is in the wrong file format, and has static text and images which will likely conflict with the actual code for SUSEgreeter, which I believe is in the package kdebase4-openSUSE which can be found here: https://build.opensuse.org/package/show?package=kdebase4-openSUSE&project=KDE%3ADistro%3AFactory (I'm not sure, but a quick google around has pointed me in this direction - I'm learning too, thats how these things are learned) Please, feel free to learn how SUSEgreeter works, please feel free to change it so your concept can become reality, but with the time left before 12.3 needs to be ready, our collective resolution for the new year really has to be one of 'getting stuff done', not posting very pretty concepts in the hope that someone else can do the work for you -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
5 Jan
5 Jan
18:37
New subject: [opensuse-artwork] 12.3 (and beyond) To-Do list (was Re: Regular Meetings Proposal)
On Tue, 01 Jan 2013 20:34:58 +0000 "Richard Brown"wrote: > >>> Andres Silva 01/01/13 6:39 PM >>> > >> 5. SUSEgreeter - Still using 12.2 design in factory. Needs to be > >> updated. (Might be derived from something else as I see it in my > >> working folder but not in github) > > > >I do not know how to package or get sources ready for this particular > >package but I am working on a design mockup for it taking influences > >from the grow design. (Posting soon) > > > If you don't know how to package or get sources ready, then I'd > suggest you learn. Without those skills, you are going to be hindered > in two regards. Firstly, you are going to be reliant on the > generosity of others to turn your ideas into reality, and this is > both to the misfortune of yourself (who will therefore be less likely > to see those ideas become reality) and those helping you (it's always > much harder turning someone elses ideas into production than your > own) Don't get me wrong Richard, but your suggestions require to abolish collaboration and let everyone learn every detail of distro, before one can publish anything. You speak about generosity of others like that is benefit of artist alone. I don't see there any notion that any work in software creation and publishing process should be shared between those that know technical part, workflow, commands, and those that can produce beautiful art. Look at software translations, they are far ahead with friendliness to translators, and should be used as idea how to organize collaboration of artists. Translators don't chase strings within source code and submit patches. They have strings isolated in a file that once translation is done and published, strings will auto-magically find its place. IMHO, the most one should require from an artist is: * size of an image, * adherence to general idea for theme, * adherence to principle that make, for instance, good wallpaper, * in some cases on can require certain format, raster or vector graphics. Asking to: * research on its own requirements for an image * details of publishing process is over the top for almost all artist that have any success in art. Research, even with links that you gave and which are great help to get started, it is still quite some work, that includes: * learning git * learning github * learning how OBS is using github, * learning OBS, * learning osc, * learning packaging, * learn to read software sources, * learn every coding language, that one might stumble upon, * learn workarounds for script, packaging, and software deficiencies that one might stumble upon. The other option is that one with right ideas comes up with process that will require from artist to upload images to dedicated server, and let other that are better at coding and packaging put that in right place. Of course that doesn't mean that they should disassemble png mockup in separate files. Providing images that software requires is still artist responsibility, but research what software requires is not. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse-artwork+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-artwork+owner@opensuse.org
4127
Age (days ago)
4131
Last active (days ago)
1 comments
2 participants
participants (2)
-
Rajko
-
Richard Brown