text:
The current Books page (listing published books about Drupal, currently at http://drupal.org/books) is hard to maintain, as it is a collection of several static pages.
Proposed resolution
Create a Book Listing content type, and a filterable View, to replace the current static pages.
Development site: http://docs-infra-drupal.redesign.devdrupal.org/books
Guidelines discussion: #1681566: Decide on guidelines for new Book Listings content type
Test site: http://marketplace-drupal.redesign.devdrupal.org/books
Remaining tasks
Test and deploy.
Deployment instructions
- Remove /books path alias from http://drupal.org/node/42200 ( admin/build/path/list/books to search )
- Upload and enable drupalorg_book_listings feature ( admin/build/features )
If /books pages gives "invalid vocabulary is selected" or "illegal choice" error - go to Views ( admin/build/views ), edit the book_listings view, click on first Taxonomy:Term in Filters and select "Book availability" as the taxonomy, and select "Available" as the default. Do the same taxonomy selection in the Availability taxonomy field (near bottom of fields list). Save the view.[note: the preceding should never be necessary]
- Apply the patches to bluecheese, drupalorg_handbook, drupalorg_crosssite projects and clear the cache
- Edit taxonomy vocabularies: Drupal version, Audience, Keywords, Level, Book availability, Book format to add them to "Book listing" content type ( admin/content/taxonomy )
- Enable blocks "Book listing add link" and "Book listings Information", and put them on the right sidebar in that order ( admin/build/block )
- Edit new Book Listing content type ( admin/content/node-type/book-listing ) and set:
- "Published" off
- "Promoted to front page" off
- "Sticky at top of lists" off
- "Create new revision" on
- "Attachments" disabled
- Comments are turned on
- Go to global Theme settings ( admin/build/themes/settings ) and check off "Display post information" for Book listing
- Check user permissions ( admin/user/permissions ): authenticated users should be able to create book listings and edit own book listings (these are in the "features" section of permissions).
To-Dos after deployment:
1. LoMo to fill in new content type using his Selenium script
2. Manually add a link to the new Books page from Documentation landing page, and from "Understanding Drupal" http://drupal.org/documentation/understand (where Books used to be).
3. Manually delete the previous node pages for the books listings, and redirect them to /books (or if we want to get fancy, to a filtered subset of /books):
Comment #1jhodgdon CreditAttribution: jhodgdon commented
Great proposal LoMo!
A few thoughts:
- Sub-title -- I think this should just be part of the main title field.
- "Any notes" -- we should just call this field "Description".
- Link to news & announcements -- hmmm. I'm inclined to skip this. If the Description field is formatted HTML, then you could put a link to the release announcement there; let's leave it at that.
- Order links - can't the Amazon order link be generated automatically from the ASID? Can something similar be done for Packt? I'd like to avoid the person creating the content item having to know what our particular vendor ID would be -- they're not likely to create the right links all the time.
- Preview link... again, maybe put this in the Description if it's available? And is it even necessary? I think Amazon/Packt both have some preview capability.
- Taxonomy - maybe we can just use the Keywords taxonomy that we have now for book pages? It seems like we don't need to have a separate one.
Comment #1.0jhodgdon CreditAttribution: jhodgdon commented
Minor edits, links, etc
Comment #4jhodgdon CreditAttribution: jhodgdon commented
- I don't think we need to exactly replicate what is currently on the Books page.
- Google Preview: yes that is what I'm thinking, it will be less likely they would use the affiliate link to purchase.
Comment #6jcnventura CreditAttribution: jcnventura commented
ASIN is the ISBN-10.. Explaining a bit how the OOcalc file that I used to use to generate all these pages work:
I add a new ISBN-10 to a text file that is passed to a script that crawls Amazon.com and gets all the remaining info (pages, ISBN-13, title, authors, etc. etc.). The result of the crawl is a CSV file that contains the basic template for a book.. Then I copy paste that into the OOcalc file and that one takes part of that information to generate some automatic links (such as the Amazon link and the Google Preview). The only "work" is finding the Packt page for one of their books, the author links and the announcement node for a book (we used to have book announcements on the old d.o homepage, but now no one does them anymore).
Ah, and of course resizing the image is also crap..
What I'd suggest for a new book/media content type would be to do the same. Creating a book node would start by asking the ISBN-10. Then it would crawl Amazon to fill most of what remains, and allow the user to edit them before "publishing" the node. The relationship to the book author's should be handled by a cck relationship field (author numbers vary from 1 to 30+).
The new book nodes should allow for commenting, which is something that only happens when someone decides to create an announcement node for a book.
So my list of fields:
- Title*
- Sub-title*
- Author(s)* ** (possibly multiple with human name linked to Drupal.org user)
- Drupal version(s)**
- Publisher*
- Date of publication*
- Publication status** (published, upcoming, cancelled, out-of-print)
- page count*
- Website for book**
- Publisher book webpage (only used in Packt books)**
- Book audience** (newbies, developers, themers, etc.)
- Cover image (imagecache)**
- Book description** (long book description as currently available in dedicated book announcement nodes)
* would be crawled from Amazon
** needs to be inserted manually
Comment #7jhodgdon CreditAttribution: jhodgdon commented
Having a crawler doesn't sound like something we can/will install on Drupal.org, and this seems more complicated than is merited. If I am adding a new book to the listing, it's really not going to take me that long to copy/paste a few fields from the Amazon page into the node creation fields, is it? We're talking about quite a bit of effort (it seems to me) to save someone a minute or two of effort each time a book-for-sale node is created, right?
Comment #9jhodgdon CreditAttribution: jhodgdon commented
Here's a list of the modules currently on d.o (sorry for the formatting, it's a cut/paste of ls sites/all/modules on my d.o test server, but should at least get you going):
apachesolr filter_html_image_secure path_redirect
apachesolr_mess_up_results flag project
apachesolr_multisitesearch flot project_dependency
autoload forum2 project_git_instructions
bakery google_admanager project_issue
beanstalkd google_analytics project_issue_file_test
bueditor homebox site_network
cck html5_user_geolocation sshkey
codefilter httpbl tracker2
comment_alter_taxonomy image versioncontrol
comment_upload imageapi versioncontrol_git
ctools imagecache versioncontrol_project
dbtng imagefield views
devel jquery_ui views_bulk_operations
diff link views_content_cache
drupal_queue materialized_view views_field_view
drupalorg memcache views_litepager
features multiple_email waiting_queue
filefield paranoia
Comment #10jhodgdon CreditAttribution: jhodgdon commented
Keep in mind that d.o is currently running Drupal 6, but it's supposed to be updated to D7 this year sometime (sprints may be starting this week at DrupalCon, and there's a big one planned for April).
Comment #12jhodgdon CreditAttribution: jhodgdon commented
It won't be split. There is a planned sprint next month to port project* modules and anything else that needs it.
Comment #15jhodgdon CreditAttribution: jhodgdon commented
The new plan looks good! I would just amend the Taxonomies section slightly, to say that we want to use the following taxonomies from Documentation Book nodes:
Drupal version [instead of it being a stand-alone field]
Keywords [note: this is the name of the "tagging" taxonomy you are I hope referencing]
And then you would have another taxonomy for
Publishing status [values: Published, Upcoming, Out of print]
Otherwise, let's go for it!
Comment #15.0jhodgdon CreditAttribution: jhodgdon commented
Updated to reflect a more full development of the plan.
Comment #17jhodgdon CreditAttribution: jhodgdon commented
+1 green light from me. :)
I think it's OK to put in your request now for a server. jredding indicated to me that he's not so concerned with the exact formatting etc.
Comment #20jhodgdon CreditAttribution: jhodgdon commented
Hey, I was thinking while I took a walk today (always a good time to think) and you can probably use the existing site I've been using for some other docs infrastructure issues. It's at
You'll still need ssh access to the server in order to get anything done (such as log in as admin).
Comment #22jcnventura CreditAttribution: jcnventura commented
@LoMo: I can provide you the current OOcalc spreadsheet so if you want to import data from that, it could make it simpler to you.
As to my comments in the now-closed issue.. I do like the way it is (but I preferred the way it was :).. However, I agree that "power-users" are probably not using that page anyway (they'd be following amazon.com sorted by release date), so no one is really interested in having the newest books on top vs. having categories. What I did have is a system that alllowed me to update that with minimum effort. After these changes the effort is increased somewhat, so I'll stop curating the list.
However, and looking forward, I see we're finally moving away from the this-is-crap-but-leave-it-until-we-make-it-a-view approach to someone getting his hands dirty.. I'd be willing to help if you need.. It'd be neat if we could eventually recycle the existing book articles to the new content-type, in order to maintain the existing system.
I'd suggest that you organize the work as a feature that is created around a book-type module. This would include the content type, imagecache presets and the view, but it might be useful to separate some code (like a mutable list of bookstores depending on the user's geo location).
Comment #24jcnventura CreditAttribution: jcnventura commented
I'd suggest keeping the book-content-type-features-module generic.. Develop it as something that might be useful to other sites, and everyone will benefit from it (including d.o).
The reason why I chose Drupal over Mambo (yeah, that long ago), was because of the biblio module, which defines a content type and a list for scientific papers, that is useful to academic institutions and to wannabee scientists with their small collection of papers (like me).
I'd suggest looking at the Amazon module and see what could be done to improve it, instead of starting from scratch and ending up with something like the project module that is so d.o.-specific that it needs someone to come and work on it every time d.o. needs to be upgraded.
Comment #27webchick CreditAttribution: webchick commented
Well, we might be able to put Date module on d.o. Could you open a separate issue for that (probably in the "Drupal.org Infrastructure" queue)?
Comment #28jhodgdon CreditAttribution: jhodgdon commented
Comment #30jhodgdon CreditAttribution: jhodgdon commented
From IRC - drumm says that we can have the Date module on d.o when we're ready to deploy this. :)
I will go add it to the staging server...
That is done. The Date module is added to (installed/enabled) docs-infra-drupal.redesign.devdrupal.org
Comment #31jhodgdon CreditAttribution: jhodgdon commented
Version I downloaded of Date is 6.x-2.8
Comment #32jhodgdon CreditAttribution: jhodgdon commented
RE images on #31... What I would do is:
a) Use a file field (with image widget/formatter).
b) Set this image field so people have to upload the largest size you actually need, and don't allow anything larger than that to be uploaded.
c) Create a new imagecache preset (or presets) to resize to the smaller size(s) you need. Use those in the View and in the full Node display settings.
d) You can use CSS to make the image float to the right spot in full-node and Views page. That will be a patch to the Bluecheese theme.
Ignore the existing Imagecache presets... they are for some other purpose that we don't need to worry about, unless one of them happens to resize to the exact size that you need, in which case you don't need to create a new one.
Comment #34jcnventura CreditAttribution: jcnventura commented
The "Advanced Flex Application Development" book covered Drupal partly at a time when almost no books covered Drupal.. Nowadays that there are 70+ with Drupal in their titles, it seems strange indeed :)
Would there be a way to provide me with enough credentials to see the links above? Currently it asks me for a username and pass.
Comment #35jcnventura CreditAttribution: jcnventura commented
Also, note that I stopped updating the German list once the German books were removed from d.o.. I know of a lot of Drupal books in Spanish, French, German and Brazilian Portuguese. Using Drupal 1st edition by webchick et al, was translated into a lot of languages :)
Comment #37jhodgdon CreditAttribution: jhodgdon commented
LoMo: Please don't grant anyone admin permissions on the docs-infra site without checking with me first -- I am also using it for other issues. jcnventura is fine to add. :)
So... I took a look at the new site. I have a few suggestions:
a) Rather than having different pages like books/current, books/current/site-builders, etc. -- just make one page called "books", with some default values for the filters, and give the user the ability to filter by Drupal version, audience, and current vs. upcoming vs. out of print. I also think it would be good if all of those filters allowed multiple selections (e.g., find books on Drupal 6 for both site builders and themers).
b) With the page full-screen like this (no right sidebar), it's hard for me to scan and associate images with books. Maybe the image should go on the left, which would probably make the images closer to the text?
c) Regarding stale modules, the server should be using the same versions that are on Drupal.org, as of a couple of weeks ago when it was built.
Comment #39jhodgdon CreditAttribution: jhodgdon commented
(a) What do you mean "we need to build menus for that or something"? I don't see why, just use exposed views filters. We don't need to get fancy.
(c) I am certain that when the site was built, module config was the same as drupal.org. It's possible drupal.org has been updated in the meantime, but updating contrib modules often introduces incompatibilities (in my own experience maintaining sites), so I wouldn't count on it. Just export with what you have.
Comment #41jhodgdon CreditAttribution: jhodgdon commented
Yes, of course, we are going to use this instead of the current path /books, and we can redirect any other previous URL aliases to appropriate filtered pages.
Regarding sorting -- I don't think that's a killer feature really, and having full filter capability would more than make up for it, in my opinion.
Comment #44jhodgdon CreditAttribution: jhodgdon commented
What is "archive" in #43?
Other than that, I like #43 over #42 (as stated above, I think the flexibility is better to have).
Comment #46jhodgdon CreditAttribution: jhodgdon commented
If you are still unable to ssh into the site, let me know what lines need to be added to the CSS and I will add them.
Anyway... the site looks pretty good to me!
A few comments on the current look of the books page on the test site:
a) I am confused as to why the typography is so strange on the title. I would undo everything custom you did in the view fields and see if it gets better (you should be able to just use the fields as-is). I didn't realize the book titles were links in their current state, and I think it's because they have H3 inside the A link rather than the other way around. Also, if you just use the default field formatting, you'd get bold field labels, which IMO would be a plus for scannability.
b) The order links for Packt -- should it have some kind of vendor code in it?
c) Is there going to be any difference between the full-node view and the summary in the View page? Right now I don't see any except that the image is larger. If there is no difference, I would not bother to make the book titles be links or indicate that there is a page view at all. If there is a difference, I think a "more information" link at the bottom of the listing would help make it clearer that you can click through (especially for anyone familiar with the old page, which did not have any extra information available).
d) If we are keeping the full-node page, let's make the image about half the size. Actually, I really don't see why it needs to be any bigger than on the view page, but if you want you could make it that size, and if you click on it you could get the full-size image.
e) Formatting nitipicks:
- I don't think we need the (s) on Drupal version or Level. It makes them look strange in comparison to Audience.
- Field labels should be bold (mentioned above).
- ISBN-13 label could just be ISBN
- The two "order from" labels should have the same label (Order from:) and both end with :.
f) I went to /node/add and I think the "on drupal.org" should be left out of the content type description. If you do feel it's necessary, it should be "Drupal.org" (capitalized). It probably also shouldn't start with "A book listing...", since all of the added content types omit duplicating their content type names. So it could just start with "Describes a book...".
g) I also went to the node edit page to look at that. It looks mostly good, with a few small nitpicks:
- On the author field: just tell people what to do, not "ideally", and there are some grammar/punctuation issues.... How about:
Enter list of authors' full names (as shown by publisher), with each one being a link to that author's Drupal.org user profile. Include a title attribute on each link showing the Drupal.org username; e.g., [your examples]
- Book status: "Select a term describing the book's current availability." -- none of the other vocabulary descriptions say "a term"... I think you could actually just change the vocabulary name to "Book availability" and leave out the description entirely.
- Brief notes: Can you make the help text much shorter, and not use "ideally"? Probably it's not necessary to describe in depth what it's used for.
- Publisher help - obviously you left notes for yourself to change this...
- Page count field manadatory?!?!? I think this is unlikely to be known for books that are not yet in print.
- Generally... I didn't get through the rest, but you get the idea -- make the help text short and definite.
- Maybe add help text to website field explaining this is a web site about the book, not where to purchase it? Or omit this field -- do we need it for something? Also make sure when it is output that it is "nofollow".
Comment #47jhodgdon CreditAttribution: jhodgdon commented
And a couple more thoughts:
Generally, when I build D6 content types for sites, I avoid using the built-in D6 "body" field, and substitute a CCK field. The body field is special, and is very difficult to use for theming and filtering later, should that become necessary. In this case, I think I would just have one field for the description (get rid of the brief/long dual field), and just cut it off at, say, 250 characters (experiment with this cut-off) with a "read more" link at the end for the view.
And regarding the node add/edit help, I would point you at these UI text guidelines/standards:
Comment #49jhodgdon CreditAttribution: jhodgdon commented
You should be able to turn on/off display of any fields you don't want displayed for the node, on the Display Fields settings page for the content type... oh I see, you do need a template, or maybe just a preprocess function -- and hopefully just for the ISBN-10 field display and not the whole content type? That would be preferred, because then if someone adds a field at least it would get displayed. Hopefully you can take care of this.
Regarding image sizes... The cover image is not all that important and it takes up nearly a screenfull of space on the full node view. Use a smaller image and link to the larger one if you want, but don't make me scroll just to see the information I actually need. Right?
Regarding order from... You could just make the link text "Order from Amazon" and "Order from Packt", and leave off the "order from" labels entirely? Those would be more usable/accessible link text anyway. Just saying "Amazon" is not good UI design actually.
Regarding custom/rewritten fields vs. using the default field output: I would try to keep this at an absolute minimum -- like rewrite individual fields if it's entirely necessary, but don't set all of them to invisible and have one big rewrite. Those kinds of things are just really difficult to maintain, in my experience, and it's preferable to live with things not being absolutely perfect vs. impossible to maintain. IMO.
Anyway... Let me know when you're done with a round of changes and want another review, and I'll take a look.
Comment #51webchick CreditAttribution: webchick commented
|» Needs review
Marking needs review. Nice work on this, LoMo!
Comment #55jhodgdon CreditAttribution: jhodgdon commented
A better place for the preprocessing might be in the custom module for this feature, rather than in Bluecheese, but that looks like a good approach.
I'll make some time later today to give the test site another look. Anyone else following the issue can do so too. :)
Comment #56Taxoman CreditAttribution: Taxoman commented
Is there any way the results of this work could also be made as a "feature" for reuse on other sites?
(That would probably be a separate issue "somewhere", though.)
Comment #60jhodgdon CreditAttribution: jhodgdon commented
RE #57 - I guess it can be a bluecheese patch, but since it's code, I think it would be better to add to the drupalorg project instead of to the theme.
RE #56 - not sure what you mean by "this stuff". The content type and view will be exported as a feature eventually and added to the drupalorg project.
Comment #61jhodgdon CreditAttribution: jhodgdon commented
Sorry, I've been busy with the Drupal 7 port of the API module, and I've neglected this issue... just getting back to it.
So. I took a look at
It looks mostly great! I think there are only a couple of remaining things that should be fixed, and then we can make a patch and a deployment plan:
a) In the "official web site" link's title attribute, "etc" needs to have a . after it. [this is in the book listing page]
b) I did NOT like that after doing some filtering, when I then went to /books in another browser tab, it remembered the filter settings that I had used on the other tab. I think we should turn off the "remember my settings" checkbox for the exposed filters in Views, because it would make it impossible (I think) to be looking in one browser tab for current and another tab for upcoming books, for instance.
c) I don't think we need the "posted by" information to show up on individual book item pages. Turning that off should be part of the deployment plan.
d) The Status value needs to be shown for each book in /books, in case you are filtering with multiple terms selected. Also it seems to be not shown on the individual book page, and it should be.
e) The authors should not be shown twice on the book listing pages. Maybe that is specific to this book:
f) The authors are indented strangely on the book listing page (see authorindent.png attached screenshot).
g) When I logged in, at node/add I saw this description for the content type:
A published print-media book covering a Drupal-related topic.
What about electronic books? I think maybe we should just leave out "print-media" here.
h) When I went through to node/add/book-listing:
- Can the help/description for the Authors field give the raw HTML for the title attribute rather than the link (which isn't very useful really)? And we probably don't need two examples.
- Did you customize the "Please Choose" on the book availability or is that the default? Normally we don't use "please" in Drupal UI (I can find a reference for you if you don't believe me). So if you did customize it, put it back to the default please. :)
- Under Website: list it here -> enter it here
- Could the two ISBN fields be put next to each other?
These are all (I think/hope) fairly minor tweaks... The site looks great and is a vast improvement over what we have now -- so let's get this done!
Comment #63jhodgdon CreditAttribution: jhodgdon commented
RE (c) - *someone* has to make a patch and deployment instructions for this. I was hoping it was "your department", because you would know better than I would what changes you made in the admin UI.
But just as a note, there are a couple of things I think we'd want to do on deploy:
- We know from experience on past Features that did content types that the Publishing Options (published, promote to front page, sticky) are not set by Features for content types, so we need to specify to turn off "promote to front page" after enabling the feature.
- Similarly, the installer would need to visit the theme config page and turn off "display post information" for book listing nodes, if we want it turned off.
RE (f) - OK.
RE (g) - if someone publishes an electronic-only e-book, are you saying we couldn't include it in the Books listing? That seems silly, as I think people are increasingly going that route. I think it should encompass both print and e-books, and I don't see any technical reason why it shouldn't, if they have ISBNs and stuff?
RE (h) author - yes, use HTML entity
> and we really only need one example please (it doesn't even have to be a real d.o user or a real author).
Comment #65jhodgdon CreditAttribution: jhodgdon commented
g) OK, how about saying "published print or e-book"? :)
c) True... I'm OK either way. I was thinking that we would let anyone create/edit these book listing nodes, just like docs pages. What's your thought on that?
Comment #67jhodgdon CreditAttribution: jhodgdon commented
(c) further thoughts:
1) Where is this policy stated? What is a "regular publisher"? Paper books are really declining in popularity as time goes on, and the big publishing houses are losing market share. Why wouldn't we want a major Drupal project contributor's (future, hypothetical) self-published-on-Amazon but excellent e-book on Drupal 8.x to be added to the list? I think you're looking at this too narrowly. We should be inclusive rather than exclusive, if the objective is to help people find quality information.
2) What do you think people would mess up? It seems like the node/add page is pretty clear, and if it isn't, it should be made clearer in the areas you think would be problematic. What's the big deal anyway? If one of the listings is bad, and anyone can edit it, anyone can fix it too. That's the philosophy of community documentation...
3) Put a note on the node/add form about that then please, below the field in question.
4) I'm not planning to add to the responsibilities of the community docs moderators or the future curated docs team that they be the only ones to update this section. I think it needs to be open to everyone and be part of the Community Documentation, rather than maintained by a small team (or worse yet, one person), or it won't ever get updated.
Comment #68Taxoman CreditAttribution: Taxoman commented
1) "Why wouldn't we want a major Drupal project contributor's (future, hypothetical) self-published-on-Amazon but excellent e-book on Drupal 8.x to be added to the list?"
Yes, why should we not want that? Do we need any kind of restrictions at all? And if there are any, they should be documented, kept open for debate, and easy to find (...). Would be nice with a link if there is an existing info page or discussion about this "somewhere". (I am sure it has been debated.)
How about simply "whenever a book gets good reviews from the community", then it can be listed? It is newsworth for the development of the community anyway.
(On the other hand, here is where we would benefit from having a decent voting and userpoints system in place. Then we could set some rules according to that to find out a combination of good reviews, number of votes and previous author points, for example. But that is for another debate.)
I'd say that any Drupal books should be listed, and then we should find a way to assign points/votes or some kind of rating to each, and to offer (re-)sorted listings and filters based on criterias such as year, category, votes/points, price, format (ebook/etc.).
Comment #70jhodgdon CreditAttribution: jhodgdon commented
People put spam on drupal.org/documentation all the time, and we have a "report to moderator" link so the community can request it be deleted. Let's just use the same system here. We'll have comments turned on too, right? So people would be able to comment on individual books. Crowd sourcing. :)
Points and voting are a separate issue, being discussed elsewhere for other purposes... not sure where though.
Comment #71tvn CreditAttribution: tvn commented
I took a look at the dev site and it looks great! We could tweak things like indented fields later with some theming.
One minor thing - would be good to add some "empty text' to the view for when nothing is found during filtering.
Sidebars on both listing page and individual nodes could use some blocks with useful links - like "Add a book", "Report to moderator", "All books" etc., could be done later also.
As we're adding new content type, we probably should open new issue and discuss content creation guidelines for books, and include there all requirements like permission to use the official book descriptions from publishers etc.
Right now we are also discussing such guidelines for case studies so later we could centralize guidelines for various content types here #1041394: Organize guidelines for content by type; move them to About drupal.org
Comment #72jhodgdon CreditAttribution: jhodgdon commented
Sidebars: Yes, I was thinking about that. The site needs to be set up how it will be eventually -- you might need to make the view be a Block rather than a Page, and embed it on a Book page (probably via a patch to the drupalorg_handbook module), in order to get it to appear in the proper place in the Documentation outline. Or if it is not supposed to be in the Documentation outline, we need a patch in the drupalorg_crossite module to put it in whatever place it should be. In either case, we would also need a patch in drupalorg_crossite to make individual Book pages appear in the right section of the site.
Guidelines: good idea.
Comment #73jhodgdon CreditAttribution: jhodgdon commented
LoMo: How are things going? Do you need any assistance to take this to completion?
Comment #74jcnventura CreditAttribution: jcnventura commented
Just a note on "the policy": It wasn't to exclude all author editions and/or ebooks.. It was just to level the playing field.
One thing that a book published by an editor has is an editor and/or a technical reviewer.. An author edition is usually only viewed by the book author (and maybe his mom) before being "released" out there.. Even Johan Falk's "Drupal 7 Essentials" suffered from this.. I spoke with him after I removed that book from the list asking for some kind of review process prior to publication, and his reply was "the swedish version was reviewed, but not the translation into English". Maybe we got lucky and his translation is spot on, but I have my concerns.. (see the original here: http://www.bokus.com/bok/9789144075440/drupal-7-borja-har/)
As to where "the policy" is stated: http://drupal.org/node/383388 (second paragraph). This page is linked from the "upcoming books" page.
There are some really bad books out there, and the best Occam's Razor was this policy.. The 2 books in the above page are pretty good IMHO, but I didn't want to play "god" when choosing books. I played an experiment (there's a thread in the Policies group in g.d.o where this is detailed), where an "Amazon SalesRank(tm)" was used to weight the books, but this also involved a robot fetching Amazon, and in the end it wasn't suitable for automation in d.o, and created too much of an overhead on the book list update process.
Comment #75jhodgdon CreditAttribution: jhodgdon commented
Great, thanks for the insight! I think we can probably keep that policy for the time being at least, and we'll formalize it with a short page in this section of the style/content guide:
Comment #76jcnventura CreditAttribution: jcnventura commented
Just for completeness: the previous discussion on g.d.o/Drupal.org policies: http://groups.drupal.org/node/174354
Comment #78jhodgdon CreditAttribution: jhodgdon commented
- I don't think we want to use Views for the individual page node display. Too complicated (comments, etc.). What is the problem you are trying to get around, specifically?
- Language field -- I think I would leave that off. Drupal.org documentation is currently English-only, and we leave documentation in other languages to the web sites maintained by those language communities. Let's also let them deal with making lists of books relevant to their language.
Comment #79jhodgdon CreditAttribution: jhodgdon commented
And LoMo: Do you want someone else to take this over and get it done, or are you still planning to finish it?
Comment #81jhodgdon CreditAttribution: jhodgdon commented
LoMo: What all needs to be done on this project?
Comment #84jhodgdon CreditAttribution: jhodgdon commented
One other ToDo item:
c) These pages are not getting any sidebars or navigation, so we would also need to figure out where they belong, and get the appropriate section navigation and sidebars. Any thoughts on that?
Regarding (b): I don't really think that is totally necessary.
Regarding (a): Like documentation-book nodes, we could probably put this status information on the right sidebar (and it would be consistent with those pages then).
Comment #87webchick CreditAttribution: webchick commented
Wait. I'm confused. Why do we need permission to copy/paste what is freely available online? Especially when the whole point is to get people to buy those books?
Comment #89tvn CreditAttribution: tvn commented
Great to see this is moving again.
We do not really need views for individual pages and agree with jhodgdon "b) Combine the publication fields into one line" is not really necessary.
As for the placement, they definitely should not be deep in the documentation. I do not think they belong to the main menu either. I think that we could put them into Marketplace (http://drupal.org/marketplace), adding "Books" to the subnav ("Services Hosting Training Books"). Potentially later we'll also add Jobs there.
Maybe we could also use top navigation from http://drupal.org/marketplace-preview for books listings.
All theme changes should go to Bluecheese, generally we try to re-use current theme classes etc. as much as possible.
I'll wait for you to finish current to-dos and then will take closer look on the dev site and help with some theming.
Comment #90jhodgdon CreditAttribution: jhodgdon commented
RE: Placement... I think if it's in Marketplace, people are not going to notice it. I personally never go to Marketplace, and I am not sure people who might buy books would go there?
I was actually thinking that when you go to http://drupal.org/documentation, that we could add it to that sub-navigation (where it currently says "Community documentation home", "Installation guide", etc.). Then we could add a link from Marketplace to that page too.
Or we could do it the other way around (make it a sub-nav of Marketplace and put a link on the Documentation landing page).
Any votes or other ideas?
Comment #91tvn CreditAttribution: tvn commented
All pages in the subnav "Community documentation home", "Installation guide" etc. have "Community documentation" as a page title which will look strange for books. Also "Documentation" implies that you can read it right there, whereas you can't actually read books there - you need to buy them first. And from this perspective Marketplace seems more fitting as it suggests you to buy something. So I think it is better to make it subnav of the Marketplace and link to it from various places in Documentation to make sure people notice it.
Comment #92jhodgdon CreditAttribution: jhodgdon commented
Comment #93silverwing CreditAttribution: silverwing commented
Being a part of Drupal services makes sense. (The top nav Marketplace title is "Buy Drupal Products and Services.")
However, we really need to turn http://drupal.org/drupal-services into a real landing page instead of having the list of companies there. But that's another issue :)
Comment #95silverwing CreditAttribution: silverwing commented
Found an old issue about placing advertisements on /books and I'm not sure how it would work now. So I thought it worth mentioning here.
#1154298: Create new ad placements on /books
Comment #96jhodgdon CreditAttribution: jhodgdon commented
I guess it's time to assign this to myself for final touches, and to get it done as soon as I can!
Comment #97jhodgdon CreditAttribution: jhodgdon commented
Here are some ***preliminary*** patches for Bluecheese [work by LoMo] and drupalorg_crosssite... not ready for testing yet...
Comment #98jhodgdon CreditAttribution: jhodgdon commented
One more preliminary patch (note: previous crosssite patch has a typo! don't use!).
Comment #99jhodgdon CreditAttribution: jhodgdon commented
New versions of patches... still testing...
Comment #100jhodgdon CreditAttribution: jhodgdon commented
One more try...
Comment #101jhodgdon CreditAttribution: jhodgdon commented
Sorry about all the traffic. If someone wants to tell me a better way to transfer patch files to the dev server so I can try applying them and testing them, please do (I find it much easier to develop and make patches on my own machine with git and not via ssh/bzr). My current method is: upload the patch here, and use wget on the command line on the dev server. Crude but effective...
Comment #102jhodgdon CreditAttribution: jhodgdon commented
|Needs work
|» Needs review
OK, I think I have a working set of patches now. I've added the Books pages to the Marketplace, and moved the taxonomies to the sidebar. You can check it out at:
and then click on individual book titles to get to the detail pages, such as:
I think it might be useful to test deployment on another dev site before going live on Drupal.org. The deployment will be a bit complicated:
1. Apply the attached patches to bluecheese (sorry, this is a bzr diff -- not sure how to do anything else for Bluecheese), drupalorg, and drupalorg_crosssite projects.
2. Add the Date module to drupal.org (http://drupal.org/project/date).
3. Do whatever is needed to enable the Feature that is in the drupalorg patch.
4. We know from experience on past Features that did content types that the Publishing Options (published, promote to front page, sticky) are not set by Features for content types. So after turning on the feature, someone will need to edit the new Book Listing content type:
- Turn off "promoted to front page"
- Turn off "sticky".
And on the Theme config:
- Turn off "display post information" for book listing nodes.
5. LoMo I think (??) has a way to generate the content for the existing book listing nodes once the content type is up there.
6. Add link to new Books page from Documentation landing page, and from
"Understanding Drupal" http://drupal.org/documentation/understand (where Books
used to be).
7. Redirect the previous node pages for the books listings to /books and delete them:
8. Decide on permissions -- who should be able to create/edit book listings? I'm inclined to say "everyone with a d.o account" at least for now. Give these permissions to the appropriate role(s).
9. Decide on guidelines for books. (E-books vs. paper books? established publishers vs. self-published, and how do we decide what constitutes which -- the lines are rather blurry these days? Etc.) The current policy for books is at the top of http://drupal.org/node/383388 (rather terse). Eventually, the policy should go as a sub-page to http://drupal.org/node/1588120 -- and as a note, it should include the list of publishers whose web sites it is OK to copy/paste book descriptions from (LoMo has been managing that).
Whew! Please take a look at the new layout and let me know if I did anything stupid. And please read the deployment instructions and let me know if I forgot anything (or if you have ideas about guidelines -- items 8/9).
Comment #103tvn CreditAttribution: tvn commented
Thanks for finishing this one jhodgdon. I'll do a proper review early next week.
Comment #104jhodgdon CreditAttribution: jhodgdon commented
Something to think about: What should go into the right sidebar on the Books landing page? Right now, nothing is in there at all (adding it to the Marketplace section didn't enable any sidebars).
Things we could put there:
- Copyright information (probably a good idea, although a lot of the info on the Books pages is not written by d.o authors -- it's book descriptions from the publishers).
- Link to add a new book listing.
- Link to the guidelines page (when we create one).
The individual book listing pages already have the book taxonomy on the right sidebar, but presumably any right sidebar block we make for the books section should also go on the individual book pages.
Comment #105tvn CreditAttribution: tvn commented
I looked around on the dev site today, some comments:
Revisions should be enabled for book_listing content type (I did enable them).
Individual pages looking good, only I think we should remove
"Edit this page
Report to moderator"
from the sidebar if possible. We don't need to encourage edits as much on this pages as on doc pages and issues about them should probably go to webmasters queue not docs. Also I don't really want this book pages to look absolutely like documentation book pages to make a bit less confusion.
Listing view:
- titles should be changed to h2, this will be in line with other listings such as marketplace, case studies
- view should use full pager
- view has some hard-coded styles for example on images
- the view should stretch on full grid-8 width
- i think view should be changed from HTML list to unformatted, it will be easier to fix previous item and generally clean up css a bit
jhodgdon, if it is ok - I can do these changes to the view and clean up the view and css.
Another issue is filtering on the top of the listing, I'd love to have standard filtering/navigation same on all pages in the marketplace: drupal services, books, trainings, potentially jobs later. Right now filtering on the top of marketplace-preview is a bunch of custom code which we won't copy for each section. I opened an issue here to think about making this navigation flexible and usable for every section of the Marketplace: #1671320: Re-write categories navigation on top of /marketplace-preview to be more generic
I think we could probably deploy this right now, with current filtering, just something to think about.
I think we should start from adding a block similar to the one on Marketplace preview and Case studies - with "Add a book" button and link to Books guidelines page. This block should not be shown on individual pages.
I'll open an issue for Books guidelines tomorrow.
Also I'd love to know more on
"5. LoMo I think (??) has a way to generate the content for the existing book listing nodes once the content type is up there." - is there a way to generate or we'll have to populate the listing manually?
Comment #105.0tvn CreditAttribution: tvn commented
Updated taxonomy descriptions and removed "Drupal version" as a field. It will be the existing Drupal Docs taxonomy.
Comment #106jhodgdon CreditAttribution: jhodgdon commented
Thanks for the review!
- I've just edited the issue summary. The Remaining Tasks section now contains the deployment instructions from #102, with the addition from #105 on turning on revisions.
- I emailed LoMo - he's on vacation this week, and plans to come back to this issue and explain his content importing (I think) and review the changes (definitely) next week.
- I opened an issue for discussing guidelines: #1681566: Decide on guidelines for new Book Listings content type
Regarding the other questions in #105, tvn and I are going to talk shortly in IRC and decide who should do what -- will report back.
Comment #106.0jhodgdon CreditAttribution: jhodgdon commented
Add standard issue summary with status
Comment #107jhodgdon CreditAttribution: jhodgdon commented
Plan agreed to (I think) by tvn, silverwing, and myself in IRC just now for the ideas in #105:
a) tvn will take care of updating the view/CSS as described in section "Listing view".
b) I will take care of the "edit this page" and "report to moderator" changes. We'll actually make "report to moderator" go to the Webmasters queue for all book pages too, since most of the issue reports have been spam issues anyway. And we won't have an "Edit this page" on the sidebar of book listings.
c) We will stick with using Views filtering for now.
d) I will add a block to the drupalorg_handbook module containing:
- for people with permission there is an 'add a new book' link.
- something about copyrights on the text (which is a bit complicated for these pages)
- link to the guidelines.
And We display this block on the individual book listing pages as well as the view page.
Comment #108tvn CreditAttribution: tvn commented
I've updated the view and cleaned css. Also moved the field "Availability" up so "more information" link would be last, I think this makes more sense. Attached is a patch for Bluecheese, apparently it also includes the patch for #1528530: Add CSS support to Bluecheese D7 for common HTML elements in content - should I remove it or let's deploy them together?
Comment #109jhodgdon CreditAttribution: jhodgdon commented
RE #108 - thanks! I don't see an attached patch... We should remove the part for #1528530: Add CSS support to Bluecheese D7 for common HTML elements in content and get that deployed separately. (I forgot to bring that other issue to office hours yesterday - can we get that on the agenda?)
Anyway, I'll take a look at what you did, make my changes, and roll new patches probably tomorrow.
Comment #110tvn CreditAttribution: tvn commented
Ehh, forgot an attachment indeed :) Removed superscripts part and attaching now. Neil is ready to review this issue and deploy this week. So we just need clarification on how we are going to populate new content type.
I forgot to bring that other issue to office hours yesterday - can we get that on the agenda?
Comment #110.0tvn CreditAttribution: tvn commented
update status on guidelines
Comment #111jhodgdon CreditAttribution: jhodgdon commented
Temporary interdiff patch, in testing, ignore...
Comment #111.0jhodgdon CreditAttribution: jhodgdon commented
update instructions slightly
Comment #112jhodgdon CreditAttribution: jhodgdon commented
OK, here are some new patches, based on the task list in #107. Some notes:
- Edit this page link - this will only appear for people who have permission to edit the page, so I didn't remove it after all.
- New patch for Bluecheese - I thought the Book Listings styles should be all in one section, and I added a newline to the end (as compared to the patch in #110).
- No change to the drupalorg_crosssite patch (re-uploaded so they are all together).
- Changes to the drupalorg patch [aside from the feature, the interdiff from the last version is in the previous comment]:
-- Moderator links - now going to Webmasters. The link does not seem to work on the dev site (I think the Webmasters project doesn't exist there), but you can copy the URL and substitute drupal.org and test that way.
-- Block added to sidebar - needs review. Note that the link to the guidelines page doesn't work on the dev site (I just added the page to the live d.o site and it does not exist on dev; again, substitute drupal.org to test the link).
-- Feature exported again (tvn made changes to the View).
Comment #113tvn CreditAttribution: tvn commented
I had one style at another section just to control space for all this sort of listings in one place, so when we decide to change it - it's same everywhere. If however you think it's better to move it, please change the value 2em to 2.077em.
As for the block - to make this look good I think we need 2 of them.
1st - contains:
- button-styled link "Add book listing" (class .action-button) same as we have on case studies, marketplace etc. (I can't see such button now so not sure if it's there or not)
- link to the guidelines, I think link's text should be just "Book listing guidelines" without "view", to be similar to what we have at other places
This block should have no gray background and should be visible only on listing pages.
2nd - contains the text about the copyright, has gray background and is visible on both listing pages and individual pages.
"Edit this page" and "Report to moderator" - I still think we should remove them because this content type is not something that should/will be edited a lot. And looking at the guidelines issues, seems that everyone will have permission to add/edit books and therefore will see this links.
Comment #114jhodgdon CreditAttribution: jhodgdon commented
Seriously, 2.077em? That seems ridiculous... but if you want that specifically, then let's go back to the patch you posted in #100, except it needs a newline at the end of the file.
I can make those changes to the blocks, but let's wait until we decide on the guidelines for sure, because right now I wouldn't say it's certain who is going to be able to edit the listings. #1681566: Decide on guidelines for new Book Listings content type
Comment #115jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Postponed
Actually, let's postpone this issue until the guidelines are decided upon (I don't want to make another patch here and then have to change it because the guidelines are changed).
Also, hopefully LoMo will let us know how to get the content transported to Drupal.org -- we don't really want to deploy this until we have a plan for that.
Comment #116jhodgdon CreditAttribution: jhodgdon commented
Anyone interested in the guidelines and workflow for getting new books listed should take a look at the proposal on http://drupal.org/node/1691562
If you have opinions, please post them on the guidelines issue:
#1681566: Decide on guidelines for new Book Listings content type
If we don't hear any dissenting opinions within a few days, we'll probably adopt these guidelines (at least for the initial release; can revisit if they become problematic).
I'll update the issue summary here too...
Comment #116.0jhodgdon CreditAttribution: jhodgdon commented
another deployment instruction
Comment #117jhodgdon CreditAttribution: jhodgdon commented
Changes that will need to be made to the existing patches from #112 if we adopt the proposed guidelines:
a) Add (and export) a new book format taxonomy (multi-valued -- not sure what the values should be? print, electronic ... should we be specific about electronic formats?).
b) Remove the edit this page and report to moderators links.
c) Change the sidebar blocks (see #113).
d) Possibly some CSS tweaks (see #113/#114).
And LoMo: Can you please comment here about how we can import the content for the new book listings when we deploy? We aren't going to deploy until we know how that will be done. Thanks!
Comment #118tvn CreditAttribution: tvn commented
re: a) - I don't think we should be specific about various formats. I suggest we use "Paperback" and "eBook" terms. And potentially someday "Audiobook"?
Comment #119Taxoman CreditAttribution: Taxoman commented
I'd say "Audiobook" is relevant already. Including that one too will help paving the way for further developments in that direction.
Comment #120webchick CreditAttribution: webchick commented
Dude. I'm totally going to lobby O'Reilly for Using Drupal, in the voice of Samuel L. Jackson. :D
Comment #120.0webchick CreditAttribution: webchick commented
status update
Comment #121tvn CreditAttribution: tvn commented
One more note: on the dev site sidebar block with the link to guidelines and copyright text is now being shown on every page including front page, /support, /forum etc.
Comment #123tvn CreditAttribution: tvn commented
Lomo, your Selenium system sounds good. (Make sure you don't add new books too fast to avoid troubles with the infra team :) )
Could you contact publishers for permissions so we have that settled before deployment?
We'll need to do some changes to patches etc., as well as work on D7 version of the listing so deployment will happen only after DrupalCon Munich, but would be good to have that one ready.
Comment #124jhodgdon CreditAttribution: jhodgdon commented
tvn: In an email thread, we actually decided *not* to contact publishers for permisssions for now, I think. Most of the books are available on Amazon and we can use those descriptions.
Comment #126jhodgdon CreditAttribution: jhodgdon commented
We should be discussing this (copyrights) on #1681566: Decide on guidelines for new Book Listings content type so moving there.
Comment #127jhodgdon CreditAttribution: jhodgdon commented
But... wait a minute. LoMo are you saying that the information you currently are putting in the book listings on the test page, we don't have permission to post because your Selenium script is grabbing it from Amazon? If so, we should get rid of that immediately.
Comment #129jhodgdon CreditAttribution: jhodgdon commented
So... are you saying that most of the information we have on the test site now is information we don't have permission to use? In which case, we need to remove it.
Comment #131jhodgdon CreditAttribution: jhodgdon commented
|» Needs work
Some thoughts from #1681566-30: Decide on guidelines for new Book Listings content type and the previous two comments from that issue:
a) We should turn on comments.
b) Add dummy links to purchase at other Amazon stores (Canada, UK, Germany, France) to see what this would look like, so we can ask the DA to create affiliate stores there, if they're willing to.
Other ToDos from above:
1. Add (and export) a new book format taxonomy: Print, Electronic, Audio
2. Remove the "edit this page" and "report to moderators" links (since we are pre-moderating)
3. Change the sidebar blocks (see #113), and make sure the guidelines block is only visible on the correct pages.
4. CSS tweaks (see #113/#114).
5. LoMo needs to tweak his Selenium import script to have the new book taxonomy, and to make sure not to include any copyrighted information we don't have permission to post.
I think the guidelines are sufficiently agreed to that it's time to get this rolling again...
Comment #136jhodgdon CreditAttribution: jhodgdon commented
RE #134 - discuss that on the Guidelines page.
RE #135 - yes we need to add that to the deployment checklist.
Comment #136.0jhodgdon CreditAttribution: jhodgdon commented
Comment #136.1tvn CreditAttribution: tvn commented
update, remove original post for easier reading
Comment #136.2tvn CreditAttribution: tvn commented
Comment #136.3tvn CreditAttribution: tvn commented
Comment #136.4tvn CreditAttribution: tvn commented
Comment #136.5tvn CreditAttribution: tvn commented
formats done
Comment #136.6tvn CreditAttribution: tvn commented
Comment #136.7tvn CreditAttribution: tvn commented
3 done
Comment #136.8tvn CreditAttribution: tvn commented
Comment #136.9tvn CreditAttribution: tvn commented
updating instructions
Comment #136.10tvn CreditAttribution: tvn commented
Comment #136.11tvn CreditAttribution: tvn commented
Comment #136.12tvn CreditAttribution: tvn commented
Comment #136.13tvn CreditAttribution: tvn commented
Comment #136.14tvn CreditAttribution: tvn commented
Comment #136.15tvn CreditAttribution: tvn commented
Comment #136.16tvn CreditAttribution: tvn commented
Comment #137tvn CreditAttribution: tvn commented
I finished to-dos:
- Added book format taxonomy
- Removed links from the sidebar
- Changed sidebar blocks. Left one in code and added 2nd with the button and guidelines link manually
- CSS tweaks
I went ahead and created Book availability and Book formats vocabularies on d.o, to have them ready before deployment.
Cleaned up patches, so they would apply to current d.o and deployed everything on:
Exported feature and patches attached.
Deployment instructions in the issue summary updated. If step 1 is just term edit via UI, I'd do it now, not waiting for deployment.
Please test and we can deploy this next week.
Please open new issues for any additional features suggestions, this issue is now only about testing current version and deployment.
Comment #138tvn CreditAttribution: tvn commented
|Needs work
|» Needs review
The only problem now is that taxonomy term "Available" has different id on live site and dev site. So we should either manually edit feature with correct id or update views after deployment as noted in deployment instructions.
Comment #140jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Needs work
Looks pretty good! A couple of things I noticed that I think still need to be fixed:
a) When I was on the marketplace dev site as an anonymous user, I had "log in to edit this page" links in the sidebar and footer. I think those should be removed (one of the changes tvn just did was to remove the "edit this page" links for logged-in users from those spots, so for consistently I think the "log in to edit" links should also be removed).
b) Logged in as myself, I don't see any links to create a new book. Isn't there supposed to be a block for that? I have permission for node/add/book-listing so I should be able to see that link?
c) When I'm on the node/add/book-listing page, I don't see a link to the guidelines. Isn't there supposed to be a link? Actually I think the guidelines block is supposed to be visible on every book page and the book listings page too, so it seems to be missing.
Comment #141tvn CreditAttribution: tvn commented
a) agree, "log in to edit this page" should be removed.
Bottom one though says "login or register to post comments" - I think we could keep this one?
b) There is a block on /books page. I logged in with bananas (which has no special permissions I think) and was able to see it. Can you check again please?
c) Good point, I added message on top of the form via content type's settings.
Comment #142tvn CreditAttribution: tvn commented
|Needs work
|» Needs review
Removed "log in to edit this page". Updated handbook patch attached.
Updated feature attached, I also manually edited feature per #138 so it has now correct id.
Other 2 patches without changes.
Comment #143jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Needs work
This is better, but there are still a couple of problems:
a) When I'm not logged in and I go to
- http://marketplace-drupal.redesign.devdrupal.org/books (listing page)
- http://marketplace-drupal.redesign.devdrupal.org/node/1791042 (individual book page)
I am still not seeing a link to the guidelines page. I think it is important for this to be visible to everyone, so they know why a particular book is or is not included in the listings.
Even when I'm logged in, I am not seeing a link to the guidelines on the individual book pages.
b) The crosssite patch has some extra whitespace in this line:
'training' => array('title' => t('Training'), 'href' => 'training', '#active' => drupalorg_crosssite_child_of('training')),
+ 'books' => array('title' => t('Books'), 'href' => 'books', '#active' => drupalorg_crosssite_child_of('books') || drupalorg_crosssite_is_type(array('book_listing')) || drupalorg_crosssite_child_of('node/add/book-listing')),
c) [done] I went ahead and edited the Audience taxonomy on drupal.org with the suggestions in #135 from LoMo.
d) The final patch that we deploy needs to not have the "Order from test" link that is currently on the Goats book on the test site.
e) It would be great if LoMo could test his Selenium script on the current test site so we can verify that it's all working correctly before we deploy to drupal.org.
f) This line in the handbook patch cannot be correct:
++ drupalorg_crosssite_child_of('node/add/book-listing')) {
It should not have two + signs on it.
Comment #144jhodgdon CreditAttribution: jhodgdon commented
tvn or LoMo - maybe you should assign this to yourself... I'm obviously not working on it very actively right now, just reviewing changes others do.
Comment #144.0jhodgdon CreditAttribution: jhodgdon commented
Comment #145tvn CreditAttribution: tvn commented
a) block with "Add your listing" button and guidelines link is shown only on the listing page /books and only for authenticated users. Let's deploy this basic version and improve later.
d) I removed "Order from [Publisher]" field from the view. Please tell me if there is anything else I need to remove. If nothing else - I'll recreate feature again.
I'll upload updated patches for b and f with the feature.
To clarify #137 by "cleaned up patches" I meant that I applied original patches to tvn- dev site, not all of them worked. I then manually edited module files to work how we want them, created bzr diff patches off that and applied this new set of patches to fresh dev site marketplace-. Apparently it applied with extra + :/, removed it now from handbook file on marketplace-.
Comment #146jhodgdon CreditAttribution: jhodgdon commented
I disagree with #145 (a). People (even unauthenticated users) need to see the guidelines. If we deploy it will never get fixed "later". Probably the block needs to be put in code so that it can display the guidelines on the right pages, and only display the "add" link on the correct pages for authorized users, as we do for other documentation-related blocks. Deploying things that need immediate fixes seems silly, and since I don't see LoMo chiming in to say he's ready to put the content in there, I don't see what the rush is?
Comment #148jhodgdon CreditAttribution: jhodgdon commented
LoMo: Thanks! Please edit the Guidelines page if you haven't already, to say that these publishers have granted us permission. And maybe forward the confirmations to someone at the DA so they can keep them on file... Or better yet attach them as text files to the Guidelines page itself? I think that might be useful so we don't lose them.
I guess we'd better get this thing finalized... I can probably work on it today.
Comment #149jhodgdon CreditAttribution: jhodgdon commented
OK, I'm going to take on the last bit of work here now. I'll be making updates to
and then I'll make some new patches to attach here.
Then I plan to do a test deploy on a newly created dev site, at which point hopefully LoMo can test his Selenium scripts on that site, and if we get this all done by Thursday morning, we should be able to deploy live this week and put this one to rest finally! :)
Comment #151jhodgdon CreditAttribution: jhodgdon commented
Thanks LoMo -- I will post back here when it's ready to test.
LoMo: Can you edit http://drupal.org/node/1691562 with the current information on which publishers we can use, and attach your confirmation letters as text files to that page? It currently just says we can use info from Packt. Thanks!
Comment #151.0jhodgdon CreditAttribution: jhodgdon commented
one item is done
Comment #151.1jhodgdon CreditAttribution: jhodgdon commented
Edit deployment instructions
Comment #152jhodgdon CreditAttribution: jhodgdon commented
OK, I've made a few tweaks to the site -- I moved the guidelines link and the "add new" button into the block that was already in code (removed the manually-added block), and fixed the typos in the earlier patches.
I also updated the deploy instructions in the issue summary, and I'm about to test them (will report back in a separate comment).
Attached are:
- zip file for the Feature (add to drupalorg project in directory features). [same as previous export]
- git diff patch for crosssite [slight change for whitespace and it's a git diff]
- git diff patch for drupalorg [combined blocks and it's a git diff]
- bzr diff patch for bluecheese [one style line removed since that block is eliminated]
Comment #152.0jhodgdon CreditAttribution: jhodgdon commented
update to deploy guidelines
Comment #152.1jhodgdon CreditAttribution: jhodgdon commented
update instructions
Comment #153jhodgdon CreditAttribution: jhodgdon commented
|» Unassigned
|Needs work
|» Needs review
Welll... there were a few deployment glitches, mostly due to the taxonomies having different IDs on drupal.org than they did on the test sites (and I just deployed it on a newly rebuilt test site).
So here is a new patch for drupalorg and a new export of the feature. The other two patches from #152 are still fine, but I've attached them again anyway.
I think this is now ready for LoMo to test his Selenium script on, and if that goes fine, we should be ready to deploy on drupal.org I think? LoMo: The site to use is http://docs-infra-drupal.redesign.devdrupal.org/books and I've made it so you can log in as yourself using password "tmppwd".
Comment #154jhodgdon CreditAttribution: jhodgdon commented
To Dos before we say this is ready to go:
- LoMo to run Selenium scripts on http://docs-infra-drupal.redesign.devdrupal.org/books
- tvn, jhodgdon, LoMo to look at http://docs-infra-drupal.redesign.devdrupal.org/books after scripts are done to see if the listings look OK.
- LoMo to edit http://drupal.org/node/1691562 (guidelines page) with list of publishers we have OK from, and attach the confirmation letters as text files to that page
Comment #157tvn CreditAttribution: tvn commented
LoMo, I just set your password to "lomo" on the docs-infra site and was able to login, please try. ping me on IRC if there is anything else you need help with.
Comment #158jhodgdon CreditAttribution: jhodgdon commented
RE #156 - Well, since this is a legal matter, maybe you could forward the email messages to someone who handles that kind of stuff in the DA? I just think they need to be on record somewhere besides in your email inbox. :) Thanks!
Comment #159jhodgdon CreditAttribution: jhodgdon commented
tvn pointed out in IRC that we need to have two separate blocks for the add link/guidelines vs. the copyright, for consistency with training and case studies sections.
So, here's a new patch (needs testing!) for drupalorg. The other patches from #153 still are valid. I will apply this patch and report back shortly.
Comment #159.0jhodgdon CreditAttribution: jhodgdon commented
update instructions again
Comment #160jhodgdon CreditAttribution: jhodgdon commented
There's a typo in that previous patch (block didn't appear). And an additional bluecheese CSS addition was needed. So here is a set of new patches. Disregard any previous ones. I also edited the deploy instructions to include the new block.
Both tvn and I think this is looking good now, so I guess it's ready to commit/deploy!
Comment #161jhodgdon CreditAttribution: jhodgdon commented
Since the deployment of this apparently needs to wait for a downtime (to install date module -- it alters the user table) and will therefore be delayed for a short time, we can do a couple of style tweaks suggested by LoMo:
a) Float the book images right on the node pages
b) Put the authors in-line with the Author label (have to see how this would do with the few books we have with a lot of authors).
We now have the books uploaded to the demo site (thanks Lomo!), so we should have plenty of data to test on.
LoMo also suggested a bit of formatting for the Views page:
c) "I was just thinking it might look nicer with tighter spacing between related lines (e.g. wrapped authors, etc) and a bit looser between the fields... more "type-set" with appropriate indents for wrapped groups."
As I am not a CSS wizard, I am hoping that someone else can do these tweaks... Otherwise if they don't get done before the deploy time, we can file a separate Bluecheese d7 issue and fix them later.
Comment #162drumm CreditAttribution: drumm commented
|Needs review
|» Needs work
I'd also like to see template_preprocess_content_field() moved into drupalorg module. We don't need it on other sites, and modules are the right place for PHP.
A 30 min downtime window will have to be scheduled with nnewton.
Comment #163jhodgdon CreditAttribution: jhodgdon commented
Doh! Sorry about that. I'm on the job...
Comment #164jhodgdon CreditAttribution: jhodgdon commented
OK, #162 and #161 are taken care of. You can see the new formatting on:
http://docs-infra-drupal.redesign.devdrupal.org/books [view]
http://docs-infra-drupal.redesign.devdrupal.org/node/1801786 [lots of authors]
http://docs-infra-drupal.redesign.devdrupal.org/node/1801774 [a few authors]
http://docs-infra-drupal.redesign.devdrupal.org/node/1801767 [one author]
Attached are new (and old) patches. Install instructions remain the same.
Comment #165jhodgdon CreditAttribution: jhodgdon commented
Hopefully tvn/LoMo can take a look at the site to check formatting etc., and drumm can review the patches. Thanks!
Comment #167tvn CreditAttribution: tvn commented
Looking good, thanks Jennifer.
Comment #168jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Reviewed & tested by the community
All right, pending @drumm's review of the patches, setting to RTBC again then.
Comment #email@example.com CreditAttribution: email@example.com commented
|Reviewed & tested by the community
|» Needs work
I am not happy to deploy date module just for a mini-feature such as a date of publication. We could use a textfield for this.
Date is a huge blob of code.
Comment #171jhodgdon CreditAttribution: jhodgdon commented
OK. I wish we had known that 130 comments and 6 months ago. On #27/#29 above we filed #1504778: Please add Date module to d.o. in March, where we were told that we could deploy Date if we had a reason for it (it was marked as a dup of this issue). Now we find out that we can't. Sigh. We should have gotten a firmer decision then I guess. Processes on d.o are eternally frustrating...
So, I think the best thing will be just to have the publication year and not the entire date, to avoid formatting issues and still allow us to do some filtering.
And I think we will need a new dev site where I can test deployment again, since I will need to create a new feature and probably some different code here and there.
LoMo: your scripts, sigh, will also need some tweaking.
Comment #173webchick CreditAttribution: webchick commented
Yes, please YYYY-MM. a) sortable, b) year isn't quite granular enough; a lot can happen in a year. :)
Comment #176jhodgdon CreditAttribution: jhodgdon commented
|Needs work
|» Needs review
Thanks for taking care of the content type and Views update, and updating your scripts, LoMo!
So it sounds like what we need to do is just export the feature again, have people take a final look at the dev site to make sure it looks OK, and update the deployment instructions... I took a look and I think it's fine. Here are some URLs again:
http://docs-infra-drupal.redesign.devdrupal.org/node/1801841 [one-author book]
http://docs-infra-drupal.redesign.devdrupal.org/node/1801856 [many-author book]
I am not all that inclined to do anything complicated with displaying the publication month/year -- I think everyone can figure out what it means as-is, and I just want to get this done. So, given that... the patches in #164 are still the ones we want to use, and here they are along with a new Features export tgz... and once again I think this is RTBC (pending drumm reviewing the patches and anyone else seeing any problems with how the pages look).
I will also go update the deployment instructions in the issue summary right after I save this. Since Date is now not involved, we shouldn't need to have a downtime in order to deploy this, right?
But... I do think it might be useful to test deployment on another site, since the feature is different, just to make sure... do we have one we can use for testing?
Comment #177jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Reviewed & tested by the community
Hm. Maybe this was enough of a test: I used Drush to disable the Date module and the book listings feature module, then I downloaded the new tgz attached above and unpacked it, then I used drush to enable the module. Everything seems to work fine, and the Features admin page on the dev site reports that the feature has not been overridden and is in its default state. So, I think we're probably OK without further testing.
That said, if drumm wants to see it tested again before final depoyment, and can point me to a dev site to use for deployment testing, I'd be happy to do that.
Comment #177.0jhodgdon CreditAttribution: jhodgdon commented
new block added to instructions
Comment #180jhodgdon CreditAttribution: jhodgdon commented
Hi LoMo! This is currently scheduled to get deployed to drupal.org this Thursday (oct 25). I just found this out yesterday and was going to update this issue but I forgot. Sorry!
Comment #181drumm CreditAttribution: drumm commented
All Drupal.org deployments are frozen for #1793968: Deploy Apache Solr Search Integration 6.x-3.x. That has been rescheduled for Saturday. If that goes well, then this can go Monday.
Comment #182jhodgdon CreditAttribution: jhodgdon commented
The deployment has been postponed (again). Current ETA is Sunday or Monday. It's waiting on Solr new version deployment, which continues to be problematic.
Comment #184Senpai CreditAttribution: Senpai commented
|Create new content type and Views for books.
|» Create new content type and Views for books
|Reviewed & tested by the community
|» Needs work
|Issue tags:
|+Drupal.org D7
The drupal.org push-to-prod schedule is every Thursday at 1:00pm PDT (see https://drupal.org/website-schedule), but I don't see a D7 branch of this feature anywhere, so I'm marking it as 'needs work'.
Comment #185jhodgdon CreditAttribution: jhodgdon commented
|Needs work
|» Reviewed & tested by the community
If we have to have a d7 port before deployment than this is never going to get deployed. I think that is an unacceptable criterion on an issue that was ready to deploy MONTHS ago and has been delayed through no fault of the people who worked on this.
Comment #186Senpai CreditAttribution: Senpai commented
@jhodgdon, it looks like you're the closest person to the details of this feature, so could you estimate how much time will it take to make a D7 version of this thing? One day? Two days?
Comment #187jhodgdon CreditAttribution: jhodgdon commented
|Needs review
|» Reviewed & tested by the community
This is mostly just a feature (a content type with a few text fields and an image field, plus a view). I don't think these take long to port, but I have no experience porting features to d7 so I cannot say for sure. I think all that has to be done is run the update (which ports the fields?) and then open and save the view like techgirlgeek was doing yesterday, and then export the feature again (10 minutes).
Then there are a few easily-ported lines in crossssssite (10 minutes), and probably an hour of work to port the drupalorg module lines. And a few CSS additions to be added to Bluecheese (10 minutes).
So, is that 2 hours or so total? Anyway the port should really be a separate issue please. We already have way too many comments on this issue for anyone to grok.
Comment #188Senpai CreditAttribution: Senpai commented
Assigning to @sdboyer for a review of this code in light of the automated D7 build process. Sam, if nothing looks like it will break our nightlies, please give a green light on this deployment before 1pm today.
Comment #189sdboyer CreditAttribution: sdboyer commented
|Needs review
|» Reviewed & tested by the community
sorry i didn't make it by the deadline.
i don't THINK anything should break our build process here, but it's honestly hard to say without letting it run at least once. the best course of action here is really just to assume it will break, run the upgrade off the reduced snapshot so we get data, and go from there.
Comment #190drumm CreditAttribution: drumm commented
Comment #191drumm CreditAttribution: drumm commented
Comment #192jhodgdon CreditAttribution: jhodgdon commented
Should we file a separate issue for the d7 port, or has that been done?
Comment #193drumm CreditAttribution: drumm commented
Committed basic merges to drupalorg and crosssite 7.x. They will still need attention, at least in QA. This does not include the feature code, since it will have to be recreated anyway. And does not include theme changes, because our CSS is now SASS.
Leaving open to make sure we have our D7 issues open and content migration done.
Comment #194drumm CreditAttribution: drumm commented
The D7 issue should be separate from this one. I'm not aware of one filed already.
An issue in http://drupal.org/project/doobie to make automated tests for the functionality is good too. They need to know what behavior to test for. Behat does either simulate a browser or drive Selenium.
Comment #195tvn CreditAttribution: tvn commented
|Reviewed & tested by the community
|» Fixed
Opened separate issue for content migration with all after-deployment to-dos: #1836258: Migrate Drupal books from book pages to new book-listing content type. LoMo please use that issue for further work with your script.
Upgrade issue: #1836252: Upgrade Book listings feature to D7
Theming issue: #1836254: Theme Book listing pages and view
I'll take care of BDD tests as well.
Closing this issue before we hit 200 comments.
Comment #196Tor Arne Thune CreditAttribution: Tor Arne Thune commented
Removed comment, as I suppose no books are migrated yet.
Comment #197jhodgdon CreditAttribution: jhodgdon commented
Thanks for making those issues tvn! yes re #196, getting the content in there is #1836258: Migrate Drupal books from book pages to new book-listing content type and I already emailed LoMo to request that he run his script.
Comment #199Tor Arne Thune CreditAttribution: Tor Arne Thune commented
Gotta love scripts :) Great work, all. The new view looks very clean and helpful.
Comment #203greggles CreditAttribution: greggles commented
Fixed #202 - node deleted.
Comment #205tvn CreditAttribution: tvn commented
Thanks for creating book listings LoMo! We now have a separate issue for everything related to books migration, please use that one for further comments: #1836258: Migrate Drupal books from book pages to new book-listing content type.
Comment #206tvn CreditAttribution: tvn commented
Quick note for those who were active in this issue. The books view/content type is now live, issue queue and guidelines are in place. We need someone to take over moderation of book listing requests. If you'd like to do it, please comment in this issue: #1794810: Documenting team leaders for webmasters issue queue components.
The queue is located here: http://drupal.org/project/issues/content?status=Open&component=Books+lis...
Guidelines for book listings: http://drupal.org/node/1691562
Guidelines for reviewers (in progress): http://drupal.org/node/1860526
Comment #206.0tvn CreditAttribution: tvn commented
update instructions - not using date module


