DebOps identity at a glance

[AnBuKu]

Some rough outline and reminder for open non-tech issues

DebOps identity at a glance

• Vision
• Mission
• Message to the crowd
• Brand
  • Brand name
    • DebOps
  • Message to the crowd (see standalone point)
  • DebOps logo (Addressed in DebOps logo - Status, requirements and re-desing/development #205)
    • Requirements
    • Developement
      • ascii art
      • SVG visual graphic
  • Domain names
    • https://debops.org/ (main website of the project)
    • debops.net (reserved, not yet used)
• Visual identity
  • DebOps logo (see in point "Brand")
  • DebOps typeface or font
  • DebOps colors
  • DebOps branding and style guide
• Communication principles
• Code of conduct - Principles of the Community (Addressed in Code of conduct #198)

Sooner or later answers about these points mentioned above need to be answered.

[ypid]

@AnBuKu Thanks! I edited your answer to make them check marks so that we can track progress. I would be interested in the "Code of conduct". There are many good versions out there. Qubes is adapting on as well currently. I will keep an eye open for that.

[AnBuKu]

@ypid these are simply some bullets. Just as a reminder. Nothing more :-)

[ypid]

I guess "Domain names" should be pretty defined already with debops.org?

[AnBuKu]

"Domain names" are FQDN. Thus, debops.org is one. Others could be: debops.net, debops.info etc. or deb-ops.org, deb-ops.net etc. Either these FQDN's are singel web sites or redirects to debops.org

[drybjed]

Hmm, mutiple domains... Debian has debian.org for official organizational services, and debian.net for something additional, stuff maintained by project developers which might or might not become official. Still, who pays? :-)

[AnBuKu]

What about "Godparent of a DebOps domain name"? - Sponsoring program for people or organizations to support DebOps by funding the annual fee for one of the domains on behalf of DebOps, but neither being the legal owner nor the technical contact of the respective domain, but a godmother or a godfather of a DebOps domain.

I hereby confirm to be the godfather of debops.ch - Tell me where to make the payment.

[ypid]

@AnBuKu Not sure if that would be useful for the project if users help us to get on more tlds. I guess we could setup something with bitcoin in the further or allow users to vote for features with donations.
We should check what Debian does here first.

I thought about this question a couple of days ago for myself (not that it is really urgent 😉) and currently, my personal policy for this is that I would rather have people pick an org from awesome-donations and donate there. I will benefit indirectly which is fine.

Reasons for this:

• I don’t have to deal with the topic of receiving donations
• It allows me/users to prioritize

[drybjed]

The more domains project uses, the more "muddy" everything becomes. debops.com is already taken. I think that sticking to 1 domain should be enough. I bought debops.net in case we want do to something similar to what Debian does with its debian.net domain. But, IMO, that should be enough for now.

[ypid]

"DebOps Project" or "DebOps project"?

[drybjed]

I think that "DebOps Project" refers to the project as a whole, ie. an official name. And "DebOps project" could be expanded to "DebOps Project project", when you refer to the Project in a conversation. Does that make sense?

[AnBuKu]

ehm, would use DebOps only. That's the brand name.

"Project" doesn't really add value.

What is needed: Content to /Message of DebOps (brand)

[ypid]

Does that make sense?

Except: And "DebOps project" could be expanded to "DebOps Project project", when you refer to the Project in a conversation.

"Project" doesn't really add value.

I think @AnBuKu is right. Other "projects" also don’t include the word "project" in the name.

[drybjed]

Very well. So, DebOps project then.

[AnBuKu]

@drybjed skip the projet ;-)

DepOps

[AnBuKu]

sorry for closing, what not my intention to stop this thread :-(

[drybjed]

@AnBuKu Old habits die hard. :-)

[AnBuKu]

hehe :-)

[drybjed]

However, I think that 'DebOps' by itself might bring too close connotations to 'DevOps'. Since DebOps is a "project" and not a "methodology", I think referring to it as such might be better.

[AnBuKu]

'DevOps' is named 'DevOps' and not 'DevOps methodology' or 'DevOps whatever'.

Thus, my POV, DebOps can be self-confident without any "false" modesty. I't's up to DebOps to add a message and content to it's brand and by doing so, creating the difference towards 'DevOps'.

Basically you might even say, my POV again: DebOps is 'DevOps' focused onto Debian.

[AnBuKu]

For the record: https://en.wikipedia.org/wiki/DevOps

[drybjed]

@AnBuKu Agreed, I like this meaning.

[ypid]

So to summarize: DebOps should be able to stand for it self and should be preferred but when we refer to it as a project we would write it as: DebOps project.

[ypid]

Note that "DebOps project" is currently used to refer to two different things:

1. The DebOps project, https://debops.org/
2. A Ansible/DebOps project directory used to manage a data center as setup by the DebOps Tools. Can also be referred to as "DebOps project directory".

So, when we now only use the phrase "DebOps project" for the second meaning, this will hopefully also make the docs clearer.