Making WordPress for iOS

Isaac Keyet 8:08 pm on September 5, 2012 Permalink
Tags: dev chat ( 3 )   

• WordPress › Mobile Dev Chat Sep 5, 2012 « Make WordPress Mobile 8:29 pm on September 5, 2012 Permalink | Reply

  [...] Game plan for the next week. [...]

• 

  Judy 8:03 pm on September 6, 2012 Permalink | Reply

  Ive been looking to get involved, but it is unclear to me where to start. Can you offer any advice?

  • 

    Isaac Keyet 10:18 pm on September 6, 2012 Permalink | Reply

    There needs to be a better getting started guide.

    Basically this is how development works for the WP for iOS app:

    1. A decision is made in the weekly dev chat (Wednesdays 15:00 UTC in #wordpress-mobile on Freenode) to work on an app update. We decide – as a community – what enhancements make the most sense to do next and what bugs/UX inconsistencies should be a priority to resolve. This process can span over multiple meetings.
    2. Tickets are gathered/created in a new milestone on the WP for iOS Trac and the major tasks are assigned to contributors, the rest are usually up for grabs. The dev cycle has a rough timeline, scope has been decided, and tasks divided, and so it starts.
    3. Each week we discuss the progress of open dev cycles in the weekly dev chat. Discussion also happens spontaneously in IRC throughout the weeks.
    4. Once enhancements are in and bugs are fixed, testing starts. We usually set aside 1/3 of each dev cycle for testing – much less than say Core WP does. This is because the user base is relatively small and there are not too many people building and testing the app outside of the core app dev team.
    5. If testing goes well, the app is submitted to the App Store for evaluation, and we draft announcements to have ready. Usually by this time we’re already discussing the next major release and any bug fix updates that may be needed for the just submitted release.

    To create your first patch you should join the weekly meeting and/or ping is in #wordpress-mobile another time to figure out where a good place would be to start based on your obj-c knowledge coming in and of course where your strengths lie in general. After it’s been discussed you get assigned or assign yourself to tickets as needed in Trac and start cranking. Create a patch with the diff and upload that to the ticket and ask someone to review it. If it goes through, you’ll be on the contributors list in the next announcement!

    Looking forward to talking more about all this. Is there anything that’s unclear still? Any and all feedback that would’ve helped you get started would probably help others so feedback is much appreciated.

  • 

    Isaac Keyet 2:50 am on September 18, 2012 Permalink | Reply

    Hi Judy, have you found your way around the app yet?