Participant 9

TASK 1

[7:09pm] changes site name
[7:09pm] hoo zah!
[7:10pm] task complete
[7:10pm] "nice and simple"

TASK 2

[7:13pm] notices vertical tabs
[7:13pm] "i like"
[7:13pm] like vertical tabs
[7:15pm] ISSUE: Adds revision information even when creating new content - does this even get saved properly?
[7:16pm] BUG: preview looses rev log message
[7:16pm] shouldn't revisions need to be enabled?
[7:17pm] nevermind, that's just the default setting. getting tired
[7:19pm] ISSUE: expects to find a listing of nodes per content type.
[7:19pm] admin/settings/site-information - putting node/1 as the front page to get it to show up "I'll fix it later"
[7:20pm] ISSUE: front page selection does not say what shows up by default
[7:20pm] Should say "By default, nodes which are promoted by the front page are displayed"
[7:20pm] ++
[7:21pm] ^ +1
[7:22pm] • ultimateboy is beginning to see a few issues with that menu patch
[7:22pm] ISSUE: we removed the default menu item for primary links, and hes looking for it.
[7:22pm] well ya.. but thats not in d6 currently...
[7:23pm] thats not to say that it still should not be there
[7:24pm] Deals with creating menu items by remember paths, hovering over titles in admin/content/node or with the path module
[7:24pm] "Maybe there's a better way to do it but I haven't found it yet"
[7:25pm] POTENTIAL ISSUE: if users are using path to make menu items, ugly things start happening when those paths change..
[7:25pm] they're resolved to the system path when saving.
[7:25pm] (I think)
[7:26pm] looking for a way to put his menu item on left side from page .. using menu admin page
[7:26pm] Entering items into each menu individually - just realised he could move an item between them.
[7:26pm] indeed
[7:26pm] Puts it straight into navigation to get it in the left sidebar.
[7:26pm] though that could be extremely confusing
[7:26pm] TASK COMPLETE

TASK 3