text:
Words formed when one letter is changed in grades
Letter 1 (G) changed: 2 words found:
Letter 2 (R) changed: 1 word found:
Letter 3 (A) changed: 1 word found:
Letter 4 (D) changed: 5 words found:
Letter 5 (E) changed: 1 word found:
Letter 6 (S) changed: 2 words found:
A total of 12 words can be formed from grades by changing one letter.
Some random words: roach gip eicosanoid wikiup rhyme oka ileum
This is not a dictionary, it's a word game wordfinder.
- Help and FAQ - Examples - Home
Privacy and Cookies Policy - Share - © Copyright 2004-2017 Morewords.com - 65.475mS

subset: commoncrawl


text:
Amanda Setton was born December 16th 1985 (age 27) she grew up in Great Neck, New York and went to school there. She graduated from Ithaca College in her Junior Year.
Amanda has had a recurring role in Gossip Girl as Penelope Shafai, she has also played Kimberly Andrews in the ABC daytime soap One Life to Live where she worked opposite Florencia Lozano, Tika Sumpter and Bree Williamson.
She has reportedly quit One Life to Live and is moving to Los Angeles to search for new roles.


text:
Printer-friendly format
Email this thread to a friend
Bookmark this thread
|Home » Discuss » DU Groups » Reading & Writing » True Crime Group
|RamboLiberal (1000+ posts) Send PM | Profile | Ignore
|Thu Mar-03-11 06:59 PM
Original message
|Family's capture of serial killer Adam Leroy Lane chronicled in book
|Refresh | 0 Recommendations
|Printer Friendly | Permalink | Reply | Top
|raccoon (1000+ posts) Send PM | Profile | Ignore
|Fri Mar-04-11 09:45 AM
Response to Original message
|1. Thanks for the head up. I didn't know it was a book but will get it. nt
|Printer Friendly | Permalink | Reply | Top
|DU AdBot (1000+ posts)
|Sun Aug 20th 2017, 08:11 PM
Response to Original message
|Advertisements [?]
|Home » Discuss » DU Groups » Reading & Writing » True Crime Group
Powered by DCForum+ Version 1.1 Copyright 1997-2002 DCScripts.com
Software has been extensively modified by the DU administrators
Important Notices: By participating on this discussion board, visitors agree to abide by the rules outlined on our Rules page. Messages posted on the Democratic Underground Discussion Forums are the opinions of the individuals who post them, and do not necessarily represent the opinions of Democratic Underground, LLC.
Home | Discussion Forums | Journals | Store | Donate
About DU | Contact Us | Privacy Policy
Got a message for Democratic Underground? Click here to send us a message.
© 2001 - 2011 Democratic Underground, LLC


