Hello, everyone. I work with Travis at Continuum, and he asked me to setup a YouTrack server that everyone is welcome to play around with. There is a test project currently set up, with some fake tickets. Here is the address: http://ec2-107-21-65-210.compute-1.amazonaws.com:8011/issues It's running on an AWS micro instance, so it might be slow at the moment. Any feedback or comments would be welcome. Maggie
On Fri, Mar 30, 2012 at 4:08 PM, Maggie Mari <maggie.mari@continuum.io>wrote:
Hello, everyone.
I work with Travis at Continuum, and he asked me to setup a YouTrack server that everyone is welcome to play around with. There is a test project currently set up, with some fake tickets.
Here is the address:
http://ec2-107-21-65-210.compute-1.amazonaws.com:8011/issues
It's running on an AWS micro instance, so it might be slow at the moment.
Any feedback or comments would be welcome.
Looks nice, although it will take a little getting used to. It's hard to tell with these things until you have actually made some use of them. Is it configurable? I was wondering what sort of feedback you were looking for. Who will have access to these issues? Is this going to be hosted at Continuum? Chuck
The idea is to allow people to test-out YouTrack for a few weeks and get to know it while we migrate bugs to it. it looks like it is straightforward to export the data out of YouTrack should we eventually decide to use something else. The idea is to host it on an external server (Rackspace or AWS that multiple people are able to admin). So far, I like the keyboard interface and the searchable widget on top. We will continue to work on moving tickets into the system. Please give it a try if you have an interest in the Issue Tracker. Best, -Travis On Mar 30, 2012, at 7:33 PM, Charles R Harris wrote:
On Fri, Mar 30, 2012 at 4:08 PM, Maggie Mari <maggie.mari@continuum.io> wrote: Hello, everyone.
I work with Travis at Continuum, and he asked me to setup a YouTrack server that everyone is welcome to play around with. There is a test project currently set up, with some fake tickets.
Here is the address:
http://ec2-107-21-65-210.compute-1.amazonaws.com:8011/issues
It's running on an AWS micro instance, so it might be slow at the moment.
Any feedback or comments would be welcome.
Looks nice, although it will take a little getting used to. It's hard to tell with these things until you have actually made some use of them. Is it configurable? I was wondering what sort of feedback you were looking for. Who will have access to these issues? Is this going to be hosted at Continuum?
Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Sat, Mar 31, 2012 at 9:45 PM, Travis Oliphant <travis@continuum.io>wrote:
The idea is to allow people to test-out YouTrack for a few weeks and get to know it while we migrate bugs to it. it looks like it is straightforward to export the data out of YouTrack should we eventually decide to use something else.
The interface looks good, but to get a feeling for how this would really work out I think admin rights are necessary. Then we can try out the command window (mass editing of issues), the rest API, etc. Could you send those out off-list?
The idea is to host it on an external server (Rackspace or AWS that multiple people are able to admin). So far, I like the keyboard interface and the searchable widget on top. We will continue to work on moving tickets into the system.
I assume you're doing that based on http://confluence.jetbrains.net/display/YTD3/Python+Client+Library? We discussed before keeping the conversion code somewhere public, is that possible already? Then we can also see the Trac --> YouTrack mapping. For example, it was unclear to me if "fix versions" equal Trac Milestones or not. Ralf On Mar 30, 2012, at 7:33 PM, Charles R Harris wrote: On Fri, Mar 30, 2012 at 4:08 PM, Maggie Mari <maggie.mari@continuum.io>wrote:
Hello, everyone.
I work with Travis at Continuum, and he asked me to setup a YouTrack server that everyone is welcome to play around with. There is a test project currently set up, with some fake tickets.
Here is the address:
http://ec2-107-21-65-210.compute-1.amazonaws.com:8011/issues
It's running on an AWS micro instance, so it might be slow at the moment.
Any feedback or comments would be welcome.
Looks nice, although it will take a little getting used to. It's hard to tell with these things until you have actually made some use of them. Is it configurable? I was wondering what sort of feedback you were looking for. Who will have access to these issues? Is this going to be hosted at Continuum? Chuck _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 4/1/12 6:02 AM, Ralf Gommers wrote:
The interface looks good, but to get a feeling for how this would really work out I think admin rights are necessary. Then we can try out the command window (mass editing of issues), the rest API, etc. Could you send those out off-list?
Hi Ralf, I have added you to the admin group. Let me know if you have any trouble. Who else should be added? Thanks, Maggie
On Tue, Apr 3, 2012 at 4:32 PM, Maggie Mari <maggie.mari@continuum.io>wrote:
On 4/1/12 6:02 AM, Ralf Gommers wrote:
The interface looks good, but to get a feeling for how this would really work out I think admin rights are necessary. Then we can try out the command window (mass editing of issues), the rest API, etc. Could you send those out off-list?
Hi Ralf,
I have added you to the admin group. Let me know if you have any trouble. Who else should be added?
Thanks Maggie. Here some first impressions. The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report ). Overall, I have to say that I'm not convinced yet. Ralf
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report). Ralf, I don't know about most of these issues offhand, but it does seem
On 4/3/12 4:18 PM, Ralf Gommers wrote: like youtrack offers github integration, in the form of being able to issue commands to youtrack through git commits (is that the kind of integration you are looking for?) http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/ Bryan
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues: I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each. Also we can certainly create some standard queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :) Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell: http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/ I'm not sure this is what you were thinking about though. For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week. Of course, we'd like to evaluate any other viable issue trackers as well. Do you have any suggestions for other systems besides YouTrack? Bryan
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here. Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two: - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic. Cheers, Ralf
On Tue, Apr 10, 2012 at 8:40 PM, Ralf Gommers <ralf.gommers@googlemail.com>wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two:
- I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as
well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow
Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic.
Redmine is "trac on RoR", but it solves two significant issues over trac: - mass edit (e.g. moving things to a new mileston is simple and doable from the UI) - REST API by default, so that we can build simple command line tools on top of it (this changed since I made the wiki page) It is a PITA to install, though, at least if you are not familiar with ruby, and I heard it is hard to manage as well. IIRC, roundup was suggested by Robert, but it is more of a custom solution I believe. David
On Tue, Apr 10, 2012 at 9:53 PM, David Cournapeau <cournape@gmail.com>wrote:
On Tue, Apr 10, 2012 at 8:40 PM, Ralf Gommers <ralf.gommers@googlemail.com
wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two:
- I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as
well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow
Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic.
Redmine is "trac on RoR", but it solves two significant issues over trac: - mass edit (e.g. moving things to a new mileston is simple and doable from the UI) - REST API by default, so that we can build simple command line tools on top of it (this changed since I made the wiki page)
It is a PITA to install, though, at least if you are not familiar with ruby, and I heard it is hard to manage as well.
Thanks, that's a clear description of pros and cons. It's also easy to play with Redmine at demo.redmine.org. That site allows you to set up a new project and try the admin interface. My current list of preferences is: 1. Redmine (if admin overhead is not unreasonable) 2. Trac with performance issues solved 3. Github 4. YouTrack 5. Trac with current performance Ralf
On Thu, Apr 12, 2012 at 5:43 PM, Ralf Gommers <ralf.gommers@googlemail.com>wrote:
On Tue, Apr 10, 2012 at 9:53 PM, David Cournapeau <cournape@gmail.com>wrote:
On Tue, Apr 10, 2012 at 8:40 PM, Ralf Gommers < ralf.gommers@googlemail.com> wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two:
- I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as
well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow
Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic.
Redmine is "trac on RoR", but it solves two significant issues over trac: - mass edit (e.g. moving things to a new mileston is simple and doable from the UI) - REST API by default, so that we can build simple command line tools on top of it (this changed since I made the wiki page)
It is a PITA to install, though, at least if you are not familiar with ruby, and I heard it is hard to manage as well.
Thanks, that's a clear description of pros and cons. It's also easy to play with Redmine at demo.redmine.org. That site allows you to set up a new project and try the admin interface.
And I just discovered this (and in python !) https://github.com/coiled-coil/git-redmine David
This looks good. Maggie and Bryan are now setting up a Redmine instance to try out how hard that is to administer. I have some experience with Redmine and have liked what I've seen in the past. I think the user experience that Ralf is providing feedback on is much more important than how hard it is to administer. NumFocus will dedicate resources to administer the system. -Travis On Apr 12, 2012, at 11:43 AM, Ralf Gommers wrote:
On Tue, Apr 10, 2012 at 9:53 PM, David Cournapeau <cournape@gmail.com> wrote:
On Tue, Apr 10, 2012 at 8:40 PM, Ralf Gommers <ralf.gommers@googlemail.com> wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io> wrote: On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two:
- I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as
well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow
Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic.
Redmine is "trac on RoR", but it solves two significant issues over trac: - mass edit (e.g. moving things to a new mileston is simple and doable from the UI) - REST API by default, so that we can build simple command line tools on top of it (this changed since I made the wiki page)
It is a PITA to install, though, at least if you are not familiar with ruby, and I heard it is hard to manage as well.
Thanks, that's a clear description of pros and cons. It's also easy to play with Redmine at demo.redmine.org. That site allows you to set up a new project and try the admin interface.
My current list of preferences is:
1. Redmine (if admin overhead is not unreasonable) 2. Trac with performance issues solved 3. Github 4. YouTrack 5. Trac with current performance
Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Has anyone tried Rietveld, Gerrit, or Phabricator? On Thu, Apr 12, 2012 at 4:05 PM, Travis Oliphant <travis@continuum.io>wrote:
This looks good. Maggie and Bryan are now setting up a Redmine instance to try out how hard that is to administer. I have some experience with Redmine and have liked what I've seen in the past. I think the user experience that Ralf is providing feedback on is much more important than how hard it is to administer.
NumFocus will dedicate resources to administer the system.
-Travis
On Apr 12, 2012, at 11:43 AM, Ralf Gommers wrote:
On Tue, Apr 10, 2012 at 9:53 PM, David Cournapeau <cournape@gmail.com>wrote:
On Tue, Apr 10, 2012 at 8:40 PM, Ralf Gommers < ralf.gommers@googlemail.com> wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two:
- I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Of course, we'd like to evaluate any other viable issue trackers as
well. Do you have any suggestions for other systems besides YouTrack?
David wrote up some issues (some of which I didn't check) with current Trac and looked at Redmine before. He also mentioned Roundup. See http://projects.scipy.org/numpy/wiki/ImprovingIssueWorkflow
Redmine does look good from a quick browse (better view, does display diffs). It would be good to get the opinions of a few more people on this topic.
Redmine is "trac on RoR", but it solves two significant issues over trac: - mass edit (e.g. moving things to a new mileston is simple and doable from the UI) - REST API by default, so that we can build simple command line tools on top of it (this changed since I made the wiki page)
It is a PITA to install, though, at least if you are not familiar with ruby, and I heard it is hard to manage as well.
Thanks, that's a clear description of pros and cons. It's also easy to play with Redmine at demo.redmine.org. That site allows you to set up a new project and try the admin interface.
My current list of preferences is:
1. Redmine (if admin overhead is not unreasonable) 2. Trac with performance issues solved 3. Github 4. YouTrack 5. Trac with current performance
Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
On Thu, Apr 12, 2012 at 9:29 PM, william ratcliff < william.ratcliff@gmail.com> wrote:
Has anyone tried Rietveld, Gerrit, or Phabricator?
rietveld and gerrit are code review tools. I have not heard of phabricator, but this article certainly makes it sounds interesting: http://www.readwriteweb.com/hack/2011/09/a-look-at-phabricator-facebook.php There is a quite complete command line interface, arcanist, and if done right, having code review and bug tracking integrated together sounds exciting. Thanks for mentioning it, I will definitely look it out. regards, David
On 4/12/12 11:43 AM, Ralf Gommers wrote:
Thanks, that's a clear description of pros and cons. It's also easy to play with Redmine at demo.redmine.org <http://demo.redmine.org>. That site allows you to set up a new project and try the admin interface.
My current list of preferences is:
1. Redmine (if admin overhead is not unreasonable) 2. Trac with performance issues solved 3. Github 4. YouTrack 5. Trac with current performance
Ralf
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
Hi Ralf, I have a redmine server up now at http://ec2-107-21-65-210.compute-1.amazonaws.com/redmine/projects/numpy with mostly default settings. If you would like to play around with it, I will give you admin status after you sign up. Maggie
12.04.2012 18:43, Ralf Gommers kirjoitti: [clip]
My current list of preferences is:
1. Redmine (if admin overhead is not unreasonable) 2. Trac with performance issues solved 3. Github 4. YouTrack 5. Trac with current performance
Redmine seems pretty nice, apparently has all the features Trac has, and more. It's actually *easier* to administer than Trac, because you apparently can do most configuration via the web interface. With Trac, you have to drop down to command line and use trac-admin. Just don't deploy it on CGI like the Tracs we currently have :) Pauli
On 4/10/12 2:40 PM, Ralf Gommers wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io <mailto:bryanv@continuum.io>> wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote: > Here some first impressions. > > The good: > - It's responsive! > - It remembers my preferences (view type, # of issues per page, etc.) > - Editing multiple issues with the command window is easy. > - Search and filter functionality is powerful > > The bad: > - Multiple projects are supported, but issues are then really mixed. > The way this works doesn't look very useful for combined admin of > numpy/scipy trackers. > - I haven't found a way yet to make versions and subsystems appear in > the one-line issue overview. > - Fixed issues are still shown by default. There are several open > issues filed against youtrack about this, with no reasonable answers. > - Plain text attachments (.txt, .diff, .patch) can't be viewed, only > downloaded. > - No direct VCS integration, only via Teamcity (not set up, so can't > evaluate). > - No useful default views as in Trac > (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two: - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Ralf, I don't believe there is a solution for the first issue. There are tickets on YouTrack filed specifically asking for this feature, but it does not seem clear they want to implement it. For the second, I created a saved search called "open" that I think should show up for all users (let me know if it does not). The nice thing is, this save search can be referenced in other searches, so you can do: saved search: open Subsystem: test3 sort by: updated and get all the open tickets for that subsystem. I think basically it's just a different type of workflow, fixed tickets show up "by default" because everything shows up by default, there is no search criteria to exclude them. But it seems easy enough to combine searches to get what you want. Another trac feature that I did realize is missing is a "group by" functionality. So you can sort by subsytem, but there is no notion of nicely grouping by them as in trac. There's a feature request for this, too, but who knows if or when it will get put in. Travis mentioned he had created a code.google.com site for numpy a long time ago that never got used. I think Maggie is going to create a few dozen test tickets on its issue tracker today and then we can also have that to evaluate as well. Bryan
On Thu, Apr 12, 2012 at 5:37 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/10/12 2:40 PM, Ralf Gommers wrote:
On Mon, Apr 9, 2012 at 10:32 PM, Bryan Van de Ven <bryanv@continuum.io>wrote:
On 4/3/12 4:18 PM, Ralf Gommers wrote:
Here some first impressions.
The good: - It's responsive! - It remembers my preferences (view type, # of issues per page, etc.) - Editing multiple issues with the command window is easy. - Search and filter functionality is powerful
The bad: - Multiple projects are supported, but issues are then really mixed. The way this works doesn't look very useful for combined admin of numpy/scipy trackers. - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers. - Plain text attachments (.txt, .diff, .patch) can't be viewed, only downloaded. - No direct VCS integration, only via Teamcity (not set up, so can't evaluate). - No useful default views as in Trac (http://projects.scipy.org/scipy/report).
Ralf, regarding some of the issues:
Hi Bryan, thanks for looking into this.
I think for numpy/scipy trackers, we could simply run separate instances of YouTrack for each.
That would work. It does mean that there's no maintenance advantage over using Trac here.
Also we can certainly create some standard
queries. It's a small pain not to have useful defaults, but it's only a one-time pain. :)
That should help.
Also, what kind of integration are you looking for with github? There does appear to be the ability to issue commands to youtrack through git commits, which does not depend on TeamCity, as best I can tell:
http://confluence.jetbrains.net/display/YTD3/GitHub+Integration http://blogs.jetbrains.com/youtrack/tag/github-integration/
I'm not sure this is what you were thinking about though.
That does help. The other thing that's useful is to reference commits (like commit:abcd123 in current Trac) and have them turned into links to commits on Github. This is not a showstopper for me though.
For the other issues, Maggie or I can try and see what we can find out about implementing them, or working around them, this week.
I'd say that from the issues I mentioned, the biggest one is the one-line view. So these two: - I haven't found a way yet to make versions and subsystems appear in the one-line issue overview. - Fixed issues are still shown by default. There are several open issues filed against youtrack about this, with no reasonable answers.
Ralf,
I don't believe there is a solution for the first issue. There are tickets on YouTrack filed specifically asking for this feature, but it does not seem clear they want to implement it.
For the second, I created a saved search called "open" that I think should show up for all users (let me know if it does not). The nice thing is, this save search can be referenced in other searches, so you can do:
saved search: open Subsystem: test3 sort by: updated
and get all the open tickets for that subsystem. I think basically it's just a different type of workflow, fixed tickets show up "by default" because everything shows up by default, there is no search criteria to exclude them. But it seems easy enough to combine searches to get what you want.
Well, not that easy. For example, if I want to go through all open tickets and get an overview of how many open tickets there are for each scipy module. In Trac I can just sort by "component" and see the (approximate) answer. In Youtrack I'd have to execute "saved search: open Subsystem:xxx" once for each module. Of course a tracker with a useful REST API where you could get the exact answer with a few lines of Python code would be even better.... Another trac feature that I did realize is missing is a "group by"
functionality. So you can sort by subsytem, but there is no notion of nicely grouping by them as in trac. There's a feature request for this, too, but who knows if or when it will get put in.
Agreed.
Travis mentioned he had created a code.google.com site for numpy a long time ago that never got used. I think Maggie is going to create a few dozen test tickets on its issue tracker today and then we can also have that to evaluate as well.
Is that necessary? I think there's a reason no one has suggested it so far - it has very few features. Plus it's blocked in China (and probably other countries too), which is enough of a problem in my opinion to immediately dismiss it. Ralf
Have you guys actually thought about JIRA? Atlassian offers free licences for open source projects ... Cheers, Andreas.
On Thu, Apr 12, 2012 at 5:59 PM, Andreas H. <lists@hilboll.de> wrote:
Have you guys actually thought about JIRA? Atlassian offers free licences for open source projects ...
Yes, http://article.gmane.org/gmane.comp.python.numeric.general/48224/match=jira Ralf
participants (9)
-
Andreas H. -
Bryan Van de Ven -
Charles R Harris -
David Cournapeau -
Maggie Mari -
Pauli Virtanen -
Ralf Gommers -
Travis Oliphant -
william ratcliff