tutos-devel Mailing List for TUTOS
Projects / CRM / PLM / Calendar / Tasks / SCRUM / Test / Inventory
Brought to you by:
gokohnert
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(16) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
(10) |
Aug
(4) |
Sep
|
Oct
(4) |
Nov
(1) |
Dec
(7) |
2002 |
Jan
(1) |
Feb
(8) |
Mar
(7) |
Apr
(20) |
May
(1) |
Jun
(5) |
Jul
(27) |
Aug
(18) |
Sep
(55) |
Oct
(13) |
Nov
(27) |
Dec
(20) |
2003 |
Jan
(23) |
Feb
(40) |
Mar
(20) |
Apr
(10) |
May
(12) |
Jun
(8) |
Jul
(11) |
Aug
(7) |
Sep
(3) |
Oct
(2) |
Nov
(1) |
Dec
|
2004 |
Jan
(2) |
Feb
(34) |
Mar
(10) |
Apr
(11) |
May
(5) |
Jun
(6) |
Jul
(12) |
Aug
(7) |
Sep
(16) |
Oct
(25) |
Nov
(8) |
Dec
(2) |
2005 |
Jan
(17) |
Feb
(2) |
Mar
|
Apr
(5) |
May
(5) |
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2007 |
Jan
|
Feb
(2) |
Mar
(1) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
|
1
|
2
|
3
(2) |
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
(3) |
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
(1) |
24
|
25
|
26
|
27
|
28
|
29
|
30
|
|
|
|
From: Jeroen B. <jb...@i2...> - 2004-06-23 11:12:24
|
Hi all, I know I have done nothing in the recent past coding TUTOS and stuff. Oh, eh, well, I did succeed in getting it some dutch media attention. However, I have some ideas I like to share and hope for some input. TUTOS is with regards to functionality pretty complete but I have been missing one thing and that is 'lead management'. I have been thinking about this for some time and here's what I came up with. If there is to be a module 'leads' it should be queue oriented. The place of a 'lead' within the queue is dependant upon: -date of last contact -estimation of succes rate -number of recent projects/products the client has already purchased. Some calculation should be done here. The 'leads' page shows customers with their calculated urgency with which you should contact them again. In my business a 14 day interval is fine but I can image there are other businesses where this is shorter or longer so that should be a customizable variable. So If I called them yesterday, they go back 13 days in the queue, unles I entered another value on the contact form ( a subform with all the contacts that we've had). Maybe I want to call the client in 3 months time because I don't judge this as a high-potential right now. Also, there are clients I have sold something to in the past and I just like to checkup on them and let them know I still exist. Okay, what are you ideas? greets to all -- Jeroen Baten | EMAIL : JB...@I2... ____ _ __ | web : www.i2rs.nl | )|_)(_ | tel : +31 (0)492 369 003 _|_/_| \__) | fax : +31 (0)492 369 433 Jan van Amstelstraat 26, 5421 ES, Gemert, the Netherlands |
From: Gero K. <gok...@us...> - 2004-06-14 19:40:49
|
Carl Zmola wrote: > Is there any active tutos development going on. Sure ! Most things happen behind the scenes and you will only see the activities in the CVS. There is a 1.2beta waiting for finalization and we already started a 1.3 development tree also there is a 2.0 branch which will try to use smarty as a temnplate engine. Gero |
From: Dimitri F. <dfo...@cv...> - 2004-06-14 09:01:37
|
Hi, The TUTOS development is active. Actually Gero is stabilizing the 1.2 branc= h=20 and caring for 1.3, and I'm working on a TUTOS 2.0 version. This will mean a lot of work to merge head and 2.0 branches, and then of=20 course new ideas to be implemented. Some of the ideas I have concern database management, where we could use=20 templates (yes, again) in order to manage a dedicated set of query for each= =20 supported RDBMs (that would allow for supporting mysql and at the same time= =20 using stored procedures and subqueries with postgresql). Regards, =2D-=20 Dimitri. http://dim.tapoueh.org UNIX n'est pas aim=E9 des utilisateurs car avec UNIX, un incomp=E9tent passe vraiment pour un incomp=E9tent. |
From: Carl Z. <ca...@ve...> - 2004-06-14 04:24:09
|
From: Oksana Y. <ok...@at...> - 2004-06-03 22:50:32
|
I forgot one more thing. Page Resource usage: If you'd like to follow my idea (see previous email), it'd be better = to use=20 'Volume done' instead of 'Volume' (planned volume) as a value in brac= kets for=20 tasks. Cheers. P.S. I'll submit this patch to sourceforge.=20 --=20 Oksana Yasynska Research Analyst/Web Database Developer Athabasca University 1 University Drive Athabasca, Alberta T9S 3A3 Canada Phone: 1-780-428-7269 Cell: 1-780-504-0589 Email: ok...@at... __=20 This communication is intended for the use of the recipient to wh= om it is addressed, and may contain confidential, personal, and or priv= ileged information. Please contact us immediately if you are not the int= ended recipient of this communication, and do not copy, distribute, or = take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- |
From: Oksana Y. <ok...@at...> - 2004-06-03 20:55:14
|
Hi list, Statement: Resource usage page shows events from the Calendar (e.g.=20 meetings) and tasks which have=20 'SCHEDULED start date<end of the month'=20 or =20 'SCHEDULED end date>begin of the month'.=20 Problem: I personally don't always specify scheduled start and end days for my= tasks.=20 So, when I start working on the task which doesn't have scheduled sta= rt date,=20 I'm not able to see it on my Resource usage page. Solution: Don't you think it'd be more handy to show (at Resource usage page) t= asks for=20 which=20 'REAL start<end of the month'=20 or=20 'REAL end>begin of the month'. Any comments? --=20 Oksana Yasynska Research Analyst/Web Database Developer Athabasca University 1 University Drive Athabasca, Alberta T9S 3A3 Canada Phone: 1-780-428-7269 Cell: 1-780-504-0589 Email: ok...@at... __=20 This communication is intended for the use of the recipient to wh= om it is addressed, and may contain confidential, personal, and or priv= ileged information. Please contact us immediately if you are not the int= ended recipient of this communication, and do not copy, distribute, or = take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- |