PostNuke

Site search

Search results

Number of hits: 80

Postnuke politics: a user's view   (News)

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

Generated on August 30, 2002.

New site addition to the PostNuke community   (News)

a wide range of independent forces from computer-generated art to prose and poetry, student news outlets, indy music and more.

The site runs PN Rogue .713, a range of modules such as My E-Gallery and XForum, and alltogether shows the ease of use of the PostNuke system even to the green-ish newbies. Give us a click and find out why we chose PostNuke over any other development system. A special thank you goes to John Cox and his dedication to free and independent web media over the past years, as well as his generous hosting and help with Freewriters.

http://www.freewriters.c

Generated on August 11, 2002.

Rogue .72 Pre-release Beta   (News)

Generated on July 29, 2002.

Rogue 714 files for spanish   (News)

but that's a reflex oy my being one. Spain users may elect to change some terms but I'd say you'll be hard pressed to find them.

I missed the Downloads module, which I'll upload next week (it's a wordy module).

To install
This file contains ONLY the spa subdirectories. You can just go to your root rogue dir and do a
tar -zxf pn714_esp.tar.gz.

Link to the tar.gz:
pn714_esp.tar.gz, 85 kb.

(the host site, bcrux, is now not-fully-upgraded, so it does not show a thing...)

Generated on July 14, 2002.

Rogue .714 Patch Available   (News)

Generated on July 7, 2002.

Development Report   (News)

The Rogue Report

We will be releasing at least one more package under the Rogue name. I hope to release .715 (or .72) either next weekend or the weekend after (if you are a betting type person go with the latter). I imagine that there will be a few DB changes, so the version number may escalate to .72. The database changes will be for bug fixes only.

I also hope to have a couple of new modules that have been ported to the API with the next release as well. We do have the Top Lists module ready to go, and I believe that the Ephemerids are ready as well.

The delay in the release is caused from our recent move to the new CVS, as well as the passing of Greg. However, I will be pushing for a release of the maintenance branch as soon as it is ready.

The adam_baum Report

We have decided to rename the .8 series from Ragnarok to adam_baum for obvious reasons. .8 is shaping up to be a very nice and revolutionary release. Many features have already been developed and tested and are ready to go. I am shooting for an August Feature Freeze with an early September release.

We have a ton of work to do in the meantime though. We desperately need people to volunteer to help with the module conversions to the API. As always, if you want your 5 minutes to 1 year of PostNuke fame and glory, we will welcome you into the fun.

Below is a very brief overview of what is in the pan this month for .8. This is meant as a tease, but we invite you to check out the CVS and see the changes for yourself. There are some omissions from the report (namely pnComments, some hooks that have been developed, and the pnExceptions), but it should give you a very nice detail as to what is being worked on.

The following is the adam_baum .8 report from Gregor:

Performance

Mike and Marco have started work on caching PostNuke data with a new set of functions, pnVar*Cached. Mike has written an excellent performance white paper
here.

TODO: Describe it in MDG, use it throughout core, database indexes

Sessions

Mike has begun to take a hard look at the sessions code, trying to isolate workarounds, and make the code saner. Depending on the decision about PHP minimum requirements
this code might be simplified further.

TODO: Fix all session bugs :)

Block layout

The basic block layout system is nearing completion. Modules can register their own tags.

TODO: MDG section for block layout, samples, resolve ML issues

Dynamic User Data

Dynamic User Data is incomplete, however Christopher Grote agreed to take a look at it and make it feature complete.

TODO: Implement required fields, code cleanup

Users module

The users module is currently un-maintained. We are looking for interested parties to take over the module.

TODO: Integrate registration workflow from x-users, templates, dynamic user data

Multilanguage System

The API functions for the new ML systems are complete. Work continues on a translation module.

TODO: upgrade path, translation module, implement storage backend

Installer

With Block layout in place, work on the Installer can begin in earnest. Zoom and Neo are building a nice remote installer which we will try to integrate with the core installer. The
aim is to leverage as much infrastructure as early as possible in the installation. This means loading of the API etc.

TODO: Design Installer architecture.

Database abstraction

Gary is working on table creation / modification support, the remaining omission from ADODB. Jeremy has MSSQL working, and Johnny is working on Postgres support.

TODO: merge MSSQL / Postgres work with core

Generated on June 29, 2002.

German Translation for Rogue .714   (News)

Generated on May 20, 2002.

Rogue .714 Released   (News)

Please post any bugs or problems to sourceforge. We appreciate your feedback.

Mirror available at:
ftp://ftp.totalpilot.com/pub/postnuke/Rogue_714.tar.gz.

Generated on May 18, 2002.

Proper Browser Title Bar Titles   (News)

Is there any way to have the page title imported from the title of whatever module is being browsed at the time? For instance, On this site to the menu on the right there is a Project Processes menu link. The menu under stands that Project Processes is a link to http://www.postnuke.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=10 Would in not be possible

Generated on April 29, 2002.

Idea...Maybe....   (News)

At our community we have webmail and homepages and I wanted to provide links to these programs in the member's area.

I hope you all know what I am talking about, because I am kind of wondering if I do...lol

Anyway I have been examining the PHP files trying to figure out which one puts the menu together and how to add my options to it as well. Can anybody explain which file does this or point me to the correct documentation if there is any?

Maybe this option could be put in future versions of PostNuke Rogue?

Generated on April 21, 2002.

Page 1 / 8 (1 - 10 of 80 Total)