Drupal Dojo CoffeeTalk

Events happening in the community are now at Drupal community events on www.drupal.org.
joshk's picture

Hey everybody. This weekend I am on the road, meaning I'm not going to be able to give a lesson on Sunday. I also haven't hustled up a substitute, although anyone is welcome to jump in.

What I wanted to propose as an alternative, if no guest-teacher emerges, is that the group gather on IRC, moderated skype, and whatever VNC screensharing seems appropriate, and have a community meeting to talk about how things are going. I think this has been a great success, and I think with a little planning and cohesion, we can really take it to the next level.

Suggested topics:

  • How to better organize group activity on g.d.o. (brainstorm, don't be held back by existing functionality)
  • Promoting the group?
  • How to best present the group and existing materials (screencasts, documentation, etc) to new members?
  • Future lesson topics?
  • Dojo Projects?

Any feedback on this idea? Even if it doesn't happen on Sunday, I still think a real-time conversation about the Dojo's future is a good thing to do.

Comments

Maybe we should contact Merlinofchaos

coupet's picture

As per merlinofchaos suggestion in in Drupal Dojo Lesson #6!

It's clear there needs to be a node access presentation. I'm willing to take part in one, though I'm not sure I'm quite organized enough (or have the time to BE organized enough) to truly run one, I can certainly handle a section describing how node access works in Drupal 5, and what writing a node access module is going to be like.

Oooooh

joshk's picture

This is something I need to learn more too. Let me see if I can get Merlin and maybe Moshe to team up on this. ;)

http://www.chapterthreellc.com | http://www.outlandishjosh.com

I Too Have Great Interest In This...

mpare's picture

I think this would be a great lesson. And really I would assume that it would need more attention than just the lesson. Count me in for documentation or whatever else you would nee/like to see to get this going.

Peace,

Matthew Pare

Pare Technologies
info at paretech dot com

www.paretech.com

Peace,

-mpare

Pare Technologies
Drupal Consulting, Themeing, and Module Development
806.781.8324 | 806.733.3025
www.paretech.com

Figure Something Out? Document Your Success!

Video in chapters?

kreynen's picture

I've been discussing this with greggles via email, but I'll throw this out for feedback from the group. I've used Lynda.com videos when teaching into to media production classes. They work great for self paced, all online course as well as a supplementing instructor led training. Many of you probably have at least one of their HOT (Hands on Training) books.

Breaking up the videos into logical break points is REALLY helpful when you want to point someone to a specific part of a video. Like...

Before we talk about compression take a look at what is the goal of media compression?.

For the CVS video, I'd recommend breaking it up into...

1 Trunks and Branches - 0:00 - 25:15
2 Tools (WinCVS and CLI) - 25:15 - 1:00:15
3 Project nodes on Drupal.org - 1:00:15 - 1:19:00
4 Tools (Eclipse) 1:19:00 - 1:22:24
5 Q&A 1:22:24 - 1:33:55

I'm not saying the goal of Dojo videos should be to produce something as polished as Lynda.com stuff. Simply that breaking up the videos makes it easier to point to specific content and MUCH easier for users who want to see that content to get that video because of the smaller file size.

video work

joshk's picture

Greggles has a video pro who's willing to help us refine our work. I'll add the above to lesson #5. If anyone has other ideas on how to edit/break up the screencast videos, please add them here:

http://groups.drupal.org/node/2645

http://www.chapterthreellc.com | http://www.outlandishjosh.com

heh

I like the idea of the meeting

victorkane's picture

Along with the reasons you cite, I think it will give us a great way of seeing where we are, assessing the positive aspects of what we have been able to achieve and share together, hear some success stories of actual real world application of what we have covered (I know I have a few) and what difficulties we have, as well, and what we most need and where we want to go.

I think it would help the group a lot.

Also, it will help to coordinate the need to talk, I know a lot of important conversations have taken place on various topics, but it's hard to guess when everyone will be hanging out with some "quality time".

Victor Kane
http://awebfactory.com.ar

I really think we ought to

Squidgy's picture

I really think we ought to sticky these lesson notices up until they've passed - they almost always end up sinking into obscurity under the weight of unnecessary content. I'd actually suggest making a subgroup for all non-lesson items, or some such - things just get lost. I guess I'll bring this up at the actual meeting and see what the group feeling is.

Also (mwaha), http://squidgystudios.com/drupal/drupal_saloon.jpg .

really necessary

victorkane's picture

I have another major reason why I think this discussion is very important.

I have just posted the Wiki Class Notes Lesson #6 -- Theming. http://groups.drupal.org/node/2764 . It was a monumental task, taking some ten hours or so to work through my notes and the two-hour video, as well as running all the configuration and code and debugging along with the class to make sure that the attached pastebin.txt can really be pasted in and run by newbies with no hassle.

Don't get me wrong, I do it because I love it, and above all because it is bringing me up to speed fast. And not only me, but also several programmers on each of two teams I am working with as architect/mentor/lead are benefiting hugely also. As will the Buenos Aires Drupal Users Group (next meeting this coming Thursday, on organization and with a presentation on theming from this class). So there's no altruism here, just pure benefit and yes, the joy of contributing to the community.

And in this case, at least, I am sure that the text is useful. I know it would have been useful for me a year ago.

