Re: Re: [Opie-cvs] opie/library locationcombo.cpp, 1.1 locationcombo.h, 1.1 global.cpp, 1.29 global.h, 1.4 library.pro, 1.37 qlibrary_unix.cpp, 1.8 timestring.cpp, 1.8 timestring.h, 1.6

Guys, from my point of view, we need to commit the code as good as we 
can to give the rest of the Linux users chance to test our contributions.
Again, we need a consensus on WHAT WE ARE GOING TO DO. If we decide that 
the whole tree reorganization will help us, let's do this.
But I really don't like two things:
1. A position like "everything is ugly, everything sucks, everything 
must be completely done from the scratch, but I'm to busy to do this".
2. Arguments like "it sucks, I hate this".
I think if we want to make a good and really working system, we need:
1. What and why we are going to do.
2. Decide who will do this (have time, strenghts, etc.)
Let's try to do this.
Lorn, I'm waiting for your e-mail to the list with your proposals.

Dmitriy

P.S. Guys, I need to inform you that next week (may be more) I have to 
spend in the hospital.
See you.

Michael 'Mickey' Lauer wrote:

>>not at all random, but trying to get libqpe up to date and more 
>>compatible with Qtopia.
>>    
>>
>[...]
>  
>
>>When has HEAD _ever_ been known as the stable tree on any project?
>>    
>>
>
>Upgrading libqpe sounds good in theory, but it would have been better to
>have branched before that. Since we don't have a development branch in
>Opie, HEAD _is_ the stable tree in this project. Feel free to dig it up
>in the mailing list archives, if you forgot on what we agreed after
>merging development and stable branches.
>
>  
>
>>>Opie development may be effectively dead,
>>>      
>>>
>>Then why does it matter to you and why bring this up, if you or everyone 
>>else is not interested in developing Opie?
>>    
>>
>
>Because it is still an important environment option for embedded linux
>distributions like OpenZaurus, Familiar Linux, and Angstrom.
>
>  
>
>>I am, and I am going to proceed with changes I see fit, otherwise I will 
>>simply start my own project, and make changes there as I see fit.
>>    
>>
>
>Ok, if you insist on doing these things on HEAD, then a stable branch is
>necessary. If your planned changes are huge, I recommend starting a
>completely new Opie repository. It would be a good chance to clean up
>the build system and infrastructure and remove the core/noncore split.
>
>  
>
>>You don't have to agree with my changes, I certainly do not agree with 
>>all the changes everyone has made, but I did not cause a stink because 
>>whoever developer wanted them in.
>>    
>>
>
>I don't know how you manage your contributions to other open source
>projects, but until now this project has been based on consensus. Feel
>free to dig in the opie-dev archives, major changes have been discussed
>before they went in.
>
>  
>
_______________________________________________

http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex

Opie-devel mailing list
[email protected]
https://handhelds.org/mailman/listinfo/opie-devel