View · Index

Getting help

Introduction to the OpenACS Community

How to get help from the OpenACS community most effectively.

by Jade Rubick

OpenACS is more than a technology, it is a vibrant community. If you are new to, you are coming into this community as a newbie, or a new person. The OpenACS folks are extremely helpful. However, consider what resources you have available for getting information most effectively.

Communities work similarly to how a bank account works. You make deposits by doing things that are beneficial to the community, and you make withdrawals by doing things that take time and energy from the community. The more helpful you are, the more people are going to be willing to help you out. If you have a pattern of being demanding and unhelpful, people are less likely to help you as much. This is not a conscious effort to punish, but common social equitable practices. It is just how people tend to participate in general.

What have you to offer?

What have you to offer the community? You are new, so maybe you cannot offer much in the way of technical knowledge. Can you trade for detailed technical help from more knowledgeable individuals?

  1. If there is no documentation for what you're trying to do, then the single most helpful thing you can do is write documentation as you learn. Use documentation to both keep track of what you’ve learned, and as a way of sharing that knowledge with others. It is also something you can trade for the time of more experienced developers. They know that if they help you out, you'll write up documentation for it, and they might not have to answer that question again.
  2. As you find bugs, you can file them in the OpenACS bug-tracker.
  3. If you have a particular project in mind, or something you're planning on creating, then building that project and sharing it with the community is good incentive for people to help you. They may be interested in what you're building.
  4. When a newer newbie asks a question you know the answer to, answer it! Many OpenACS developers budget out a certain amount of time a day to help the general community. This builds goodwill, strengthen the platform you're using, and helps those users become more knowledgeable so they can contribute to the community.
  5. As a newcomer, you have a unique perspective to OpenACS. You can often see deficiencies and areas to improve that old-timers might not even notice. Feel free to bring them up as suggestions. Remember that the OpenACS community is a community, not a company. It isn't their responsibility to fix things for you, or make them better. But it is often in their self-interest to improve things, and they will. Flames won't get you anywhere, but thoughtful suggestions will.
  6. Even though you aren't proficient with OpenACS (yet), you may have other skills that are useful. For example, some people have UI design skills, others may have Linux administration skills, or a security background.

I write this not because you're going to have trouble getting help. On the contrary, I've seen people in the OpenACS community help out people that are being very demanding and troublesome. My main hope in writing this is to give newbies a guide to how to most effectively get information.

previous April 2024
Sun Mon Tue Wed Thu Fri Sat
31 1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 1 2 3 4

Popular tags

17 , 5.10 , 5.10.0 , 5.9.0 , 5.9.1 , ad_form , ADP , ajax , aolserver , asynchronous , bgdelivery , bootstrap , bugtracker , CentOS , COMET , compatibility , CSP , CSRF , cvs , debian , docker , docker-compose , emacs , engineering-standards , exec , fedora , FreeBSD , guidelines , host-node-map , hstore
No registered users in community xowiki
in last 30 minutes