Presentation given at Drupaldelphia (Drupal Camp Philadelphia) on Friday, July 31, 2009.
Covers how to understand and become a part of the community along with a variety of tools for getting help and interacting.
19. Drupal Community Awesomeness Handbooks (Documentation) Properties: - Permanent - Reviewed - Open **Documentation is one place where someone new to drupal can contribute! See http://drupal.org/contribute/documentation
20. Drupal Community Awesomeness The ”Planet” - http://drupal.org/planet Properties: - Current - Non-Interactive - Trendy!
24. Know How To State Your Issue Clearly... Go to http://drupal.org/getting-involved , and look for ”Report a Problem” and ”Use the Issue Queue” sections for much more information and advice!
25. Drupal Community Awesomeness The Drupal Dojo http://groups.drupal.org/drupal-dojo Properties: - Training - Curriculum - Working Group
26. Drupal Community Awesomeness IRC!! Properties: - Live, all the time - Global - Local - Real People - Drupal Community loves IRC http://drupal.org/irc Please read and understand everything on this page. Please.
27. Drupal Community Awesomeness The Channels: - #drupal - #drupal-support - #drupal-theming - #drupal-design - #drupaldelphia - #drupalcon The Commands: /join /me /msg /away The Bot! (Druplicon!!): seen? tell karma factoids function lookup node lookup logs Don't ask if you can ask, just ask IRC See http://www.disobey.com/bot
Hinweis der Redaktion
Welcome!
Drupal For Fun Since 2005 Hobbyist/Enthusiast Looking to have fun and make friends
So who are you? And can you help me? Introductions? If a small group.
It's Open Source! It's Free! Is that a good thing? Bad thing? Mean's different things to different freedom.
There is a lot of this kind of free yes? Is there a hidden catch? Something else you have to buy? - Well ya got to run it somewhere - Someone has to make the website work!
For some people free = low quality/junk right?
With respect to the free software Drupal may be freedom, but I don't think it is free. You have to participate and sweat to get any value from it!
Here is why I don't think it is free. So tell me... Which Module is the best? Which one will do what you want? Which module will be around two versions from now? Which one will leave you up the creek without a paddle?
When you are part of the community...
It gets easier!
Well you've already made the right start. Find ways to meet fellow drupallers face to face at... Camps Meetups Cons
The person you want to anser: - Is a volunteer/limited time to spend on this non-$$ task - Is probably scanning forum titles trying to pluck out questions they think they can answer (or would like the answer to themselves) - The easier you make it, the more likely you'll get a response - If you don't get a response, maybe you didn't ask the right question?
Handbooks are an excellent resource. As a newbie this is one area where you can give back right now! Don't forget api.drupal.org. Keep going back to it to understand what is under the hood.
Knowing which way the wind is blowing is critical in Open Source Software. It helps you to make good choices for your projects. It gives you a better feel for the community.
Twitter Kind of a stream of consciousness Tags to follow: #drupal #d4d (for the theming and design crowd) #drupaldelphia (or inserteventtag here... ) Really a blast when you are at an event like Drupalcon! Definitely for the hard core ”can't get enough” drupaller
It's where maintainers live! Everything (almost) in Drupal has an issue queue. Even things you might not have thought of like - webmasters -
Category: Is it really a bug? If so, boil it down to the simplest way to report/reproduce if possible – then report it. Feature Request? You'll do best if you make sure you are working with the latest version. Developers mostly want to add new features to the latest code. Task? Unless you are the maintainer, you won't use this one much. Support Request? Did you REALLY try the forums, IRC and other channels first? Make sure that is clear in your issue. No one owes you anything here. Assigned. Don't assign it to yourself unless you are planning to fix it! Status. Mostly for the maintainer or anyone participating in FIXING the problem will use that field. If the maintainer looks at your feature requests, gives you a reason why they don't want that feature, then marks your issue ”won't fix” well too bad. Nothing stopping you from rolling your own. What do the status mean? Active, Needs Work, Needs Review, Reviews and Tested by the Community, patch (to be ported), fixed, postponed, postponed (maintainer needs more info), duplicate, won't fix, by design, closed Component: Standard are Code, Documentation, Miscellaneous and User Interface. Project maintainers can define their own. Try your best to pick the right one Title: Can the maintainer get an idea of what your problem might be just by the title? If so, it is a good title. ”Help!!” Not so much...
Use these druplicon: tell winstond I have a great idea for your presentation...wait you giving it now aren't you – doh! Seen webchick? Yay! cache_set? Cheer? Context? Views? Zen? Winstond++ druplicon: karma webchick