← Back to team overview

launchpad-dev team mailing list archive

Re: [RFC-UI] indicate which Launchpad services are not linked to upstream projects


On Thu, Mar 11, 2010 at 4:48 PM, Edwin Grubbs
<edwin.grubbs@xxxxxxxxxxxxx> wrote:
> On Wed, Mar 10, 2010 at 8:13 AM, Jonathan Lange <jml@xxxxxxxxxxxxx> wrote:
>> On Thu, Mar 4, 2010 at 2:32 PM, Curtis Hovey <curtis.hovey@xxxxxxxxxxxxx> wrote:
>>> On Thu, 2010-03-04 at 07:52 -0600, Edwin Grubbs wrote:
>>>> On Thu, Mar 4, 2010 at 1:20 AM, Martin Pool <mbp@xxxxxxxxxxxxx> wrote:
>>>> > On 4 March 2010 16:32, Edwin Grubbs <edwin.grubbs@xxxxxxxxxxxxx> wrote:
>>>> >> I would appreciate any feedback on this proposal for displaying users
>>>> >> which services are unconfigured. This is very closely related to the
>>>> >> proposal that Curtis emailed with the subject "RFC Changing
>>>> >> permissions to allow contributors to set upstream information", but
>>>> >> this document is only concerned with the project index page.
>>>> >>
>> Thanks for this Edwin. Sorry I've taken so long to get to replying.
>> A couple of quick thoughts:
>>  * we should just drop "Register a blueprint" from the "Get involved" box
>>  * what would clicking on the "Bugs" tab show for a project that has
>> "Report a bug" crossed out on the "Get involved" box? similarly for
>> Translations etc.
> Why would we remove the "Register a blueprint" link from the "Get
> involved" portlet?

It's orthogonal to this discussion, but...
  - hardly anyone uses blueprints (see
  - I want to see if anyone complains if we remove the link
  - Why do we want to have it there?

> Right now, the tabs show some info on activating
> usage of the service, if the user has permission to do that.

As in, this is the current behaviour of Launchpad? I guess I should
actually test this.

> The one
> exception is the Branch tab, on which you can register a branch
> without any prior configuration to activate the service. Therefore,
> graying out the "Submit a branch" link in the "Get involved" portlet
> just serves the purpose of advising the user whether the upstream code
> base is readily available.

That makes sense.

>> Can I encourage you to turn this into a LEP and add it to
>> https://dev.launchpad.net/LEP (I've recovered from my blueprints
>> insanity)?
> I have converted the page into a LEP. The scope has been narrowed and
> new mockups have been added, so it is worth rereading.
> https://dev.launchpad.net/Registry/InvolvementPortletRefactor

Thanks! I'll take a look.


Follow ups