text:
|From: David Richards (vottamusic at verizon.net)
Date: Thu Jun 22 18:40:45 EDT 2006
On Jun 19, 2006, at 11:47 PM, Jepri wrote: > Matthias Felleisen wrote: > >> This sounds indeed like an appalling response time and it makes me >> wonder why some 10,000 people are using DrScheme on Windows. Now I am >> using DrScheme on Windows XP only via Virtual PC on a Mac OS X laptop >> and it runs very nicely there. On my Mac, I am running "large" >> programs (up to 5,000 lines, threaded) in DrScheme, leave the >> environment open for days and weeks at a time, and haver very few >> problems of this kind. > > Users will often silently tolerate some suprisingly bad program > behaviour if they like the program enough. When asked why they didn't > report the problem they just shrug. That's been my experience. I've waited several minutes to get a Help Desk page to display. Very often I restart DrScheme, to try to ease the pain. I've been reluctant to mention on the list because I didn't want to seem like I'm whining. DrScheme is perhaps the single most important application I have - at least it often seems that way. I'm incredibly thankful each time I launch it, and I worry about the dark day that for some reason the project goes defunct. That being said, I did not find the present sluggish response and poor GUI performance in earlier versions of DrScheme. I guess I've been thinking that it was painfully obvious and irritating to everyone, that the forces of light were working on the problem, and that it would magically vanish never to return again in a not-too-future update. >> >> But before we bash Microsoft one more time on this list, let's >> investigate your report in some detail. We don't want to blame them >> for nothing, right? >> >> 1. What kind of machine do you own? CPU speed and memory are two >> things we'd really like to know. A Mac Mini. I forget now how fast it is. 1.42 GHz maybe. Should be 'fast enough'. I think I've got 1 GB of RAM. >> >> 2. Which PLT Scheme implementation are you running? 350? 103p1? >> Anything in between? Welcome to DrScheme, version 350. >> 2a. Have you modified your PLT Scheme installation in any form or >> manner? Not consciously or intentionally. >> 3. What kind of programs do you run? Are they text-book exercises? >> Dynamic flow equations? Very simple ones. Lot's of Help Desk use. >> Once we have that information we will figure out how to get you to >> use this thing in an acceptable manner. >> >> Thanks for the report -- Matthias - David
|Posted on the users mailing list.


