Ethos
goozbach
Please help me to fill this out.
* Open -- everything (minus signing keys/system access) are shared
under an open license. *EVERYTHING* build scripts, one-off scripts,
etc.
* Kind -- Community communication is encouraged to be kind and never
attack. Work with the other rebuild projects out there to improve
*EVERYONE*
* Transparent -- Spend time on helping everyone easily know "where are
things?". Ask for help when needed.
* Good -- Have a well-defined "pass criteria". Enable QA to have a
checklist and when we slip something concrete to point to.
* Organized -- One channel for the "This is Released" mechanism. The
canonical location always gets updated first. Twitter, blog, irc,
mailing list always points to that.
--
What else?
Clint Savage
> What is our ethos?
>
> Please help me to fill this out.
>
> * Open -- everything (minus signing keys/system access) are shared
> under an open license. *EVERYTHING* build scripts, one-off scripts,
> etc.
Completely agree here. I think the point of being open is also
inviting the community to participate. 'Patches Welcome' should be
our mantra.
> * Kind -- Community communication is encouraged to be kind and never
> attack. Work with the other rebuild projects out there to improve
> *EVERYONE*
>
> * Transparent -- Spend time on helping everyone easily know "where are
> things?". Ask for help when needed.
I think these two really need to be a core value. Kindness and
Transparency make it easier for people to get involved and our project
to grow quickly. Thanking people for their comments and concerns and
encouraging them to join us seem paramount to this community's
success, overall.
We should never respond with RTFM unless we have a good resource to
point them. And even when we give them the resource, make sure we're
reasonably available to answer questions or update a document that
might be incorrect. Invite questions, encourage someone to return to
ask more questions, etc., etc.
> * Good -- Have a well-defined "pass criteria". Enable QA to have a
> checklist and when we slip something concrete to point to.
Maybe change 'Good' to 'Quality' here? I like the idea of a 'quality'
release over a 'good' release. In addition, if we put quality in
everything we do, it helps to prove a methodology for why we do things
and repeatability.
> * Organized -- One channel for the "This is Released" mechanism. The
> canonical location always gets updated first. Twitter, blog, irc,
> mailing list always points to that.
Isn't this just communication? I'm curious if maybe organization
should be 'document everything - procedures, policies, etc.' and this
should be re-labeled 'communication' or some such.
> --
> What else?
>
Enjoy your work. If you are overwhelmed, or not enjoying the work, say
so and take a break. Use the rule of two feet and walk away. Please
let people know what is going on with sincerity and grace. I would
rather someone be happy doing the work than someone who grumps all of
the time.
Value your fellow community members' contributions. Be it big or
small, every contribution helps our community. Give what you can and
encourage others to do the same. Never disparage just because someone
isn't 'pulling their weight'. There is no such thing as not doing
enough.
Commit to only what you think you can handle. Don't feel pressured to
do more. There will be times when the community is in a crunch. Don't
feel as though you have to take on more just to meet deadlines.
---
I'm sure I have other thoughts, but I'd like to see the others'
comments. If we throw some away, I'm cool with that...
Cheers,
Clint
goozbach
Clint Savage
four letters - T - I - M - E
:)