Hi there, My personal view on the issues at hand is simple. We have all been taught to support our leaders and build up the Kingdom. While at times things are not going as fast as we might like them to go I have taken a simple view at heart.
1. If there is something that you think or know is broken report it, but give a bit more detail describing how you think the problem could be solved. Eg. If you know some functionality is broken write up test script that can be followed to reproduce the problem. 2. If it is more of a feature request like described in the email have patience, but don't give up on it. If you think it is taking too long just email again. After all we are imperfect humans working in an imperfect world striving to be perfect ;) 3. If you have programming experience stubbing out a runnable prototype could prove to be helpful. If you don't have programming experience just draw/sketch or describe in detail what you want changed/added. After all a picture says more than a thousand words. Kind regards, ---- Manfred Riem [EMAIL PROTECTED] http://www.manorrock.org/ > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ed Hammond > Sent: Saturday, January 14, 2006 12:22 PM > To: [email protected] > Subject: [Ldsoss] Re: MLS Bugs and Discussions > > See the official link: > http://mls.lds.org/ > Also, for MLS related discussions, the better list to > subscribe to for ongoing dialog is: > http://www.MormonsToday.com/ldsclerks/ > This is where clerks discuss such problems, etc. > > There are precious few development resources supporting MLS > and the pressure on them is great, so unless it is painful to > CHQ, "priorities" delay resolving a many items. > I've reported things like the stake's view of membership is > inaccurate relative to what the units have, even after forced > syncs from both sides. The problem remains broken even a > year after submitting the problem report. > > As I tell folks > "... it is what it is, and it is better than it was, so be > grateful ..." > Ed > > P.S. Fully concur with the concern about exporting all the > MLS data for Emergency Preparedness. MLS has native support > for such and (for the most part) it automatically feeds the > stake the info via secure channels. I'd recommend you > investigate that avenue. > Again, "ldsclerks" has a better audience for that discussion. > > >------------------------------------------------------------- > --------- > >Message: 1 > >Date: Fri, 13 Jan 2006 15:04:26 -0800 (PST) > >From: "Greg Hart" <[EMAIL PROTECTED]> > >Subject: [Ldsoss] MLS/LUWS Bugs and Feature Requests > > > >Hi All- > > > >Is there a good place to send these? Our unit has been > sending them to > >"[EMAIL PROTECTED]" (with the blessing of our Stake Admin). > >Honestly, it feels like a black hole. Is there a better course of > >action? Does HQ have a system for receiving and processing user > >reported bugs and feedback? > > > >Thanks, > >-Greg > > > >------------------------------ > >Message: 2 > >Date: Fri, 13 Jan 2006 17:08:00 -0600 > >From: "Neeland, Steve" <[EMAIL PROTECTED]> > >Subject: RE: [Ldsoss] MLS/LUWS Bugs and Feature Requests > > > >And bugs a plenty there are. We are on v2.3.2 and it got > worse. I've > >got newborns getting assigned to the Young Single Adults > Sunday School > >class (I guess that's sort of accurate) and several $100,000 extra > >getting reported in a budget area if you print it by previous month. > >Hopefully your issues and those others submitted get addressed soon. > > > >Steve > > _______________________________________________ > Ldsoss mailing list > [email protected] > http://lists.ldsoss.org/mailman/listinfo/ldsoss > _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
