Re: [mbravo@tag-ltd.spb.ru: Re: [phpBT-dev] Postgres SQL problems]

[Ben C. <php...@be...>]

Man, I've been too busy at work doing work to do the bug tracker. :)  

On Thu, Aug 23, 2001 at 02:19:31PM -0700, Ben Curtis wrote:
> Forwarding to the list... :)
> 
> ----- Forwarded message from Michael Bravo <mb...@ta...> -----
> 
> From: Michael Bravo <mb...@ta...>
> To: Ben Curtis <php...@be...>
> Subject: Re: [phpBT-dev] Postgres SQL problems
> Organization: TAG Ltd
> 
> On Thu, 23 Aug 2001 13:40:31 -0700
> Ben Curtis <php...@be...> wrote:
> 
> > I'll also do some thinking on how I want to link users to projects, so
> > this will help your desire, Michael to get the group restrictions going.
> 
> Yeah, we can introduce the generic user-group model and link groups to projects, or we can skip the generic groups and do a somewhat custom user-vs-project thing.

I was thinking about this... that would allow groups based on projects, and also groups based on other things such as access level or even department.  Hmm, I wonder just how flexible we can get before adminning it becomes a burden.

> 
> What I am thinking about is how do we combine the ability of users to self-register and the user-vs-project restrictions. It seems we will have to give bugtracker admin a choice of either running an open bugtracking system, a closed bugtracking system (i.e. disable self-registration capability altogether), or a combined one. In the latter case we will have to support an explicit marking of a project as publicly accessible.
> 

Yeah, if you take a look at bugzilla, each project (or product) can be toggled on whether only members belonging to the project's group can see it.

> Personally, I think the combined case is a little farfetched and mightn't be needed in real life cases. I mean, you are either running an internal bugtracker with your customers coming from outside and restricted to specific projects, or you are running an open source project and do not actually care about any such restrictions. What do you think?

Well, I would agree, had I not had the following experience... I wanted to use phpBB (forum software) but not the cruddy old 1.4.x version, but the yet-to-be-released-and-very-alpha version 2.  So, I started hacking away on it to get it to a working level (I didn't need all the functionality -- luckily I just needed the stuff that had been done to that point).  But, as I was working on the integration, I found bugs and attempted to submit them via their sourceforge bug tracker.  These were promptly closed with a comment like "v2 is still under development -- no bug reports on it please".  So, in this case, having a publicly available tracker for a stable version and another tracker restricted for just dev staff might be useful.  Of course, in this case, they probably _do_ have some way to track bugs on their v2, but it might be nice to have that flexibility in phpbt.  Thoughts?