SEO Expert Blog

Drupal associaiton Fund raiser & community service manager Employment type:  Part time Telecommute:  Allowed The Drupal association is a non-profit organization which provides support for the Drupal, web content management, open source project. The Drupal association is an all volunteer organization with thirty permanent members, and a support base of over 1000 financial contributors. We will provide event sponsorship packages for the fund raising activity. You will also receive access to the Drupal association CRM, CiviCRM 2.1. As a fund raiser you will receive direct requests through the event website and be required to follow up via email and over the phone. This is a contract position. The association is looking for an experienced fund raiser to work part time. * Experience with creating fund raising plans and delivering regular reports on progress of those fund raising plans. * Excellent written and verbal communication skills * Experience with fund raising campaigns and selling sponsorship programs is preferred * Experience with CRMs, and newsletter mailings * Must have a mail client that can send emails with an alias, such as fundraising@drupcalcon.org. e.g. Gmail. * Ability to work remotely, this is a telecommute position. You must have your own computer, internet connection, and phone system (e.g. Skype) for making long distance and International calls. Expenses will be re-imbursed. * Experience working with sponsors to deliver sponsors assets into marketing and advertising products. e.g. incorporating logos to banners * Experience with web based advertising delivery software. e.g. Google Ad manager * Knowledge of Drupal and open source communities is a significant asset * Written/Verbal knowledge of French or German is bonus Hours are flexible. Start date would be immediate. Initial contract length would be 6 weeks, and renewable going forward. Pay:$20-30/hour to begin, 20 hours a week. DrupalCon Paris 2009

---

I would like to see a hiearchical view of modules, that require dependencies, both in images of the actual module on its page, and also in the URI/URL. It cements the idea I have of it, if you know what I mean. A lot of modules are listed as living in ether, and are middleware for views or another module. At the moment the projects section is quite difficult to traverse. Could it be possible to maintain it with either just a block that lists its dependancies, and which modules require it? This would organise it so that in order to create an installation or a profile, that does one thing, a person/programmer could grab at one tree of modules, and not waste time looking at the whole kaboodle, going wow it does this or that.. and instead go okay, today I am creating with that 'treemodule'. This also gives an impression of finding what possibilities there are from the start, with this CMF thing. I didn't realise there was any genealogy stuff here, but I would have known sooner if there were fewer base modules to glean functionality from. Helper functions can be listed as CRUD base modules, for instance, unless you want to rename that as HUDBF, i.e. Helper (User) Drupal Base Functions, or even something that rolls off the tongue better. Essentially, this create a few extra fields for each modules submission, dependancy (1,2,3,..), required by (1,2,3,..). The moduletree module would compile all it sees, when people click on projects, and it would display, in context, the module, and its close ties. Okay, so it might run into problems when 200 modules require this one, but it would in this circumstance show what is popular, and most used/required. The stats from something like this would be rather interesting. When there are more than one galleries, it may cause problems, but then, I guess this would invlove putting a horizontal view together with the vertical view. It might be interesting to see a link to another page of this picture/view, or even a small banner above the content, or even a tab with these details. It would also be nice to see examples, for instacne to show organc groups as being simialr to alt.newsgroup design/structure. So another block/tab would have similarites. In some pages there are usages and features, but that is only down to the module author to instance these, whereas if authors had to populate these fields, they might put something other in than n/a, which of course would not show, it being part of an if statement, i.e. if n/a then dont show endif. I did not associate organic groups with newsgroup functionality, and was quite confused about whether I needed it until that is I delved deeper. It took me too long to find out what it was, and I really did waste a lot of time. Drupal has many many modules, and I really dont need to waste months going through modules until I find the right ones to build a site. Its just not feasible, and from a design pov it does not make drupal accessible. I understand that it would be very dificult to start redesigning the whole site, telling authors they need to populate these fields, so you could instead just introduce it as a part of D7, when its roled out for this site g.d.o and/or d.o. In a way this is partially represented in the Beyond The Basics block, for instance the Videos and Slides menu item has child item Modules, which iself has children. This, for me, is a bit confusing, seeing as there are a few items with video in the title, which could all be children of media instead of Videos and slides. Although with the beyond the basics module, it would be nice to find things which are specific to my version of drupal, i.e. D6, and not have to wade through them all, or if it is for D5, which automatically makes it for D6 then it should say that, as modules are not crossversionable, so why should howto's. It seems a bit jumbled all together for me, but then maybe I am a special needs case, or maybe I am an average user. I'm certainly no programmer, although I know my php's from my asp's. Enough of me. What does everyone else think? Does this rattle a few bones, produce a few hums, or maybe just brings out a few blank stares? Thank you in advance. Building Site Traffic

