Pat,
That's a good suggestion. However, for the discussion to bear useful
fruit, the participants need an
anchor to work from. Gen'ing up an API discussion has only partial value
with respect to where the
FH Dept is going if the folks on this list dont know understand what has
been discussed, what is up
for consideration, and product roadmap.
Ideation needs a focus, and a specific purpose.
So, having said that, are there any particular items that can be open
for debate in this forum? AND,
is there any history that can be shared to qualify those items?
...Paul
Pat Eyler wrote:
On Fri, 14 Oct 2005, Paul Penrod wrote:
[deleted]
For example, the duplication of effort in both the IGI and temple
work. My father submitted work
for a realtive back in the 1970's that has been done 9 times since,
and in all those cases, some of
the information is wrong or missing. Is the Church addressing this?
Yes, finally. Pres. Hinckley
found it important enough to announce it during conference. Will they
succeed? Eventually, but
don't hold your breath. It's a simple problem to comprehend, but it's
the issue of scalability that
gives it a new dimension beyond what they've dealt with before. So,
it will take some study, and
some politicing and the usual mating elephant dance before we see
anything. That's the way of
things.
If they offer an API - take it for what's it worth and do something
useful, but don't expect it to
be around forever. Software is mearly a work in progress. It is never
really "done".
Actually, it would be good to go beyond passive acceptance here.
Think about what should be in the API, discuss it (use this list to
keep the discussion available) -- the church might not use all of the
ideas that come up, but they will be seen, discussed, and (maybe) used.
There are a lot of people from the Family and Church History
department on this list now. I've heard it mentioned in more than 3
discussions/meetings today alone.
...Paul
-pate
Pat Eyler
Infrastructure Engineer, FCH
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
