Diff for "Registry/UpstreamLinkUbuntu"

Not logged in - Log In / Register

Differences between revisions 2 and 3
Revision 2 as of 2010-01-28 19:51:18
Size: 2709
Editor: sinzui
Comment:
Revision 3 as of 2010-01-28 19:57:07
Size: 2670
Editor: sinzui
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
  * Launchpad could provide information about what each package needs to send upstream to make the need specific and clear.
  * Since crowd sourcing is the preferred solution to collect this information, karma can be awarded and top contributors can be displayed.
  * 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 privide community/service information.
Line 12: Line 12:
     * It could search for matching projects for the contributor and ask him or her to select from a list.      * It could search for matching Ubuntu packages for the upstream contributor and ask him or her to select from a list.
Line 14: Line 14:
     * It could make project registration easier by pre-populating the form with the source package information.

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 privide community/service information.
  • 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)

alt packages in Ubuntu portlet (no packages)

The distroseries index page needs a portlet that encourages users to link source packages to registered upstream projects.

This proposed design is very similar to the portlet Curtis and Martin discussed in August 2009 when redesigning the project and distro series pages. The project series index page lists where to get the code as the second most important portlet so that user can start working on bugs and features. The same activity is hard to do in a distro series because most of the work must be forwarded upstream, or upstream needs their latest code sent upstream to Ubuntu. A different kind of portlet is needed by the distro series.

  • The portlet summarises the work that must be done.
  • The portlet must list a subset of the packages that need linking. The list is prioritised so that the users see the most urgent packages first.
  • The portlet could show recently linked packages
    • Showing recent activity encourages contributors to be a part of the group.
    • Showing who and when it was done give contributors exposure
  • The portlet has links to both the linked packages and unlinked packages views.

The recently linked listing breaks portlet conventions by showing the who and when on the same line as the what. This information is collected but has never been shown in the Launchpad UI.

Comments

  • Curtis: The query to create the prioritised list of packages that need linking is hard.

Product +index page with packages (updated)

alt packages in Ubuntu portlet (packages)

Registry/UpstreamLinkUbuntu (last edited 2010-02-23 01:32:48 by edwin-grubbs)