|
a/Allura/docs/faq.rst |
|
b/Allura/docs/faq.rst |
| 1 |
Why not improve existing tools like Trac, Redmine or Bugzilla?
|
1 |
Why not improve existing tools like Trac, Redmine or Bugzilla?
|
| 2 |
---------------------------------------------------------------------
|
2 |
---------------------------------------------------------------------
|
| 3 |
|
3 |
|
| 4 |
One word. Scalability.
|
4 |
One word. Scalability.
|
| 5 |
|
5 |
|
| 6 |
Ok, two words. Scalability and Performance
|
6 |
Ok, two words. Scalability and Performance
|
| 7 |
|
7 |
|
| 8 |
Ok, three words: Scalability, Performance, and Flexibility
|
8 |
Ok, three words: Scalability, Performance, and Flexibility
|
| 9 |
|
9 |
|
| 10 |
Seriously though, we didn't think that any of the existing systems have
|
10 |
Seriously though, we didn't think that any of the existing systems have
|
| 11 |
actually hit the right usability, scalability, or flexibility targets that
|
11 |
actually hit the right usability, scalability, or flexibility targets that
|
| 12 |
we needed to hit, and we knew that it would be a **lot** of work to get
|
12 |
we needed to hit, and we knew that it would be a **lot** of work to get
|
| 13 |
any of them to do what we needed.
|
13 |
any of them to do what we needed.
|
| 14 |
|
14 |
|
| 15 |
But we knew e-mail integration was going to be a big deal to our forge,
|
15 |
But we knew e-mail integration was going to be a big deal to our forge,
|
| 16 |
so we did take a long look at Roundup, which is a very well designed
|
16 |
so we did take a long look at Roundup, which is a very well designed
|
| 17 |
system build from the ground up around the idea of e-mail integration.
|
17 |
system build from the ground up around the idea of e-mail integration.
|
| 18 |
|
18 |
|
| 19 |
If you were so inspired by Roundup, why not just use it?
|
19 |
If you were so inspired by Roundup, why not just use it?
|
| 20 |
---------------------------------------------------------------------
|
20 |
---------------------------------------------------------------------
|
| 21 |
|
21 |
|
| 22 |
We liked the flexible schema system provided by Roundup's HyperTable layer,
|
22 |
We liked the flexible schema system provided by Roundup's HyperTable layer,
|
| 23 |
but thought that native MongoDB bindings were both cleaner, faster, and
|
23 |
but thought that native MongoDB bindings were both cleaner, faster, and
|
| 24 |
ultimately more powerful.
|
24 |
ultimately more powerful.
|
| 25 |
|
25 |
|
| 26 |
Sure we sacrifice the flexibility of Roundup's
|
26 |
Sure we sacrifice the flexibility of Roundup's
|
| 27 |
backend, but our main goal is to make usable, high performance system,
|
27 |
backend, but our main goal is to make usable, high performance system,
|
| 28 |
not to maximize the number of backend storages systems supported.
|
28 |
not to maximize the number of backend storages systems supported.
|
| 29 |
|
29 |
|
| 30 |
Why create all the apps as plugins?
|
30 |
Why create all the apps as plugins?
|
| 31 |
---------------------------------------------------------------------
|
31 |
---------------------------------------------------------------------
|
| 32 |
|
32 |
|
| 33 |
We know that some projects are going to want more locked down
|
33 |
We know that some projects are going to want more locked down
|
| 34 |
access controls in their bug trackers, or more workflow based
|
34 |
access controls in their bug trackers, or more workflow based
|
| 35 |
processes. These things are inevitable, and we really do want
|
35 |
processes. These things are inevitable, and we really do want
|
| 36 |
to support them, but at the same time they are going to conflict
|
36 |
to support them, but at the same time they are going to conflict
|
| 37 |
with the way many other projects want to work.
|
37 |
with the way many other projects want to work.
|
| 38 |
|
38 |
|
| 39 |
Building a plugin (tool in Allura terms) system, and standard
|
39 |
Building a plugin (tool in Allura terms) system, and standard
|
| 40 |
integration points makes it possible to serve everybody in one
|
40 |
integration points makes it possible to serve everybody in one
|
| 41 |
way or another.
|
41 |
way or another.
|
| 42 |
|
42 |
|
| 43 |
Why not just allow web-based extensions?
|
43 |
Why not just allow web-based extensions?
|
| 44 |
---------------------------------------------------------------------
|
44 |
---------------------------------------------------------------------
|
| 45 |
|
45 |
|
| 46 |
We talked about this quite a bit, and decided that we could write local
|
46 |
We talked about this quite a bit, and decided that we could write local
|
| 47 |
native tools more quickly and easily, and that we could build a
|
47 |
native tools more quickly and easily, and that we could build a
|
| 48 |
local app tool that proxied out to an external webapp, and that
|
48 |
local app tool that proxied out to an external webapp, and that
|
| 49 |
we could provide a lot more flexibility by allowing custom
|
49 |
we could provide a lot more flexibility by allowing custom
|
| 50 |
external webapp proxies -- which brought us right back to local
|
50 |
external webapp proxies -- which brought us right back to local
|
| 51 |
tools.
|
51 |
tools.
|
| 52 |
|
|
|
| 53 |
|
|
|
| 54 |
|
|
|