17
I Use This!
Activity Not Available

News

Analyzed almost 3 years ago. based on code collected over 3 years ago.
Posted over 10 years ago by bherlig
All good things must come to an end Dear Users, Origo was first released in 2006 to provide an all encompassing platform for software development, where users could not only host their code, but also document their project, manage issues and ... [More] releases, and a whole lot more. Origo currently hosts 7500 projects with over 19000 users. What started as a purely academic project at ETH's computer science departement, was carried on as a purely FOSS (free and open-source software) project by a small team of dedicated developers, administrators and supporters. Together we manage all aspects of Origo: tending to your needs as users, maintaining the hardware and all the while developing code, bringing you new features and eliminating bugs. Unfortunately we couldn't grow our team as much as our platform did. Amongst other things, with one of us changing jobs we are now at a point where we can't guarantee the continued service of the Origo platform, and thus you as users with an adequate experience anymore. We thus decided to close Origo by the end of May 2012. What does this mean for you? As of now, we've closed the creation of new projects. Note that you can still create new users & add them to your projects should you whish to do so. All other services are continuing as normal, most importantly the subversion repositories. We'd like you to start migrating your projects to other places. You can download a full nightly dump of your project's repositories from the "Development" page, e.g. http://svn.origo.ethz.ch/dump/$PROJECT_NAME/latest.tar.gz This is the most flexible way to move your repository. Note that neither the repositories nor the nightly dumps will be available after May 31st. Should you have any other needs or questions, feel free to contact us at support@origo.ethz.ch We thank all who have used and supported Origo over the years. Till, Pat, Beat, the Origo Team [Less]
Posted about 12 years ago by bherlig
Dear Users, We at team Origo are quite excited about the latest release - this weekend we have released a new Origo version, 2010.5! Together with the previous, intermediate milestone 2010.4, Origo provides new features, two of which I want to ... [More] present here. A Brand new Design The Origo Team has found a new member in Eva, who not only brings new ideas to Origo, but a fresh, non-programmer mind and a very keen eye for design :) She has spend some quality time resolving design sins that we have committed in the past, and has revamped the basic layout, colors and look of the site. The result is the new theme named "Oxymoron". The changes you see are only part of the redesign: we plan to work some more on the different elements, and we will also reorganize the menu. The most important changes in the theme are: New Header This is perhaps the most prominent change: we've change the header of the page containing the menu and navigation links. The top links are enlarged and put in nice big buttons at the top of the page. New Menu The menu that was previously on the left side is now integrated into the header directly under the top links. Note that although the location changed, the menu points themselves are the same. Git Support It has always been one of Origo's principal design goals to be as flexible as possible. It is why we chose a plug-in system for the web front-end, and a message based node system for the back-end. In this release, we've added Git as a second flavor of source code management system, a fast version control system where each clone is a full-fledged repository, which allows for distributed workflows for both individuals and teams. Origo's Git support integrates into the existing architecture, i.e. pushes to your Origo's Git repository are tracked by the work item system and will show up on the dashboard and result in email notifications. Each project can hold multiple repositories, all of them protected by the usual access rights. Together with private projects - a project type that allows client users that can access content and issues that are otherwise hidden from the public - we've decided to release Git exclusively on oriact.com, our Origo Team Workspace for users with professional needs. Other Changes Besides these two bigger features there is a number of smaller changes and other improvements in this release: Annotated tag- and visibility changes in email notifications API changes - please consult the changelog for details A semantic change in the return value of issue.retrieve Some project related calls have a new parameter denoting a project's revision control system (SVN or Git) Simple matrix on project request & manage page explaining access rights Update to newer Drupal Core & 3rd party modules (Diff, jQuery-UI, Pathauto, Token) As always, the more technical details of this update and its list of bug-fixes can be viewed in Origo's 2010.5. [Less]
Posted about 12 years ago by bayt
We're aware that our documentation is not very user-friendly and it is difficult to understand what Origo's capabilities are. Here is a new picture of the architecture of Origo - hopefully this helps!
Posted over 12 years ago by bherlig
Dear Users, We've just updated the servers with Origo's new version, 2010.3. By far the largest change of this release is the issue tracker: large parts of the the main overview page were rewritten to support a brand new feature - custom filter ... [More] categories. But there's a slew of other new features, too! Here's an overview over all of them Custom Categories Until now, the issue tracker's filtering capabilities were quite limited: you're provided with a fixed set of six filters, the "Tags" containing most of the tags one assigned to the issues. But we now have changed this to be much more flexible! You may categorize issue tags by using a special delimiter, "::" (two colons). Each used prefix will cause a separate filter to appear on the issue overview page. So by using e.g. "priority::high" and "priority::low" in your issues will result in a new filter, which you can direct use for searching through your issues. We also added the possibility for project owners to order and hide the filters, so you can rearrange them to suit your needs. Just click the "Customize Filters" link, and drag and drop the filters around, or click the "hide" icon to remove them from public view. Horizontal Layout We've rearranged some of the input fields in the issue pages. It now puts some of the inputs side-by-side, resulting in a broader page, and thus eliminating some of the necessary scrolling to get to the main "Description" field. Take Button The "Assigned To" input field now sports a "Take" button - a useful little shortcut when assigning issues to oneself! Code Highlighting Patrick enabled a whole lot of new languages in the code highlighting engine for you to enjoy more colorful code :) Check the list of supported languages right below the text input field when creating new or editing existing content. Striked-through issue links Another little useful helper: each issue that you link to using the [[issue:123]] shortcut will decorated with a strikethrough if the referenced issue is closed. This comes in very handy on lists of issues, where you can see the state of an issue at a glance! Pagination of Reported Issues The Reported Issues page was overhauled and now displays your issues in a paginated table, thus resolving the display errors we've had for users with a lot of reported issues. New Setting "rss show unread" You can now control the contents of your dashboard RSS feeds: should it display all work items (and let your RSS reader handle which ones you already read), or only new ones that you haven't seen before? Uncheck the box to restrict the feed to unread items only (note: this setting may take a while to show its effect, as the feeds are cached on the server). New Setting "issues per page" There's a new setting where you can choose how many issues you want to display on a single page of the issue overview. The "Reported Issues" page will use the same setting. Configurable project frontpage Project owners now have the option to change the project's landing page, e.g. to directly show the issue-tracker when navigating to the project. The setting can be found in the Navigation section of the project settings. Other Changes Of course there are further changes and bug fixes in this release, amongst them Show diff in work item notifications for edited comments Lift restriction on uploadable files (don't check file extensions) API changes The user.list_reported_issues API call was changed so it can be used with pagination. Consult the changelog for details. Code blocks now show line-numbers Highlight changes to special tags SVN Links in commit mails wrong Improve sign in message Refrain from creating Issue-Nodes when an error in the back end occurs (prevents "Zero Issues") As always, the more technical details of this update and its list of bug-fixes can be viewed in Origo's changelog. [Less]
Posted over 12 years ago by bherlig
This Wednesday, I've held a talk at the User Group of Switzerland. Note the somewhat special extend of this talk: it only encompasses part of Origo, namely it targets Origo and its use of Drupal highlights three specific problem areas For your ... [More] reference, the slides of my talk (in German) are attached to this post. For questions and/or clarifications, please be welcomed to post a comment below. AttachmentSize origo_dug_07-2010.pdf541.93 KB [Less]
Posted over 12 years ago by jutzeler
Hello everyone! I would like to inform you all that the Oriact homepage (the selling platform of Origo) has a new design. You can visit the page at: www.oriact.com The goal of the design was to strive for lighter colors and to incorporate the ... [More] trademark Oriact green. It also features a new and improved prices table and better-structured information. In later updates, more restructuring and features will follow. - your Origo Team [Less]
Posted over 12 years ago by patrick
Hi, for quite some time now, Cruisecontrol had built-in support for Origo. If a build fails and issue is opened, if the build is recovered the issue is closed again. Now another continuous integration system, Hudson, does have this feature. To ... [More] install the Hudson Plugin for this, simply go to the plugin manager in your hudson installation and install the Origo Issue Notifier plugin. Thanks to the open API of Origo, it is quite simple to integrate external systems. [Less]
Posted over 12 years ago by bherlig
Dear Users, +Origo Dashboard +Details of a Work Item Last week we released a new Origo version 2010.2. The focus of this release was placed on Origo's work items, i.e. how work items generated, handled, stored and published. We've re-written ... [More] large parts of the back-end to facilitate this, and also ease future development of work-item related parts of Origo. While most of the changes only concern the back-end, we've wanted to make the new work item system visible in the front-end, too. To this effect we've introduced the Dashboard. We think that it is not quite ready yet, and may (does!) still contain some bugs. We therefore released it as a "beta" feature, and encourage you to try it out and tell us how you feel about it. +Issue Notification +Extended RSS Feeds With the new Work Item System, a lot of small things changed too. Minor annoyances are now fixed, e.g. notification emails of issues now display the issue ID in the subject line. Also a longstanding issue has now been fixed: Origo now shows the full detail of work items in RSS feeds. Here's a summary showing the most important changes in the new release: Rewritten Work Item System A new Dashboard for Work Items Extended RSS Feeds API changes Along with the rewrite of the work item system, it was necessary to change some of the API calls handling them. Consult the changelog for details. Spam module for automated filtering of possible spam comments. As always, the more technical details of this update and its list of bug-fixes can be viewed in Origo's changelog. Regards, The Origo Team [Less]
Posted over 12 years ago by patrick
It is quite common, that you want to link commits to issues. This is now possible using the standard bugtraq properties. Simply set the bugtraq svn properties svn propset bugtraq:url http://MYPROJECT.origo.ethz.ch/issue/%BUGID% ... [More] https://svn.origo.ethz.ch/MYPROJECT svn propset bugtraq:logregexp #(\d+) https://svn.origo.ethz.ch/MYPROJECT The first property sets the url of your issue tracker, the second sets the regular expression that will be converted to links. In this code for example, everything that looks like #1234 will be converted to a link. This properties are supported in the web based interface and also many other svn tools. See http://tortoisesvn.tigris.org/svn/tortoisesvn/trunk/doc/issuetrackers.txt external (login with guest and no password) for details. [Less]
Posted over 12 years ago by patrick
We finished migrating to a new, larger and more powerful machine, sponsored by Oriact[0]. Subversion, website, chat and all other services are available again But due to a DNS problem at our hosting site, release downloads over ipv4 are not working. ... [More] We hope to resolve this issue next week. Edit: DNS problem fixed, everything should be working again Regards, Your Origo Team [0]: http://www.oriact.com [Less]