Page "Proposals/BEP-0003" was added by olemis
Comment: BEP-0003 : Initial draft including **brief** abstract , motivation and 
reference implementation
Content:
-------8<------8<------8<------8<------8<------8<------8<------8<--------

= BEP 3 : Multi-product architecture #overview

[[PageOutline]]

|| '''PEP''' || 3 ||
|| '''Title''' || Multi-product architecture ||
|| '''Version''' ||  ||
|| '''Last-Modified''' ||  ||
|| '''Author''' || The Bloodhound project ||
|| '''Status''' || Draft ||
|| '''Type''' || Standards Track ||
|| '''Content-Type''' || [wiki:PageTemplates/Proposals text/x-trac-wiki] ||
|| '''Created''' ||  ||
|| '''Post-History''' ||  ||

----

== Abstract #abstract

The evolution on the field of issue tracking systems leads to many request for 
supporting multiple products in a single environment. This document is meant to 
gather community consensus on the implementation of this feature . Besides it 
is a starting point to envision the impact on the underlying components 
architecture and the corresponding development strategies to get everything 
done. Ultimately it will explore compatibility considerations for existing 
plugins and suggest recommended upgrade paths so that hacks authors will take 
advantage of this feature .

== Motivation ==

Nowadays it is possible to manage multiple projects by creating multiple 
environments. As a consequence data is scattered across multiple databases and 
maintenance tasks turn out to be more difficult. Since a long time users have 
expessed the need for managing multiple ''projects'' in an easy way . In the 
case of a family of related products it is usually important to have a unified 
view on the development activity as well as the ability to share common 
resources among them. Under those circumstances it is convenient to manage 
multiple products within a single ''Trac'' environment.

The term ''project'' is very generic and may be confusing considering the 
context. Therefore in this specification the word ''product'' is used instead . 

== Proposal #proposal

'''TODO'''

== Rationale #rationale

'''TODO'''

== Backwards Compatibility #backwards-compatibility

'''TODO'''

== Reference Implementation #reference-implementation

Multi-product plugin is under active development by the ''Bloodhound'' 
community. It is possible to check out 
[https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/bloodhound_multiproduct/
 the source] using [http://subversion.apache.org/ Apache™ Subversion] by 
executing the following command

{{{
#!sh

$ svn co 
https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/bloodhound_multiproduct

}}}

== Resources #resources

Source code management is powered by [http://subversion.apache.org/ Apache™ 
Subversion].

== References #references

  1. Multi-project support (trac:ticket:130)
  2. Multiple Projects within a Single Trac Environment
     (trac:wiki:TracMultipleProjects/SingleEnvironment)

== Copyright #copyright

Copyright © 2009-2012 The [http://www.apache.org Apache Software Foundation] 
[[BR]] 
Licensed under the [http://www.apache.org/licenses/LICENSE-2.0 Apache License, 
Version 2.0].

Apache Bloodhound, Apache, the Apache feather logo, and the Apache Bloodhound 
project logo are trademarks of The Apache Software Foundation.

-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0003>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0003' page.
If it was not you, please report to .

Reply via email to