Current Status

From Linguistic Team International Wiki

Global Developers TeamAbout the Dev Team | GDT Environment Foundation | TZM 2.0/Phoenix Project | Projects Documentation | Contributors | Resources | Meetings| Wiki Use Help (edit)

TZM Redesign-The Phoenix ProjectProject AdminstrationCurrent StatusProject Personnel TableBrainstormingFinal technical specifics (edit)

This page is updated almost daily, with information on the project overall, latest event last. Project details will be recorded in the PM site.

— 19 October, 2011 (UTC)

--Boldhawk 01:22, 19 October 2011 (UTC)—This is the last update that will be posted here! As noted in the Project Introduction, this wiki now remains primarily a historical document. Join us at the site where we're conducting most of our work: Atrium.

Global Development Team information in this wiki is generally still valid. The Phoenix Project only has changed it's primary working location to the Atrium.

— 13 August 2011 (UTC)

--Boldhawk 13:25, 13 August 2011 (UTC)—Since the Atrium installation is now declared the collaborative space for the Phoenix Project, the Final Technical Specifications will be posted in the Atrium's Notebook.

— Phoenix Project Update—11 August 2011 (UTC)

Some issues were clarified and resolved concerning the current Atrium installation, and its status at the last Phoenix Project TS meeting. The current Installation ( shall be the 登fficial site�for two purposes:

  1. Project management site, where the development of programs, modules, and features will be tracked and discussed by concerned personnel. In this way, the work will be transparent, and people can watch progress on a blow by blow basis, and can contribute as appropriate on higher level decisions, as well as low level details.
  1. The live installation of chapter co-sites, teams co-sites, projects co-sites, members. This is one of the key elements of the Phoenix Project: One site reaches all; one sign on, reaches all. No matter where you log in, you can see and reach the entire global network. The implementation of this portion requires the participation of all stake holders, team, chapter Sys Admins, to register, and start developing methods of interface, which have already been presented, but may require one-to-one set ups.

Note: in item 1, projects refers to software project, modules, programs, scripts, etc. All cyber projects. In item 2, projects refers to everyday world activities, taking place in the physical environment, in the planet.

Progress Report:

Milestone Two, the final fleshing out of all components, is slightly delayed due server personnel overload with recent system crises, like TS installation, and other less visible problems, and personnel scheduled time reduction.

However, we appear to be on target to complete Milestone Two, Final Technical Specification. You can review the documentation here: We may still meet this milestone, though, if we can complete the second part of the document therein presented.

The Up Side:

We have resolved various critical issues which are part of future third and fifth milestones: Collaborative space, and underlying systems. For details you can log into the Atrium site and read any of many posts under the Phoenix Project cases, blogs, and notes.

The down side:

It has been difficult contacting the more than1100 system admin's from all the chapters, and other concerned at large developers. We get word from all corners of the world congratulating our efforts (people we meet in TS).

The smallest, least difficult action you can take is to forward this call to anyone whom you think needs or wants to know, or has the ability to contribute.

Needed: system administrators, coordinating managers and administrators, programmers, developers, designers, documentation experts. When: NOW!

— 22 July 2011 (UTC)

Boldhawk, 22 July 2011 (UTC)

—I spent most of the week making personal contacts with different chapters. I have a couple of people going to chapter web sites talking to people about the Phoenix project. I spent the week pretty much dealing one to one with about eight people wanting information and understanding on the project, which resulted in people joining whether as chapter or developers, or just to find ways to help.

Pete was under the weather, so I didn't get to talk to him. Right before that he had completed a couple of training clips for developers and trainees. Dave is actively handling the case information and getting developers settled in the Atrium, and answering questions, and supervising tasks or "cases."

All communication around the TZM about Phoenix has been positive and encouraging, and it confirms that chapters, teams and users do need the project to succeed.

I do think the project is a test of the potential success of the TZM, as if we can't find ways to work together, despite wide cultural differences, and at time ideological variations, we cant make it. The up side is that I've seen conflicts resolve here much easier and faster than I've seen before in many progressive project in the last 40 years.

The project will get easier as we fill the functions needed to bring it around. I have someone who has been working on a Z-Bank or Resource bank, and maybe we'll have a module to show in the next week or two.

— 13 July 2011 (UTC)

Boldhawk 04:01, 13 July 2011 (UTC)

—Reviewing Atrium and comparing to wiki as a collaborative site. The more I learn about it, the more it becomes apparent that for general users, they are likely to participate in the Atrium features a lot easier than making wiki posts. I'm beginning to move the actions items to the Atrium.

--Boldhawk 04:01, 13 July 2011 (UTC)—Yesterday, sent a notice to signed up volunteers giving general working guidelines.

--Boldhawk 12:36, 10 July 2011 (UTC)—This past week I've been studying organizational issues related to the Atrium site set up to manage the Phoenix project. Also have been researching Integration software, and other CMS. Hope to discuss at meeting tonight.

--Boldhawk 12:59, 4 July 2011 (UTC)—I started posting in the Atrium site to manage some of the task of the Final Technical Definition portion of the Phoenix Project. David Zwolski is in Charge of that section, and it looks like the area is beginning to show some organization.

— 4 July 2011 (UTC)

—Pete sent out a memo about the training set up for developers.

--Boldhawk 08:38, 3 July 2011 (UTC)—Discussion on technical definitions has been opened in the Atrium site for various technical reasons, part of which is to consolidate mailing lists and mailing requirements to members, as well as easy of discussion management. Atrium Developers' site

--Boldhawk 08:38, 2 July 2011 (UTC)— Examination of Requirements in the brainstorming, suggest we need to study Web Integration Software, and Content Management software.

--Boldhawk 08:38, 2 July 2011 (UTC)—Dave Zwolski takes over Programmers to organize the web page building.

--Boldhawk 08:34, 30 June 2011 (UTC) Milestone One, Project Definition, completed.