Other persons involved before:
Project was initially managed in Redmine hosted by Activeark. Redmine's issue tracking was replaced with MeeGo's Bugzilla at http://bugs.meego.com. In Bugzilla, site bugs are categorized under product "developer.meego.com".
Drupal source is managed by using GIT. *Source code is public and should be available at Gitorious*. See link for the repository: http://meego.gitorious.org/meego-web-infrastructure/meego-developer-website
Michael R. Shaver from Intel is responsible for hosting. There is plans to move hosting at Oregon State University (OSU), the status can be followed in bug #12683.
Production and staging environment
Production and staging environment are in the same server. No passwords are used, instead we are using SSH public keys which should be provided to Michael when server access is needed.
Production site is mapped to document root " /home/developer.meego.com/www/developer.meego.com " and uses " dev_meego " database/name. Folder is linked to repository and should contain latest stable snapshot of site.
Staging site is mapped to document root " /home/developer.meego.com/www/dev.developer.meego.com " and uses " dev_dev_mego " database/name. Folder is linked to repository and has latest state of the site.
No centralized development environment provided. Development happens locally.
Intel is currently responsible of hosting. The contact person for hosting is *Michael R. Shaver* from Intel.
Site uses Drupal's default structure, collation, storage engine.
Staging site is not using shared tables.
Production site is using following database settings:
$db_prefix = array( 'default' => '', 'users' => 'meego.', 'authmap' => 'meego.', 'openid_associations' => 'meego.', 'profile_fields' => 'meego.', 'profile_values' => 'meego.', );
Note! When synchronizing content from production site, you will be required to set node.uid to value 1 and clear cache to ensure availability of content. Nodes doesn't get loaded when user is not available (uids are different in production since we're sharing users table!).
Site is using Drupal's distribution *Pressflow* , because of better performance. Project uses PHPTemplate as template engine.
Contributed modules are located in @./sites/all/modules/contrib@. Custom modules are located in @./sites/all/modules/custom@. Modified contributed modules are located in @./sites/all/modules/modified-contrib@.
Most of custom modules are generated by Features module, but they might contain also alternative code in .module files made by developers.
Site is using external search indexing from Acquia Network which provides apache solr search index.
> Contains two node types "guide" and "guide_external" and big set of CCK fields and module dependencies. Generated by features and added some alternative implementation for making a redirect for external guides + view lists for guides.
> Has node type "note" and few views lists. Generated by features.
> Contains variable settings related to Apache Solr search. Generated by features and contains alternative implementation related to search.
> Contains node types "promo", "section_head" and "section_head_view" and large amount of CCK fields and couple views lists. Generated by features.
h2. Contributed modules
> Features, context and strongarm is used for tracking site structure by code. This makes site structure more easy to change structure between different environments.
> Acquia network is used to provide Apache Solr search indexing
> Book and BookMadeSimple modules are used for keeping guide menu structure separated from other menu links (primary links).
> Feeds is needed to import planet and blog entries from RSS feed
> Used to provide colored code formatting in code snippets in node bodies
> Installed for allowing users to add YouTube videos to guides. However, Video Filter is used to add videos into content.
> Installed to allow content editors edit keywords and description of page.
> To prevent user being logged in automatically.
> BUEditor is used instead of WYSIWYG editors because it's a simple way format text without messing up the HTML code by WYSIWYG editors
> Allows content editors to clone node content.
> Installed to allow users see differences between two versions of content.
> provides basic cleanup of urls - redirection of alternative aliases, removal of trailing slashes, forces access via clean urls...
> Used to put images into node bodies
> Required by feeds for the import of community information, such as blogs / planet
> LESS makes CSS styling more easy by allowing several dynamic features. See more information from http://lesscss.org
> Generates dynamically first level of links under guides section. This block is used in footer.
> Makes links to main menu which actually links to first child page.
> Makes guides and api pages to look like they would be in guide category or reference api sections even if they're not added into menu at all.
> Nice Menus is used for main menu which hovers 1st level links and displays 2nd level links below.
> Allows content to be added by less skilled writers which can be hidden, after edit set to public.
> Automatically replaces and references in node content fields to the development / staging servers with the live server url.
> Makes easier to embed YouTube videos inside content.
> _I believe this is unused, was going to be tested for import of forums - andb_
> Tracks the popularity of guides to promote popular content in guides sections.
> A cleaner, easier to use interface for adding tags to nodes
> Makes external links to be opened in new window and adds an external link icon to indicate link being external.
> Makes guides to be voted so content editors knows which guides are helping application developers.