ODK 1 Developer Calls

The full (but short) notes from our recent call are here: https://docs.google.com/document/d/1hszoTRzWG5W04JXgcBzE7BcdEZGB75lA8tftTNZ5lzA5.

For those who just want the highlights:

  • We had about 15 participants from Nafundi, Ona, Enketo, Carter Center, DIAL, Redcross, and of course individual contributors. It's a nice increase over the first call.

  • We covered the status of the action items from the last meeting. We've had big wins in code review and the docs website. Not so big wins on ODK Aggregate and making real progress on the technical steering committee and a technical roadmap. @yanokwa vowed to make progress on those fronts. Of course, he vowed that on the last call, but he was more vowey this time.

  • On the docs front, @adammichaelwood explained the scope of docs.opendatakit.org (anything that has to do with installing, using, developing on ODK) and how developers can contribute (read the docs and file issues).

  • There was great knowledge sharing from @martijnr on the importance of external secondary instances and a good question and answer session about why it was never implemented properly to begin with and how we can prevent that class of mistakes.

  • @Shobhit_Agarwal reported on his Google Summer of Code experienced and said he planned to continue working on ODK.

  • @tomsmyth discussed his feature request of setting arbitrary key-value pairs under the Form Metadata. More at Custom form metadata

The next call is: October 4, 2017 from 14-15 UTC

@ln and @yanokwa will be on a field visit to Somalia(!) during this time. We'll try to join, but there might not be a great connection.

Who would like to lead call? And who would like to take notes?

Some potential topics:

3 Likes

I’ll be glad to lead it.

4 Likes

I also would be happy to talk about repeat instance naming.

2 Likes

Quick alert for those who participate in the developer calls. The PMC made good progress on putting together governance for a technical steering committee. We've put that document at Proposed governance for ODK 1 Technical Steering Committee and we'd love your feedback!

Thank you @dcbriccetti and @tomsmyth!

This issue may also help provide context for repeat instance naming: https://github.com/opendatakit/collect/issues/183

Some other tentative agenda items:

@dcbriccetti, do you want to set the agenda in https://docs.google.com/document/d/1hszoTRzWG5W04JXgcBzE7BcdEZGB75lA8tftTNZ5lzA/edit#?

Somaliland has been great so far and it's really impressive to see how many people here know of and use tools in the ODK ecosystem. It seems @yanokwa and I will likely be able to join the call.

Let's do a quick poll to see who will be there

  • I will be on the call Wednesday October 4, 2017 from 14 to 15UTC (see in my timezone)
  • I can't make it this time but am interested in future calls

0 voters

Please join at https://www.uberconference.com/opendatakit.

We will use the same notes document: https://docs.google.com/document/d/1hszoTRzWG5W04JXgcBzE7BcdEZGB75lA8tftTNZ5lzA/edit#heading=h.o59rk99q6syt

I think it's just plain https://www.uberconference.com/opendatakit ...

Notes from the Oct 4 Developer Call
See the agenda for details.
Dave Briccetti and James Knight described work they are doing that led to a plan for them to create learning sessions on performance measuring and improvement, and Android testing, respectively.
David McCann discussed his work with Briefcase and Aggregate.
Tom Smyth discussed a proposal to better handle repeat instance naming.
Ronald Munjoma updated us on the Outreachy project.
Yaw discussed the proposed governance for the ODK 1 Technical Steering Committee
Action:

2 Likes

Thanks @dcbriccetti for leading the meeting today! :trophy:

Wow I really wasn't aware of ODK Developer calls. Got here by chance. I really love the idea and will surely participate in the next call. Big up to you guys. This is great @yanokwa

4 Likes

The first Wednesday of the month is quickly approaching! I'm looking forward to hearing everyone live for our next call on Wednesday November 1st 14 to 15UTC (see in my timezone).

Does anyone want to lead and/or have topics they want to make sure we discuss?

Here are some things on my mind:

Let's do a quick poll to see who will be there

  • I will be on the call Wednesday November 1, 2017 from 14 to 15UTC (see in my timezone)
  • I can't make it this time but am interested in future calls

0 voters

I may be en route to the airport to drink Txakoli with @ggalmazor but I will at least be listening in.

Could you add a little 30 second slot for me to remind everyone about the testing workshop next Wednesday?

2 Likes

So jealous!! :clinking_glasses:

Yes, absolutely on the testing workshop plug. Is the beginning or the end more convenient? (For the interested -- ODK Testing Workshop 2017-11-08)

I know as soon as I say one way or the other I'll be wrong, but I think towards the end would be better.

Not that it super matters -- jump in when you can!

Today is a holiday in Spain and I have the family over for lunch... I could hop in for 15 minutes and give some feedback about Aggregate if that’s ok.

Is it going to be recorded?

I think you should enjoy the time with your family and not worry about the call! We’ll have one again next month.

For those joining, the call in link is https://www.uberconference.com/opendatakit

We just wrapped up our monthly developer call and it was great to talk to everyone!

We touched on getting more call participation, the progress on Aggregate, the JavaRosa/Collect releases, Collect developer docs, Collect geo widgets, a presentation for local devs in Cameroon, and the TSC process.

You can find the call notes here https://docs.google.com/document/d/1hszoTRzWG5W04JXgcBzE7BcdEZGB75lA8tftTNZ5lzA

The next call is: December 6, 2017 from 14-15 UTC

1 Like

Sorry to have missed this one. I enjoy them and plan to attend most.

1 Like

During the last call we talked about having a thread for each call to keep things organized and to plan in advance. I've started such a thread for the next call -- ODK 1 Developer Call - 2017-12-06. See you there!

1 Like