theKompany.rom - Need to dispurse workload more...

[Anonymous]

I need to dispurse the workload more for the tkrom... I will open up the buildsystem used and be open to others making updates and fixes to the ROM..

I would like to keep this going but cannot do so on my own anymore as many other things are using my time fast...

I would like to kill all the bugs on the 2.5.1 series and pack them up into a new ROM with a new name/versioning system.

I want to move to more yearly releases like \"rom name, 2004 SPx\"

The main thing here is to stick with Sharp\'s Qtopia, and keep the ROM as modular as possible by keeping all the extra packages in the feed that is already hardwired in.

If you think you would be able to help please let me know. Please don\'t try to break this project up or fork it... Lets all work together on making this the most compatible and polished ROM available... Javaboy is the kernel maintainer for the ROM and I will just oversee the ROM work.

Thanks

-Mike

[holck]

I am not a programmer, so I can\'t contribute to your work as a developer.  I can offer help in more \"soft\" areas like user tests and documentation. I use your latest ROM on my C760 and have been very happy with it, so a great thank you from me for your work.
Jesper, Denmark

[Mickeyl]

Proto - why don\'t you join us and use OpenEmbedded as the build system for your next generation tkcROM? Take a good look at OE, it\'s worth it.

[undrwater]

Proto, Mickeyl:
I think Mickeyl has a great idea...especially when you consider the standpoint that the Zaurus is a linux device, and having the ability to sync it with a linux desktop makes more sense than not.

Also, I know there are some efforts to reverse-engineer the Sharp syncing process so that other roms will have the ability to use the latest intellisync/qtopia desktop solutions for windows, but maybe starting development of a new syncing structure from scratch(?) would finally release us from dependency on Sharp.

Mickeyl,
Has Lycoris contacted you at all regarding their release?  I\'m guessing they\'re using your build.

[n8a]

Similar to holck, I\'m willing to help in a non-developer role.  Just let me know if I can help with any testing and documentation, as I\'m a happy tkcROM user.

[Mickeyl]

@underwater: We\'ve not being contacted yet, neither the Opie nor the OZ team...

[Anonymous]

Proto

As a user of your 5500 v1 ROM I can only praise your work and attention to detail.  I hope you can find help with the project, but alas I have not got the skills you require.  As I enquired some time ago, is this still a TKC project?  are you getting payed for the work?.  If not why not.  I know how much time it takes to complete a project of this size and your efforts should be rewarded.  I for one would be glad to pay for the updated ROM as there is no such thing as a free lunch.  Again Thanks for your time making a ROM that beats Sharp\'s default hands down.

Good luck

Craig

[jh]

I\'ve been using the OpenEmbedded build system for a couple weeks now and have been really happy with it.  I\'m running OZ 3.3.6 and it\'s been a piece of cake to add any of the available packages to my Z.  I haven\'t actually added any new packages (I\'m hoping to, though), but it seems like using the OE build system is a great idea in order to focus the developer community on one system so it keeps improving and effort isn\'t duplicated.

Of course, I know nothing about the tkcRom build system, so it might not even be possible.  Just a happy OE builder :-)

jason

[foopirata]

Proto,

First of all thanks a lot for the work on the ROM. I am a happy user on a 5500, and would like to help. I do have some skills I could lend to the project.
Is there a mailing list I should join or a roadmap that should be read ?

[Anonymous]

The main thing here is to stick with Sharp\'s Qtopia, and keep the ROM as modular as possible by keeping all the extra packages in the feed that is already hardwired in.

Is it worthwhile to make the kernel modular? Since there is a fixed size flash partition, wouldnt it make more sense to build as much into the kernel as will fit in that space to prevent using up the limited space on the 5x00 flash?

[Anonymous]

When I said \"modular\" I am refering to the packages... Much like OZ/OE...

This is the main thing... I wouldn\'t mind using the OE build system but having the updated packages in the root system break much compat... Libs like libpng can be very touchy...

