Changes in CakePHP and new plugins

This article is also available in the following languages:
By markstory
With the development of 1.3 and 2.0 well underway the CakePHP team has taken some time to re-evaluate and reconsider some of the tools we use as a team and as a community. Recently, CakePHP has undergone several changes, such as switching from Subversion to Git, and switching from trac to the current code.cakephp.org issue tracker. Each of these changes has brought change helping the community and project grow.
We feel at this time that the change to code.cakephp.org (using thechaw.com software) has not been an entirely beneficial change. The code.cakephp.org code base has a number of issues, and the present core team lacks the interest to improve this code as there are numerous existing solutions that fit our needs. After hours of discussion and considering many different options and avenues, we've decided that the best course of action is to utilise one of the many existing open source supporting project management web applications. We will be using github[1] for source control. In addition we will be using lighthouse[2][3] for issue tracking and temporary documentation in the form of wiki pages.

As before there are separate repositories for CakePHP1.x[4] and CakePHP2.x[5], as well as separate lighthouse projects. We feel these changes will provide the community with the tools and resources they need and have requested. In addition these changes will lighten the load on the core team allowing us to focus on we do best, create the best framework and related tools we can. We hope you - the community - can understand our motivations for wanting to switch and sincerely apologize for any inconvenience it will cause you.

Once the transition is complete trac and code.cakephp.org will be deactivated and all activity related to CakePHP will occur on github and lighthouse. We expect this transition to take no more than a couple of days. The repository on github has had some of the history rewritten to fix irregularities and errors that occurred in the past. If you have local changes in your clones you should be able to migrate and maintain those changes by rebasing your changes.

At this time we'd also like to announce the introduction of two new projects, named localized[6] and datasources[7]. Localized is a project designed to contain all the country specific validators for 1.3. At the time of writing we have 13 countries already partially or fully implemented. If your country is not in the repository please fork the project, add your country and send a pull request.

Datasources is a project to contain community powered datasource classes. Initially this repository will contain the datasources that have been deprecated and removed from 1.3. Over time we hope it grows into a useful repository for datasources of all shapes and sizes. By keeping these two projects separate from CakePHP we can provide a more flexible release schedule that does not conform to that of CakePHP itself.

Both datasources and localized have lighthouse projects for issue tracking so please file any issues with these plugins on their respective lighthouses[8][9]. If you are interested in getting involved with either project, please fork the project on github and send any pull requests.


[1] http://github.com/cakephp
[2] http://cakephp.lighthouseapp.com/projects/42648-cakephp-1x/overview
[3] http://cakephp.lighthouseapp.com/projects/42649-cakephp-2x/overview
[4] http://github.com/cakephp/cakephp1x
[5] http://github.com/cakephp/cakephp2x
[6] http://github.com/cakephp/localized
[7] http://github.com/cakephp/datasources
[8] http://cakephp.lighthouseapp.com/projects/42658-localized/
[9] http://cakephp.lighthouseapp.com/projects/42657-datasources

