diff options
| -rw-r--r-- | MAINTAINERS | 20 | ||||
| -rw-r--r-- | README | 64 |
2 files changed, 5 insertions, 79 deletions
diff --git a/MAINTAINERS b/MAINTAINERS deleted file mode 100644 index 446f85c..0000000 --- a/MAINTAINERS +++ /dev/null @@ -1,20 +0,0 @@ -This file contains a list of maintainers for the meta-intel-iot-middleware -layer. - -Descriptions of section entries: - - M: Mail patches to: FullName <address@domain> - F: Files and directories with wildcard patterns. - A trailing slash includes all files and subdirectory files. - F: recipes-devtools/ all files in and below meta-ivi - F: recipes-selinux/* all files in meta-ivi, but not below - One pattern per line. Multiple F: lines acceptable. - -Please keep this list in alphabetical order. - -Maintainers List (try to look for most precise areas first) - -COMMON -M: Kevron Rees <kevron.m.rees@intel.com> -F: * - @@ -1,63 +1,9 @@ meta-intel-iot-middleware ========================= -This is the middleware layer for the Intel IoT developer kit. Here are -middleware parts useful for the iot-devkit but not shipped as part of meta-oe -or backports from newer versions of meta-oe which are not appropriate for -meta-oe itself. Software in here is likely to follow a more agressive upgrade -schedule. - -This layer depends on: - - URI: git://git.openembedded.org/meta-openembedded - branch: daisy - -Guidelines for submitting patches -================================= - -Please submit pull requests on the github mirror here: -https://github.com/tripzero/meta-intel-iot-middleware - -Alternatively patches can be submitted to the meta-intel mailing list -(meta-intel@yoctoproject.org) and cc the most appropriate maintainer in the -MAINTAINERS file. Prefix your email with [meta-intel-iot-middleware]. Also, if -your patches are available via a public git repository, please also include a -URL to the repo and branch containing your patches as that makes it easier for -maintainers to grab and test your patches. - -Regardless of how you submit a patch or patchset, the patches should -at minimum follow the suggestions outlined in the 'How to Submit a -Change' secion in the Yocto Project Development Manual. Specifically, -they should: - - - Include a 'Signed-off-by:' line. A commit can't legally be pulled - in without this. - - - Provide a single-line, short summary of the change. This short - description should be prefixed by the BSP or recipe name, as - appropriate, followed by a colon. Capitalize the first character - of the summary (following the colon). - - - For the body of the commit message, provide detailed information - that describes what you changed, why you made the change, and the - approach you used. - - - If the change addresses a specific bug or issue that is associated - with a bug-tracking ID, include a reference to that ID in your - detailed description in the following format: [YOCTO #<bug-id>]. - - - Pay attention to line length - please don't allow any particular - line in the commit message to stretch past 72 characters. - - - For any non-trivial patch, provide information about how you - tested the patch, and for any non-trivial or non-obvious testing - setup, provide details of that setup. - -Doing a quick 'git log' will provide you with many -examples of good example commits if you have questions about any -aspect of the preferred format. - -The maintainers will do their best to review and/or pull in a patch or patchset -within 48 hours of the time it was posted. For larger and/or more involved -patches and patchsets, the review process may take longer. +This layer is no longer maintained - the useful recipes that used to be +here have now been moved out to other layers (meta-oe, meta-python, +meta-networking etc.) If you wish to resurrect any of the remaining +recipes here please feel free to do so, but there are no current plans +to maintain this layer any further. |