- the lastMod_version_status=pst2012.01.21Sat0934 6.2 released
- the title=our Meetup.com groups’ visit to SCALE10x http://1.JotHere.com/LX26CM
- LX26NU: “SCALE10x” is the official abbreviation for “10th annual Southern CAlifornia Linux Expo“.
- LXTXOE: –a “fantastic event .. a convention of all things open source that keeps growing in size every year“ —says William
- LY1L5X: –a “community organized event” “celebrating its tenth year”, the largest-by-far open source software conference in Southern California IMHO, with “over 100 seminars and presentation sessions, and an exhibit hall where non-profit and commercial organizations will demonstrate the latest developments in the open-source and free software realm” (quotes from official home page)
- LY5SLY: The SCALE Wikipedia page now gives its history and says it’s “one of five community run Open-source software events in the United States, as of Spring 2011. It attempts to maintain a balance between commercial and non-profit organizations.”
- LX7R55: The conference would be better titled say “10th annual Southern CAlifornia Free Software and Open-Source Conference=SCAFSOSC10” (changes in italics).
- LX27A0: “our Meetup.com groups” are OC-PHP, OCDrupal, OCAndroid, OC iOS, Ubuntu Hour (of Lake Forest), and ideally more (indeed any Meetup groups which refers to this article for the details).
LX23GM: Where: a hotel by LAX, Los Angeles, CA 90045
- LXTZXO: RSVP on our Meetup event listings for exact location & our hotel room(s)..
LX2WUA: Our Last Visit:
- LX2X4T: Great conference, better than I expected, definitely would go again & for more!
- LX2X56: Seemed ~500 people attended and were all having a great time!
LX24VH: OC-PHP+OC-Drupal+OC Android will be running a booth at the conference, staffed by our members, to promote our groups!
- LXXI6O: From the Special Events, here’s the official booth listing for OC-PHP, for OCDrupal, for OCAndroid.
LX2554: FREE FULL-ACCESS PASS to the conference for all days, a $70 value!
–IFF you RSVP YES on our Meetup event listings with the needed info and then we select you to help staff our booth & you agree & do so.
- LXX97B: ” We do have a very limited number of full access passes to give out to those who help out…” posts OC-PHP head William.
- LXXIJ5: In order to qualify for the free full access pass, one would need, for the booth, to
LXTYC0: Intro on what helping our booth entails:
- LXXQZL: “…[At the “Expo”=Exhibits (on Saturday & on Sunday & not on Friday)],
- LXXR05: ..[each ] volunteer would
- LXXR2Z: The .. booth is to
- LXXR6A: [And ]when you are not volunteered to be at the booth, you are free to watch any presentations or walk the exhibition hall.
- LXXS5B: Additional details are in William’s volunteer email below BUT, since the immediate details are included here, that you can read after you’ve scheduled your shifts & resources:
- LXXQZL: “…[At the “Expo”=Exhibits (on Saturday & on Sunday & not on Friday)],
–see this for what you & everyone’s volunteering for and to set what you’re doing.
- LX5MT3: To pick what you’redoing, do in order:
- LXU0FJ: RSVP YES on our Meetup event listings with the needed info.
- LXTZRA: sign into your Google Account now
- LXU09W: –required now to overcome a Google Docs bug: so the later “Sign in” button will give you a general Google Account login, not the odd ~”Sign in to your account at \ OCPHP | Orange County PHP \ Username: firstname.lastname@example.org” which will be useless to you unless you actually have an account on ocphp.org.
- LXTZSK: see/refresh our latest schedule for our booth
- LXU07B: if the upper-left button still says “Sign in” (a bug in Firefox 9.0.1 but not Chrome 16.0)then click it and it will refreshed where indeed you are signed in from above.
- LXTZSY: If you are still listed as a viewer, do File->Share and enter an email address for yourself (which is/will-be linked to a Google Account), and William will send you an email to there telling that email address now has edit access..
- LXTZT6: When you’re viewing with edit access, in your columns, put a “1” in every box which you can do (a booth-time or -supply) or “0” if you definitely can’t do it, else William assign you
- LXXQFI: Ideally give not just “your answer but also your reason as “0 as attending http://…” –see examples below and on the spreadsheet itself.
- LXXQIX: An added benefit to you in the case of time slot answers: your “0” (no) answers with reasons (what you’ll be doing instead) then also allow you to keep track of & share of not just your booth staffing plans but everything you’ll be attending at the conference!
- LXXQ2H: To make smart choices & detailed responses, for each time slot, first review the conference schedule as to what is happening now including “give yourself the chance to walk the exhibition floor”); then you can reply with say
- LXXQ51: “0 as attending http://socallinuxexpo.org/scale10x/presentations/create-stunning-videos-openshot”
- LXXQ70: “0 as will attend something on http://socallinuxexpo.org/scale10x/schedule “
- LXXQA7: “1 as no sessions on http://socallinuxexpo.org/scale10x/schedule”
- LXXQ7V: “1 as nothing on http://socallinuxexpo.org/scale10x/schedule interests me.”
- LXXQAU: “1 as events on http://socallinuxexpo.org/scale10x/schedule interest me but I need to put in some hours here.”
- LXU2NG: In the 1st layout of this schedule, each person was assigned a unique color. But in this 2nd redesign by Destiny, every person has his/her own clear column(s), so it’s no longer necessary to know & use your color: just put a “1” or “0” in the boxes of your column.
- LX5NJ0: With your volunteer schedule in place, William will email you your private promo code so you can register without having to pay anything! As William says, “When you get the code, please do not share or use more than once.”.
- LX5MT3: To pick what you’redoing, do in order:
LX5KZY: Especially if you’re going, please RSVP & post those details to help everyone:
- LX5MDI: What?
- LX5MFW: RSVP to our Meetup event listings (see below table) for all groups you belong to, and
- LX5MIS: As you figure out your attendance plans in more detail, post those details! In particular, tell us:
- LX5LNZ: Just RSVP now with what you know now (such as what days you can be there, and for what hours) and post more (as what events you’ll be attending) as you determine that.
- LX5L7C: Why? So we can
- LX5L7N: Where (to post these details)? LX5LVY: Are you RSVPing YES to multipleevent listings for the same thing (such as when you belong to more than one Meetup group which lists this event)?
- LX5LZV: If YES, post on this article as comment(s) below (ideally create a free login).
- LX5M1M:If NO, does your public RSVP comment give you enough room for these details?
- LX5MDI: What?
- LX23ON: As with all our events, follow Etiquette & Things-To-Know when RSVPing to any Meetup Event LEVV22;
- LX5N5V: for your convenience, the most important details of this which are relevant to this event we’ve tried to already cover above.
LX24U3: Official URL: SoCalLinuxExpo.Org/scale10x including schedule –read this!
LXIDIU=Scroll (horizontally=left or right) by selecting text range going left or right.
LX37AZ: Hours & Why go & Event listings –per day & per group
LX37MK: LX39T4: LX37DA: LX37DT: LX37JZ: LX3C5R: LX623L: LX37H6: Hours OC Android OC-PHP OCDrupal OCiOS Ubuntu Hour of Lake Forest LX37N2: Why go (besides being local) — open-source-mostly programmers open-source-mostly programmers open-source CMS developers closest is open-source-mostly programmers Ubuntu is seeming the leading Linux distribution LX37O6: Day 1=Friday 0900-~2100 http://meetu.ps/6lpws not yet; held-up not yet; held-up http://meetu.ps/6MmvK
group head Linus may have limited interest
44528412 LX37P8: Day 2=Saturday 1000-~1900 http://meetu.ps/6lZWP ditto ditto http://meetu.ps/6MnNg 44528392 LX37Q9: Day 3=Sunday 1000-~1730 http://meetu.ps/6m3hC ditto ditto http://meetu.ps/6Mpyg 44528402 LX38WI: Discussion thread — here ditto ditto use event comments ditto LX3C1K: Last time — here here none here TBA
- LX5X4W: Instead of depending on the Meetup group heads to do this, we need you members to
become event leaders! –for special conferences related to the group topic (such as this conference) or for this conference every time it occurs) –volunteer or nominate someone!
- LX5XDQ: Just post that as comments on this article else on the event listing.
- LX5XE0: Before you begin the job, read its _ track leader requirements & responsibilities (at least for OC Android).
LX5HIT: Other Meetup groups & similar community groups can super-easily list & advertise this conference as well
–as I’ve designed the (above) Discussion Thread and 3 event listings of OC Android as easy template for such!, with instructions below.
- LX5IDJ: By building on what’s already built here, another group can well-list this conference easily & just-minutes and with very minimal text that needs posting & updating, as most all the work I’ve already done for here and made easily-sharable.
- LX5I3R:a organizer-else member need only copy-them exactly then, in the respective places within their group, create 1 new discussion thread and 3 new event listings respectively, and
- LX5IOZ: Be sure to copy the content with all its formatting including links, bolding, & sizing & coloring; this is trivial if you follow instructions below.
- LX5I8I:For the discussion thread,
- LX5IV1:For each event listing,
- LX5I76: you must also set to match things that don’t copy, including that it repeats annually on the 2nd Friday/Saturday/Sunday respectively.
- LX5IVC: Copy the displayed HTML text and paste into Meetup’s event listing description HTML editor in (standard=WYSIWYG) mode, then recreate the little remaining formatting not copied.
- LX5I69: In your copy, just appropriately update the links & dates & stuff (the text needing copied I’ve kept super short).
- LX5IFC: When you’re finished, post a comment here linking to your discussion thread (and, if that doesn’t already link to them as it should, to your 3 event listings), and I will update this table (above) with your information!
- LX5J6P: I’m not familiar with anything like this intermediate shared post for event listings to link to give them their details, plus the templating system it offers (for additional self-made listings), though it may exist.
- LX5J75:I don’t know of any other conference like this in Southern California like this on this topic. The closest:
- LX263T: Why this post? I’m creating this OCAndroid 2011.01.20(Fri) event (see 1st version of archive) but see most text will be essentially be repeated by 3x for Fri-Sun, and that triple will then be potentially repeated on other Meetup groups, so I want to factor out all the common text to an article (this one) and just have the various instances link to it.
- LX2689= I (did not know of any JotHere article on this subject) so created this post http://2.loverules.info/631 by:
- LX369V=Around right after LX2689, decide to remove from status the #s as “1st” in “1st draft” and “30%” in “30% complete, as this is implied by a version number as “1.3”.
- (LX28UY: regarding the header section (last mod thru where), rather than make it not part of outline, make it part of numbered main body outline.)
- LX29DY=Make the where it’s own 1st section, to also to hold last mod thru the title.
- LX30QW=starting ~10 hrs ago, cut the “()” when the list-item does the nesting.
- LX30GH: take the title out of bold as it will already be featured by the WordPress theme: nah, worth bolding as it has key links.
- LX30W0=For the major headings plus the title, drop the parens per LX30QW except first replacing the “(” with “the“.
- LX314O: The highlighted “(” looks ugly & asymmetrical.
- LX316I: If one copies the “(” to make a link, because it’s a 1-character link, in WordPress 3.2.1, one can’t edit the text without dropping into HTML.
- LX3192: In English, “the ” is what’s implied already and so what you would say if not being terse.
- LX31B9: “the” is what one would generally would start with if copying to make a link as “the title“
- LX372B: Putting “the” not “The” calls less attention to a secondary and repeated word and is per the growing convention to write text in lower-case.
- LX31H0: By doing “the ” and not “the_“, with default formatting it makes it much clearer that the next item is a separate link
- LX34MK: From LX30W0, “(where” becomes “the Where” and no longer makes sense
- LX34RN: reads awkward and as if it was referring to geographic “where” which is not the case.
- LX34US: consider “the Givens”. That makes sense, but “givens” is a much rarer & unexpected than “Subject”.
- LX34WF:consider “the Subject” -yes, but it’s a different meaning so needs its own ID
- LX35L9: Pro: familiar & expected.
- LX35MH: Pro: more than “where” or “givens”, logically includes (the items included in it per LX29DY =”last mod thru where“)
- LX35IO: create link “Subject, complete & context-free” -nice but wordy
- LX3631: “Complete” is important because in the most frequent use of the “Subject” field, email, it’s usually half-thought & incomplete & bad.
- LX364Z: “Context-free” is accurate but a complex & unfamiliar idea. “Complete” is enough to say “Hey, there’s something special going on here so pay attention here when that could be important”.
- LX3600: rename link to “Complete Subject“
- LX35VM: replace “Where” with “Complete Subject“
- LX36KJ: Realize LX369V gives its own new meaning for status, so create new link “status” replacing the former.
- LX3BM7: Re this line (q=(last mod=2011.12.31(Sat)pst1455)(version=1.4)(status=constructing actively))-also it’s present value.
- LX3CD8: Small con: ugly in that “(” is a link but “)” is not.
- LX3CEC:several (3) individual fields which are pretty much taken as a unit but still separate is
- LX3CKU: Conceive & consider a single field-variable “lastMod+version+status” –yes!
- LX3D1W: Convert to this, so line now reads
- LX6X4E: In the prior version, changed official date format to say “pst2012.01.02Mo0228″
- LX6X6D: from say “2011.12.31(Sat)pst153″
- LX6X88: Includes time zone as “pst” in the start as
- LX6X9U: time zone determines not just hour and sometimes-minute, also day of month and (on edges) month of year and (on ages) year (for instance in any year x, in some time zones when it’s Jan 1st of year x, in prior time zones it’s Dec 31 of year x-1), so time zone would belong before even the year as it sometimes determines even that.
- LX6XCO: time zone typically also says “time” (via it’s “T”), so makes sense to put at start of whole time (which includes the date).
- LX6XG6: Day name is abbreviated to 2 characters to make it shortest while still standard.
- LX6XIX: Day name is capital-letter then lowercase-letter as a CamelCase shortening.
- LX6XY=Drop the parens as “()” around the named-day as this is only adds that it’s determined based on the date (YMD) which isn’t sufficient to justify the extra & special characters.
- LX61JA: Cut the URL from the title pasted into the WordPress title field
- LX61LX: Per the recent convention (last few posts here) of hiding the IDs whenever possible, especially as already done for the section headings
- LX61QU: Tiny con: might hurt search indexing if one was searching for just that ID but it’s not in the title.
- LX61OD: Pro: cuts down the clutter notably
- LX61NE: URL is still in (the title which is part of the initial body) where it is needed (should one want to reference the post in a non-formatted environment as SMS) and for indexing.
- LX7O8M: consider replacements for “Definition“
- LX7O9J: consider “Answer“
- LX7OA6: My idea
- LX7OAF: Mixed: Makes good sense when “Complete Subject” is replaced with “Question” or “Query” but not much sense otherwise.
- LX7ODP: Con: Sounds arrogant, especially as “the Answer“.
- LX7NFP: consider “Description“
- LX7NOD: Lucy proposes it (after a painful 2 hours getting her to understand the topic)
- LX7NPJ: Pro: More familiar & expected
- LX7NQQ: Pro: seems more appropriate when “Definition” couldn’t realistically be done (for say something which isn’t readily uniformly formally defined, say an organization or a person)
- LX7NQ8: Mixed: Seemingly a superset
- LX7NU7: Con: could allow “alternatives” (as “2x bigger than alternative y”) instead of putting that in (the section for it=Comparison with Alternatives, from most to least similar)
- LX7O1C: consider “Details“
- LX7VLT: Did these plans:
- .LX321F=LX2XL1 needs to be its own post.
- LX36ZH: after LX321F, in the subject, put “SCALE” definition before “Meetup” (per new the title) and move “<!–more–>” link right after “the details“‘s “When & where”)
- LX7VW2: renamed “Complete Subject” to “Subject“