Future of phpwcms - 1.3 is planned
To my opinion it would be enough for now to just have a system capable of easily plugging in add-ons, mods and so on without the need to rewrite every changed/edited file when a new release arises.
Then much more user input could happen...
And much more use could be easily made out of all these fantastic developements for phpwcms popping up all the time
And users would get the feeling to be able to act instead of beeing forced to wait and react
And wanted as a side effect: development isn't hindered by such concerns like "what if all is changing again" and "what if my own script will stop functioning with later developements"...
Anyways, just kind of deja vu: did I already really write about this topic recently ?
Greetings
claus
(happily sitting around, wondering how to get from 126dev to 126final without destroying all website output in a second (where's my own changelog gone to? ), deciding myself clearly for no or yes every other minute, feeling like a pinball )
Then much more user input could happen...
And much more use could be easily made out of all these fantastic developements for phpwcms popping up all the time
And users would get the feeling to be able to act instead of beeing forced to wait and react
And wanted as a side effect: development isn't hindered by such concerns like "what if all is changing again" and "what if my own script will stop functioning with later developements"...
Anyways, just kind of deja vu: did I already really write about this topic recently ?
Greetings
claus
(happily sitting around, wondering how to get from 126dev to 126final without destroying all website output in a second (where's my own changelog gone to? ), deciding myself clearly for no or yes every other minute, feeling like a pinball )
- marcus@localhorst
- Posts: 815
- Joined: Fri 28. May 2004, 11:31
- Location: localhorst
- Contact:
Just ideas and fears...
What I can not understand yet is why PHPWCMS is still so dependant on Oliver Georgi.
My humble opinion is that if we want PHPWCMS as a major CMS system its development should not be so highly dependant on just one (!?) person. At least a core group of 5-10 people shoul be neccesary, working transparently with all the PHPWCMS community.
We should not be asking OG to write all the code himself, but think about him as a big coordinator whose task could be to unify the work of the group/community... In the case he has time, of course.
Several times I found myself asking what would be of PHPWCMS if OG leaves off working on its code.
Imagination is free
My humble opinion is that if we want PHPWCMS as a major CMS system its development should not be so highly dependant on just one (!?) person. At least a core group of 5-10 people shoul be neccesary, working transparently with all the PHPWCMS community.
We should not be asking OG to write all the code himself, but think about him as a big coordinator whose task could be to unify the work of the group/community... In the case he has time, of course.
Several times I found myself asking what would be of PHPWCMS if OG leaves off working on its code.
Imagination is free
* Maybe I'm wrong * Maybe not *
Re: Just ideas and fears...
Agree. His ideas and approach seem good. But Oliver should take the power of a small team to implement stuff faster. Pitty that it's so slow.Evoplure wrote:My humble opinion is that if we want PHPWCMS as a major CMS system its development should not be so highly dependant on just one (!?) person. At least a core group of 5-10 people shoul be neccesary, working transparently with all the PHPWCMS community.
We should not be asking OG to write all the code himself, but think about him as a big coordinator whose task could be to unify the work of the group/community... In the case he has time, of course.
1.3 out, testing, testing...
Sponsoring 4 phpwcms Blog and Usermanagement
Sponsoring 4 phpwcms Blog and Usermanagement
Ja, is denn heut scho' Weihmnachten? | Christmas today?
Fine, sure. But I'm remembering at this:
Source: http://phpwcms.de/index.php?id=1,39,0,0,1,0Within the next weeks not months a consolidated release of phpwcms will be published.
How long are "weeks, not months"? Some people think, this would not be more than 60 days. And now, 60 days are over.
And – where is the "consolidated release"?
Sorry for this, OG, but it is the same mistake you made so often in the past. And this doesn't show a good credibility.
How I often said – more transparency and less of dates and all will be satisfied. But no, you gives at "every corner" the next date.
Tschuldige, aber das mußte ich mal loswerden. Es nervt einfach – ich erinnere mich da ganz besonders an Weihnachten.
Hi all - the irony is that opensourcecms removed phpwcms from its listings (about a month ago - according to Pappnase) even though it was listed as #1 about a year ago (above Mambo)- They based their ruling on this criterion - NO STABLE RELEASE....
Well that call is unfortunate - its pretty stable on this end and VERY flexible and PRACTICAL. I have been looking at others - Drupel - very good (taxonomy framework) - Wordpress (yes a blog) and Mambo (tons of modules) - Typo - great class structure - but I still say that Oliver has the big picture in mind.
As mentioned by Oli - the chance to have user defined content parts - has me very, very excited - since i am a flash developer.
Oliver should be encouraged and thanked
lets all be patient.
I believe great things are coming from the resident genius.
DANKE OLI
Well that call is unfortunate - its pretty stable on this end and VERY flexible and PRACTICAL. I have been looking at others - Drupel - very good (taxonomy framework) - Wordpress (yes a blog) and Mambo (tons of modules) - Typo - great class structure - but I still say that Oliver has the big picture in mind.
As mentioned by Oli - the chance to have user defined content parts - has me very, very excited - since i am a flash developer.
Oliver should be encouraged and thanked
lets all be patient.
I believe great things are coming from the resident genius.
DANKE OLI
hello johnjsw_nz wrote:Hi all - the irony is that opensourcecms removed phpwcms from its listings (about a month ago - according to Pappnase) even though it was listed as #1 about a year ago (above Mambo)- They based their ruling on this criterion - NO STABLE RELEASE....
Well that call is unfortunate - its pretty stable on this end and VERY flexible and PRACTICAL. I have been looking at others - Drupel - very good (taxonomy framework) - Wordpress (yes a blog) and Mambo (tons of modules) - Typo - great class structure - but I still say that Oliver has the big picture in mind.
As mentioned by Oli - the chance to have user defined content parts - has me very, very excited - since i am a flash developer.
Oliver should be encouraged and thanked
lets all be patient.
I believe great things are coming from the resident genius.
DANKE OLI
wow nice and wise words! some should these reade more than one time!
Definitely, in my opinion patience is not what PHPWCMS needs. All of us should thank OG for his initial job, that is fantastic. But for me an open source project is more than sit and wait for the next release by OG. Open source is a work system oriented to the development of applications by communities. And if PHPWCMS has not a real community of developers is because of:
1. OG: There is not enough transparency, maybe not real interest in PHPWCMS as a real colective project. No coordination, no information. Lots of copyright stuff...
2. Us: No skills as programmers (???), lazyness (???)... or we do not dare to create a parallel PHPWCMS branch which could work without being waiting OG releases (with clear roadmaps, common working space, good organization...)
There are some people writing good code for PHPWCMS, but their work is not encouraged because this lack of information, communication and infrastructure. I think this is the work we should first encourage.
In this situation, my strategy as web designer is:
1. Improve my PHP skills and (later) try to find a close group of interested people in order to develope and customize PHPWCMS to our necesities, and (later, in case of success) open our developments to a broader comunity.
2. Keep on trying as many CMS I can. Alternative CMS could be just around the corner...
1. OG: There is not enough transparency, maybe not real interest in PHPWCMS as a real colective project. No coordination, no information. Lots of copyright stuff...
2. Us: No skills as programmers (???), lazyness (???)... or we do not dare to create a parallel PHPWCMS branch which could work without being waiting OG releases (with clear roadmaps, common working space, good organization...)
There are some people writing good code for PHPWCMS, but their work is not encouraged because this lack of information, communication and infrastructure. I think this is the work we should first encourage.
In this situation, my strategy as web designer is:
1. Improve my PHP skills and (later) try to find a close group of interested people in order to develope and customize PHPWCMS to our necesities, and (later, in case of success) open our developments to a broader comunity.
2. Keep on trying as many CMS I can. Alternative CMS could be just around the corner...
* Maybe I'm wrong * Maybe not *
Right now I am liking 'ModX'Evoplure wrote:....
2. Keep on trying as many CMS I can. Alternative CMS could be just around the corner...
seems like the approach is similar in many ways.. sure it lacks in some ways but it expends in others...
I still search, and I feel terrrible t be looking else where.. I have been here for sometime, and have promoted wcms heavily online.
======
DX
======
DX
======
DusX wrote:Right now I am liking 'ModX'
" it gives you a true system for registered web users and groups that is separate from administration users. You can grant some web users access to one page and others access to another page. For content management, you can easily duplicate documents, folders (and all their children!), chunks and snippets. "
DusX wrote:Right now I am liking 'ModX'
I must say, I like this page: http://modxcms.com/modx-team.html
.