API Update: Momentum at the Official level

[AJ ONeal (Home)]

I've been asked to keep my public update high-level, so I'm not going to go into the detail, but here's the overview:

The concerns that we're trying to address have been heard, discussed, validated, and are on a path to action. There are managers that see the value and are willing to take on the responsibility. I'll be kept in the loop on progress at a high-level and I may have opportunity for involvement, but that's just a maybe. I'll in-turn make some high-level updates as appropriate.

ldsconnect.org will not continue as I have created it currently. I have some ideas of how to modify it to make it still useful while staying within the bounds that have been set, but don't expect to see an update on that before September.

It'll be slow and sparse but, honestly, I couldn't be happier. The positive official involvement over these concerns is truly the best outcome for the project.

AJ ONeal
(317) 426-6525

[K Anderson]

I don't know anyone at that level and I'm located in California, but if there is anything from a software architecture or engineering level you need, let me know. I'd be happy to add my efforts to the cause.

[KC Erb]

This is all excellent news. Just bumped into the project and wanted to say Hi, and I'm here! About 4 years ago I knew nothing about programming and hated what I did know. Then I became an EQP and realized that I needed software tools and started learning.

The past 4 years has been life-changing in that I've learned that excellent software development is a deep-seated passion that I was born with and the common thread through all of my projects has been my callings. I'm very excited about a church-approved OAuth 3.0 based API. That would be the most important thing in my life (well maybe after my testimony, family etc. but you know what I mean)!

Maybe I'm a little giddy and talking nonsense but that's my self-intro to the group.

Now I have a couple of questions about the post

1.

I've been asked to keep my public update high-level, so I'm not going to go into the detail

I don't know what this means. Can you rephrase? Does keeping something high-level mean only talking about it with high-level lds-tech folks?

 

2.

What is the next step here? I see a kickstarter, I see this google group, I see the lds.io website what are the plans? I get the impression that you had some apps out there that were using the church's undocumented API (https://www.lds.org/mls/mbr/records/member-list?lang=eng) and decided to put them together into your own documented API (https://lds.io/api/ldsio/<accountId>/me). 

So is the goal going forward for this lds.io approach to go forward and get rewritten for church sanction?

Is the goal for the church to produce their own developer API?

Should I put projects that would use this API on hold or start building them?

If it's on hold do you have an estimate for how long? You mentioned September is that still the right timeline?

How does ldsconnect.org factor into all of this?

I'd be happy / able to update lds.io with a FAQ page addressing these if you'd like.

[Daniel King]

Awesome news. KC told me about this.  Exciting stuff.

Is there a need for programmers to help with the project?  I would love to help anyway I can whether it's through programming/testing etc.  Please let us know and keep up the good work.  

[John Norton]

So is this thing dead?

On Wednesday, July 15, 2015 at 1:11:34 PM UTC-6, AJ ONeal wrote:

[AJ ONeal (Home)]

The project is not dead, but sleepeth.

--
LDS I/O on Meetup: https://www.meetup.com/LDS-IO/
---
You received this message because you are subscribed to the Google Groups "LDS I/O" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lds-io+un...@googlegroups.com.
To post to this group, send email to lds...@googlegroups.com.
Visit this group at https://groups.google.com/group/lds-io.

For more options, visit https://groups.google.com/d/optout.