info for every http://Meetup.com/OCAndroid event LEVW4X

^LGDMC7: :

1. ^LGDMVI: Purpose

   • ^LGDMXW: In The Android Developers/Users Group of US.CA.Orange Co. http://Meetup.com/OCAndroid , this is for all the info which attendees should know but which which generally stays the same for event/meeting/meetup and for every of same type.
   • ^LGDNP9: And rather than burden each meeting event listing with this same repeating info, I’m storing it here having every event listing just link to here for these details.
2. ​

   ​

   For every (OCAndroid) meeting

   ​

   1. ^LEUINB: Follow Etiquette & Things-To-Know when RSVPing to any Meetup Event LEVV22

   2. ^LDHPMS: Please carpool! Android Developers should be as green as the Android robot!

      • ^LGDNA6: See “Please carpool” instructions in the next item then
      • ^LGDNAN: Set up carpooling with your potential carpool buddies by posting here else contacting them direct. To find them, see the RSVP YES/MAYBEs on the right and our map of prior & present attendees complete with potential carpool routes.

   3. ^LEUIGL: Follow Every Meeting has it’s own (live) Meeting discussion thread LEUFYB.

3. ​

   ​For every meeting involving presentations, serious discussion, and definitely coding, writing, web lookup​

   ​

   1. ^LEUIK3: Follow Things you must bring  LEUIAV.

4. ​

   ​
   

   Kinds of Meetings (under construction & ~30% complete)

   ​

   ​

   ​
   

   LQVWHK​	LQVWOW​ ​	​LQVWJR​	​LQVWT9​	LQWQFR​	​LQVWRB​	​LQVXCH​	​LQWQ55​	​LQVXG1​
   LQVWII​ ​	for doer-type	​for experience-level	​Event type​	​Activities​	​Frequency​ ​	When (period(s) served)​	​agenda	host(s)
   ​LQWQU0​			LQWSX2-general meeting
   ​LQVX5B​	Varies, but open to all	​Varies, but open to all​	​Introductions, Annoucements, & especially Presentations;  (except for 30min initial social)​	​mostly single-speaker; most topics​ planned	​Monthly​			​DestinyArchitect
   ​LQWQI9​			​Bash	​mostly simultaneous speakers; most topics on the fly
   ​ ​LQVWJ8​ ​	​Developers​	​Advanced+Intermediate	Bash		​Monthly​			​James Turner​
   ​LQVWW8​	​Developers​	​Intermediate​+Beginner ​	​Bash		​Monthly​
   ​LQVWZW​	​Users​	​All: Beginner thru Advanced​	​​Bash		​Monthly​			​Lucy Parker​
   ​LQWPWI​	All	All	Classic			2011.05		DestinyArchitect​

   .

   ​
   

   ​LQWRA2​	​LQWRBH​	​LQWRFW​	​LQWRGT​
   ​LQWRCO​	​object​	​attribute​	​value​
   ​LQWRLD​	name	​name	​ ​name​
   ​LQWRPX​	inherits	name	​inherits​
   ​LQWRWA​	for doer-type	name	​for doer-type​
   ​LQWS38​	for experience-level	name	​for experience-level​
   ​LQWSEQ​	host(s)	name	​host(s)​
   ​LQWSII​	when	name	​when​
   ​LQWSL3​	agenda	name	​agenda​
   ​LQWSSQ​	meeting	name	​meeting​
   ​LQWSWE​	LQWSX2-general meeting	name	​LQWSX2-general meeting​
   ​LQWT05​	LQWSX2-general meeting	inherits	meeting
   ​LQWT13​	LQWSX2-general meeting	agenda	​~10min ​ ​Networking​ ​arrivals & socializing & networking​ ​~20min​ ​ ​Introductions​ ​each attendee introduces him/herself ​~10min​ ​ ​Annoucements​ ​annoucements​ ​~2hrs​ ​ ​Main Meeting​ ​main body of meeting​

   .

