Introducing Rancho!

Since a while ago I started a project with friends to develop an Open Source group/project management tool with the best web framework out there – Django!

Today is the day! Rancho 0.1 alpha is out!!!

Rancho goal is to make it easy for any company or group of people to manage its projects and people.
Here are some of Rancho’s feature:

  • Clear and simple graphical user interface
  • Wikiboards that provide collaborative editors that also keep old versions
  • Exportation of wikiboards to several formats like PDF or HTML
  • Multi-lingual
  • Companies to group people
  • Threaded messages
  • ToDo lists
  • Milestone lists
  • Files with support for versions
  • Simple users management
  • E-mail notifications for actions within the projects
  • Statistics of every item in every project
  • Powerful permissions system

Go ahead and download Rancho from here or try a running demo here. Both the user name and password are ‘admin’.

In case you like Rancho, give us a hand and help us translating Rancho to your language.

For this or for questions, feedback, etc, please write to us using the contact form here.

Have fun with Rancho!

21 thoughts on “Introducing Rancho!”

  1. Because if I integrate my code with yours, I will be forced to adopt AGPL3 as well.
    And I really don’t want to have a very restrictive license applied to my code.

    I know that this is a matter of contention, but I don’t think the 35k (5535 words, to be exact) of hard-to-understand legalese that the AGPL3 is has much to do with freedom.

    So if I adopted Rancho for anything serious, I’d be in a bottomless pit of legal mud, because no one really knows what the Danish court system would do with the AGPL, and I could possibly be sued for not sharing everything related to the code (customer-specific changes and data included) with the general public.

    That’s just not a risk I’m going to take.

  2. Okay, that’s a matter of philosophy and vision.
    I believe that free software is NOT software you take for your profit and no one else’s. Modifying open source code and selling it for example, is not what I think open source is about.

    I think that for a project like Rancho, AGPL is the best way to guarantee all the rights but also obligations that Free and Open Source Software has.

    Anyways, that’s your opinion and thanks for sharing it.


  3. Hi there,
    are you brazilian? hehhehe

    Se sim, eu tenho um projeto em andamento basicamente igual ao seu, e em django tmb… se possível, entre em contato pelo gtalk (e-mail do post) para trocarmos uma ideia, ok?


  4. It’s nice to see at least some support for copyleft licenses in the Django community. While I certainly respect the views of authors who prefer more permissive licenses, I’ve noticed a borderline phobia of copyleft within communities of the various python web frameworks.

  5. Aww… I too am disappointed by the choice of AGPL for your project. I have partial implementations of similar tools in one of my own projects and was hoping for inter-operation or replacement, but your choice of license is too restrictive to work with my project.

    The other side of Free and Open Source Software is to promote community and the sharing of code between projects to the benefit of all. I sincerely believe that the AGPL is an awful firewall that doesn’t interoperate at all well with non-AGPL projects. (Not to mention that I believe the AGPL violates the spirit of copyright law in attempting to enforce the spirit of sharing, but that is another rant for another time.)

  6. No more Trac? No more Redmine? Great news! Rancho looks really nice.

    One thing – I’m curious whether Rancho integrates with svn, mercurial etc? I couldn’t find information about that on Rancho website.

  7. Well, yeah, it’s a philosophy-thing, but restrictive licenses (whether you call the obligations or something else) tends to limit the success of Open Source software.

    I work a lot with Drupal, and I can only say that its current success would not have been possible were it not for the so called web services loophole in the GPL2 (which is Drupal’s license).

    Because all the people that make their living with Drupal need to make tweaks and custom solutions for their clients, not to mention themes and graphics and that is usualy not very interesting code, and code that tells a lot about the clients’ internal system – information they would rather not have available to the general public.

    So I think that the thing that makes Open Source work is a _moral_ obligation to share, not the legal threat.
    Try and think of it – how many of the GPL lawsuits (there’s been a couple) brought back useful contributions to Open Source?

    So while you can do whatever you want with your code, it’s probably not going to see much uptake by other developers until you grant us the freedom to do as we please with it.

  8. Wow, great work! I’ll be sure to take a closer look the code as soon as I have some time on my hands. AGPL seems to be a good pick for a project like this… funny how Django projects seems to be almost exclusively BSD but I guess that comes from the strong focus on developers.

  9. args = [Variable(arg).resolve(context) for arg in url.split(‘,’)]
    AttributeError: ‘long’ object has no attribute ‘split’

    when adding a new project using mysql database.
    I did not have this issue using sqlite3 but has others of cours as it’s not supported. when switched back to mysql, I got this TemplateSyntaxError traceback.

    Anyway this project seems very promising.

    Keep the good work !

  10. following my last comment, you could activate “New tickets” for anonymous user in your trac in order to report bug, RFE, contribution and so on.

  11. Hi guys,

    Thanks for all your support and good words. Even for the non-AGPL people, thanks for expressing your opinions.

    For someone who asked about the version control systems integration, currently it’s included but we intend to develop that support soon.

    For any questions related with technical stuff, etc. please lets use the Rancho group on Google Groups:

    Kind Regards.

  12. Real nice.
    To bad you choose a v3 license – means I won’t use or contribute.
    As Linus described it, a license is meant to help you share your code and install trust among the developers. They way he describes GPLv3 it doesn’t provide enough trust. Contributes can decide they want to un-release their code, leaving you with holes in your project.
    I wander what it is your trying to guard against?

  13. Guys, again, we didn’t choose AGPL and its 3rd version following any conspiracy you might believe in. We analysed the licenses and asked some other people who know a lot about licensing what was the licenses that guarantee everybody gets the code with the best rights and obligations and AGPL v3 was the chosen one.


  14. Hi all,

    Just to say that Rancho’s Trac system now supports ticket submission from anonymous users.

    Please leave report any problems you find while installing or running Rancho there.

    Best Regards,

Comments are closed.