Closed (fixed)
Project:
DrupalCon Denver 2012 Website
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
5 Jan 2012 at 22:52 UTC
Updated:
4 Jan 2014 at 01:39 UTC
Jump to comment: Most recent
Hi All
I am proposing to build dedicated iOS/Android apps for DrupalCon Denver. Apps will be build upon platform I created for DoItWithDrupal and BadCamp apps http://itunes.apple.com/us/app/do-it-with-drupal-2011/id466705282?mt=8 ; http://itunes.apple.com/us/app/badcamp-2011/id470519171 ; https://market.android.com/details?id=net.sumitk.badcamp2011
Few features on my list:
For COD (in Drupal 6) I have created a feature which sends JSON data to app via views_datasource module, I am hoping to port same for Drupal 7 COD.
All changes on site will be pushed to apps - as user refreshes app's database! No custom code required Drupal side.
Comments
Comment #1
sirkitree commentedSound good, let us know if you need anything in particular on our end. And Thanks!
Comment #2
drummThe Denver site so far has been built to be responsive and there is work on #1361010: Utilize appcache and local storage for optimal offline site browsing. I don't know if there has been any decision that this replaces apps.
If we are moving forward with an App, I'd like to involve the people and codebase from previous DrupalCons. Either codebase is okay to move forward with. It does need to be able to be reused for future DrupalCons and future people working on it.
I'm the account holder for posting both apps. As usual, iOS needs lots time for review. How long did you wait for approval on the others?
Comment #3
coltraneI spoke with Sumit a bit today and asked that he post here.
Right now the volunteer team's focus is on using the site. My only concerns about having dedicated apps is 1) if they don't get complete in time 2) any extra effort that's required to support them 3) advertising and promoting the multiple (somewhat different) solutions and confusing users and 4) following DA/DrupalCon guides regarding sponsorship etc.
It's fine to me to provide multiple options, but if there's any promotion and listing on the "official" channels I think we'd need to compare them. For example, unless there's a solution for syncing bookmarking of sessions (for personal scheduling) then user's should know that their online personal schedule won't match the dedicated app schedule.
I was additionally contacted by someone from Twilio who wants to offer sms notifications of upcoming sessions.
I think the local Denver team should discuss these different methods and decide if and how much we want to support. I've added this to our next team meeting, Jan. 9th.
Comment #4
sumitk commented@Neil Thanks for replying!
Yes I am following #1361010 . But I still think apps are important.
Well my codebase is written from scratch and a lot different than previous DrupalCon apps. It already supports COD (d6 version) ... so can be used anywhere. For Denver app I am planning to do-
1. More performance optimizations on app
2. Integrate it with d7 COD
I got above apps approved in 6-8 days ... I have lots of experience getting thru Apple's app store approval process ;) so don't worry!
Comment #5
sumitk commented@Ben
About your concerns-
1. I take full responsibility of project and very positive that we will have apps ready by 15th Feb
2. Again me!
3. Team has to make decision on this
4. Why not
Well browsing sessions and set your own schedule take seconds on app (try above apps!) We may talk about syncing them with website (using their username OR uid) but I am not in huge favor of it.
Let me know if I can provide more details here.
Comment #6
sumitk commented@Jared :) I need-
1. Approval from DrupalCon Denver team
2. A new feature installed on website (for mobile integration)
3. Couple of new modules installed (views_datasource, services etc)
4. Access to code, database and files dir
Comment #7
sirkitree commentedOk
I assume this is a feature you will create?
Please give me a complete list
This can be a lengthy process. @drumm should be able to help you get access.
Comment #8
sumitk commentedYes I'll create this feature.
I will know all modules once I see codebase as website is using new D7 COD
Comment #9
drummGetting dev sites to regular contributors, is not a lengthy process at all. See http://drupal.org/node/1018084.
(Commit access and Jenkins are lengthy since those go through the OSL's LDAP system and then need a little more work on our end. As always, website changes will need to be reviewed and deployed by someone who is already a committer.)
Comment #10
coltraneThe Denver volunteer is still behind the site as the primary method for all Drupalcon information, including mobile but consensus that having native apps as well is not a problem. SumitK, you can consider this a green light to go ahead.
The code running on the Denver site is available here in this project for you. Check out the README to get started. The git repos is behind the live site at the moment, so I'll try to update it soon.
The actual site is using drupal.org bzr infrastructure, so you can also follow drumm's link in #9 to get access to development builds.
Comment #11
sumitk commentedThanks Ben! we gonna rock it :)
I will ping you today for admin account and db access.
Comment #12
coltrane"I will ping you today for admin account and db access."
No, you should follow steps in comment #9 for getting a test site on drupal.org staging.
Comment #13
sumitk commentedMy webmaster issue is here http://drupal.org/node/1405454 :)
Comment #14
drummTo be clear on access to Drupal.org servers: DrupalCon Denver's site is on Drupal.org's servers and has quite a bit of personal data which we do not hand out access to lightly. Dev sites aim to be complete working copies of the site, but with personal information, like email addresses, removed. You do get full access to the files and DB for dev sites.
You should aim to have your additions packed up as a feature with good deployment instructions, including version numbers of modules to add, for either kenwoodworth, coltrane, and/or myself to review and deploy.
Drupal admin access http://denver2012.drupal.org/ is a separate thing to consider. What specifically needs to be done there?
Comment #15
coltraneRemaining work is happening in #1443622: Features and Modules for Mobile Apps
Comment #16.0
(not verified) commentedupdating feature list