Trac tickets email notification

[Jef van Schendel]

Hey all,

To me, our Trac ticket queue feels really disconnected from the rest
of our work. It's like a completely separate space that nobody keeps
track of. It's all out there in the open, which is great and all, but
we hardly pay attention to it. Or at least, I know I don't. :)

For instance there are a bunch of new tickets that don't have any
comments yet, like this one [1], started by jsmith two months ago.

We've got two main ways to keep track of new tickets: we can either
check the Trac page every day or get notified on IRC. The first one is
boring, slow and clunky. The second one relies on people being present
in the channel at the exact time a ticket is created.

However I believe there are a couple of teams who get new tickets
reported to their mailing list. I think Marketing is one of these? Can
we start using the same function? I don't want new tickets to be
forgotten and leave the reporters without so much as a response.

Jef

[1] https://fedorahosted.org/design-team/ticket/171

[Máirín Duffy]

On Mon, 2011-02-07 at 17:47 +0100, Jef van Schendel wrote:
>  We've got two main ways to keep track of new tickets: we can
> either
>  check the Trac page every day or get notified on IRC. The first one is
>  boring, slow and clunky. The second one relies on people being present
>  in the channel at the exact time a ticket is created. 
We could also take time during meetings to go through some.

>  However I believe there are a couple of teams who get new tickets
>  reported to their mailing list. I think Marketing is one of these? Can
>  we start using the same function? I don't want new tickets to be
>  forgotten and leave the reporters without so much as a response. 
We have a separate mailing list for tickets so as to not clutter this
list -
https://admin.fedoraproject.org/mailman/listinfo/design-team-tickets

Does it make sense to have two or should they be merged?

~m

[Onyeibo Oku]

On 02/07/2011 07:50 PM, Máirín Duffy wrote:
>  We could also take time during meetings to go through some. 
well, that depends on how it is handled.  If we're going to be 
addressing lots of tickets in IRC meetings, the meeting will be 
over-burdened. If we're going to be announcing tickets like this:

'Tickets of the day  = #so-and-so'

... and then deal with the highlighted ticket #so-and-so during the 
meeting amidst other issues, then that's ok.  Summary: add between none 
and two in the agenda so we know what's coming.

> > However I believe there are a couple of teams who get new
> tickets
> > reported to their mailing list. I think Marketing is one of these? Can
> > we start using the same function? I don't want new tickets to be
> > forgotten and leave the reporters without so much as a response.
>
>  We have a separate mailing list for tickets so as to not clutter this
>  list -
>  https://admin.fedoraproject.org/mailman/listinfo/design-team-tickets
>
>  Does it make sense to have two or should they be merged?
>  
That depends on the frequency of Ticket additions.  If we're receiving a 
ticket or two in a week, then separating the two is pointless.  With 
increasing frequency, maintaining sanity and following threads on the 
mailing list will become challenging.  Then, in that case, a separate 
mailing list is ideal.  In reality, we don't get outrageous frequencies 
so I think a merger is appropriate

I don't always remember the trac ... merging the two will help me 
remember that we do have a 'line-up' of things to do (I don't know how 
the rest of the team see that).  I'll also be nice to get a report/table 
from trac at beginning of every month bearing the state of tickets.

>  ~m
>
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/design-team

[Jef van Schendel]

2011/2/7 Máirín Duffy <duffy(a)fedoraproject.org&gt;:
>  We could also take time during meetings to go through some. 
Onyeibo's plan sounds good to me. Right now it just seems like people
who ask for help sometimes never hear back from us. :(

>  We have a separate mailing list for tickets so as to not clutter
> this
>  list -
>  https://admin.fedoraproject.org/mailman/listinfo/design-team-tickets
>
>  Does it make sense to have two or should they be merged?
>
>  ~m 
Wow, I did not know that. I wouldn't mind if they were merged, since
it's much smaller than this list, but I can see why it was kept
separate.

/me subscribes

Jef

[Máirín Duffy]

On Mon, 2011-02-07 at 20:55 +0100, Jef van Schendel wrote:
>  2011/2/7 Máirín Duffy <duffy(a)fedoraproject.org&gt;:
>  > We could also take time during meetings to go through some.
>  
>  Onyeibo's plan sounds good to me. Right now it just seems like people
>  who ask for help sometimes never hear back from us. :( 

I wouldn't have a problem merging the two lists. Do you want to file a
ticket on Fedora infrastructure trac to make it happen? It should be
under the Fedora hosted category.

~m

[Onyeibo Oku]

On 02/07/2011 09:07 PM, Máirín Duffy wrote:
>  I wouldn't have a problem merging the two lists. Do you want to
> file a
>  ticket on Fedora infrastructure trac to make it happen? It should be
>  under the Fedora hosted category.
>
>  ~m 
How about having trac CC-to Design-Team list ... so that there the trac 
list retains its identity and record while remaining an integral part of 
the team (record keeping)?  Since the design-team handles those tickets, 
the Design-team mailing list should be more comprehensive and informative.

This approach ensures that you don't perform much administrative task in 
the future should the need for that 'sanity' arise. :)

[Jef van Schendel]

2011/2/7 Máirín Duffy <duffy(a)fedoraproject.org&gt;:
>  I wouldn't have a problem merging the two lists. Do you want to file a
>  ticket on Fedora infrastructure trac to make it happen? It should be
>  under the Fedora hosted category.
>
>  ~m 
Ok, so here's Ian's request for the design-team-tickets mailing list:

https://fedorahosted.org/fedora-infrastructure/ticket/1501

...Which makes me wonder if this is the right course of action. I have
the feeling that if we combine the two lists, we'll flip-flop on that
decision again in the future. :)

