Re: Bugzilla for cfengine

[Christian Pearce]

Before we ask that.  How much existing infrastructure would remain in
Oslo?  Regardless:

* Web Server
- Web site
- Bug tracking
- Web based SVN viewer
* Mailing Lists
* SVN Repository
* Backups
* shell access for commiters

We still should have sourceforge to access the compile farms.  Unless we
can get that somewhere else.  This is very important for regression
testing.



On Wed, 2004-12-15 at 09:28, John Sechrest wrote:
> 
> It is certainly possible to create a foundation where we have
> as much or as little as we want at sourceforge and 
> then put the rest of the services on some other spot. 
> 
> It looks like you are suggesting that for the bug tracker that
> something like trac or bugzilla would be better than sourceforge (at
> some level). And that having an alternative hosting makes sense.
> 
> Let's turn the conversation around a bit. If we had a base configuration
> on a self hosted machine, what services would be on it? 
> 
> 
> 
> address@hidden (Kevin Campbell) writes:
> 
>  % On Tue, Dec 14, 2004 at 09:24:20AM -0800, John Sechrest wrote:
>  % > 
>  % >  Right now, I am focused on the mundane task of moving
>  % >  away from Savannah because it has become unreliable
>  % >  and because basic requests could not be satisified. 
>  % > 
>  % >  This does open up the door for more involvement in a wider audience
>  % >  using the site. Organizing bug reports, organizing material and
>  % >  opening up a mechanism for bug submissions, repairs and group   
>  % >  development make sense.
>  % 
>  % Trying to step back from the SVN vs CVS arguement here for the moment
>  % and get back to the bug tracker. At the moment, getting a bug tracking
>  % system up and running and having people insert details into it would be
>  % very helpful to myself, and many others who are using cfengine. There has 
>  % been a fair amount of momentum going on recently, and I'd like for this 
>  % to push on if possible.
>  % 
>  % I do have my reservations about sourceforge, both from my experience of
>  % trying to use it to view details on other projects, and from reports I
>  % hear from other developers of issues they have with it. From digging on
>  % google to try and find migration scripts to go from bugzilla to sf's 
>  % bugtracker, the general concensus is that people want to go the other 
>  % way round.
>  % 
>  % On that note, could we start using the current bug tracker just now and
>  % inserting bugs into it? I will happily migrate any bug information by hand
>  % if and when a bug tracker on sf is brought up and running. We may still
>  % find that sf's tracker isn't really up to scratch (or may find the same
>  % with bugzilla), so this also provides an alternative for that case.
>  % 
>  % -- 
>  % Kevin Campbell
>  % GPG key: 06CBB693
> 
> -----
> John Sechrest          .         Helping people use
>                         .           computers and the Internet
>                           .            more effectively
>                              .                      
>                                  .       Internet: address@hidden
>                                       .   
>                                               . http://www.peak.org/~sechrest
> 
> 
> _______________________________________________
> Bug-cfengine mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-cfengine
-- 
Christian Pearce
http://www.commnav.com
http://www.perfectorder.com