Re: [ubuntu-art] Getting something done

2008-08-05 Thread Justin Dugger
On Tue, Aug 5, 2008 at 3:06 PM, Salane Ashcraft <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 5, 2008 at 3:00 PM, Justin Dugger <[EMAIL PROTECTED]> wrote:
>> On Tue, Aug 5, 2008 at 5:23 AM, SzerencseFia <[EMAIL PROTECTED]> wrote:
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Matthew Nuzum wrote:
 On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <[EMAIL PROTECTED]> wrote:
>> I see your point. Just to make it clear what I meant at the first place,
>> the first hurdle is my lack of understanding on:
>> - what are the needed steps on the process I have read about on this 
>> list;
>> - what should I do after I have made (let's say) a gtk2 theme and I want
>> to contribute with it and it is uploaded on wiki site;
>> - what to read that is short and gives answers without having to read
>> couple of hundreds of posts mostly unnecessarily commented and off of
>> the original subject;
>> - and final to learn something what worked and no need to re-develop to
>> reach the goal.
>>
>> These is the frame, these are minimal understanding on what it takes to
>> complete the target per my knowledge.

> If, however, we need an overview of the whole process, feel free to write
> away :-)
>>>
>>> Okay, in short here is what I understood and follow so far:
>>>
>>> 1. Moke-up the idea.
>>> 1.a (optional) inform the list on your idea to get some useful input.
>>> 2. Make the first beta.
>>> 3. Create preferable an Ubuntu-wiki or Launchpad page for the project.
>>> 4. Upload the project on the site.
>>> 5. Bug hunting.
>>> 6. Bug fixing.
>>> 7. Pack the stable version and upload it to the proper site.
>>>
>>> What do ya think about this checklist?
>>
>> Very nearly perfect, but I do wish somehow that more team building
>> were part of it, and maybe more research.  I see lots of mockups that
>> never move from 1 to 2 because they require forking gtk or GNOME.
>>
>> Justin Dugger
>>
>> --
>> ubuntu-art mailing list
>> ubuntu-art@lists.ubuntu.com
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-art
>>
>
>
> How many times has someone tried to organize the team?

We don't need to organize "the team". Just "a team" is sufficient.

>More than should have had to happen.

Indeed I've tried to do just such a thing, and the apparent failure
(thus far) is due to my own inadequate research. I need to figure out
how to get stuff done on my own before I lead others to help on a
common goal.

Justin Dugger

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-08-05 Thread Salane Ashcraft
On Tue, Aug 5, 2008 at 3:00 PM, Justin Dugger <[EMAIL PROTECTED]> wrote:
> On Tue, Aug 5, 2008 at 5:23 AM, SzerencseFia <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Matthew Nuzum wrote:
>>> On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <[EMAIL PROTECTED]> wrote:
> I see your point. Just to make it clear what I meant at the first place,
> the first hurdle is my lack of understanding on:
> - what are the needed steps on the process I have read about on this list;
> - what should I do after I have made (let's say) a gtk2 theme and I want
> to contribute with it and it is uploaded on wiki site;
> - what to read that is short and gives answers without having to read
> couple of hundreds of posts mostly unnecessarily commented and off of
> the original subject;
> - and final to learn something what worked and no need to re-develop to
> reach the goal.
>
> These is the frame, these are minimal understanding on what it takes to
> complete the target per my knowledge.
>>>
 If, however, we need an overview of the whole process, feel free to write
 away :-)
>>
>> Okay, in short here is what I understood and follow so far:
>>
>> 1. Moke-up the idea.
>> 1.a (optional) inform the list on your idea to get some useful input.
>> 2. Make the first beta.
>> 3. Create preferable an Ubuntu-wiki or Launchpad page for the project.
>> 4. Upload the project on the site.
>> 5. Bug hunting.
>> 6. Bug fixing.
>> 7. Pack the stable version and upload it to the proper site.
>>
>> What do ya think about this checklist?
>
> Very nearly perfect, but I do wish somehow that more team building
> were part of it, and maybe more research.  I see lots of mockups that
> never move from 1 to 2 because they require forking gtk or GNOME.
>
> Justin Dugger
>
> --
> ubuntu-art mailing list
> ubuntu-art@lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-art
>


