anonym: > intrigeri: >> That's not all. I'll still need to follow changes to subsets of our >> Redmine. I don't know for sure since I've not clearly identified my >> needs ye, but I guess I'll have to improve our Redmine toolbox to make >> this possible. I suspect that some of you are in the same situation. >> Tell me your needs (privately or on some dedicated blueprint) and I'll >> try to take them into account while looking for solutions to mine. > > Could you please clarify what you mean here? Obviously it's not > sustainable to rely on a single person (you) following all of Redmine, > but in order to not have tickets be forgotten or go unnoticed, we need > some processes and tools to deal with it instead. I assume this is what > you are getting at, and that you already has some ideas for it. Please > share!
Frontdesk is already responsible for doing something with tickets in "Status: New" (I understand that this is forced for people who don't have a special role). Maybe we could have other mechanisms to spread the responsibility of tracking what's happening on Redmine. As said to intrigeri in private, for example I wouldn't mind being responsible for tracking "End-user documentation" and "Website" tickets for example. _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
