Codex

Interested in functions, hooks, classes, or methods? Check out the new WordPress Code Reference!

User:MichaelH/Responsiblities of Plugin Users and Authors

This article is a ROUGH DRAFT. The author is still working on this document, so please do not edit this without the author's permission. The content within this article may not yet be verified or valid. This information is subject to change.

programmers aren't doing plugins, because they're getting beatup by users with questions etc. so want to address that issue

Plugin User Obligations

  • owen's article
  • being polite
  • patience
  • it's free what do you expect?
  • follow instructions
  • research before asking do you homework
  • what version of WordPress using
  • what version of plugin
  • has the question been asked and answered
  • learn the software
  • good return email
  • leads to learning
  • read the faqs
  • form cogent questions
  • be concise
  • show link to problem
  • recompense the author
  • be professional
  • How to ask a quesiton http://www.catb.org/~esr/faqs/smart-questions.html
  • acceptable forum behaviour


Plugin Author Responsibilities

  • why to blog interact with readers
  • how the plugin author can prevent the assault.
    • write a complete description and usage examples (don't assume mind reading abilities)
    • Provide a space on your site - don't rely upon the Forum.
    • Understand that making a plugin is a commitment to provide support, too. that kind of knowledge helps diffuse things

because they've just been told this is going to happen.

    • Writing plugins isn't about fame, it's about giving.
  • some plugin writers talk about how they have to come up with something HOT to attract attention to their site. They want

the fame.

  • its got to be fun
  • take vacations
  • get help from others
  • off load support
  • get a life
  • quality
  • grow up
  • retain talent
  • be honest with yourself
  • balance
  • diversions
  • be professional