31 Oct
2008
31 Oct
'08
7:13 p.m.
Similar offers appear quite regularly, some people come out of
nowhere, and start telling us - hey, you have a bad management, you
don't have a business-plan, you don't have regular developers
meeting, you don't demand work from developers regularly, you don't
set priorities right - developers should work on XXX instead of YYY,
because XXX is way more [some cool reason, usually referred to the
future].
But please understand, I *know* how professional development is done,
that was my main employment for the at least last 5 years.
Let's see your key sentence:
But why would it suddenly be
a big no-no to employ the same tactics which make commercial projects
such a success, like proper management, a schedule to which people
stick
(with some more tolerance, of course
"proper management" - I'm listening, what should be proper?
"a schedule to which people stick" - all what I said went to nothing.
What kind of schedule are you talkign about? If Klemens have exams,
if Johannes have exams at different time, if Stefan is busy with
school, if Alex can't answer my question because he works in another
company. What can I demand from people? Set them deadlines? Blame
them? A perfect way to loose developers, and a perfect way to
unmotivate.
I recently had a similar talk with Arty, where I said that I
immediately begin to hate any good task when someone demands
completion from me (Z98 - that doesn't apply to you.. well... yet ;)).
So, any more offers how to make us better, rather than just saying
facts that ReactOS should work better than Windows 7 now, and it
works worse?
WBR,
Aleksey.
On Oct 31, 2008, at 6:36 PM, Maya Posch wrote:
Aleksey Bragin wrote:
This is the point where Maya mistakes most of
all: ReactOS is an
opensource and a FREE project. Managing and working in an opensource
project is different.
Of course it's different. You can't expect people to work from 9 - 5
like in a company. I'm well aware of that. But why would it
suddenly be
a big no-no to employ the same tactics which make commercial projects
such a success, like proper management, a schedule to which people
stick
(with some more tolerance, of course) and in general a sense of
professionalism and focus.
We can't compare ReactOS engineering technologies with Alcatel
engineering technologies. Or with Microsoft technologies.
But I try to keep the most valuable what we have in ReactOS, and what
is lost in some other project which tries to provide Windows
compatibility - freedom. And my intention is to keep this even after
commercial ReactOS vendors appear.
As some may know, I've got my own software/R&D company and have some
people working for me with expansions planned this and next year. I
consider freedom to be the biggest asset as well. I want to me my
employees feel at home, wanted and free to share their ideas. How
ReactOS can offer more freedom I don't know. Heck, we even pay
people :)
As for another question, by Marc or by Alexandru, there is no real
development roadmap of ReactOS, the one on the website should
actually be removed, since it's mostly incorrect.
Well, I guess that kind of settles it then. I'm willing to spend
some of
my spare time on a project I like, but only if I feel that my time is
not wasted while following inefficient procedures and chasing devs
because nobody bothers to write down implementation details (NT
references != ROS implementation details. D'oh).
For now I'll finish the ROSE installer project, but after that I'm not
sure what I'll do. Perhaps I'll put my own OS together based on
*BSD or
so, or fork ReactOS, or... we'll see ;)
At any rate I don't foresee ReactOS going anywhere soon within the
next
5 years, and I don't want to be part of such a frustrating experience.
So long and thanks for the fish.
Maya