• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Upstream linking to Ubuntu

Launchpad must make it easier for upstream contributors to link their projects to Ubuntu source-packages.

Launchpad has had packaging links for years, but the message regarding its value is not compelling.

• Launchpad could provide specific information that other communities need to know about what each upstream project, and make it clear when the information is missing.
• Since crowd sourcing is the preferred solution to collect this information
  • karma can be awarded to users who provide community/service information.
  • Launchpad could allow contributors to add information that project owners have not provided.
• Launchpad could do some of the monotonous work for the contributors:
  • It could search for matching Ubuntu packages for the upstream contributor and ask him or her to select from a list.
  • It could show exactly what information is missing.

Product +index page without packages (updated)

The product index page has a portlet that shows distribution packaging, but nothing is shown on this page when there is no packaging.

The project page could show a portlet that asks contributors to select the Ubuntu package from a list of probable candidates.

• The portlet must state why the links are valuable.
• The portlet must make it clear that the candidates are for the current Ubuntu development series.
  • Upstream projects are more interested in what their users use (the current or LTS release).
  • Upstream projects have often created false packages (that were never published in an Ubuntu series) to indicate that a package was made. The package was probably made in a PPA.
• The portlet could make it clear that the packaging link is the the upstream project's development series.
• The portlet must offer a link to select other packages and product series if the candidates are wrong.

Comments

• Curtis: There are some concerns about using this portlet:
  • This portlet could be very annoying to project that are not packaged in Ubuntu. I do not think this should be something that can be disabled by the project owner. Is there something intrinsic about some project that indicate this portlet should never be shown.
  • The portlet is shown at the bottom of the page? Can it be moved higher? It can be argued that it should be shown closers to the bugs and blueprints portlets because some project do make packages, but they are not linking them to Ubuntu.'
  • Can the portlet be moved closer to the series and milestone portlet because that shows releases?

Product +index page with packages (updated)

The product index page has a portlet that shows distribution packaging. It can be improved.

• The portlet can be renamed "Packages in Ubuntu" to clarify the intent.
• The portlet can show the most recent packages first.
  • The current portlet shows the oldest first
  • Older entries look wrong because the binary package release was removed, so there is less information to display.
  • Older entries are not as important to newer ones, users and developers will agree on this point.
• The portlet can provide a link to register more packages that the upstream project provides.
  • This packging links are normally

Comments

• Curtis: There are some concerns about using this portlet:
  • Who uses the portlet? It's primary existence appears to be a window to the +packages page.
    • Users do not use this because it does not provide them with an archive to add to their sources.
    • Power users could use it to navigate to a the deb, but that is 4 clicks away for knowedgeable Launchpad users.
    • Contributors can use this to get to the packages in recent Ubuntu series, but upstream care most about the current Ubuntu series, not the Ubuntu development series.
    • Contributors can use this to learn what the most recent version is in each Ubuntu series.
  • Why so many packages? 5 will ensure that the last LTS is always listed

Product +ubuntupkg page (new)

Launchapd currently shows the links to add an ubuntu package on the product series pages (and with the series listings on Product +packages) because the series is used to create the packaging link.

Launchpad can provide an alternate +ubuntupkg form for Products that lets the contributors select the product series. The current development series can be the default value.

Project community services (New)

The Uses launchpad for information is too simple. It acts as a flag, ignoring the fact that communities need to know who, what, and where to contact essential services.

New requirements: Registry/InvolvementPortletRefactor

Projects on launchpad are rarely hosted entirely by launchpad. Community need to know where the essential services are hosted, say it is hosted in Launchpad is not enough. New projects need to think about this and provide the information so that they can attract contributors; A project starts with code, then needs a bug tracker and translations for example. The page design must encourage users to provide this information. The design must also make it clear that even when a project uses hosted services, Launchpad can still be used.

The "Uses Launchpad for" section of Project Information must be replaced by something that presents the essential services: bug tracker, code hosting, translations, blueprints, and answers.

• The presentation can be simple when launchpad hosts the service.
• Some basic info is needed when the hosting is remote.
• When information is missing, the page must encourage users to provide it.

Launchpad can allow owners to change the the information from an inline edit link.

This information might be shown as a separate portlet next to the project information. The suggested design shows it as an intrinsic part of the project information. Regardless of the how we label this information, it pushes the Series and milestone portlet below. The good aspect of tis is that there is more space to show the timeline. The bad aspect is that only 30% of Launchpad users will see the timeline when it loads (70% of users can see the it now). This may not be an issue because users who want to hack on a project will want to see the new information before looking at the series.

Comments

• Curtis:
  • This information is hard to convey. Do we want to have a separate prestentation for hosted and remote services?
    • In the case of code, the branch is mirrores so Launchpad communities will still us Launchpad to work with the code.
    • In the case of the remote bug tracker, should users still report the bug in Launchpad?
    • Traslations is hard to represent as hosted and non-hosted. Does this presentation undermine the Launchpad community that uses Launchpad to translate the upstream project?
    • Blueprints is easy to show because Launchpad already collects the wiki info.
    • Answers is easy to show, but Launchpad does not collect the forum or mailing list used for questions. This may also undermine a Launchpad community that chooses to support the project using Answers.
    • blueprints, and answers can be argued to be unimportant, but I suspect we already have this information, or can add it in time. Project wikis are used for blueprints. forums and mailing list are used for answers.

Product and product series permissions (update)

Is knowledge power if you cannot act upon it?

Many projects are missing upstream information. The project owner is not interest in providing it, or is absent, or the project is owned by the Registry Administrators. Contributors cannot fix the information, so they struggle to contact someone with the power to make the fix.

• Launchpad can change the permision rules to permit contributors to set missing information on the product an series. The common fields that contributors need access to are: bug tracker, bug contact, series branch, series filereleaseglob, import/export translations.
• If the project is owned by Registry Administrators, any user can correct/update the current information.

Comments

• Curtis:
  • Maybe communities need permission to create alternate product series. The power is restricted to project drivers aimed are creating a release. Communities may need permission to create series for experimental features or packaging.