2728
Comment: page was renamed from Registry/LinkUpstreamLinkUbuntu
|
2885
|
Deletions are marked like this. | Additions are marked like this. |
Line 11: | Line 11: |
* Since crowd sourcing is the preferred solution to collect this information, karma can be awarded to users who privide community/service information. | * Since crowd sourcing is the preferred solution to collect this information * karma can be awarded to users who privide community/service information. * Launchpad could allow contributors to add information that project owners have not provided. |
Line 14: | Line 16: |
* It could show exactly what information is missing | * It could show exactly what information is missing. |
Line 21: | Line 23: |
The distroseries index page needs a portlet that encourages users to link source packages to registered upstream projects. | The prodict index page has a portlet that shows distribution packaging, but nothing is shown on this page when there is no packaging. |
Line 23: | Line 25: |
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 project page could show a portlet that asks contributors to select the Ubuntu package from a list of probably candidates. * The portlet must states why the links are valuable. * The portlet must make is clear that the candidated are for the currect 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 must offer a link to select other packages if the candidates are wrong. |
Line 25: | Line 32: |
* 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. |
|
Line 32: | Line 33: |
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. | |
Line 36: | Line 36: |
* Curtis: The query to create the prioritised list of packages that need linking is hard. |
* 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? |
Upstream linking to Ubuntu
Launchpad must make it easier for upstream contributors to link their projects to Ubuntu source-packages.
Contents
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 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 prodict 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 probably candidates.
- The portlet must states why the links are valuable.
- The portlet must make is clear that the candidated are for the currect 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 must offer a link to select other packages 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)