Re: Antw: [Envolution-devel] little resume from italian discussion

[TiMax <ma...@em...>]

On Fri, 30 May 2003 10:18:57 +0200, Stefan Koehler wrote:
>  [...] we talk about our chaos code for css, styles, classes=
 etc ....
>  about that Tchichi and @ngelspike work to clean code, to=
 prepare list of class we must use in modules and core, so 
all people use same class when write modules, blocks or themes,=
 they want to release public list in next days.
>  Tchichi work also to check, delete or remplace deprecated=
 class in our code [...]
>
>  Ah. Two new names: Tchichi and @ngelspike are developers? Or=
 designers? Or what?
>  Please remember my points of view. I talk about developers,=
 and I meant workers for the core and basis eNvo system.
>  I think you mix on italian discussion all we have to do in=
 core AND design. But we have to share tasks. We need 
persons for both parts and we have to group them into different=
 teams:

Tchichi is not a new name, you can found it like our member in=
 envolution CVS, and @angelspike want to help he 
they don't are designer, code writer or somethig, they are people=
 in Italian staff want to help to develope and clean 
code.
You are right when you talk about share tasks, for this raison i=
 write here to inform all about that, Tchichi and 
@angelspike start to work to clean code and prepare list for=
 class, so all of us know about it. 


>  1. Core-Dev: Make code stable and wellformed
>  2. Core-Dev: Re-code some parts of core modules to get same=
 look-and-feel (Input- and output-masks, not theme design)
>  3. Core-Dev: check classes (i.e. pnAPI, pnHTML, ...)
>  4. Core-Dev: create new classes and functions for use in=
 several modules
>  5. Core-Dev: Optimize and clean core to make it faster and=
 eliminate overheads (code not needed)
>
>  6. Themes-Dev: Check CSS and modify it
>  7. Themes-Dev: Create a basic, non-grafical theme to check=
 module functions and system integritiy (i.e. for module 
devs.)
>  8. Themes-Dev: Check existing themes (Experience, Borobudur,=
 Michelangelo). It seems, that there are some bugs.
>  9. Themes-Dev: Write docus and descriptions how to use=
 Encompass (Smarty), modify existing themes and create themes 
on basis of Experience or Borobudur (I know this is under=
 process).
>
>  ... to be continued

That is nice, but where we can found so many people ? LOL
Or maybe we can select a  Core-Dev manager and he work to found=
 helpers like  re-code - check classes etc ....

Remember we are in Open Source contest and is not easy to manage=
 people.

So for example :

Pyksel is our designer manager and he worked aroudn new theme=
 system and style definition, and sure new graphics but now 
he have some family troubles and i don't see he from 40 days i=
 think 

Zxvision is our code manager, he writed nomoreblocks and=
 visualblocks, and he have some other ideas to manager templates=
 
etc with nomoreblocks and visual blcoks but now he have lot of=
 trouble with his work so he can't help us from 1 month 
and maybe more for 1 month 

cyblenoire work around new subjects module and some other=
 develpoement but now he have school problem so he can't help 
us and i don't reaad about he from one month 

and also sometimes we have language barrier, but we need to=
 improve it, so sometimes is hard to manage it but we must 
continue so we can be one International developement Network and=
 not only a site developement.

Sure we need to re-wamp our organization structure and need to=
 define better all responsability, but we need also to 
keep it very flexible and with all language included.


>  [...]We all agree to keep compatiblity with modules and blocks=
 Postnuke, and sure after next release we can take time 
to check and clean some modules for eNvolution [...]
>
>  The backward compatibility to PN-modules is nice and a=
 must-have for older modules. But PN and eNvo goes not the same 
way and the devs of the two CMS make changes, add several=
 functions and recode basis code.
>  It will be more and more harder to integrate PN-module (I mean=
 newer and newest modules) into eNvo.
>  Look on PN-CVS. They have add some new code in the=
 API-functions. And the module- and 3rd-party-devs will use this=
 
now and in near future.
>  So we have to find needed modules and make them compatible=
 with eNvo. Problems can be, to check updates of this 
programs.
>

Yes i agree, for this raison we start with envoaddon.com to have=
 international demo site for modules, blocks and addons 
That want to be only a demo site for downloads, support or news=
 alle people are redirect in our international support 
site.

>  [...] Maybe we can think also about something like xaraya, one=
 repository where we or developer can assign number for 
each module and let know people about what he mean develope and=
 status of developement.[...]
>
>  This is, what I want installate with my ToDo-module. And we=
 can combine it with "credits" and "envoDev".
>
>  WindMeUp

That is good 

TiMax