Re: [Envolution-devel] org. questions... talk with me

[<s.k...@pr...>]

@sjah:

[...] Yes, you're right, it needs managers to organize the groups task and
keep
the committed rules.

However, in commercial hierarchy, you have the power, superior, to enforce
the task list. In opensource you don't have it. It only depend on how we
respect each other. So it needs more personal approach rather than formal
ways.

About PN, yes, why they don't create two branches, one pn-bl and pn-
encompass :) There will be no fork, because both concept has its own
strength points and qualified developers. Such as Windows95 and Win-NT4.0 :)
[...]

I agree. Maybe I'm to critically. But I think the project "eNvo" needs a
better guidance to go the desired way. I know, that you can't predescribe
anybody, what he has to do. Also you can't define a strictly timeframe for
parts or the whole project as in commercial projects. But a Lead Developer
has to manage and decide which is good for the core, which is an
additionally function, 3rd-party, possible for the future or not needed.

[...] I tried the module, thats great!. This is also can become an added
value for
envo. Once you're ready, I hope we can use it for our intranet site.

For the current purpose I already installed the phprojekt, so we can
organize all issue here in intranet site. Then we can use this mailing list
back to development purpose. [...]

Thanks. I have finished the  ToDo-module near 90%. To show you parts of the
functionality, I have recode some parts. But I think it would be ready this
week. Then we can use it as eNvo-module on every site.
You say, you have installed phproject on your intranet and want to use this
mailing list for dev. purpose, this is good, but not enough.
I mean, if a new developer enters eNvo.com and install the latest release on
his server, maybe he find some parts useless or want to change something.
Because he can't find any infos, which parts are under development and which
person do what, it would be possible he starts with programming and think he
do something new. But at same time other developer code the same. Not good.
Also: Only members who are on the mailing list, can read this infos and
results.
So we need a complete actual (public) project status over all parts of eNvo.
Nice features for that are:
credits, envoDev, ToDo.

WindMeUp