How many times has someone tried to organize the team? More than
should have had to happen.
-- 
Salane Ashcraft
[EMAIL PROTECTED]

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-08-05 Thread Justin Dugger
On Tue, Aug 5, 2008 at 5:23 AM, SzerencseFia <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Matthew Nuzum wrote:
>> On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <[EMAIL PROTECTED]> wrote:
 I see your point. Just to make it clear what I meant at the first place,
 the first hurdle is my lack of understanding on:
 - what are the needed steps on the process I have read about on this list;
 - what should I do after I have made (let's say) a gtk2 theme and I want
 to contribute with it and it is uploaded on wiki site;
 - what to read that is short and gives answers without having to read
 couple of hundreds of posts mostly unnecessarily commented and off of
 the original subject;
 - and final to learn something what worked and no need to re-develop to
 reach the goal.

 These is the frame, these are minimal understanding on what it takes to
 complete the target per my knowledge.
>>
>>> If, however, we need an overview of the whole process, feel free to write
>>> away :-)
>
> Okay, in short here is what I understood and follow so far:
>
> 1. Moke-up the idea.
> 1.a (optional) inform the list on your idea to get some useful input.
> 2. Make the first beta.
> 3. Create preferable an Ubuntu-wiki or Launchpad page for the project.
> 4. Upload the project on the site.
> 5. Bug hunting.
> 6. Bug fixing.
> 7. Pack the stable version and upload it to the proper site.
>
> What do ya think about this checklist?

Very nearly perfect, but I do wish somehow that more team building
were part of it, and maybe more research.  I see lots of mockups that
never move from 1 to 2 because they require forking gtk or GNOME.

Justin Dugger

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-08-05 Thread SzerencseFia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Matthew Nuzum wrote:
> On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <[EMAIL PROTECTED]> wrote:
>>> I see your point. Just to make it clear what I meant at the first place,
>>> the first hurdle is my lack of understanding on:
>>> - what are the needed steps on the process I have read about on this list;
>>> - what should I do after I have made (let's say) a gtk2 theme and I want
>>> to contribute with it and it is uploaded on wiki site;
>>> - what to read that is short and gives answers without having to read
>>> couple of hundreds of posts mostly unnecessarily commented and off of
>>> the original subject;
>>> - and final to learn something what worked and no need to re-develop to
>>> reach the goal.
>>>
>>> These is the frame, these are minimal understanding on what it takes to
>>> complete the target per my knowledge.
> 
>> If, however, we need an overview of the whole process, feel free to write
>> away :-)

Okay, in short here is what I understood and follow so far:

1. Moke-up the idea.
1.a (optional) inform the list on your idea to get some useful input.
2. Make the first beta.
3. Create preferable an Ubuntu-wiki or Launchpad page for the project.
4. Upload the project on the site.
5. Bug hunting.
6. Bug fixing.
7. Pack the stable version and upload it to the proper site.

What do ya think about this checklist?

- --
Cheers, Erno [szerencsefia]
- ---
Home: http://www.szerencsefia.webs.com/
WhoIs https://wiki.ubuntu.com/SzerencseFia
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFImCoXuMODVs5J2pwRAhG2AKCRPRHwC3GbMJJjBWjX6qwJ5/SSGACgimBe
AvsBMHhqibzGixirI5iYT7s=
=fJx6
-END PGP SIGNATURE-

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-31 Thread Matthew Nuzum
On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <[EMAIL PROTECTED]> wrote:
>> I see your point. Just to make it clear what I meant at the first place,
>> the first hurdle is my lack of understanding on:
>> - what are the needed steps on the process I have read about on this list;
>> - what should I do after I have made (let's say) a gtk2 theme and I want
>> to contribute with it and it is uploaded on wiki site;
>> - what to read that is short and gives answers without having to read
>> couple of hundreds of posts mostly unnecessarily commented and off of
>> the original subject;
>> - and final to learn something what worked and no need to re-develop to
>> reach the goal.
>>
>> These is the frame, these are minimal understanding on what it takes to
>> complete the target per my knowledge.

> If, however, we need an overview of the whole process, feel free to write
> away :-)

