layerindex-web/TODO
Paul Eggleton 714bc8e39f update.py: error out with unexpected arguments
It's easy to forget you need to use -l to specify the list of layers to
update and previously we just ignored unused arguments, so check for
them and error out if present.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2013-05-08 22:01:25 +01:00

2.1 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
  • Update script does not report which layer failed with -q when fetch fails
  • Document macros for URL fields

Later:

  • Breadcrumbs / fix tab navigation?
  • Detailed change history page [Paul working on this]
  • 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
  • Update script still retries a fetch when repo has already failed
  • 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?