an issue tracker for crypto++

[Zooko O'Whielacronx]

Crypto++ needs an issue tracker. I recommend launchpad:

https://launchpad.net/cryptopp

Or if you prefer, we could use this Trac that I set up in order to
have an web source code browser for Crypto++:

http://allmydata.org/trac/cryptopp/wiki

Launchpad is managed by Canonical and probably has much better uptime
and long-term support than my little server does. :-)

Trac has the advantages of integrating ticketing, source code
browsing, and wiki, and having many useful open source Trac plugins to
extend functionality.

Either of them will do fine for the simple job of tracking issues.

I'll do the work of setting it up if you tell me which one you want to
use. (It is very little work to set up.)

Regards,

Zooko

[Wei Dai]

It looks like SourceForge supports Trac. I've enabled it, and added you
(Zooko) as an admin. Can we set it up so that it's linked with the mailing
list somehow, so that I don't have to keep track of two different places
bugs might be reported? Oh, the URL is
https://sourceforge.net/apps/trac/cryptopp/

--------------------------------------------------
From: "Zooko O'Whielacronx" <zoo...@gmail.com>
Sent: Sunday, December 13, 2009 1:18 PM
To: "Crypto++ Users" <cryptop...@googlegroups.com>
Subject: an issue tracker for crypto++

> --
> You received this message because you are subscribed to the "Crypto++
> Users" Google Group.
> To unsubscribe, send an email to
> cryptopp-user...@googlegroups.com.
> More information about Crypto++ and this group is available at
> http://www.cryptopp.com.
>

[Zooko Wilcox-O'Hearn]

On Sunday, 2009-12-13, at 19:01 , Wei Dai wrote:

> It looks like SourceForge supports Trac.

...
> https://sourceforge.net/apps/trac/cryptopp/


Hrm, this is weird -- why does sourceforge support trac, when it has
its own bug tracker that is widely used?

I had forgotten that Crypto++ uses sourceforge. Would it make more
sense to use the sourceforge-native issue tracker?

I personally don't like it much (nor do I much like anything about
sourceforge project hosting compared to the newer alternatives), but
I would be willing to do a bit of admin work to maintain it.
Shouldn't be hard.

Regards,

Zooko

[Wei Dai]

I guess some people didn't like SourceForge's native issue tracker, so they
added Trac as an additional option. SourceForge now has a bunch of "apps"
like Trac that projects can opt-in for.

Since Trac is available, and already enabled, I see no reason not to use it.

--------------------------------------------------
From: "Zooko Wilcox-O'Hearn" <zo...@zooko.com>
Sent: Sunday, December 13, 2009 7:36 PM
To: "Wei Dai" <wei...@weidai.com>
Cc: "Crypto++ Users" <cryptop...@googlegroups.com>
Subject: Re: an issue tracker for crypto++

[Geoff Beier]

On Sun, Dec 13, 2009 at 22:36, Zooko Wilcox-O'Hearn <zo...@zooko.com> wrote:
> On Sunday, 2009-12-13, at 19:01 , Wei Dai wrote:
>
>> It looks like SourceForge supports Trac.
> ...
>> https://sourceforge.net/apps/trac/cryptopp/
>
>
> Hrm, this is weird -- why does sourceforge support trac, when it has
> its own bug tracker that is widely used?
>

IIRC they're trying to phase out their built-in bug tracker in favor
of their new integrated trac installs. They're not making those of us
who use the old one migrate (yet) but I think they've disabled the
ability to instantiate the old one. This is the best I remember from
their update newsletters, anyway :-). At any rate, it's clear that
trac is now preferred. They're doing the same for their old forum
system, encouraging us to move to phpBB.


Geoff

[Zooko O'Whielacronx]

Okay, good. Whoops, not so good -- the URL
http://sourceforge.net/apps/trac/cryptopp/ redirects to
https://sourceforge.net/apps/trac/cryptopp/ which redirects to
http://sourceforge.net/apps/trac/cryptopp/ . It was working yesterday
but not today. I guess I'll try again tomorrow. Oh, I see that it
works with Firefox but not Safari. Okay.

Anyway, we need to decide if we're going to use the wiki features of
the trac at all. They have an advantage over the current wiki [1]
because they can be integrated with the issue tracking and
source-code-browsing features of trac. For example, you can have a
link to an open issue on a page of your wiki, and when that issue gets
closed then the hyperlink gets marked up (with a strikethru) to show
that the link is closed. Also it is easy to type [987] to mean
"hyperlink to patch #987 in the revision control history" or "#123" to
mean "issue ticket #123" in your wiki edits.

On the other hand, there is already a lot of content in the current
wiki, and I for one don't feel like spending time porting it over, so
we should probably either have two wikis or just keep the old one and
not use the new one, unless someone else wants to volunteer to copy
everything into the new one.

Regards,

Zooko

[1] http://www.cryptopp.com/wiki/Main_Page

[Jeffrey Walton]

Hi Zokoo,

> On the other hand, there is already a lot of content in the current
> wiki, and I for one don't feel like spending time porting it over, so
> we should probably either have two wikis or just keep the old one and
> not use the new one, unless someone else wants to volunteer to copy
> everything into the new one.

What ever you choose, please stay consistent. The point of the FAQ and
the wiki is to make things easier on both the beginner and the mailing
list. A FAQ and multiple wikis will surely complicate matters. If you
choose the old wiki, please disable the new wiki so folks don't begin
using it. If you choose the new wiki, I'll help cut over the old wiki
and then Wei Dai should make the old wiki go away. Otherwise, folks
will use both.

Also keep in mind that SourceForge generally sucks at serving up
content. I'm not sure if there are configuration issues, or if the
servers are overworked an underpaid, or if SourceForge trying to serve
up too many ads, or some combination. If I ever get Wall Street-MBA
wealthy, I'll donate a bunch of hardware to SourceForge so we can
remove one variable from the equation.

Jeff