My problem is the autistic-like silence in the group on this effort (I may be isolated on an individual basis, but on a collaboration level we are spectacularly functional on the multimedia front, but on little else), and what to do with it so it best serves the community. Now, even though several Dojos seem to have involved themselves heavily in the documentation project, from what I can see from the mailing lists, still no-one has done anything to suggest how the class notes wikis, or parts of them, as well as a lot of other excellent material here, can find their way into any of the Drupal handbooks. (People have made declarative suggestions, but no-one has done anything AFAIK. I would love to be wrong on this.)

I myself have not joined the documentation team, since although I feel I do documentation very well, I prefer to work on the development side with the little free time I have. So I need to run with a pack here, I need to work in a functioning group that is collaborating. So my question is, and I think this can only come out of discussions among all of us in the group, what is going to happen to all of this material? When you just know that poor souls are peeling their eyeballs searching for stuff like this on drupal.org (maybe not even aware of groups.drupal.org's existence) (not only the class notes, of course, but stuff like the screencasts, the forays into eclipse php development tools as an IDE for us to use, and countless other user posts: how is all of this going to make it into the Handbooks?

I mean, here in the Drupal Dojo classes and posts, we do a heck of a lot more than just bounce around catchwords and mention websites and drop names amidst cackles of buddy-like "cool" laughter. I know through my own pain and starvation for knowledge and cookbook like info (which, apart from within the Drupal Dojo community and other serious efforts, seems to come at a premium price few can afford to pay) that what we are doing here is damn important, and is in line with the other serious efforts, like merlinofchaos' Themer Pack group, the Javascript group, the Newspaper group and many, many others.

But to get the word out in a sharing community way, and that is through the Drupal Handbooks, we must foster more collaboration among us, things have to be discussed and decisions have to be taken.

Don't get me wrong. I think it's great that people who have sacrificed themselves for years on end publish books and get paid for it and send a portion of that back to Drupal. That's wonderful (even if for some inexplicable reason no-one can get their eyes on even an old PDF ... that's not wonderful). Heck, I may even write a book myself, make it bi-lingual (English and Spanish) or something. But I can assure all my fellow drupalers, that I will follow the practice of people like Alistair Cockburn (whose "Writing Effective Use Cases" was published countless times in PDF form in beta before coming out, and thousands of copies were still sold and continue to be), and practically all community based authors put the beta versions up on their websites so the brothers and sisters can get the benefit first... and they will be able to benefit from the corrections. I believe in the way of the Bazaar, not the Cathedral: a thousand pairs of eyes are better than two or three self-appointed "knowers". That's supposed to be what we are about.

And if your publisher won't let you, get another publisher.

So the Handbooks should be the best open source way of sharing info there is. That's where the stuff has to be published first, in a no-nonsense, but user-friendly way.

The whole open source model is supposed to be based on "the more people know the better".

So I hope all dojos can participate in this discussion, rather than chancing it on whoever happens to be around IRC at a given point in time. We need to see how this stuff gets put into the Handbooks in an orderly fashion.

I also want to take this opportunity to send a huge "Thank you" to Josh for this initiative, and to all my brothers and sisters in the group. It has really been fun, and a thrilling experience. Let's keep growing and reaching out.

Victor Kane
http://awebfactory.com.ar

Noted.

Tresler's picture

I've written on this before. Basically, I'm of the opinion that while all the work we do is extraordinarily helpful, it needs major refinement to become true documentation. That includes the notes, screencasts and all.

At this point, I've assigned integrating the screencasts into the doc to myself on the To-Do wiki.

In order to accomplish this I think a to-do list is the minimum toolset needed. Out group of 500+ can't know what others are working on, what they can help on, or what is desired without it. The wiki format of this has garnered little interest; although that could be for lack of visibility. We had talked of linking it to the top of the dojo page, but we never got around to it. When I proposed a dojo-specific issue queue I encountered some resistance. But these things won't happen without a little more organization.


Tresler Designs

Thank YOU!

joshk's picture

First of all, thanks for putting in so much hard work on this documentation. You are absolutely correct that we should be doing more to get it out to people.

There are a couple of things I think we can do immediately. First of all, I need to track down Sepeck and figure out what the documentation team is open to having in the handbook. I know there were some concerns that the scale of the documentation you've been creating would dwarf many other pages (which are shorter), and that they might want to take exceprts or break them up into many pages. That discussion happened after lesson #1 though, so now that we have more of a body of work, I think it should be revisited.

The second thing we can do is, as you suggest, put a little more group focus on grooming the documentation. To be honest, I haven't even had time to read through the latest lesson notes. As they say, the fish stinks from the head! I'll make more of an effort there.

Lastly, I've been thinking about registering drupaldojo.com(org?) as a more effective "aggregator" page of our activity. The idea here is not to replicate or replace the g.d.o. group, but rather comes from my feeling that I really want to have three or four web pages where we can take over the whole screen. This would be a place to showcase our work, explain the process (such as it is) to new participants, and putting the documentation and screencasts up in an inviting way, etc.

Anyway, thanks again for all your hard work. I have a feeling that if we continue to push forward for another month or two, this group will truly hit critical mass.

http://www.chapterthreellc.com | http://www.outlandishjosh.com