[Trac] Re: Requirements for a new and improved Gantt plugin
On Behalf Of jevans Sent: Friday, April 10, 2009 11:46 PM To: Trac Users Subject: [Trac] Re: Requirements for a new and improved Gantt plugin To effectively display project progress, tickets must have estimated and actual times as in the TimingAndEstimation plugin. Is this sched vs execution (plan vs real progress ;) time? My bias is for the way we use it here: actual is how much time you've put in. Estimate is how long it's expected to take. When we accept a ticket, we put in an initial estimate. If we find out that the task is much more or less complex than originally believed, we revise the estimate. Time remaining is always estimate-actual. However, since this seems to be a matter of contention, I think I'd take Yogi Barra's advice (When you get to a fork in the road, take it.) and add a configuration option to specify whether remaining time is in the DB or must be computed. Personally, I'd like to see 3 values - the original estimate, the actual work time spent, and the remaining estimate. During development, I am most interested in the current estimated time remaining. After completion it can be useful to compare the time it actually took with the initial estimate. - jevans I am very glad to see the conversations on each of our visions of the proposed system. All of the time fields discussed are relevant. They are not all directly related. They each have their own value in existence and can be used in comparisons and relationships but they are different and should be kept separate. There is an initial estimate, time expended fact, time remaining calculation, and estimated time to completion, etc. Not all of these data points are 'owned' by the ticket responder. Tickets are used in many different ways: A ticket may be an execution token for a particular activity in an overall business solution program, an activity of a business program's project, a derivation of a project activity, or simply a step in a standard workflow. In each case, the data may be owned by someone other than the ticket responder (TR). Of course, the ticket responder may have envisioned data structures of time fields for activities she wishes to accomplish. The responder is given time data from previous stakeholders. The TR has other activities that may need to be addressed in parallel with the ticket at hand, thus there are time durations for ticket activities but there are also timing considerations to efforts of other, possibly, non-related tasks. For example, the TR may have many tickets each with expected durations and possibly iterations with others in subtasks of the ticket at hand. The TR is not responsible for the subtasks that others are performing on the ticket and thus can only produce data on her own activities and can only report or 'pass forward' data on subtasks. Since the TR has other responsibilities, 8 hours on a ticket doesn't mean it will get done today. It may have many other tickets ahead of it on that TR's input queue. So there are task specific durations and there are integrated schedule durations. All of which must be considered. So, when I am working at a company that has a business program to develop forestry products for South America and a business program to maintain existing supply chains for North Atlantic oil rigs, and there are projects under each of those programs for which I have tasks to perform in my domain of customer relations management, do I put timing data about my forestry program efforts in the ticket for the offshore rig program so I can keep them coordinated? As time goes on, the timing data will change. The business programs and projects are different, I am the only common stakeholder and through me they are related. If something changes in one, it affects the other. How many places do I put my timing data? When that data changes, where are all the places I have put that data that I will need to change? How much information do I want my issue tracker application to carry? Can I keep my timing data in a separate store and let the issue tracker/project management tool access my time data store so the most up-to-date data is available to tracking concerns? In such a matrix organization, there are many people in my same situation and their commitments affect project schedules across the enterprise. I know my vision is simplistic in comparison to coordination efforts of many others, but I would like to make sure that the lower level concerns are at least viewed if not addressed. Ray __ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information which is confidential to, and/or privileged in favor of, CDI Corporation or its affiliated companies (CDI) or CDI's customers. Any review, use, reproduction,
[Trac] Re: Requirements for a new and improved Gantt plugin
Joseph, Ray wrote: ... I am very glad to see the conversations on each of our visions of the proposed system. A flexible system can serve many needs. ... The business programs and projects are different, I am the only common stakeholder and through me they are related. If something changes in one, it affects the other. How many places do I put my timing data? My goal would be only one place! When that data changes, where are all the places I have put that data that I will need to change? How much information do I want my issue tracker application to carry? Can I keep my timing data in a separate store and let the issue tracker/project management tool access my time data store so the most up-to-date data is available to tracking concerns? In such a matrix organization, there are many people in my same situation and their commitments affect project schedules across the enterprise. I work in a multi-project matrix organization as well. I'm very sensitive to the fact that one project can affect another in unexpected, undesireable, and sometimes unavoidable ways. The key, to me, is that you *know* those effects and can work around them. Being surprised on the day of a milestone is not good. I know my vision is simplistic in comparison to coordination efforts of many others, but I would like to make sure that the lower level concerns are at least viewed if not addressed. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Dynamic pull-down population
On Fri, Apr 10, 2009 at 08:22:20AM -0400, Ted Gifford wrote: How would something like this work with queries/reports? *That's the main issue I haven't been able to resolve in trying to develop this sort of functionality. *The simple answer would be to store the computed value of the field in Trac's DB, but how would it know when to update the value? There are two answers that I have been thinking about, neither one of which I'm fully satisfied with: How about defining several default policies for cache invalidation (such as those listed below), and then allow plugins that define computed fields to provide (via another interface?) their own policy own when to recompute the field? Ted Yeah, that would be the ultimate goal (though maybe with a callback instead of an interface?). Jeff * *1. The more robust answer (though maybe still not robust enough): *Whenever a /query or /report URL is hit, compute all of the computed fields, as well as doing this every time a /ticket URL is hit. *The values are stored in the the Trac DB, specifically inside the ticket-custom table. This would be horribly slow for any sizable number of tickets. *2. The less robust answer: *Only do this when individual /ticket URLs are hit. *The /query or /reports get cached values. 2. is probably required, at least for my use-cases. You could imagine doing something more intelligent too: ** caching fields every N minutes, e.g. with a cron job (if there's not a pluggable cron plugin -- I thought there was but have since been unable to find it -- it would be easy to write). ** For /queries or /reports, filter by other criteria to get back the desired ticket set, then compute the computed fields for the remaining tickets and doing additional filtering by these computed values. ** For each computed field, cache them on certain events. *For instance, some might only need to be cached when the ticket is updated (method 2. above). *Others might need to be updated on repository commits. Etc. ** Some combination of the above. I admit there's no easy answer for the general case. *The event-trigger criterion appeals to me the most, but its easy to see times when it wouldn't work. *For instance, if a field requires data from an external service, you won't know when this data will be updated in general. Still, I'm encouraged to try to get something working :) Jeff -- * * * * * + * * * * * * * * * * * - --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Email notification sorted by component
On Sun, Apr 12, 2009 at 5:53 PM, rupert 78 zmo.rup...@gmail.com wrote: Hi to all, im pretty new of Trac. There is a project now divided in two team developers, Component1 and Component2. About notification, Component1 doesn't want to recieve email about Component2 ticket changing and the other way round. Is it possible link each Component to a different email address? Using coponent's owner attrib ? -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
On Mon, Apr 13, 2009 at 8:16 AM, Chris Nelson chr...@sixnetio.com wrote: Joseph, Ray wrote: ... I am very glad to see the conversations on each of our visions of the proposed system. A flexible system can serve many needs. :) ... The business programs and projects are different, I am the only common stakeholder and through me they are related. If something changes in one, it affects the other. How many places do I put my timing data? My goal would be only one place! Even if it changes from one company to the other. -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Email notification sorted by component
Thanks for your reply, im too new to trac to understand your answer in a useful way. What i'm doing is play with the AnnouncerPlugin on 0.11. I'm working to make it works in the way i need and as clean as possible. Mabye its not much frequently divide two profile inside of a project. regard rupert Olemis Lang wrote: On Sun, Apr 12, 2009 at 5:53 PM, rupert 78 zmo.rup...@gmail.com wrote: Hi to all, im pretty new of Trac. There is a project now divided in two team developers, Component1 and Component2. About notification, Component1 doesn't want to recieve email about Component2 ticket changing and the other way round. Is it possible link each Component to a different email address? Using coponent's owner attrib ? -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: -- View this message in context: http://www.nabble.com/Email-notification-sorted-by-component-tp23015702p23024645.html Sent from the Trac Users mailing list archive at Nabble.com. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Requirements for a new and improved Gantt plugin
This has already seen enough different takes on what it should do for me to say it shouldn't be part of the core, but some set of coordinated plugins to achieve the final goals Similar to how several tools have taken data from the TimeAndEstimation plugin to achieve the end goals As for the above comment about Eclipse. Actually, the reason I stopped using Eclipse was as it matured, enough specific preferences/ usage expectations were added to the core, that it was more productive to go back to Vi and command-line scripts for development. Anyway, I am curious to see how this goes, there are some specific things from the PM side I would love to pluck out and use in my trac sites. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Email notification sorted by component
On Mon, Apr 13, 2009 at 11:33 AM, rupert 78 zmo.rup...@gmail.com wrote:
Thanks for your reply,
im too new to trac to understand your answer in a useful way.
AFAIK if you set an owner for a component then all notifications are
sent to that specific person ... isn't it?
{{{
$trac-admin component chown component1 user1
}}}
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: SubversionException: (Failed to load module for FS type 'fsfs', 160033)
I have the same error. It occurred after I upgraded subversion to v1.6.1. I am running Gentoo. Anyone else find this problem? Mike --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: SubversionException: (Failed to load module for FS type 'fsfs', 160033)
mslinn wrote: I have the same error. It occurred after I upgraded subversion to v1.6.1. I am running Gentoo. Anyone else find this problem? Apparently... see http://trac.edgewall.org/ticket/8206 Besides, if anyone else has seen the following error message Couldn't perform atomic initialization, please mention the platform you're using on http://trac.edgewall.org/ticket/8199, I was probably wrong when I thought this happened only on FreeBSD. Seems we can now answer that e-mail from a few days ago, asking if it was OK to use Subversion 1.6 with Trac ;-) -- Christian --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] ANN: TracPyTpp, «enhancing» TracDotOrg them e
The last weekend I made a few changes to PyDotOrg theme. It's been installed in a public site [1]_ so I'd appreciate if you could please provide some feedback in order to enhance it further. Every comment will be welcome. It borrows features from PyDotOrg theme and also from The Python Papers design. If you like it (I mean enough people ;) and a few things are ok, then I'll publish it in Trac-Hacks in the next few days. Hope you like it ... ;) .. [1] Simelo's projects site (https://opensvn.csie.org/traccgi/swlcu/wiki/WikiStart) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: Email notification sorted by component
Thanks for your reply.
This what i've done:
- Installed AnnouncerPlugin (because this provide good notification
managment and easy esclude recieving email from area doesn't in your
intresting);
- Create 2 fake users who have link of mailing list as e-mail contact;
- Setting these 2 users as component owner to recieve notification when
something is changed in their component area (AnnouncerPlugin);
It works.
The only unclean thing is the reply_to, because i think you can only
setting one istance for sending. Then in the reply field i ve added two mail
address, so when i do reply i ll simply remove the address not needed
.
e.g: smtp_reply_to = mailingli...@bye.it, mailingli...@bye.it
Better configuration will be notified
Regards
Rupert
jevans wrote:
On Apr 13, 1:05 pm, Zmo rupert_pupkin zmo.rup...@gmail.com wrote:
Goal is:
when change tickets about Component1 send notification to
compone...@mailinglist
when change tickets about Component2 send notification to
compone...@mailinglist
On Apr 13, 7:29 pm, Olemis Lang ole...@gmail.com wrote:
On Mon, Apr 13, 2009 at 11:33 AM, rupert 78 zmo.rup...@gmail.com
wrote:
Thanks for your reply,
im too new to trac to understand your answer in a useful way.
AFAIK if you set an owner for a component then all notifications are
sent to that specific person ... isn't it?
{{{
$trac-admin component chown component1 user1
}}}
Hi,
If you set the component owner to an artificial user whose email is
actually a mailing list, the list should receive notification of new
tickets.
But then you may want to reassign tickets to individual owners to work
on them. You could at that point add the component's mailing list to
the cc field for each ticket if you want everyone on that team to
continue receiving updates on each ticket. A bit manual but should
work?
- jevans
--
View this message in context:
http://www.nabble.com/Email-notification-sorted-by-component-tp23015702p23030473.html
Sent from the Trac Users mailing list archive at Nabble.com.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Trac
Users group.
To post to this group, send email to trac-users@googlegroups.com
To unsubscribe from this group, send email to
trac-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~--~~~~--~~--~--~---
[Trac] Re: ANN: TracPyTpp, «enhancing» TracDotOrg theme
On Apr 13, 2:04 pm, Olemis Lang ole...@gmail.com wrote: The last weekend I made a few changes to PyDotOrg theme. It's been installed in a public site [1]_ so I'd appreciate if you could please provide some feedback in order to enhance it further. Every comment will be welcome. It borrows features from PyDotOrg theme and also from The Python Papers design. If you like it (I mean enough people ;) and a few things are ok, then I'll publish it in Trac-Hacks in the next few days. Hope you like it ... ;) .. [1] Simelo's projects site (https://opensvn.csie.org/traccgi/swlcu/wiki/WikiStart) -- Regards, Olemis. Blog ES:http://simelo-es.blogspot.com/ Blog EN:http://simelo-en.blogspot.com/ Featured article: Looks good. I don't like that the meta-nav bar scrolls inside the page. But tickets, roadmap, and change history look good as well. While you're messing with the wiki, maybe you could add some instructions on how your TracGViz tool works with wiki-formatting and the exposed properties of trac it supposedly makes available :D The examples only show how to embed the widgets with static arguments. Nice work --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Trac Users group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
