From my POV it looks like pdaX develusers should create team which will work on improving pdaX and sashz should be degraded to kernel hacker/pdaX developer from 'pdaX the only one devel'.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=132153\"][{POST_SNAPBACK}][/a][/div]
(I'm sure the word meant is downgraded, not degraded (lol) before anyone gets upset by the word Hrw used!)
I'm not sure "downgraded" is the right word, necessarily either.
Consider two things:
a) Sash is currently the only one who
gets to work on pdaXrom
b) Sash is currently the only one who
is working on pdaXrom
excluding laze, and the few other direct contributors they've had, its basically
Sash's project. Some on the OESF forums (and some elsewhere) think the project
might benefit, if Sash wasn't the only one working on it-
there are really three ways to go from here.
I) continue pdaXrom as it has been. which will make some people happy,
and some people unhappy, and some will not especially care
Ia) give sash more $$$
Ib) give sash less $$$
Ic) give sash the same amount of $$$ as before
II) fork pdaXrom! (and by attribution, "fork" sash). This should make a few people
happy, a few people unhappy, and most won't really notice or care much.
III) work with sash to build a better pdaXrom. This has been tried, apparently, with not great results so far. There is no greater authority who can "downgrade" Sash from mainline pdaXrom development; only he can choose to take a different role, or not. Perhaps there is some inspiration to be gained from Linus' stepping away from
day-to-day Linux development, to focus, progressively on more and more "core" and essential subprojects. If Sash is happy with the role he currently has, or doesn't wish to give up any power or control, he's probably going to stick doing what he's doing. If he gets sufficiently unhappy, I fear he's going to probably quit.
IIIa)
What might help Sash (and pdaXrom) would be to offer specific help with specific tasks; bug-testing, bug-fixing, general apps, pdaXrom tools, kernel, bootloader, etc.
What Sash would have to do, in turn, would be to keep an open svn/cvs that lets developers have write access. If this already exists, we're a step closer.
What Sash would have to do, which would be a pain, would be to *use* that repository for all the changes he makes, and commit himself to keeping it current.
This could be a small bother, or a real hassle, but it would probably be good practice for him, too :)
IV) OE devs keep insulting Sash, Sash keeps insulting oe devs, until either
OE people get annoyed and quit, or Sash gets annoyed and quits, which will leave
the Zaurus community poorer. This is the "solution" that I hope we don't find.
"OE MUST DIE" and "sashz should be degraded" are both... fun things to chat about
and definitely this kind of speech releases anger and stress for the speaker,
but it causes more stress for the listener.
I hope we can keep trying to make option (III) or (IIIa) a reality, or (I) if not that,
or (II) if not that, and avoid (IV), but we'll have to see what people want the most, and are willing to contribute to.
(IV) death to [all zaurus development] is probably the easiest path to pursue :(
