PostNuke

Footnote: 1

Arabic
Bulgarian
Catalan
Chinese (Simplified)
Chinese (Traditional)
Czech
Croatian
Danish
German
Greek
English
Esperanto
Estonian
Finnish
French
Hebrew
Hungarian
Indonesian
Icelandic
Italian
Japanese
Korean
Latvian
Lithuanian
Malay
Dutch
Norwegian
Polish
Portuguese (Portugal)
Portuguese (Brazil)
Romanian
Russian
Russian (KOI8-R)
Slovenian
Spanish
Swedish
Thai
Turkish
Ukrainian
Yiddish
Klingon

It is no secret, Harry has stepped up and is going to move PostNuke forward to the best of his ability. I wish him luck and I encourage those who want to join Harry, as a developer and/or as a community member, to do so and support the PostNuke project.

It is no secret that John has also stepped forward and made his intentions clear to fork. I wish him luck and I encourage those who want to join John, as a developer and/or as a community member, to do so and support the Yet2Bnamed project. If you don’t already know visit http://www.dinerminor.com

MAKE YOUR CHOICE, JOIN YOUR SIDE AND LEAVE THE OTHERS ALONE.

SO STOP THE BITCHING AND LET’S MOVE ON !

Before the change in the project's management, as a user I almost didn't notice who was in charge, or what was happening in the internals. John Cox and other names were more or less known to me, but just as "developers".

Now it seems that HarryZ is everywhere. Just looks like he changed his last name to Postnuke, and named his children Rogue and Mutant. I mean, previously the Postnuke code was just developed and released, now the released code is visibly a result of political struggle.

Developing opensource has always been an Ego driven (if you remember the PHP-Nuke and Postnuke fork).
Now I don't know how long HarryZ has been around in the project, but I would suppose that all core developers were already talking to John Cox before HarryZ joined. Whereas the title of PM is clearly a hierarchic title, the developers may have been tied to John Cox on a more personal level, so that in addition to maybe being pissed off that they weren't chosen as PM, they were maybe also confronted to the reality of hierarchy in the postnuke project. This is equal to a degradation of their rank and status in the project, they have realized that they are not "eternal fathers of the postnuke wonder of the world" but just devs - not less, not more.

That's why the team is new - the remaining people have less problems accepting the current leadership.

But I can't help thinking that the change of leadership has been ill-managed by John Cox and HarryZ. Or maybe this task was too difficult and just not doable considering the dev's Egos... No one will ever know.

What does it mean for HarryZ? He must show his leadership, affirm it and show that there are teammembers accepting it. There's no other way than reapeatedly posting messages and making decisions.

What does this mean for me as a user?
Before the exodus I thought that Postnuke had about 90% chance to be developed to a 1.0 release, and that the finished product would be widespread, with further development and versions.
Now I must objectively say that the risk increased drastically that Postnuke will not reach these goals, partly also because of the deaths in the team.

The themes question certainly needed to be addressed, and the new possibilities are stunning. But the themes, let's face it, are a short term cosmetical change - the core also needs to be worked on.

Today I am worried that the Postnuke that I love will be left on the road by some other opensource product, because of uncontrollable Egos.
But since we cannot undo what has happened, I appeal to HarryZ and to the former devs to focus on the goal and make Postnuke also my future choice!

Regards,
Manarak.

Footnote: 1

Footnote: 1

The goals are to make PostNuke become very popular among the rest of CMS due to its native support. Furthermore each community hopefully will create their own language pack. This way PN will have much to gain with a little effort for the core team.

Anyway this is just an idea. I'll try to submit an official email to Harry and hope it will got his approval.

P.S. Indonesian community already got build and currently run by vipixel.com and probably myself.
Hopefully I can really get http://id.postnuke.com

regards,

Neo has worked with his usual fervor and tenacity to bring you a great release - here's what's been changed / fixed:

1.- NS-AddStory (case issues on templates)
2.- NS-Referers (bug in older 0.72 code - pre-phoenix)
3.- Themes (0.72 themes with lower case, they have
now been all fixed)
4.- Quotes (Had pre-phoenix bugs all fixed)
5.- NS-Settings (overlooked, gzip compression and other
fixes, now updated)
6.- NS-Comments (updated)
7.- Members_List ( fixed an odd bug there )
8.- Xmlrpc (upgraded)
9.- All new 0.72 pre-phoenix fixes, cvs dates and user
commit names are fixed and up to date.
10.- Multiple session fixes.
11.- Multisite fixes many.
12.- Added compression option in settings
13.- Stats langiage definitions in english bug fixed,
14.- Download module fixed
15.- Comments module removed
(now only NS-Comments is needed)
16.- NS-Quotes removed (Quotes is the active one)
17.- Enhanced index.php and header.php for
Encompass compatibility fixes many bugs, provides
flawless compatibility with existing PN installations
that have encompass in use.
18.- All permissions of all files and directories where
corrected for the tgz version.
19.- Installer script and upgrade routines updated to
reflect all db changes and needed modifications.
20.- Al pnTheme() calls where deprecated.
21.- Hundreds of small code fixes where applied and all
latest cvs commit information were restored to all files.