Vanilla 1 is no longer supported or maintained. If you need a copy, you can get it here.
HackerOne users: Testing against this community violates our program's Terms of Service and will result in your bounty being denied.
Options

Why vanilla isn't on Sourceforge

When ever I'm looking for free opensource software, sourceforge is the first place I look.
Why isn't Vanilla mentioned on Sourceforge?

Comments

  • Options
    MarkMark Vanilla Staff
    It may be silly, but I don't like sourceforge. I think it's a badly designed site and very unintuitive - so I'm not a part of it. I know there are many arguments to use it, but I just don't care to.
  • Options
    fair enough.
    do u have plans for a bug tracking or code management for vanilla. like Google code hosting.
  • Options
    MarkMark Vanilla Staff
    I've been working with Jazzman's issue tracker extension for a client. I want to get some of the kinks out before I use it here, but I will soon enough...
  • Options
    Mark, you could also have a look at trac (http://trac.edgewall.org/). Here at my work we use it for a couple of projects and it works great, has an integrated Wiki for documentation, tickets and great online svn support with visual diff's. The only thing that is missing is a discussion board ;). That said, if anyone ever feels like integrating both, feel free to let me know.
  • Options
    nup trac is out of question. its based on python.
    Issue tracker will work just fine. just need svn checkin
  • Options
    if you could get similar diff rendering like trac into vanilla, that would be great. For me that is the main reason we use trac.
  • Options
    oh issue tracker isn't there yet. right now it's just a listing. nothing else
  • Options
    Mark has dedicated server. Sure he could install trac... But, do we need it?
  • Options
    edited May 2007
    i don't think we need trac. All examples i ahve seen of trac suggest it is to handle one project. I haven't seen one where it is handling one main project and tons of subprojects. How will trac work for vanilla plus extensions in the same interface? We need something like Drupal Issue (http://drupal.org/project/issues) which we already have as in Issue Tracker. just need a way to have access to any extension and be able to checkin bug fixes, since original authors have abondoned the extensions. thats all. plus diff support and reverts
  • Options
    dan39dan39 New
    edited May 2007
    What about Bugzilla for issue tracking?

    http://www.bugzilla.org/

    They just released Bugzilla 3.0. You can test it out here: http://landfill.bugzilla.org/

    Another alternative is Google Code. See Dinoboff's Vanilla Packer page:
    http://code.google.com/p/vanilla-packer/
  • Options
    edited May 2007
    With Google you will have to create an independent project for every vanilla extension. these projects cannot be linked together, or maintained together. Mark already has what he needs. Now can we sink this thread or close it
  • Options
    lechlech Chicagoland
    Trac can handle multiple projects, just depends how you treat them. In this case they would be treated as a Vanilla "component" rather than its own individual project in the dev tree. Added it also works with subversion which is kind of a plus. The important part is that each file would have a maintainer which is all that is really necessary to treat it as "it's own project" so that's all really a grey area.

    But it's really all what Mark needs vs what everyone else wants and his decisions usually do trump whatever we want. I wouldn't consider this discussion "sunk" or "closed" as it was merely a suggestion and a topic of discussion which is still somewhat on track. The decision was made though. Mark is using something else so we'll have to trust he made a wise choice based on how he's going to do it since he does after all maintain the body of code which is Vanilla. And I respect that choice.
  • Options
    SF could use a better layout. I don't care for the place that much either. It is unfortunate cause there are a lot of great projects there. Tons of dead ones too I might add. The real pity is the fact that the project managers do not use it very well. No screenshots on what really needs them. No one ever checks the forums there, too many links to too many places. Ive seen a ton of projects that have different infos on their SF page and their "site" page. Of course most of these issues are with the people using the site, but a site is only as good as its community.

    Keep kicken ass Lussumo!! :)
  • Options
    Same problem here, no screenshoots. atleast i have screenshots for almost all my extensions. hopefully I'll rub on other developers
  • Options
    lechlech Chicagoland
    Depends really on the type of project or extension, you can't really provide an accurate screenshot for something that does 99.9% of it's work on the back-end of things like text formatters. That would require some kind of whimsy abstract to say "this is what it is/or should look like" with the same applying to things like developing frameworks. Some things just don't really need a screenshot as it's not exactly helpful when in that particular context.

    But I'll agree that there are a ton of of dead or dying projects and that SF seems a bit mis-used depending on how you look at it. The latest update to the site seems to have set things back rather than making it more useful. Particularly the advanced search they've implemented, it seems to have taken several steps back instead of going forward.

    I think accurate descriptions trump that of a screenshot, while sometimes the screenshots do complement software in more ways then one. There's still those cases where screenshots, no matter how pretty make it only that: pretty. While underneath the engine is a a cluttered and dysfunctional mess, BF titles are a good example of this. :)
  • Options
    BF titles?
  • Options
    lechlech Chicagoland
    BF = BattleField... IE: BattleField 1942, Vietnam, 2, 2142... don't get me started on this one, but I was simply using it as an example. Either way it still illustrates my ideas on the subject :)
This discussion has been closed.