Instead, we could just advertise design-team-tickets a little more.
It's on neither of these pages:

http://fedoraproject.org/wiki/Design
http://fedoraproject.org/wiki/Join_the_Design_Team

So I can put something up there. Does that sound good?

Jef

[Onyeibo Oku]

On 02/07/2011 09:29 PM, Jef van Schendel wrote:
>  2011/2/7 Máirín Duffy<duffy(a)fedoraproject.org>:
> >
> > I wouldn't have a problem merging the two lists. Do you want to file a
> > ticket on Fedora infrastructure trac to make it happen? It should be
> > under the Fedora hosted category.
> >
> > ~m
>
>  Ok, so here's Ian's request for the design-team-tickets mailing list:
>
>  https://fedorahosted.org/fedora-infrastructure/ticket/1501
>
>  ...Which makes me wonder if this is the right course of action. I have
>  the feeling that if we combine the two lists, we'll flip-flop on that
>  decision again in the future. :)
>
>  Instead, we could just advertise design-team-tickets a little more.
>  It's on neither of these pages:
>
>  http://fedoraproject.org/wiki/Design
>  http://fedoraproject.org/wiki/Join_the_Design_Team
>
>  So I can put something up there. Does that sound good?
>
>  Jef
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/design-team 

our replies hit the server almost simultaneously
I considered this in my last response ...
Check it out.  What do you think?

[Emily Dirsh]

On Mon, 2011-02-07 at 21:29 +0100, Jef van Schendel wrote:
>  2011/2/7 Máirín Duffy <duffy(a)fedoraproject.org&gt;:
>  >
>  > I wouldn't have a problem merging the two lists. Do you want to file a
>  > ticket on Fedora infrastructure trac to make it happen? It should be
>  > under the Fedora hosted category.
>  >
>  > ~m
>  
>  Ok, so here's Ian's request for the design-team-tickets mailing list:
>  
>  https://fedorahosted.org/fedora-infrastructure/ticket/1501
>  
>  ...Which makes me wonder if this is the right course of action. I have
>  the feeling that if we combine the two lists, we'll flip-flop on that
>  decision again in the future. :) 
Looking at the trac list, we're really not getting more than one or two
tickets a week if that, so I don't think there's much chance that this
list is going to get cluttered up with tickets. So, why have to maintain
two lists? I'm pro combining lists.

>  Instead, we could just advertise design-team-tickets a little more.
>  It's on neither of these pages:
>  
>  http://fedoraproject.org/wiki/Design
>  http://fedoraproject.org/wiki/Join_the_Design_Team
>  
>  So I can put something up there. Does that sound good? 
Actually, it is mentioned on both pages, just not particularly
prominently. ;)

>  Jef
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/design-team
>

[María Leandro]

Hello team!

For me the tickets always where useful as they are.

We only need to be more active. FUDcon(tempe-panama) - FOSDEM take a lot of
time, also Fedora 15 atwork take a lot of time and effort and perhaps now
that almost all are done we will have more time to get back to the normal
tasks

Now, merge both lists would be incredible.

see ya :)


-- 
tatica
Maria Gracia Leandro
http://www.tatica.org
http://www.fedora-ve.org
http://proyectofedora.org
http://fedoraproject.org/wiki/MariaLeandro
LinuxUser= 440285
GPG Public Key: E1CDCC56
"Be yourself... Don't be anyone else"

[Fabian A. Scherschel]

With all due respect, I don't really need any more email. If people want to
get the tickets by mail they can subscribe to that list, where's the
problem?

Being subscribed to the QA list, their tickets spamming around in their
normal list is really annoying to me. :/

Fab



2011/2/7 María Leandro <tatica(a)fedoraproject.org&gt;

>  Hello team!
>
>  For me the tickets always where useful as they are.
>
>  We only need to be more active. FUDcon(tempe-panama) - FOSDEM take a lot of
>  time, also Fedora 15 atwork take a lot of time and effort and perhaps now
>  that almost all are done we will have more time to get back to the normal
>  tasks
>
>  Now, merge both lists would be incredible.
>
>  see ya :)
>
>
>  --
>  tatica
>  Maria Gracia Leandro
>  http://www.tatica.org
>  http://www.fedora-ve.org
>  http://proyectofedora.org
>  http://fedoraproject.org/wiki/MariaLeandro
>  LinuxUser= 440285
>  GPG Public Key: E1CDCC56
>  "Be yourself... Don't be anyone else"
>
>
>  _______________________________________________
>  design-team mailing list
>  design-team(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/design-team
>

[Onyeibo Oku]

On 02/07/2011 09:53 PM, Fabian A. Scherschel wrote:
>  Being subscribed to the QA list, their tickets spamming around in their
>  normal list is really annoying to me. :/
>
>  Fab 
This is just what I was afraid of.  I think we should be flexible with 
this.  Order is important and so is efficiency.  As things stand now, 
design trac is not popular.  Many design-team members don't even know it 
exists.  Some, that do, have conveniently forgotten.  I, personally, did 
not subscribe to it because I wasn't sure what traffic would be like. 
We all want to be able to follow or mails.

Now I see the traffic is manageable and that tasks hang on for long. 
Men, there are tickets that have been there since I joined the team.  I 
feel something about that (not that I can help it anyway ... crazy 
schedule) but a reminder goes a long way. We are not cyborgs.

The mean route would be to connect the two by one-directional CC.  The 
trac copies the Design-team so everybody knows what is waiting.  This 
shouldn't be a problem at the present rate.  When the ticket mails 
become and issue ... just remove the CCs and we can all have a rest of mind