Google Summer of Code

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

Jesse

PGP.sig (186 Bytes)

Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

Good idea.

What would you like to do/see done as part of a RT summer of code
project?

AJAX interface would be my first thought, 3.6 went a long way towards
simplifying the interface for users but I think there’s still room for
improvement in the layout.

Jay

Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code project?

It might take more than a summer, depending on how close-coupled you try
to make it, but I’d love to see a connection between RT and opennms
(The OpenNMS Group) so that network problems
could open RT tickets automatically (that could probably be done by
email now), and from the ticket you would have a link to the opennms
node and asset info and history. One complication would be how to do
this in a way that would still make sense if you delete network nodes or
start over again with a new opennms database. A link to a twiki page
using some convention for naming would be nice too.

Les Mikesell
les@futuresource.com

Billing and accounts. O:-)On Wed, 2007-02-28 at 14:29 -0500, Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

Jesse


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

AJAX interface would be my first thought, 3.6 went a long way towards
simplifying the interface for users but I think there’s still room for
improvement in the layout.

Exactly what I was thinking!

Regards,

joe
Joe Casadonte
joe.casadonte@oracle.com

========== ==========
== The statements and opinions expressed here are my own and do not ==
== necessarily represent those of Oracle Corporation. ==
========== ==========

The ability to use AD (or LDAP) to hold group members.On Feb 28, 2007, at 1:29 PM, Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

Jesse


The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Billing and accounts. O:-)

And real reporting, output to PDF or HTML, with the ability to automate
scheduled emails of reports to the pointy-haired.

/Ole Craig
Security Engineer
Team lead, customer support

ocraig@stillsecure.com
303-381-3824 direct
303-381-3802 support
303-381-3880 fax

www.stillsecure.com

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

A rational, extensible, full-featured REST 2.0
   bobg

Jesse Vincent wrote:

What would you like to do/see done as part of a RT summer of code
project?

Hi Jesse,

How about improving performance for very large databases (I am talking
millions of tickets)? There are a couple of approaches I have been
considering:

