Hi Julian,
the only reason I added that was that this way I was hoping to reduce your
hesitation to have just anyone listed.
I think there is nothing preventing us from just taking the first three columns.
But I think we need to have anyone listed who asks to be listed (even if it's a
company
Hi Chris,
I think ist a good idea to model it as other projects do it BUT I don’t like
the way this is setup.
One thing we take very high at apache is the "two hats" principle.
Thus I dislike that companies list "all" their employees that are comitters /
pmcs like a "trophy", that feels
Hi all,
it seems we can rowspan in tables with asciidoc:
https://mrhaki.blogspot.com/2014/12/awesome-asciidoctor-span-cell-over-rows.html
So I would suggest to rowspan the logo name and the description of companies
and to have the remaining columns one row per employee.
Chris
Am 05.06.20,
Hi Julian,
I had already sent an update ... I had initially just copied the text from the
adopters page ...
Well I thought that we would have multiple rows for multiple people involved
and for each specify their involvement ... not sure if we should have a table
in a table or similar.
Chris
LGTM.
Although I suggest some changes in the table:
- More important than a company description would be what they offer (see e.g.
Postgres Page: https://www.postgresql.org/support/professional_support/europe/)
- I would make it a bit smaler
- And Involvement level we should standardize a bit
