|
a/pyforge/docs/faq.rst |
|
b/pyforge/docs/faq.rst |
|
... |
|
... |
| 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 tools?
|
| 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 system, and standard integration points
|
39 |
Building a tool system, and standard integration points
|
| 40 |
makes it possible to serve everybody in one way or another.
|
40 |
makes it possible to serve everybody in one way or another.
|
| 41 |
|
41 |
|
| 42 |
Why not just allow web-based extensions?
|
42 |
Why not just allow web-based extensions?
|
| 43 |
---------------------------------------------------------------------
|
43 |
---------------------------------------------------------------------
|
| 44 |
|
44 |
|
| 45 |
We talked about this quite a bit, and decided that we could write local
|
45 |
We talked about this quite a bit, and decided that we could write local
|
| 46 |
native plugins more quickly and easily, and that we could build a
|
46 |
native tools more quickly and easily, and that we could build a
|
| 47 |
local app plugin that proxied out to an external webapp, and that
|
47 |
local app tool that proxied out to an external webapp, and that
|
| 48 |
we could provide a lot more flexibility by allowing custom
|
48 |
we could provide a lot more flexibility by allowing custom
|
| 49 |
external webapp proxies -- which brought us right back to local
|
49 |
external webapp proxies -- which brought us right back to local
|
| 50 |
plugins.
|
50 |
tools.
|
| 51 |
|
51 |
|
| 52 |
|
52 |
|
| 53 |
--------------------------------------------------------------------- |
53 |
--------------------------------------------------------------------- |