---

As you may know, I spent a few months this year working with Mark Boulton and the Drupal community to try to make Drupal 7 (their upcoming release) a Great User Experience. I’ve spent the past weeks reflecting on that experience and trying to understand what we learned from that project and with any luck [...]

---

Drupal/Economist Project – Sprint 2 Demo from Leisa on Vimeo. Today is Demo Day at The Economist, where all the various SCRUM teams will show and tell what they’ve achieved in their latest iteration. I thought I might see if I can get into the habit of pre-recording my demo so I can share it with [...]

---

I’m in the midst of our first sprint on the ‘publishing tools’ project at the Economist, wherein we’re defining interface designs for the ongoing migration of economist.com over to Drupal 6. hurrah! There is no sprint zero in this project and no time to consider the overall environment design, we’re going to be approaching this incrementally [...]

---

Economist/Drupal – Intro to the Publishing Tools Project from Leisa on Vimeo. Some of you may know that The Economist is in the process of moving their web content management over to Drupal and I am really excited to be joining the team working on the implementation of these publishing tools over the coming months – [...]

---

Infrastructure: Development/testing instances (Discussion in Infrastructure Requirements) We are still hamstrung by the lack of dev/testing instances. What we need from dev/testing instances A test instance that the public can view and click around on. This will help us build interest and momentum. Several dev instances (at least 5) split between developers and themers. Nice to have: Script to roll out new instances on the fly Sanitized DB for remote and local dev instances. Should be easily downloadable for those who want to set up local dev instances. User 1's username and password should be pre-reset. Nice to have: Script to clone a canonical, sanitized DB into remote dev instances as needed. Apache Solr needs to be set up. Next steps Contact Damien to see if he can help plan and delegate infrastructure tasks. Find additional infrastructure team members to help set up dev/testing instances. Talk to David Strauss about Capistrano to manage scripts that automate various tasks (like dev instance rollouts and DB cloning). Settle on a file-storing service for theme assets and move assets out of SVN. We are currently leaning towards Wuala. Create a guide to getting started We need a comprehensive guide to getting started. There are a number of posts in this group that contain elements of this guide; we need to compile and expand on them. What a "getting started" guide needs How to work with a dev instance (both local and remote) Using SVN How to set up a local dev instance Using MAMP or other local dev environments Checking out the drupal.org redesign branch locally Setting up clean install Importing d.o database where to download database importing database How to keep up with the project: notifications, RSS, issue queue, etc Asset management How to find things to do prototype Communication with volunteers Send a link to the "getting started" guide. Explain the situation with the dev/testing instances. Emphasize that work can still be completed without a remote dev instance. Enumerate what our plans will be once this is completed. Communication with volunteers who already have SVN access Set up times for local dev "installfests." Find Linux and Mac experts willing to troubleshoot. Use Doodle to arrange convenient times. Gauge interest in creating and distributing Linux virtual machines. Communication with designers Send a designer-only email that omits all the technical details. This email should contain only information on MB's prototypes, remaining design tasks, and links to the assets file-storing service. Other remaining tasks Kathleen is working on digesting all literature and issues related to the redesign. She will then conduct a site audit to determine what remains to be done. Ensure new drupal.org functionality has been ported to the drupal.org redesign branch. Establish a procedure for porting changes between branches. Drupal.org redesign implementers

---

Drupal.org Drupal Re-design infrastructure manager [Manager] Employment type:  Part time Telecommute:  Allowed The Drupal redesign needs several infrastructure managers to help manage testing sites for redesign themers and redesign developers. A Virtual Machine will be provided to the infrastructure managers. You will be given access to recent copies of scrubbed database copies of Drupal.org. Duties will include: 1) Approving SVN Accounts for themers and developers to the private theme and drupal.org code repositories. 2) Creating new drupal.org instances for themers to work on. 3) Pushing theme and code changes from SVN To learn more, see: http://groups.drupal.org/node/23645 Drupal.org redesign implementers

---

