Dev chat summary for April 24 2013 Chat…

Dev chat summary for April 24, 2013

Chat log.

Agenda

  • iOSiOS The operating system used on iPhones and iPads. : version 3.5.3 released
  • iOS : status
  • Android : version 2.3.1 released
  • Android : status
  • Windows Phone : status
  • Mobile Handbook Reminder

iOS : version 3.5.3 released

The latest version of the app was released on Monday April 23, and has fixed even more crashes and bugs. Unfortunately there’s still a crash occurring with featured images.

iOS : status

Now working on some improvements to the WPcom Notifications screen and looking into ways the app can better handle accounts (from both WPcom and multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. installs).

NUX project: wrapped up (*crosses fingers*) some of the stuff that will improve the signup flow and have shifted toward the wizard walkthrough features.

Native WPcom reader project: implementation is progressing. Basic views are implemented and being iterated on. Currently working on the best way to handle video in posts.

Android : version 2.3.1 released

A bug fix update for version 2.3 (Holo update) of the Android app was released. This took care of a handful of crashes and a multitasking issue.

Android : status

Another bug fix release with some fixes to the ActionBarSherlock library and James Hu’s comment editing patch.

The next major version is 2.4 (WPcom Notifications). This release is progressing, push notifications are working and the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. is being wired up.

Windows Phone : status

Nothing big in the pipeline, although there’s now a milestone with tickets for the next update.

Mobile Handbook Reminder

There are quite a few items left to do, both assigned and open — you know who you are! Let’s wrap this up. Eric said he’s started to look into the remaining items for Windows Phone.

Rachel got in touch (yay!) so we’ll bring her up to speed on the status of the handbook as well.

Next week

The next dev chat will be on July 1, 2013 at 1500 UTC. Mark your calendar and join us in #wordpress-mobile on Freenode.

#android, #handbook, #ios, #weekly-chat, #windows-phone

Mobile dev chat summary for Dec 19, 2012

We had a brief meeting in iRC today.

Agenda

  • WPiOS status
  • Windows Phone status
  • Forum and Dev blog migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. heads up.
  • Mobile Handbooks

WPiOS

The current plan is to submit to Apple on December 28th.  Development is proceeding while we await a few APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. changes.

Windows Phone

Version 1.8.1 was submitted Monday and should be available for download by week’s end.
Work is proceeding on version 1.9 with an early January target for submitting to the store.  The big items for this release are improvements to the post/page content editor and the addition of featured images.  There are extensive changes in this release so we’ll take some extra time for testing before we submit.

Forum and dev blog migration heads up

We mentioned the planned migration of the mobile forums and dev blogs.  @Nacin dropped by to comment that the dev blog migration might begin before the forums and the start date might be the week after next depending on how the holidays go.  The todo list https://make.wordpress.org/mobile/2012/12/19/plan-for-migrating-mobile-dev-blogs-and-forums/ is still valid, just maybe reordered a bit.

Mobile Handbooks

We’re not sure what the timeline for having these ready looks ilke or what might be blocking us from starting.  We have a todo of answering these questions.

Next week

Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

#dev-chat, #weekly-chat

Mobile dev chat summary for Dec 12, 2012

Unfortunately the IRC channels doesn’t seem to have been logged at all for the past few days (although it seems to be working again today). This means there’s no public transcript of the chat this week.

Agenda

  • WPWindowsPhone bug fix release and what’s next?
  • WPiOS’s next release, release date?
  • Other platforms heads ups
  • Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. voting

WPWindowsPhone

We’re working on v 1.8.1 to fix a couple of crashes and some layout issues on taller Windows Phone 8 screens. When submitted, we’ll have two binaries: one for devices running less than Windows Phone 8 and one for Windows Phone 8 and up. This should help fix display issues for the latest Windows Phone devices. This update should be submitted late this week.

We’re also working on a better crash reporting tool but since it’s not a major feature it would likely be a point releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality..

For 1.9 (next version) we’ve discussed either having Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. support or a WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ Reader being the main new feature. [Since the meeting we’ve agreed upon making Featured Image support the title feature for version 1.9.]

WPiOS

We’ve had to push back the release another few weeks to make sure the APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. on WordPress.com’s side is fully optimized. We’re now looking at a submit date around Jan 1st.

Since the release is a ways out still, we contemplated doing a bug fix update to resolve some of the issues we’ve fixed so far for the next feature release. We’ll discuss this more next week.

Other platforms heads ups

Nothing to report on other platforms (WPAndroid, WPBlackBerry, etc).

Team rep voting

We noted that we’re voting on new team rep(s) for the first time, and made mental notes to go vote.

Next week

Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

#dev-chat, #weekly-chat

Mobile Dev Chat Summary for Nov 28 2012…

Mobile Dev Chat Summary for Nov 28, 2012

View chat log.

Agenda

  • Mobile handbook
  • WPiOS Sounds release
  • WPWindowsPhone progress
  • WPAndroid UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. Idea

Mobile Handbook

We’re going to create a WordPress mobile handbook to help new contributors get up to speed quickly when wanting to help out with all things mobile. Some notes:

  • We will have a main overview page that will link off to specific instructions on contributing to each app.
  • We should also include information for stuff outside of the apps, such as responsive design.
  • Each app lead is responsible for writing the page with instructions on getting set up and contributing to the app.
  • A google doc spreadsheet is going to be made by the weekend that will help us get the basic outline created for the Handbook.

WPiOS Sounds Release

  • App was submitted on Monday!
  • We’re not done with sounds, we’d like to continue iterating on them when possible.

WPWindows Phone Progress

  • Still waiting on version 1.7.1 to be approved from Microsoft.
  • Good progress has been made on version 1.8, which includes better comment moderation support.

WPAndroid UI Idea

  • For the next release (Date TBD) we’d like to create an Android 3.0 or higher version of the app that can use the ‘Holo’ theme and also make use of the native action bar.
  • We’ll split the APK distribution so that we can still offer the older UI version of the app to Android 2.3 or lower users.

Next chat

Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile dev chat summary for Nov 21, 2012

Chat log.

Agenda

  • WPiOS
  • WPWindowsPhone
  • Make/mobile changes and migrations
  • TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. guidelines for feature driven development
  • Mobile Handbook

WPiOS

Sounds release (should be v 3.3):
Ready to go, asking for some final feedback on the sounds on Twitter and in the forums.

Notifications release:
No update, but development is progressing.

WPWindowsPhone

1.7 (Local drafts, Windows Phone 8 support):
Complications when submitting, the update doesn’t work as expected for Windows Phone 8 devices. We’re in touch with Microsoft to help resolve the issues, but can only wait right now. Announcement pending.

1.7.1 bugfix update is pretty much ready to go.

1.8 (Moderation and Comments):
Work is progressing. If everything goes well we’ll submit early next week (shooting for Monday), but depends on when we can push the 1.7 and 1.7.1 releases through.

Make/mobile changes and migrations

Just a heads up: over the next few weeks we’ll work on moving all the dev blogs, app sites, public blogs, and forums/support over to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. This will happen gradually starting with the simple bits (like moving all the /development pages on the various sites) to one central location (most likely on this blog or in the upcoming Mobile Handbook).

Trac guidelines for feature based development

We spent a good chunk of time discussing how we should go about feature-driven development in Trac (full log here). In the end we concluded the following:

  • Milestones should be based on features and not versions.
  • Bugs fixed should be tagged with the Next Release milestone, and then migrated over when a feature is ready to be submitted/released.
  • Bugs that need to be curated with a feature release are the only types of defects that should be tagged with a specific feature release.
  • After every major app update has been submitted, we’ve now made it the norm for the team working on that update to spend the time in between submitting to the app being approved to go on a bug hunt in Trac, as well as keep testing the release and fix any issues.

Feature-driven development enables us to iterate faster and quickly submit app updates when a particular feature or set of enhancements are ready. Any new feature or major enhancement means a version number bump (e.g. 3.X).

We acknowledged the overwhelming amount of “defect” type tickets especially in the WPiOS Trac and recognized that something has to be done about this to build sustainable, bug-free apps. The steps above are intended to deal with this.

Mobile Handbook

Some concerns were brought up as to what the Mobile Handbook would contain. To the best of our knowledge, the Mobile Handbook would have a bit of the same content as the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Handbook. We acknowledged the guidelines already posted, and that the Mobile Handbook would need at least in part specific sections for each app (because the platforms and how you develop on them are so different). We’ll also want to mention that the apps are on GITGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. as well as SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/.. As previously noted, mrroundhill, koke, and daniloercoli will help write it as the lead developers for their respective platforms. Jkudish mentioned in the chat that he’d be up for providing some pointers for us as he recently got started with mobile development himself.

Next chat

Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile dev chat summary for Nov. 14, 2012

Read the chat log.

Agenda

  • WPWindowsPhone
  • WPAndroid
  • WPiOS
  • Adjust Weekly Meeting Time

WindowsPhone

Version 1.7 was submitted to the Windows Store.  It take about a week for it to be approved.  This version includes:

  • Local Drafts.
  • Post Format Support.
  • Upload photos from camera or photo library.
  • Set the positioning of individual photos.
  • Windows 8 compatibility.

We learned that when submitting an app to the Microsoft Store you have to upload images separately for each XAP, and for each language that is supported for that XAP. This is rather time consuming.

There is a milestone for version 1.7.1 that will focus on improvements and bug-fixes.  We would like to have it ready by the 23rd.

WPAndroid

We’re planning to release version 2.2.5 today.  This version fixes a few bugs, including an issue with some multi-user blogs not being able to view Jetpack stats.

WPiOS

Version 3.2.1 has been out a bit and we’re seeing reduced crash levels. Down from 15.48/h in version 3.2 to 12.04/h in 3.2.1.  This is roughly a 20% drop. (Yay!)

Koke has fixes in place for some of the remaining crashes, and the thought is the switch to ARC will fix a few more. We’re thinking it probably makes sense to include these in the release of 3.3 than to 3.2.2.

Beau should have a prototype of the new notifications view by the end of the week.

Dan plans to fix a few layout issues on the iPad mini.

Eric is finishing wiring up in-app sounds on the remaining pull to refresh views.

We’ve had a new contributor to WPiOS this past week. fklu is his IRC handle and we’re glad he’s around.

Adjust Weekly Meeting Time

Last week we talked a bit about making the weekly dev chat an hour later now that so many of us are on daylight savings time.  Today we took a vote and the motion carried so the weekly chats will now be at 1600 UTC, at least while daylight savings time is in effect.

 

Join us for the next weekly chat Wednesday at 1600 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile dev chat summary for Nov. 7, 2012

Read the chat log.

Agenda

  • WPiOS
  • WPAndroid
  • WPWindowsPhone
  • WPBlackBerry

WPiOS

Submitted 3.2.1 to Apple.  This is a bug-fix release that fixes the top 10 crashes in the app.

The plan for 3.3 is to add a Notifications panel which would be a WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ only feature.

WPAndroid

Version 2.2.4 was released.

Nothing new planned for Android for the time being.

WindowsPhone

Development for version 1.7 is underway.  This version includes:

  • improvements to media,
  • local drafts,
  • minor UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. refresh
  • bug fixes

A betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. should be ready Friday, Nov. 9th.

It was mentioned that we’re targeting Windows Phone 8 but currently do not have a device for testing.  We’ll discuss internally what makes sense as far as acquiring devices for the team for testing.

BlackBerry

Version 2.2.4 of the Android app is available for the BlackBerry PlayBook.

At this point no other releases beyond bug fixes are planned for for the classic BlackBerry app.

Join us for the next weekly chat Wednesday at 1500 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile dev chat summary for Oct 24, 2012

We had a short meeting in IRC this week. Chat log.

WPiOS 3.2 status update

