Skip to content

Update contributing docs with guidelines for LLM code and unwanted featuresΒ #2003

@micahellison

Description

@micahellison

Affected Page(s)

I think our Contributing docs could use some more specific boundaries.

What Could Be Better?

  • Document practices around issues and code generated by LLMs.
    • Do we want these at all?
    • At the very least, I'd like some guardrails against contributors submitting LLM responses that they themselves don't understand.
  • Document more boundaries around what kinds of features we won't accept.
    • For example, I don't want jrnl accessing anything over the internet, because I want to minimize the risk of data exfiltration, I do not want to support constantly-shifting online APIs, and it isn't concordant with the UNIX philosophy we're trying to follow.

Other Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    πŸ†•New!documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions