Home » Community

Category: Community

Announcing the end of ChiliProject

Unfortunately, we have to announce the end of ChiliProject. This might not come as a surprise for people following the GitHub repository or this blog as there were indeed no new releases or even commits for quite some time.

We have now faced the inevitable truth that we, the current developers of ChiliProject, are no longer able to maintain the current code base or develop new features for ChiliProject. Thus, we believe it is necessary to shutdown the project and make it clear that there will be no further updates in any way to ChiliProject.

While the current website on chiliproject.org is still available, we have removed the possibility for changes. Going forward, we will provide a static version of the wiki and a dump of the current issue list. Furthermore, we have closed all outstanding pull requests on GitHub.

We are very thankful for the support we have received over the years from all of you. I’m sorry we have to let you down. Should anyone be willing to step up and continue to maintain ChiliProject, please contact either Holger or Felix.

In order to continue using your project management systems, we recommend that you migrate to a currently maintained system, e.g. Redmine. As a last update, we plan to provide a migration script to move your existing ChiliProject data to Redmine. In the meantime, you could use one of the community-provided scripts, e.g. the instructions by Christian Daehn of ASinteg GmbH.

So Long, and Thanks For All the Fish!

Going forward: get involved!

After the dry spell we went through in the last few months, the ChiliProject Team wants to get things going again. We still want to get more people involved in ChiliProject and are looking for ways for the Team to communicate outwards but also for the Community as a whole to better communicate. We’re also going to apply more focus on the technology and code work, which will mean some hard-to-make decisions and harsh cuts, but we think those will help us make better progress now and things easier later.

On the community side of things, we’re going to try having a development and a general mailing list. This might sound like an old idea but that’s one we’ve been discussing on and off since the beginnings of ChiliProject. The biggest concern was that it will split discussions even further than they actually are, but the fact is we don’t have correctly functioning discussions at all at the moment. You can find more arguments in the ChiliProject forums. Anyone interested in discussing things ChiliProject or just following what we’re discussing can get on the chiliproject-devel Google Group. There’s only one list for the moment, should things get too crowded there we’ll open more as needed.

On the code side of things, one thing we learnt the hard way was that we’re too few people for too much work / too many goals. One of our top priorities was trying to decruft the codebase, but we’ve been held back amongst other things by concerns about compatibility (backward, with Redmine, with plugins and so on) and not dropping features even if we don’t think they’re central to ChiliProject. All those things have cost us a lot of time and energy, and we don’t think we can afford that anymore. Current candidates for legacy we’d like to shed are the Darcs adapter and the old Rails 2.3 Engines currently used for ChiliProject plugins, but more on that in an upcoming post.

So those are the things currently on the minds of the ChiliProject Team. If you want to get involved, want to yell at us, tell us that we are wrong or just want to read more about where ChiliProject is headed, sign up to the chiliproject-devel Google Group and chat with us.

Retrospective

So the last 6 months happened. Many of you rightly noted that ChiliProject development halted to near nothingness in that time and Holger and I are not only very sorry but also feel guilty about that (anyone who wants to know why one can feel guilty about a voluntary contribution, go read the excellent article Open Source Guilt & Passion by Nick of 37signals). I’m writing this post to try to explain what happened in that time. It’s not meant as an excuse, rather it’s a retrospective to try to avoid this in the future, ideas welcome. We’re also working on getting the ball rolling again, but more on that in a coming blogpost.

One thing that took a lot or time in the past months was University. Holger actually is not a student anymore as he finished his thesis and graduated as a Master in Software Engineering last summer, congrats for that! I don’t have as much to show for it but between work and studies, the time I had left for ChiliProject was little and far between.

Speaking of work, the more important change in our time for ChiliProject went down in October and November. Those of you on board with us since the beginning might remember that we started ChiliProject backed by our then employer finnlabs. finnlabs made several contributions in the months following that, including the current design (thanks for that!), but the way those contributions were made didn’t correspond to what ChiliProject expected. The passing months only went to show that the way Holger, Eric and I envisioned Open Source for ChiliProject wasn’t compatible to the type of Open Source work finnlabs was willing to do, ultimately leading to finnlabs working on their own fork of ChiliProject (rebranded since then). Holger’s and my growing frustration with finnlabs also lead us to quit finnlabs, and we started working with Plan.io since October and November 2012 (you can read Holger’s and my introductory blog posts on the Plan.io blog). Our current work at Plan.io consists of Redmine hosting and development, so we’re still pretty near to what we’re doing here 🙂

