Re: [Printing-architecture] More on What/How to Do

[Till Kamppeter <till.kamppeter@gmail.com>]

I think that is a good idea. Let's make it our principal agenda item on 
today's architecture telecon.

    Till

Petrie, Glen wrote:
> Hello All,
> 
> Yesterday I gave some of my opinions and suggestions on what we might do 
> to get things rolling again for the US/European Teams but I believe now 
> what is more important and I did not realized it until later was the 
> question of "How to Do It".  (Whatever "it" is.) 
> 
> In the past we had weekly meetings and could, at the best of times, move 
> forward at a good pace; however, it seems harder and harder to recreate 
> that same momentum.   Face-to-Face meetings, with sufficient frequency, 
> are impossible for most of us due to travel restrictions.  Therefore, 
> what I would to propose is having regular 2 or 3 day telecom meeting 
> with the express goal of working on architecture or software development 
> activities.  I believe that many our companies would give us the time to 
> attend this type of working meetings if no travel is involved.  But I 
> would like to emphasis that these meeting must stay away from being 
> status meetings, general discussion, discussing / creating slides or any 
> other activity which in not a direct development function.  Otherwise, I 
> believe the idea and the meetings will degenerate into discussion 
> meetings.  Below is more on my idea, I would be interested in hearing 
> what you think or other suggestions for "how to do"it"".
> 
> 
> Glen's Proposal
> 
> Multi-Day Telecom Technical Meetings
> 
> Leader:         Rotate between active members (Glen, Norm, Ira, Till, 
> Wendy, Claudia, ????)
> 
> Duration:       2 days (I would really like to see 3 days)
> 
> Frequency:      Once a month (that is only 12 times a year)
> 
> Start Time:     9:00am          Eastern Time
> 
> Lunch Time:     11:45am to 1:15pm       Eastern Time
> 
>                         (long lunch to check on other work to be done at
>                         our offices)
> 
> End Time:       5:00pm                  Eastern Time
> 
> Agenda: Everyone Sign in        9:00am
> 
>             Agenda Check            9:15am
> 
>             Technical Work          9:30am
> 
>             Lunch                   11:45am
> 
>             Technical Work          1:15pm
> 
>             Daily Summary           4:30pm
> 
>             End                     5:00pm
> 
> Pre-work:       2 weeks before meeting, members reminded of their 
> assignments
> 
>                 (remember none of us will work on it until we're bugged)
> 
>                 1 week before meeting, members must submit their 
> assignments to the mail list
> 
>                 (remember the rest of us need time to review content 
> before the meeting, not at the meeting)
> 
> How to make this happen
> 
> 1.      Discuss at next architecture meeting.
> a.      Can SUN or IBM support such meetings with their toll free 
> call-in numbers?
> b.      What kind of sharing tools should we use?
> c.      What is the "it" we should work on
> i.      Architecture details
> ii.     Thin Thread the Architecture
> iii.    JTAPI
> iv.     Others
> d.      Set up schedule
> i.      Realizing that not everyone can attend each telecom
> 1.      But they can do pre-work and follow ups
> 
>                
> 
> */Rgds,
> /**//**/Glen W. Petrie/**//**/
> /**/Epson Imaging Technology Center
> 2580 Orchard Parkway, Suite 200
> San Jose, CA, 95131
> Voice: 408.576.4131  Fax: 408.474.0511 /*
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.freestandards.org
> http://lists.freestandards.org/mailman/listinfo/printing-architecture