Just to be sure, if your questions are about creating art-work
packages, start with this:
https://lists.ubuntu.com/archives/ubuntu-art/2008-July/007043.html
(posted just a couple days ago)

If your question is about something else let the team know more
specifically what you'd like to do. Or if you're just suggesting we
write a book on how to participate in the art-team - it's a good idea
but will probably have to get done at a later time.

Sorry for being gruff in my previous reply.

-- 
Matthew Nuzum
newz2000 on freenode

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-31 Thread Kenneth Wimer
On Thursday 31 July 2008 19:08:52 SzerencseFia wrote:
> Matthew Nuzum wrote:
> > On Wed, Jul 30, 2008 at 4:17 AM, SzerencseFia <[EMAIL PROTECTED]> 
wrote:
> >> On my opinion Who, you should share in a form of list the necessary
> >> steps in correct sequence on the entire process you made successfully.
> >> It is important to achieve the same target you did on a workable way. In
> >> fact it does not limit to achieve the target *only* on that way.
> >
> > No, that's wrong. You should try to do it based on the information
> > already posted to this list (some good stuff within the last 7 days)
> > and when you run into a hurdle you should ask for help.
>
> I see your point. Just to make it clear what I meant at the first place,
> the first hurdle is my lack of understanding on:
> - what are the needed steps on the process I have read about on this list;
> - what should I do after I have made (let's say) a gtk2 theme and I want
> to contribute with it and it is uploaded on wiki site;
> - what to read that is short and gives answers without having to read
> couple of hundreds of posts mostly unnecessarily commented and off of
> the original subject;
> - and final to learn something what worked and no need to re-develop to
> reach the goal.
>
> These is the frame, these are minimal understanding on what it takes to
> complete the target per my knowledge.
>
> Without making anyone wrong I definitely think team work means more then
> giving some advices when one is already stocked. I have hardly found on
> this list team activity for real only between few active guys, but I
> found a lots of stops and smart opinions why some idea is wrong and
> giving no solution to improve it but only stopping it.
>
> I still think to write an overview in few steps (in maybe 10-15 lines)
> as a checklist would help a lot to "n00bs" like me who is more an artist
> then a coder.
>
> In this way, for dude like me would have a chance to make something
> useful for the community I belong too and fast but without having to
> spend huge amount valuable time to contribute.

As every package is different and changes over time it is very hard to write 
such documentation. Note that there are quite a few wiki pages which can help 
(ie that is how I figured out how to do this stuff, that and talking to 
people). I once wrote a wiki page explaining exactly what to do to use the 
automatic artwork builder but nobody (not one person) used it so we removed 
the system (with ppa's you don't need it anyway). My point is that the 
information is available and if anyone wants help doing it there are people 
to ask questions.

It's kinda like trying to make a "how to make icons" tutorial, once you've 
written it you figure out that you've only covered one case and the 
information is hardly more than an overview.

If, however, we need an overview of the whole process, feel free to write 
away :-)

--
Ken

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-31 Thread SzerencseFia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Matthew Nuzum wrote:
> On Wed, Jul 30, 2008 at 4:17 AM, SzerencseFia <[EMAIL PROTECTED]> wrote:
>> On my opinion Who, you should share in a form of list the necessary
>> steps in correct sequence on the entire process you made successfully.
>> It is important to achieve the same target you did on a workable way. In
>> fact it does not limit to achieve the target *only* on that way.
>>
> 
> No, that's wrong. You should try to do it based on the information
> already posted to this list (some good stuff within the last 7 days)
> and when you run into a hurdle you should ask for help.
> 

