"Also affects project" doesn't provide any instructions

Rebuntu being incorrectly added as the upstream should be due to bug #117494.

Thanks for your detailed report, Andy. This will need to be split up into several reports that can be fixed independently.

Oh, you mean you want *me* to split it up? Apologies for the delay, I thought a launchpad dev was going to do it because they know the launchpad development infrastructure and the logic behind splitting it up better than I do. How would you like it split?

Done. Sorry for the delay.

This has been changed in the UI such that "also affects upstream" no longer appears. On what page should there be instructions and what should they instruct? There is also no help tab either.

At the same time I'll add help for "...distribution" "target to release" "Also affects me".

Easy to fix, but what text should be used for the comment?

"""
Launchpad tracks the upstream bug and warns the subscribers to the bug when the status upstream has been changed.

Unfortunately no upstream relationship has been established for this product. Please indicate which project to link to link to this specific bug report.
"""

Above is pieced together from help text at https://wiki.ubuntu.com/Bugs/Watches and https://wiki.ubuntu.com/Bugs/HowToTriage.

Anyone mind helping copyediting?

I think the term "upstream" does not cover all situations where more than one bugtask makes sense. Other scenarios are a bug that affects a client and a server, or one that affects a library (maintained as a separate project) and an application that uses the library.

On Thu, Jun 03, 2010 at 08:37:39AM -0000, Abel Deuring wrote:
> I think the term "upstream" does not cover all situations where more
> than one bugtask makes sense. Other scenarios are a bug that affects a
> client and a server, or one that affects a library (maintained as a
> separate project) and an application that uses the library.

Ah, that's a good point. What would you suggest as a more complete
wording?

On 4 June 2010 02:34, Bryce Harrington <email address hidden> wrote:
> On Thu, Jun 03, 2010 at 08:37:39AM -0000, Abel Deuring wrote:
>> I think the term "upstream" does not cover all situations where more
>> than one bugtask makes sense. Other scenarios are a bug that affects a
>> client and a server, or one that affects a library (maintained as a
>> separate project) and an application that uses the library.
>
> Ah, that's a good point.  What would you suggest as a more complete
> wording?

I would say "Add task for project" or "Add project task" or something like that.

mpt expressed reluctance in another bug to exposing the internal term
"task" to users unnecessarily. However this is a concept people need
to know about for intermediate-advanced use of Launchpad: having them
just call it "a row in that table at the top of the bugs" isn't really
helping anyone.

To me the key concepts here are:

 * you're going to add a new dimension to the bug
 * it's about a project, rather than a distro package or series
 * to track some work that needs to be done there

"Affects" is a bad word because it's overloaded by "affects me too":
we see people getting confused by saying that a bug in gcc affects
mysql, which is literally true but doesn't mean it needs a task
against mysql.

--
Martin <http://launchpad.net/~mbp/>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03.06.2010 18:34, Bryce Harrington wrote:
> On Thu, Jun 03, 2010 at 08:37:39AM -0000, Abel Deuring wrote:
>> I think the term "upstream" does not cover all situations where more
>> than one bugtask makes sense. Other scenarios are a bug that affects a
>> client and a server, or one that affects a library (maintained as a
>> separate project) and an application that uses the library.
>
> Ah, that's a good point. What would you suggest as a more complete
> wording?
>

What about "A bug may need fixing in more than one project. You can add
here such a project. See also some-link-to-help.lp.net."

"Needs fixing in (distribution|project)" might also be an alternative
for the link texts that lead to the forms to avoid the confusion
mentioned by Martin.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFMCKzmekBPhm8NrtARAkSKAKCKbzxg8fLnEBlaT9Zt3fL97JresgCdEiL7
T0SUyQwdNTgTj51KnGEpve8=
=DOOe
-----END PGP SIGNATURE-----

Updated with feedback, thanks.

The link that leads to this page afaict is the 'Also affects project' link. I hesitate to change it since it is right next to 'Also affects distribution' so the current text is at least consistent. I think if changes are needed to those links, that should be handled as a separate bug report from this one.

Fixed in stable r11844 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/11844>.