natalie/indefero
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
4323edcf0c
indefero/src/IDF/relations.php

124 lines
6.0 KiB
PHP
Raw Normal View History

Initial commit.
2008-07-25 08:26:05 +00:00
<?php
/* -*- tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
/*
# ***** BEGIN LICENSE BLOCK *****
# This file is part of InDefero, an open source project management application.
Update copyrigt
2011-04-02 19:37:07 +00:00
# Copyright (C) 2008-2011 Céondo Ltd and contributors.
Initial commit.
2008-07-25 08:26:05 +00:00
#
Correctly set the copyrights.
2008-07-25 08:28:35 +00:00
# InDefero is free software; you can redistribute it and/or modify
Initial commit.
2008-07-25 08:26:05 +00:00
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
Correctly set the copyrights.
2008-07-25 08:28:35 +00:00
# InDefero is distributed in the hope that it will be useful,
Initial commit.
2008-07-25 08:26:05 +00:00
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
#
# ***** END LICENSE BLOCK ***** */
$m = array();
Implement a basic, configurable project activity taxonomy.
2011-12-23 00:03:07 +00:00
$m['IDF_ProjectActivity'] = array('relate_to' => array('IDF_Project'));
Add a relation between IDF_Project and IDF_Tag (again), this time its a many-to-many. We store project tags in IDF_Tag with a project id "0" (this has minimal to no impact on existing code) and therefor only need to ensure that the new relation table exists in the migration. Then just the project summary configuration and the admin's project create and project update forms and views needed to be adapted to be able to render, create and update project tags.
2011-12-11 00:38:56 +00:00
$m['IDF_Tag'] = array('relate_to' => array('IDF_Project'),
'relate_to_many' => array('IDF_Project'));
Initial commit.
2008-07-25 08:26:05 +00:00
$m['IDF_Issue'] = array('relate_to' => array('IDF_Project', 'Pluf_User', 'IDF_Tag'),
'relate_to_many' => array('IDF_Tag', 'Pluf_User'));
$m['IDF_IssueComment'] = array('relate_to' => array('IDF_Issue', 'Pluf_User'));
Fixed ticket 36, attach a file to a ticket. It is now possible to attach a file to a ticket.
2008-11-12 19:40:58 +00:00
$m['IDF_IssueFile'] = array('relate_to' => array('IDF_IssueComment', 'Pluf_User'));
Fixed issue 8, show the featured downloads on the homepage.
2008-08-05 18:33:43 +00:00
$m['IDF_Upload'] = array('relate_to' => array('IDF_Project', 'Pluf_User'),
'relate_to_many' => array('IDF_Tag'));
Added a search engine in the issues.
2008-08-13 16:26:36 +00:00
$m['IDF_Search_Occ'] = array('relate_to' => array('IDF_Project'),);
Move the Wiki* models into the IDF_Wiki_* namespace and adapt all models, table names and relations accordingly. Start with a resource and resource revision model and add migrations for that as well. Note in NEWS.mdtext that we need a more recent Pluf version to take advantage of the MySQL introspection implementation.
2011-11-06 00:05:27 +00:00
$m['IDF_Wiki_Page'] = array('relate_to' => array('IDF_Project', 'Pluf_User'),
'relate_to_many' => array('IDF_Tag', 'Pluf_User'));
$m['IDF_Wiki_PageRevision'] = array('relate_to' => array('IDF_Wiki_Page', 'Pluf_User'));
$m['IDF_Wiki_Resource'] = array('relate_to' => array('IDF_Project', 'Pluf_User'));
$m['IDF_Wiki_ResourceRevision'] = array('relate_to' => array('IDF_Wiki_Resource', 'Pluf_User'),
'relate_to_many' => array('IDF_PageRevision', 'Pluf_User'));
Started ticket 39, add code review. We now have a limited support of the code review. Still some work to be done to allow the submission of new patches on a given review and update the status. For the moment, only pre-commit review is supported.
2008-11-30 09:26:05 +00:00
$m['IDF_Review'] = array('relate_to' => array('IDF_Project', 'Pluf_User', 'IDF_Tag'),
'relate_to_many' => array('IDF_Tag', 'Pluf_User'));
$m['IDF_Review_Patch'] = array('relate_to' => array('IDF_Review', 'Pluf_User'));
Fixed the review backend to support multiple patches per review and line level comments.
2009-07-16 08:04:58 +00:00
$m['IDF_Review_Comment'] = array('relate_to' => array('IDF_Review_Patch', 'Pluf_User'));
$m['IDF_Review_FileComment'] = array('relate_to' => array('IDF_Review_Comment', 'Pluf_User'));
Added the upload of the SSH key for the end user.
2009-01-14 22:05:52 +00:00
$m['IDF_Key'] = array('relate_to' => array('Pluf_User'));
Added the IDF_Conf relation.
2009-01-24 09:07:33 +00:00
$m['IDF_Conf'] = array('relate_to' => array('IDF_Project'));
Added the relations of the IDF_Commit model.
2009-02-16 10:55:14 +00:00
$m['IDF_Commit'] = array('relate_to' => array('IDF_Project', 'Pluf_User'));
Continued the SCM backend refactor. The new backend is near completion.
2009-04-25 14:24:40 +00:00
$m['IDF_Scm_Cache_Git'] = array('relate_to' => array('IDF_Project'));
Updated the plugin to match InDefero's coding standards.
2008-12-03 22:02:59 +00:00
Implemented an extended user profile based on a patch from Jethro Carr (issue 510). Changes with respect to the original patch: - use Gconf instead of separate table / data scheme - better form validation for URLs and emails - no htmlentity-encoded contents in the database (pluf automatically safe-encodes stuff before it writes out contents into templates) - add visual separators in the form views to have a distinct view of basic (important) data and other data which are only displayed in the public profile - give a hint about the maximum display size of 60x60 px^2 and use max-width and max-height in the templates to avoid nasty distortions by the browser - use target=_blank and rel=nofollow on the twitter and website links in the profile - some whitespace / formatting / code style fixes
2010-12-05 00:22:32 +00:00
$m['IDF_UserData'] = array('relate_to' => array('Pluf_User'));
Store secondary email addresses. Create a place to store additional email addresses and provide an API to access them
2011-02-09 12:19:16 +00:00
$m['IDF_EmailAddress'] = array('relate_to' => array('Pluf_User'));
Basic model files added.
2011-05-10 15:22:32 +00:00
$m['IDF_IssueRelation'] = array('relate_to' => array('IDF_Issue', 'Pluf_User'));
Implemented an extended user profile based on a patch from Jethro Carr (issue 510). Changes with respect to the original patch: - use Gconf instead of separate table / data scheme - better form validation for URLs and emails - no htmlentity-encoded contents in the database (pluf automatically safe-encodes stuff before it writes out contents into templates) - add visual separators in the form views to have a distinct view of basic (important) data and other data which are only displayed in the public profile - give a hint about the maximum display size of 60x60 px^2 and use max-width and max-height in the templates to avoid nasty distortions by the browser - use target=_blank and rel=nofollow on the twitter and website links in the profile - some whitespace / formatting / code style fixes
2010-12-05 00:22:32 +00:00
Updated to simplify the configuration. We do not need to have the extra tags and modifiers in the configuration as a signal is taking care of that. That way we can add new tags, modifiers without the need to update the configuration settings.
2008-12-05 10:53:22 +00:00
Pluf_Signal::connect('Pluf_Template_Compiler::construct_template_tags_modifiers',
array('IDF_Middleware', 'updateTemplateTagsModifiers'));
Updated the plugin to match InDefero's coding standards.
2008-12-03 22:02:59 +00:00
# -- Standard plugins, they will run only if configured --
#
# Subversion synchronization
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::membershipsUpdated',
Updated the plugin to match InDefero's coding standards.
2008-12-03 22:02:59 +00:00
array('IDF_Plugin_SyncSvn', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::created',
Updated the plugin to match InDefero's coding standards.
2008-12-03 22:02:59 +00:00
array('IDF_Plugin_SyncSvn', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('Pluf_User::passwordUpdated',
Updated the plugin to match InDefero's coding standards.
2008-12-03 22:02:59 +00:00
array('IDF_Plugin_SyncSvn', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::preDelete',
Added the possible deletion of the repository when deleting a subversion project.
2009-06-25 19:37:46 +00:00
array('IDF_Plugin_SyncSvn', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('svnpostcommit.php::run',
Added the subversion post commit hook.
2010-04-15 08:00:05 +00:00
array('IDF_Plugin_SyncSvn', 'entry'));
Added the Mercurial repository serving synchronization. This fixes ticket 79.
2008-12-08 08:56:31 +00:00
#
# Mercurial synchronization
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::membershipsUpdated',
Added the Mercurial repository serving synchronization. This fixes ticket 79.
2008-12-08 08:56:31 +00:00
array('IDF_Plugin_SyncMercurial', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::created',
Added the Mercurial repository serving synchronization. This fixes ticket 79.
2008-12-08 08:56:31 +00:00
array('IDF_Plugin_SyncMercurial', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('Pluf_User::passwordUpdated',
Added the Mercurial repository serving synchronization. This fixes ticket 79.
2008-12-08 08:56:31 +00:00
array('IDF_Plugin_SyncMercurial', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('hgchangegroup.php::run',
Added the Mercurial hook connection to run on groupchange.
2010-04-19 07:14:29 +00:00
array('IDF_Plugin_SyncMercurial', 'entry'));
Added the latest elements of the git repositories control. Now, need to write the documentation.
2009-01-20 09:33:56 +00:00
#
# Git synchronization
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::membershipsUpdated',
Fixed to correctly update the git daemon export flag as needed.
2009-01-20 16:31:55 +00:00
array('IDF_Plugin_SyncGit', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Key::postSave',
Added the latest elements of the git repositories control. Now, need to write the documentation.
2009-01-20 09:33:56 +00:00
array('IDF_Plugin_SyncGit', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Project::created',
Automatically create the git repository during the cron run.
2009-01-21 19:05:03 +00:00
array('IDF_Plugin_SyncGit', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Key::preDelete',
Added ticket 165, multiple SSH keys per user.
2010-02-22 21:27:31 +00:00
array('IDF_Plugin_SyncGit', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('gitpostupdate.php::run',
Added the subversion post commit hook.
2010-04-15 08:00:05 +00:00
array('IDF_Plugin_SyncGit', 'entry'));
Added the webhooks.
2010-05-10 08:11:27 +00:00
#
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
# monotone synchronization
Pluf_Signal::connect('IDF_Project::created',
array('IDF_Plugin_SyncMonotone', 'entry'));
* update the permissions on IDF_Project::membershipsUpdated - listen to the same signal also for the initial setup, since the memberships haven't been added at the time the create signal is thrown * my array references goo was slightly stupid (the usage of foreach is of course hazardous in cases like this) * always insert a trailing new line in write-permissions and skip read-in newlines from being processed
2010-09-14 22:30:28 +00:00
Pluf_Signal::connect('IDF_Project::membershipsUpdated',
array('IDF_Plugin_SyncMonotone', 'entry'));
* configure whether or not to set remote client authentication for IDF -> remote_stdio * hook into IDF_Project::preDelete, IDF_Key::postSave and IDF_Key::preDelete * this is all not quite finished, but a big leap forward to completion
2010-09-13 00:53:24 +00:00
Pluf_Signal::connect('IDF_Project::preDelete',
array('IDF_Plugin_SyncMonotone', 'entry'));
Pluf_Signal::connect('IDF_Key::postSave',
array('IDF_Plugin_SyncMonotone', 'entry'));
Pluf_Signal::connect('IDF_Key::preDelete',
array('IDF_Plugin_SyncMonotone', 'entry'));
The signal name was wrong, therefor mtn syncs never updated the IDF timeline.
2010-10-14 19:26:09 +00:00
Pluf_Signal::connect('mtnpostpush.php::run',
- initial work on a mtn-post-push script which updates IDF's timeline when new revisions arrive. this still needs some more tests, but its a start. - refactor out the monotonerc template from SyncMonotone.php and place it in a separate template file (access control hooks are still missing from there)
2010-08-30 11:20:47 +00:00
array('IDF_Plugin_SyncMonotone', 'entry'));
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
#
Added the webhooks.
2010-05-10 08:11:27 +00:00
# -- Processing of the webhook queue --
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('queuecron.php::run',
Added the webhooks.
2010-05-10 08:11:27 +00:00
array('IDF_Queue', 'process'));
Added the latest elements of the git repositories control. Now, need to write the documentation.
2009-01-20 09:33:56 +00:00
Added the webhooks.
2010-05-10 08:11:27 +00:00
#
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
# Processing of a given webhook, the hook can be configured
# directly in the configuration file if a different solution
Added the webhooks.
2010-05-10 08:11:27 +00:00
# is required.
First attempt on a monotone plugin which creates a new database upon project creation and adds the new server to the running usher instance. If everything goes well, the usher instance is told to reload its configuration, so the new server / database is picked up and started automatically.
2010-08-28 23:10:08 +00:00
Pluf_Signal::connect('IDF_Queue::processItem',
Pluf::f('idf_hook_process_item',
Added the webhooks.
2010-05-10 08:11:27 +00:00
array('IDF_Webhook', 'process')));
Initial commit.
2008-07-25 08:26:05 +00:00
return $m;
Reference in New Issue Copy Permalink