|
I agree. If you look at the three fold mission of the Church, one does not see the statement: "Write Software". The fact the Church is even involved to any extent in technology is a byproduct of the fact that good tools make work easier. The computer, for all it's glitter and warts is a good tool for repetitive tasking. As Shane has pointed out, the Church is behind the curve on OSS, but is making steps to catch up, as there is perceived value. I also agree, you can not sit around looking to them for leadership in this matter. In the D&C, the Lord was quite plain about the fact the saints should be "going about doing good", and "not to be commanded in all things". If you do something good, and they like it, they will come. I am somewhat reminded of my sister's ward in S. Jordan where there were young marrieds that pester the bishop as to what kind of furniture to buy, what color to paint their house, or what to name a newborn. That's a bit too dependent in my book, but I use it to illustrate the point of the question raised about leadership. I, myself, in a previous thread have suggested that someone from HQ take the lead on the scout project - but, did so in the vein that we have to establish the boundaries to the initial problem/ request, so that people can speak to it properly. That make sense irrespective of what method the Church uses to address the matter, as they have to understand the problem internally, before they can focus resources of any kind effectively - be internal or not. So, my suggestion, to echo Shane's is to go do something useful with your time, and don't look to be directed in the matter until the need for your services is there - and it will be. Patience is a virtue - though not a timely one. Shane Hathaway wrote: Ed Ashton wrote: |
_______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
