coderkrow
[en]
~$./lang --switchSwitch language
~$cycle --themeclaro → oscuro → sistema
[legal] ~/help

Help

Need a hand with coderkrow? Whether you're exploring the site, joining the community, working with one of our projects, or something simply isn't behaving the way it should, this is the place to start.

What is coderkrow?

coderkrow is an independent software development project and community focused on building things, sharing knowledge, experimenting with technology, and documenting the process along the way.

You can explore the ecosystem through:

Where should I go?

Use this as a quick map:

Something is broken?

If you found a bug in one of our projects, report it through the project's GitHub Issues rather than contacting us with a vague description.

A useful bug report includes:

What happened?
What did you expect to happen?
How can we reproduce it?
Which project/version are you using?
What environment are you running it in?

If possible, include:

Before opening an issue

Please check whether:

  1. The issue already exists.
  2. The project documentation addresses it.
  3. You are using a supported version.
  4. The problem can be reproduced consistently.
  5. The issue is actually related to the project.

Never include passwords, API keys, access tokens, private keys, or other secrets in an issue.

Have an idea?

Not every problem needs to be solved with a pull request.

If you have an idea for improving a coderkrow project, propose it through the project's discussions or issue tracker.

Good proposals explain:

We care about the problem before the implementation.

Found a bug?

Bugs happen. That is software.

When reporting one, do not worry about making the report perfectly technical. Start with what you know:

I did X, expected Y, but got Z.

That is enough to start. If you can provide more technical information, even better.

Want to contribute?

coderkrow projects may be open to contributions depending on the repository.

Before contributing:

  1. Read the project's README.
  2. Check its contribution guidelines.
  3. Look through existing issues and discussions.
  4. Avoid duplicating work that is already underway.
  5. Keep changes focused.
  6. Follow the project's existing conventions.
  7. Test your changes before submitting them.

For larger changes, opening a discussion before implementing the feature can save everyone time.

Contributions don't have to be code

You can also contribute by:

Can't find the documentation?

Documentation is continuously evolving.

If something is missing, confusing, or outdated, let us know.

A documentation issue can be as simple as:

This example doesn't work anymore.

or:

I followed these instructions and got this error.

That is useful information.

Community

The coderkrow community brings together developers and technology enthusiasts from LATAM and beyond.

The community is multilingual and may include content in:

You don't need to be an expert to participate.

Ask questions, share what you are building, discuss technology, show your projects, or simply hang around.

The goal isn't to pretend that everything works perfectly.

It's to build, break, learn, and do it again.

Discord

The community Discord is the best place for informal conversation and real time interaction.

Use it for:

For actionable bugs and project specific issues, prefer GitHub Issues so they can be tracked and resolved properly.

Security

Found a security vulnerability?

Do not publish sensitive vulnerability details in a public issue or community channel.

Security reports should be handled through the designated security reporting process.

When reporting a vulnerability, provide enough information to reproduce and assess the issue while minimizing exposure of sensitive information.

Privacy

Please be careful when sharing information publicly.

Never post:

If you accidentally expose a credential, revoke it immediately. Do not simply delete the message or file.

For information about how coderkrow handles personal information, see the Privacy Policy.

Policies

The following pages contain the rules and policies governing coderkrow:

If you are contributing to an open source repository, also check the repository's own license and contribution guidelines.

Still stuck?

If you went through the documentation and still can't find an answer, that's fine.

Start with the most relevant place:

Question about a project?
  Check its README or documentation
    Still stuck?
      Search existing GitHub issues
        Still stuck?
          Open an issue or discussion

Want to talk?
  Join the community

Found a security vulnerability?
  Use the security reporting process

Found something wrong with this website?
  Report it to the coderkrow project

When in doubt, tell us what you were trying to accomplish, what happened, and what you expected instead.

That is usually enough to figure out where to go next.

The short version

And when something inevitably explodes:

Check the logs first.