I'm happy with that, but I generally think it's good to have project
pages maintained at as many of these websites as possible. It helps
people know about MantisBT as they're looking for issue/bug trackers.
Coupled with frequent releases (most of these sites have a "files
released today" list that gets a lot of views) you can quite easily
bring a lot of attention to the project.
The key thing IMO is to have a very well written project summary that
you can copy and paste to each site. A summary of "MantisBT is a bug
tracker that lets you report and track bugs in a team" is completely
useless. A summary that mentions tons of keywords/features such as
"customisable workflow, source code repository integration, twitter
integration, blah, blah" gets more attention. Keywords are important :)
Mantis is already #3 in the "international" Google results for "bug
tracker". In the Australian Google, it is #2. It comes up as #4 in
Google Australia for "bug tracking". No top 10 hits for "issue tracker"
or "issue tracking" however. It is #1 for "mantis" (ahead of the
Wikipedia article on the insect). Interestingly, the SourceForge page
for MantisBT also appears in the top 10 results of "mantis".
So does anyone have thoughts on establishing/maintaining the following
Or is it a waste of time in many/all of those cases?
On Sat, 2009-10-10 at 13:47 -0400, John Reese wrote:
> Hi all,
> With all the garbage and such that I had to go through to upload and set up for
> the recent RC2 release, I'm very frustrated, confused, and annoyed at the
> changes SourceForge has made to their file hosting system. It no longer
> supports any concept of releases, just folders of associated content. It also
> no longer allows (or at least doesn't work for me) uploading of files via SCP,
> not to mention a 30 minute lag time between uploading the files and seeing the
> latest file available for download.
> With that in mind, I've been poking around Ohloh's site, looking into their
> release hosting system. The Download FAQ  and Tutorial  gives an overview
> of the options they provide, and it looks very tempting. With the Console
> Upload FAQ  and Tutorial , it shows how we could even add something to the
> build scripts to automate generation of an "instruct" file that, when uploaded
> to Ohloh, automatically creates the appropriate release versions and associates
> the necessary files.
> If this sounds like a good idea, or if noone disagrees, I'd like to shoot for
> getting this in place for the 1.2 final release. Any comments, questions, or
>  https://www.ohloh.net/help/download_faq
>  https://www.ohloh.net/help/download_tutorial
>  https://www.ohloh.net/help/console_upload_faq
>  https://www.ohloh.net/help/console_upload_tutorial