5. ​

   ​For Classic Meetings ​

   1. ​

      ​

      Examples:

      ​

      for regular (Classic) Meetings, as http://meetu.ps/lSsS

       

   2. ^LGAYGP: Classic Meeting Schedule:

      • ^LGDMZV: In short:

        • ^{LGAZXC:based on last 4 meetings” says our 2011.01.12 Meeting. We do dinner, news, presentation(s), jobs & technical issues, group planning, update member profiles, hackathon, & maybe club afterwards! –source}

      • ^LGAYKT: 6pm- setup & group dinner –we need to take time eat!, plus appreciate our venue host

      • ^LGAYL5: 7pm- single-speaker session –one person speaks, all else listen

        • ^LGAYLZ: News & Announcements.

          • ^LGAYMF: Example from a prior mtg: Android tablets from CES 2011.

        • ^LGAYMZ: =Presentation(s):

          • ^LKYE36: There are usually 1 to 4 presentations per Classic Meeting.
          • ^LGAYWJ: =Some real presentation examples(copied from our event listings):
            1. ^LKXVK8:
               

               LJZ90I: “ Johanan (+1) of San Macros 92078&Irvine;. joined 2011.01.01″ Member & attendee Johanan presenting his Android apps

               from Our 12th/2011.05.11(Wed) Classic Meeting.
               

            2. ^LGB08L:
               

               New member JohnJ presents some of his beginner Android apps he’s coded

               from Our 7th/2011.01.12(Wed) Meeting.

            3. ^LGB091:
               

               Presentation & workshop: Intro to Android Development by our published developer member(s); member GregS presented last time and we’re hoping member Tod will present this time as he promised he soon would…

               from Our 7th/2011.01.12(Wed) Meeting.

            4. ^LGB09H:
               

               Presentation of Google’s App-Inventor (super easy way to start in Android development) if Jeff H. or someone can to do this: reply on that thread if & when you can!

               from Our 7th/2011.01.12(Wed) Meeting

          • ^LKXUPB: Please suggest a presentation! And ideally present something!
            1. ^LKYHCY: See Some real presentation examples above & read motivation & examples.
            2. ^LGAYNM:Please suggest a presentation (and optionally offer to present it) by either:
               1. ^LGAYSD: post or 2nd a presentation name-else topic discussion thread (in our event forum) then ideally post a link on the event listing page(s), as below Presentation rules details.
               2. ^LGAYTA: else bring a presentation to the meeting (but then we can’t advertize it nor really budget much time for it, nor share it online as well, so we much prefer the prior approach)
          • ^LKYE21: =Presentation rules:
            1. ^LKYFUC: So far we’ve always had a hunger for presentations and never had to turn one down.
            2. ^LKYFPS: Presentations are usually the technical details of the topic (Android development & use) but they can be marketing or business details, or they can be other topics that are somewhat related.
            3. ^LKYE6I: Each presentation is generally from 10min to ~1.5hrs, with the average about 35min.
            4. ^LKYFJI: To present, presenters generally use one or more of these devices:
               1. ^LKYFKH: hooking up their laptop they bring to a flat panel or projection display, with VGA or HMDI input, if the venue has one or someone brings one.
               2. ^LKYFMQ: setting up their laptop as an UltraVNC server on the wireless LAN and have attendees set up their laptops as clients so the presenter can share his/her desktop with everyone.
               3. ^LKYFPA: –we’ve done all of these and they work well. See Things you must bring to every meeting LEUIAV for further details.
            5. ^LKYE8P: =presentation name-else topic: Every presentation name-else-topic (call it a show, as it could be repeated)
               1. ^LKYEHK: should have its own discussion thread
                  1. ^LKYGIJ: For examples, see the discussion thread linked to in Some real presentation examples .
                  2. ^LKYECT: which the presenter(s) should ideally create and should definitely watch & maintain
                  3. ^LKYEFR: where all details of the presentation are kept, including
                     1. ^LKYF2L:giving links/URLs to the planned & actual
                        1. ^LKYF2L: members presenting (to member profiles)
                        2. ^LKYF4P: event listings where it’s given
                        3. ^LKYFE7: topics being covered (use Wikipedia links if they exist)
                     2. ^LKYEGM: where members post their questions
                     3. ^LKYEVG: where everyone esp. presenters post answers and links to say slides, code, and other materials.
                     4. ^LKYEYK: ideally enough detail so those who can’t come in person can still get the gist by participating online
                  4. ^LKYEU6: which is usually suggested (& ideally posted) by the presenter(s) but can be posted by any member wanting this presentation topic, in which case the thread can also be used to solicit votes & presenters & meeting times for that topic.
                  5. ^LKYF0S: which is reused & extended every time the same presentation is given, so doesn’t go-out-of-date whenever a showing is canceled or postponed but is saved & extended for whenever it’s given.
                  6. ^LKYEOH: posted in our event forum
                  7. ^LKYEP9:linked to on every event listing (page) where the presentation will/may be given
                     1. ^LKYES5: the link (to the presentation) will be in the event listing description else it can be posted in the Talk comments.
                  8. ^LKYFAT: Note so Meetup will alert you to changes in this thread (via a daily email for all groups one is in), a member must make at least one post to the thread where s/he selects “Track this discussion”
                     1. ^LKYGBP: =LKYGBP: The presenter(s) MUST do this so they will find out when members & organizers post them related questions & news.
                  9. ^LKYHVD: Note presenter(s) should post the status of their presentation to their presentation thread shortly before their presentation event(where they will present it), as this:
                     1. ^LKYI2T: assures everyone they will be presenting it there as described (important)
                     2. ^LKYI2Y: gives everyone any missing details (including anything special to bring)
                     3. ^LKYI5O: insures presenter(s) know how to use their presentation thread and have set their thread so they will be alerted to updates there.

      • ^LGAZ09: 8pm- breakout session

        • ^LGAZ13: Group planning –we need presentations & events. Followup on
          Please present something, or host an event, for your OCAndroid group! LEVX1Z
        • ^LGAZ1H: Read & respond on our jobs offered
        • ^LGAZ1O: (newcomers especially) Update your group profile & including our extra public data (member directory)
        • ^LGAZ1V: User problem solving on our our support forum: read & reply there: post your Android problems, Qs, plus your solutions, plus add your experiences if they’re already there. Help out & get solutions now!
        • ^LGAZ2A: hackathon –bring your tools to code Android!

      • ^LGAZ2M: 9:15pm~- adjourn (as venue closes) then hang outside & chat, sometimes going to a nearby club as Tia Juana’s

   3. ^LDHPMB: The venue

      • ^LGDND7: has good reasonably-priced food plus free wifi Internet.
      • ^LGDN88: Additional venue details & discussion for organizers & helpers.

