layerindex-web/TODO
Paul Eggleton d1b875a76b Improve history collection and add link to history page
Save individual field changes into revision comment and display this
comment on the history page. Now we're ready to add a link at the
bottom of every page so the history is easily visible.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-06-03 10:59:10 +01:00

1.9 KiB

TODO:

  • Duplication of first maintainer when editing to add a second?
  • Try to re-use existing recipe record with same PN instead of deleting and re-creating (if within same layer)
  • meta-arago-extras is preferred over meta-networking e.g. for crda; probably need an explicit field for priority order
  • Document macros for URL fields

Later:

  • Breadcrumbs / fix tab navigation?
  • Ability for reviewers to comment before publishing a layer?
  • Add link to the all layers and all recipes tables from the layer details page?
  • Prevent SMTP failures from breaking submission process
  • All-branch search/results so you can see version availability of recipes in all branches at once?
  • Rawrecipes branch support
  • Display no-results found message when search does not return any results (all tables)
  • Change behaviour of filter menus to stay open so that you can check / uncheck multiple items
  • Show layer type in layer detail?
  • Usage links in list page?
  • Subdirs in list page?
  • Avoid page content changing size depending on whether scrollbar is there or not?
  • Return to last page (review/detail) after editing (with success alert)?
  • Cancel button on edit form?
  • Query backend service? i.e. special URL to query information for external apps/scripts
  • Tool for finding/comparing duplicate recipes?
  • Tool for editing SUMMARY/DESCRIPTION? [Paul working on this]
  • Dynamic loading/filtering for recipes list
  • Track BUGTRACKER
  • Track PROVIDES and BBCLASSEXTENDS?
  • Some way to notify the user when they search for something that has been renamed / replaced / deprecated?
  • Create simple script to check for unlisted layer subdirectories in all repos
  • Move import script to utils/ subdir
  • Are we going to need some way of indicating forks of another layer? (would rather avoid having forks altogether...)
  • Track bbappends in each layer
  • Auto-detect more values from github pages?
  • Ability for submitters to get email notification about publication?