Version 3.2 was released yesterday and seems to be working fairly well so far. There has been quite a few bugs fixed since we submitted the update though, and there are pending translations, so we decided to issue a bug fix update (will be version 3.2.1). We noted that we need to pay closer attention to the app store reviews as some of them highlight fairly severe issues with the app.

Currently WPiOS trunk is not suitable to work on the bugs so we’ll work in a branch for any WPiOS 3.2.X releases, and move on to have trunk always be functional come version 3.3 of WPiOS.

Join us for the next weekly chat Wednesday at 15:00 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile Dev Chat Summary for Oct 17, 2012

View the discussion in the chat log.

Agenda

  • Two-Step Authentication: heads up
  • WPiOS: AFNetworking/ARC/modernizing & the plan for 3.3.
  • WPWindowsPhone: check in
  • WPAndroid: check in
  • WPBlackBerry: check in

Two-Step Authentication

The team will be adding support for two-step authentication for WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ blogs to the apps for their meet-up project.  We want to add support for all four major platforms, time permitting, but will likely focus on WPiOS and WP Android first.

Two-step authentication is an optional feature that adds an extra layer of security to the apps. Our implementation will be similar to what was done with Google Authenticator (source).

WPiOS

AFNetworking, ARC, and modernizing

We are updating to AFNetworking 1.0 and using this as an opportunity to also update the app to use ARC.

We discussed limiting support to iOSiOS The operating system used on iPhones and iPads. 5.0+ starting with WPiOS 3.3 and everyone present was in support of taking this step.  This will let us take advantage of some modernizations to Objective-C, and remove legacy libraries that now have native support (e.g. Twitter, Facebook).

The plan for 3.3

We talked about what to prioritize for WPiOS 3.3 and decided that Notifications and modernizations should be the focus.  We will include the rich text editor in this update if its ready to go, otherwise we’ll look to make it the major feature for 3.4.

WPWindowsPhone

Last week the team made progress on local drafts and media improvements.

This week development is on hold while we are focused on other things.  Development will resume starting Oct. 29th, the week after our meet-up.

WPAndroid

No new development last week.

WPBlackBerry

We fixed a few bugs over the weekend.

Danilo had a chat with a RIM representative during the Blackberry Jam in Milan about the posting issue some folks are experiencing and whether there was a bug fix in the works. We’re waiting to hear back from RIM.

The team chatted about the future release of Blackberry OS 10 and what we have planned for the new OS. At this time there is nothing on our road map.  The likely option is that the WP Android app will be repackaged for BB10, but several of the team mentioned a desire to create a native BB10 app so we have the best experience.  It was observed that this is what Twitter, Facebook and Foursquare have done.

Join us for the next weekly chat Wednesday at 1500 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat

Mobile Dev Chat Summary for Oct 10, 2012

View the discussion in the chat log.

Agenda

  • WPiOS 3.2 status, discuss 3.3
  • WPWindowsPhone: next milestone
  • WPAndroid: check in
  • WPBlackBerry: check in

WPiOS status and upcoming

WPiOS 3.2 submitted to Apple App Store review on Tuesday, Oct. 9 2012 and is now awaiting review. In-app notifications view and rich text editing have been pushed to a future release.

In-app sound effects have been pushed to a future release as well.

String translations need to be reviewed. Polyglots will be notified.

Notifications UIWebView vs native

The team unanimously chose to implement a native interface for the notifications view instead of embedding a UIWebView implementation. Notification polling will require using REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/. use so it would make sense to use the same data for the UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing..

WPWindowsPhone

The goal is to add some new features that are glaringly absent as well as fix any major bugs for the WindowsPhone 8 launch.

New features:

  • Local drafts
  • Media improvements

WPAndroid

Development is quiet at this moment. One ticket closed this week to fix a bug.

WPBlackBerry

No new development. WordPress 3.5 is removing the AtomPub APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. so it needs to be removed as an option from the app.

Join us for the next weekly chat Wednesday at 1500 UTC on irc.freenode.net in the #WordPress-Mobile room.

#weekly-chat