JoomlaWorks

Member Dashboard
  • Home
  • Extensions
    • Commercial
      • Frontpage Slideshow
      • K2 Plugin for sh404SEF
      • Simple Image Gallery Pro
      • SocialConnect
    • Free
      • K2
      • AllVideos
      • DISQUS Comments for Joomla!
      • IAKI (Import As K2 Image)
      • Quick Menu (for Joomla 4)
      • Simple Image Gallery
      • Simple RSS Feed Reader
    • Free On Github
      • Akismet for Kunena
      • Fill It Up
      • K2 Example Plugin
      • K2 Links for JCE
      • Rebuild K2 Image Cache (CLI utility for K2)
      • TinyLetter Subscribe
      • URL Normalizer
      • User Extended Fields for K2
  • Templates
    • Commercial Templates
      • Anagram
      • Archetype
      • BusinessOne
      • Ibento
      • Janaro
      • Kiji
      • Matchbox
      • nuMuzik
      • RadioWave
      • Toreda
    • Free Templates
      • nuModusVersus
      • Takai
  • Demos
    • Joomla Extension Demos
    • Joomla Template Demos
    • WordPress Plugin Demos
  • Labs
    • Web Apps
      • JSON 2 JSONP
      • Feed Reader (bookmarklet)
      • Device Info
  • Support
    • Documentation for Joomla Extensions
      • AllVideos
      • Frontpage Slideshow
      • Simple Image Gallery
      • Simple Image Gallery Pro
      • SocialConnect
    • Documentation for Joomla Templates
      • General Resources
        • Installation
        • Content
        • Customization
      • Commercial Templates
      • Free Templates
    • Get Help
      • Community Forum
        • Recent Topics
        • Categories
        • Create free account
      • Help Desk
      • Contact us by e-mail
      • Contact us on Facebook Messenger
      • Contact us on Twitter
  • About
    • Blog
    • Company
    • License & Terms of Service
    • Privacy Policy
  • My Account
10 05 2010
Written by  JoomlaWorks
Published in Blog
Tagged under
  • +16
  • +core team
  • +development
  • +ideas
  • +joomla
  • +thoughts
20 comments

A new perspective on the future development of Joomla

A new perspective on the future development of Joomla
There have been endless discussions around how Joomla is developed and maintained. One thing is clear though: development is quite slow and new significant features for the end user have not yet been introduced since the Mambo days... It's one of the reasons we decided to build K2, so we could introduce more modern and popular features into Joomla now.

But how could the development of Joomla not be slow? Given that the core team are human beings and not robots that work 24 hours a day on coding and debugging Joomla, it's really simple to realize why the development process is slow. Additionally, it is not easy to contribute code to Joomla because there are certain protocols need to be followed that make the entire process even slower.

Obviously this is not a post to bash the core team but a new thought on how we could possibly see Joomla being development in the not so distant future.

So how could we speedup Joomla development?

It's really simple. Joomla is modular by nature. So why not make development modular as well?

Here's a realistic example: Joomla is made up of components like com_content (for articles), com_menus (for the menu management system), com_polls (for the polls) and so on. The Joomla team could easily "contract" some professional developers and have them undertake the development of a specific component or perhaps module or plugin or whatever!

Imagine this: Joomla 1.6 will be released without comments (despite original claims for the opposite). How difficult would it be for some developers to create a comments component, contribute it to the default Joomla 1.6 distribution and also be responsible for maintaining the code!

One thing is for sure. A lot of weight would be lifted off the core team and significantly boost Joomla's development. If a bug is introduced on the above example of the comments component, the developers of that component could issue an upgrade and deliver the upgrade through joomla.org to all Joomla users. Why update an entire Joomla website when there is a specific problem in some component?

It's how things work in bigger software deployments like operating systems (OS). Teams and sub-teams developing and maintaining individual applications that make up the end product. The best example I guess is from the Linux world where there are applications developed for certain Linux distributions - the bond is so strong that you think they are actually part of the OS (see Ubuntu).

To conclude, I don't think it will be hard for the Joomla core team to find such developers to code and maintain specific elements of Joomla. If others can do this in projects with a gazillion lines of code, then Joomla can do it too.

We (as JoomlaWorks) have offered to code (yes, code, not debug) many times and I know a lot more people who have expressed the same interest as well. And I know it's difficult for the core team to just give away SVN access to others. I wouldn't easily trust other devs to code on K2! But I would certainly trust someone to develop and maintain a module of K2 and have it included in the default distribution.

