Home
The Toolkit for Online Communities
17362 Community Members, 1 member online, 2213 visitors today
Log In Register
OpenACS Home : Forums : .LRN Q&A : .LRN Web Site : One Message

Forum .LRN Q&A: Re: Re: .LRN Web Site

Collapse
3: Re: Re: .LRN Web Site (response to 2)
Posted by Caroline Meeks on
Maybe .LRN doesn't have one clear daddy like Moodle but certainly Roc and Al are at least Uncles. So who gets to decide?

We need a clear, documented path for these decisions. I'm all for discussions in the forums but if we want to get this project going we have a zillion of these decisions to make. Many, perhaps even most of them it won't matter which we decide as long as we decide and act. But for some of them it will matter.

We need clear, documented governance and decision making processes.

In my opinion power needs to rest with the paying .LRN members but authority to make decisions needs to be deligated in a transparent and legitimate manner.

Something like.

Paying members (organizations) elect the board. The board elects/appoints by majority a technical team. The board has a voting procueedure like the OCT's. The board can ask for nonbindng advice from he technical committee. A certian number of paying members can veto a board decision. Maybe the board elects a webmaster or two for the .LRN site and they can make automous decisions like this one, and the board can veto if they don't like it.

Personally I like veto as a tool in these types of organizations. It gives people the abiltiy to make a decision and know if it really isn't what the elected goverance wants then they can stop them. It lets people act in a "ask forgiveness rather then seek permission/concenus" mode. That promotes action.

My advice to .LRN is write up some rules. Delegate down. Enforce transparency. Give the level above Veto. Create a clear terms of service and proceedures as to how new people are appointed/elected/hired to positions.

Collapse
4: Re: Re: Re: .LRN Web Site (response to 3)
Posted by Malte Sussdorff on
Hi Caroline, I think your idea is great. But isn't this already in place or how does the .LRN foundation work? Doesnt it have to have a board? Maybe we could jump start this process by writing a wiki page on what is already in place, along with an annotation which is made out of legal demands.

Then anyone can add suggestions to this and the paying members can then vote on whether they like the bylaws. And then you go from there.

Collapse
Posted by Matthew Coupe on
I'm not sure I agree about the dotLRN website being a static site, IMHO it already is a static site with an occasional news entry. I really feel it would benefit from it's own forums, wiki pages, blogs etc (all the best bits of the dotLRN!)

There is currently a single forum in openACS.org for everything from LDAP to installation to development to how to teach. Now this makes it quite difficult to find past posts that may be of interest to people, this may also deter people from reqesting notification from the forum and as such we lose the valuable input of the users of the platform.

With regards to the decision making process I think the route we are discussing is viable and probably the 'fairest'. I do feel though that the decisions made by this group should then be advertised in a clear roadmap. - perhaps this could be something benefitial to the current discussions regards openACS quality for those following that thread. Bits of development here and there without a real indication of what is new in each release.... unless I'm missing something....

There must be a large dotLRN community out there yet they seem to be lurking in the shadows much of the time. I have been working with dotLRN for almost a year now and have definitely found it quite difficult to get the information/support I needed to make my life easier, this can be very offputting for people who maybe don't have the motivation to really search for things (ie organisations just starting off on the road and maybe doing comparitive studies). I definitely feel we need to bring everything dotLRN closer together, but not alienating or distancing dotLRN from openACS could be a challenge there.

Matthew