<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>On 7/12/2017 3:44 PM, Kendall Nelson wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAJ6yrQjL2wP-epcU=PJaU_c8+YF6QqfRWFdvfHJqd4KS6bugCA@mail.gmail.com">
<div dir="ltr">
<div>
<div>@Jay: I would definitely urge projects to update the
places they have any info about bug tracking since different
projects use tags differently. I suppose we could add to the
SB documentation what the common practices are, but I
imagine there will be a lot of project specific details
about how the project sets up their boards and worklists,
what tags they use, how things are formatted etc that would
be better kept elsewhere. <br>
<br>
</div>
</div>
</div>
</blockquote>
Agreed, this is an opportunity to for Cinder to document how we use
StoryBoard as we migrate to it and anything that is specific to our
usage is something we document. :-) I am asking if there is a high
level common documentation location. I found development
documentation and links in your Wiki. Looking for the, 'here is
what everyone needs to know to start using StoryBoard' documentation
so I can get that linked in our devref.<br>
<br>
Hope that makes sense.<br>
<br>
<blockquote type="cite"
cite="mid:CAJ6yrQjL2wP-epcU=PJaU_c8+YF6QqfRWFdvfHJqd4KS6bugCA@mail.gmail.com">
<div dir="ltr">
<div>@Sean: Agreed! Having it dealt with before we reach
critical mass in SB will save us later. As one of the people
helping people migrate to sb, I will include this decision in
the information I give projects that are migrating. I think we
have a FAQ somewhere we can add the decision to as well. <br>
<br>
</div>
-Kendall (diablo_rojo)<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Jul 12, 2017 at 1:34 PM Jay S Bryant <<a
href="mailto:jungleboyj@gmail.com" moz-do-not-send="true">jungleboyj@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Kendall,</p>
<p>It looks like our current bug tracking documentation is
quite minimal:
<a class="m_-5168733493313038293moz-txt-link-freetext"
href="https://docs.openstack.org/cinder/latest/devref/launchpad.html#bug-tracking"
target="_blank" moz-do-not-send="true">https://docs.openstack.org/cinder/latest/devref/launchpad.html#bug-tracking</a></p>
<p>Is there going to be a place where SB is going to be
documented with some of these details that we can link to
under our bug-tracking section?</p>
<p>Thanks!</p>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<p>Jay</p>
</div>
<div text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="m_-5168733493313038293moz-cite-prefix">On
7/12/2017 3:19 PM, Kendall Nelson wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>
<div>Hey Sean :) <br>
<br>
</div>
So we discussed the issue of tag collisions in the
SB meeting we had today. Basically, we came to the
conclusion that projects should append their project
to the start of the tag, thereby avoiding collision
i.e. ironic-compute, nova-compute, manila-storage,
swift-storage, cinder-storage. If we can ask bug
triagers in their respective projects to follow and
uphold the convention, we should be fine. It might
also be helpful to add this to any directions
projects might have about filing bugs so new
contributors start off on the right foot. <br>
<br>
</div>
Thanks for bringing this concern up before it becomes
a problem! If anyone has other questions or concerns,
please attend our meetings or drop into our channel
(#storyboard)!<br>
<br>
</div>
-Kendall Nelson(diablo_rojo)<br>
<br>
[1] <a
href="https://wiki.openstack.org/wiki/Meetings/StoryBoard"
target="_blank" moz-do-not-send="true">https://wiki.openstack.org/wiki/Meetings/StoryBoard</a>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Wed, Jul 12, 2017 at 5:47 AM Sean
Dague <<a href="mailto:sean@dague.net"
target="_blank" moz-do-not-send="true">sean@dague.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
07/11/2017 04:31 PM, Jeremy Stanley wrote:<br>
> On 2017-07-10 07:33:28 -0400 (-0400), Sean Dague
wrote:<br>
> [...]<br>
>> Ideally storyboard would just be a lot more
receptive to these kinds of<br>
>> things, by emitting a more native event
stream,<br>
><br>
> Well, there is<br>
> <URL: <a
href="http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/notifications/publisher.py"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://git.openstack.org/cgit/openstack-infra/storyboard/tree/storyboard/notifications/publisher.py</a>
><br>
> so replacing or partnering its RabbitMQ publisher
with something<br>
> like an MQTT publisher into <a
href="http://firehose.openstack.org"
rel="noreferrer" target="_blank"
moz-do-not-send="true">firehose.openstack.org</a> is
probably not<br>
> terribly hard for someone with interest in that
and would be<br>
> generally useful.<br>
><br>
>> and having really good tag support
(preferably actually project<br>
>> scoped tags, so setting it on the nova task
doesn't impact the<br>
>> neutron tasks on the same story, as an for
instance)<br>
> [...]<br>
><br>
> Your queries (including those used to build
automatic tasklists and<br>
> boards) could just include project in addition to
tag, right? Or is<br>
> this more of a UI concern, being able to click on
an arbitrary tag<br>
> in the webclient and only get back a set of
tagged stories for the<br>
> same project rather than across all projects?<br>
<br>
My concern is based on current limitations in
launchpad, and to make<br>
sure they don't get encoded into Storyboard.<br>
<br>
Tags in launchpad are at the Bug level. Bugs map to
projects as Tasks.<br>
Which is why you can have 1 Bug set to be impacting
both Nova and<br>
Neutron. You get lots of weirdness today when for
instance a bug is<br>
assigned to Nova and Ironic, and the Nova team tags it
"ironic" in<br>
triage, but that means that now Ironic has a bug with
the "ironic" tag.<br>
Then if later Nova is removed from the bug, it ends up
really all<br>
looking odd and confusing.<br>
<br>
Or the fact that "compute" as a Nova tag means the
compute worker, but<br>
other teams tag things with compute to just mean Nova
is involved.<br>
Project scoped tags would help clarify what context it
is in.<br>
<br>
-Sean<br>
<br>
><br>
><br>
><br>
>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage
questions)<br>
> Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
<br>
--<br>
Sean Dague<br>
<a href="http://dague.net" rel="noreferrer"
target="_blank" moz-do-not-send="true">http://dague.net</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage
questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank"
moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
<fieldset
class="m_-5168733493313038293mimeAttachmentHeader"></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="m_-5168733493313038293moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank" moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="m_-5168733493313038293moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
rel="noreferrer" target="_blank" moz-do-not-send="true">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a
href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>