Organization

• release a new stable 2.5 version
• regain the public image and credibility
• recruit new developers to release a 3.0 version

We need to define the different communication channels and project management tools that we have and how/when to use them:

• phpCollab official Website/Blog: news about development, new releases, other nice news (e.g. new partnerships, half million download reached etc.)

• phpCollab Wiki : all the documentation (not only the install/upgrade guide, but also how to use the application) should be put there

• phpCollab Issues: bug reports, feature requests (Conflict with the Forum for the Support Requests. Solution: remove the Support Requests section from the tracker)

• phpCollab: we have the tool we are developing, we should use it to manage a release, at least "in the large": we can define a date e.g. for release 2.5 and all the phases to reach that date, it would be easier to reach the goal if we have the pressure of project management Gannt charts and visible calendar)

Google+ Communities

• public - phpCollab Community - Gather with other phpCollab enthusiasts and share your experiences!.
• private - phpCollab Developers Community

Old Locations

• depricated - phpCollab Google Group: works like a forum/mailing list (Conflict with Forum and Blog)
• depricated - phpCollab-dev Google Group: discussions group intended for developers only (advantage: good alternative to e-mai;, disadvantage: not collaborative like the Wiki)
• E-mail: goood for private messages (Conflict with other project management tools, with the tracker and with the forum if we use it to define next goals, tasks to do or discuss about bugs etc.
• Chat (Google Talk): nice way to know each other. Time consuming. If we chat we are not productive. Should be avoided ;)

** Priorities**. We need:

• website back and running (no dead links). Important for the image of the project.
• phpCollab platform for us. Important for us, to have an overview of milestones, release dates, deadlines etc.

the team is composed by project admins:

• mindblender: project admin, project architect, blog/forum admin, developer, community admin, forum moderator

development team: {tbd}

past team members:

• fullo project admin, project architect, blog/forum admin
• ceam
• sululdln: PHP developer
• pbworks(firepol): wiki/documentation publisher, quality control, bug triage

We need to publish a new release. It should be stable enough to be put in production environments. The Test cases page contains a checklists of functionalities to test before releasing rc4. 2.5-rc4 should be published in August. After getting feedback and correct bugs we should finally publish v2.5. Then we can go on implementing features and correcting bugs and I would recommend to make lots of releases, such as 2.5.1, 2.5.2 in order to avoid to let the project "die" (at least from the public perspective).