Discussion from February 11 online meeting

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

We should carry on the discussion from today's online meeting to help nail down things that were discussed and bring those that could not make it up to speed. This is a VERY brief rundown of the highlights and I'm sure the recordings will be available soon for those that want to follow the whole thing. If I'm off-base on any of this (which could easily be the case) please correct/discuss in comments.

Two big topics that were covered were 1) the idea of a separate scratch site to experiment and work ideas out in and 2) how to work with d.o handbook and get improvements into it. Sepeck was kind enough to stop in and really hash out these ideas, give guidance and be involved in the discussion.

Here is a list of some of the finer details that I remember (I'm sure I'll miss stuff so please correct me and I will add it):
1 - We would like to have a separate site(s) for certain aspects of the Dojo. We really need to discuss what we want to use it for. The general consensus was yes to this and some felt strongly (including me) that this should not be an end unto itself but rather just a scratch place to work up something that we can then contribute back to d.o or g.d.o. Other ideas (not necessarily all on the same site) included a "more organized" place to keep track of lesson information and a "project" site that creates a fully functioning site for some fictitious entity. Additionally members of the Dojo have purchased the .com, .org and .net domains for drupaldojo. I have volunteered space on my server for a scratch site.

2 - We may also consider creating a proposal to present to d.o asking for a new drupal site along the lines of Cookbook for Drupal.

3 - Since we are looking at other sites/spaces for our needs we need to come up with a good, solid list of a) functionality that we are looking for and b) what of that is not being currently provided by available resources at d.o or g.d.o and can we work to resolve some of them?

4 - There was a lot of discussion about changes people would like to see to the d.o handbooks. We need to get these ideas down and come up with solutions, which means writing documentation and proposing ideas to the documentation team either through discussion or issues as appropriate.

OK, I can't remember much else but I know there was more. There was a lot of discussion and many ideas - let's not lose all that. Let's get some solid plans down. I just want to add as my personal note to the above that I feel oadaeh's wiki page can suffice for us to keep Dojo lessons simple to access by simply updating the wiki page for each lesson and I'd like to keep as much of that sort of thing on g.d.o as we can. I can see doing "work in progress" elsewhere but I think splitting too much Dojo information into many different sites will make it harder for people to know where to go or what is what, much less keeping it all updated.

So, anyway, discuss...

Comments

recording?

lapur's picture

what was recorded? I didn't hear any announcement of voice or audio.

Great!

Excellent summary

victorkane's picture

I saw your post a couple of days ago, and haven't had time to respond.

I think it is an excellent summary and really gives the most important points which motivated everyone on Sunday.

The only thing I would stress would be some of Sepeck's contributions, apart from, as you say, helping us to hash out some very complicated issues. One was that, the weird "contributor links" checkbox that is half way down the page when you edit your user profile at d.o., when you check it, makes a new block appear on the right-hand side of the page when you log into d.o., chock full of fun and games and handy links for drupal geeks. And the first link (Sepeck implemented it as we spoke on Sunday) is to the advanced search facility on d.o. (there is a similar one here on g.d.o when you go into advanced search). It's facilities for narrowing down searches through node types and taxonomy and module topics is remarkable, and goes a long way to ward off one of everyone's pet peeves on d.o., namely, how to find stuff without a sequential search through all the handbooks and their single hierarchy , single entry-point structure.

So now I have seen Josh's post, which is amazing in the sense that it is as if he was there talking with us, because a lot of the stuff he is saying in his post really addresses most of our concerns from last Sunday.

Josh is all for a having DrupalDojo.com set up so people (the people!) can easily find the good stuff we are producing here on Dojo. So people can easily find a way of getting to what they need. And where everything is integrated into the handbooks, can be used to enrich the handbooks. What Josh is saying meets squarely on one of our biggest concerns, which is overcoming our relative isolation so we can reach out to many people who as we speak are pulling their hair out (if the posts on d.o. are anything to go by). And also to showcase what we are doing so everyone knows about that, too.

I would comment directly on Josh's post, but the wiki commenting isn't set up, so I will go on commenting here on what Josh is saying.

Josh fully meets head on another of our concerns, where some of us (including you, from what you were saying, add1sun, the other day, and what you have said above), namely, that we not drift away from g.d.o at all, and continue using the group as our main water cooler. That is, let's have DrupalDojo.com to meet some of our needs that can't be addressed in any other way, but let's stay centered in the community, let's make sure we remain squarely centered in what we are doing with a scenario of collaborating with the Drupal community (whose high level of activity, intelligence and good solid work over the years has made Drupal possible after all), and not forking in any way, even as an interest group.

That leaves only one of our major concerns from the other day which Josh does not address, perhaps because of what he says about it being too much work and in the end a drain of resources. He may be right there. What most of us are in dire need of (apart from having our brains tested, of course), is a scratch site, where:

  1. We would have a place to put fully functioning demos from the lessons;
  2. And a place to put demos of our own, and perhaps use them for mini lessons.

