[Mesa-dev] [PATCH mesa] add project README

[Dylan Baker]

Quoting Jason Ekstrand (2018-06-08 10:04:50)
> On Fri, Jun 8, 2018 at 9:27 AM, Eric Engestrom <eric.engestrom at intel.com>
> wrote:
> 
>     On Friday, 2018-06-08 09:06:06 -0700, Jason Ekstrand wrote:
>     > On Fri, Jun 8, 2018 at 8:57 AM, Eric Engestrom <eric.engestrom at intel.com>
>     > wrote:
>     >
>     > > Now that we're using GitLab, let's take advantage of the "landing page"
>     > > README feature with some minimal information, mostly to point people to
>     > > the right resources.
>     > >
>     > > Signed-off-by: Eric Engestrom <eric.engestrom at intel.com>
>     > > ---
>     > >  README.rst | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>     > >  1 file changed, 76 insertions(+)
>     > >  create mode 100644 README.rst
>     > >
>     > > diff --git a/README.rst b/README.rst
>     > > new file mode 100644
>     > > index 00000000000000000000..6a89b129661a949351e7
>     > > --- /dev/null
>     > > +++ b/README.rst
>     > > @@ -0,0 +1,76 @@
>     > > +`Mesa <https://mesa3d.org>`_ - The 3D Graphics Library
>     > > +======================================================
>     > > +
>     > > +
>     > > +Source
>     > > +------
>     > > +
>     > > +This repository lives at https://gitlab.freedesktop.org/mesa/mesa.
>     > > +Other repositories are likely forks, and code found there is not
>     > > supported.
>     > > +
>     > > +
>     > > +Project health
>     > > +--------------
>     > > +
>     > > +Travis:
>     > > +
>     > > +.. image:: https://travis-ci.org/mesa3d/mesa.svg?branch=master
>     > > +    :target: https://travis-ci.org/mesa3d/mesa
>     > > +
>     > > +Appveyor:
>     > > +
>     > > +.. image:: https://img.shields.io/appveyor/ci/mesa3d/mesa.svg
>     > > +    :target: https://ci.appveyor.com/project/mesa3d/mesa
>     > > +
>     > > +Coverity:
>     > > +
>     > > +.. image:: https://scan.coverity.com/projects/139/badge.svg?flat=1
>     > > +    :target: https://scan.coverity.com/projects/mesa
>     > >
>     >
>     > I'm going to Parrot Mark and say that build tests and coverity warning
>     > levels are not good metrics of project health.  They're mildly useful
>     > development tools and that is all.  We don't want to send the message
>     that
>     > the project is healthy and/or the patches are good if the pass coverity
>     and
>     > build.
> 
>     Fair enough, but I'd like to keep them there, as I aimed them at devs,
>     for them to actually notice when the build is broken on some
>     platform/compiler/configuration instead of having to manually go to the
>     websites and check (which not many devs do).
> 
>     Do you have a suggestion for a better section title?
>     How about "CI status" ?
> 
> 
> How about "Public CI tools" with a comment saying that other non-public CI
> systems exist which actually test hardware.

How about "Build System Status"? Since that's what appveyor and travis are
really testing for us.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180608/c81578bf/attachment-0001.sig>