Re: Hyperledger JIRA boards: how do we use them and why there are so many of them?


Nikolay Yushkevich
 

Cris,

I think that we might need to review your approach of using dashboards over boards, this can be helpful for our project as well.  We've always dreamt of having regular meetings where we can discuss processes and tools that support them. If we can talk about how other projects use JIRA for e.g. Fabric or Sawtooth community work or tasks for maintainers this will help us improve processes together.

If we combine that with a clean-up call that'll be more effective as we possibly are going to cross-question needs for some boards, tags and as a result we will have tidier JIRA.

Haven’t you started to use https://wiki2.hyperledger.org? This is a new confluence instance, we already have access there. 

Nikolai


6 дек. 2018 г., в 17:40, Christopher Ferris <chris.ferris@...> написал(а):

Nicolai,

Don't disagree, but frankly, using just the list of boards without context is useless, even if there were fewer.
I deleted mine, most had been created in a different time when I was experimenting how best to leverage for Fabric. Now we create dashboards instead, because most Fabric teams (anyway) are not using scrum or kanban boards. It really doesn't fit the open source model.

That said, I wouldn't object to a clean-up of JIRA, generally. We might want to discuss how we go about that. e.g. do we issue a call for self-cleanup, then issue warning (we're going to delete X unless you object in a week's time) and then have someone with administrative privileges delete, etc.

I'm also keen on us getting access to Confluence, because putting content around dashboards and epics will help immensely, and we can then leverage a wiki page as the front door for new developers etc.

Chris

On Thu, Dec 6, 2018 at 7:24 AM Nikolay Yushkevich <nikolai@...> wrote:
Hello!

Recently HL Iroha maintainers have started to use HL JIRA instance for project tracking and issue/bug reporting. Almost immediately we realized that there are too many boards, and possibly it is hard for an occasional contributor to check how things are going with a project’s release or where to find a good first issue.

There are some boards with restricted visibility, and they are empty as well. There are boards with stale issues, which are pending for 100, 200, 300 days. There are boards that are spelled in ALL CAPS; that have «copy of» in their name — and this looks very messy for a curious contributor.

Our concern is that we can’t find the board of our project easily if we open a list of all boards.

Let’s agree on some policy that is meaningful for all projects, supports their delivery process and would be transparent for contributors: where to find good first issues? Where to check if the bug is fixed? And similar things.

I think that you have something to add to this discussion and I would be happy to hear your thoughts on that.

Nikolai



Join tsc@lists.hyperledger.org to automatically receive all group messages.