I see your point. Just to make it clear what I meant at the first place,
the first hurdle is my lack of understanding on:
- - what are the needed steps on the process I have read about on this list;
- - what should I do after I have made (let's say) a gtk2 theme and I want
to contribute with it and it is uploaded on wiki site;
- - what to read that is short and gives answers without having to read
couple of hundreds of posts mostly unnecessarily commented and off of
the original subject;
- - and final to learn something what worked and no need to re-develop to
reach the goal.

These is the frame, these are minimal understanding on what it takes to
complete the target per my knowledge.

Without making anyone wrong I definitely think team work means more then
giving some advices when one is already stocked. I have hardly found on
this list team activity for real only between few active guys, but I
found a lots of stops and smart opinions why some idea is wrong and
giving no solution to improve it but only stopping it.

I still think to write an overview in few steps (in maybe 10-15 lines)
as a checklist would help a lot to "n00bs" like me who is more an artist
then a coder.

In this way, for dude like me would have a chance to make something
useful for the community I belong too and fast but without having to
spend huge amount valuable time to contribute.

- --
Cheers, Erno [szerencsefia]
http://www.szerencsefia.webs.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIkfGkuMODVs5J2pwRAhcvAKCngAHe0jChDw+87gCK5X+gciTk0ACeOqPl
+QTczev1ZOCtk2it7XVT8lI=
=W78r
-END PGP SIGNATURE-


pgpkeys.asc
Description: application/pgp-keys
-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-30 Thread Matthew Nuzum
On Wed, Jul 30, 2008 at 4:17 AM, SzerencseFia <[EMAIL PROTECTED]> wrote:
> On my opinion Who, you should share in a form of list the necessary
> steps in correct sequence on the entire process you made successfully.
> It is important to achieve the same target you did on a workable way. In
> fact it does not limit to achieve the target *only* on that way.
>

No, that's wrong. You should try to do it based on the information
already posted to this list (some good stuff within the last 7 days)
and when you run into a hurdle you should ask for help.

-- 
Matthew Nuzum
newz2000 on freenode

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-30 Thread SzerencseFia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Who wrote:
> On Thu, Jul 24, 2008 at 7:35 PM, Cory K. <[EMAIL PROTECTED]> wrote:
>> Matthew Nuzum wrote:
>>> For
>>> example, "Who" has been very active on the list lately and he is one
>>> of the people who achieved this goal a few releases ago. And he didn't
>>> even have PPAs available for his project! As a matter of fact, you can
>>> benefit from his hard work by starting with the bluebuntu source
>>> package and using it as the base for your own theme.
> 
> Giving credit where due, Frank Schoep and Daniel Holbach managed the
> packaging, I did the other bits :)
> 
>> Actually, example-look is better as Ubuntu Studio made it's initial art
>> packages from it. Improved it, then gave the changes back to example-look.
> 
> Alongside ExampleLook as an example of packaging there is the Blubuntu
> Wiki which is still around - that gives a nice idea of how we got
> everything together for design. It isn't the best way to do it, but it
> did work... Maybe you can take some ideas from it, or even save
> yourself some time by just using it as a template (find and replace
> Blubuntu and you'll have a good generic template, I reckon...)
> 
> https://wiki.ubuntu.com/Artwork/Incoming/Blubuntu
> 
> Everything else I would say about getting stuff done is here
> 
> https://lists.ubuntu.com/archives/ubuntu-art/2008-April/005837.html
> 
> Ken's response suggests that he agreed then, not sure if he still does...
> 

On my opinion Who, you should share in a form of list the necessary
steps in correct sequence on the entire process you made successfully.
It is important to achieve the same target you did on a workable way. In
fact it does not limit to achieve the target *only* on that way.

- --
Cheers, Erno [szerencsefia]
http://www.szerencsefia.webs.com/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIkDGWuMODVs5J2pwRAjPgAJ9sUkbNYWdXxyPtb04a9C456rWCjACaAlZX
znubgFFRO6IK0mt7I1j3ubI=
=Jw+J
-END PGP SIGNATURE-

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-29 Thread Nemes Sorin
Kenneth,

that is what I talk about, few times ago, here on this forum ..this kind 
of "pro-cons" keep me out a bit,  being ... somewhat disappointed.

I prefer to work quick - on clear objectives - on a recent post I 
reaffirmed idea of 'teams' with different objectives - but on a common, 
planned, concentrated effort...  No  any response ;) on subject.

Here too much pro and contra and bla-bla.

So maybe the best thing is to organize spaces ( being on Bazaar or 
Launchpad ) for various kind of tasks and who  wanna do something - they 
can go on the specific place.