I sort of suspect that this one will be relatively hard to pass off as a
student project for the summer (though I’ve been surprised before :wink:

I’ve recently spent some time with an RT instance running on an entirely
unoptimized MySQL 4.1 with about a million and a half tickets.
Performance was surprisingly eppy (most page loads were well under a
second). What kinds of performance are you seeing? And how many
millions?

Best,
Jesse

The ability to use AD (or LDAP) to hold group members.

Definitely using normal LDAP would be great, with ADLDAP support
in second. Adding full-text indexing and search capability to improve
the performance with DBs that support it (PostgreSQL, MySQL, Oracle,…)

Ken

Jesse Vincent wrote:

I’ve recently spent some time with an RT instance running on an entirely
unoptimized MySQL 4.1 with about a million and a half tickets.
Performance was surprisingly eppy (most page loads were well under a
second).

Nice…

What kinds of performance are you seeing? And how many
millions?

A couple of seconds to load a ticket with about 2 million of them in the
database; several seconds to display a page search results.

Of course, we have a heavily modified 3.4.5 and so it’s not really
apples to apples. Moving to a static (or better cached) policy would
give it a significant boost.

  • Dmitri.

Hello,

Something that I’ve been thinking about is a hierarchical task/project
module where a “project” would be the parent ticket, with individual
tasks as “children” tickets. Its basically the same structure as RT
uses for tickets, but the interface would have to be different.
Essentially, I need something better than Outlook tasks but not true
project management.

Eric Gauthier
Network Engineer
617-353-8218 ~^~ elg@nsegc.bu.edu
Boston University - Office of ITFrom: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of John
Arends
Sent: Wednesday, February 28, 2007 4:29 PM
To: Jesse Vincent
Cc: rt-Users Users
Subject: Re: [rt-users] Google Summer of Code

The ability to use AD (or LDAP) to hold group members.

Bob Goldstein wrote:> >On Wed, 2007-02-28 at 14:29 -0500, Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

A rational, extensible, full-featured REST 2.0

Yes. The server-side REST code could stand some improvement. I am
willing to donate (or [co-]maintain, if server-side changes are not very
heavy and don’t take up oodles of time to keep up) RT::Client::REST to
the project.

  • Dmitri.

The ability to tie multiple email addresses to a single user, so
that I can tell RT that joeb@example.com and joe.bloggs@mail.example.com
are the same user and mail addressed to either one ends up in the same
mailbox.

Corollaries:
* either source address should be allowed to correspond with a
ticket that the other has opened, and
* when the ticket owner sends email to the ticket, only the
address that was originally associated with the ticket will get
an email.On Wed, 2007-02-28 at 15:28 -0600, John Arends wrote:

The ability to use AD (or LDAP) to hold group members.
/Ole Craig
Security Engineer
Team lead, customer support

ocraig@stillsecure.com
303-381-3824 direct
303-381-3802 support
303-381-3880 fax

www.stillsecure.com

Jesse Vincent wrote:

What would you like to do/see done as part of a RT summer of code
project?

Hi Jesse,

How about improving performance for very large databases (I am talking
millions of tickets)? There are a couple of approaches I have been
considering:

  1. Do away with dynamic policy and calculate it once per user session
    (this would probably require removing per-ticket rights).

  2. Do a better job of caching policy results (*HasRight business) and
    associate it with user session, so they virtually become free. I have
    been given it some thought (and code) lately and can elaborate if you’re
    interested.

    • Dmitri.

In order of preference:

  1. Easily customizable reports.
  2. “Hidden” approvals. (i.e. ticket is hidden until approval is given)
  3. Group ownership of tickets.

The OpenNMS integration and project management suggestions are good also.

Les

Les Driggers :black_small_square: Manager, Corporate IT
T 662/236-8200 :black_small_square: F 662/236-2037 :black_small_square: ldriggers@fncinc.com
FNC Inc. :black_small_square: 1214 Office Park Drive :black_small_square: Oxford, MS 38655
www.fncinc.com

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf
Of Jesse Vincent
Sent: Wednesday, February 28, 2007 1:30 PM
To: rt-Users Users
Subject: [rt-users] Google Summer of Code

I’d love to submit RT to Google’s Summer of Code this summer.
It’s probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of
code project?

Jesse

Confidentiality Notice: This message is for the sole use of the intended recipient(s).
It may contain confidential or proprietary information and may be subject to the
attorney-client privilege or other confidentiality protections. If this message was
misdirected, neither FNC Holding Company, Inc. nor any of its subsidiaries waive any
confidentiality, privilege, or trade secrets. If you are not a designated recipient,
you may not review, print, copy, retransmit, disseminate, or otherwise use this message.
If you have received this message in error, please notify the sender by reply e-mail
and delete this message.

Jesse Vincent wrote:

I’d love to submit RT to Google’s Summer of Code this summer. It’s
probably time to start brainstorming projects.

What would you like to do/see done as part of a RT summer of code
project?

Better RTx::Shredder integration, with some built-in useful operations
such as “purge all users that are not referenced by any
tickets/attachments/transactions/etc”, one-button validations of
everything, and so forth.

A global scrip repository. Right now you have global scrips and
per-queue scrips. Wouldn’t it be nice if, when you set up a new queue,
that instead of writing a bunch of “new” scrips that are identical with
some of the scrip used elsewhere, you can just select them (kind of like
group membership: these queue execute this scrip)? Sure, I could write
all my scrips as global scrips and then put queue-name tests in them,
modifying them each time I add a queue, but that seems to be an
unnecessary risk.

Integration and clean-up of the RTx::Report(s) module. Reports are fun!

Brian Gallew wrote:

Integration and clean-up of the RTx::Report(s) module. Reports are fun!

And, as previously mentioned, customizable reports.

Kenneth Marshall wrote:> On Wed, Feb 28, 2007 at 03:28:37PM -0600, John Arends wrote:

The ability to use AD (or LDAP) to hold group members.

Definitely using normal LDAP would be great, with ADLDAP support
in second. Adding full-text indexing and search capability to improve
the performance with DBs that support it (PostgreSQL, MySQL, Oracle,…)
Atleast for Oracle it is already possible. Posted this to either
rt-users or rt-develop a while back. If you can’t find it I’ll repost.

Joop

Also a fully integrated soap (xml) interface , so php and .net systems
can talk to RT.
REST is good but soap is more of a standard.
Roy
Dmitri Tikhonov wrote: