[wp-hackers] Proposing WP Flavours (various WordPress forks) (Jean-Patrick Smith)

Dave R dave69 at gmail.com
Fri Dec 18 01:08:10 UTC 2009


Tell me, would you rate PodsCMS above Flutter? Used Flutter recently for the
first time, found good and bad, so curious for next major project.


Cheers,
Dave
....................................

business: www.zavadesign.com
personal: www.nakedchronicles.com
supports: www.michezoyouth.com


2009/12/18 Jean-Patrick Smith <chicagowebdev at gmail.com>

> I'd like to see a wordpress fork geared more towards a CMS, with the
> friendly backend and file-based templating system.
>
> Extend the widget functionality, making them more like Drupals blocks w/
> CCK
> and views, and i'd never use Drupal again...
>
> PodsCMS does this, but if you could fork wordpress and make PodsCMS a core
> feature, it'd be interesting to see where that went.
>
>
> On Thu, Dec 17, 2009 at 2:55 PM, <wp-hackers-request at lists.automattic.com
> >wrote:
>
> > Send wp-hackers mailing list submissions to
> >        wp-hackers at lists.automattic.com
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >        http://lists.automattic.com/mailman/listinfo/wp-hackers
> > or, via email, send a message with subject or body 'help' to
> >        wp-hackers-request at lists.automattic.com
> >
> > You can reach the person managing the list at
> >        wp-hackers-owner at lists.automattic.com
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of wp-hackers digest..."
> >
> >
> > Today's Topics:
> >
> >   1. Re: [ wp-hackers ] wp _ enqueue _ script() not working while
> >      in the Loop (TobiasBg)
> >   2. Re: [ wp-hackers ] wp _ enqueue _ script() not working    while
> >      in the Loop (scribu)
> >   3. Re: Settings API: Showing errors if validation fails (Otto)
> >   4. Proposing WP Flavours (various WordPress forks) (Callum Macdonald)
> >   5. Re: Proposing WP Flavours (various WordPress forks)
> >      (Harish Narayanan)
> >   6. Re: Proposing WP Flavours (various WordPress forks) (Ken Newman)
> >   7. Re: Proposing WP Flavours (various WordPress forks)
> >      (William Canino)
> >   8. ??i need urgente a password of a hotmail can anybody help
> >      me??? (carlos nunes)
> >   9. Re: ??i need urgente a password of a hotmail can anybody help
> >      me??? (Dion Hulse (dd32))
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Thu, 17 Dec 2009 13:46:39 +0100 (CET)
> > From: "TobiasBg"<wp-hackers at tobias.baethge.com>
> > Subject: Re: [wp-hackers] [ wp-hackers ] wp _ enqueue _ script() not
> >        working while in the Loop
> > To: wp-hackers at lists.automattic.com
> > Message-ID: <20091217124639.5C6C3181B04D1 at dd19416.kasserver.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hi,
> >
> > > That's why I use $wp_scripts->do_items(). It makes sure the same script
> > > isn't included twice. You just have to make sure you use the same
> handle
> > for
> > > both plugins.
> >
> > Argh, stupid me. Of course it does (and so does its wrapper
> > wp_print_scripts, that I prefer to use). I just had a typo in one of the
> > handles... Thanks for pointing me to it!
> >
> > I guess, I'll just leave this alone for today and go out and do some ...
> > Christmas Shopping! :-)
> >
> > Regards,
> > Tobias
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 17 Dec 2009 17:03:49 +0200
> > From: scribu <scribu at gmail.com>
> > Subject: Re: [wp-hackers] [ wp-hackers ] wp _ enqueue _ script() not
> >        working while in the Loop
> > To: wp-hackers at lists.automattic.com
> > Message-ID:
> >        <349fe48b0912170703l29937a07i517fc54417b4ef04 at mail.gmail.com>
> > Content-Type: text/plain; charset=UTF-8
> >
> >  You're welcome. :)
> >
> > I don't use wp_print_scripts() because some other plugins might have
> inline
> > scripts printed using the 'wp_print_scripts' hook.
> >
> >
> > On Thu, Dec 17, 2009 at 2:46 PM, TobiasBg <wp-hackers at tobias.baethge.com
> > >wrote:
> >
> > > Hi,
> > >
> > > > That's why I use $wp_scripts->do_items(). It makes sure the same
> script
> > > > isn't included twice. You just have to make sure you use the same
> > handle
> > > for
> > > > both plugins.
> > >
> > > Argh, stupid me. Of course it does (and so does its wrapper
> > > wp_print_scripts, that I prefer to use). I just had a typo in one of
> the
> > > handles... Thanks for pointing me to it!
> > >
> >
> >
> > --
> > http://scribu.net
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Thu, 17 Dec 2009 09:05:11 -0600
> > From: Otto <otto at ottodestruct.com>
> > Subject: Re: [wp-hackers] Settings API: Showing errors if validation
> >        fails
> > To: wp-hackers at lists.automattic.com
> > Message-ID:
> >        <161617690912170705r449ed407p8eeefc7caa822742 at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > You could use the admin_notices hook to generate your own error
> > messages based on whatever you like.
> >
> > Basically, hook a function to admin_notices. In this function, you
> > need to check for your error case and generate output based on it.
> > Then, you can unset $_GET['updated'] to prevent the Settings saved
> > message from showing up.
> >
> > Basically something like this:
> >
> > 1. On error detection, save the error somewhere that you can pick it
> > up later. Like an option, or a transient, or something.
> >
> > 2. On the admin_notices hooked function:
> >
> > if ($parent_file == 'options-general.php' && $_GET['page'] ==
> > 'my-plugin-page') {
> > // check the plugin option for errors
> > // found some errors? If so, then {
> > <div id="message" class="updated fade"><p><strong>No! You'll overload
> > the reactor!</strong></p></div>
> > //   unset $_GET['updated']
> > // }
> > } // end function
> >
> > That should do the trick.
> >
> > -Otto
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Thu, 17 Dec 2009 10:46:27 -0600
> > From: Callum Macdonald <lists.automattic.com at callum-macdonald.com>
> > Subject: [wp-hackers] Proposing WP Flavours (various WordPress forks)
> > To: wp-hackers at lists.automattic.com
> > Message-ID: <1261068387.8378.85.camel at buna>
> > Content-Type: text/plain
> >
> > Holamigos,
> >
> > Instigated in part by recent discussion on ticket 5066[1], I think the
> > time has come to create a few WordPress forks. I'm imagining a set of
> > patches applied against core rolled into a tgz. I can see a few initial
> > options:
> > * Strip out all the update checking stuff
> > * Anonymize update checking
> > * Security focused patches
> > * Remove post revisions, etc...
> >
> > I'm sure other people will have their own particular choices.
> > Personally, I'd like to see a tin foil flavour of WordPress with ultra
> > conservative privacy settings. :-)
> >
> > Rather than create a single fork, I propose to create wpflavours (or
> > maybe wpflavors), a project to provide the means to maintain multiple
> > WordPress flavours. I'm seeing an svn repo, patches (maybe using
> > quilt[2]) and a mailing list.
> >
> > I've started a discussion[3]. If you're interested in contributing, let
> > me know. I'll most likely only proceed if there is sufficient interest
> > in maintaining patch sets.
> >
> > Warmly - Callum.
> >
> > [1] http://core.trac.wordpress.org/ticket/5066
> > [2] http://savannah.nongnu.org/projects/quilt
> > [3] http://www.callum-macdonald.com/2009/12/17/proposing-wp-flavours/
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Thu, 17 Dec 2009 17:12:49 +0000
> > From: Harish Narayanan <harish.mlists at gmail.com>
> > Subject: Re: [wp-hackers] Proposing WP Flavours (various WordPress
> >        forks)
> > To: wp-hackers at lists.automattic.com
> > Message-ID:
> >        <4c95b6c20912170912mf90ac53id044a65193794cf8 at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > On 17/12/2009 16:46, Callum Macdonald wrote:
> > > Holamigos,
> > >
> > > Instigated in part by recent discussion on ticket 5066[1], I think the
> > > time has come to create a few WordPress forks. I'm imagining a set of
> > > patches applied against core rolled into a tgz. I can see a few initial
> > > options:
> > > * Strip out all the update checking stuff
> > > * Anonymize update checking
> > > * Security focused patches
> > > * Remove post revisions, etc...
> > >
> > > I'm sure other people will have their own particular choices.
> > > Personally, I'd like to see a tin foil flavour of WordPress with ultra
> > > conservative privacy settings. :-)
> > >
> > > Rather than create a single fork, I propose to create wpflavours (or
> > > maybe wpflavors), a project to provide the means to maintain multiple
> > > WordPress flavours. I'm seeing an svn repo, patches (maybe using
> > > quilt[2]) and a mailing list.
> > >
> > > I've started a discussion[3]. If you're interested in contributing, let
> > > me know. I'll most likely only proceed if there is sufficient interest
> > > in maintaining patch sets.
> >
> > I haven't any opinions on the specific flavours mentioned, but I have
> > one thing to add to this discussion. I have been part of a few Free
> > Software projects that recently migrated their development
> > repositories to Bazaar[1] and launchpad[2]. (The specific choices are
> > not important to the discussion, but the capabilities these choices
> > provide are.)
> >
> > This was supposed to be an infrastructural change, but it had some
> > unintended, interesting and useful consequences. Because
> > branching/merging was now easily possible[3], people who had cool
> > ideas of their own maintained a branch (or a fork, or a parallel
> > version of the tree, however you prefer to call it) containing their
> > own experiments and pet features. Then, other curious people would
> > check these features (flavours, in Callum's words), and the clearly
> > useful changes would be merged back into the arbitrarily decreed
> > "primary tree."
> >
> > I think considering such a development process will allow for a lot of
> > things:
> >
> > * Allowing people to easily implement and publicise their own pet
> > features and ideas.
> > * Allow others to easily try out these implementations.
> > * Doesn't require maintaining sets of patches Callum proposed.
> > * Allows the "primary project branch" to easily pull in important,
> > useful and cool changes from these offshoots.
> >
> > If someone is interested in seeing this in action, I can set up a
> > mirror to the WordPress source repository on a hosted site (e.g.
> > launchpad, github, bitbucket, ...). Others can branch/fork/clone/...
> > this and maintain their pet features.
> >
> > Harish
> >
> >
> > [1] http://bazaar.canonical.com/en/
> > [2] https://launchpad.net/
> > [3] It is possible in svn as well, but most big outfits tend to have a
> > centralised development repository much like WordPress does,
> > discouraging it. In comparison, check out the number of parallel
> > branches for a project like MySQL https://code.launchpad.net/mysql .
> >
> >
> > ------------------------------
> >
> > Message: 6
> > Date: Thu, 17 Dec 2009 12:32:00 -0500
> > From: Ken Newman <Ken at adcSTUDIO.com>
> > Subject: Re: [wp-hackers] Proposing WP Flavours (various WordPress
> >        forks)
> > To: wp-hackers at lists.automattic.com
> > Message-ID: <4B2A6B10.6060201 at adcSTUDIO.com>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> >
> > On 12/17/2009 11:46 AM, Callum Macdonald wrote:
> > > Instigated in part by recent discussion on ticket 5066[1], I think the
> > > time has come to create a few WordPress forks. I'm imagining a set of
> > > patches applied against core rolled into a tgz. I can see a few initial
> > > options:
> > > * Strip out all the update checking stuff
> > > * Anonymize update checking
> > > * Security focused patches
> > > * Remove post revisions, etc...
> > >
> > > ...
> > >
> > > Rather than create a single fork, I propose to create wpflavours (or
> > > maybe wpflavors), a project to provide the means to maintain multiple
> > > WordPress flavours. I'm seeing an svn repo, patches (maybe using
> > > quilt[2]) and a mailing list.
> > >
> > Hello,
> >
> > I think that the privacy concerns are largely address by a declaration
> > that WP does phone home and why that's desirable, and with a link to
> >
> >
> http://markjaquith.wordpress.com/2009/12/14/excluding-your-plugin-or-theme-from-update-checks/
> > for those that need to disable checks on sensitive data.
> >
> > As far as forks go, I don't really think that's needed if the Canonical
> > Plugins are used instead. Lots of functionality some would like added to
> > core can (shortly) do so with canonical plugins.
> >
> > Additionally, Functionality that some would like **removed** from the
> > core could be likewise dealt with in a canonical plugin. This goes for
> > non-privacy related functionality like:
> >
> >   1. Code Editors for Themes and Plugins: Some people hate this and
> >      want it out of core, some like it tho; would make a good canonical
> >      plugin.
> >   2. The new Image Editing Functionality: Some think it adds to much
> >      bloat and functionality is too niche. Others absolutely love it. I
> >      think it should be a canonical plugin, but installed and activated
> >      by default.
> >   3. TinyMCE or LightBox: I'm using these as illustrating examples.
> >      Making these canonical plugins, with other versions, Colorbox or
> >      the text editor from google (whatever) would provide a smoother
> >      changing out of functionality. These wouldn't be able to be turned
> >      off without a substitute, which is why I included it here for
> >      consideration.
> >
> > I bring this up because I'm not sure if its been considered how
> > canonical plugins can be for moving out core functionality as well as
> > bringing in existing plugins as canon.
> >
> > Its also a better way to go then forking I believe.
> >
> > Thanks,
> > Ken
> >
> >
> > ------------------------------
> >
> > Message: 7
> > Date: Thu, 17 Dec 2009 15:19:46 -0500
> > From: William Canino <william.canino at googlemail.com>
> > Subject: Re: [wp-hackers] Proposing WP Flavours (various WordPress
> >        forks)
> > To: wp-hackers at lists.automattic.com
> > Message-ID:
> >        <e4dc67e0912171219x7183a3fagfcb5d1cbd3a820d at mail.gmail.com>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Considering its thousands of action and filter hooks -- and more and
> > more made in each release, in my opinion, WordPress is too
> > customizable and open-ended to need particular forks.... that is,
> > unless a very good programmer (or a group of them) comes up with a
> > direction for WordPress that the lead devs (Boren, Jacquith,
> > Mullenweg, Ozz and Westwood) feel strongly against.
> >
> > Realistically, the lead devs cannot allow/approve every kind of patch
> > that will be suggested that disables features or takes WordPress in
> > every sort of direction.  While a plugin developer might say, "Hello,
> > here is a one-line diff that will let WordPress handle Foobar content,
> > I think people will find it useful," if the trac discussion says
> > wont-fix, it's a wont-fix.  I can see how the wont-fix feels to the
> > plugin developer; the word "fork" will come to her mind.
> >
> > I haven't yet worked with WP Core closely to see how open-minded or
> > politically-heated trac discussions get. To Foobar plugin developers:
> > go right ahead anyway, strut your stuff, tell your plugin users to add
> > that line as an installation step!! Don't ever let anybody tell you
> > your idea isn't worth shit.
> >
> > Thank you for letting me speak.
> >
> > W.
> >
> > 2009/12/17 Ken Newman <Ken at adcstudio.com>:
> > > On 12/17/2009 11:46 AM, Callum Macdonald wrote:
> > >>
> > >> Instigated in part by recent discussion on ticket 5066[1], I think the
> > >> time has come to create a few WordPress forks. I'm imagining a set of
> > >> patches applied against core rolled into a tgz. I can see a few
> initial
> > >> options:
> > >> * Strip out all the update checking stuff
> > >> * Anonymize update checking
> > >> * Security focused patches
> > >> * Remove post revisions, etc...
> > >>
> > >> ...
> > >>
> > >> Rather than create a single fork, I propose to create wpflavours (or
> > >> maybe wpflavors), a project to provide the means to maintain multiple
> > >> WordPress flavours. I'm seeing an svn repo, patches (maybe using
> > >> quilt[2]) and a mailing list.
> > >>
> > >
> > > Hello,
> > >
> > > I think that the privacy concerns are largely address by a declaration
> > that
> > > WP does phone home and why that's desirable, and with a link to
> > >
> >
> http://markjaquith.wordpress.com/2009/12/14/excluding-your-plugin-or-theme-from-update-checks/
> > > for those that need to disable checks on sensitive data.
> > >
> > > As far as forks go, I don't really think that's needed if the Canonical
> > > Plugins are used instead. Lots of functionality some would like added
> to
> > > core can (shortly) do so with canonical plugins.
> > >
> > > Additionally, Functionality that some would like **removed** from the
> > core
> > > could be likewise dealt with in a canonical plugin. This goes for
> > > non-privacy related functionality like:
> > >
> > > ?1. Code Editors for Themes and Plugins: Some people hate this and
> > > ? ? want it out of core, some like it tho; would make a good canonical
> > > ? ? plugin.
> > > ?2. The new Image Editing Functionality: Some think it adds to much
> > > ? ? bloat and functionality is too niche. Others absolutely love it. I
> > > ? ? think it should be a canonical plugin, but installed and activated
> > > ? ? by default.
> > > ?3. TinyMCE or LightBox: I'm using these as illustrating examples.
> > > ? ? Making these canonical plugins, with other versions, Colorbox or
> > > ? ? the text editor from google (whatever) would provide a smoother
> > > ? ? changing out of functionality. These wouldn't be able to be turned
> > > ? ? off without a substitute, which is why I included it here for
> > > ? ? consideration.
> > >
> > > I bring this up because I'm not sure if its been considered how
> canonical
> > > plugins can be for moving out core functionality as well as bringing in
> > > existing plugins as canon.
> > >
> > > Its also a better way to go then forking I believe.
> > >
> > > Thanks,
> > > Ken
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > >
> >
> >
> > ------------------------------
> >
> > Message: 8
> > Date: Thu, 17 Dec 2009 20:45:52 +0000
> > From: carlos nunes <carlos_nunes42 at hotmail.co.uk>
> > Subject: [wp-hackers] ??i need urgente a password of a hotmail can
> >        anybody help me???
> > To: <wp-hackers at lists.automattic.com>
> > Message-ID: <BAY119-W49234FD0A7854ECE2A98FA8860 at phx.gbl>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> >
> > HI GOOD EVENING I NEED A PERSON HOTMAIL PASSWORD, I MEAN I THINK THAT
> > PERSON IS CHEATING ON ME SO IF YOU CAN HELP ME CAUSE I ALLREDY TRIED SO
> MANY
> > SOFTWARE LIKE PERFECT KEYLOOGER WICH GOT STEALTH MODE AND I JUST NEED THE
> > PASSWORD OF THAT PERSON ONCE I GET IT I JUST TAKE A LOOK AND THEN I GET
> OUT
> > PLEASE I REAL NEED IT IF I SENT YOU THE EMAIL OF THAT PERSONA CAN YOU
> HELP
> > ME?
> >
> >
> > THANKS BEST REGARDS
> >
> > CARLOS
> >
> > _________________________________________________________________
> > Windows Live Hotmail: Your friends can get your Facebook updates, right
> > from Hotmail?.
> >
> >
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009
> >
> > ------------------------------
> >
> > Message: 9
> > Date: Fri, 18 Dec 2009 07:55:20 +1100
> > From: "Dion Hulse (dd32)" <wordpress at dd32.id.au>
> > Subject: Re: [wp-hackers] ??i need urgente a password of a hotmail can
> >        anybody help me???
> > To: wp-hackers at lists.automattic.com
> > Message-ID: <op.u43oeea6spxmuu at dd32>
> > Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
> >
> > Please be advised that this is a -WordPress- discussion mailing list
> > designed for -Hackers-. Please see
> > http://en.wikipedia.org/wiki/Hacker_(programmer_subculture)<http://en.wikipedia.org/wiki/Hacker_%28programmer_subculture%29>
> <http://en.wikipedia.org/wiki/Hacker_%28programmer_subculture%29>for a
> > explanation of the term -Hacker-
> > This list does not contain (Or it may, But its not for it) anyone who can
> > help you with your stupid non-programming needs.
> >
> > On Fri, 18 Dec 2009 07:45:52 +1100, carlos nunes
> > <carlos_nunes42 at hotmail.co.uk> wrote:
> >
> > >
> > > HI GOOD EVENING I NEED A PERSON HOTMAIL PASSWORD, I MEAN I THINK THAT
> > > PERSON IS CHEATING ON ME SO IF YOU CAN HELP ME CAUSE I ALLREDY TRIED SO
> > > MANY SOFTWARE LIKE PERFECT KEYLOOGER WICH GOT STEALTH MODE AND I JUST
> > > NEED THE PASSWORD OF THAT PERSON ONCE I GET IT I JUST TAKE A LOOK AND
> > > THEN I GET OUT PLEASE I REAL NEED IT IF I SENT YOU THE EMAIL OF THAT
> > > PERSONA CAN YOU HELP ME?
> > >
> > >
> > > THANKS BEST REGARDS
> > >
> > > CARLOS
> > >
> > > _________________________________________________________________
> > > Windows Live Hotmail: Your friends can get your Facebook updates, right
> > > from Hotmail?.
> > >
> >
> http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009
> > > _______________________________________________
> > > wp-hackers mailing list
> > > wp-hackers at lists.automattic.com
> > > http://lists.automattic.com/mailman/listinfo/wp-hackers
> > >
> >
> >
> > --
> > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
> >
> > End of wp-hackers Digest, Vol 59, Issue 85
> > ******************************************
> >
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


More information about the wp-hackers mailing list