ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Decide on core teams (Task #21)


Added by Muntek Singh at 2010-12-29 10:45 am. Updated at 2011-09-04 09:27 pm.


Status:Closed Start date:
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:ChiliProject - Organization
Target version:-
Remote issue URL:

Description

Decide on core teams. Wiki Page


Related issues

related to Task #22: Decide on the scope of each team Open 2010-12-29
related to Task #23: Decide on a process for cross-team work Open 2010-12-29
related to Task #24: Pick team leaders Closed 2010-12-29
related to Task #25: Team Leaders Processes Open 2010-12-29
related to Task #26: Benevolent dictator succession Open 2010-12-29

History

Updated by Muntek Singh at 2010-12-29 10:46 am

http://www.redmine.org/wiki/redmine/Teams is probably the best starting point since it's basically what we decided on together anyways

Updated by Eric Davis at 2010-12-29 04:48 pm

I'd like to merge a few of those teams to start. It felt like we split people up too early before there was a need. The "Development" team should be split a bit though, it's such a major section.

Changing this to Release 1.1.0. I'd like to open up the teams to everyone in the community.

  • Target version deleted ()

Updated by Eric Davis at 2011-01-12 01:41 pm

  • Project changed from Organization to ChiliProject
  • Target version deleted ()
  • Category deleted ()

Updated by Eric Davis at 2011-01-12 01:45 pm

  • Category set to ChiliProject - Organization

Updated by Eric Davis at 2011-01-12 02:29 pm

  • Tracker changed from Feature to Task

Updated by Eric Davis at 2011-01-17 03:21 pm

Do we really need a Market Research team? That doesn't feel like it fits an open source project at all.

Updated by Niels Lindenthal at 2011-01-18 12:42 am

Why shouldn't an open source project know what other projects are doing and what our users need? I am sure we need on. This is one aspect that makes our project better than Redmine.

Updated by Wieland Lindenthal at 2011-01-18 09:51 am

@Eric: As long as it is our goal to keep growing in our market share, it is absolutely necessary to know what is urgently needed and what is not urgently needed. If there are people out there willing to conducts surveys, why should we ignore their results? I mean, if we do not have additional information, we simply do what we think that is right and that might be wrong in some cases.

In my opinion a market research should should analyse bug reports, feature requests and forums and should communicate with to potential and existing new users.

Updated by Eric Davis at 2011-01-18 10:14 am

If someone is willing to lead the team and do all of the work for it, that's fine. I just think it feels really out of place, it could just be how it's phrased (feels very business-speak to me).

Whoever wants to be the team leader will need to create and maintain a set of Objectives and Goals that match the main project Objectives and Goals (every team will need to do this once things are underway).

Updated by Niels Lindenthal at 2011-01-20 08:10 am

Eric, please don't worry about business terms. Please feel free to ask. I will lead this team until somebody else wants to take over.

Updated by Felix Schäfer at 2011-02-01 10:50 pm

  • Status set to Open

Updated by Holger Just at 2011-09-04 09:27 pm

Closing this issue for now. Is there are still new ideas, please discuss them on IRC or on the forums. Or create a new issue if required.

  • Status changed from Open to Closed

Also available in: Atom PDF