<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Also - I installed TRAC on the WPLUG server (only 4 packages needed
to be added, and they can easily be removed if desired) and was
tinkering with it. One problem with the release packaged in EPEL is
that it doesn't include any man pages (that I can find, anyway), so
it drove me to their web site to look at documentation - where I
discovered that there is an "account administration" plugin
available, that lets people register for accounts in a TRAC project,
change their own passwords, etc. Which would make it much more
livable.<br>
<br>
It's not running at the moment (I don't want to leave it running at
the moment, and leave the associated hole poked in the firewall for
the port I was using, unless someone's actually working with it),
but I was able to use the account admin plugin to do useful things,
and was reasonably happy with that. (It also made me learn a little
bit about "firewall-cmd" to add the appropriate hole, since our
CentOS config doesn't just use straightforward iptables, and I
didn't want to just completely disable firewalld while I was
experimenting - so that was a nice little learning bonus...)<br>
<br>
I will admit a slight bias towards TRAC because I've set it up
before, it's relatively straightforward to set up, and once you get
it set up it doesn't require a whole lot of care and feeding. And
also because it can run completely standalone using an embedded web
server and doesn't need to be plugged into Apache (though you can if
you want - but configuring it reasonably would require either
mod_wsgi or mod_python to the Apache config, and we don't currently
use either, and I'm not particularly inclined to muck with the
Apache configuration just now....).<br>
<br>
I'm still going to look at the other one that Chuck mentioned also.<br>
<br>
--Pat.<br>
<br>
<div class="moz-cite-prefix">On 10/5/2016 4:19 PM, Pat Barron wrote:<br>
</div>
<blockquote
cite="mid:8e507a32-91ff-618b-90d0-be792ca171b6@lectroid.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
I have not - but I will check it out. Thanks!!<br>
<br>
--Pat.<br>
<br>
<div class="moz-cite-prefix">On 10/5/2016 3:31 PM, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:chuck@dasroot.net">chuck@dasroot.net</a> wrote:<br>
</div>
<blockquote
cite="mid:56D6CFED-4373-40CB-8999-D7D8A16F80A3@dasroot.net"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div>Have yinz looked at taiga?</div>
<div><br>
</div>
<div><a moz-do-not-send="true" href="Http://taiga.io">Http://taiga.io</a> </div>
<div><br>
</div>
<div>It's release planning and ticketing with integrations.
We've used it in the past with some success but it may not be
what you're looking for</div>
<div><br>
On Oct 5, 2016, at 11:35 AM, Joe Prostko <<a
moz-do-not-send="true" href="mailto:joe.prostko@gmail.com">joe.prostko@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>On Tue, Oct 4, 2016 at 11:50 AM, Pat
Barron <<a moz-do-not-send="true"
target="_blank"
href="mailto:pat@lectroid.com">pat@lectroid.com</a>>
wrote:<br>
<br>
> Any comments? Does anyone have any
other lightweight ticket tracking solutions
they like? I know that things like Redmine
exist, but are far too "heavyweight" for our
relatively simple needs.<br>
<br>
</div>
I'm not the most fond of Trac, but that is
mostly because the main instance of it that I
use ( <a moz-do-not-send="true"
href="https://dev.haiku-os.org/">https://dev.haiku-os.org/</a>
) has additional modules enabled, and I
believe some custom code. In other words,
while it usually is well-behaved, sometimes it
does indeed misbehave.<br>
<br>
</div>
I have used Open Atrium ( <a
moz-do-not-send="true" target="_blank"
href="http://openatrium.com">http://openatrium.com</a>
) before, but basically it is a customized
Drupal distribution. While older versions based
off of Drupal 6 were highly targeted for
ticketing, that seemed to take a back seat in
newer versions that are basically a type of
collaboration tool. Naturally, it comes with
the same baggage as running Drupal as well, and
requires updates to be done regularly for
security and bugfixes. I think it is overkill
for our case.<br>
<br>
</div>
I have used osTicket ( <a moz-do-not-send="true"
target="_blank" href="http://osticket.com/">http://osticket.com/</a>
) as well, and while it seems initially like it
would be a good solution, it is primarily meant
for customers to file tickets to an
organization/company. It probably isn't a great
fit in our case for tracking our own
tickets..well, or at least I think that is the use
case you are targeting. It is possible that it
allows for a private issue tracker of sorts
nowadays, but that certainly wasn't the case
previously when I used it.<br>
<br>
</div>
I know you said you didn't want anything with SCM
aspects, but Fossil ( <a moz-do-not-send="true"
target="_blank" href="http://fossil-scm.org">http://fossil-scm.org</a>
) offers a ticketing system along with its SCM and
other functionality. You will see that the project
itself has tickets disabled though, since they were
getting spammed since they allowed anybody to file a
ticket. If you do set up users though, you can make
it so that anonymous people do not have the ability
to file tickets. It also lacks LDAP integration,
although if you can kind of work around that by
using something like mod_authnz_ldap and taking
advantage of the REMOTE_USER header which Fossil
understands. Fossil is a single binary, so it's not
mysterious to get up and running. That said, even
though it is pretty lightweight, it may be overkill
as well, since it has other functionality we
probably wouldn't use.<br>
<br>
</div>
<br>
</div>
I'm open to giving Trac a whirl, but admit I don't know
squat about administering it. I do know how to interact
with it though, so maybe that counts for something. :)<br>
<br>
</div>
- joe<br>
<div>
<div>
<div><br>
<br>
<div><br>
<br>
<br>
<div>
<div><br>
<br>
<br>
<br>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>wplug-internet mailing list</span><br>
<span><a moz-do-not-send="true"
href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
wplug-internet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:wplug-internet@wplug.org">wplug-internet@wplug.org</a>
<a class="moz-txt-link-freetext" href="http://www.wplug.org/mailman/listinfo/wplug-internet">http://www.wplug.org/mailman/listinfo/wplug-internet</a>
</pre>
</blockquote>
<br>
</body>
</html>