Forum OpenACS Q&A: Job description for OCT team member

Collapse
1: Job description for OCT team member
Posted by Jade Rubick on 09/26/03 08:54 PM
The nomination process has started for electing the new OpenACS Core Team (OCT).

One thing I think we need to clarify very quickly is what the job description is for an OCT member.

This should include:

- responsibilities
- scope of position
- length of position

The scope of the position has been defined somewhat, although murkily. The length of the position has been described well. But what are the responsibilities of an OCT member? This is important, because I don't want to nominate anyone without knowing exactly what they'll do. And I wouldn't accept the nomination without knowing what's involved.

The base line would be to

- monitor Technical Improvement Proposals (TIP)s and promptly respond to them.
- attend virtual OCT meetings and participate in the decision-making process.
- make fun of Talli whenever possible.

Any other suggestions?

Collapse
2: Re: Job description for OCT team member (response to 1)
Posted by Malte Sussdorff on 09/27/03 08:04 AM
I'm not sure in what way the OCT shall act as a spokesman on behalf of OpenACS. Furthermore
  • How much effort will be put in coordination and actual organization of attendences at trade fairs.
  • Is the OCT answering to journalists on behalf of OpenACS.
  • Will the OCT support marketing activities for OpenACS of third parties and under what conditions.
  • Is Coordination of new development, trying to prevent multiple implementations of features part of OCTs work
Though I appreciate the start of the nominations and already made my move, I'd strongly suggest to get the job description out, discussed and approved before the actual election.
Collapse
3: Re: Job description for OCT team member (response to 2)
Posted by Jeff Davis on 09/27/03 10:51 AM
The core team is primarily focused on the technical side of the OpenACS (what is in the code base now, what needs to be fixed, what needs to be documented, what needs to be added etc), so helping to avoid multiple implementations of features would be part of that. The intent is to have something like the apache project management commitee or the Tcl core team.

Advocacy/marketing is something some OCT members would do anyway, but it sould not be an obligation of the job and isn't part of the OCT mandate. I think it is important to be more organized about such things but I don't think just because it's important we should pile it on to the OCT.

Collapse
4: Re: Job description for OCT team member (response to 1)
Posted by Jade Rubick on 09/29/03 06:59 PM
How about this:

"The OCT is responsible for decision-making on the technological direction of OpenACS."

Expanding the powers and responsibility of the OCT is something that can be done by future elections, if we so decide?

Can we agree on that? Or should that statement be modified?