For example, I gave a demo at the last meeting of the Buenos Aires Drupal Users Group on how to make a CRM-light with just CCK and Views, and I would love to have a "dojo" place to have that running together with some documentation so people can re-use it. I feel doing that (maybe on DrupalDojo.org, and not the brochure site DrupalDojo.com) would be extremely useful, a place full of demos of that kind, a "demo" garden, would be incredible. Just to give another example, take a look at funnymonkey's Userlink + Taxonomy = Useful demo site: I had to tag it in delicious, because I stumbled upon it by chance in the mailing lists, and then couldn't find it even on their site! And it is just incredibly useful.

In the Cathedral and the Bazaar, in the final Acknowledgements section, Eric Steven Raymond underlines one of the startlingly clear points made in the book:

"Phil Hudson reminded me that the social organization of the hacker culture mirrors the organization of its software, and vice-versa."

That means, that the democratization of the flow of information in an open source software community is essential to keeping that software strong, clean, functioning, beholden to no-one.

MVC: more value in the community!

And that is a contribution we on this Dojo group certainly have a chance of making in the Drupal community.

Victor Kane
http://awebfactory.com.ar

Regarding a Scratch Site . . .

oadaeh's picture

I have two points on that:

1) I personally don't believe that a separate scratch site is necessarily a bad idea, if a few ground rules are laid down in the interest of the community. For example, keeping all conversation on g.d.o, and making it clear that it's not a place for people to keep their personal, non-dojo-related test code.

2) What happens when someone posts code that breaks the site, due to an extra or forgotten character (or whatever)? Then we get into the maintenance issue where the site is down until one or a few people can get around to fixing it. If the site is hosted on someone's personal server, then that number of individuals may be quite small and the time to fix it may be quite large. Over time, the site may end up like the themes site, where it just seems broken or quirky all the time.

victorkane's picture

plus homework. On the .org site, not the easy to access brochure site.

Start out with putting our lesson examples (sandbox) so people can see code that is running; also, we can put up viewcvs or viewsvn or trak or gforge, so people can get the sourcecode and everything.

If that works well, we can then include some "workshop" projects... I think we have to trust fellow dojo'ers to be able not to break this specialized demo site (that should be part of the learning process).

Now, I always put all of my sites (including a database dump) into version control, so that if/when the site gets broken you can always revert to last working version. We could adopt that practice.

Victor Kane
http://awebfactory.com.ar

Here's the kind of thing I have in mind

victorkane's picture

See what they are doing in the Twin Cities group:
http://groups.drupal.org/node/2791

Victor Kane
http://awebfactory.com.ar

FWIW

joshk's picture

I'm still wary of creating a community site external to groups.drupal.org. While I understand the value of having a working project, I don't want the group end up spread out more than it already is.

Obviously you don't need my permission to do anything though!

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

External sites good only if they add value

gusaus's picture

I think a lot of good can come from an external site(s), mainly because you have a bit more room for experimentation and 'project oriented' learning. Another plus would be that the 'making of an external site' (all could be put into a lesson framework) and the 'site itself' (as an install profile or distribution) would be open and available to the community.

I share the same concerns about spreading this group too thin. Think we need to both better organize this group and look at ways to connect with others (group - group; g.d.o - drupal; irc - drupal; add the other drupal sites/blogs that are already out there). Would be helpful to us all if we could ramp up the conversations in this group - get more input/viewpoints in and outside of the 'usual suspects'.

I actually think that the site(s) discussed in these recent conversations could give us more flexibility in terms of looking for solutions. We'd be able to try out new modules, test different ways to aggregate, integrate other formats such as mediawiki, and do further experimentation with organic groups. We could integrate the best bits (what works) into both the g.d.o. and d.o. Simply by offering up RSS feeds (on external sites) and aggregating (on the drupal side) we should be able to provide at least one easy means for folks to keep tabs on all the activity.

Further embellishment/somewhat related rambling can be found on these posts -
http://groups.drupal.org/node/2618
http://groups.drupal.org/node/2030

Think we've already concluded that there's no 'one way' that's going to work for everyone (in terms of external sites and projects). We should make sure that whatever we do doesn't take away from this and other 'official' sites.

Gus Austin
Director of Chaos and Confusion
PepperAlley Productions
What am I trying to do with Drupal?

Gus Austin

The one thing I'd add to

senpai's picture

The one thing I'd add to this thought is that having a site like http://drupaldojo.com serves to solidify a source of information regarding the group and it's lessons. Having a site like http://drupaldojo.org serves to promote a community workspace for projects that the dojo is involved in. There are no plans, at the present, to allow any sort of node creation, commenting, forums, or community activity on these two sites.

That's what GROUPS.drupal.org is for. They have given us a place to converse, post info, wiki ideas, and track information, and that is what we shall do.

Until somebody decides to put http://drupaldojo.net into play, and then it's anybody's guess! ;\


Joel Farris | my 'certified to rock' score
Transparatech
http://transparatech.com
619.717.2805

Only makes sense if everyone feels the need...

victorkane's picture

No hurry, we will do it as a group or not at all, when and if there is a real need for it...
In the meantime, it is perfectly cool for people to have their own demo sites and post what they have done here on the group, that's fine too.

The times I most feel it is necessary is when I am doing the Wiki Class Notes, and running the examples, and wishing there was some "official" dojo place to have it running. But of course, everyone should run the examples in their own sandbox anyway.

Victor Kane
http://awebfactory.com.ar