You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Ryan Ollos <ry...@wandisco.com> on 2012/11/08 23:42:35 UTC

Ohloh page for Bloodhound

I didn't see that we have an Ohloh page yet, so I went ahead and made one.
"bloodhound" was already taken as a project name for the URL, so I went
with "apache-bloodhound" (1).

Please contribute to the page if you see something that can be added. Gary,
you may want to apply to be a "project manager" (2).

There are various widgets that can be placed on the Bloodhound project
pages if we'd like to do that (3).

There is a location to provide a link for Download of the project. I
pointed that to the BloodhoundInstall page since I didn't want to link
directly to the 0.1.0 download (4) that is pointed to on the project page.
Is there a URL that always points to the latest download?

(1) https://www.ohloh.net/p/apache-bloodhound
(2) https://www.ohloh.net/p/apache-bloodhound/manages/new
(3) https://www.ohloh.net/p/apache-bloodhound/widgets
(4)
http://www.apache.org/dyn/closer.cgi/incubator/bloodhound/apache-bloodhound-incubating-0.1.0-RC1.tar.gz

Re: Ohloh page for Bloodhound

Posted by Olemis Lang <ol...@gmail.com>.
On 11/8/12, Ryan Ollos <ry...@wandisco.com> wrote:
> I didn't see that we have an Ohloh page yet, so I went ahead and made one.
> "bloodhound" was already taken as a project name for the URL, so I went
> with "apache-bloodhound" (1).
>

cool !
:)

[...]
> There are various widgets that can be placed on the Bloodhound project
> pages if we'd like to do that (3).
>

This is the point I repeat that we should have custom dashboards
defined in the database instead of static DASHBOARD_SCHEMA (i.e. #140
) .

;)

[...]

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: Ohloh page for Bloodhound

Posted by Branko Čibej <br...@wandisco.com>.
On 16.11.2012 11:38, Joachim Dreimann wrote:
> Good thinking Ryan.
> According to the syntax tips wildcards are not supported, so I've replaced
> them with the actual file names (this only affects Bootstrap currently).
>
> I've also excluded the /docs/ folder for now as it's not production code
> and we may as well move out of trunk.

I very strongly advise against moving docs out of trunk. I have not seen
a good argument for doing so, and there's always a good argument (called
"maintain audit trail") for branching docs with everything else.

-- Brane


-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com

Re: Ohloh page for Bloodhound

Posted by Joachim Dreimann <jo...@wandisco.com>.
Good thinking Ryan.
According to the syntax tips wildcards are not supported, so I've replaced
them with the actual file names (this only affects Bootstrap currently).

I've also excluded the /docs/ folder for now as it's not production code
and we may as well move out of trunk.

Cheers,
Joe


On 16 November 2012 02:26, Ryan Ollos <ry...@wandisco.com> wrote:

> On Fri, Nov 9, 2012 at 6:37 AM, Joachim Dreimann <
> joachim.dreimann@wandisco.com> wrote:
>
> > > Is there a URL that always points to the latest download?
> > There isn't yet, but I believe we should have a bloodhound-latest
> > distribution file to fix that.
> > Question: Can we do this without needing further approval from the IPMC
> or
> > similar?
> >
>
> Thanks for making the updates. I adjusted the code metrics ignore files
> settings (1), just being curious as to how much "bloodhound" code exists.
> The current settings are:
>
> Disallow: trac/
> Disallow: bhdashboard/htdocs/css/bootstrap*.css
> Disallow: bhdashboard/htdocs/js/bootstrap*.js
>
> but there are probably other third-party files that could be excluded so
> that the code metrics are more accurate. It looks like the metrics update
> every day or so.
>
> (1) https://www.ohloh.net/p/apache-bloodhound/enlistments/505575/edit
>



-- 
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *

Re: Ohloh page for Bloodhound

Posted by Ryan Ollos <ry...@wandisco.com>.
On Fri, Nov 9, 2012 at 6:37 AM, Joachim Dreimann <
joachim.dreimann@wandisco.com> wrote:

> > Is there a URL that always points to the latest download?
> There isn't yet, but I believe we should have a bloodhound-latest
> distribution file to fix that.
> Question: Can we do this without needing further approval from the IPMC or
> similar?
>

Thanks for making the updates. I adjusted the code metrics ignore files
settings (1), just being curious as to how much "bloodhound" code exists.
The current settings are:

Disallow: trac/
Disallow: bhdashboard/htdocs/css/bootstrap*.css
Disallow: bhdashboard/htdocs/js/bootstrap*.js

but there are probably other third-party files that could be excluded so
that the code metrics are more accurate. It looks like the metrics update
every day or so.

(1) https://www.ohloh.net/p/apache-bloodhound/enlistments/505575/edit

Re: Ohloh page for Bloodhound

Posted by Branko Čibej <br...@wandisco.com>.
On 09.11.2012 15:37, Joachim Dreimann wrote:
> Thanks Ryan. I've expanded the profile a little bit further.
>
>> Is there a URL that always points to the latest download?
> There isn't yet, but I believe we should have a bloodhound-latest
> distribution file to fix that.
> Question: Can we do this without needing further approval from the IPMC or
> similar?

You should not rename tarballs to some "latest" kind of name, because
that's not what was signed and voted on. You can have a "latest stable
released version" link on the project page that points to the correct
download. You can also have a latest-stable symbolic link, but I have to
say I wonder why you'd want to have that instead of just posting a
single link the latest release tarball to the web site.

-- Brane

-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com

Re: Ohloh page for Bloodhound

Posted by Joachim Dreimann <jo...@wandisco.com>.
Thanks Ryan. I've expanded the profile a little bit further.

> Is there a URL that always points to the latest download?
There isn't yet, but I believe we should have a bloodhound-latest
distribution file to fix that.
Question: Can we do this without needing further approval from the IPMC or
similar?

- Joe

Re: Ohloh page for Bloodhound

Posted by Ryan Ollos <ry...@wandisco.com>.
On Fri, Nov 9, 2012 at 10:50 AM, Branko Čibej <br...@wandisco.com> wrote:

> On 08.11.2012 23:42, Ryan Ollos wrote:
> > I didn't see that we have an Ohloh page yet, so I went ahead and made
> one.
> > "bloodhound" was already taken as a project name for the URL, so I went
> > with "apache-bloodhound" (1).
>
> I have to ask -- what's the point of this?


The purpose of the site is explained here: http://meta.ohloh.net/us/

It seems to be mildly popular in the open source world. I'd expect an even
milder effect on Bloodhound's popularity by adding a page there, but it
can't hurt as far as I know.

Re: Ohloh page for Bloodhound

Posted by Branko Čibej <br...@wandisco.com>.
On 08.11.2012 23:42, Ryan Ollos wrote:
> I didn't see that we have an Ohloh page yet, so I went ahead and made one.
> "bloodhound" was already taken as a project name for the URL, so I went
> with "apache-bloodhound" (1).

I have to ask -- what's the point of this?

-- 
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com