...

The best thing you can do now - is to request a response form members ( 
just informal ) - which one - where can help with his / her expertize / 
skills. This way you can have a better idea  about who can really help 
with something and who just talk. Just in case. Peoples with skills will 
help - but is hard for them to self organize things here because they 
come after their work hours and they expect to see something clear to 
follow - not to get more nerves.

Anyway, following discussions here - from time to time - I can see some 
progress - slow but visible - last months peoples start to create 
materials - and they get better. But i'm afraid this process is too slow 
to be ready on time.



Kenneth Wimer wrote:
> Hi all,
>
> I've had my head up a time-zone map for the last couple of days (it went so 
> far as to require a new computer). Sorry if it seemed like I was gone, I was 
> really there but just acting like a zombie...mockups made in free time this 
> weekend coming soon :-)
>
> I'd like to touch on a few issues directly in response to the general 
> discussion, not all of which were included in this thread but all of which 
> are certainly pertainant to the matter.
>
> I use the word artwork later, it almost hurts me to do so. What we lack, more 
> than anything else, is the framework to do something amazing.
>
> The art teams goal is to produce artwork which one can use in ubuntu. 
> Basically, this means creating installable debian packages for ubuntu linux 
> which include artwork and configuration information to create a distinct look 
> and feel based on the technical possibilities/limitations. Usually, in order 
> to do this as a team you'll need to do it all with launchpad.net and bazaar 
> (bzr)
>
> Because there is a big difference between the various jobs you'll almost 
> certainly need to do it by coordinating your efforts with others. To this 
> end, the idea of theme teams arose in which the community can bridge the gap 
> between proposing random ideas and working as a team(s) on specific 
> ideas/goals.
>
> As stated on the FAQ (http://wiki.ubuntu.com/Artwork/FAQ) the default artwork 
> is decided by the Canonical management team. The community can work on new 
> ideas for the default artwork but should not expect to make any final 
> decisions. Parts of the default artwork currently in Hardy are community 
> efforts. Part of my job at Canonical is to be the official voice for the 
> company in relation to artwork matters.
>
> As Salane has mentioned, creating coordinated efforts to change parts of the 
> default look *is* possibleit is just really, really hard for many 
> reasons :-) 
>
> Defining an artistic direction would greatly increase the productivity of 
> talented artists, talented artists are what we lack most of, funny how that 
> works, eh?
>
> In the meantime an interesting wallpaper idea is probably the best way to 
> start, but don't tell anyone I said that, it defies the whole idea of 
> artistic direction. Reality meets "the-way-things-should-be".Fight the evil 
> spirits and overcome those who defy you (based on a very conservative 
> assumption of what is currently technically possible).
>
> Basically, you have to do the same thing as a theme team does, even if only 
> for one specific aspect of the current theme. Show your ideas by actuallythe 
> producing something.
>
> I would add that you'd also need to accept that radical change is only going 
> to happen in the rarest of exceptions and to be willing to listen to 
> criticism (whether you agree or not, and more importantly in many cases, 
> whether you understand exactly what is meant or not) and act upon it in a 
> productive manner.
>
> There is a big difference between random discussion and doing something which 
> proves your necessity, skill/talent, willingness to stay on the train for the 
> whole ride and serve drinks, whatever. This is the necessary first step.
>
> We've tried for a while now to revive art.ubuntu.com but little has happened, 
> it got stuck in code review and is forevermore lost :-) I suggest using 
> ubuntu-art.org for general submissions. The person who runs it is a friend of 
> mine, so there shouldn't be any problems. We can, as desired, reserve the 
> wiki for serious theme team proposals and work in progress.
>
> On Thursday 24 July 2008 20:25:47 Matthew Nuzum wrote:
>   
>

Re: [ubuntu-art] Getting something done

2008-07-26 Thread Kenneth Wimer
Hi all,

I've had my head up a time-zone map for the last couple of days (it went so 
far as to require a new computer). Sorry if it seemed like I was gone, I was 
really there but just acting like a zombie...mockups made in free time this 
weekend coming soon :-)

I'd like to touch on a few issues directly in response to the general 
discussion, not all of which were included in this thread but all of which 
are certainly pertainant to the matter.