1. ^LGDJ10: Document change log

   1. LGDHM:prior to now this was stored in the event listing itself

      1. as “Our 8th/2011.01.26(Wed) Meeting http://meetu.ps/5T1s and until now “Our 9th/2111.02.09(Wed) Meeting http://meetu.ps/lSsS, but this makes the event listing long and confusingly full of stuff which doesn’t change — even if the mostly static stuff is isolated, it’s still confusing to have it there. So

   2. ^LGDHPV: now I moving it as a post on http://www.meetup.com/OCAndroid/messages/boards/thread/10293031 Add a reply

      1. ^LGDH3D:do the convert
         1. ^LGDH9L: use http://www.meetup.com/OCAndroid/messages/send/?eventId=16182968 to convert HTML copy&paste to BBCode.
         2. Source description_LGAZBY.html
         3. The conversion has errors with serious, example (before/after)
            1. ^LGDIK1:
               

               ^LGAYGP: Classic Meeting Schedule: dinner,
               —
               Classic Meeting Schedule: dinner,

            2. ^LGDIKD:
               

               • ^LGAZ13: Group planning –we need presentations & events. Followup on
                 Please present something, or host an event, for your OCAndroid group! LEVX1Z

               ^—
               Please present something, or host an event, for your OCAndroid group! LEVX1Z
               

            3. enough!

   3. ^LGDILZ: Move it to post http://2.LoveRules.Info/159 (here)

      1. ^LGDLD2: (at that time) copied ExpressionWeb WYSIWYG and pasted into WordPress WYSIWYG
      2. ^LGDJJL:Published (so archiving) first version (a direct copy) before making any edits
         1. ^LGDJQB: copied this from WordPress (copy from editor’s HTML mode) –no, some other means says #LGDM60
         2. ^LGDK6Q:Do diff via kdiff3
            1. ^LGDK79:Undo insignificant changes, creating file WordPress_copy_out_test_LGDJQB.undo_LGDK79.htm
               1. ^LGDK8W: tag-b converted to tag-strong.
               2. ^LGDLAS: tag-i converted to tag-em
               3. ^LGDLBO: class attribute stripped out -that’s not okay.
               4. ^LGDMOJ: No matter how I try to undo I can’t get kdiff3 to do a decent sync, maybe it wasn’t designed for HTML.
      3. ^LGDLSC:Repeat LGDLD2
         1. ^LGDM53: the problem doesn’t reappear, class-attribute is kept, so
         2. ^LGDM60: it appears I did it by some other way which caused class-id
         3. ^LGDMN9: Preview, inspect; looks like a good copy, publish.

   4. ^LGDN27: Updating it to present: done.

   5. ​

      ​Updating to handle not just classic meetings but all meetings/events/meetups​

      ​Motivated by posting the meetup 2011 O’Reilly Android Open Conference where only a subset of this info applied.​

      ​Renamed from “http://Meetup.com/OCAndroid Standard Meeting Info LEVW4X” to “info for every http://Meetup.com/OCAndroid event LEVW4X“​

      ​Created section For every (OCAndroid) meeting​

      ​accordingly generalized the Purpopse section​

      ​other improvements –do diff to see.​