[ubuntu-art] Getting something done

Justin Dugger jldugger at gmail.com
Tue Aug 5 21:00:28 BST 2008


On Tue, Aug 5, 2008 at 5:23 AM, SzerencseFia <szerencsefia at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Matthew Nuzum wrote:
>> On Thu, Jul 31, 2008 at 12:32 PM, Kenneth Wimer <kwwii at ubuntu.com> 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



More information about the ubuntu-art mailing list