text:
Manu bennett
Prozkoumejte související témata
Manu Bennett - wonderful shoot.
Manu Bennett..Crixus Miss the Spartacus series, but at least I can see him on Arrow!
Manu Bennett love him as crixus in Spartacus and on arrow
Actor Manu Bennett [Arrow | The Hobbit | Spartacus] Photographed by Dennys Ilic Image may not be published or reproduced without the express permission of the photographer — with Manu Bennett, Manu Bennett and Dennys Ilic at Downtown Los Angeles, Los Angeles, California.
Manu Bennett
Manu Bennett is not only the Champion of Capua, but he's also a rugby player, dancer, and pianist. Call me?!?!
Manu Bennet. Love his voice almost as much as I do his acting.
Manu Bennett & Jason. wow, wish that I could have been there to see this. ;(penny)
Manu Bennett as new regular and shirtless Slade Wilson.
You can never be as badass as Manu Bennett naked on a horse. yup Azog had to make money for Bolg to go through orc college somehow


text:
NEW YORK (May. 11)
A declaration demanding the establishment of Palestine as a Jewish Commonwealth and free Jewish immigration into the country under the sole control of the Jewish Agency was adopted here today at the closing session of the three-day Extraordinary Zionist Conference which was held in the Biltmore Hotel here in lieu of the World Zionist Congress. Dr Stephen S. Wise and Dr. Chaim Weizmann delivered the closing addresses.
Pointing out that a post-war democratic world order cannot be established on foundations of peace, justice and equality unless the problem of Jewish homelessness is solved, the declaration calls for the "fulfillment of the original purposes of the Balfour Declaration and the Palestine Mandate which, recognizing the connection of the Jewish people with Palestine, was to afford them the opportunity as stated by President Wilson to found there a Jewish Commonwealth."
The declaration expresses the desire of the Jewish people to work in full cooperation with their Arab neighbors. It reaffirms the Jewish rejection of the White Paper issued by the British Government in May 1939 "which seeks to limit and in fact nullifies Jewish rights to immigration and settlement in Palestine and, as stated by Mr. Winston Churchill in the House of Commons in 1939, constitutes a breach and a repudiation of the Balfour Declaration."
"This Conference," the declaration reads, "urges that the gates of Palestine be opened, that the Jewish Agency be vested with control of immigration into Palestine and with the necessary authority for upbuilding the country, including the development of its unoccupied lands, that Palestine be established as a Jewish Commonwealth integrated in the structure of the new democratic world."
The Declaration conveyed the greetings of the Conference to the Jews of Palestine and expressed admiration for the steadfastness of the Yishuv in the face of its peril and great difficulties. "The Jewish men and woman in field and factory and the thousands of Jewish soldiers of Palestine in the Near East have acquitted themselves with honor and distinction in Greece, Ethiopia, Syria, Libya and other battlefields."
The need of educating the American public regarding Palestine and the Jewish problem was emphasized by Dr. Abba Hillel Silver in a speech at the concluding session of the Conference. "It is of utmost importance," said Dr Silver, "to intensify the education of American Jews as well as our non-Jewish friends, if we are to avert a colossal Jewish tragedy after an Allied victory." Pointing out that "Jews today are fighting on every front of the United Nations," Dr. Silver stated. "Our casualties have mounted in the millions. An Allied victory promises all nations freedom and restitution. The Jewish people alone is in danger of coming out of this
The need for a campaign of education for all America on the Jewish question and Palestine was also the major theme of the address of Emanuel Neumann, Executive Director of the American Emergency Committee for Zionist Affairs. Mr. Neumann expressed the view that "Christian America is instinctively pro-Zionist" but requires education. He predicted that it was not unlikely that there would be a Gallup poll of the American public on the question of the Jews and Palestine and the education of the public was therefore of paramount importance.
A lively discussion was precipitated on the proposal by the Zionist laborite representation that an overall Zionist federation be formed in America, including all the various Zionist groups. Prof. Hayim Fineman and Isaac Hamlin were chief spokesmen for the proposal. Gedalyah Bublick representing the orthodox Mizrachi wing, spoke in opposition, declaring that while it was possible to work together in such matters as the collection of Zionist funds, the different parties had diverse ideologies which could not be united in this country. Mrs. David de Sola Pool, speaking for Hadassah, declared that her organization had not fully gone into the matter as yet, but one objection to such a union was the danger that in such a Federation, the Hadassah wing, by the larger number of its shekel paying members, would reduce the men's Zionist organization to a comparatively inferior position.
Judge Levinthal, President of the Zionist Organization of America, stated he was in favor of the plan. The Conference decided to refer the question to the American Emergency Committee for Zionist Affairs in which all Zionist groups are represented.


