Apps/DevEngage/Content/DevEcoEngage Meetings/2012-07-17: Difference between revisions

(→‎Action Items: change link)
 
(6 intermediate revisions by the same user not shown)
Line 11: Line 11:
= Attendees  =
= Attendees  =


*
* Mark Giffin, Janet, Jeff Griffiths, James 'Pedro' Long, TofuMatt, Havi, Joe


<br>
<br>
Line 24: Line 24:
= Action Items =
= Action Items =


Action items: Proposals for the 2 weeks ahead in preparation from FISL and upcoming App Hack events. We need to prioritize the documentation tasks.
Action items - In preparation from FISL and upcoming App Hack events, we will review and prioritize the documentation tasks and dev ecosystem priorities listed below. This list is the agenda.  


'''Janet & Mark'''
'''Janet & Mark'''
* Tutorial: Restructure the existing MDN Getting Started tutorial to be more modular, sequential and fast-start friendly: Prioritize MDN over Developer Hub
* Tutorial: Restructure the existing MDN Getting Started tutorial to be more modular, sequential and fast-start friendly: **Prioritize MDN over Developer Hub (short term)
**https://marketplace-dev.allizom.org/developers/tutorial/apps?lang=en-us vs
**https://marketplace-dev.allizom.org/developers/tutorial/apps?lang=en-us  
**https://developer-new.mozilla.org/en-US/docs/Apps/Tutorials/General


'''Janet & Daniel Buchner'''
 
'''Janet & Daniel Buchner'''  
* Developer Hub: Come up with a Developer Hub plan and timeline for Q3-Q4
* Developer Hub: Come up with a Developer Hub plan and timeline for Q3-Q4
**what is top priority Apps content w/delivery dates (should map closely to tutorial priorities on MDN)
**what is top priority Apps content w/delivery dates (should map closely to tutorial priorities on MDN)




'''James Long, Fred & Mark Giffin'''
'''James Long, Fred & Mark Giffin'''  
* Tutorial: Using Mortar to build Tweetness
* Tutorial: Using Mortar to build Tweetness
** https://github.com/jlongster/tweetness
** https://github.com/jlongster/tweetness
Line 43: Line 43:




'''Bryan, James Burke & Mark Giffin'''
'''Bryan, James Burke & Mark Giffin''' NOT AVAILABLE
* Tutorial: Walkthrough of NPR app demo Install module -- installs to Moz Marketplace, Android store & iOS
* Tutorial: Walkthrough of NPR app demo Install module -- installs to Moz Marketplace, Android store & iOS
** Install module screencast delivered  
** Install module screencast delivered  
** Next steps for NPR demo app (Can James work on screencasts while Bryan is out?)
** Next steps for NPR demo app (Can James work on screencasts while Bryan is out?)




Line 54: Line 55:
** Define the tool chain
** Define the tool chain
** Documentation plan / craft tutorial
** Documentation plan / craft tutorial
UPDATE: See below


*Question: Is there a simple client-side app we can document in a tutorial style? Fred and I were having trouble coming up with one.
*Question: Is there a simple client-side app we can document in a tutorial style? Fred and I were having trouble coming up with one.


*Fred has a game called Serpent that uses WebGameStub template, but it is keyboard-based, not mobile friendly. Is this worth documenting?
*Fred has a game called Serpent that uses WebGameStub template, but it is keyboard-based, not mobile friendly. Is this worth documenting? '''UPDATE:''' Fred has now created & submitted a mobile version!


= Minutes  =
= Minutes  =


 
*Updates on Action Items (described above):
*Updates on Action Items:
** '''UPDATE:''' Modular Apps Tutorial is ready for FISL: https://developer-new.mozilla.org/en-US/docs/Apps/Tutorials/General 
*** Mark is adding new stuff based on content from Jason Smith.
***TofuMatt says we need update to manifest. Will share with Mark. Mark to include.
**'''UPDATE:''' Everyone upvotes the NPR installer module. It encourages people to submit to Marketplace and iterate.
** '''UPDATE:''' Developer hub plan is owned by Dev Ecosystem team. Janet & Mark will coordinate when Fred and Daniel are back in the office.
** '''UPDATE:''' James will use a different Mortar app to demo Mortar, not Tweetness
*** (What's Mortar: a collection of templates - base UI, game, server-side, pre-built/list view) - and will post on github before FISL
*** AND James will send markdown version of this to Janet/Mark to include on MDN
**'''UPDATE:''' Tofumatt on Server-side ecosystem tool plan -
*** web apps need server-side  components - b/c you need some place to host them - for auth and storage.
*** basic stuff that doesn't require elaborate framework for JS-savvy devs
*** host on Heroku for free till you can make money. scales well, very good for testing
*** Matt is building a little node.js server - and dealing w/node setup. Includes:
****install app
****webpage
****serves up proper manifest
****simple DB backend like redis
****2 command deploy to heroku (free for 1 server, 1 listener)
****time estimate: 1-2 weeks to get it going.
****maybe an example app for games.
** Some notes on hosting options:
***AWS - heroku is hosted on Amazon, good reliability and well-distributed, but way easier to deal with.
***Github hosting is preferable if they are only client-side.
***Volo will package, minify and push to github w/2 commands.
***set your github branch to your page branch.
Confirmed users
1,021

edits