Sorry for top-posting here, but my comment is a general response to the
interaction I'm seeing here. I'm encouraged to see this openness between
the development efforts of the church and the LDS tech community here. My
feeling is that the perception earlier of many was that trying to get any
feedback or suggestions into church software development was a big black
box. It seems that is changing, which is very refreshing.
I've thought to myself that the church unlike other business entities
doesn't really have any trade secrets it needs to be hiding so I would
hope that development processes could be a bit more transparent, and open to
the community. It seems like that is happening.
Woohoo!
As a suggestion to those developing the stake and ward websites, I would
love to see a system integrated into those websites that would allow for
the tracking of YM Duty to God and YW Personal Progress tracking. Such a
system would allow YM and YW and their parents to login and update which
requirements they have completed. It would allow stake and ward youth
leaders to login and see progress being made. When the Deacons quorum
advisor would login he would be able to see the young men under his
stewardship and their progress. Bishoprics would be able to see all the
information for thier wards, and likewise stake presidencies for their
stakes. On a larger scale, such a system could potentially provide the
General Authorities with a lot of useful information on how these programs are
funtioning church-wide.
-- Dan
On Tue, 7 Feb 2006, Peter Whiting wrote:
On Mon, Feb 06, 2006 at 02:36:25PM -0600, Stacey wrote:
Given that an almost working calendar export feature is
available from the ldschurch guys I am planning to replace my
script with an instruction page on how to export calendars
directly.
We pushed a change to production that should make the calendars
usable in ical (needed a carriage return on the last line of the
file.) I've been told there are some issues with import into
koffice (apparently with commas in the body of the text) but I
don't think it makes sense for us to start mangling the content
of the description to accommodate the idiosyncrasies of different
calendar applications - rather we'll leave those for filters
executed by the end-user.
Please provide feedback, especially if you see areas where
the ical and/or vcal outputs don't adhere to their specs.
pete
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
_______________________________________________
Ldsoss mailing list
[email protected]
http://lists.ldsoss.org/mailman/listinfo/ldsoss