Now that the dust has mostly settled over our job and company changes, we’re looking forward to working again on ChiliProject, but as mentioned earlier, that’s for another blog post!

Team changes

We’re always looking for people helping us to make ChiliProject better and we are lucky to have some great contributors investing their free time to fix bugs and generally improve ChiliProject.

In the last couple of weeks, one contributor stood out in particular as he has been steadily submitting improvements to the user interface part of ChiliProject, sanitizing and modernizing the HTML and JavaScript little by little. We were impressed by his patience and the perseverance he showed when providing his technical knowledge and when including our feedback in the areas he contributes to. Consequently, the ChiliProject team unanimously decided to ask him to join our team of core developers. I am very pleased to welcome Andrew Smith on board and we’re looking forward to working even more closely with him.

Going forward, Andrew plans to finish the migration to jQuery away from Prototype, support a fully responsive design, rewrite the CSS to SASS, and apply a lot more Web 2.x and Rails 3+ buzzwords. You can often find him in the ChiliProject IRC channel as EspadaV8, on Twitter as @EspadaV8 and on GitHub as EspadaV8. In his day job he is a PHP developer for an advertising agency in Brisbane, Australia and aside from working on ChiliProject he spends his free time cycling and reading SciFi and Fantasy.

The other change in the team is about someone several of you have inquired about. Unfortunately, we have to announce that Eric Davis is stepping down as the Project Lead of ChiliProject. He and his his wife had the joy to welcome a new member to their family earlier this year and he doesn’t feel the little time he can spare for ChiliProject will allow him to live up to the role of the Project Lead. Eric won’t leave us completely and will continue to be a member of the ChiliProject team. We all thank him for his hard work and guidance and hope to see his contributions extend again once he can justify it.

The team unanimously elected Holger Just as the new Project Lead. Holger’s primary new reponsibilty is to settle any deadlocks in decision making but he will still be a member among others of the ChiliProject team. Furthermore, his expressed opinions will continue to be only his own unless explicitly stated otherwise. Please read the Project Lead page in the wiki for more information or get in touch with us if some things seem unclear.

ChiliProject.org migrates to a new host

ChiliProject.org will be migrated to a new host starting Tuesday 29-05-2012 11:00 UTC, the site might be unavailable for minutes at a time, please plan accordingly. You might experience some connection issues for a few hours until the DNS update has propagated through the network. Please contact us (for example on Twitter: @ChiliProject) should any problems persist.

Our thanks go to Muntek Singh (aka Khalsa/@SikhNerd) for providing the hosting for ChiliProject.org since its launch 16 months ago!

Update (28-05-2012): we had to move the host migration from 6:30 UTC to 11:00 UTC, sorry for any inconvenience this might cause. The above post has been updated accordingly.

Update (29-05-2012): the migration went through smoothly and the DNS records should be updated now, please contact us if you still notice strange things, thanks!

Development meeting May 20th – Come join us!

We will be having a development meeting for May 20th at 1600 UTC in IRC

You can read about how the meetings are run here.

The topic list for the meeting is on the wiki page and is focused around finalizing the 2.0 release, and planning the 3.0 release. The meeting will last for about 1 hour, though some discussion happens after the official meeting.

If you’ve never been on IRC, please come early so we can help you out, some more information on IRC is on this page.

The meetings are public and open to everyone so if you’re going to attend, please add yourself to the attendees list. Even if you don’t have a lot to add right now, we would love to have you!

Development Team Meeting Tomorrow!

We have a development meeting planned for tomorrow March 18th at 1600 UTC in IRC

You can read about how the meetings are run here.

The topic list for tomorrow’s meeting is on this page and is mostly focused around the 2.0 release. The meetings generally last 1 to 2 hours, depending on the agenda and attendees. Please do all possible to adjust your schedule to be able to attend the meeting in it’s entirety.

If you’ve never been on IRC, please come early so we can help you out, some more information on IRC is on this page.

If you’re going to attend, please add yourself to the attendees list. Even if you don’t have a lot to add right now, we would love to have you!