[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[jfw] Re: Packages - Keep or Dump?

Yes. What I'm saying is that it will be better time to ask ourselves which packages to drop when we will know which we will need and which not.
At this point I think we should keep at lease in maintenance mode all that are already bundled with CMS.

For the next CMS version, when we will have a better picture we will need to reevaluate, just like Andreas said.
But no major refactorings at this point.

For example I haven't found a good and simple i18n package out there that beats JLanguage so maybe JF Language v2 is may be best on the market.

On Tuesday, May 26, 2015 at 12:45:37 AM UTC+2, Andreas Tasch wrote:

I think it makes totally sense to really keep only a handful Joomla! Framework packages and pick all other stuff from matured composer packages - thats the whole idea behind composer, npm and those other package managers. The framework devs should compose a set of packages to built on (with all ther knowledge and insight) - after that there will still be enough work left to build a next-gen core.

Take Drupal, I think what they do makes totally sense. Choose a framework or single packages which do the basic stuff and extend from there. They use some Symfony packages but stick with their own kernel implementation [1] and add other nice packages as Guzzle. Take a look at their composer.json: https://github.com/drupal/drupal/blob/8.0.x/core/composer.json, they even use a zend framework package. Why not. Better to contribute back to already mature packages and do not reinvent the wheel. Use all that now free manpower to focus on the main product.

Am Montag, 25. Mai 2015 23:17:57 UTC+2 schrieb Nils Rückmann:
It's obvious that there are very different opinions about the Framework and the CMS. I mean, there are even opinions to drop the Framework at all. And i don't see that all those people will find a common ground in the near future. So what's about this:

A new "Icarus" playground project ( with a better name ;) ) which is under the Joomla brand, but independent in a way that it has his own leadership. No investments are necessary. Just give those people who wants to work on a modern base a playground where they can share thoughts and build modern libraries together. If it's going down like the current Framework, there will be no bad blood, because of endless fights between different teams. And if it succeed, well, then we all should proud and of course use the new code in other Joomla projects.

Framework source code: https://github.com/joomla-framework
Visit http://developer.joomla.org for more information about developing with Joomla!
You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-framework+unsubscribe AT googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-framework.