text:
Investment Highlights
+ Highly accessible & thriving regional city (4.2% unemployment rate*) with direct flights to Sydney, Melbourne & Brisbane
+ Sub-regional centre: Target, Ritchies Supa IGA (Metcash)+ 52 shops and 5 kiosks over 15,330sqm*
+ 97%* leased to longstanding national/chain tenants. Average tenure of 19.2 years (by area)*
+ Fully leased net operating income of $7,155,465 p.a.*
+ 1.7 Ha* City centre site + expansion land under option
+ Major retail & mixed-use development plans prepared (STCA). Advanced interest from supermarkets and international fashion retailers.


text:
Poor Man's Souffle
Be the first to review
READY IN: 55mins
2Kansas A
Recipe by Kansas A
An old family favourite, I remember eating this when I was a kid! Velveeta cheese was cheap way back when, but not anymore...so I use cheese slices, grated cheddar, or even Cheez Whiz. Eggs, crackers, and milk are the rest of the ingredients. Prep time does not include 1/2 hour soaking.
See Discussion:
Ingredients Nutrition
Directions See How It's Made
- Spray Pam into a 9x13 dish.
- Line with crackers.
- *Put grated cheese, cheese slices, or Cheez Whiz, or a combination of all three if you're short with one or another. (I don't think Cheez Whiz by itself would be good so mix and match with that).
- Continue layering cheese and crackers ending with cheese.
- Crack 4-5 eggs into a four cup measuring cup. Beat eggs.
- Fill measuring cup with milk (I use skim but any milk will do) to the four cup mark.
- Carefully pour over cheese and crackers.
- Let sit for at least a 1/2 hour.
- Put into a 350 degrees F oven for about 40 minutes.
- Serve with salad.