The only hard part is for the Joomla core team to actually approve that some developer can deliver quality code by some standards, but it's really no biggie. We are a large community and there's a lot of talent to jump in and help things out. Can you imagine what a positive impact this would have to Joomla's PR and especially to users of other content management systems?

What do you think?

Read 143205 times Last modified on Friday, 03 April 2015 00:14

20 comments

  • westb westb 18 Mar 2011
    Comment Link


    I was really happy to find this. After several months of looking at Drupal I came away frustrated with the architecture, but amazed by the community - truly an engaged and engaging group of people. If you haven't done so it's worth a look at their code of conduct at http://drupal.org/dcoc" rel="nofollow">http://drupal.org/dcoc ( a direct adoption of Ubuntu's). Another contrast is looking at the project code - as mentioned several times - Joomla the code is very much lacking in comments. As a contrast you should take a look at some Drupal code, a stark difference.

    I'll throw in my opinion after spending only a few days looking at Joomla.

    - Architectural foundation of Joomla looks awesome - with the caveat about code comments. With Drupal, on the other hand the archetecthure is well .. a tough learning curve with lots of it's own unique and not always intuitive lexicon.

    - With all the Joomla hype about community and volunteers it's difficult to see evidence of an open source project with respect to core development - that concern is how I found this post - to the extent that there is a community, it does not appear to be developer driven. Joomla looks positioned to be an excellent "off the shelf" system with plenty of room for value added service providers to make a living from support and customization. It's a subtle but but significant distinction when we look at who's driving the bus and what the culture of the product community is.

    - At first I was puzzled by the copyright notice in all the source code by Open Source Matters, inc. Looking at the somewhat messy history of Mambo it is interesting that Joomla was spun off from the commercial side of Mambo (http://en.wikipedia.org/wiki/Mambo_(software)" rel="nofollow">http://en.wikipedia.org/wiki/Mambo_(software), My reason for looking into this is that Joomla has a commercial aura. Not a value judgement - just an observation. I can say that somehow looking at the board of directors of Open Source Matters with its origins and structure does not leave me with the same feeling of confidence I have - for example - with Connonical sitting behind ubuntu, or even IBM with apache.

    So here's what is bothering me a little. It seams that the people driving the system and making stragic decisions have the value added service provider as their core constituant - to the extent that they have errected onerous barriers to entry for core developers. As pointed out above, it could be soooo much better with a vibrant engaged community of core developers.

    Just sayin. Joomla, Koomla, Poomla, JoDrupLa ....


  • Fotis Evangelou Fotis Evangelou 12 Jun 2010
    Comment Link


    @Ron I'd definitely think twice before jumping on the other side :) The Joomla framework is far superior compared to other CMS' frameworks ;)


  • RonWM RonWM 12 Jun 2010
    Comment Link


    I love this discussion. It's the same thing I have been saying in my own circle for a long time. I've been using Joomla for the last 3 years and the initial love is gone. I have grown to become quite frustrated with the speed at which features are added. I am also frustrated with the lack of (good quality) documentation for developers - which also puts me in awe of fact that so many great extensions have been developed for Joomla.

    I think that the Joomla team should concentrate on making sure that the Framework is easier to use by developers. Make contacts, banners, polls, newsfeeds, and weblinks installable extensions as torkilj said. The Joomla core team should allow other developers to develop these instead, while they concentrate on the framework.

    So strengthen the framework, set standards for development, and allow the community to do what it does best: develop great Joomla extensions.

    I don't care that a comments component is not in the core, it is not a core functionality as ACL and unlimited nested categories are.

    The only other CMS I use professionally is Plone, and they do a great job of identifying what should be core functionality and what isn't. Still, there community is not half as big as Joomla's community is (in my own estimation). If the Joomla team follow their approach, Joomla will undoubtedly become the best all-round CMS to work with.

    Joomla has helped me put a good amount of money in my pocket over the years, but sad to say I'm now looking over in the Drupal camp for a possible new home as a PHP CMS user/developer. But as always, the grass is always greener on the other side...


  • torkilj torkilj 18 May 2010
    Comment Link


    I agree wholeheartedly; For instance, Joomla should make contacts, banners, polls, newsfeeds and weblinks installable extensions rather than core components. They are creations from an era long gone.

    I would love to see this as a milestone for 1.7. Less dead weight gives us more time to focus on what is important.

    Search has it's place in a CMS and framework, but not in it's current form.


  • Fotis Evangelou Fotis Evangelou 17 May 2010
    Comment Link


    In my opinion, Joomla should remain spartan on end user features and offer a very strong framework for developers to build web applications with it. That way, we get to see more features released sooner than a new Joomla distro. ;)

  • torkilj torkilj 16 May 2010
    Comment Link


    As long as the #Joomla core is not providing new features, K2 will still be in high demand, no? ;) #jos

  • Fotis Evangelou Fotis Evangelou 15 May 2010
    Comment Link


    You do have a point to what you say Torkilj...


  • torkilj torkilj 15 May 2010
    Comment Link


    Fotis: As you said, feature-wise not much has happened in the core since the Mambo days. Well, except that the codebase changed and a framework was introduced. So why should this not be a post to bash the core team? Who's responsibility is this lack of progress, if not the core team?

    I think the model for which development is now being done, is an obstacle in itself. With two developers being paid and the rest of all the project participants being volunteers, what does this do with accountability and motivation for those not being paid for their efforts? Paying one guy and not the other is basically like saying "his work is worth more than that guy's". This goes not only for the code production of the project, but for all contributors in all working groups.

    Paying a developer also gives the developer an economic incentive to try to hold on to his/her position; A job puts food on the table of course, but being a lead developer for a major project like this also gives your own business extra attention and credibility. This should have a nice effect on the amount of orders you get in and the fee you're able to charge for your work, so holding on to the position becomes imperative.

    All in all this model becomes an obstacle for innovation and development speed in my opinion; People who are skilled and "hungry" and want to bring this project forward, are being effectively stopped and are unable to contribute. If you, the lead developer, make it hard enough for people to contribute, they won't bother, and if people stop contributing then the project seemingly has no choice but to keep paying you to code.

    Or paying you not to code? For comments, ACL and nested categories were all part of stable, production ready code that was already being sold and used in live sites back in 2008 by jXtended, and donated to the Joomla project in January 2009. And now, announced the day after feature freeze, comments have been taken out.

    http://jxtended.com/blog/company/89-jxtended-investing-in-joomla-16.html" rel="nofollow">http://jxtended.com/blog/company/89-jxtended-investing-in-joomla-16.html

    Isn't it time to just say "okay, we tried and it did not work", and now let some fresh blood with vision, ambition and new energy step in and take over some of the heavy lifting? As Fotis said, we are just people, not machines.


  • gobezu gobezu 11 May 2010
    Comment Link


    thank you for this excellent idea although i see that the issue raised by @ewoutw is one which is of a real headache

    but since this blog entry is breathing pragmatism all over it let me suggest this

    k2, jseblod cck, resources, flexicontent and zoo - why don't you pull your resources together and develop the ultimate joomla cck and simply try to commit it to the 1.7

    another real concern is the maintenance and development of the joomla library where koowa having taken such a leap from current joomla library and offering so much more flexibility in terms of development and yet we know how that is not even being considered, at least as far as the readings from the various discussion group entries


  • Amy Stephen Amy Stephen 11 May 2010
    Comment Link


    Fotis - +1 This is how Drupal does it. Individuals/teams create and then maintain / further develop the modules for each release. And yes, it spreads the load and builds ownership. Now, they are positioning for more distributions on Drupal.org. That is made easier by the centralized repository of shared code and distributed support structure.

  • spletodrom spletodrom 11 May 2010
    Comment Link


    This is definitely some positive direction of thinking, also I'm glad to see retweets from core devs about posts like this lately :)

  • adamfoerster adamfoerster 11 May 2010
    Comment Link


    Some times I think the best thing for Joomla would be a fork. . .

  • websiteinabox websiteinabox 10 May 2010
    Comment Link


    Would have to agree concentrate on managing the development let others do the work :)

  • ewoutw ewoutw 10 May 2010
    Comment Link


    Too much is never good but sometimes discussion is good - you've just sparked a good one :)
    After the leaders decide who takes what portion of the development, I'd like two discussions. One is a sort of white paper process like we've seen before (how will that work with timed releases?). The second is a bit more discussion between the developers selected for a portion. Just like you probably do within your team, but then it is a discussion between the developers of the best 3rdpp alternatives to that portion of the core who hopefully are all volunteering and selected for the task together. Otherwise it's just moving selected third party extensions into the core. Mind you sometimes that wouldn't be a bad idea...

  • Fotis Evangelou Fotis Evangelou 10 May 2010
    Comment Link


    @ewoutw My belief is that if you wanna get things done fast and professionally, you need to code more and discuss less. The leaders orchestrating this will still be the core team and of course it's up to them to decide who could undertake portions of the development work. Once that is done, why should there be more talk? Were you asked for the features of com_content? Obviously not. But you perhaps had the chance to vote the features somewhere. The core team will then pick who is capable to deliver the code ;)


  • ewoutw ewoutw 10 May 2010
    Comment Link


    This is very similar to what my thoughts have come to. But if there are enough developers who would want to contribute in this way, then I see a risk of progress being criticised by competing developers. Since just before the NL Joomla days my thought was that it would be great to put the developers of competing products together to create something they are all happy with - leaving them free to offer their own software as a step up. What if you worked with the people of FlexiContent and jSeblod CCK in this way? K2 and the others might still be better than the result but no doubt the result would be a good component. Perhaps it would also lead to some unexpected advantages like some open Joomla standards for CCK content storage. The bottom line is: the project would need some clever way to select developers for a particular part of the code, and I think part of the cleverness would lie in making people work together.

  • RobertsWeb RobertsWeb 10 May 2010
    Comment Link


    Excellent post Fotis and ultimately could tie in with what a lot of other folks are thinking Joomla should become. Both inside the core and out. Monday is busy for me here, so I will have to keep this short, but again great idea.

  • Fotis Evangelou Fotis Evangelou 10 May 2010
    Comment Link


    Let me add 2 things:

    First, we have already witnessed modular development with the design of the default templates by RocketTheme, Robert Deutz & Angie Radtke, JoomlArt.

    Secondly, if core component/module/plugin development is given to approved third parties, then we could see Joomla with an automated updater for core extensions, thus make the entire update process simpler and faster. In other words, I would not have to go to joomla.org to update my com_comments component. The third-party developer would make the update available via joomla.org and directly into this automated core updater. ;)


  • philiplocke philiplocke 10 May 2010
    Comment Link


    What a great post - well done Fotis ;-)
    Simple really & would create an even better community feeling & belonging!

  • anotherguy anotherguy 10 May 2010
    Comment Link


    I completely agree with this perspective. After working with the Palm WebOS community for the last few weeks, I have been pondering how plausible it would be to change to this very system for Joomla. The Joomla core can be an excellent framework to allow developers to release extensions that fill in many of the empty spots found in the current releases, while also letting the core team focus on stability, speed, the user-interface and experience.

    Apple doesn't build a ton of features into their products, they built a UI andpowerful OS and then opened it up for others to develop with. Palm's webOS took this a step forward by making their development process sooo much simpler (uses html, js and css - languages we are already used to).

    I would love to see the Joomla team focus on the UI, UX, Documentation and distributing extensions. That would totally change the game that we play in, and put Joomla on top.


Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.

