Launchpad allows questions, code and blueprints even if the project states that it doesn't use them

Joey Stanford pisze:
> ** Changed in: ubuntu-website
> Product: Launchpad itself => Ubuntu Website

Are you sure? I've seen such thing on other projects too.
Ie. https://edge.launchpad.net/exaile/
The project overview page says that this project doesn't use Answers or
Blueprints while it is still possible to send questions and blueprints.
Maybe the description should be changed?
Because we have 2 cases here:
- a project doesn't use blueprints/answers/... and
blueprints/answers/... can't be filed (expected from description)
- a project doesn't use blueprints/answers/... but
blueprints/answers/... can still be filed (unexpected)
--
## Przemysław Kulczycki <<>> Azrael Nightwalker ##
# jabber: azrael[na]jabster.pl | tlen: azrael29a #
### www: http://reksio.ftj.agh.edu.pl/~azrael/ ###

Hi,

On Wed, Apr 9, 2008 at 11:40 AM, Przemysław Kulczycki
<email address hidden> wrote:

> Are you sure? I've seen such thing on other projects too.

Yes, it's an option that the project owner has to set and change. As
an owner of the project you can select which of those cases apply and
then LP's UI will display them properly. LP itself can't tell a
project owner what he/she should or should not use. This permits the
project owner to be flexible and use the components of LP that they
want to.

I think Przemysław has a point - if a project hasn't selected to use a particular component, it's odd that Launchpad allows users to submit stuff on those components.

I'll see if I can fix the ubuntu-website project, though.

I agree with that. I'll ask Diogo to fork a bug for that so we can fix it.

The fact that a project doesn't use some Launchpad components and allow those components to be filed under that category is clearly a bug. I think we might have that reported though. I'll look further tomorrow.
Bug 151251 is related.

Another consideration is that a project might use a component (e.g. translations) in a different place on Launchpad - e.g. the ubuntu-doc project uses translations on the ubuntu/$release/+source/ubuntu-docs location. It's possible to link project code to a distro source package, but in a lot of cases like that, there is no way to link the two.

It would be nice to be able to say "uses Launchpad for translations / bugs" and have the bug or translations tab pointing at the right place for those instances. That's probably worth a separate bug though, I guess.

Tested locally and confimed that both blueprints and answers allow specs/questions to be filed even when the project is set as not using them.
Haven't open tasks for Bugs and Translations because they both clearly states that the project doesn't use the component for bugs/translations.
Opened a task for launchpad-bazaar but I'm not confirming as I'm not sure what the setting is supposed to mean in the code hosting context.

Matthew: That's indeed a different bug. Please file a new bug for that.

I'm closing the Launchpad specific task because this will have to be fixed in the components.

Tim, can you explain what does it mean when a project sets "Doesn't use Code" in the project +edit details page?

Diogo, "Doesn't use Code" means that whatever branches may be stored on Launchpad are not officially recognized by the project and may not be up to date.

(We considered "Doesn't officially use code", but this is consistent with the other items.)

Thanks for the explanation Aaron. Do you think this should be explained somewhere in the UI to avoid the confusion outlined in this bug report?

I have the same issue for Answers on my https://launchpad.net/epidermis project. Anyone know how I can turn off the answers section of my site?

This bug has been confirmed for several months now, and I think that all necessary information has been submitted, so what's happening?

Same issue with me for Blueprints (not tried answers), this is on the 'tangocms' project.

So I'm marking this Won't Fix for Code since it's useful for any user to be able to upload bzr branches of the project code even if the trunk isn't in bzr on Launchpad.

Answers and Blueprints should act like Translations and Bugs when the project doesn't use Launchpad for these features, but it's a low priority issue for now.

Is it still not possible to disable a section / hide the tabs? It would be nice to be able to remove the translations tab, for example, since our project is not using it.

Barry.

This bug relates to this issue I was discussing. The tab must exist so that instructions are available to enable it. The page should not have robots noindex,nofollow in the meta. The officially uses launchpad <translations|answers|blueprints> should be on these pages too.

Don't the unused tabs only need to be active for users with appropriate privileges to activate them?

On Wed, 08 Jul 2009 10:41:29 William Grant wrote:
> Don't the unused tabs only need to be active for users with appropriate
> privileges to activate them?

I think there is another code related issue.

What if the project doesn't officially use Code, but someone requests an import
(from a git repo say), which creates a vcs-import branch.

Other users then could have their own bazaar branches.

The decision a long time ago was to make this a possibility.

I think what we'd need in that case though is a big warning at the top of the
code listing saying:
  "This project doesn't officially use Launchpad code hosting.
   Please see: <a>some anchor</a>"

But we shouldn't stop people from making stuff available there.

That applies to Code, where people can upload unofficial branches. It applies to Bugs, where people can add bug watches from reports of bugs in the project's various distribution packages. It may even apply to Answers. It doesn't apply to Blueprints, though, and it doesn't apply to Translations as long as Translations expects you to be the project maintainer.

I believe there are two different issues here. One is the UI and feature discoverability (i.e. figuring out when and how certain tabs need to be shown, and what they need to show themselves), and another is that we allow people to file blueprints and answers even if projects specifically say they are not using them.

While the latter is a useful feature (it's like independent forum), it's very confusing on everything but "imported" projects. That's why we've got maintainers complaining. If done properly, however, I am sure it'd be a great asset for discussing "external" project features, though we do know that all upstreams want that to happen in their own back yard. Well, most of it at least.

lxml could only be affected by this bug if lxml used launchpad as a library, and it does not.