xmlroff-list

[xmlroff] What's next for xmlroff?

[Tony G. <Ton...@Me...>]

I have it in mind to move xmlroff off CVS on SourceForge to a
Subversion repository hosted on xmlroff.org (which would also move off
SourceForge's servers).

I would then choose to use Trac (http://trac.edgewall.com/) for the
new xmlroff website, ticket tracking system, and repository browser.

I have been using Trac for a while now and I quite like it, but what
do you people think?

Regards,


Tony.

Re: [xmlroff] What's next for xmlroff?

[Noah S. <ns...@gm...>]

Tony,

> I have been using Trac for a while now and I quite like it, but what
> do you people think?

Trac is an excellent choice. I have been using it for 2 years now both
professionally and personally. It makes the perfect compliment to
Subversion or SVK.

Noah

Re: [xmlroff] What's next for xmlroff?

[Stefan S. <se...@sy...>]

Tony Graham wrote:
> I have it in mind to move xmlroff off CVS on SourceForge to a
> Subversion repository hosted on xmlroff.org (which would also move off
> SourceForge's servers).

Do you already have a host for xmlroff.org ?

> I would then choose to use Trac (http://trac.edgewall.com/) for the
> new xmlroff website, ticket tracking system, and repository browser.
> 
> I have been using Trac for a while now and I quite like it, but what
> do you people think?

I haven't really used Trac myself, yet. I'v only looked at it quickly
when comparing features to other trackers (such as roundup).

If you are comfortable, you should use it. You are the main person who
will be affected by it.

Thanks,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...

Re: [xmlroff] What's next for xmlroff?

[Tony G. <Ton...@Me...>]

On Thu, Feb 01 2007 16:57:49 +0000, Stefan Seefeld wrote:
> Tony Graham wrote:
>> I have it in mind to move xmlroff off CVS on SourceForge to a
>> Subversion repository hosted on xmlroff.org (which would also move off
>> SourceForge's servers).
>
> Do you already have a host for xmlroff.org ?

I registered the hostname several years ago on some anniversary of
Sun's open-sourcing of xmlroff and then doing nothing with it.

www.xmlroff.org is currently aliased to SourceForge
vhost.sourceforge.net, so http://xmlroff.org is currently served from
the SourceForge project's htdocs directory.

I now have other webhosting that allows hosting multiple domains for
no extra charge, so I am better placed than ever before to be able to
host xmlroff.org off SourceForge.

One more change would probably be to also move xmlroff-list off
SourceForge and on to xmlroff.org.

>> I would then choose to use Trac (http://trac.edgewall.com/) for the
>> new xmlroff website, ticket tracking system, and repository browser.
>> 
>> I have been using Trac for a while now and I quite like it, but what
>> do you people think?
>
> I haven't really used Trac myself, yet. I'v only looked at it quickly
> when comparing features to other trackers (such as roundup).

Trac does more than just issue tracking.  I would also expect that the
way that you can link between tickets and both the wiki pages and the
Subversion revisions and changesets would mean that bug reports would
receive more attention than they have been receiving.

> If you are comfortable, you should use it. You are the main person who
> will be affected by it.

That is true, but while it is true, it's not necessarily the best
possible arrangement.

And if I did all major changes without signalling them or inviting
comment, then I could soon be the only person affected by them.

Talking about it beforehand also gives people a chance to chime in
with alternative, and possibly better, solutions.

Regards,


Tony.

Re: [xmlroff] What's next for xmlroff?

[Stefan S. <se...@sy...>]

Tony Graham wrote:

> I now have other webhosting that allows hosting multiple domains for
> no extra charge, so I am better placed than ever before to be able to
> host xmlroff.org off SourceForge.

Sounds good.

> One more change would probably be to also move xmlroff-list off
> SourceForge and on to xmlroff.org.

Yes, please ! :-)
(sf.net's list archive interface is really bad.)

>>> I have been using Trac for a while now and I quite like it, but what
>>> do you people think?
>> I haven't really used Trac myself, yet. I'v only looked at it quickly
>> when comparing features to other trackers (such as roundup).
> 
> Trac does more than just issue tracking.  I would also expect that the
> way that you can link between tickets and both the wiki pages and the
> Subversion revisions and changesets would mean that bug reports would
> receive more attention than they have been receiving.

Right.

>> If you are comfortable, you should use it. You are the main person who
>> will be affected by it.
> 
> That is true, but while it is true, it's not necessarily the best
> possible arrangement.
> 
> And if I did all major changes without signalling them or inviting
> comment, then I could soon be the only person affected by them.

Ah well. Don't be too afraid, though. With sf.net the expectations are
pretty low, so almost anything will be a win. ;-)

> Talking about it beforehand also gives people a chance to chime in
> with alternative, and possibly better, solutions.

FWIW, we are in the process to migrate python.org's issue tracker from
sf.net to a new site, using roundup. They evaluated a couple of alternative
candidates, among them Trac. However, Their requirements are different
from yours, and so that doesn't have to mean much in this context.
>From all I have heared, Trac is a very good tool.

Best regards,
		Stefan

-- 

      ...ich hab' noch einen Koffer in Berlin...

Re: [xmlroff] What's next for xmlroff?

[Steinar B. <sb...@do...>]

>>>>> Stefan Seefeld <se...@sy...>:

> Yes, please ! :-)
> (sf.net's list archive interface is really bad.)

Note that this list is also archived on gmane, which is really good,
and also gives a lot of alternative ways of accessing it:
	http://dir.gmane.org/gmane.text.xml.xmlroff.general

Re: [xmlroff] What's next for xmlroff?

[Keith F. <ke...@or...>]

Tony Graham wrote:
> I have it in mind to move xmlroff off CVS on SourceForge to a
> Subversion repository hosted on xmlroff.org (which would also move off
> SourceForge's servers).
> 
> I would then choose to use Trac (http://trac.edgewall.com/) for the
> new xmlroff website, ticket tracking system, and repository browser.
> 
> I have been using Trac for a while now and I quite like it, but what
> do you people think?

Yeah, I've been happy with Trac in all the places that I've eventually got it 
setup. Occasionally it barfs or gives totally stupid errors, and setting it up 
initially is a real pain, but once it's going, it's great (I especially like the 
RSS feed for commits, among other things).

All that said, I don't really think it's a very good Wiki.



HTH,
Keith

Re: [xmlroff] What's next for xmlroff?

[Tony G. <Ton...@Me...>]

On Tue, Feb 06 2007 19:49:07 +0000, Keith Fahlgren wrote:
> Tony Graham wrote:
...
>> I would then choose to use Trac (http://trac.edgewall.com/) for the
>> new xmlroff website, ticket tracking system, and repository browser.
>> 
>> I have been using Trac for a while now and I quite like it, but what
>> do you people think?
>
> Yeah, I've been happy with Trac in all the places that I've
> eventually got it setup. Occasionally it barfs or gives totally
> stupid errors, and setting it up initially is a real pain, but once
> it's going, it's great (I especially like the RSS feed for commits,
> among other things).
>
> All that said, I don't really think it's a very good Wiki.

If I was looking for just a wiki, I doubt that I'd pick Trac either.

I like Trac because it does wiki, repository, and tickets and supports
easy linking between the three.  With little extra effort, it also
does easy linking to mailing list archives as well.

As for setup problems, that's why I'm looking at the hosted service
instead of doing it myself.  With a hosted service, the security
angles should have been already thought out and upgrades should also
'just happen' instead of my having to find out about them and apply
them.

Regards,


Tony.