Hi @all
I will be back "full time" end of next week. Then I can start to talk to all
developers in details again.
First:
I have read the threads on eNvo.com-forum "eNvo&PN" and can't follow the
discussion clearly because I haven't understand it 100%.
But I see more disadvantages than advantages if we reunion the two projects.
But we can participate from each other. So we can use some code from PN,
i.e. security issues, API-functions, recoded core-modules, etc. Otherwise PN
can use our theme-engine-knowhow for their new Xanthia-engine.
For us it would be very important because we want to use several
3rd-party-modules which are coded for PN. We can only use them without
changings, if the fundament of our API and other functions is nearly the
same as PN uses.
This doesn't mean that we can't modify or change them for our needings. We
only have to be a bit carefully by doing this.
And another point is (this is for me the most important thing), that our
community is differently structured. Our resolution is Open Source. This
means that every eNvo-member is part of the development process. Without the
feetback of every eNvo user we can't create a stable, full-featured CMS
product for the whole community.
I think we will lost this very important point if we combine both projects
again.
eNvo exists since 1 year. It was hard work to bring up the actual version
(1.2.5 FLS) to what it is now. Also the community grow and work perfectly
together.
We should not risk that !
Ok. You also talk about needed standards, rules, guidelines for developing.
I think this thema is a bit more complex to write it here on mailinglist.
You can read my points of view on envolution.com as an article tonight.
This article includes:
1. What we have to do next
2. What we have to consider with programming
3. Some rules for source codes (note: using of phpWiki for documentation)
4. Using of API (or all files in folder "includes")
5. New structured API
6. Centralize images, functions, code blocks
7. Uniform design for buttons, input forms, lists and outputs (for core and
3rd-party)
8. Code clearing to reduce multi-calls and speed up
9. How we can build teams for this new tasks, who is part of what
10. How we have to communicate
I hope we can discuss this points and can find a solution for this
organisational structure.
So we have rules, guidelines and standards and everyone knows where we want
to go and what he has to do.
Possible there are missing points. I don't want to dictate. We have to talk
about. At the end of discussion I hope everybody can except this paper for
"eNvolution Development Standards".
Stefan aka WindMeUp
[eNvo-Devel-team]
[Lead Developer]
s.k...@pr...
http://www.drachentasche.de
http://www.envolution.de
|
