Update on 1.6 feature patch guidelines
Wilco Jansen
As promised I am writing down the 1.6 feature patch guidelines...in
short a description that explains what it takes get your feature patch
accepted into the Joomla core code. Please be patient for just some
days, it is a pretty long article and I need some people to proof read
it before we can publish, sadly some of those people most likely will
be traveling upcoming days (I know, bad excuse :-P).
If you have any question in the mean while, feel free to fire them
here.
Regards, Wilco
Mr Phil E. Taylor
process/idea?
Does it replace it?
Kindest regards
Phil.
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
> To post to this group, send email to joomla-de...@googlegroups.com
> To unsubscribe from this group, send email to joomla-dev-gene...@googlegroups.com
> For more options, visit this group at http://groups.google.com/group/joomla-dev-general?hl=en-GB
> -~----------~----~----~----~------~----~------~--~---
>
>
Wilco Jansen
Mr Phil E. Taylor
help an aging developer out with a definitive link to the roadmap
containing the features that you are talking about that need to be
completed?
Is there a absolute list of tasks/features?
Wilco Jansen wrote:
> Hi Phil,
>
> This does'nt have any relation with white papers. Everyone is free to
> suggest any feature he/she needs, but for now it should be clear what
> our focus is...the 1.6 roadmap. Only in very specific cases we will
> consider changes on the current roadmap, but for now we really will
> prevent us from scope creeping.
>
> Looking forward to your feature patches.
>
> Regards, Wilco
> Joomla Development Coordinator
>
> On 2/9/09, *Mr Phil E. Taylor* <ph...@phil-taylor.com
> <mailto:ph...@phil-taylor.com>> wrote:
>
> Where does the submitting of patches sit with the white paper
> process/idea?
>
> Does it replace it?
>
> Kindest regards
> Phil.
>
>
> Wilco Jansen wrote:
> > Hi All,
> >
> > As promised I am writing down the 1.6 feature patch guidelines...in
> > short a description that explains what it takes get your feature patch
> > accepted into the Joomla core code. Please be patient for just some
> > days, it is a pretty long article and I need some people to proof read
> > it before we can publish, sadly some of those people most likely will
> > be traveling upcoming days (I know, bad excuse :-P).
> >
> > If you have any question in the mean while, feel free to fire them
> > here.
> >
> > Regards, Wilco
> >
Ian MacLennan
http://community.joomla.org/blogs/leadership/724-development-coordinator-summit-summary.html
Ian
Wilco Jansen
You probably have been busy in NY, and missed that blog...happens the best ;-)
To help you even more, here comes the better copy/pasting:
We discussed 1.6 a "lot". What we resolve was that there would be a single "alpha" stage. The following is a list of what we resolved would form the alpha, and if not finished, would prevent the alpha from being released. These features are:
- The Access Control system needs to at least emulate what is in 1.5, allow adding of new groups and access levels, and allow you to set new "view" rules for at least articles.
- Implement a new JForm
- Implement and standardise several new triggers
- Implements a Javascript translation system
- Implement new controller dispatchers
- Implement a JContent class that will be used by onPrepareContent plugins and views
- Upgrade to Mootools 1.2
- Finish the new extension updater work
After we release the alpha, each beta release will be time-boxed (we hope that not more than four are required). The following is a list of the features highly desired for the final distribution. Each features need to be "ready" in order to be included in each beta release. Some of these features will make it in the alpha, but will not prevent the alpha being release if they are not ready. Overall though, we will need significant help from the Joomla development community to pull all these features together:
- Implement unlimited depth categories (but not multi-mapping)
- Refactor the user management system and make it more extensible (eg, allow customer user fields)
- Implement a comments system (including pings and trackbacks)
- Implement queue redirects (allows you to, for example, return to the previous page you were on after you edit something)
- Refactor parameters and make them more extensible (for example, plugins could allow you to add additional custom parameters to articles)
- Finish MVC-ing the Administrator components (we need lots of help here)
- Implement Captcha helpers for any form
- Implement systems whereby external authentication systems, such as LDAP, can map to our new Joomla user groups
- Reimplement the ability to select multiple categories for some views in com_content (was in 1.0, got dropped in 1.5 for some unknown reason)
- Implement a database driven installation log
- Refactor JError
- Examine the PDF generation system in detail and see if we can make it work properly (otherwise we will look at dropping it if we can't make it work well)
- Localise the Invalid Token messages
- Drop the Polls component because the quality of that extension is pretty bad and there are much better third-part alternatives available
- Convert all layouts to symmantic and XHTML Strict
- Convert of ini-based "params" fields to use JSON instead of INI format (huge technical and performance improvements). Note, the language files will remain in INI format.
Regards, Wilco Jansen
Joomla Development Coordinator
Mr Phil E. Taylor
daughter to the Brooklyn Aquarium to see Sea Lions :-)
I guess I was looking for a document entitled "Joomla 1.6 Roadmap" :-)
hehe - I guess that this blog post is the fore-runner of such a document
then... as some of these things need expanding a little before a
"community developer" can work on a "feature patch" (E.g. "Implement a
database driven installation log") and some need a hell of a lot of
discussion and fine tuning before any code can be mocked up.
Some I guess are quick and easy (Upgrade mootools, nuke com_polls)...
hehe - re-reading the blog post there are 1,2,3,4 headings (4 being
roadmap) but only 1,2,3 sections :-) hehe
I guess what I'm trying to say is that is ok keep saying you want
community supplied feature patches, but unless those developers know
exactly what is required for that feature then there is not a lot they
can do. Also there needs to be some structure else you will get 5
developers all submitting their patches for "Adding a comments system"
and then be downhearted when non of them get used (however good).
Maybe rather than have individual developers working on "feature
patches" you could set up working groups, or at least a "feature
manager" that has responsibility for a certain features development
(coordinating several developers working on the same feature patch) -
else like I say you might get 5 patches all implementing the same
feature in different ways (Not always a bad thing: allows "you" (the svn
commit team) the decision which to use) - but can be a bad thing as
developers could get disheartened when their hard work was rejected.
Imagine Andrew had provided the ACL improvements as a single feature
patch, and Mr A N Other was already working on it within the core team
(The "OTher" Andrew) - would you turn away months of planning
preparation and development to dishearten a developer? some of these
things on the roadmap could take months of development time!!
Just thinking aloud - no axe to grind here, just trying to see if there
is a clear way ahead, maybe all these things are in hand with Wilcos
yet-unreleased guidance document...
Phil.
Wilco Jansen wrote:
> Hi Phil,
>
> You probably have been busy in NY, and missed that blog...happens the
> best ;-)
>
> To help you even more, here comes the better copy/pasting:
>
> We discussed 1.6 a "lot". What we resolve was that there would be a
> single "alpha" stage. The following is a list of what we resolved would
> form the alpha, and if not finished, would prevent the alpha from being
> released. These features are:
>
> * The Access Control system needs to at least emulate what is in
> 1.5, allow adding of new groups and access levels, and allow you
> to set new "view" rules for at least articles.
> * Implement a new JForm
> * Implement and standardise several new triggers
> * Implements a Javascript translation system
> * Implement new controller dispatchers
> * Implement a JContent class that will be used by onPrepareContent
> plugins and views
> * Upgrade to Mootools 1.2
> * Finish the new extension updater work
>
> After we release the alpha, each beta release will be time-boxed (we
> hope that not more than four are required). The following is a list of
> the features highly desired for the final distribution. Each features
> need to be "ready" in order to be included in each beta release. Some
> of these features will make it in the alpha, but will not prevent the
> alpha being release if they are not ready. Overall though, we will need
> significant help from the Joomla development community to pull all these
> features together:
>
> * Implement unlimited depth categories (but not multi-mapping)
> * Refactor the user management system and make it more extensible
> (eg, allow customer user fields)
> * Implement a comments system (including pings and trackbacks)
> * Implement queue redirects (allows you to, for example, return to
> the previous page you were on after you edit something)
> * Refactor parameters and make them more extensible (for example,
> plugins could allow you to add additional custom parameters to
> articles)
> * Finish MVC-ing the Administrator components (we need lots of help
> here)
> * Implement Captcha helpers for any form
> * Implement systems whereby external authentication systems, such as
> LDAP, can map to our new Joomla user groups
> * Reimplement the ability to select multiple categories for some
> views in com_content (was in 1.0, got dropped in 1.5 for some
> unknown reason)
> * Implement a database driven installation log
> * Refactor JError
> * Examine the PDF generation system in detail and see if we can make
> it work properly (otherwise we will look at dropping it if we
> can't make it work well)
> * Localise the Invalid Token messages
> * Drop the Polls component because the quality of that extension is
> pretty bad and there are much better third-part alternatives available
> * Convert all layouts to symmantic and XHTML Strict
> * Convert of ini-based "params" fields to use JSON instead of INI
> > <mailto:ph...@phil-taylor.com <mailto:ph...@phil-taylor.com>>>
> wrote:
> >
> > Where does the submitting of patches sit with the white paper
> > process/idea?
> >
> > Does it replace it?
> >
> > Kindest regards
> > Phil.
> >
> >
> > Wilco Jansen wrote:
> > > Hi All,
> > >
> > > As promised I am writing down the 1.6 feature patch
> guidelines...in
> > > short a description that explains what it takes get your
> feature patch
> > > accepted into the Joomla core code. Please be patient
> for just some
> > > days, it is a pretty long article and I need some people
> to proof read
> > > it before we can publish, sadly some of those people
> most likely will
> > > be traveling upcoming days (I know, bad excuse :-P).
> > >
> > > If you have any question in the mean while, feel free to
> fire them
> > > here.
> > >
> > > Regards, Wilco
> > >
> > >
>
>
>
>
>
>
Kevin Sookocheff
I am a developer looking to contribute to Joomla feature patches and
would really love some guidance on these features as Phil suggests.
For example, I could take a look at the PDF generation system but I
don't know what is wrong with it since PDF generates fine for me. A
little more detail on the expectations of these features would be
great. Of course maybe my comments are premature since I have yet to
see Wilco's document.
Kevin
> > <mailto:ianlen...@gmail.com>> wrote:
>
> > This is probably the document to look at atm.
>
> > Ian
>
> > On Mon, Feb 9, 2009 at 4:43 PM, Mr Phil E. Taylor
>
> > Forgive me, google was unable to find the roadmap for 1.6 :-)
> > Can you
> > help an aging developer out with a definitive link to the roadmap
> > containing the features that you are talking about that need to be
> > completed?
>
> > Is there a absolute list of tasks/features?
>
> > Wilco Jansen wrote:
> > > Hi Phil,
>
> > > This does'nt have any relation with white papers. Everyone is
> > free to
> > > suggest any feature he/she needs, but for now it should be
> > clear what
> > > our focus is...the 1.6 roadmap. Only in very specific cases we
> > will
> > > consider changes on the current roadmap, but for now we really
> > will
> > > prevent us from scope creeping.
>
> > > Looking forward to your feature patches.
>
> > > Regards, Wilco
> > > Joomla Development Coordinator
>
> > <mailto:p...@phil-taylor.com>
> > > <mailto:p...@phil-taylor.com <mailto:p...@phil-taylor.com>>>
>
> > > Where does the submitting of patches sit with the white paper
> > > process/idea?
>
> > > Does it replace it?
>
> > > Kindest regards
> > > Phil.
>
> > > Wilco Jansen wrote:
> > > > Hi All,
>
> > > > As promised I am writing down the 1.6 feature patch
> > guidelines...in
> > > > short a description that explains what it takes get your
> > feature patch
> > > > accepted into the Joomla core code. Please be patient
> > for just some
> > > > days, it is a pretty long article and I need some people
> > to proof read
> > > > it before we can publish, sadly some of those people
> > most likely will
> > > > be traveling upcoming days (I know, bad excuse :-P).
>
> > > > If you have any question in the mean while, feel free to
> > fire them
> > > > here.
>
> > > > Regards, Wilco
>
> > >
>
>
> 6KViewDownload
Wilco Jansen
The document has become quite big, and is up for final review. Hope to get it out this weekend. I will drop a note when it is available.
Regards, Wilco