From BioAssist
Jump to: navigation, search



As soon as we have a reasonable list, I can setup a Doodle poll. But then again, I could also not do that. ;-) --Pieter van Beek

Notice: Hosting a repository within the domain is required. -- MvD

Probable Candidates

  • Atlassian Jira (or a hosted development suite Atlassian Jira Studio)
    • is being used by numerous open source projects, like the Apache Software Foundation, Zend Framework, Spring Framework, Hibernate, Grails, JBoss, Maven, OpenSymphony and many others. In our field the University of San Diego Department of Computer Science and Engineering (lots of omics) also uses Jira. -- Jeroen Wesbeek
    • has a large public plugin repository for connecting to and integrating with other systems (version control, hudson build server, workflow extensions, worklog and timetracking, etc etc) -- Jeroen Wesbeek
    • Free licensing for non profit and academic institutions. Hosting required.
      • AFAICS Jira is free for non-profit organisations, but Jira Studio isn't. --Pieter van Beek
      • Yes, but Jira was the candidate (someone changed it to Jira Studio?), while Jira Studio is something else as it is more than just Jira. It is Jira + Subversion + FishEye + Confluence + Greenhopper + Bamboo + Crucible in a hosted environment... -- Jeroen Wesbeek
    • Doesn't have SCM! --Pieter van Beek
      • Not true as there are many plugins providing VCS integration to link commits to bug resolvements (like the SVN plugin) and there are also several plugins to integrate JIRA into your IDE (Eclipse, Intellij). JIRA really is the most full featured platform in my opinion and I have used it for 2.5 years at my previous employer with Perforce integration. It definitely has my vote... --Jeroen Wesbeek
        • Are these plugins available for Jira as well, or only for Jira Studio? --Pieter van Beek
        • They are available for JIRA, and not for JIRA Studio (as the latter is a full featured hosted platform --> JIRA Studio comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existing plugins. Requests for additional plugins should be created as feature requests in the JIRA Studio project] ). Of course except for the client IDE integration plugins as these are obviously client specific. -- Jeroen Wesbeek
      • It does not have integrated e.g. SVN support, but that is not a problem, as SCM is an "invisible horse". Maybe ACL for SCM might be a problem... --Dmitry Katsubo.
        • While JIRA does not natively support version integration it can integrate with version control systems through plugins (svn, git, perforce, etc), see my remark above as well. It can also -for example- integrate with Hudson using a connector plugin to execute builds and display build statuses from within JIRA. -- Jeroen Wesbeek
        • Could you explain what you mean by "invisible horse"? I want to be able to browse through revisions, changesets and side-by-side diffs. --Pieter van Beek
    • Use with no hosting? --Dmitry Katsubo
      • Nice for individual projects, but not really suitable for a BioAssist group containing many projects -- Jeroen Wesbeek
  • Bugzilla
    • Open source, hosting required
  • RedMine
    • Open source, hosting required
  • Google code
    • No hosting required.
    • I don't think GoogleCode allows us to create our own, distinctively stylized, BioAssist project group. --Pieter van Beek


Nexus Maven Repository

Separate from (but related to) the forge / reposititory hosting issue: Would any of you have any interest in having a Nexus Maven Repository complement whatever hosting is chosen above?

Although it is mainly (but not exclusively) geared towards Java development, I think it could really complement the hosting efforts at NBIC in reducing the overhead of working with code developed and maintained by others.

For those unfamiliar with Nexus or Maven:

Nexus manages software "artifacts" required for development, deployment, and provisioning. If you develop software, Nexus can help you share those artifacts with other developers and end-users.

Maven’s central repository has always served as a great convenience for users of Maven, but it has always been recommended to maintain your own repositories to ensure stability within your organization. Nexus greatly simplifies the maintenance of your own internal repositories and access to external repositories. With Nexus you can completely control access to, and deployment of, every artifact in your organization from a single location.

(I'd be happy to elaborate if necessary.)