I use the word artwork later, it almost hurts me to do so. What we lack, more 
than anything else, is the framework to do something amazing.

The art teams goal is to produce artwork which one can use in ubuntu. 
Basically, this means creating installable debian packages for ubuntu linux 
which include artwork and configuration information to create a distinct look 
and feel based on the technical possibilities/limitations. Usually, in order 
to do this as a team you'll need to do it all with launchpad.net and bazaar 
(bzr)

Because there is a big difference between the various jobs you'll almost 
certainly need to do it by coordinating your efforts with others. To this 
end, the idea of theme teams arose in which the community can bridge the gap 
between proposing random ideas and working as a team(s) on specific 
ideas/goals.

As stated on the FAQ (http://wiki.ubuntu.com/Artwork/FAQ) the default artwork 
is decided by the Canonical management team. The community can work on new 
ideas for the default artwork but should not expect to make any final 
decisions. Parts of the default artwork currently in Hardy are community 
efforts. Part of my job at Canonical is to be the official voice for the 
company in relation to artwork matters.

As Salane has mentioned, creating coordinated efforts to change parts of the 
default look *is* possibleit is just really, really hard for many 
reasons :-) 

Defining an artistic direction would greatly increase the productivity of 
talented artists, talented artists are what we lack most of, funny how that 
works, eh?

In the meantime an interesting wallpaper idea is probably the best way to 
start, but don't tell anyone I said that, it defies the whole idea of 
artistic direction. Reality meets "the-way-things-should-be".Fight the evil 
spirits and overcome those who defy you (based on a very conservative 
assumption of what is currently technically possible).

Basically, you have to do the same thing as a theme team does, even if only 
for one specific aspect of the current theme. Show your ideas by actuallythe 
producing something.

I would add that you'd also need to accept that radical change is only going 
to happen in the rarest of exceptions and to be willing to listen to 
criticism (whether you agree or not, and more importantly in many cases, 
whether you understand exactly what is meant or not) and act upon it in a 
productive manner.

There is a big difference between random discussion and doing something which 
proves your necessity, skill/talent, willingness to stay on the train for the 
whole ride and serve drinks, whatever. This is the necessary first step.

We've tried for a while now to revive art.ubuntu.com but little has happened, 
it got stuck in code review and is forevermore lost :-) I suggest using 
ubuntu-art.org for general submissions. The person who runs it is a friend of 
mine, so there shouldn't be any problems. We can, as desired, reserve the 
wiki for serious theme team proposals and work in progress.

On Thursday 24 July 2008 20:25:47 Matthew Nuzum wrote:
> On Thu, Jul 24, 2008 at 1:03 PM, Salane Ashcraft <[EMAIL PROTECTED]> wrote:
> > Its just I hear stuff from people who have been here long, but what
> > have they done? Ken himself has said the art team needs to prove
> > itself to be trusted with anything substantial.
>
> In order for this team to have a success this time around, one person
> needs to take ownership of a project (a theme) and ensure that
> whatever needs to be done in order to get it complete and installable
> gets done.

Right, this has been what we want to achieve for quite some time now. Groups 
of people working towards their own goal(s). Talents from one team benefit 
others, more gets done and it becomes easier for everyone. Get something real 
out there, that is the whole point, or? 

> There are very few people who can create all of the graphical elements
> of a theme AND package it AND get it ready for distribution. But
> that's ok because one person doesn't need to *do* all of that. They
> just need to be tenacious enough to get it done, asking for help where
> necessary. As a matter of fact, the right person may not be able to do
> any of the tasks other than being able to get something done.
>
> It is a challenge but people on this list have accomplished it. For
> example, "Who" has been very active on the list lately and he is one
> of the people who achieved this goal a few releases ago. And he didn't
> even have PPAs available for his project! As a matter o

Re: [ubuntu-art] Getting something done

2008-07-24 Thread Cory K.
Who wrote:
> Whopsie, PingunZ made the GDM from my images. Sorry PingunZ!
>   

Something someone who *actually cares* to move their theme/idea forward
to they packaging stage should learn when they dig through the example
of your package. :)

