Oct 122011
 

(LSZPOS (LT2MOD last mod LT8K31=2011.10.17(Mon)pst1731) (LT2VER version 1.3) (LT2STA in-starter-use) (LT2NAM

(LSZTHR=(Meetup event listing’s )discussion thread of All Additional Aspects, from-conception-to-legend, in that order http://1.JotHere.com/LSZ1QK)  )

  1. (LSZDEF Definition

    1. (LSZ259 a discussion thread tied 1-to-1 with an event listing)
    2. (LSZ95J Every event listing of any complexity should have and advertise 1 of these threads else the functional equivalent since it’s functionality key for events of any complexity)
    3. (LT2FZT designed for any event listing of
      1. (LT2GEW Meetup
        1. (LT2GAI since a Meetup event listing currently lacks this functionality –unless the listing creators (or Meetup.com) eventually sense the problem and add a solution as this
        2. (LT2J0B so currently listing creators have to manually add this)))
      2. (LT2GNG potentially another Meetup.com-like service))
    4. (LSZB48 Purpose: to record & share ideally-all (details of a-certain-kind) relevant to the event listing which happened prior, during, and after
      1. (LSZQL1 Notably “additional” details (for lack of a better word) which
        1. (LSZQMU can be shared to the group) but
        2. (LSZQNS don’t really belong
          (in event listing comments (including won’t fit well and/or shouldn’t be instantly emailed out to all RSVPers)) nor
          (in the event listing description (which should contain only essential & approved details))
          ). LSZQL1)
      2. (LSZQSG It includes the detailed feedback on & updates to the event listing, advertising of the event listing, live notes during the event, detailed reports after, plus other details.)
      3. (LSZQUA For more purpose, see (LSZ1U9 Motivation ..).)

      LSZB48)

    5. (LSZAC2 All leaders/organizers of the event listing should read & follow this thread and ideally collaborate via it per (Communicate foremost by appropriate posting)LHPXDE)
    6. (LSZB7H Each item (mentioned in the thread) should be prefixed by the date it happened and listed in the order it happened.
      1. (LSZBDJ An effective way to do this is to have:
        1. (LSZBKW a list-item for each date, such as “[*](2011.10.11(Tue)pst[list=1] …[/list])”) then
        2. (LSZBL3 under each of these, the time the change made or the micro-event happened & ideally it’s GUID, such as “(LSXC54=1405: <item_or_change/>)“)

        LSZBDJ )

      LSZB7H)

    7. (LSZ265 Listed/stored-in the (Meetup) group’s event forum, as events & presentations LBQGMR on OCAndroid)
    8. (LDFVCF Put (and factor-out) each potentially-repeated sub-concept into its own discussion-thread and link to it from here instead of detailing & discussing it here.
      1. (LSZIB7 each venue, if it could possibly be re-used, have a thread for it in (the group’s venue forum, as OCAndroid’s venues for our regular meetings (past, present, & possibilities) LH2C7F) and avoid putting details here, just a link to them there.)
      2. (LSZIE2 each event-topic, presentation, or sub-event, if could possibly repeat, have a thread for it in (the group’s event & presentation forum, as OCAndroid’s events & presentations LBQGMR) and avoid putting details here, just to a link to them there.)
      3. (LSZIU3 How? Search for the discussion of that concept: if a good thread exists for it, use it, else create one; then find-else-post the details of that concept there, not here; then post here in the event’s listing’s thread just a link to these details.)
      4. (LSZJ11 Why? This
        1. (LSZJ6A Keeps the event listing’s discussion thread clean & shorter –as much as possible like a summary with links to more details)
        2. (LSZJ78 Puts the re-usable details in their own thread where then they can be re-used by several events and more)

        LSZJ11).

      LDFVCF)

    9. (LEUHR0: Members & especially leaders, get the thread used:
      1. (LSZJK7 At the start of the event or before, designate at least 1 event note-taker to post the minutes & what happens hereon this main discussion thread for the event.
        1. (LSZMS2 See also So see also Meeting Note-taker needed))
      2. (LSZJL0 Encourage all attendees, and even remote attendees, to post here their event notes and Q&A on this thread.)
      3. (LSZJOD Remind all attendees that doing this gets the event documented, to benefit everyone afterwards and sometimes even allows remote attendees to participate.)

      LEUHR0)

    10. (LSZ280 Named (per real 1st example) “OCAndroid Advanced+Intermediate Developers Meetup #1’s Additional Discussion prior, during, & after
      1. (LSZ2AR a complete, context-free name, so should include, ideally in this order:
        1. (LT143J the complete name of the event given by the listing, as “OCAndroid Advanced+Intermediate Developers Meetup #1″, which should also be context-free so should include, ideally in this order:
          1. (LT13SC The full event-series name, as “OCAndroid Advanced+Intermediate Developers Meetup”, which should also be context-free so should include, ideally in this order:
            1. (LT13ZD The full subgroup-else-group name, which should also be context free, so should include, ideally in this order:
              1. (LSZ29Q the group name, as “OCAndroid”)
              2. (LT13VE the subgroup name, as “Advanced+Intermediate Developers”, if any) )
            2. (LSZ2CO the activity, as “Meetup”)

            ))

          2. (LSZ2DL the # in the series, as “#1″)
        2. (LT143J likely some punctuation, as “‘s” or “:”)
        3. (LSZ2FE the specifier words “Additional Discussion prior, during, & after“, referring to this kind of discussion thread per that name)

        LSZ2AR)

      LSZ280 )

    11. (LSZ7VW The thread’s first post begins:
      1. (LSZ84N models after this 1st example
        LSZ84N)
      2. (LSZ97V note it immediately links back to its 1 event listing)

      LSZ7VW)

    12. (LSZ8WM Referencing/linking-to the thread
      1. (LSZ8LD The thread is referenced in the event listing’s description in the section about this particular listing (NOT about the series), by an item containing the text

        Additional Discussion prior, during, & after, including any advertising of, planning for, & detailed-reports from this event.
        but replacing that URL with the link to the thread created (LSZ8UV aside: this sample from 1st OCAndroid Bash for Advanced+Intermediate Developers listing)

        LSZ8LD)

      LSZ8WM)

    13. (LSZ8I9 for remainder definition, see the section (LSZ8AY Creating))

    LSZDEF)

  2. (LSZ8AY Creating

    1. (LSZ936 Tragically Meetup does not create this important thread automatically)
    2. (LSZ85M: steps:
      1. (LSZ8GO copy the BBCode from a href=”http://www.meetup.com/OCAndroid/messages/boards/view/addpost?parent=56992112&quote=yes&forum=1432750&pager.offset=”>Quote in reply then selecting the text between [quote]…[/quote] then abort that post) then
      2. (LSZ8GW in (the above appropriate forum), paste this text as new thread)
      3. (LSZ8H3 adjust the text & its links as appropriate for this new listing)
      4. (LSZ8KC add to the event listing the link to this thread as defined in LSZ8LD above)

      LSZ85M)

    LSZ8AY)

  3. (LSZCMP Comparison with Alternatives

    1. (LSZG1X “[Meetup event listing's] Organizer discussion thread” as done on http://Meetup.com/AsianFriendster events as Sharkand much earlier.
      1. (LSZG79 The new will encompass & replace that)
      2. (LSZGB7 Big Con: by name, was only for organizers
      3. LSZG1X)
    2. (LSZFPF (Every Meeting has it’s own (live) Meeting discussion thread) LEUFYB)
      1. (LSZ6TP The new will encompass & replaces that)
      2. (LSZFXZ Pro: The most similar construct I’m aware)
      3. (LSZGKN Pro: featured points (LDFVCF) (LEUHWM) (LEUHR0) which I incorporated in the new.
      4. (LSZFYL Pro: this new is based on that prior)
      5. (LSZFUK Con: The name “Meeting” –as the idea can more generally apply to an “event”)
      6. (LSZFZM Con: the name “live” which got into popular use; that is only an extra aspect, not fundamental)
      7. (LSZFVW Con: The documentation of this was on Meetup.com, not JotHere.)

      LSZFPF)

    LSZCMP)

  4. (LSZMOT Motivation

    1. (LSZ1V5 Behind every event listing description is also planning, advertising, reports of the event, and feedback.
      1. (LSZ2NN These details are beyond what should be featured in the main event listing description: the essential details every attendee needs to know, the bottom-line of when, where, who, what, etc.)
      2. (LSZ2PW But especially with the collaborative event planning which Meetup and a few other Web 2.0 sites make possible –where potentially everyone can be an organizer and planner– it would be good to share and even collaborate with these details, indeed alongside the event listing description if possible.)
      3. (LSZ2TT And for events with few attendees and/or very simple events, Meetup makes this possible by allowing these details to be placed in event comments,
        1. (LSZ35U as an event comment:
          1. (LSZ30W Any group member can make one, by just filling in the comment box on the event)
          2. (LSZ318 Can be up to 500 ASCII characters.)
          3. (LSZ31K Is by default emailed to all who’ve commented on the event or who’ve RSVPed YES or MAYBE (and possibly who have RSVPed NO) except as noted.
            1. (LSZ334 except to members who have turned off this for all events in the group, a feature which Meetup should have never offered)

            LSZ31K)

          LSZ35U) but

      4. (LSZ36P For all other events (events with more than a handful of attendees and of even a little complexity)
        1. (LSZ3PM These listings, for all but simple events, often take some & space to evolve and even report on.
          1. (LSZ5W7 A common example, a new kind of event and especially an event-series takes some time & communication before it’s organizers, venues, and exact dates are figured out, so one typically would want to list the event on the group’s website to see what the interest is, who is interested, and work out the these details.)

          We need posting-space to work out these details. LSZ3PM)

        2. (LSZ39F In this case, there are details and & discussion about the event which:

          1. (LSZ67U really don’t need to-be-private-to-just-organizers –most anyone who wants to help here is welcome ) BUT
          2. (LSZ4VK still not suited, else best-suited for an event listing’s comments nor description.
            1. (LSZ4P3 Not good for the comments as these details:
              1. (LSZ4TD won’t fit well in 500 ASCII characters with no other rich formatting)
              2. (LSZ3A1 shouldn’t be instantly emailed all potential attendees, and that would just overload & confuse them (is this proposal really happening & approved?, etc), info which shouldn’t be broadcast until it’s worked out)
              3. (LSZ59H it may need to be updated and where we don’t want every update sending this bulk email)

              LSZ4P3)

            2. (LSZ4VK Not good for the description as are:
              1. (LSZ4ZY details (venue, speaker, etc) not approved/authorized, just proposed or just being discussed)

              LSZ4VK)

            3. (LSZ6X1 additional examples
              1. (LSZ50T additional details & discussion which probably only organizers would care about or need to know)
              2. (LSZ3V2 advertising details as when/if it the listing was emailed out, as a more event needs to be planned over time so the advertising of it isn’t immediate but now readers then look at the event listing and wonder “Why so few RSVPs and reaction?” not realizing, unless it’s recorded & displayed in a standard place, that the event hasn’t really been advertised. These details (of how & when it was advertised) we don’t want to clutter the event listing with, but the reader really concerned with the reaction thus far needs a standard place to find this advertising status.)
              3. (LSZ54D feedback on the listing or a report on the event that also doesn’t best suit an event listing comment, including:
                1. (LSZ6LW live notes of the event(now that we have a Web 2.0 site to share them!), which are ideally done by the group/meeting’s secretary but now also can be effectively done by all the meeting attendees, and should be done by as many attendees as possible
                  1. (LSZHS5 The “live notes” idea I first pioneered in (LSZFPF ..))

                  LSZ6LW )

                LSZ54D)

              LSZ6X1)

            LSZ4VK)

          LSZ39F)

        3. (LSZ3LX to address these exceptions (for events beyond the most simple), I have invented and use “(LSZ1QK A Meetup event listing’s Additional Details thread)” and created this post to document this standard.)

        LSZ36P)

      LSZ1V5)

    LSZMOT)

  5. (LT10FI Full Name with Etymology

    in historical order –so only read the last bolded text here for just the latest essentials:

    1. (LT11W7 2010: (LSZG1X [Meetup event listing's] “Organizer discussion thread” .. …)–see that)
    2. (LT1166 2011.01.10: (LSZFPF (Every Meeting has it’s own (live) Meeting discussion thread) LEUFYB)
      –see that)
    3. (LT10HH 2011.11.12: (LSZ1QK Meetup event listing’s Additional Details discussion-thread) plus separate permalink http://1.JotHere.com/LSZ1QK)
    4. (LT10RS=2011.11.13: (LSZ1QK Meetup event listing’s Additional Discussion prior, during, & after thread http://1.JotHere.com/LSZ1QK )
      1. (LT121R Notable pro: Replaces “Details” with “Discussion” (specifically” moves “discussion” to the front & capitalizes, and drops “Details”), which is more accurate & (desirably) more enticing, plus shortens by 1 word.)
      2. (LT12EH Notable Pro: Does all of:
        1. (LT12H(LT12HH Makes the short-else-std-URL part of title (at end) and with trailing space and in “()”, so even pasting the title into pure ASCII systems retains the link & grouping
          1. (LT12XI for simple single copy & paste of name into pure-ASCII entry without loosing the link. Systems as:T137F SMS messaging systems)
            (LT137Q BBCode as most-notably Meetup’s Message Boards))
          2. (LT130V A technique I’ve for at least a year within Meetup event listings when they reference themselves, so they can be easy referenced in SMS messages & message boards.)
        2. (LT1343 Makes the permanent redirectable URL for the item part of its title)
        3. (LT135(LT135J Ends the title with the GUID it began with))
      3. (LT125T Pro: makes “prior, during, & after”, which I had often used in the link reference, now part of the name, as they are helpful as it’s too tempting to think of an event listing as just capturing ?before an event, not during & after which Web 2.0 sites as Meetup can do & excel in)
      4. (LT161S Completed quite a bit of work required to update all references due to this name change) )
    5. (LT8D04=On 2011.11.14~:
      (LSZTHR=(Meetup event listing’s )Thread of All Additional (Discussion+Happenings prior+during+after) from-First-to-Last http://1.JotHere.com/LSZ1QK)

      1. (LT8GDL=Now reconstructed this section from memory as WP lost this.)
      2. (LT8D3H=Added “=” between the ID & name
        (LT8D7W=as this seems to make increasing sense))
      3. (LT8D58=Put “Meetup event listing’s ” in “()”
        (LT8D7H=as it’s optional and dropped in uses where the subject already is that)
        (LT8DAD=as this is more like OOP methods where the goal is to have universal methods that work on many types/objects))
      4. (LT8GFJ=Replaced ” thread” at end with “Thread of ” towards start
        (LT8GGF=Notable pro: made root concept easier to reach as the rest is a mouthful especially with its longer length)
        (LT8GIF=Pro: Allows “Thread” to be capitalized w/o distraction and be nearer to the ID LSZTHR which parallels its name.)
        (LT8GHY=Con: 3 characters longer)
        )
      5. (LT8DBR=add “All ” as this is where all of this goes, not just some of it.)
      6. (LT8DDA=Replace “Discussion” with “Discussion+Happenings”
        1. (LT8DDV=”Happenings”, compared to “Details”
          (LT8DFM=Pro: More active & appealing)
          (LT8DG9=Pro: Conveys the time component))
        2. (LT8DHF=”Happenings” compared to “History” or “Planning”
          (LT8DI4=Notable pro: all inclusive here, covering past+present+future))
        3. (LT8DJI=”Happenings” compared to “History+Planning+Creation+Changes+Results”
          (LT8DJX=Huge Pro: seems to mostly cover all this in 1 simple word.)
          (LT8DKR=Con: emphasizes “Results” fine but not the other words as much.)
          (LT8DT1=Con: seems to cover a bit too much, as potentially sub-events))

        )

      7. (LT8F92=”Discussion+Happenings” compared to “Happenings+Discussion”
        (LT8FAG=Pro: “All Additional Happenings+..” would strongly suggest sub-events, though flipping the words doesn’t less this too much)
        LT8FGW=Ideally we want all happenings to be discussed so discussion is the goal so comes first.))
      8. (LT8ECR= “Discussion+Happenings prior+during+after” compared to “History+Discussion+Planning+Reporting+Results”
        LT8F13=tiny pro: slightly better I think as the term “happenings” summarizes, but a real toss-up
        )
      9. (LT8G0W=Replaced “prior, during, & after” with “prior+during+after” as this is shorter & easier to absorb at least in reading (harder to say, though))
      10. (LT8G5M=added “from-First-to-Last
        (LT8G67=Pro: this is a very important characteristic of this thread)
        (LT8G79=Compared to “increasing chronological order”
        (LT8GA9=Pro: shorter & simpler
        (LT8GAM=Pro: specifies from start-to-finish)
        (LT8GBI=Con: mostly but not always clear it refers to time.))
      11. (LT8K0L=Drop the end space ” ” before “)”, so replace “<url/> )” with “<url/>)”,
        (LT8K31=as Meetup BBoard posts now don’t seem to mess up the URL if no ” “))
      12. (LT8H0L=I am still not happy all the words in this name!)
    6. LT8GMW=2011.10.17, renamed to:
      (LSZTHR=(Meetup event listing’s )discussion thread of All Additional Aspects, from-conception-to-legend, in that order http://1.JotHere.com/LSZ1QK)

      1. (LT8GVA=This is a complete rewrite of the OOP method component of the prior name, that took me the following steps:
        1. (LT8H03= frustrated with prior name, I started permutating & effectively replacing virtually all of it:
        2. (LT8H8D=”Happenings” is really too broad as noted (as “Additional Happenings” suggests other events, not what we want).  What we want is “Characteristics”, “Attributes”, or “Aspects” of the event.)
        3. (LT8H1T=But then “Discussion” doesn’t parallel these well, as “Discussion+Aspects”, indeed “Discussion” isn’t really on the level of “happenings”, just an aspect itself, but it is important quality of the whole thing. So where to put it? Hey move it say next to “thread” –indeed that’s where it usually is, anyway: “discussion thread of” –yeah!)
        4. (LT8J3K=Drop caps of everything but the most central concept, in this case “All Additional Aspects”, that way one can quickly see what is the most essential part in this long name.)
        5. (LT8H3G=”from-first-to-last” made me think more time-wise to the phrase “from-cradle-to-grave” but we want beyond that, exploring an idea that likely materializes, so came up with “from-conception-to-obsolescence” to cover its entire aspects.”
          (LT8H5V=hey, those then remove the need for “prior+during+last”!))
          )
        6. (LT8HFL=but while “from-conception-to-obsolescence” gives the range of attributes, we also want to say they are listed in that order, so insert “listed”.
        7. (LT8FRU= So now pioneered rephrasing that to “discussion thread of All Additional Aspects listed from-conception-to-obsolescence“)
        8. (LT8GZ3=However that has the drawback that sounds like it means or could-mean “from-conception-to-obsolesce” of the particular aspect, not the whole thing. So we really have to put “add “in that order”:
          (“discussion thread of All Additional Aspects from-conception-to-obsolesce listed in that order“)
        9. (LT8HRA=It’s nice to have “listed” and it applies makes sense for something in writing, but if it were a video-log or talk that wouldn’t make sense. Moreover it’s redundant as “discussion thread” implies writing. So to save a word in already long name, cut it.)
        10. (LT8I7G=Add some needed punctuation to get:
          discussion thread of All Additional Aspects, from-conception-to-obsolesce, in that order“)
        11. (LT8IS9=”Aspects” is not the perfect word. But it’s pretty good and I can’t think of anything better.
          (LT8ITG=alternative “Stages” nicely parallels “from-conception-to-obsolesce” but then that wouldn’t cover people’s opinion & discussion & viewpoints plus individual properties, as “aspects” does.))
          )
        12. (LT8IVZ=Change “obsolesce”
          (LT8J0O=”obsolesce” is accurate & true (yes, I suppose eventually everything is entirely obsolete), but very depressing. Indeed almost as bad as “grave”. Plus a bit intangible. How do we really know when something is entirely “obsolete.”
          (LT8J14=So I came up with an alternative: “legend”!  That’s positive! Okay, yes, it’s usually not so realistic, but why not in some sense? And does it matter? Probably not. Plus if you’re going to deal with this mouthful name, you might as well have some fun with it.).
          (LT8IZQ= So present result “OOP method”:
          “discussion thread of All Additional Aspects, from-conception-to-legend, in that order” –yeah!) )  )

      )

    LT10FI)

  6. (LT2HIS Additional History, in order

    1. (LSZ1PK (to (address-the-shortcomings-of and replace my present solution, as (LSZFPF (Every Meeting has it’s own (live) Meeting discussion thread) LEUFYB..) details))
      (I created (this post http://1.JotHere.com/521 (from scratch=by copying (nothing) then removing all that didn’t apply and correcting the rest)) and set its ID to (new ID LSZ1QK)))
    2. (LT2OFL ~yesterday
      (LT2OQ0 I like this post format so much)
      that (LT2OQC I intend this post to be a template for other posts
      (LT2OQK but where, by design, many of the template’s IDs now don’t need to be but AREN’T replaced by fresh ones in instantiation but instead can serve as a permanent field name
      (LT2ORL which is a very different way of thinking of section IDs but simply practical & unavoidable)))
    3. (LT2OS7 ~this morning, see 1st use of this as a template at LT2FH3)
    4. (LT2NC0 – (LT2O2Z since (LT2OQC I intend this post to be a template for other posts …) but it has not yet been copied but 1x)
      (LT2O3H changed-else-introduced the following IDs to section the post components:

      1. (LT2NFH changed (LT2NC0, which wraps around the post body) to LSZPOS to be short for “POSt”)
      2. (LT2NFH created guid LT2MOD to wrap around the last mod date/ID)
      3. (LT2NMK created guid LT2VER to wrap around the version # info)
      4. (LT2NOP created guid LT2NAM to wrap around the title (LT2NQI found a nice way to do this without messing up is nice-center look) and hopefully suggest that the name needs to be in a particular format as it does)
      5. (LT2NSE changed (LSZ1VW, which wraps around the definition) to LSZDEF)
      6. (LT2NU2 changed the ID of (LSZFK7 Comparison with Related & Prior Constructs…) to LSZCMP)
      7. (LT2NX0 changed the ID (LSZ1U9 Motivation…) to LSZMOT)
      8. (LT2O21 changed the ID & (name so concept) of (LT2E2Z Additional Changes, in order ..) to (LT2HIS Additional History, in order …))
      9. (LT2O2H did NOT change the other section IDs as they didn’t seem so reusable)

      (LT2O3Y which substantially increased the readability, including making the IDs less obnoxious and much more clear what they were supposed to mean) )

    5. (LT2P9L add & define last section (LT2PLN Additional Planned Changes, in order …)
      1. (LT2PO4 making this just after (LT2HIS Additional History, in order..) and last has overall advantage
        1. (LT2PQ7 Pro: the (LT2HIS Additional History, in order..) reads directly & logically into the (LT2PLN Additional Planned Changes, in order …))
        2. (LT2PS1 Imagined Con: it breaks the traditional newsprint form of put your most important point first & your least last)
        3. (LT2PUE Pro: as this text is not newsprint but electronic posts, the least likely to be read text is likely not at the end but near the end, exactly where (LT2HIS Additional History, in order..); the end would get not a lot but a bit more traffic, and that then is where recent changes/history and also important (LT2PLN Additional Planned Changes ..) would be seen) ) )
    6. (LT31TO 2nd use of template to create (LSAUBO famous Chipotle Mexican Grill http://1.JotHere.com/LSAUBO ): make some updates (the 1st entry of LT2HIS=the post creation entry) to support that.)

    LT2HIS)

  7. (LT2PLN Additional Planned Changes, in order

    1. ()

    LT2PLN )

  8. )

LSZPOS)