Comments

  • Posted 02/24/10 02:29:17 AM
    Hello cakeTeam!
    It would be nice to hear from anyone in this thread. There are multiple comments waiting for an answer and more spam comments to be deleted! Please... this all shines no good light on cakephp at all!!


    @Mauro: You can change your notifications in "MyAccount" but only for all articles/comments.
  • Posted 02/22/10 09:28:27 AM
    Can someone moderate the spam in the comments? I can help if you want.
    How can I unsubscribe from the comments notifications by email?
    Thank you!
  • Posted 01/11/10 08:26:07 AM
    another +1 for migrating tickets.
    Just like the source code and documentation itself, the database of issues along with their comments was a valuable resource both for the community, but especially for the developers (at least, it should be).

    Losing it means losing something very valuable.
    • Posted 01/11/10 08:28:36 AM
      Any comments from the dev-team on the issue with migration tickets?
  • Posted 12/11/09 10:03:38 AM
    The old version of trac.cakephp.org use to have lot of usefull information really helpfull for development. Now we only can read old tickets using the google's cache, but it will be unavailable at any moment. May be there is a way to import old tickets into the new system or just leave readable the old tickets in trac.cakephp.org

    Thank you!
    • Posted 01/05/10 05:48:48 PM
      The old version of trac.cakephp.org use to have lot of usefull information really helpfull for development. Now we only can read old tickets using the google's cache, but it will be unavailable at any moment. May be there is a way to import old tickets into the new system or just leave readable the old tickets in trac.cakephp.org

      Thank you!
      +1 here as well... Personally I've submitted several tickets that were never closed, and have found it frustrating ever since the move to thechaw that they have not been supported since. Personally I would rather maintain those tickets that we already have so that we know where we've come from and where we're going as a community.
    • Posted 12/18/09 03:28:07 AM
      The old version of trac.cakephp.org use to have lot of usefull information really helpfull for development. Now we only can read old tickets using the google's cache, but it will be unavailable at any moment. May be there is a way to import old tickets into the new system or just leave readable the old tickets in trac.cakephp.org

      Thank you!

      +1 here

      It is very disturbing to search for tickets and info on tickets these days, since nothing is found at the new location. It would be very helpful for our development!

      Is there a plan for importing the old tickets or maybe just make an archive with the olds tickets and entries?
    • Posted 12/11/09 11:03:15 AM
      The old version of trac.cakephp.org use to have lot of usefull information really helpfull for development. Now we only can read old tickets using the google's cache, but it will be unavailable at any moment. May be there is a way to import old tickets into the new system or just leave readable the old tickets in trac.cakephp.org

      Thank you!
      There is a Ruby script for something like that:
      http://github.com/shayarnett/trachouse
  • Posted 12/10/09 08:19:14 PM
    Very good decisions, esp the GitHub one.
    Sadly lighthouse's tagging is a bid, unsatisfying, but that aside its great.

    Thanks for your efforts to move all those chaw tickets over.
  • Posted 12/10/09 10:32:06 AM
    Is there any reason why CakePHP is using Lighthouse Wiki/Tracker versus the built-in ones with Github? The Github Ticket Tracker and Wiki pages are fully functional, and although they do not add an Milestones etc, these could easily be simulated using an (extremely) small application that hits the API and looks for tags on open tickets. It seems that there would be some people confused by the at least the built-in ticket tracker and that might cause inefficiencies in terms of migrating bug reports to Lighthouse.

    Just wondering. Other than that, this should reduce the amount of people asking for how to download the source, as it's no longer something they can blame on thechaw. It's now apparent they should probably learn a little more as to how Git works :)

    Good job everyone, and hopefully CakePHP continues to gain traction as you move ahead towards 1.3!
  • Posted 12/10/09 09:59:53 AM
    Nothing against the chaw...

    But it seemed to be an "almost" finished product. Github and Lighthouse are well proven systems, and with the integration between the two it should make development process much smoother for the whole team.

    So, great move, IMO.
  • Posted 12/10/09 08:33:33 AM
    Hi Mark,

    Is the API Generator plugin still staying on thechaw?

    Neil
  • Posted 12/10/09 08:23:16 AM
    I think the switch to Github and Lighthouse is a great move...

    Thanks for this.
  • Posted 12/10/09 06:19:26 AM
    Big thanks for this - the pubkey system in Chaw was a royal pain for a lot of people, including myself. I for one welcome our new Github overlords.
  • Posted 12/10/09 02:24:17 AM
    Could thechaw.com source code be opened then?
    • Posted 12/10/09 08:22:27 PM
      Could thechaw.com source code be opened then? Its not a project of the current core team memebers afaik. Probably ask on http://thechaw.com/
      Would be great if "debug kit", "cakebook", "api_generator" would find a place at cake's lighthouse account, maybe the bakery (for reporting issues on that one) too.

      What about cakemate and cake tm bundle and github?
  • Posted 12/10/09 02:15:04 AM
    That's a really great news guys. We were waiting for this since a loooong long time.

    Thanks !
    Sébastien

Comments are closed for articles over a year old