Zikula Community

• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Apr 27, 2005
  • Posts: 7

  Posted: Apr 27, 2005 - 07:19 AM

  Thanks to all who post. I understand the desires of those who say postnuke should be a base or platform which modules are integrated into but before that system is implemented I think there needs to be some changes in the way modules and postnuke setup is done:
  
  Here are a few thoughts I had on the topic:
  1. A new branch of postnuke support is needed that certifies modules for the generic postnuke “platform”. Authors who want their modules listed must submit them. From there they are tested and then published if they pass and do things their documentation states they do.
  2. A module database available from the postnuke site allowing people to easily look through all the modules submitted in the above system (#1) and their progress in the certification system is needed. The current “pnModules” section of the postnuke site has no intuitive system for finding modules. Isn’t that what it’s supposed to be for???
  3. I think a modules system like the Linux Kernel would be VERY nice. (don’t freak out here, keep reading)
  4. The Postnuke download package would be HUGE (and should be a BitTorrent type distribution).
  5. In the setup web gui (similar to the kernel) you can choose from modules you'd like.
  6. Only those modules selected would be included into the final production site being run.
  7. We can still have competition between modules BUT we can also help newbees keep from pulling their hair out by giving them a basic easy way to install needed modules that we KNOW work.
  8. Going a little further, perhaps even a base module built into PN allowing people to get certified modules from with in postnuke. (like red carpet ??).
  
  I do not intend to offend anyone working on the modules system or currently supporting the postnuke project. I’m very grateful for your work. I only feel in the interest of helping the project progress and helping the user base grow we could look at some of these ideas.
  
  Any thoughts anyone?
  BK

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Apr 27, 2005 - 12:56 PM

  byteharmony

  
  1. A new branch of postnuke support is needed that certifies modules for the generic postnuke “platform”. Authors who want their modules listed must submit them. From there they are tested and then published if they pass and do things their documentation states they do.

  
  Good idea in theory, in practice, unless someone wants to fund the testers/certifiers, it's going to be hard to do because of time constraints.
  

  Quote

  2. A module database available from the postnuke site allowing people to easily look through all the modules submitted in the above system (#1) and their progress in the certification system is needed. The current “pnModules” section of the postnuke site has no intuitive system for finding modules. Isn’t that what it’s supposed to be for???

  
  Hammerhead and I have something in the works, but there's some things we still have to figure out to get it to be acceptable for our needs. If 1 can be done, it won't be hard to add that in to the system that is in the works.
  
  
  As far as the rest of your suggestions, which as I read them really is one more, this whole thing will be addressed in version .8, but not exactly as you laid it out. With .8, the installation system will recognize what modules are present in the distro, and I'm not sure how it's set right now, it will either install them, or present a list to choose from (I think it would be good to have a flag that a distro creator could set to decide how and have the core capable of both way). This will simplify the ability to create custom distro's with whatever modules you want in them.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Apr 27, 2005
  • Posts: 7

  Posted: Apr 27, 2005 - 02:54 PM

  Quote

  1. A new branch of postnuke support is needed that certifies modules for the generic postnuke “platform”. Authors who want their modules listed must submit them. From there they are tested and then published if they pass and do things their documentation states they do.

  
  
  I agree, most corporates would keep strict control over this part of the product, but that control costs time ($). What about building some type of wikipedia or ebay feedback type system to determine what modules are “certified”? If a module gets enough positive feed back then (quantity and quality) then it can be integrated into the main release. Most people don’t want to test for fun, but I’d bet that they wouldn’t mind leaving feed back. Feed back isn’t quite the same as a test certification, but with enough of it should give similar results.

  • 
  •  
• HalbrookTech
  
  

  • Rank: Developer
  • Registered: Dec 31, 1969
  • Last visit: Jun 01, 2010
  • Posts: 6859

  Posted: Apr 27, 2005 - 02:59 PM

  The main release, as you've been told already, will be streamlined, not added to.
  
  --
  Home Page | Find on Facebook | Follow on Twitter
  

  • 
  •  
• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Apr 27, 2005
  • Posts: 7

  Posted: Apr 27, 2005 - 03:17 PM

  I hope you don’t think I’m trying to waste your time, as that is not my intent. My intent is to bring idea’s into the development fold that would allow the postnuke system to be:
  1. More functionable for tasks people want to do with it “out of the box”
  2. Easier to use
  3. More secure
  4. Help the online community communicate and share information easier on the postnuke web site.
  
  I think point 4 is the one that perhaps did not have enough detail. I think the web site is the place for feedback, statistics and information to be gathered so that releases can be made based on statistics, not just personal preferences. (I’m guessing that’s what’s used right now, no offence intended)
  
  

  Quote

  The main release, as you've been told already, will be streamlined, not added to.

  
  
  I agree, the main release or “CORE” of postnuke should be slimmed down, efficient, as simple as possible. But why not give people all that we can with the package. Who wants to buy a car frame and then have to special order the motor, radio, wind shield wipers.....
  
  I’d like to see a setup procedure that allows people to choose what modules are copied into the “modules” folder:
  
  

  Quote

  6. Only those modules selected would be included into the final production site being run.

  
  
  The default could be to have nothing selected, if nothing was selected the install would very slim indeed. But in this world of highspeed connections if I want a postnuke system setup I’m not worried about a 400MB download that takes 2 – 3 hours, I’m worried about 5-10 hours attempting to find 1 or 2 modules that I need to do the main task for the site. Internet connection speeds get faster, and search time keeps getting more expensive.
  
  I want to look at postnuke as a finished package: If I got it on CD I could use it. I wouldn’t want to get a word processor that is bare bones slimmed down and then have to download and setup a spell checker, font set, table tool........
  
  If the options (modules) are written and working include them in the download (setup) and let me choose them if I want them at setup. Don't make me "hunt" for them and install them manually after. I believe most people who want a web solution want to accomplish most of their goals in one package, not a journey of modules and integrations. Don't get me wrong, I like modules and integration, but why bother if no one can find what you're looking for and even when you do you don't know if it's going to work or be worth the time to download and setup???
  
  
  
  
  BK

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.