Hi, (resending, as my first mail didn't make it to the list for some reason) On 04/23/2018 03:49 PM, Sage Weil wrote: > (Note that there is a third tool here--github--that probably isn't going > away.) FWIW, we used the openATTIC JIRA on https://tracker.openattic.org/ for keeping track of the development of the Dashboard development, particularly of reaching our first milestone (reaching feature parity with the old dashboard and getting merged into the Ceph code base). This was primarily based on the fact that the team behind this effort is mostly familiar with this tool. Atlassian was so kind to grant us a free license for open source projects and we host our own instance instead of using Atlassian's SAAS offering. But in order to make our work on the Dashboard more accessible for others, we're currently evaluating our options. Frankly, coming from JIRA we somehow dread the thought of having to move to Redmine, as it's UI leaves a lot to be desired in comparison. As you already set a precedent with the Trello board above, we are contemplating to follow suit and set up a Trello board for keeping track of the dashboard feature list. But that already moves it out of your radar screen, as it's a separate board. I'd actually love to have one tool that gives me a quick way to keep track of both feature development and bug tracking, especially when a new release is imminent. > I'm game for a better tool. The main friction with change here is around > the bug tracking in redmine, just because there are so many issues there > covering such a large time period, but if we're talking about > feature/radomap/release tracking (which are already handled outside of > redmine) then I don't see that as a problem. And for archival reasons, the Redmine instance should definitely be kept around - it carries a lot of background and history. But that should not mean that moving to a new platform is completely out of the question - but it's definitely a big switch that would have to be carefully planned. > I'm personally not super thrilled about jira because it's a closed > platform, even if they do offer free accounts for open source projects. > (Yes, github and trello are no better.) > > Right now the only trello board I really use is > > https://trello.com/b/ugTc2QFH/ceph-backlog > > and I only use it for a high-level view of feature work across the > project. The lists are per-topic or subsystem, which isn't (I think?) how > these things are normally shown (i.e., it's not kanban). The only other > thing it does it loosely track what is targetted at the next release via > colored labels. That's all pretty basic, and to be honest I don't know > that I need much more. One of the things we become very fond of in the openATTIC project is JIRA's flexibility, the ease of use (especially adding new issues and editing/updating existing ones), and the JIRA Query Language (JQL), which gives you a powerful tool for querying the existing database based on countless criteria. However, that requires that you actively work with the tool and make use of it's features (and that issues are properly kept up to date and groomed). But of course in the end it still is a proprietary tool and you're at the mercy of Atlassian when it comes to keeping it and your data. > On the other hand, it's not very useful for other contributors (especially > new ones) to come look at. That's partly because there is no detail > written for the cards, but that could easily be fixed by writing up some > notes for each item, linking to the relevant CDM discussions or etherpad > notes, and so on. Right, making the list of existing issues actually useful is pretty much tool-independent. It's a matter of being consistent and diligent about creating new issues and maintaining the backlog. But some tools make this harder than others - Trello cards and JIRA issues are fairly easy to update, the workflow in Redmine seems to be more involved here. There actually is an agile extension to Redmine (thanks for pointing this out to me), but it seems to be "open core" only: https://www.redmineup.com/pages/plugins/agile > So I guess my question are we looking for out of the tool(s), and what > is currently missing? See above - I'd be very much in favor of having one tool for both issue and feature tracking, with a nice UI/UX and good github integration. I wonder if taiga.io would suit the bill here? Lenz -- SUSE Linux GmbH - Maxfeldstr. 5 - 90409 Nuernberg (Germany) GF:Felix Imendörffer,Jane Smithard,Graham Norton,HRB 21284 (AG Nürnberg)
Attachment:
signature.asc
Description: OpenPGP digital signature