Opie isn\'t bad but needs much work and manpower to become polished wnough for use... Native Qtopia in all honesty just sucks in many cases as well for usability and overall polish... Qtopia Phone has been looking quite impressive, once Qtopia PDA is brought up to speed it will be very nice...

The main problem I see at the moment is that everything at Sharp US in the zaurus division is pending on an IBM deal that quite honestly doesn\'t look good with Symbol showing more commitment.

Sharp has proven time and time again that it isn\'t really commited to sticking to anything... The plug is waiting to be pulled once all the 5600 stock is gone... Much like the reason we waited from november to march to get the 5600, they wanted to get rid of the 5500 stock. Then release the flawed 5600 wich was already outdated. They don\'t give a rats ass even know they had the only Linux PDA market in north america in the palm of their hand. The nickel and diming hurt.

They didn\'t really want third party developers either... They wanted to do all the apps in house as well... Sharp entered and exited the US PDA market wrong...

The hardware from Japan is nice but its not hardware on its own that can pull the market...

/RANT OFF

-Mike

[Mickeyl]

This is the main thing... I wouldn\'t mind using the OE build system but having the updated packages in the root system break much compat... Libs like libpng can be very touchy...

Huh? I don\'t understand this. OpenEmbedded is not OpenZaurus. OE features different versions of the software packages which can live happily together. You decide which version get built by specifying the dependencies.

OpenEmbedded doesn\'t care about what you build with it - that\'s what we designed it for.
You could use the same system to build OpenEmbedded/Zaurus, Cacko, tkcROM, familiar, CackoX11 or whatever will be added to it.

We see this as the possibility to let the people forget about the buildsystem (because OE is there and works) and the base distribution (things like sysvinit, getty, tinylogin, busybox etc. are already there and proved to work fine) and let them concentrate on developing what really matters - the applications!

The hardware from Japan is nice but its not hardware on its own that can pull the market...

Exactly. Another reason why it\'s time to join forces in one or the other way. I don\'t request people to work on Opie or OpenZaurus if they would like to work on X11 or Qtopia-based distributions - pretty fine with me. But for the sake of our few valuable resources - let us unite the build system and the base distribution!

[Anonymous]

Hello Proto, sadly Im not a software developer (Im electromechanical engineer that works in buildings design and construction), but I\'m more to happy to help If you may consider it usefull, as a tester or with docs,also I could help with spanish support/translations if may be it could be usefull for some part of the rom.

One question about sharp PIMS & sync, in the case of mail sync with a desktop...  it\'s too difficcult to compile/port some already made email prog like Sylpheed or Balsa,or something like that that could run on a linux desktop to Z in order to get the same email group of messagues on the Desktop and Z in sync, no matters if you made emails or changes in one computer or the other....  In the cacko linux version I see they port the sylpheed email to the Z 7xx series fo their rom, and I wonder if it coul run on Z Qt or something...

Best Regards to all!  

[bluedevils]

I think mickeyl is right and in light of the devnet fiasco maybe more so.  If and when the Z community thrives again, I could see more diversity but not now.  We need the quantity and quality (polish) of apps that Proto spoke of and the only way is for the developers to pull resources.  There are few PIM projects out there.  It would be best if they pulled together and polished one PIM project.  Using the same build app may be a step in the right direction.  I\'m not a programmer so there may be errors in my thinking.

[Anonymous]

From what I have seen (and this is not taking away anything from either camp - if there is such a thing as a camp), Mickey and OZ group seem to be developing an entirely open implementation of the Sharp\'s Qtopia ROM in Opie and while it may be very good, often there are complains that it lacks the finish and stability of Sharp\'s ROM.

Proto on the other hand with his TKC builds has demonstrated the ability to take off from Sharp ROM base and add spit and spittle to it - a more overall completeness and polish.

And one thing about mickey - he has been a VERY open (and stong ) advocate for continuation of these efforts independant of Sharp. I think his suggestion to join forces will be good for the zaurus community and nothing better than to have the base of Opie and the finishishing touch and completeness and polish that Proto brings to come together.

Proto and OZ - that would be a potent combination.
And alongside there the Sash X11

I think this zaurus community rocks baby !