3:44 p.m.
Discussions have started back up around creating a brand with associated
logo, color palette, design elements, and the like. You are invited to
participate, as a community member reviewing design ideas, or directly
involved in generating designs and related tasks.
Ideally, we'll be able to apply some beta decisions in the debut
announcement, such as color palette and a logo idea.
Main branding task and tracking ticket:
https://github.com/theopensourceway/theproject/issues/62
Logo discussion:
https://github.com/theopensourceway/theproject/issues/13
These elements are the building blocks and patterns for the website,
guidebook styling, print book styling (for PDF), and so forth.
If you are interested in this topic, we should be seeing some items
coming from Tuomas Kuosmanen and Shaun McCance (from Red Hat's OSPO) for
your input.
The list of items in issue #13 are the needs we're tracking for this.
Take a look, any questions or anything missing?
We could use some illustration skills, especially around a book cover
design that can be applied to the PDF and prepare for a possible printed
run future.
Tuomas—what other skill gaps do we need to fill?
There are also some web designer skills needed around styling the
Asciidoc output, including building a multi-page website for the HTML
version (perhaps generated by Antora?).
Shaun—what skill gaps do we have around the various book rendering tools?
There are some large and some small tasks in here, and we should all be
able to review some iterations of the work created by those who step up
to work on the task. Ultimately, we should let designers and the doers
of the task decide on the choices we consider and brand we land on.
Best regards,
- Karsten
--
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
https://theopensourceway.org | https://github.com/theopensourceway/guide
2:50 p.m.
On Wed, 2021-01-27 at 13:44 -0800, Karsten Wade wrote:
There are also some web designer skills needed around styling the
Asciidoc output, including building a multi-page website for the HTML
version (perhaps generated by Antora?).
Shaun—what skill gaps do we have around the various book rendering
tools?
I'm going to try to bullet point skills people could bring. I have
varying levels of experience across these points, but I don't need to
own any of them if others are eager.
* Visual style work. Document design is related to but distinct from
graphic design. I have some experience, and I put together a draft of a
start of a visual identity. I'll remind the crowd that I am red-green
colorblind, so I always copy color palettes from others, and even then
I might mess up.
* CSS work to implement the visual style in HTML. I do this kind of
thing often enough.
* Asciidoctor experience to make sure our CSS and whatever else is
smoothly fits into how docs are generated, and aren't hacks on top.
* Work with asciidoctor-pdf (and possibly the underlying renderer
Prawn) to implement our style. I have some print experience, but it's
old, and tools are new. I can figure it out, but I have to yell at
clouds first or something.
* Site publishing/orchestration work. Is Antora the answer? Maybe,
maybe not. But different pieces of the site come from different places,
and there's not a clean publishing story.
3:15 a.m.
Le lundi 01 février 2021 à 15:50 -0500, Shaun McCance a écrit :
On Wed, 2021-01-27 at 13:44 -0800, Karsten Wade wrote:
>
> There are also some web designer skills needed around styling the
> Asciidoc output, including building a multi-page website for the
> HTML
> version (perhaps generated by Antora?).
>
> Shaun—what skill gaps do we have around the various book rendering
> tools?
I'm going to try to bullet point skills people could bring. I have
varying levels of experience across these points, but I don't need to
own any of them if others are eager.
* Visual style work. Document design is related to but distinct from
graphic design. I have some experience, and I put together a draft of
a
start of a visual identity. I'll remind the crowd that I am red-green
colorblind, so I always copy color palettes from others, and even
then
I might mess up.
* CSS work to implement the visual style in HTML. I do this kind of
thing often enough.
* Asciidoctor experience to make sure our CSS and whatever else is
smoothly fits into how docs are generated, and aren't hacks on top.
* Work with asciidoctor-pdf (and possibly the underlying renderer
Prawn) to implement our style. I have some print experience, but it's
old, and tools are new. I can figure it out, but I have to yell at
clouds first or something.
* Site publishing/orchestration work. Is Antora the answer? Maybe,
maybe not. But different pieces of the site come from different
places,
and there's not a clean publishing story.
For that part, now my team has a openshift cluster for production, we
can help. It is much easier to have a pipeline of heteroclite toolsthan before.
--
Michael Scherer / He/Il/Er/Él
Sysadmin, Community Infrastructure
8:38 p.m.
All:
We'd like your thoughts on the project logo.
Tuomas has a new treatment for a logo, which has gotten some +1s in
discussion so far and is the "current favorite" attached to this email.
You can comment on this design and other ideas here:
https://github.com/theopensourceway/theproject/issues/13#issuecomment-776...
I like how this design evokes a classic Art Deco or Paris Metro feeling
that is very grounding, and the electric modern edge of the git merge
pattern.
We're putting together some stuff right away for e.g. the Red Hat
Summit, so this is your chance to provide some thoughts about this logo.
Can we get your feedback by Wed of this week?
Regards,
- Karsten
On 1/27/21 1:44 PM, Karsten Wade wrote:
Discussions have started back up around creating a brand with
associated
logo, color palette, design elements, and the like. You are invited to
participate, as a community member reviewing design ideas, or directly
involved in generating designs and related tasks.
Ideally, we'll be able to apply some beta decisions in the debut
announcement, such as color palette and a logo idea.
Main branding task and tracking ticket:
https://github.com/theopensourceway/theproject/issues/62
Logo discussion:
https://github.com/theopensourceway/theproject/issues/13
These elements are the building blocks and patterns for the website,
guidebook styling, print book styling (for PDF), and so forth.
If you are interested in this topic, we should be seeing some items
coming from Tuomas Kuosmanen and Shaun McCance (from Red Hat's OSPO) for
your input.
The list of items in issue #13 are the needs we're tracking for this.
Take a look, any questions or anything missing?
We could use some illustration skills, especially around a book cover
design that can be applied to the PDF and prepare for a possible printed
run future.
Tuomas—what other skill gaps do we need to fill?
There are also some web designer skills needed around styling the
Asciidoc output, including building a multi-page website for the HTML
version (perhaps generated by Antora?).
Shaun—what skill gaps do we have around the various book rendering tools?
There are some large and some small tasks in here, and we should all be
able to review some iterations of the work created by those who step up
to work on the task. Ultimately, we should let designers and the doers
of the task decide on the choices we consider and brand we land on.
Best regards,
- Karsten
--
Karsten Wade [he/him/his]| Senior Community Architect | @quaid
Red Hat Open Source Program Office (OSPO) : @redhatopen
https://community.redhat.com | https://next.redhat.com | https://osci.io
https://theopensourceway.org | https://github.com/theopensourceway/guide
1374
days inactive
1394
days old
3 comments
3 participants
participants (3)
-
Karsten Wade -
Michael Scherer -
Shaun McCance