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)

Section Suspended.

This Scope of Work section began shortly before the Phoenix Project was initiated as an attempt to set up some structure to the Global Development Team. However, at the advent of the Phoenix Project, this section is suspended, and maybe reinstated or or the structure of the Phoenix Project will become the structure that will be used for the Global Dev. Team.


--Boldhawk 11:30, 27 May 2011 (UTC) :

The IT folks, developers, programmers, and their managers are the Gate Keepers of the 21st Century. Before I suggest a code of conduct, let's look at the potential social impact of what an Internet company can do to shape the mind of a culture:

Let's take Google. This brief video in TED, which looks at how Google controls the results people get when using their search engine.

Filter Bubbles

When you control the distribution of information based on some 50+ criteria, many of which are based on commercial reasons or social or political reasons, the intent becomes clear, and your responsibility becomes a Damocles' sword ready to smite you for whatever reasons, but you hold the power in your hands.

So, as modern Gate Keepers, your main responsibilities lie in not only keeping the gates open, but making it easier for everyone to have unfettered access to knowledge. Keep the Gate Keeper's Code.

Areas of Work

The list below attempts to divide different areas of work for a master global scope of work.


The page does not yet have content. It will have information on the administrative structure for the development team, indicating who is in charge of what, and such other appropriate information concerning administration.

Technical Areas

This section should breakdown into technical components, such as "back end," "server type and name," General structure underlying the application the users will see. It is yet to be defined/broken down. One of you modern IT guys who understand the various layers as they are done at this level of technology, may want to help define this section.

Developers Side—Collaborative_Content_Management_Systems

The organization of a project normally starts with the organization of the communication between developers, project managers, and systems and software designers. Currently the conversation about collaborative space has been conducted at the Global Developer's GG site. Developers are encouraged to bring the discussion here.

In these page(s) (Title is the link) a tentative breakdown of collaborative points to be considered have been started. You're welcome to participate in creating the necessary documentation to support whatever your system preference is. This point is set first, as it is akin to find a building or a home where to run an operation or business! --Boldhawk 08:23, 27 May 2011 (UTC)

Server Side

Server software

(Apache, Unix, Solaris, etc.)  

Support languages

(PHP, Python, etc.) 

Server-side apps

(Pootle, Drupal, Joomla, custom, etc.)

Modules, Plugins & Addons for those apps.

Mailing system: | Open Source: Mailman

Client Side


Support dependencies



Users Side—User's Needs and wishes

Users will be asked to present their needs in terms of functionalities, for their interfaces, so the requirements are included in the scope of work.

Undivided tasks-Ling. Team

| Ling Team Development

These are Ling. Team items which are being tracked from the Ling Team Wiki; included here for reference.--Boldhawk 05:52, 30 May 2011 (UTC)