I think the idea and direction for .com has been pretty well hashed out and there have been snatches of discussion re: .org in various places but we really need to have a "central" discussion on its use. I have set up a basic site so that we can begin using it as a work environment for the SoC Getting Started guide (just a top-level book has been created for it). There has also been some discussion regarding what kind of "projects" we might use it for in this thread: http://groups.drupal.org/node/2772#comment-7788 . Currently anyone with a d.o or g.d.o account can login and they will have create/edit rights.
So, here are the two biggest things to hash out that I see right now:
1) How do we want to use the site, other than the docs work we have already identified? If we will use it for code and demos, how do we determine what's allowed on and what isn't? Who has rights to do what? You get the idea... (Note: keep in mind that the scratch site will not be a place for individuals to just test out code they are working on. Everything here will be directly related to collaborative Dojo activity. You can create your own personal test sites for playing with things you learn in the Dojo.)
2) Who will administer this? We need to have a small group of people who are willing to help admin the site. How many do we need? If we want a wiki or OG or whatever then it would be helpful if people interested in those things would volunteer as admins. Admins can have full admin rights on the site as well as an FTP account for getting stuff onto the server.
So, any ideas, suggestions or volunteers are welcome so we can help focus our energies a bit.
Comments
Should we make multisites?
Maybe we should place all the known-good modules we can think of into /sites/all, and then just create a multisite for each project and enable just the modules that it needs?
dojomodule.drupaldojo.org
screencasteditors.drupaldojo.org
themepack.drupaldojo.org
project1.drupaldojo.org
project2.drupaldojo.org
We could then turn the drupaldojo.org domain into a placeholder that just does listviews of all the subdomains currently in action. Sound good?
Senpai
Joel Farris | my 'certified to rock' score
Transparatech
http://transparatech.com
619.717.2805
Yes!
I agree that if we have different types of projects running they should each be their own site. Otherwise we will have a mess pretty quickly I imagine. I guess I can start that with a docs.drupaldojo.org for the docs project and we can add others as we settle on what else we are doing.
As a note, I don't think we need a thempack area. There is already a g.d.o group for it and all of the work is going on in the sandbox, which is where it needs to be.
Learn Drupal online at Drupalize.me
Great ideas - great work!
Really like the direction you're going with this site. Think the external site(s) are shaping up to be both complimentary of each other and the official Drupal sites (g.d.o./d.o.). As there have been many different people thinking along these lines, we should be able to get some great feedback and contributions.
Here's my take on a some of the aforementioned points:
How do we use this site? Who gets to do what? Who has rights, etc.? - Think it's going to be a trick to come up with definitions that will accommodate the entire group (one of the reasons I've started a learning portal experiment on my site!?!). And when talking about 'collaborative Dojo activity', how does that differ from Drupal activity? To me, anything that adds value back to the larger Drupal community should not be off limits to the Dojo and any affiliated sites. If we work towards coming up with some general guidelines pertaining what would and wouldn't benifit Drupal, that could be a step in the right direction. Although the comments took a completely unrelated path, I tried to set up some talking points in this wiki. While the concepts behind install profiles and distributions are still very new, I think they have some resonance in terms of the scratch site(s) and this discussion. If the end goal of a given project is to make it available (to the community at large) as an install profile and/or distribution, then it's probably fair game. If a project is either a personal or client project in which they don't want to share back to the community... that's probably something we don't want to bother with.
RE: Who should administer, do the active development? Probably should just leave it open to folks that are really willing and excited to actively participate in this type of thing. But then again, that's pretty wide ranging. If the site is going to contain a bunch of different projects (on subdomains), then it's prob. going to vary from project to project. When it comes to creating projects/subdomains for something that may already exist as a working group, I think there may be some room for collaboration. There are a lot of working groups (on g.d.o.) that don't have much activity. If we're able to provide a space for collaboration and open development, we may be able to add value and ramp up activity. For the main .org site itself, it may be nice to identify a few folks with different skillsets (or things they want to learn) to tackle various parts (customizing themes, modules, documentation, and even marketing). To me, all the external sites could be looked at as learning projects themselves. We should try to document each step from start to finish and try to put it into some sort of 'lesson framework'.
For what it's worth, I'm in the beginning stages of outlining some of these ideas as I'm setting up a 'learning portal experiment' on my site. As I'm planning to open things up to collaboration, and share back as much as I can (including actual client projects), I think it's be a benefit to all if we could keep these conversations going on the official drupal sites.
Good stuff, y'all - the Dojo is pretty amazing!
Gus Austin
Director of Chaos and Confusion
PepperAlley Productions
What am I trying to do with Drupal?
Gus Austin
Who should administer the sites?
I'm of the opinion that we could turn over full multi-site control to any group of people who want to make a sandbox for their dojo-related project. These sandboxes could actually become the week-to-week pedestals from which we learn our crane stance. The sensei for the weekly session could be working from a live server, which we all can refresh at will to see updates. There are only 50 users in the dojo sessions right now, so by watching the screencast for instant updates, and being able to have the lesson.drupaldojo.org window in another tab? I'd call that fantastical.
Joel Farris | my 'certified to rock' score
Transparatech
http://transparatech.com
619.717.2805
Setting up projects
I have already set up the first project for documentation work at http://docs.drupaldojo.org. Any group that would like a project site at .org should run it by the group first by posting about it here in g.d.o. Once the community gives support for dd.org to be used for the project in question, I will create the subdomain and db and do a basic install (we are running these as a multisite). I can then give admin rights to the group of people that want to run it.
Learn Drupal online at Drupalize.me
Do we have guidelines in place?
Just wondering if we have any guidelines/benchmarks in place regarding what would/wouldn't be a good project to support on the drupaldojo.org. How and who would be making these sorts of decisions. Majority vote? A committee or something? If we don't have something in place, it may not be a bad idea to hammer out some ideas.
Gus Austin
Director of Chaos and Confusion
PepperAlley Productions
What am I trying to do with Drupal?
Gus Austin