[7:27pm] wait, I entered "alias" and now it says "node/2"
[7:27pm] did that work the way you expected it to? "uhm.. no, I have to say the menus thing is something I've struggled with a lot"... paticularly when working w/ different roles/themes
[7:28pm] this guy is used to people being smart and putting site-specific links in their own menu, rather than crowding them into navigation.
[7:28pm] he also wants adminmenu
[7:28pm] Another adminmenu fan.
[7:29pm] thinks menu name is "machine name"
[7:29pm] ISSUE: machine readable wants underscore almost everywhere. on menu, it wants dash
[7:30pm] (and it's labelled menu name here :D)
[7:30pm] I hate that!
[7:30pm] since it's the same concept, would be nice to see unified verbiage.
[7:30pm] Wants javascript validation instead of saving then getting told off.
[7:30pm] and unified validation
[7:30pm] and automatically create it like machine names now do
[7:31pm] "theres something on the whole about this page that makes me feel uncomfortable"
[7:31pm] "navigation makes me most uncomfortable"
[7:31pm] "There's something about this navigation menu, which as a whole makes me uncomfortable, since the very first day I used Drupal"
[7:31pm] ^he loves admin_menu
[7:31pm] talking about blocks page "this I like"

TASK 4

[7:34pm] thinking about dates, calendar, signup
[7:34pm] Thinking about calendars, sign-up etc.
[7:34pm] "what I'm thinking now is cck"
[7:34pm] "What I'm thinking right now is CCK"
[7:35pm] looking at core modules
[7:35pm] BUG: fcking field API modules aren't hidden.
[7:36pm] (and testing)
[7:36pm] "so I'll just add a content type, even though it may not be much different"
[7:36pm] Doesn't want to add a content type because there aren't extra fields.
[7:37pm] does not see added benefits from separating content types
[7:37pm] "I wouldn't make a new content type unless there's something unique about it"
[7:38pm] ISSUE: Once you set a different front page, 'promoted to front page' doesn't mean anything.
[7:38pm] ISSUE: this guy is overly complicated things
[7:39pm] but he is exactly correct
[7:39pm] useful for blocks though.
[7:39pm] flag in core baby.
[7:39pm] ++
[7:39pm] or specifically, views as a block.
[7:39pm] it does nothing in core when a single node is selected
[7:40pm] although most people nodequeue for that I suppose.
[7:40pm] • ultimateboy coughs "core"
[7:40pm] also shows up on /node and rss.xml though so we can't remove it.
[7:40pm] • catch cries
[7:40pm] indeed

TASK 5

[7:41pm] understands task and how to do it
[7:43pm] user permissions completely understood. appears to understand inherited permissions
[7:43pm] going above and beyond and adding a user with role of speaker
[7:43pm] Creating a user to assign the role to so they can post stuff.
[7:43pm] even going so far as to create a speaker account

TASK 6

[7:45pm] Knows that menus are really hard to maintain long term if you want multiple nodes assigned to them.
[7:46pm] does not appear to know about taxonomy
[7:46pm] until he sees the word
[7:46pm] "I think I'll use taxonomy for that"
[7:46pm] still does not think that is the best way to do it
[7:46pm] Weighing up taxonomy vs. CCK.
[7:46pm] looking for other options
[7:47pm] goes for taxonomy
[7:47pm] edits the tags vocab
[7:47pm] changes it to workflow content type
[7:48pm] Didn't immediately uncheck tags.
[7:48pm] ISSUE: Tags vocabulary overlaps with tags option in vocabulary settings (change to autocomplete)
[7:48pm] ISSUE: checkbox is very confusing.. should be a select list or radio button
[7:49pm] Gave up on taxonomy after seeing tags.
[7:51pm] ISSUE: taxonomy help text is way too freaking long. needs a big 'add vocabularly' button
[7:51pm] "I don't read all this text, I look for cues of functionality"
[7:51pm] as his eyes are flaring across the page "you might be able to tell that I dont read all the text"
[7:52pm] thinks as taxonomy as free tagging
[7:52pm] thinks taxonomy is most useful when a strong structure is not imposed on it.
[7:52pm] Got it.
[7:53pm] Back on track, adding terms.
[7:53pm] note: he edited the default tags vocab
[7:53pm] (and didnt create a new one)
[7:55pm] ISSUE: taxonomy terms not listed in order user entered them (still)
[7:55pm] lol
[7:55pm] I think we get the point on that issue
[7:56pm] Really strong association between tags and taxonomy.
[7:56pm] in his mind "taxonomy" = "tag"
[7:56pm] The skill levels are an 'attribute' - not to appear in a tag cloud.
[7:57pm] "Taxonomy seems like too advanced a notion for something this simple" (three options in a select list)

TASK 7

[7:58pm] Straight to blocks.
[7:58pm] Everybody loves blocks.
[7:59pm] Task complete.
[7:59pm] 2 minute task.
[7:59pm] "blocks has come pretty naturally as a new Drupal user"
[8:00pm] task 7 follow up
[8:01pm] ISSUE with task description: "admin" instantly relates to 'roles' and 'permissions' in users minds
[8:02pm] Knows how to use page visibility, but associated admin with the role.
[8:02pm] "finding an easy way other than defining admin/* in block configuration"

TASK 8

[8:03pm] goes to administer content types
[8:03pm] nice! '/admin' is excluded even though 'admin/*' was entered.. I guess that was fixed
[8:06pm] figured out it's not there, goes and uses full html on node, when told that there is a security risk involves, starts looking for an image content type
[8:07pm] "I've yet to figure that out, in my real life" PRESENTATION
[8:09pm] on the filter help text "uhg.. too much text"
[8:09pm] "google-ing it now"
[8:12pm] "Now configuring filtered html filter " - he got it after getting a clue
[8:12pm] "wow, didn't know that this existed"
[8:12pm] "wow, ok.......geez"
[8:12pm] "that definitely made me feel stupid"
[8:13pm] NO!
[8:13pm] seems to expect search to be enabled already
[8:13pm] we have no task 9

TASK 11

[8:14pm] not the first to do so...
[8:15pm] pressed reindex site
[8:15pm] runs cron
[8:16pm] doesn't realize search block is already showing
[8:16pm] enables search block
[8:16pm] actually realizes last minute it's showing
[8:16pm] does not enable search box
[8:16pm] question: so you would expect that to be disable? user: "yeah, because everything else is"
[8:16pm] expected search block to be disabled at once (default appears in garland)
[8:17pm] "in my mind it broke a drupal paradigm. I'm wondering if I put it up in the header if it would be there as well"
[8:17pm] "and now I'd have no idea if you asked me to get rid of that search" (talking about default enabled search box)
[8:18pm] Here comes trigger!

TASK 12

[8:18pm] knew about trigger.module
[8:18pm] he know triggers
[8:20pm] task complete.