You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Cory Johns <jo...@gmail.com> on 2013/11/21 18:29:51 UTC
OSS Forge feature comparison chart
I have created a feature comparison chart comparing Allura to some other
OSS Forge platforms, at:
https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
I'd like to put it to the community for comment; are there any platforms or
features that should be added, are there any inaccuracies in the data,
should it have more reference citations, etc?
NB: I know the table is a fair bit wider than the fixed width layout
supports, and we don't yet have the Maximize button on wiki pages (pending
#6908), but you can maximize it using the JavaScript console using:
$('body').addClass('content-maximized')
Thanks,
Cory
Re: OSS Forge feature comparison chart
Posted by Cory Johns <jo...@gmail.com>.
Awesome. Thanks, Olemis. Apache Bloodhound added and Trac updated.
On Fri, Nov 22, 2013 at 3:27 PM, Olemis Lang <ol...@gmail.com> wrote:
> On Thu, Nov 21, 2013 at 12:29 PM, Cory Johns <jo...@gmail.com> wrote:
>
> > I have created a feature comparison chart comparing Allura to some other
> > OSS Forge platforms, at:
> >
> > https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
>
>
> nice !
>
> BTW other related comparisons are :
>
> http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
> http://en.wikipedia.org/wiki/Comparison_of_time_tracking_software
> http://en.wikipedia.org/wiki/Comparison_of_project_management_software
>
>
> >
> > I'd like to put it to the community for comment; are there any platforms
> or
> > features that should be added,
>
>
> yes, Apache™ Bloodhound
> ;)
>
>
> > are there any inaccuracies in the data,
> >
>
> if behavior added by plugin counts then afaict , yes . For Trac the matrix
> would look like
>
> BSD || Python || SQLite, PostgreSQL, or MySQL || Yes || Yes ||
> Yes || Yes || Yes || No
> Yes || Yes || Yes [1]_ || Yes [2]_ || Yes [3]_ || No || Yes ||
> Yes || Yes [4]_ || Yes
>
> Apache™ Bloodhound should only differ in Project discovery = yes
>
> should it have more reference citations, etc?
> >
>
> .. [1] http://trac-hacks.org/wiki/DiscussionPlugin
> .. [2] http://trac-hacks.org/wiki/FullBlogPlugin
> .. [3] http://trac-hacks.org/wiki/DownloadsPlugin
> .. [4] http://trac-hacks.org/wiki/ThemeEnginePlugin
>
> [...]
>
> --
> Regards,
>
> Olemis - @olemislc
>
> Apache™ Bloodhound contributor
> http://issues.apache.org/bloodhound
> http://blood-hound.net
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>
Re: OSS Forge feature comparison chart
Posted by Olemis Lang <ol...@gmail.com>.
On Thu, Nov 21, 2013 at 12:29 PM, Cory Johns <jo...@gmail.com> wrote:
> I have created a feature comparison chart comparing Allura to some other
> OSS Forge platforms, at:
>
> https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
nice !
BTW other related comparisons are :
http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems
http://en.wikipedia.org/wiki/Comparison_of_time_tracking_software
http://en.wikipedia.org/wiki/Comparison_of_project_management_software
>
> I'd like to put it to the community for comment; are there any platforms or
> features that should be added,
yes, Apache™ Bloodhound
;)
> are there any inaccuracies in the data,
>
if behavior added by plugin counts then afaict , yes . For Trac the matrix
would look like
BSD || Python || SQLite, PostgreSQL, or MySQL || Yes || Yes ||
Yes || Yes || Yes || No
Yes || Yes || Yes [1]_ || Yes [2]_ || Yes [3]_ || No || Yes ||
Yes || Yes [4]_ || Yes
Apache™ Bloodhound should only differ in Project discovery = yes
should it have more reference citations, etc?
>
.. [1] http://trac-hacks.org/wiki/DiscussionPlugin
.. [2] http://trac-hacks.org/wiki/FullBlogPlugin
.. [3] http://trac-hacks.org/wiki/DownloadsPlugin
.. [4] http://trac-hacks.org/wiki/ThemeEnginePlugin
[...]
--
Regards,
Olemis - @olemislc
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: OSS Forge feature comparison chart
Posted by Cory Johns <jo...@gmail.com>.
Good idea, Dave. I've split the table and it definitely works better.
On Fri, Nov 22, 2013 at 1:54 PM, Dave Brondsema <da...@brondsema.net> wrote:
> Some wikipedia pages avoid the width issue by breaking up comparison
> tables into
> 2 tables, one on top of each other.
>
> On 11/21/13 12:29 PM, Cory Johns wrote:
> > I have created a feature comparison chart comparing Allura to some other
> > OSS Forge platforms, at:
> >
> > https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
> >
> > I'd like to put it to the community for comment; are there any platforms
> or
> > features that should be added, are there any inaccuracies in the data,
> > should it have more reference citations, etc?
> >
> > NB: I know the table is a fair bit wider than the fixed width layout
> > supports, and we don't yet have the Maximize button on wiki pages
> (pending
> > #6908), but you can maximize it using the JavaScript console using:
> >
> > $('body').addClass('content-maximized')
> >
> >
> > Thanks,
> > Cory
> >
>
>
>
> --
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> <><
>
Re: OSS Forge feature comparison chart
Posted by Dave Brondsema <da...@brondsema.net>.
Some wikipedia pages avoid the width issue by breaking up comparison tables into
2 tables, one on top of each other.
On 11/21/13 12:29 PM, Cory Johns wrote:
> I have created a feature comparison chart comparing Allura to some other
> OSS Forge platforms, at:
>
> https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
>
> I'd like to put it to the community for comment; are there any platforms or
> features that should be added, are there any inaccuracies in the data,
> should it have more reference citations, etc?
>
> NB: I know the table is a fair bit wider than the fixed width layout
> supports, and we don't yet have the Maximize button on wiki pages (pending
> #6908), but you can maximize it using the JavaScript console using:
>
> $('body').addClass('content-maximized')
>
>
> Thanks,
> Cory
>
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
<><
Re: OSS Forge feature comparison chart
Posted by Cory Johns <jo...@gmail.com>.
On Thu, Nov 21, 2013 at 1:33 PM, Roberto Galoppini <
roberto.galoppini@gmail.com> wrote:
>
> What about adding all or some of the other features mentioned here:
>
>
> http://en.wikipedia.org/wiki/Comparison_of_open-source_software_hosting_facilities
>
> I did use that list as a reference, and there's definitely some overlap.
However, most of the features from that table that weren't included, such
as Web Hosting or Shell Server, seem more specific to the hosting provider
as opposed to the software platform itself. Some of the others are
analogous but could possibly be named more clearly, e.g., Announce seems
the same as the Blog / News category, Release Binaries I've got as Download
Manager, etc. Others, I wasn't sure about, like what's the difference
between Personal Branch and Private Branch? We could maybe add columns for
Private Projects / Repositories.
Re: OSS Forge feature comparison chart
Posted by Roberto Galoppini <ro...@gmail.com>.
2013/11/21 Cory Johns <jo...@gmail.com>:
> I have created a feature comparison chart comparing Allura to some other
> OSS Forge platforms, at:
>
> https://forge-allura.apache.org/p/allura/wiki/Feature%20Comparison/
Sounds a good start to me.
> I'd like to put it to the community for comment; are there any platforms or
> features that should be added, are there any inaccuracies in the data,
> should it have more reference citations, etc?
What about adding all or some of the other features mentioned here:
http://en.wikipedia.org/wiki/Comparison_of_open-source_software_hosting_facilities
Roberto
>
> NB: I know the table is a fair bit wider than the fixed width layout
> supports, and we don't yet have the Maximize button on wiki pages (pending
> #6908), but you can maximize it using the JavaScript console using:
>
> $('body').addClass('content-maximized')
>
>
> Thanks,
> Cory