ORPHEUS CHAMBER ORCHESTRA TO HOLD TEACHING CASE

Orpheus, the only chamber orchestra in the world that consistently rehearses, performs, and records without a conductor, has garnered attention from the corporate sector for its unique approaches to creativity, innovation, and self-management.

For example, Orpheus had showcased its innovative approach to leadership for a group of Haas MBA students at the International House auditorium. Morgan Stanley has sponsored the event at Haas. The firm also sponsored an Orpheus residency at Hitotsubashi University in Tokyo.

Central to the distinctive personality of Orpheus is its unusual process of sharing and rotating leadership roles.

The "Orpheus Process" is built on individual responsibility, shared leadership, and workplace democracy.

The process has enabled the orchestra to unleash the talent, vision, creativity, and leadership potential of each member of the group.

For every work, an elected committee of musicians selects a concertmaster and each instrumental section chooses a representative.

These chosen representatives (the "core group") are responsible for forming the initial concept of the piece and developing an overall interpretive approach to the music before the entire orchestra comes together to rehearse.

The core also structures the rehearsal process for the entire orchestra, which provides clear leadership while insuring that every member has a real stake in the artistic outcome of every piece performed by the orchestra.

The results of the process have produced 28 years of sustained excellence at the highest level of international accomplishment.

The main focus of the residency at Haas it was to demonstrate the Orpheus Process in action, as the orchestra rehearses the first movement of Haydn's Symphony No. 63 in C Major in "real time," showing by example their work process from core preparations to final product.

The applications of the Orpheus Process to the business world or the communities of open source projects, can be framed in the introduction of a Xoops Management thread and reinforced through a question-and-answer and a discussion period with the xoopsers and auto-proclaimed “Leaders”.

.
https://xoops.org/modules/newbb/viewtopic.php?topic_id=36319&start=0#forumpost157884
.

errrr.. never mind :-|

@ monty

"Interest: Internet, Clubbing, Trance & Hard House Music."

As multimedia producer i manage a few DJs, clubs and events like
http://www.sonar.es
I'm also still working at geneva (Lab Art Media R&D)
where there will be the
http://www.lakeparade.ch/

You should find here some interest !

Cheers


P.S. Every where it's open there's a cash opportunity!

nice :) i sometimes do PR work & promotions for uk media companies like frantic records, godskitchen, gatecrasher, bbtb, goodgreef and nukleuz. i love the scene.. and of course i get to get in practically all the uk clubs/events for free (aswell as free drinks) along with friends i take along with me :) it's just all the decent clubs are more than 80 miles from where i live so i have to travel, not that i mind cos it's worth it.. when i finally get round to building my own site i'll be doing more of it tho..

(sorry to the rest for this off topic reply)

I really look forward to the planned several XOOPS Management Teams to work.

As for the former XOOPS Simplified Chinese Support Site http://hiweed.com/xoops , I told Herko that the webmaster had stopped supporting XOOPS and put some words on his homepage offending XOOPS by recommending another CMS.
Herko removed that site from https://xoops.org/modules/xoopspartners/ and said would also remove cn.xoops.org

Unbelievable, how many months passed?
if you check http://cn.xoops.org, what could you read?!
If you do not understand Chinese, I ever translated it on this forum. If you need a humanbing translator, I am ready whenever you need.

Plz, deal with XOOPS seriously!
Plz, manage XOOPS professionally and efficiently!

When will the XOOPS management proposal get out?

Sorry, I was too emtional.

A few minutes after my above post, I realized that Herko perhaps does not have the right to change xoops.org's subdomains.
If it is this case, I talked to a wrong target and would appologize.

Perhaps, I have taken XOOPS too seriously and have made too much noise.
I would not get myself involved in any more non-technical discussion.

Phppp, please continue posting about concrete issues that need to be addressed. It's due to people like you noticing problems and trying to do something about it that the system improves.

With the subdomain issue, if it's still a problem then it is good that you bring up the issue again. It was probably overlooked the first time - this time it should be fixed.

phppp, rowd, I agree, that is something I forgot completely. The subdomains need to be looked at, all of them. I *think* I have access to the subdomains, but I'll make sure that they get changed soon.

This has nothing to do with XOOPS not being taken seriously or not, but everything with available resources. IMHO. AT the moment, I'm really busy with work and the preparations of my upcoming wedding. I put about 70% of my free time into XOOPS (used to be close to 90%). I don't have all the skills, and could really use some help. Mithrandir, Carnuke, Wtravel, Ackbarr all have taken part of the job, as had Predator.

I agree that things can be more open. But being more open requires good preparation, and some people tend to forget that (not pointing any fingers here!). The roadmaps have been in preparation for a while, and due to the lack of time from my side, could have been published earlier. The new organisation model (not proposal) will be published real soon, I really want to make this as clear as possible, so everyone understands how we are going to organise things. And my goal is that I can retire from managing the project, really. That everyone knows how to start initiatives within the collective project, how guidelines, rules and standards are set, how intra project decisions are made, how people can be held accountable (very important, I would have liked to have had Pred's feedback sooner, I really do care!), and how people get assigned tasks and privileges. That whole structure does not come falling from the sky. I have based this model on discussions with the community, feedback given, discussions with the President of the Apache Software Foundation, the MMBase Foundation and some of the leading members of the open source community,I have done research on open source project managemnent with failures as well as successes. And this is the area I do have skills in.

Anyways, it's going to be a lot more open then it's ever been (and as Skalpa has stated in his post, XOOPS has never been very open, ever), and it requires that people don't question everything that is being said or done, but trust that they do their part, so you can do yours. And that is what teamwork and a community is all about, collaborating to reach the goals of something bigger then yourself (and that goes especially for me!)

Herko

Herko, you're doing a great job - I hope you didn't take my previous post as being critical in any way. It takes time to set up management structures, especially going from what basically was a pretty closed, internal structure to a community-driven one. I appreciate all the work you put into it.

Could it be an idea to just set all the language code subdomains to point to xoops.org (local support page) for now, until the XOOPS Liaison Team decides on:
1. which sites are 'official' support sites.
2. a guideline about the use of the language code subdomains.

As we once discussed, the current system doesn't allow for 2 or more local support sites in the same language. One possible solution could be to have the subdomain lead to a 'portal' page listing the local support sites for that language, if there's more than one...perhaps? Something for the Liaison team to debate, I'd say