BTW, when are you gonna update Blubuntu? :P

/me runs.

-Cory \m/

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-24 Thread Who
On Thu, Jul 24, 2008 at 7:49 PM, Who <[EMAIL PROTECTED]> wrote:
> On Thu, Jul 24, 2008 at 7:35 PM, Cory K. <[EMAIL PROTECTED]> wrote:
>> Matthew Nuzum wrote:
>>> For
>>> example, "Who" has been very active on the list lately and he is one
>>> of the people who achieved this goal a few releases ago. And he didn't
>>> even have PPAs available for his project! As a matter of fact, you can
>>> benefit from his hard work by starting with the bluebuntu source
>>> package and using it as the base for your own theme.
>
> Giving credit where due, Frank Schoep and Daniel Holbach managed the
> packaging, I did the other bits :)
>
Whopsie, PingunZ made the GDM from my images. Sorry PingunZ!

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-24 Thread Who
On Thu, Jul 24, 2008 at 7:35 PM, Cory K. <[EMAIL PROTECTED]> wrote:
> Matthew Nuzum wrote:
>> For
>> example, "Who" has been very active on the list lately and he is one
>> of the people who achieved this goal a few releases ago. And he didn't
>> even have PPAs available for his project! As a matter of fact, you can
>> benefit from his hard work by starting with the bluebuntu source
>> package and using it as the base for your own theme.

Giving credit where due, Frank Schoep and Daniel Holbach managed the
packaging, I did the other bits :)

>
> Actually, example-look is better as Ubuntu Studio made it's initial art
> packages from it. Improved it, then gave the changes back to example-look.

Alongside ExampleLook as an example of packaging there is the Blubuntu
Wiki which is still around - that gives a nice idea of how we got
everything together for design. It isn't the best way to do it, but it
did work... Maybe you can take some ideas from it, or even save
yourself some time by just using it as a template (find and replace
Blubuntu and you'll have a good generic template, I reckon...)

https://wiki.ubuntu.com/Artwork/Incoming/Blubuntu

Everything else I would say about getting stuff done is here

https://lists.ubuntu.com/archives/ubuntu-art/2008-April/005837.html

Ken's response suggests that he agreed then, not sure if he still does...

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Getting something done

2008-07-24 Thread Cory K.
Matthew Nuzum wrote:
> For
> example, "Who" has been very active on the list lately and he is one
> of the people who achieved this goal a few releases ago. And he didn't
> even have PPAs available for his project! As a matter of fact, you can
> benefit from his hard work by starting with the bluebuntu source
> package and using it as the base for your own theme.

Actually, example-look is better as Ubuntu Studio made it's initial art
packages from it. Improved it, then gave the changes back to example-look.

> If in doubt, ask
> for help either here or the MOTUs.
>   

There will be little help there. Though it's still worth a try. Ken
can't even get help with the *official* art packages. :P

-Cory K.


-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


[ubuntu-art] Getting something done

2008-07-24 Thread Matthew Nuzum
On Thu, Jul 24, 2008 at 1:03 PM, Salane Ashcraft <[EMAIL PROTECTED]> wrote:
> Its just I hear stuff from people who have been here long, but what
> have they done? Ken himself has said the art team needs to prove
> itself to be trusted with anything substantial.

In order for this team to have a success this time around, one person
needs to take ownership of a project (a theme) and ensure that
whatever needs to be done in order to get it complete and installable
gets done.

There are very few people who can create all of the graphical elements
of a theme AND package it AND get it ready for distribution. But
that's ok because one person doesn't need to *do* all of that. They
just need to be tenacious enough to get it done, asking for help where
necessary. As a matter of fact, the right person may not be able to do
any of the tasks other than being able to get something done.

It is a challenge but people on this list have accomplished it. For
example, "Who" has been very active on the list lately and he is one
of the people who achieved this goal a few releases ago. And he didn't
even have PPAs available for his project! As a matter of fact, you can
benefit from his hard work by starting with the bluebuntu source
package and using it as the base for your own theme. If in doubt, ask
for help either here or the MOTUs.

-- 
Matthew Nuzum
newz2000 on freenode

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art