decentralization

Jason Pyeron jason at pyeron.com
Fri May 9 23:14:59 UTC 2003


I really think that this is a good point.

as to the project issue:

 bug 42 at bugzilla.mozilla.org

this way a domain name can serve as a authoritative project identifier. 
This should prevent collisions. this is kinda link sun's java package naming 
rules.

On 9 May 2003, C.J. Collier wrote:

>bugzilla would do well to decentralize.  Each bugzilla server should
>communicate with others.  Bug reports should be shared between projects.
>
>For example, on bugs.debian.org bug #189211 depends on the resolution of
>bug #97177 on bugzilla.gnome.org.  There is no way to have one depend on
>the other, so it is not easy to tell when the bug is resolved.  Taking a
>look at #189211 (bugs.debian.org) will show you a bit about the unhappy
>mess this causes.
>
>My suggestion would be to use URIs to reference bugs.  Perhaps something
>like the following:
>
>bugzilla://bugs.debian.org/?project=gnome-theme-manager&bugnumber=N
>
>"bugnumber" would be gnome-theme-manager (on bugs.debian.org) specific. 
>Global variables are bad.  I suggest some type of scoping, even if it
>doesn't follow my suggestion exactly.
>
>This would allow projects that use bugzilla to co-ordinate with the
>projects that they depend on without being on the same server.
>
>Thoughts?
>
>C.J.
>
>
>----
>To view or change your list settings, click here:
><http://bugzilla.org/cgi-bin/mj_wwwusr?user=jpyeron@pyerotechnics.com>
>

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
-                                                               -
- Jason Pyeron                   http://www.pyerotechnics.com   -
- Owner & Lead                  Pyerotechnics Development, Inc. -
- +1 410 808 6646 (c)           500 West University Parkway #1S -
- +1 410 467 2266 (f)           Baltimore, Maryland  21210-3253 -
-                                                               -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and 
notify the sender immediately.  Any other use of the email by you 
is prohibited.






More information about the developers mailing list