We need to discuss how we want the d.o redesign project to move forward. One- to 5-day sprints every few months is not a sustainable solution. Maintaining momentum and continuity is nearly impossible. Initial thoughts: Take a cue from the Aegir project and introduce a proper schedule Require weekly time commitments and weekly meetings Initial thoughts: 4 hours per week for at least three out of every four weeks (meaning you can skip one week from every four to catch up on client work) Find a proper Project Manager -- not a designer/themer/developer willing to take the role of PM May require hiring a part-time PM We need a dedicated and managed development environment. Having to download, pass around, and import DB dumps can easily eat up half a day or more, and we need a place where people can publicly view or test our work. Drupal.org redesign implementers

---

Will the g.d.o design be changing with the d.o redesign? I'm wondering b/c I'd like to customize the g.d.o group i admin - add pages, blocks, et cetera.. and am wondering if that will be lost effort if g.d.o is changing soon? thanks in advance, Stein Drupal.org redesign plan for the Drupal Association

---

I've been helping with documentation pages and found that some pages appear to be editable, but in fact are off limits. This seems to be related to Full HTML pages or Auto-generated pages. The pages themselves look like any other page - which is what causes the confusion. Would the redesign infrastructure team please discuss possible solutions to this that involve a visual queue? After my hand gets slapped for dinking with a page, I then go beg forgiveness OR After I try to edit a page I realize I have to go grovel in another issue queue to get someone else to do my dirty work. All this begging is making my knees hurt (she said with a smile). Drupal.org redesign implementers

---

Could we add a task to clean up existing contribution branches by removing invalid ones (e.g. DRUPAL-6--1-0 or DRUPAL-4-7--2-0 , and many more). This assumes we actually have an automated way to generate a list of valid branches - not currently easily done in cvs. This node is what sparked the issue http://drupal.org/node/97084 thanks, bekasu Drupal.org redesign implementers

---

Start:  2009-06-12 09:30 - 18:00 America/New_York Organizers:  Amazon User group meeting On Friday June 12th, we will be having the Drupal.org redesign sprint. All Drupal designers and developers who would like to learn how to how to contribute to theming drupal.org and implementing the redesign are welcome to attend, but must sign-up in advance. 20 Ames St., Cambridge, MA white-tiled building - Sprint is in Conference Room 135: Go to lower level of Media Lab, look for double glass doors "001"; go through doors, up metal staircase; 135 is at the top on right. We will meet on the lower level of Media Lab near the piano at 9:30am. If you have any questions, please call Todd Nienkerk at 512-517-5165. In order to attend, we will train you how to set-up your infrastructure.drupal.org account, and get your own hosted copy of drupal.org so you can see how your theme improvement looks. We will also train you how to work in the redesign theme(BlueCheese) issue queue. If you are interested in helping, please sign-up and we will schedule your training. Design For Drupal

---

Start:  2009-05-07 19:00 Europe/Berlin Organizers:  Thomas_Zahreddin Virtual meeting (eg. IRC meeting, Drupal Dojo) Hallo jeden Donnerstag abend treffen sich Leute online, um gemeinsam an Übersetzungen von Modulen in Deutsche zu arbeiten. Dazu wird der Editor gobby, die voice-chat-Software mumble und IRC #drupal.de auf Server: irc.freenode.net . Detais zu den Programmen und der Konfiguration findest Du unter http://www.drupalcenter.de/drupalchannel. Ich freue mich über jede/n . Bis dann Thomas Zahreddin PS: Sorry für das crossposten, gerne verteile ich die Einladung auf einem anderen Weg, wenn ich damit alle deutschsprachigen Drupal-User erreichen kann :-) DrupalCamp & DrupalCon Germany

---

Chris Charlton posted a reply: Just saw, I'm getting caught up.

---

Rob Mills posted a new topic: the comments on this flickr group tie in nicely with a task at: www.disambiguity.com/ perhaps some of you could post some wireframes over there.

---

Rob Mills posted a new topic: Hi All, I posted quite a few screenshots of other blogging/CMS/open source sites etc. Would be really interested in people's comments on what they like and dislike about these sites. What can we learn from them for the drupal redesign and what should we avoid and so on ... Thanks Rob

---

A Keynote presentation at Drupalcon Szeged, Hungary 2008. Presented by Mark Boulton and Leisa Reichelt

---