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

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

Hi @all:
It is nice to hear, that we want to release the new version eNvo 1.2.1 =
soon, and we are preparing for the next milestone "eNvo 1.3".
Thanks sjah for the article on www.envolution.com .
But about this article, it seems to me, I have to write some lines and =
my points of view about the complete project "eNvolution".
And I think the env-devel mailinglist is the correct platform to do =
this.

sjah: You wrote, the developement team is preparing for eNvo 1.3. Who is =
the devel-team? Who is developer of eNvolution core? Who works on what? =
Who coordinates all things that has to be coded? Where is the new =
roadmap? What we do next?

Questions over questions. I'd discussed it with TiMax sometimes ago. And =
I think it is time now, to bring up the complete eNvo-Team (not only the =
CMS-project itself) into the right direction.=20

Here are my points of organize structure we have to do:
  a.. First of all: Is the "Organization Structure" up-to-date ? Read =
here: =
http://www.envolution.com/modules.php?op=3Dmodload&name=3DSubjects&file=3D=
index&req=3Dviewpage&pageid=3D25
  b.. I mean: For better developement of all parts of eNvo (core, =
module, 3rd-party) we need a Lead Developer, who coordinates all other =
devs and delegate things. Look into the document. The description there =
is perfect. Also it would be a nice idea, to create local dev-teams (and =
a Local Lead Developer). Because perhaps the priorities of eNvo-features =
differs (users in USA need other features as users in Germany).
  c.. As we can see on "eNvo network" we have many local sites in many =
countries. All sites are authonom. This is OK. But it would be nice, if =
we can link together some parts of eNvo, i.e. Downloads, Weblinks, some =
support forum desks. So I can see on eNvo.de, if there is a new upload =
on eNvo.com.
  d.. Where are all the developers? And who coded what? I don't know it =
in details. I can't find any public (or private) information which will =
answers my questions. If I read "credits.txt" on CVS, I can only find =
two developers (Frank and me). Where are the others? And I mean =
developers, not designers, supporters, testers, etc.
  e.. The official roadmap is out of date. It was written last year. =
This document has to be update on new status of the actual eNvo-version. =
There are a lot of code changed, modified, included in the meantime. =
Possible we need a new starting point.
  f.. In parts it seems to me, that everybody do anything: Developers do =
translations, Translators supports, Testers fixes, and so on. And nobody =
knows, what the other do.
  g.. At this time the hole eNvo-team is small, but in the near future, =
lot of people wanted to be members of the team. So we need a hirarchical =
structure for personal, positions, things todo and complete projects =
process.
  h.. To produce a final version of eNvo (Version 1.3 ?) we need a =
identical "look-and-feel" in all core modules. At this time, the layout =
of News, Comments, Reviews, Downloads, Weblinks, etc. differs. Possible =
to coordinate it. Also we can centralize some parts of code into a =
secondary API, which will only load if modules needed (not every =
loadtime as the pnAPI). Here we can include functions and programs i.e. =
PopUps, Select-Boxes, Colorpicker, Imagepicker, DateTime-converter, etc.
  i.. We must distribute the project-tasks on several shoulders. It is =
good for now, that TiMax, as Project Manager and Founder, manages all =
and hold his hands on it. But in the future it would be better to split =
it off and coordinate it in a strictly way. It is not possible to do =
anything at same time. I see it for eNvo.de and TiMax see it for =
eNvo.com and eNvo.it It is impossible for one person to code, support, =
discuss basics, coordinate, administrate, etc. for this kind of program =
eNvo is. If we can change it, everybody can concentrate his work on his =
primary tasks in the community.
  j.. A good idea is also, to initiate a periodical discussion board on =
IRC. Possible to meat i.e. once a week, every 2nd Thursday, once a =
month; and splitted for development and support.
This are only some of my points of view. Possible my opinion is too =
heavy-weight. Possible I'm too critical. But I want to dicuss my =
thoughts with all of you.=20

And remember:
This is not a flame. I don't want to critizise single persons. The =
points above are fundamental problems I see for the whole project. I'm a =
developer who works the whole day (and sometimes the whole night) with =
eNvolution. In real life I'm software engineer fo a large production =
company in germany. The frontend of our intranet is eNvolution. And I =
don't want to change it to an other system.=20

So, all what I do (now and in the future) is with and for this great =
CVS.

Stefan Koehler aka WindMeUp
s.k...@pr...
www.drachentasche.de
www.envolution.de

+++ walking in the air +++