text:
Honora Cultured Pearl 9.0mm X Design Bronze Ring
In Stock
Sold Out
We're sorry. This item is not available at this time.
Pre Order Possible .
Low Stock
- Colored bronze
- Cultured freshwater pearl measures approximately 9.0mm
- White cultured freshwater pearl set in center of polished X design
- Sizes 5, 6, 7, 8, 9, 10
- Measures approximately 3/4"L x 3/4"W
- Honora box, floral pouch
- Imported
The GIA (Gemological Institute of America) is widely recognized as the world's foremost authority in gemology, including diamonds, colored stones, and pearls. Through research, education, and laboratory services, the GIA serves the public interest through objective gemstone evaluation, including identification.
You can purchase our gemstone jewelry with added confidence knowing that QVC incorporates the GIA's expertise into the QVC gemstone identification quality assurance process.
For more information on the GIA, visit www.GIA.edu.
For more information on the gemstones found at QVC, check out our gemstone glossary.


text:
Civil contracting and mining services company
NRW's JV partners are Laing O'Rourke and John Holland, and the variation is worth about $145 million. NRW's additional component is worth about $105 million.
Both UBS and Royal Bank of Scotland have increased their financial year 2011 forecasts. UBS raised its FY11 forecast for reported net profit by 3.4 per cent to $53.7 million (forecast $44.9 million in FY10), while RBS upped its reported net profit in FY11 by 9 per cent to $44.9 million (forecast $38.6 million in FY10).
Moreover, RBS downgraded its recommendation on NRW to "hold" from "buy" because of the stock's recent strong price performance.
RBS notes that some $380 million of new contract wins in the past six months has boosted earnings visibility and shows the company is making headway in the larger-scale construction and mining contract markets.
The company will achieve its 20 per cent revenue growth target for FY10, RBS thinks. Earnings visibility 12 to 18 months out is less clear, but because the outlook for mining and construction is improving, RBS has set a price earnings ratio of 12 times FY11 forecast earnings and a target price of $2.15.
On Monday, the shares closed down 9¢ at $1.95.
The Australian Financial Review