back to top
BY MAIL BY RSS

Archives

  • May 2024 (1)
  • March 2023 (1)
  • January 2022 (1)
  • July 2021 (2)
  • May 2021 (1)
  • February 2021 (1)
  • December 2020 (1)
  • September 2020 (1)
  • June 2020 (1)
  • May 2020 (1)
  • February 2020 (1)
  • January 2020 (5)

Tag Cloud

allvideos announcement apache community development frontpage slideshow future joomla k2 Performance plugin release sh404sef simple image gallery simple image gallery pro simple rss feed reader socialconnect tips update video

Latest Entries

  • K2 will not be made available for Joomla 4/5 - change of course
    Written by  JoomlaWorks
    30 May 2024
  • New free extension release: Quick Menu (for Joomla 4)
    Written by  JoomlaWorks
    06 Mar 2023
  • Simple Image Gallery (free) v4.2 released
    Written by  JoomlaWorks
    07 Jan 2022
  • Simple Image Gallery Pro v3.9.1 released (bug-fix release)
    Written by  JoomlaWorks
    26 Jul 2021
  • Simple Image Gallery Pro v3.9.0 released
    Written by  JoomlaWorks
    05 Jul 2021

Join Our Newsletter

Enter your e-mail address to subscribe to our new or updated product notifications. We send combined newsletters, so we won't spam you every week :)

Get Social

  • Twitter
  • GitHub
  • Facebook
  • GitHub (K2)
  • YouTube
  • Speaker Deck

Grab Our Feeds

  • Extension Updates
  • Blog
  • Videos
  • Presentations
Copyright © 2006 - 2025 JoomlaWorks Ltd.
JoomlaWorks Ltd. and this site is not affiliated with or endorsed by The Joomla! Project™. Any products and services provided through this site are not supported or warrantied by The Joomla! Project or Open Source Matters, Inc. Use of the Joomla!® name, symbol, logo and related trademarks is permitted under a limited license granted by Open Source Matters, Inc.
designed by Nuevvo