OpenBMC Fix-It Planning

[Nancy Yuen]

I've created this spreadsheet
<https://drive.google.com/open?id=1S8h68UPVTh3Fc79P6Az-95JEFiGesTce3M--y0IDLaA>
for everyone to share ideas for next week's Fix-It, Tues 6/12.  Please
remember this is a virtual Fix-It, so please plan to work on Fix-It items
for most of your work day and and communicate via IRC to ask questions and
discussions.

This is just a list of possible tasks people can sign up to do on Fix-It
day.  Suggesting something doesn't mean you have to be the one fixing it!

Please suggest ideas that are in the spirit of fix-it.  Small tasks that
can be tackled in less than a day by one or two engineers.  Tasks that are
not regular ongoing development.  Tasks don't have to be code related;
documentation, website changes, improving things in gerrit or other setting
up other infrastructure are good things to tackle in a Fix-It.

Some examples:

   - specific tests cases for a feature
   - specific documents that would be useful
   - code that needs to be cleaned up (adding comments, refactoring,
   splitting into multiple source files or header files)
   - smallish bugs that never make it to the top of priority list


----------
Nancy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20180605/b2879aef/attachment.html>