text:
There is an exquisite video collection on the NY TImes called 'Fourteen Actors Acting' – brief black and white snippets of famous faces playing different minute roles with a classy string soundtrack.
Is it just me, or could you just watch these over and over all day? Hands down favorites – James Franco chatting himself up the mirror and an exhausted be-wigged vampy Natalie Portman removing her movie star 'skin'.
Having just watched The Girl With the Dragon Tattoo last weekend (ooooh boy, that was something) Noomi Rapace's steamy songstress is quite nice too.


text:
|Fix You
|Sung by
|Charlie Lubeck
|Called Back
Fix You was a last chance performance sung by Charlie in the third episode of the second season of The Glee Project, Vulnerability. It was originally sung by Coldplay. Unusually, Charlie chose to stray from the original melody. This performance secured Charlie a place in the next week's episode.
When you try your best, but you don't succeed
When you get what you want, but not what you need
And the tears come streaming down your face
I will try to fix you.
When the tears stream down on your face
I promise, I will learn from my mistakes
Tears stream down, down your face
And I...
And I will try to fix you.
- This is one of Ryan Murphy's favorite last chance performances.
- That song is sung by Will on Glee's episode "Asian F" .


text:
Shedding light on 'Shadow IT'
BYOD, BYOA, BYOx. The IT industry is full of acronyms depicting its constant evolution and relationship with the professional world. First came the devices; employees saw the power of personal devices and insisted on using them in the workplace. And so the consumerisation of IT was born.
After the devices came the apps. Companies reported greater productivity and higher employee satisfaction at enabling Bring-Your-Own-Device policies, but attention then turned to the applications being used. And IT executives were left wondering whether they would face a similar 'revolution' to the one that followed BYOD – the 'Bring-Your-Own-Apps' trend where employees choose the virtual tools needed to empower their devices and facilitate jobs. Recent research we conducted alongside Frost & Sullivan's Stratecast proves that the app revolution is already here, but with some slightly insidious repercussions – 'Shadow IT.'
Our global study, which questioned IT and enterprise decision-makers, aimed to uncover the extent and risks of unauthorised Software-as-a-Service (SaaS) applications. It found that more than 80 per cent of employees use non-approved SaaS applications in their jobs, with IT employees actually using a higher number than other company employees.
These SaaS applications are also referred to as 'Shadow IT', a term which broadly describes the use of technology solutions within an enterprise that have not been approved by the IT department or adhere to policies. Why is this happening? Low-cost, ease of access and ease of maintenance are factors, as is the cloud, which acts as a vehicle for employees to acquire and deploy these applications without involving anyone else. This 'self-serve' behaviour puts business at risk; in most cases, IT departments and security professionals are unaware of the extent of 'Shadow IT' and consequently are underprepared.
The current state and prevalence of 'Shadow IT' presents a great opportunity for resellers looking to engage with the many businesses struggling to understand their sprawling software use and the security implications of this. Deploying SaaS apps without the appropriate technical knowledge means corporate standards for data protection and encryption may be unknowingly neglected. This is particularly important for businesses managing sensitive customer or third-party data. Resellers should recognise the much needed help and guidance businesses need to ensure systems are in place to mitigate against the associated risks that deploying non-approved applications have within business. Although employees' intentions aren't malicious and are indicative of a workforce trying to be productive in a hyper-competitive market, the use of 'Shadow IT' within business can have severe repercussions on security and compliance.
The study highlighted a lack of understanding on the part of the employee, and lack of awareness and readiness on the part of the businesses that pressingly need to be addressed. Similarly with BYOD, the answer is not preventing employees from using these apps — it's about striking the right balance between flexibility and control.
The channel can and should work with IT and business leaders to create and support policies that enable employees to use the apps they need while still minimising corporate risk. These policies should be built around security solutions that provide employees with secure access to a broad range of recognised SaaS options. The ability to control app usage – for example allowing users to access Facebook but restricting the 'chat' function or automatically encrypting files before they are uploaded to a file-sharing site – is also key. Tools like McAfee Web Gateway can track web traffic and automatically provide proactive protection against malware, as well as block undesirable URLs, prevent outbound data loss and enforce acceptable usage policies.
The right security solution, together with education, policy control and consistent communication with employees can make the difference between a business that is agile, innovative and competitive or closed and removed from the opportunities around them. The channel has a crucial role in helping enterprises to shine a light on this new behaviour and ensure that when it comes to the competition, they aren't left behind.