[drupal-devel] creating drupal-doc teams
Currently, it seems we have lots of interest in taking Drupal documentation in new and interesting directions. To facilitate this, I'd like to see if we can't form some documentation teams. Much like I asked if Djun and Bryan would be in charge of reorganizing the About section of the handbook, I'd like us to form other two person teams for any major area that we have expressed interest in developing. Here are just a few examples of some areas I could imagine Documentation teams for * Restructuring/reorganizing each of the new handbook sections as defined on the V2 page: http://drupal.org/handbook/v2 For example, the About the handbook section. We need a couple of people to be in charge of our authoring guidelines and best practices for creating Drupal handbook documentation. (Anisa spearheaded the style guide revision; perhaps we could coax her and one other person to handle the About the handbook section?) * Best practices for configuring and building Druapl sites (Roland has already volunteered for this one :) Is there another?) * Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation. (Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.) * Marketing materials (Andre? You seem to have lots of marketing ideas :) * Etc. The documentation team would be responsible for most decisions regarding their project (in some cases there might be some overlap between other documentation teams, so they'd have to coordinate). Initially, I would hope that each documentation team would run a proposal by the drupal-docs list so that all of us could offer feedback in the construction of their individual project so that a good compromise of the important opposing interests (if any) can be reached. Otherwise, let us know when new documentation is posted (maybe this will be automated) so that we can offer feedback and suggestions. Or when the documentation team members are having trouble solving an issue between themselves, contact the list for assistance in resolution. In the case of any who volunteer for restructuring/revising the handbook sections, if they would like, they could also continue on as the offical book maintainers for those new books. If anyone has ideas for other documentation team areas, please respond to this post via the drupal-docs list. I've mentioned a few people here, but I'm sure there are a lot more. If anyone would like to volunteer to be a documentation team member for a specific project, feel free to post to the drupal-docs list or contact me privately. Once the documentation teams have been created, I'll create a page in the About handbook section so that people know who's in charge of individual projects. I hope this works well for everyone. Putting people in charge of specific areas seems to me the best way for us to get the things we want accomplished. Charlie
On Thu, 19 May 2005, Charlie Lowe wrote:
* Best practices for configuring and building Druapl sites
(Roland has already volunteered for this one :) Is there another?)
I can recommend Steven E Peck (sepeck). I don't know if he is on any of these lists. If he isn't, he can be reached through the contact module at drupal.org or #drupal.
* Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation.
(Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.)
I might be able to help with this (depending on the direction of the ideas). Cheers, Gerhard
Hi All, On 19 May 2005, at 3:48 PM, Gerhard Killesreiter wrote:
On Thu, 19 May 2005, Charlie Lowe wrote:
* Best practices for configuring and building Druapl sites
(Roland has already volunteered for this one :) Is there another?)
I can recommend Steven E Peck (sepeck). I don't know if he is on any of these lists. If he isn't, he can be reached through the contact module at drupal.org or #drupal.
* Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation.
(Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.)
I'd certainly be interested in this. I currently have export to very simple XML working. There's lots of other things which need attention, too. I'd love to work with Gerhard on moving book.module forward and working on other tools for the documentation team. Regards, Djun
I might be able to help with this (depending on the direction of the ideas).
Cheers, Gerhard
On Thu, 19 May 2005, puregin wrote:
On 19 May 2005, at 3:48 PM, Gerhard Killesreiter wrote:
On Thu, 19 May 2005, Charlie Lowe wrote:
* Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation.
(Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.)
I might be able to help with this (depending on the direction of the ideas).
I'd certainly be interested in this. I currently have export to very simple XML working.
*g* That is why I wrote "depending on direction of ideas": I have no experience with XML, docbook, and all those other acronyms that popped up in discussions about improving book.module. I am also not too much interested in this. I'd rather include features that can be directly used on drupal.org and on sites that use book.module.
There's lots of other things which need attention, too.
We should draft a list and make tasks from the items in the project tracker. We could also have an irc meeting to identify tasks. Cheers, Gerhard
On May 19, 2005, at 3:02 PM, Charlie Lowe wrote:
Currently, it seems we have lots of interest in taking Drupal documentation in new and interesting directions.
Well, I was going to be nice and wait 24 hours so all our friends in Asia and Europe had a chance to respond. But why not take the best jobs while I can ;-)
Documentation teams for
* Restructuring/reorganizing each of the new handbook sections as defined on the V2 page:
I am happy to run refined card sorts or further documentation surveys to help with this effort.
For example, the About the handbook section. We need a couple of people to be in charge of our authoring guidelines and best practices for creating Drupal handbook documentation.
(Anisa spearheaded the style guide revision; perhaps we could coax her and one other person to handle the About the handbook section?)
Probably the number one thing on my list is helping to get 60+ module handbook pages going by working on that little section of the handbook guidelines. Here's my campaign speech: I am open to suggestions, and I work like a dog if you just want tell me how to do it right.
* Best practices for configuring and building Druapl sites (Roland has already volunteered for this one :) Is there another?)
I spend a lot of time building and tearing down sites so I'll be happy to edit or contribute my upgrading and navigation tutorials. I have also done some videos for analysis in the past. Sounds like we already have some leaders for this.
* Initiatives for improving the collaborative book and other technological solutions to improve Drupal documentation usability, integration, and creation.
I'd be happy to help with block and navigation suggestions for information architecture.
(Djun has already been working on this. Perhaps he'd like to be one of the team members. We'd only need one other volunteer then.)
Putting people in charge of specific areas seems to me the best way for us to get the things we want accomplished.
Woo-hoo! Let's get writing!
Charlie -- [ drupal-docs | http://lists.drupal.org/listinfo/drupal-docs ]
Charlie Lowe wrote:
* Marketing materials
(Andre? You seem to have lots of marketing ideas :)
Sure. (sorry for the late response - its virtually impossible to keep on top of all the discussions on devel and docs - even just to read them let alone getting around to respond). Would anyone be interested in doing a brainstorming session on a full list of features and/or uses of drupal? From there I would like to boil that list down to some real benefits of the product and come up with ways to market the product based on those. I will be doing my own brainstorming and share the results somewhere (perhaps the wiki or a forum on drupal). If anyone is interested - e-mail me at: andre at andremolnar dot com (not my mcsparkerton address as the message might get lost in the dev/docs list postings). andre
On May 22, 2005, at 10:57 AM, Andre Molnar wrote:
Would anyone be interested in doing a brainstorming session on a full list of features and/or uses of drupal? From there I would like to boil that list down to some real benefits of the product and come up with ways to market the product based on those.
A good place to start would be to look at the Admin Help that has been written. The first paragraph of 60 of the more popular modules contains user benefits. Cheers, Kieran
Market drupal for sale or as open source free software? It is amazing how many niches we could target. I.E. clubs, government, real estate, mortgage, small business. A multi media platform positioned to replace television and radio. Gee, let us integrate VOIP and CRM, voice XML, accounting, and web casting. Let us explore new and innovative ways of delivering content to the end user. Cell phones, personal readers, Etc. Did you know the concept of Open Source is not very widely understood in the business community? People just don't have time to grasp the concept. People have heard of Lynyx and the stories behind that saga. But, many people still don't get it. Do you think their IT staff is telling them? Heck no! It seems to be some type of trade secret. Not once did one of my IT guys say: "Hey, you know you can load a practically turnkey website right now and it won't cost you an arm and a leg. It is not only a web site, but a platform you can grow your business on for a long time. If I had tried to get a bid on my project, it would run into the thousands of dollars! Catch my drift? It is phreaken amazing! If I understood what this was all about ten years ago, I would be a wealthy man. If only I realized that I could have built a practically free platform using voice xml five years ago. All I would have needed is dialogic cards and a development platform from IBM. And... it was free free free. Sorry, I don't mean to make this all about business. I am just envious of the folks who were ten years ahead of me. And, I thought I new alot about computers. So, what do you mean by marketing? business or education? I guess I still don't exactly understand how Open Source Software survives and flourishes. I am awed. Kind Regards, Christopher Taylor Business Development Manager Bnmc, Inc. ----- Original Message ----- From: Kieran Lal To: drupal-devel@drupal.org Sent: Monday, May 23, 2005 1:04 PM Subject: Re: [drupal-devel] creating drupal-doc teams On May 22, 2005, at 10:57 AM, Andre Molnar wrote: Would anyone be interested in doing a brainstorming session on a full list of features and/or uses of drupal? From there I would like to boil that list down to some real benefits of the product and come up with ways to market the product based on those. A good place to start would be to look at the Admin Help that has been written. The first paragraph of 60 of the more popular modules contains user benefits. Cheers, Kieran
participants (7)
-
Andre Molnar -
Charlie Lowe -
Christopher Taylor -
Gerhard Killesreiter -
Kieran Lal -
Moshe Weitzman -
puregin