Forum OpenACS Q&A: What is an OpenACS Citizen?

Collapse
Posted by Talli Somekh on
Hi everyone,

Al Essa and I were having a conversation about the governance issue the other day and one of the issues we discussed was what made up a good member of the OpenACS community. Al's background in philosophy produced an interesting discussion of what citizenship means in the context of a community.

I'm in no way qualified to begin a discussion in political philosophy, so I'll allow those familiar with Aristotelian philosophy to do so to their heart's content.

What I'm interested in, though, are people's thoughts about what makes a good OpenACS citizen or community member. That is, as we move towards implementing a governance model, what are the traits of people who we want to lead the community? What kinds of skills should they have? How should we encourage newbies to get involved? How do we accept newbies into the community? Most importantly, who buys the beer?

There are all sorts of questions that can further be asked. I'm hoping this will be an interesting discussion that will help us understand the governance issue better.

talli

Collapse
Posted by Torben Brosten on
Thanks for asking, Talli.

"as we move towards implementing a governance model.."

First, is the word "governance" a hinderance to managing the development of a tool set? Governance implies authority by power and control. Granted, the authority would be benevolent, perhaps some others, like myself, may be concerned about authority for authority's sake. Authoritarian positions attract the types of personalities that are incompatible with goals (other than stagnation and decay).

The OpenACS community is full of bright participants. There must be another word that better fits the function: Core-mangement? For starters, "management" is obscure and flexible enough to fit the model regardless of structure or process. Still, there must be other words that fit better.

"what are the traits of people who we want to lead the community?"

I'm partial to traits consistent with "servant leadership" which describes current leadership dynamics (as I see them). Leading is not necessarily authoritarian (top-down), but found by inspiring others to participate and learn through a kind of nonspecific expert mentoring (expert hierarchy), where sometimes the student is the teacher.

"What kinds of skills should they have?"

listening skills are as important as computing and conventional leadership skills.

"How should we encourage newbies to get involved?"

how about creating the forums previously discussed? (admin, end-user/marketing/advocacy)

"How do we accept newbies into the community?"

Auto accepted (like anonymous ftp). Only rejected when behavior is harmful to community ie spamming, trolling etc.

"Most importantly, who buys the beer?"

What if someone doesn't drink beer, but eats bread soaked in it, and cooked like porridge (beerbread)?  It takes all kinds to create something really great and improve on it (translation for Essa types: diversity in community leads to continual innovation, a key aspect of a competing knowledge/learning community)

This food talk is making me hungry. Time for some fruit porridge covered with a "healthy" layer of whipping cream. Followed by a thick cup of coffee.

cheers,
Torben

Collapse
Posted by Rafael Calvo on
Talli,

I posted this on .LRN forum, but it might help to this discussion. Have a look at:
http://news.com.com/2009-1087_3-1024609.html

"Programmers contribute to free software and open-source projects for many reasons--some for the fun of it, some to improve their skills and others for a paycheck.

Many people have wondered why these people give their work away. The truth is that many projects have become incorporated in order to protect themselves from individual liability. Since the founding of the Free Software Foundation in 1985, a number of new nonprofit foundations have formed, often around specific technologies, to serve the interests of programmers.

Harvard Business School professor Siobhan O'Mahony discusses her research on foundations formed around three projects: Debian, a complete non-commercial distribution of Linux; the GNU Object Model Environment (GNOME), which is a graphical user interface for Linux-based operating systems; and Apache, a public domain open source Web server."

Collapse
Posted by Torben Brosten on
Following-up on Rafael Calvo's comments, Eric S. Raymond has written extensively about the open-source culture. Many of his observations about "How to become a Hacker"[1] are relevant to leadership qualities for OpenACS.

Last night, I re-read a copy of The Cathedral and the Bazaar [2] that's been heavily worn with highlights, bookmarks and scribblings in the margins. The relevant points are too numerous to repeat here, but I would like to note one point in particular, because I believe it describes how OpenACS.org (the community) has tackled problems with the complex system OpenACS. And, why the politics (power dynamics) of OpenACS should not be the focus for leading OpenACS.

quote:

..Another vital factor was the development of a leadership style and set of cooperative customs that could allow developers to attract co-developers and get maximum leverage out of the medium.

But what is this leadership style and what are these customs? They cannot be based on power relationships--and even if they could be, leadership by coercion would not produce the results we see.  Weinberg quotes the autobiography of the 19th-century Russian anarchist Pyotr Alexeyvich Kropotkin's <em>Memoirs of a Revolutionist</em> to good effect on this subject:

Having been brought up in a serf-owner's family, I entered active life, like all young men of my time, with a great deal of confidence in the necessity of commanding, ordering, scolding, punishing and the like.  But when, at an early stage, I had to manage serious enterprises and to deal with [free] men, and when each mistake would lead at once to heavy consequences, i began to appreciate the difference between acting on the principle of command and discipline and acting on the principle of common understanding.  The former works admirably in a military parade, but it is worth nothing where real life is concerned, and the aim can be achieved only through the severe effort of many converging wills.

previous quote from pages 51-52, (Jan 2001 ed.) Cathedral and the Bazaar.

Raymond has written a second paper, entitled "Homesteading the Noosphere"[3] where his "analysis has large implications for anyone interested in organizing large-scale intellectual collaborations" to which I believe coordinating the variety of expertise requirements for OpenACS development parallel "organizing large-scale collaborations" even if the number  of core-developers remain small. The tool set is designed for scalable and high-demand/performance websites, where development decisions have far-reaching impacts on tens of thousands or more end-users.

1. http://catb.org/~esr/faqs/hacker-howto.html

2. http://catb.org/~esr/writings/cathedral-bazaar/index.html

3. http://catb.org/~esr/writings/homesteading/homesteading/

Collapse
Posted by Malte Sussdorff on
Leaders of the community should be well connected within the community. It is important that they know the people and are not afraid to speak their minds. Furthermore, if we talk about leadership here, we should look for a diverse set of people that make up the board. Though the community primarily consist of developers, I do think that some non technical people would be a good thing for attracting other non developers to the community as well. Just have a look at the discussions we had about business and marketing back in 2001. One was 48 pages long......