From drupal at rocktreesky.com Tue Sep 2 11:59:11 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Tue, 2 Sep 2008 07:59:11 -0400 Subject: [documentation] Schedule next IRC meeting Message-ID: <6553B637-B4F1-407B-81ED-427A99EED43D@rocktreesky.com> I am planning some time later today to do a brain dump of the Doc sprint, which was totally awesome. I have a lot to write up and limited time right now though. I do however want to get us scheduling the next IRC meeting so we can keep our momentum going. I have set up a Doodle for Sep 11 - Sep 14: http://www.doodle.ch/7dx3823d582rxgsk . Everyone needs to vote on the doodle by *September 4 at 18:00 GMT*. As usual we will keep the meeting to one hour long and determine the agenda ahead of time on the mail list. Addi (add1sun) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080902/fc6ae966/attachment.htm From drupal at rocktreesky.com Wed Sep 3 11:14:03 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 3 Sep 2008 07:14:03 -0400 Subject: [documentation] Szeged Doc Sprint summary Message-ID: <2B0DD956-98E9-4EC1-803D-9B7FE48CFC58@rocktreesky.com> Here is a "short" summary of the Doc sprint we had at Szeged. It was an awesome time and I can't capture all of it in here. I just wanted to list of the big points (that I even know about). Lots of people were working on all kinds of stuff so I'm sure more was done than I can cover here. The biggest bummer for me is that I couldn't really manage to extend to the sprint into the evening which would have made it more possible for folks in North America to attend. I do have a bunch of thoughts on more sprints though, so stay tuned for a post about that in the next week or so. So, here is a quick list of stuff we accomplished. I don't have the names of everyone who helped out, so I'm sorry that I can't list them all out. There were too many people ;-) and I only had a chance to meet most of them briefly. - Thanks to Niels Bom and David Strauss we had a chunked up list of docs issues that needed components converted so that went swimmingly. It was tedious but a big thansk to everyone for rocking that. - We also moved anything in the Documentation in CVS component to Drupal core's queue under the Documentation component there once webchick gave the go ahead. - Paschal Ssemaganda assisted the Usability team with a bunch of component work as well so they could close down the User Experience project. - Joachim Noreiko wrote the new simple tasks page at http://drupal.org/node/302146 and worked on a bit of clean up of the Contributing to Docs section. - Once the simple task page was written a *lot* of folks reviewed the task page and worked on the tasks listed. ;-) Everyone should please review the page and make improvements. We want to have a clear place to send new docs folks so they can dig in right away and feel like they have some direction. - We opened up the Getting started guide for Drupal 6 (http://drupal.org/getting-started/6 ) to editing by the docs team (it was previously restricted by input format). We need these docs updated and many people at the sprint were eager to work on them, so they are now open. Please feel free to get them up to speed so that new users have a good reference. - Paschal and Barry Madore did work on improving the docs on adding screenshots. - Stella Power worked on JS code standards and Alan Burke worked on CSS code standards. - Moshe did a little Diff module mojo and created a patch for the Drupal.org module to add a direct link to the latest diff on the recent updates page (http://drupal.org/handbook/updates). That will appear on the site once Killes gets a chance to deploy the updates. - The Usability team outlined a new Usability section for the handbook and Niels started to write it up. - We added a bunch of people to the docs team, so welcome to all the new team members. - There was a ton of activity in the IRC channel that was hard for me to keep up with since there was so much snatching me away at the sprint, so kudos to the folks who were in the channel, especially the ones not in Szeged but still taking part in the srpint. - Lots and lots and lots and lots of people were cleaning up the issue queue, rolling in comments, reviewing sections of the handbook, eating chocolate and generally having a great time. Whew, that's about as much as I can spit out right now. Other stuff going on in docs that isn't sprint-related per se: - I've created a read-only g.d.o group at http://groups.drupal.org/documentation-team where we can post updates on work and announcements. This allows people who are not on the mailing list to be apprised of things and gives a central location for Doc team info with an RSS feed. It will mainly be used to summarize and point to mailing list threads, important issues in the queue and to d.o forum/front page posts. We will also post all scheduled meetings here so you can keep track of those too and add them to your calendar. Since it is read-only, there are no group subscriptions available and currently myself and sepeck have rights to add new posts. - Just want to remind folks (and point new members) to the ongoing discussion about opening editing to all auth users (http://lists.drupal.org/pipermail/documentation/2008-August/006191.html ). Please provide your feedback *in that thread* by Sept. 8. - The Getting involved handbook issues (http://drupal.org/project/issues?projects=18753&text=Contrib%20Redesign:)still need work so we can do the reorg. Thanks to everyone that has been chipping away at that. I've got a bunch more stuff to sput about but this post is already hella long so I'll wrap up there. Really, HUGE thanks to everyone. I am damned excited about the docs team right now and I feel like we are kicking butt. Keep rockin' the docs! Addi (add1sun) From mike at michaelfbooth.com Wed Sep 3 15:11:40 2008 From: mike at michaelfbooth.com (Michael Booth) Date: Wed, 3 Sep 2008 11:11:40 -0400 Subject: [documentation] Szeged Doc Sprint summary In-Reply-To: <2B0DD956-98E9-4EC1-803D-9B7FE48CFC58@rocktreesky.com> References: <2B0DD956-98E9-4EC1-803D-9B7FE48CFC58@rocktreesky.com> Message-ID: <61147EFF-4D5D-4770-8DA4-9CFBECAE12FD@michaelfbooth.com> I'm very glad to see that you've created RSS announcements for the Doc Team (http://groups.drupal.org/documentation-team). That will reduce the odds that I miss future meetings! Thanks for all your hard work. Mike Booth (mechfish) On Sep 3, 2008, at 7:14 AM, Addison Berry wrote: > Here is a "short" summary of the Doc sprint we had at Szeged. It was > an awesome time and I can't capture all of it in here. I just wanted > to list of the big points (that I even know about). Lots of people > were working on all kinds of stuff so I'm sure more was done than I > can cover here. The biggest bummer for me is that I couldn't really > manage to extend to the sprint into the evening which would have made > it more possible for folks in North America to attend. I do have a > bunch of thoughts on more sprints though, so stay tuned for a post > about that in the next week or so. > > So, here is a quick list of stuff we accomplished. I don't have the > names of everyone who helped out, so I'm sorry that I can't list them > all out. There were too many people ;-) and I only had a chance to > meet most of them briefly. > - Thanks to Niels Bom and David Strauss we had a chunked up list of > docs issues that needed components converted so that went swimmingly. > It was tedious but a big thansk to everyone for rocking that. > - We also moved anything in the Documentation in CVS component to > Drupal core's queue under the Documentation component there once > webchick gave the go ahead. > - Paschal Ssemaganda assisted the Usability team with a bunch of > component work as well so they could close down the User Experience > project. > - Joachim Noreiko wrote the new simple tasks page at http://drupal.org/node/302146 > and worked on a bit of clean up of the Contributing to Docs section. > - Once the simple task page was written a *lot* of folks reviewed the > task page and worked on the tasks listed. ;-) Everyone should please > review the page and make improvements. We want to have a clear place > to send new docs folks so they can dig in right away and feel like > they have some direction. > - We opened up the Getting started guide for Drupal 6 (http://drupal.org/getting-started/6 > ) to editing by the docs team (it was previously restricted by input > format). We need these docs updated and many people at the sprint were > eager to work on them, so they are now open. Please feel free to get > them up to speed so that new users have a good reference. > - Paschal and Barry Madore did work on improving the docs on adding > screenshots. > - Stella Power worked on JS code standards and Alan Burke worked on > CSS code standards. > - Moshe did a little Diff module mojo and created a patch for the > Drupal.org module to add a direct link to the latest diff on the > recent updates page (http://drupal.org/handbook/updates). That will > appear on the site once Killes gets a chance to deploy the updates. > - The Usability team outlined a new Usability section for the handbook > and Niels started to write it up. > - We added a bunch of people to the docs team, so welcome to all the > new team members. > - There was a ton of activity in the IRC channel that was hard for me > to keep up with since there was so much snatching me away at the > sprint, so kudos to the folks who were in the channel, especially the > ones not in Szeged but still taking part in the srpint. > - Lots and lots and lots and lots of people were cleaning up the issue > queue, rolling in comments, reviewing sections of the handbook, eating > chocolate and generally having a great time. > > Whew, that's about as much as I can spit out right now. > > Other stuff going on in docs that isn't sprint-related per se: > - I've created a read-only g.d.o group at http://groups.drupal.org/documentation-team > where we can post updates on work and announcements. This allows > people who are not on the mailing list to be apprised of things and > gives a central location for Doc team info with an RSS feed. It will > mainly be used to summarize and point to mailing list threads, > important issues in the queue and to d.o forum/front page posts. We > will also post all scheduled meetings here so you can keep track of > those too and add them to your calendar. Since it is read-only, there > are no group subscriptions available and currently myself and sepeck > have rights to add new posts. > - Just want to remind folks (and point new members) to the ongoing > discussion about opening editing to all auth users (http://lists.drupal.org/pipermail/documentation/2008-August/006191.html > ). Please provide your feedback *in that thread* by Sept. 8. > - The Getting involved handbook issues (http://drupal.org/project/issues?projects=18753&text=Contrib%20Redesign:)still > need work so we can do the reorg. Thanks to everyone that has been > chipping away at that. > > I've got a bunch more stuff to sput about but this post is already > hella long so I'll wrap up there. Really, HUGE thanks to everyone. I > am damned excited about the docs team right now and I feel like we are > kicking butt. > > Keep rockin' the docs! > Addi (add1sun) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Thu Sep 4 16:13:45 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 4 Sep 2008 12:13:45 -0400 Subject: [documentation] IRC meeting on Sept. 14 In-Reply-To: <6553B637-B4F1-407B-81ED-427A99EED43D@rocktreesky.com> References: <6553B637-B4F1-407B-81ED-427A99EED43D@rocktreesky.com> Message-ID: <2FB92256-026E-4571-88AB-A4427697745E@rocktreesky.com> OK, the Doodle is done. :-) Next IRC meeting will be on the FreeNode IRC network in #drupal-docs on Sunday, September 14 at 17:00 GMT (1 pm EDT, 10 am PDT) Feel free to post to the list with agenda items you would like covered. The main things to discuss right now: - Getting involved book - Open editing to all auth users An event post was created on the group page as well (http://groups.drupal.org/node/145700 ). See you there! On Sep 2, 2008, at 7:59 AM, Addison Berry wrote: > I am planning some time later today to do a brain dump of the Doc > sprint, which was totally awesome. I have a lot to write up and > limited time right now though. I do however want to get us > scheduling the next IRC meeting so we can keep our momentum going. > > I have set up a Doodle for Sep 11 - Sep 14: http://www.doodle.ch/7dx3823d582rxgsk > . Everyone needs to vote on the doodle by *September 4 at 18:00 > GMT*. As usual we will keep the meeting to one hour long and > determine the agenda ahead of time on the mail list. > > Addi (add1sun) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080904/0409ce08/attachment.htm From drupal at rocktreesky.com Thu Sep 4 21:34:00 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 4 Sep 2008 17:34:00 -0400 Subject: [documentation] Blog about it Message-ID: Hey all, So I put up a blog post on my thoughts about the Doc sprint we had on Sunday (http://www.lullabot.com/blog/documentation-kicking-butt). I really want to encourage everyone on the docs team to blog* about their own experiences as well. I say this for two reasons: 1) I really want to know what everyone worked on at the sprint since I missed a lot of things. It was crazy in there. :-) 2) I want the larger Drupal community to know all of the awesome stuff that we are working on. We should be tooting our horns and in the process get the word out that everyone can contribute and that there are lots of different ways to contribute and make a difference. While I personally want to see stories from the sprint just cuz I'm curious, I also plan to do more blog posts generally about my work on docs and I encourage everyone else to as well. If you don't have a blog or don't feel like making a full post right now, feel free to leave a comment on my post with your thoughts. I know that I wasn't the only one at the sprint and I'd like to hear other voices in the blogosphere. :-) * To really hit the Drupal community you should get your blog on the Drupal Planet feed (http://drupal.org/planet), if you aren't already. The Planet is an aggregator of Drupal related posts from all over the web. If you aren't "on the planet", you just need to create a Drupal- specific feed on your blog (which is easy to do by creating a term for it). I use the term "drupal", some folks use "drupal planet". Just pick a term that you will use for any posts you want to send to the planet. Then get the feed URL for that term (e.g. my personal blog one is http://www.rocktreesky.com/tags/geek/drupal/feed) and create a webmasters issue (http://drupal.org/project/issues/webmasters) asking to be added to the planet. Make sure you include the link to the feed and the name you want for your entry (some people prefer their name, others like to use the name of their site or company). - Addi (add1sun) From drupal at rocktreesky.com Sat Sep 6 15:42:19 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sat, 6 Sep 2008 11:42:19 -0400 Subject: [documentation] Documentation taxonomy? In-Reply-To: <1406bb8f0808280138q3c967c9bs3266b4d2fc86d7ec@mail.gmail.com> References: <7A448460-AD30-465A-BBE8-E1C05D887ACE@rocktreesky.com> <1406bb8f0808280138q3c967c9bs3266b4d2fc86d7ec@mail.gmail.com> Message-ID: <15B19575-2164-4D96-83FF-4007273AB522@rocktreesky.com> I, too, was originally thinking that we could form_alter the select list out for regular users but I guess depending on what we put in there it may be useful to let users flag pages as well. This wouldn't make much sense now probably but *if* we decide to open editing to regular users, it would make more sense. I still lean towards removing it but want to leave the option open if people feel strongly one way or the other. I have created an issue in the queue (http://drupal.org/node/304826) about this so we can define what terms should be in the list. Everyone, let's hammer on it and come up with a good, tight list of terms and then we can move it on to the webmasters queue for implementation. Benjamin, I've added your module to the list of modules for review for docs team use, particularly in light of the coming redesign. I'll carry that conversation itself to another thread though. Thanks for the feedback! - Addi (add1sun) On Aug 28, 2008, at 4:38 AM, Benjamin Melan?on wrote: > All for using taxonomy to flag more information about handbook pages. > If we can add this customization to drupal.org the vocabulary could be > de-emphasized with theming (or just moved down with form_alter) or > even hidden from some roles on the node add/edit page. > > (For presentation of information regarding assigned terms, an > alternative to theming is http://drupal.org/project/term_message which > was written for documentation purposes and I'd rewrite it to meet any > handbook needs.) > > benjamin > > Agaric Design Collective > Open Source Free Software Web Development > http://agaricdesign.com/ > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Sat Sep 6 15:45:34 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sat, 6 Sep 2008 11:45:34 -0400 Subject: [documentation] Proposal to open up editing rights In-Reply-To: References: Message-ID: Just a reminder to please give feedback to this thread by September 8. We've had a lot of good discussion and ideas floating around in here. On September 9, I'll summarize what we've got and we can figure out next steps, if any right now. - Addi (add1sun) On Aug 29, 2008, at 5:31 AM, Addison Berry wrote: > I'll start by apologizing for the long email here but I think this > deserves more than a few sentences. Also note that at the end I've got > a deadline for responses of Sept. 8. ;-) > > So I have a proposal to put out to the team regarding opening up > editing rights to all authenticated users on d.o. This would be a big > change and I'd like us to really hammer this out in discussion so that > we identify and address pitfalls ahead of time as well as possible. I > have long been a proponent of absolutely *not* opening this up and I > still have concerns about it, but I'd like to see what the community > would really do with it. The Drupal community is very different now > than it was several years ago, whether it is different in a way that > would make open editing successful this time remains a question. > > Before I get to it, a bit of history: > This has been done in the past and failed. Years ago all auth users > were allowed to edit the handbook and there was too much vandalism and > spam to be caught and cleaned up by the community. This is still a > concern and not one to be taken lightly. > > But there are some definite points to be looked at: > * It requires MUCH less knowledge and time to fix a typo than it does > to author a new page. Same with rolling in comments, another common > task that the docs team is stretched a bit thin on. > * New users are the best poised to ferret out errors in documentation, > but also the least likely to create new pages. > * While the barrier to joining the documentation team is low, it is a > barrier nonetheless, and one that is non-obvious to new users, whose > input we need the most. I've also found that many new people just > won't take the step to ask because they feel that it means they have a > certain time obligation that they don't feel they can "commit" to. > > Some issues we will need to look at: > * We have a mix of input formats out there and anything above Filtered > HTML needs to be restricted for security reasons. So even if we open > it up there will definitely be many pages that folks can't edit unless > they join the team, particularly pages with images. We can explain > this and make it clear what is going on but there will still be a lot > of folks that don't read wherever we happen to explain it and will > complain a lot. So we need to be ready for lots of forum posts/issues/ > irc pings about this unless someone has any other brilliant ideas > about it. ;-) We should have a standard explanation written up that we > can point people to and/or copy/paste into emails, etc. > * We are going to get vandalism, no doubt. So the trick is to see if > the community can actually self-maintain fairly well and keep up with > it. The doc team in particular will need to make an extra effort to > keep an eye on things and be as responsive as possible about reverting > things and helping clean it up. this is the kicker and if this doesn't > happen, then this fail. Any and all ideas about ways to help us track > what is happen and deal with it quickly are welcome. One thing that > comes to mind is that we do have a Recent updates page (http://drupal.org/handbook/updates > ) and it would reduce a click if the table included a link directly to > the revisions tab of the page in question so you could easily review > the list, see the revision history and get a quick diff on changes. > This would require a patch to the d.o module so I'll write up a patch > for that either Sunday or next week. > * Any other issues we are missing here? > > The idea is to try this out as a test. Here is my general plan. Help > me shore it up: > Open up general handbook page editing to authenticated users (since > they can only edit Filtered HTML nodes, the Getting Started Guide and > other more "official" resources would be off-limits) for a trial > period of one month. Publicize what the deal is, and then assess the > number of reversions needed, and decide if we will continue or close > back up. We can extend the test a month at a time until we are sure of > our decision and just keep communicating with the community about what > the progress is. Basically, the community has asked for this and I > want to see if we can really handle it. If it works, awesome, if it > doesn't then this will give us some recent experience and data to > consider when the request is raised again. > > So, let's talk about this on the mail list for a week or so and get > ourselves aligned about whether to agree to the proposal or not and > also hash out idea for how to actually deal with it. Please respond > with your thoughts to this list by September 8. > > Thanks > - Addi (add1sun) > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From andrewberry at sentex.net Sat Sep 6 19:41:19 2008 From: andrewberry at sentex.net (Andrew Berry) Date: Sat, 6 Sep 2008 15:41:19 -0400 Subject: [documentation] Proposal to open up editing rights In-Reply-To: References: Message-ID: On 6-Sep-08, at 11:45 AM, Addison Berry wrote: > Just a reminder to please give feedback to this thread by September 8. Sorry for using this thread, I just recently subscribed so I don't have a copy of the older message. I had two thoughts on this which could work together. First, how about automatically adding module authors to the documentation permissions? Those who have committed code in my mind at least are very unlikely to vandalize pages. The other thought would be to do a "time delay" for new accounts being added to the documentation team. For example, if an account is active at least once a month for six months, then automatically add the permissions, and send an email with style information and a thank-you for participating in d.org's community. Of course, this could always be overridden by a formal doc team request. One other thing - the revision log field should be made to be required. This probably requires a custom module to hook into the form, but would be very useful. --Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2692 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080906/cfc36a5f/attachment.bin From catch56 at googlemail.com Sat Sep 6 20:17:53 2008 From: catch56 at googlemail.com (Nathaniel Catchpole) Date: Sat, 6 Sep 2008 21:17:53 +0100 Subject: [documentation] Proposal to open up editing rights In-Reply-To: References: Message-ID: > > > > One other thing - the revision log field should be made to be required. > This probably requires a custom module to hook into the form, but would be > very useful. > > --Andr A big +1 to required revision logs. Would be a tiny patch to drupalorg.module and would be a bit of extra piece of mind opening things up. Nat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080906/afc844d5/attachment.htm From emmajane at xtrinsic.com Sun Sep 7 16:43:22 2008 From: emmajane at xtrinsic.com (Emma Jane Hogbin) Date: Sun, 07 Sep 2008 17:43:22 +0100 Subject: [documentation] Proposal to open up editing rights In-Reply-To: References: Message-ID: <48C404AA.1020106@xtrinsic.com> Addison Berry wrote: >> The idea is to try this out as a test. Here is my general plan. Help >> me shore it up: >> Open up general handbook page editing to authenticated users (since >> they can only edit Filtered HTML nodes, the Getting Started Guide and >> other more "official" resources would be off-limits) for a trial >> period of one month. Publicize what the deal is, and then assess the >> number of reversions needed, and decide if we will continue or close >> back up. We can extend the test a month at a time until we are sure of +1 on moving forward with this plan (and especially with a limited time to start). I would like it if there was also some kind of rating system on the pages. Something like: - "This is so good we're calling it 'Official' and locking it." - "This has been through loads of edits, vote to make it 'Official.'" - "Brand new page, edit me and make me better." Yes, it's more tedious than a straight Wiki-style set of pages. I think it would help to let people voice their opinion without having to leave a comment or edit the page. We ran into similar kinds of questions on The Linux Documentation Project when I was active a few years ago. This was the solution that was proposed at the time. Another idea was to have the ability for new authors to "lock" their pages so that they could not be community-edited (but could be edited by the core LDP team). I think that's less relevant here though. regards, emma -- Emma Jane Hogbin, B.Sc. work: www.xtrinsic.com play: www.emmajane.net learn: www.hicktech.com From vishakhatambe.mcs at gmail.com Mon Sep 8 09:49:16 2008 From: vishakhatambe.mcs at gmail.com (Vishakha Tambe) Date: Mon, 8 Sep 2008 15:19:16 +0530 Subject: [documentation] Search Module Message-ID: Hello all, Acually i a implementing search module in my site. I want some extra functionality in "Advanced Search". For example, if i want to search a particular person, but i dont know his name. Bu i know the address. So i will search him according to the address. Means i want particula fieldwise search, like citywise, countrywise, statewise etc. So how can i add that in the serch module? Regards, Vishakha. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080908/aabffaaf/attachment.htm From lee.hunter at hum.com Mon Sep 8 13:14:20 2008 From: lee.hunter at hum.com (Lee Hunter) Date: Mon, 8 Sep 2008 09:14:20 -0400 Subject: [documentation] Tag clouds and documentation Message-ID: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> John Forsythe of Blamcast has recently blogged this nice tag cloud showing the top search terms on Drupal.org for the past month http://blamcast.net/articles/top-drupal-search-terms http://blamcast.net/files/drupal-search-terms-cloud.html Wouldn't it be great if the documentation page had a similar tag cloud and each of those terms was a link to ALL the related documentation for that term? In other words, if you clicked "image" you'd see a page that has links to every piece of image-related documentation, regardless of whether it happened to be filed (i.e. hidden) under module documentation, how-to, theming, FAQ, video, developer documentation etc. No more wild goose chases checking whether there's something on images in the how-tos, or the FAQs, or the videos, or the troubleshooting etc etc etc. To me, that would be heaven. Lee Hunter Technical Editor From sepeck at gmail.com Mon Sep 8 16:24:45 2008 From: sepeck at gmail.com (Steven Peck) Date: Mon, 8 Sep 2008 09:24:45 -0700 Subject: [documentation] Tag clouds and documentation In-Reply-To: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> Message-ID: His analysis is NOT of drupal.org search terms, but of his own personal sites. On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter wrote: > John Forsythe of Blamcast has recently blogged this nice tag cloud > showing the top search terms on Drupal.org for the past month > > http://blamcast.net/articles/top-drupal-search-terms > http://blamcast.net/files/drupal-search-terms-cloud.html > > Wouldn't it be great if the documentation page had a similar tag cloud > and each of those terms was a link to ALL the related documentation > for that term? In other words, if you clicked "image" you'd see a page > that has links to every piece of image-related documentation, > regardless of whether it happened to be filed (i.e. hidden) under > module documentation, how-to, theming, FAQ, video, developer > documentation etc. > > No more wild goose chases checking whether there's something on images > in the how-tos, or the FAQs, or the videos, or the troubleshooting etc > etc etc. > > To me, that would be heaven. > > Lee Hunter > Technical Editor > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > From lee.hunter at hum.com Mon Sep 8 16:31:32 2008 From: lee.hunter at hum.com (Lee Hunter) Date: Mon, 8 Sep 2008 12:31:32 -0400 Subject: [documentation] Tag clouds and documentation In-Reply-To: References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> Message-ID: <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> Sorry, you're quite right, the cloud is from his sites.. However, it doesn't change the point of my message. The organization of the documentation is seriously fractured and a tag cloud of drupal.org searches (whatever that might be) would help a lot to bring things together. Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 12:24 PM, Steven Peck wrote: > His analysis is NOT of drupal.org search terms, but of his own personal sites. > > On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter wrote: >> John Forsythe of Blamcast has recently blogged this nice tag cloud >> showing the top search terms on Drupal.org for the past month >> >> http://blamcast.net/articles/top-drupal-search-terms >> http://blamcast.net/files/drupal-search-terms-cloud.html >> >> Wouldn't it be great if the documentation page had a similar tag cloud >> and each of those terms was a link to ALL the related documentation >> for that term? In other words, if you clicked "image" you'd see a page >> that has links to every piece of image-related documentation, >> regardless of whether it happened to be filed (i.e. hidden) under >> module documentation, how-to, theming, FAQ, video, developer >> documentation etc. >> >> No more wild goose chases checking whether there's something on images >> in the how-tos, or the FAQs, or the videos, or the troubleshooting etc >> etc etc. >> >> To me, that would be heaven. >> >> Lee Hunter >> Technical Editor >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > From skiquel at mac.com Mon Sep 8 16:55:07 2008 From: skiquel at mac.com (Tony Narlock) Date: Mon, 08 Sep 2008 11:55:07 -0500 Subject: [documentation] Tag clouds and documentation In-Reply-To: <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> Message-ID: <48C558EB.7090107@mac.com> Lee Hunter wrote: > Sorry, you're quite right, the cloud is from his sites.. > > However, it doesn't change the point of my message. The organization > of the documentation is seriously fractured and a tag cloud of > drupal.org searches (whatever that might be) would help a lot to bring > things together. > > Lee Hunter > Technical Editor > > On Mon, Sep 8, 2008 at 12:24 PM, Steven Peck wrote: > >> His analysis is NOT of drupal.org search terms, but of his own personal sites. >> >> On Mon, Sep 8, 2008 at 6:14 AM, Lee Hunter wrote: >> >>> John Forsythe of Blamcast has recently blogged this nice tag cloud >>> showing the top search terms on Drupal.org for the past month >>> >>> http://blamcast.net/articles/top-drupal-search-terms >>> http://blamcast.net/files/drupal-search-terms-cloud.html >>> >>> Wouldn't it be great if the documentation page had a similar tag cloud >>> and each of those terms was a link to ALL the related documentation >>> for that term? In other words, if you clicked "image" you'd see a page >>> that has links to every piece of image-related documentation, >>> regardless of whether it happened to be filed (i.e. hidden) under >>> module documentation, how-to, theming, FAQ, video, developer >>> documentation etc. >>> >>> No more wild goose chases checking whether there's something on images >>> in the how-tos, or the FAQs, or the videos, or the troubleshooting etc >>> etc etc. >>> >>> To me, that would be heaven. >>> >>> Lee Hunter >>> Technical Editor >>> -- >>> Pending work: http://drupal.org/project/issues/documentation/ >>> List archives: http://lists.drupal.org/pipermail/documentation/ >>> >>> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > Ideas are harmless. :) If there is something that we can do to help people get the documentation they want quicker, by all means. When designing sites, we have things like the "3 click rule". The handbook gives us a hierarchy, with stuff like tags, they can click on "handbook" and see a tag cloud on the top. It we can do it to make it look professional, it doesn't need to be big, just to give a quick link to the most common stuff. See an example here: http://bakery.cakephp.org/ If you take some time to think about what people who are looking for info on... Sometimes they may need a tag to "spark" a particular search word they may other wise not be thinking of. There are cases where you don't want tags+tag clouds, and cases where you do -- this may be a case where it's advantageous. Hope this helps Tony From lee.hunter at hum.com Mon Sep 8 17:13:39 2008 From: lee.hunter at hum.com (Lee Hunter) Date: Mon, 8 Sep 2008 13:13:39 -0400 Subject: [documentation] Tag clouds and documentation In-Reply-To: <48C558EB.7090107@mac.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> Message-ID: <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> That's an excellent example, Tony. I would imagine that the topic of connecting with databases would be one of the most popular subjects on a PHP framework site and, sure enough, "database" is the largest item in the CakePHP cloud. When I click on "database" I get all the relevant tagged articles. Contrast that with the user experience on Drupal.org. Searching for even the most common topics means that I have to either do a search (which is messy and unreliable) or I make a series of attempts to crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) that lead me into a maze of unhelpful subheadings until I finally stumble across enough information to satisfy my need (although I'll never know whether or not I've found everything on the subject) or I just collapse in exhaustion. :) Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock wrote: > See an example here: http://bakery.cakephp.org/ From sepeck at gmail.com Mon Sep 8 17:37:25 2008 From: sepeck at gmail.com (Steven Peck) Date: Mon, 8 Sep 2008 10:37:25 -0700 Subject: [documentation] Tag clouds and documentation In-Reply-To: <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> Message-ID: Other than saying 'tags will help' do you have a better hierarchy suggestion? My experience with tags in general on many other sites has been that they also pollute search results into rabbit warrens of unrelated pages. I am not against tags, just not seeing them as a magic bullet currently. I am loathe to just 'tack things on' while we have a redesign project starting up. On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter wrote: > That's an excellent example, Tony. > > I would imagine that the topic of connecting with databases would be > one of the most popular subjects on a PHP framework site and, sure > enough, "database" is the largest item in the CakePHP cloud. When I > click on "database" I get all the relevant tagged articles. > > Contrast that with the user experience on Drupal.org. Searching for > even the most common topics means that I have to either do a search > (which is messy and unreliable) or I make a series of attempts to > crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) > that lead me into a maze of unhelpful subheadings until I finally > stumble across enough information to satisfy my need (although I'll > never know whether or not I've found everything on the subject) or I > just collapse in exhaustion. > > :) > > Lee Hunter > Technical Editor > > > On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock wrote: > >> See an example here: http://bakery.cakephp.org/ > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > From lee.hunter at hum.com Mon Sep 8 17:58:46 2008 From: lee.hunter at hum.com (Lee Hunter) Date: Mon, 8 Sep 2008 13:58:46 -0400 Subject: [documentation] Tag clouds and documentation In-Reply-To: References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> Message-ID: <197f52f50809081058k521abc22te58435cad0b54f2a@mail.gmail.com> I don't think there's any way it could be worse than the utterly inscrutable architecture we have now. :) Using the Cake example, one click gets you all the database articles. On the current Drupal.org you would probably have to click *hundreds* of times (quite literally) before you rounded up everything on databases (and personally I'd get lost and give up long before I got there). The Cake example, does show one of the limitations in that you might get an overwhelming number of results, however this is still preferable to not even knowing where to start. To solve the issue of too many results, one approach I really like is the guided search or faceted search, which is used on quite a few large and complex sites. In fact, there's a module here: http://drupal.org/project/faceted_search Faceted search has several advantages, one of which is that you can see at a glance how your search could be broadened or narrowed by choosing from a list of options. Using the "database" example, there might well be too many results to be useful, but the faceted search would allow me to easily narrow it down by clicking on the "facets" or related tags (and I'd also see how many articles can be found in each related tag). Re. the redesign project, that's one reason I'm raising this issue again now, because I think it would be just tragic if the current non-architecture gets baked into the redesign. To my mind, the total lack of navigability in the documentation is by far the most pressing problem with Drupal.org. A while back, I'd actually proposed an alternative architecture for the documentation (http://drupal.org/node/199388) but I'm now thinking that some kind of organic tagging scheme would work better for this kind of site. Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck wrote: > Other than saying 'tags will help' do you have a better hierarchy suggestion? > > My experience with tags in general on many other sites has been that > they also pollute search results into rabbit warrens of unrelated > pages. I am not against tags, just not seeing them as a magic bullet > currently. I am loathe to just 'tack things on' while we have a > redesign project starting up. From drupal at rocktreesky.com Mon Sep 8 18:23:28 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 8 Sep 2008 14:23:28 -0400 Subject: [documentation] Tag clouds and documentation In-Reply-To: <197f52f50809081058k521abc22te58435cad0b54f2a@mail.gmail.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> <197f52f50809081058k521abc22te58435cad0b54f2a@mail.gmail.com> Message-ID: Yep, I agree that the way the docs are organized/categorized/found needs to change in the redesign. I'd love a flexible way for people to get to the docs they need in different ways. This is a major thing that I want us to work with Mark Boulton Design (MBD) on. I am gathering together a list of features/dream requests with regards to docs and hope to post a mail to this list by the end of the week so we can be a bit organized about brainstorming, prioritizing and giving feedback to MBD. I'm so frickin excited we have not just design, but actual IA and UX work going into the redesign. Faceted search is awesome stuff as well and I dare say that is something that the redesign search team will be looking at. Their first hurdle is to figure out how to have robust search across multiple drupal.org sites and I have no idea where something like faceted search is on their radar. Would be awesome if it makes it into the redesign, but I'll leave that to those experts. Doesn't hurt to say that docs team thinks it would be neat-o-keen, though. :-) - Addi On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote: > I don't think there's any way it could be worse than the utterly > inscrutable architecture we have now. > > :) > > Using the Cake example, one click gets you all the database articles. > On the current Drupal.org you would probably have to click *hundreds* > of times (quite literally) before you rounded up everything on > databases (and personally I'd get lost and give up long before I got > there). > > The Cake example, does show one of the limitations in that you might > get an overwhelming number of results, however this is still > preferable to not even knowing where to start. > > To solve the issue of too many results, one approach I really like is > the guided search or faceted search, which is used on quite a few > large and complex sites. In fact, there's a module here: > > http://drupal.org/project/faceted_search > > Faceted search has several advantages, one of which is that you can > see at a glance how your search could be broadened or narrowed by > choosing from a list of options. Using the "database" example, there > might well be too many results to be useful, but the faceted search > would allow me to easily narrow it down by clicking on the "facets" or > related tags (and I'd also see how many articles can be found in each > related tag). > > Re. the redesign project, that's one reason I'm raising this issue > again now, because I think it would be just tragic if the current > non-architecture gets baked into the redesign. To my mind, the total > lack of navigability in the documentation is by far the most pressing > problem with Drupal.org. > > A while back, I'd actually proposed an alternative architecture for > the documentation (http://drupal.org/node/199388) but I'm now thinking > that some kind of organic tagging scheme would work better for this > kind of site. > > Lee Hunter > Technical Editor > > > On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck wrote: >> Other than saying 'tags will help' do you have a better hierarchy >> suggestion? >> >> My experience with tags in general on many other sites has been that >> they also pollute search results into rabbit warrens of unrelated >> pages. I am not against tags, just not seeing them as a magic bullet >> currently. I am loathe to just 'tack things on' while we have a >> redesign project starting up. > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From me at alanpalazzolo.com Mon Sep 8 18:47:53 2008 From: me at alanpalazzolo.com (Alan Palazzolo) Date: Mon, 08 Sep 2008 13:47:53 -0500 Subject: [documentation] Tag clouds and documentation In-Reply-To: References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> <197f52f50809081058k521abc22te58435cad0b54f2a@mail.gmail.com> Message-ID: <48C57359.1000404@alanpalazzolo.com> My two cents on this. I would propose two structures in unison. 1) Formal tagging hierarchal structure, specific categories 2) Free tagging This allows for both ways of finding information. It creates a structure that is necessary for such a large amount of information while also giving opportunity for organic growth. -- Alan http://alanpalazzolo.com/ On 9/8/08 1:23 PM, Addison Berry wrote: > Yep, I agree that the way the docs are organized/categorized/found > needs to change in the redesign. I'd love a flexible way for people to > get to the docs they need in different ways. This is a major thing > that I want us to work with Mark Boulton Design (MBD) on. I am > gathering together a list of features/dream requests with regards to > docs and hope to post a mail to this list by the end of the week so we > can be a bit organized about brainstorming, prioritizing and giving > feedback to MBD. I'm so frickin excited we have not just design, but > actual IA and UX work going into the redesign. > > Faceted search is awesome stuff as well and I dare say that is > something that the redesign search team will be looking at. Their > first hurdle is to figure out how to have robust search across > multiple drupal.org sites and I have no idea where something like > faceted search is on their radar. Would be awesome if it makes it into > the redesign, but I'll leave that to those experts. Doesn't hurt to > say that docs team thinks it would be neat-o-keen, though. :-) > > - Addi > > On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote: > >> I don't think there's any way it could be worse than the utterly >> inscrutable architecture we have now. >> >> :) >> >> Using the Cake example, one click gets you all the database articles. >> On the current Drupal.org you would probably have to click *hundreds* >> of times (quite literally) before you rounded up everything on >> databases (and personally I'd get lost and give up long before I got >> there). >> >> The Cake example, does show one of the limitations in that you might >> get an overwhelming number of results, however this is still >> preferable to not even knowing where to start. >> >> To solve the issue of too many results, one approach I really like is >> the guided search or faceted search, which is used on quite a few >> large and complex sites. In fact, there's a module here: >> >> http://drupal.org/project/faceted_search >> >> Faceted search has several advantages, one of which is that you can >> see at a glance how your search could be broadened or narrowed by >> choosing from a list of options. Using the "database" example, there >> might well be too many results to be useful, but the faceted search >> would allow me to easily narrow it down by clicking on the "facets" or >> related tags (and I'd also see how many articles can be found in each >> related tag). >> >> Re. the redesign project, that's one reason I'm raising this issue >> again now, because I think it would be just tragic if the current >> non-architecture gets baked into the redesign. To my mind, the total >> lack of navigability in the documentation is by far the most pressing >> problem with Drupal.org. >> >> A while back, I'd actually proposed an alternative architecture for >> the documentation (http://drupal.org/node/199388) but I'm now thinking >> that some kind of organic tagging scheme would work better for this >> kind of site. >> >> Lee Hunter >> Technical Editor >> >> >> On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck wrote: >>> Other than saying 'tags will help' do you have a better hierarchy >>> suggestion? >>> >>> My experience with tags in general on many other sites has been that >>> they also pollute search results into rabbit warrens of unrelated >>> pages. I am not against tags, just not seeing them as a magic bullet >>> currently. I am loathe to just 'tack things on' while we have a >>> redesign project starting up. >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From info at 33rdprime.com Mon Sep 8 19:12:54 2008 From: info at 33rdprime.com (Patrick Teglia) Date: Mon, 8 Sep 2008 13:12:54 -0600 Subject: [documentation] Tag clouds and documentation In-Reply-To: <48C57359.1000404@alanpalazzolo.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> <197f52f50809081058k521abc22te58435cad0b54f2a@mail.gmail.com> <48C57359.1000404@alanpalazzolo.com> Message-ID: I, for one, am hoping that faceted_search shows up in the redesign. I have worked with it, and would say that it is, by far, the best way I have seen to search through copious amount of content. I am uncertain how it performs however, and I am sure that will be a concern. Also, can not Robert Douglass' Apache Solr integration work with faceted_search, giving a fairly powerful overall search? Another thing to keep in mind is that faceted_search works WITH taxonomy terms, so a mix of being able to free-tag something, and use a faceted search to retrieve it could be pretty useful. Thanks, Patrick Teglia CrashTest_ On Mon, Sep 8, 2008 at 12:47 PM, Alan Palazzolo wrote: > My two cents on this. I would propose two structures in unison. > > 1) Formal tagging hierarchal structure, specific categories > 2) Free tagging > > This allows for both ways of finding information. It creates a > structure that is necessary for such a large amount of information while > also giving opportunity for organic growth. > > -- > Alan > http://alanpalazzolo.com/ > > > > On 9/8/08 1:23 PM, Addison Berry wrote: > > Yep, I agree that the way the docs are organized/categorized/found > > needs to change in the redesign. I'd love a flexible way for people to > > get to the docs they need in different ways. This is a major thing > > that I want us to work with Mark Boulton Design (MBD) on. I am > > gathering together a list of features/dream requests with regards to > > docs and hope to post a mail to this list by the end of the week so we > > can be a bit organized about brainstorming, prioritizing and giving > > feedback to MBD. I'm so frickin excited we have not just design, but > > actual IA and UX work going into the redesign. > > > > Faceted search is awesome stuff as well and I dare say that is > > something that the redesign search team will be looking at. Their > > first hurdle is to figure out how to have robust search across > > multiple drupal.org sites and I have no idea where something like > > faceted search is on their radar. Would be awesome if it makes it into > > the redesign, but I'll leave that to those experts. Doesn't hurt to > > say that docs team thinks it would be neat-o-keen, though. :-) > > > > - Addi > > > > On Sep 8, 2008, at 1:58 PM, Lee Hunter wrote: > > > >> I don't think there's any way it could be worse than the utterly > >> inscrutable architecture we have now. > >> > >> :) > >> > >> Using the Cake example, one click gets you all the database articles. > >> On the current Drupal.org you would probably have to click *hundreds* > >> of times (quite literally) before you rounded up everything on > >> databases (and personally I'd get lost and give up long before I got > >> there). > >> > >> The Cake example, does show one of the limitations in that you might > >> get an overwhelming number of results, however this is still > >> preferable to not even knowing where to start. > >> > >> To solve the issue of too many results, one approach I really like is > >> the guided search or faceted search, which is used on quite a few > >> large and complex sites. In fact, there's a module here: > >> > >> http://drupal.org/project/faceted_search > >> > >> Faceted search has several advantages, one of which is that you can > >> see at a glance how your search could be broadened or narrowed by > >> choosing from a list of options. Using the "database" example, there > >> might well be too many results to be useful, but the faceted search > >> would allow me to easily narrow it down by clicking on the "facets" or > >> related tags (and I'd also see how many articles can be found in each > >> related tag). > >> > >> Re. the redesign project, that's one reason I'm raising this issue > >> again now, because I think it would be just tragic if the current > >> non-architecture gets baked into the redesign. To my mind, the total > >> lack of navigability in the documentation is by far the most pressing > >> problem with Drupal.org. > >> > >> A while back, I'd actually proposed an alternative architecture for > >> the documentation (http://drupal.org/node/199388) but I'm now thinking > >> that some kind of organic tagging scheme would work better for this > >> kind of site. > >> > >> Lee Hunter > >> Technical Editor > >> > >> > >> On Mon, Sep 8, 2008 at 1:37 PM, Steven Peck wrote: > >>> Other than saying 'tags will help' do you have a better hierarchy > >>> suggestion? > >>> > >>> My experience with tags in general on many other sites has been that > >>> they also pollute search results into rabbit warrens of unrelated > >>> pages. I am not against tags, just not seeing them as a magic bullet > >>> currently. I am loathe to just 'tack things on' while we have a > >>> redesign project starting up. > >> -- > >> Pending work: http://drupal.org/project/issues/documentation/ > >> List archives: http://lists.drupal.org/pipermail/documentation/ > > > > -- > > Pending work: http://drupal.org/project/issues/documentation/ > > List archives: http://lists.drupal.org/pipermail/documentation/ > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080908/63521970/attachment.htm From drupal at rocktreesky.com Mon Sep 8 19:36:13 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 8 Sep 2008 15:36:13 -0400 Subject: [documentation] KDI proposal for sprints Message-ID: Hello all, I've just submitted a proposal to the KDI group (http://groups.drupal.org/knight-drupal-initiative ), asking for funding to conduct various Drupal doc sprints around the world: http://groups.drupal.org/node/14669. I'd love everyone's feedback on this so I make sure I'm doing things that are most beneficial to the docs team (and Drupal community) as a whole. Thanks - Addi (add1sun) From purrin at binary.net Mon Sep 8 21:00:42 2008 From: purrin at binary.net (christopher calicott) Date: Mon, 8 Sep 2008 14:00:42 -0700 Subject: [documentation] Tag clouds and documentation In-Reply-To: References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> Message-ID: The thing about tags' effectiveness and search, the way I am seeing it, is that it is all tied into how well thought-out and structured your taxonomy/IA is. I'm starting work currently on an interactive travel directory site that is essentially based on the taxonomy system in Drupal. For the primary way someone navigates through a site, tags or taxonomy /can/ be a more usable experience for people. Rather than the decade+ old-school way of drilling down into a site, provided your admins understand how to effectively tag new bits of content, users can do what I refer to as "noodling" through a site, where every page they land upon is somewhere they want to be, rather than a single step on the path to arriving where they are trying to go. Free tagging can absolutely kill usability and search results, like you say. I want to be able to give users the ability to tag things and augment the meta information of pages, but I'm thinking the best way to handle this is a balanced or weighted system that measures our site editors' structured descriptions strongly, and then tempers the weight of free tagging, whether done by users or our editors. We don't want to give users' "votes" any less value, so they are weighted the same as editors' votes in the free tagging, but all of the votes are then given a lesser weight with regards to the structured taxonomy for each page that they are initially put into, because tags usually get played fast and loose, and aren't meant to be completely authoritative. Now, this is obviously the documentation list.. I just kind of joined in the discussion here, which feels slightly off-topic, except that I think Taxonomy is something that needs a lot more than simple documentation... Itneeds more of the ideas behind it and documentation of "approaches" and things... I tend to just be silent on the list because Documentation discussion at DrupalCon Boston seemed, frankly, a little "we don't do things that way around here..." and it sucks making helpful suggestions and getting shot down, so I just keep fairly quiet and edit bad grammar, et cetera, occasionally. I really would like to see people like me having a much more clear path to doing bigger edits and additions to documentation, without fear of reprisal. Having said that, if anyone has a place in mind to include some ideas/additions on this topic, please let me know and I'll get on it this week. have a good day, -=- christopher On Sep 8, 2008, at 10:37 AM, Steven Peck wrote: > Other than saying 'tags will help' do you have a better hierarchy > suggestion? > > My experience with tags in general on many other sites has been that > they also pollute search results into rabbit warrens of unrelated > pages. I am not against tags, just not seeing them as a magic bullet > currently. I am loathe to just 'tack things on' while we have a > redesign project starting up. > > On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter > wrote: >> That's an excellent example, Tony. >> >> I would imagine that the topic of connecting with databases would be >> one of the most popular subjects on a PHP framework site and, sure >> enough, "database" is the largest item in the CakePHP cloud. When I >> click on "database" I get all the relevant tagged articles. >> >> Contrast that with the user experience on Drupal.org. Searching for >> even the most common topics means that I have to either do a search >> (which is messy and unreliable) or I make a series of attempts to >> crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) >> that lead me into a maze of unhelpful subheadings until I finally >> stumble across enough information to satisfy my need (although I'll >> never know whether or not I've found everything on the subject) or I >> just collapse in exhaustion. >> >> :) >> >> Lee Hunter >> Technical Editor >> >> >> On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock >> wrote: >> >>> See an example here: http://bakery.cakephp.org/ >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ >> > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From lee.hunter at hum.com Mon Sep 8 22:41:29 2008 From: lee.hunter at hum.com (Lee Hunter) Date: Mon, 8 Sep 2008 18:41:29 -0400 Subject: [documentation] Tag clouds and documentation In-Reply-To: References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> Message-ID: <197f52f50809081541j61976c24k7687967bf6a1f4c1@mail.gmail.com> I hear what you're saying about free-tagging and the risk of things degenerating into a meaningless soup. I think the solution might be to allow free tagging but not have the tags cast in stone. As I mentioned recently on another thread, I think this is where Wikipedia got it exactly right. Anyone can add a "category" (effectively free tagging) but editors are encouraged to aggressively refactor and reword those tags wherever it makes sense. Also a page can appear in multiple hierarchies (you can discover Ronald Reagan by navigating through movie stars, shooting survivors, politicians etc.) That way, you get the world view of the individual user, which is often surprising, idiosyncratic and useful (e.g. when they propose something like "survivors of shootings") and you get the collective wisdom of the other editors that say "Great idea, but let's make the category 'shooting survivors' not 'survivors of shootings' and let's make that a sub-category of "shooting victims". Lee Hunter Technical Editor On Mon, Sep 8, 2008 at 5:00 PM, christopher calicott wrote: > The thing about tags' effectiveness and search, the way I am seeing > it, is that it is all tied into how well thought-out and structured > your taxonomy/IA is. I'm starting work currently on an interactive > travel directory site that is essentially based on the taxonomy system > in Drupal. For the primary way someone navigates through a site, > tags or taxonomy /can/ be a more usable experience for people. > Rather than the decade+ old-school way of drilling down into a site, > provided your admins understand how to effectively tag new bits of > content, users can do what I refer to as "noodling" through a site, > where every page they land upon is somewhere they want to be, rather > than a single step on the path to arriving where they are trying to go. > > Free tagging can absolutely kill usability and search results, like > you say. I want to be able to give users the ability to tag things > and augment the meta information of pages, but I'm thinking the best > way to handle this is a balanced or weighted system that measures our > site editors' structured descriptions strongly, and then tempers the > weight of free tagging, whether done by users or our editors. We > don't want to give users' "votes" any less value, so they are weighted > the same as editors' votes in the free tagging, but all of the votes > are then given a lesser weight with regards to the structured taxonomy > for each page that they are initially put into, because tags usually > get played fast and loose, and aren't meant to be completely > authoritative. > > Now, this is obviously the documentation list.. I just kind of joined > in the discussion here, which feels slightly off-topic, except that I > think Taxonomy is something that needs a lot more than simple > documentation... Itneeds more of the ideas behind it and > documentation of "approaches" and things... > > I tend to just be silent on the list because Documentation discussion > at DrupalCon Boston seemed, frankly, a little "we don't do things that > way around here..." and it sucks making helpful suggestions and > getting shot down, so I just keep fairly quiet and edit bad grammar, > et cetera, occasionally. I really would like to see people like me > having a much more clear path to doing bigger edits and additions to > documentation, without fear of reprisal. Having said that, if anyone > has a place in mind to include some ideas/additions on this topic, > please let me know and I'll get on it this week. > > have a good day, > -=- christopher > > > > > > On Sep 8, 2008, at 10:37 AM, Steven Peck wrote: > >> Other than saying 'tags will help' do you have a better hierarchy >> suggestion? >> >> My experience with tags in general on many other sites has been that >> they also pollute search results into rabbit warrens of unrelated >> pages. I am not against tags, just not seeing them as a magic bullet >> currently. I am loathe to just 'tack things on' while we have a >> redesign project starting up. >> >> On Mon, Sep 8, 2008 at 10:13 AM, Lee Hunter >> wrote: >>> That's an excellent example, Tony. >>> >>> I would imagine that the topic of connecting with databases would be >>> one of the most popular subjects on a PHP framework site and, sure >>> enough, "database" is the largest item in the CakePHP cloud. When I >>> click on "database" I get all the relevant tagged articles. >>> >>> Contrast that with the user experience on Drupal.org. Searching for >>> even the most common topics means that I have to either do a search >>> (which is messy and unreliable) or I make a series of attempts to >>> crawl down some obliquely-labeled rabbit holes (FAQ, How-to, etc.) >>> that lead me into a maze of unhelpful subheadings until I finally >>> stumble across enough information to satisfy my need (although I'll >>> never know whether or not I've found everything on the subject) or I >>> just collapse in exhaustion. >>> >>> :) >>> >>> Lee Hunter >>> Technical Editor >>> >>> >>> On Mon, Sep 8, 2008 at 12:55 PM, Tony Narlock >>> wrote: >>> >>>> See an example here: http://bakery.cakephp.org/ >>> -- >>> Pending work: http://drupal.org/project/issues/documentation/ >>> List archives: http://lists.drupal.org/pipermail/documentation/ >>> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > From sepeck at gmail.com Mon Sep 8 23:17:24 2008 From: sepeck at gmail.com (Steven Peck) Date: Mon, 8 Sep 2008 16:17:24 -0700 Subject: [documentation] commentary Message-ID: ======== QUOTE ========= I tend to just be silent on the list because Documentation discussion at DrupalCon Boston seemed, frankly, a little "we don't do things that way around here..." and it sucks making helpful suggestions and getting shot down, so I just keep fairly quiet and edit bad grammar, et cetera, occasionally. I really would like to see people like me having a much more clear path to doing bigger edits and additions to documentation, without fear of reprisal. Having said that, if anyone has a place in mind to include some ideas/additions on this topic, please let me know and I'll get on it this week. ======== END QUOTE ========= So, often there is an idea. I don't see they benefit in the provided explanation and say so, clearly and generally ask a follow up on how an issue I see would be addressed. All to often it ends in silence so I assume that the original requester could not answer my concerns so I move on. Then later, I see people complaining about 'they were shut down' so it's all my fault they don't contribute. This is more then slightly irritating. I am also DEEPLY offended that people would accuse me of being the type of person to engage in reprisals. Offended. I have NEVER done so or acted in such a manner in my entire time in this community. Everything I have done, has been open discussion in the forums or in a mailing list. I have NEVER 'retaliated' against anyone on drupal.org despite some direct attacks on me personally. Steven Peck Current Documentation Lead. From purrin at binary.net Mon Sep 8 23:53:30 2008 From: purrin at binary.net (christopher calicott) Date: Mon, 8 Sep 2008 16:53:30 -0700 Subject: [documentation] commentary In-Reply-To: References: Message-ID: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> On Sep 8, 2008, at 4:17 PM, Steven Peck wrote: > So, often there is an idea. I don't see they benefit in the provided > explanation and say so, clearly and generally ask a follow up on how > an issue I see would be addressed. All to often it ends in silence so > I assume that the original requester could not answer my concerns so I > move on. I think this is exactly what needs improvement, since you've mentioned it. I saw multiple people in that session being met with that sort of reply, and while I'm sure the intention to clarify their ideas and distill the idea/suggestion into writing down is there, it "reads" to people like this: "I guess maybe they don't think it's a good idea, basically.." Or "I guess I'm going to have to justify my idea to this guy before it can proceed.. oh well, I guess." People don't know always know what you're getting at, Steven, to be frank. I'm still not 100% clear of what it is that you, personally, would like for people to produce to satisfy your goals for Drupal documentation, but I think we need to foster a spirit of "hey the more great ideas the better" and help these new people find the right path to include that information in the docs. I just really hate to see people's spirit quashed right off the bat, and the reality is, I saw it. Drupal is at a huge point of increasing momentum. More and more world class designers are taking an interest in the platform - more people that have worked on very, very large, high profile projects with other cms's as well - people that like to get right down to work. The community can only benefit by the influx of new people and the way that they can most directly add to the community in the shortest amount of time is through the documentation team. All I am advocating is that we try to put a little better face on the way people interface most immediately with the Drupal community - that falls to us. > Then later, I see people complaining about 'they were shut down' so > it's all my fault they don't contribute. This is more then slightly > irritating. > > I am also DEEPLY offended that people would accuse me of being the > type of person to engage in reprisals. Offended. I have NEVER done > so or acted in such a manner in my entire time in this community. > Everything I have done, has been open discussion in the forums or in a > mailing list. I have NEVER 'retaliated' against anyone on drupal.org > despite some direct attacks on me personally. > > Steven Peck > Current Documentation Lead. Uhm, I had no intentions of causing a reaction like this. I hope my points can at least be heard in the spirit that they were intended, which was meant to be a helpful, well-intentioned one. We don't need to build walls for people to climb when they have a suggestion... An extended helpful hand would go so very, very far. I guess this reaction kind of illustrates my point, though. It feels very awkward when you are relatively new and you see an area you truly needs to be addressed and you totally inadvertently rub people wrong because you're trying to improve "their thing." That, honestly, can inhibit more fresh ideas from flowing into the community, and I am - along with so many other people around the world - financially invested in Drupal being the biggest, long-term success that it can be. My business depends on that, as does most people's, I'm assuming... -=- christopher From purrin at binary.net Mon Sep 8 23:55:43 2008 From: purrin at binary.net (christopher calicott) Date: Mon, 8 Sep 2008 16:55:43 -0700 Subject: [documentation] Tag clouds and documentation In-Reply-To: <197f52f50809081541j61976c24k7687967bf6a1f4c1@mail.gmail.com> References: <197f52f50809080614v36ac4cb9n360a9fa166f75a7d@mail.gmail.com> <197f52f50809080931q6931438ahd95f592d7741e105@mail.gmail.com> <48C558EB.7090107@mac.com> <197f52f50809081013i66afc44bmfbd5b17951adecd3@mail.gmail.com> <197f52f50809081541j61976c24k7687967bf6a1f4c1@mail.gmail.com> Message-ID: <81EC8BBC-B4EF-4903-8130-FA415199A0FC@binary.net> On Sep 8, 2008, at 3:41 PM, Lee Hunter wrote: > > That way, you get the world view of the individual user, which is > often surprising, idiosyncratic and useful (e.g. when they propose > something like "survivors of shootings") and you get the collective > wisdom of the other editors that say "Great idea, but let's make the > category 'shooting survivors' not 'survivors of shootings' and let's > make that a sub-category of "shooting victims". > > Lee Hunter > Technical Editor Exactly! It's impossible to predict all the ways in which someone might /need/ to find a bit of information so this allows the users to enlighten the editors and the editors to play their role of sprucing up the taxonomy slightly as they see fit (in our case, our policy is that we do some search volume research on variations of the keyword/ category in question and then choose the one most likely to get the traffic and/or searches. In some more rare cases it might make sense to use more than one synonym and then route one to the other more popular one.) -=- christopher From sepeck at gmail.com Tue Sep 9 00:34:43 2008 From: sepeck at gmail.com (Steven Peck) Date: Mon, 8 Sep 2008 17:34:43 -0700 Subject: [documentation] commentary In-Reply-To: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> Message-ID: On Mon, Sep 8, 2008 at 4:53 PM, christopher calicott wrote: > > On Sep 8, 2008, at 4:17 PM, Steven Peck wrote: >> So, often there is an idea. I don't see they benefit in the provided >> explanation and say so, clearly and generally ask a follow up on how >> an issue I see would be addressed. All to often it ends in silence so >> I assume that the original requester could not answer my concerns so I >> move on. > > > I think this is exactly what needs improvement, since you've mentioned > it. I saw multiple people in that session being met with that sort of > reply, and while I'm sure the intention to clarify their ideas and > distill the idea/suggestion into writing down is there, it "reads" to > people like this: "I guess maybe they don't think it's a good idea, > basically.." Or "I guess I'm going to have to justify my idea to > this guy before it can proceed.. oh well, I guess." This is a large project. If you are doing a few pages, then do a few pages. People do that all the time with little or no input. If you wish to engage in larger structural changes, then propose a change, garner feedback and refine until agreement. I am unsure how else you would proceed. > People don't know always know what you're getting at, Steven, to be > frank. I'm still not 100% clear of what it is that you, personally, > would like for people to produce to satisfy your goals for Drupal > documentation, but I think we need to foster a spirit of "hey the more > great ideas the better" and help these new people find the right path > to include that information in the docs. I just really hate to see > people's spirit quashed right off the bat, and the reality is, I saw it. Then ask. What goals? Get more, get better, be accessible. I do not have a mission or agenda. I have a few things I like/want in soem areas, but beyond that I am not that complicated. When in doubt ask do not assume. > Drupal is at a huge point of increasing momentum. More and more world > class designers are taking an interest in the platform - more people > that have worked on very, very large, high profile projects with other > cms's as well - people that like to get right down to work. The > community can only benefit by the influx of new people and the way > that they can most directly add to the community in the shortest > amount of time is through the documentation team. Drupal has always been at the point of gaining momentum. This is not a new thing, this is not a new experience. People can get down to work, but one does not jump in without communications. If you have a plan, propose it, seek input, refine, seek consensues and agreement. I would hope these basics are shared across many open source projects, they have certainly been so on the ones I have participated in. We have a history of this type of work as well. > All I am advocating is that we try to put a little better face on the > way people interface most immediately with the Drupal community - that > falls to us. ok. >> >> Then later, I see people complaining about 'they were shut down' so >> it's all my fault they don't contribute. This is more then slightly >> irritating. >> >> I am also DEEPLY offended that people would accuse me of being the >> type of person to engage in reprisals. Offended. I have NEVER done >> so or acted in such a manner in my entire time in this community. >> Everything I have done, has been open discussion in the forums or in a >> mailing list. I have NEVER 'retaliated' against anyone on drupal.org >> despite some direct attacks on me personally. >> >> Steven Peck >> Current Documentation Lead. > > > Uhm, I had no intentions of causing a reaction like this. I hope my > points can at least be heard in the spirit that they were intended, > which was meant to be a helpful, well-intentioned one. We don't > need to build walls for people to climb when they have a > suggestion... An extended helpful hand would go so very, very far. > I guess this reaction kind of illustrates my point, though. It feels > very awkward when you are relatively new and you see an area you truly > needs to be addressed and you totally inadvertently rub people wrong > because you're trying to improve "their thing." That, honestly, can > inhibit more fresh ideas from flowing into the community, and I am - > along with so many other people around the world - financially > invested in Drupal being the biggest, long-term success that it can > be. My business depends on that, as does most people's, I'm > assuming... > > -=- christopher Wait? I can be accused of being the type of person that would engage in reprisals and it's still my fault for being upset that someone would accuse my of such reprehensible behavior? I wasn't inadvertently rubbed the wrong way, I was accused of being a malicious person and frankly I am still upset at that and owed a public apology. Dozens of people have made changes in the handbook, some I did not agree with, most are still there today. Why? Because they thought it would help and I thought it would not do any harm to see if it did and if someone would learn something by doing it. If you thing you you can improve something, then you must engage people to 'sell' your idea. If you are unknown, then you must build credibility and trust. The only way is to participate and communicate. If you want to change something, then propose, garner feedback, refine, carry though. I am unclear how this is different then it was last year or the year before or any other collaborative effort, closed or open source. Not agreeing with someone is not 'shutting them down', it is not agreeing with them. If you still think you have a better mouse trap, then you have to carry through on why it is a better mouse trap. If the response is "we've done that before", then you must address what didn't work 'before' and why it will work now. Your points can be heard in the spirit they were offered. The public accusation against my character is yet to be addressed. Steven From nan_wich at bellsouth.net Tue Sep 9 00:35:23 2008 From: nan_wich at bellsouth.net (Nancy Wichmann) Date: Mon, 8 Sep 2008 20:35:23 -0400 Subject: [documentation] commentary In-Reply-To: Message-ID: Steven Peck wrote: > So, often there is an idea. I don't see they benefit in the provided > explanation and say so, clearly and generally ask a follow up on how > an issue I see would be addressed. Steven was one the first, if not THE first, Drupal "authority" I had contact with. We disagreed about where something should be in the handbooks. He could tell I felt very strongly about my position, so he allowed me to proceed. I think we found out I was right. But never once did he treat me poorly nor did I ever get a feeling that there were any kind of reprisals. I, for one, appreciate all the work he does on DO and am glad he's in his position. He's in a tough position and I know there is quite a bit of stress. I have never seen him overreact, IMO. I don't agree with everything that has been done, but that's okay. That is my right; that is his right. We all have opinions and are free to state them; noone needs to get upset to the point of name-calling or threats. At the end of the day, someone has to make the decisions. That's why Steven gets "paid the big bucks." ;-) Nancy -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: multipart/alternative Size: 0 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080908/d37fc21c/attachment.bin -------------- next part -------------- Internal Virus Database is out of date. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.16/1651 - Release Date: 9/4/2008 6:57 AM From purrin at binary.net Tue Sep 9 06:34:44 2008 From: purrin at binary.net (christopher calicott) Date: Mon, 8 Sep 2008 23:34:44 -0700 Subject: [documentation] commentary In-Reply-To: References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> Message-ID: <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> On Sep 8, 2008, at 5:34 PM, Steven Peck wrote: > > Drupal has always been at the point of gaining momentum. This is not > a new thing, this is not a new experience. People can get down to > work, but one does not jump in without communications. If you have a > plan, propose it, seek input, refine, seek consensues and agreement. > I would hope these basics are shared across many open source projects, > they have certainly been so on the ones I have participated in. This is a paraphrase of what you said in response to a similar comment someone made at the documentation team talk in Boston, blowing them off publicly, as well. I'm sorry if you can't see that it is different in 2008/9 than it was in 2006/7, but it is. I've been passively observing for quite awhile now, and media coverage, rate of adoption, et cetera, is accelerating. That's a fact. It's one thing to describe to people wanting to share an idea the path to adding materials, but it's entirely another to quash their helpful spirit by shooting down their observation of how timely things need to be handled and throwing up a barrage of "red tape" about process and procedure without genuinely trying to assist them, in my opinion. When a community is smaller, things can work differently than when it grows much larger, and that /is/ taking place. I'm not sure why you have such an ongoing issue with that point about growth rates. Dries himself - in his keynote in Boston - had charts and graphs and talked at some length about past CMS's and pivotal moments in their growth and their falling into disuse because of not making the right moves and responding properly to their growth at the right time... > Wait? I can be accused of being the type of person that would engage > in reprisals and it's still my fault for being upset that someone > would accuse my of such reprehensible behavior? I wasn't > inadvertently rubbed the wrong way, I was accused of being a malicious > person and frankly I am still upset at that and owed a public apology. > Dozens of people have made changes in the handbook, some I did not > agree with, most are still there today. Why? Because they thought > it would help and I thought it would not do any harm to see if it did > and if someone would learn something by doing it. ... > Your points can be heard in the spirit they were offered. The public > accusation against my character is yet to be addressed. I genuinely do not like having words put in my mouth. This is childish, blown completely out of proportion, and I'm not going to have someone dictating to me what to say and when and where to say it. I'm not apologizing for something I did not say or for something I did say that is true. I never attacked your "character" or mentioned "reprehensible behavior." That's just silly. I think you've made it pretty clear, though, that you do make issues a personal matter, Steven, and oftentimes, very quickly so. I make comments about how people might feel about certain responses to sharing ideas and somehow I'm making a public accusation against your character as a person? Unbelievable.. I don't have any interest in anything, here, other than helping the Drupal community as a whole, which I do however I can. Every time something comes up, though, and you're around, you're right there... putting your $.02 in and putting out ill vibes when I have something to say. I seriously doubt that I'm the only person who has experienced this vibe. I'll give this another shot and repost what I had originally said that apparently caused such a strong reaction: >I tend to just be silent on the list because Documentation discussion >at DrupalCon Boston seemed, frankly, a little "we don't do things that >way around here..." and it sucks making helpful suggestions and >getting shot down, so I just keep fairly quiet and edit bad grammar, >et cetera, occasionally. I really would like to see people like me >having a much more clear path to doing bigger edits and additions to >documentation, without fear of reprisal. Having said that, if anyone >has a place in mind to include some ideas/additions on this topic, >please let me know and I'll get on it this week. > >have a good day, >-=- christopher It was a legitimate concern when I wrote it. It's even more one now. Organizations improve by having people with differing points of view sharing - without fear of reprisal - and working out the differences to the best possible effect. I know that the Drupal community can do it. I just fear that this sort of attitude I'm met with here isn't the same that any other newcomers are getting. It makes things very uncomfortable, indeed. -=- christopher From zirvap at gmail.com Tue Sep 9 07:16:29 2008 From: zirvap at gmail.com (Hilde Austlid) Date: Tue, 9 Sep 2008 09:16:29 +0200 Subject: [documentation] commentary In-Reply-To: <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> Message-ID: Hi! 2008/9/9 christopher calicott : > >I really would like to see people like me > >having a much more clear path to doing bigger edits and additions to > >documentation, without fear of reprisal. I'm assuming Steven read this as something more or less like: "I, Christopher, am afraid of reprisal from the lead doc people (including/mainly/only? Steven) if I do bigger edits to the documentation." If that is what you meant, then I agree with him: an apology is in order. If that isn't what you meant, please clarify. (When I read it, my main reaction was WTF? What kind of reprisals? For some reason I now have a picture in my mind of some super-secret docs task force mailing dead rats to offenders while cackling evilly :-) If they get to wear cool uniforms (I'm picturing something Darth Vaderish in Drupal blue) I want to join!) >I really would like to see people like me >having a much more clear path to doing bigger edits and additions to >documentation Do you have any concrete suggestions for this path? Regards, Hilde (zrivap on drupal.org) From purrin at binary.net Tue Sep 9 07:43:55 2008 From: purrin at binary.net (christopher calicott) Date: Tue, 9 Sep 2008 00:43:55 -0700 Subject: [documentation] commentary In-Reply-To: References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> Message-ID: On Sep 9, 2008, at 12:16 AM, Hilde Austlid wrote: >> I really would like to see people like me >> having a much more clear path to doing bigger edits and additions to >> documentation > > Do you have any concrete suggestions for this path? > > Regards, Hilde > (zrivap on drupal.org) I do have a lot of ideas. I don't know that now is the right time to bring up any real new work. The more important point I wanted to make overall was about us considering more carefully the approach that we take to encourage newcomers to contribute - in a way that is more inviting and fostering of productivity. If someone wants to contribute, encourage them, and show them how. Really simple, really. This approach, here, in any corporation would identify a need for restructuring. -=- christopher From wolf.zirbs at gmail.com Tue Sep 9 12:26:04 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Tue, 9 Sep 2008 14:26:04 +0200 Subject: [documentation] commentary In-Reply-To: References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> Message-ID: My two "no native english" Cents! Even if it was sometimes difficult and hard for me to understand exactly, the suggestions, critics and explanation of Team Members on Drupal.org I never felt afraid of of reprisal from the lead doc people and I have to thank anybody (mostly Sepek) because i toke the time to see what a great and waste job lies on his neck. I'm just a last-joined-in Doc Member but for me is a Honor to have the chance to learn from all of you. (And not only about Drupal.) Cheers On Tue, Sep 9, 2008 at 9:43 AM, christopher calicott wrote: > > On Sep 9, 2008, at 12:16 AM, Hilde Austlid wrote: > >> I really would like to see people like me > >> having a much more clear path to doing bigger edits and additions to > >> documentation > > > > Do you have any concrete suggestions for this path? > > > > Regards, Hilde > > (zrivap on drupal.org) > > I do have a lot of ideas. I don't know that now is the right time to > bring up any real new work. The more important point I wanted to make > overall was about us considering more carefully the approach that we > take to encourage newcomers to contribute - in a way that is more > inviting and fostering of productivity. If someone wants to > contribute, encourage them, and show them how. Really simple, > really. This approach, here, in any corporation would identify a need > for restructuring. > > -=- christopher > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080909/1dc7f316/attachment.htm From Greg at GrowingVentureSolutions.com Tue Sep 9 13:23:06 2008 From: Greg at GrowingVentureSolutions.com (Greg Knaddison - GVS) Date: Tue, 9 Sep 2008 07:23:06 -0600 Subject: [documentation] commentary In-Reply-To: <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> Message-ID: <3861c6770809090623r11d2092h5429715b0b7a9862@mail.gmail.com> On Tue, Sep 9, 2008 at 12:34 AM, christopher calicott wrote: > > On Sep 8, 2008, at 5:34 PM, Steven Peck wrote: >> >> Drupal has always been at the point of gaining momentum. This is not >> a new thing, this is not a new experience. People can get down to >> work, but one does not jump in without communications. If you have a >> plan, propose it, seek input, refine, seek consensues and agreement. >> I would hope these basics are shared across many open source projects, >> they have certainly been so on the ones I have participated in. > > > This is a paraphrase of what you said in response to a similar comment > someone made at the documentation team talk in Boston, blowing them > off publicly, as well. I'm sorry if you can't see that it is > different in 2008/9 than it was in 2006/7, but it is. I've been > passively observing for quite awhile now, and media coverage, rate of > adoption, et cetera, is accelerating. That's a fact. Actually there are some signs that the project is losing momentum. They conflict with other signs, but there is a reason that Dries has been mentioning the importance of maintaining and improving momentum is so that we don't lose what we've got. Steven's point, and I agree with him, is that the argument "Drupal is different _now_ so we have to do things different now" or "Drupal is really gaining momentum and this one thing will kill that momentum" is a pretty weak argument unless you have some data to prove it. The only argument for or against a change is "this will help Drupal" and most people agree with that simple goal - it's the implementation details where we disagree. > It's one thing > to describe to people wanting to share an idea the path to adding > materials, but it's entirely another to quash their helpful spirit by > shooting down their observation of how timely things need to be > handled and throwing up a barrage of "red tape" about process and > procedure without genuinely trying to assist them, in my opinion. I've never seen Steven do this. I've always seen him say "oh, you want to help with docs? great, I've immediately given you the role which gives you permission to make changes. If you've got a bigger change then let's discuss before you do it." If the discussions left you feeling like nobody liked your idea or you weren't able to garner the necessary support, then either the idea or the means of garnering support were faulty. But falsely blaming someone else for that failure is not a successful way to interact with a community. > When a community is smaller, things can work differently than when it > grows much larger, and that /is/ taking place. I'm not sure why you > have such an ongoing issue with that point about growth rates. Dries > himself - in his keynote in Boston - had charts and graphs and talked > at some length about past CMS's and pivotal moments in their growth > and their falling into disuse because of not making the right moves > and responding properly to their growth at the right time... This is all very true, but...what makes you so sure that your idea is the right idea at the right point? > I genuinely do not like having words put in my mouth. This is > childish, blown completely out of proportion, and I'm not going to > have someone dictating to me what to say and when and where to say > it. I'm not apologizing for something I did not say or for something > I did say that is true. I never attacked your "character" or > mentioned "reprehensible behavior." That's just silly. I think > you've made it pretty clear, though, that you do make issues a > personal matter, Steven, and oftentimes, very quickly so. I make > comments about how people might feel about certain responses to > sharing ideas and somehow I'm making a public accusation against your > character as a person? Unbelievable.. You said that you have a fear of reprisals. Either substantiate where that fear comes from or it is slanderous libel. Maybe Steven has reacted more strongly about that point than you would have, but he obviously takes his reputation very seriously and I don't blame him. Also, you can't say that Steven "makes issues a personal matter" when you started this. You made it a personal matter - he responded. > I don't have any interest in anything, here, other than helping the > Drupal community as a whole, which I do however I can. Great! That's the same goal that we all have. We just see different ways to help the project. > Every time > something comes up, though, and you're around, you're right there... > putting your $.02 in and putting out ill vibes when I have something > to say. I seriously doubt that I'm the only person who has > experienced this vibe. > > > I'll give this another shot and repost what I had originally said that > apparently caused such a strong reaction: > > >I tend to just be silent on the list because Documentation discussion > >at DrupalCon Boston seemed, frankly, a little "we don't do things that > >way around here..." and it sucks making helpful suggestions and > >getting shot down, so I just keep fairly quiet and edit bad grammar, > >et cetera, occasionally. I really would like to see people like me > >having a much more clear path to doing bigger edits and additions to > >documentation, without fear of reprisal. Having said that, if anyone > >has a place in mind to include some ideas/additions on this topic, > >please let me know and I'll get on it this week. > > > >have a good day, > >-=- christopher > > It was a legitimate concern when I wrote it. It's even more one now. > Organizations improve by having people with differing points of view > sharing - without fear of reprisal - and working out the differences > to the best possible effect. I know that the Drupal community can do > it. I just fear that this sort of attitude I'm met with here isn't > the same that any other newcomers are getting. It makes things very > uncomfortable, indeed. > So, you reiterated your claim without any more proof of it. Why? Criticism of an idea is not reprisal. Reprisal is actively blocking an account or defaming a person on a mailing list with hundreds of people... What we are having in this thread and in the other threads I have seen is frank discussion about the merits of different ideas. Your claim is that people don't contribute major changes to the docs because they fear reprisals. You've since refined that to something like "Steven responds quickly and his messages include an ill vibe." Steven (and others) are disagreeing with your claim, providing counter evidence, and asking for a clarification or retraction. There are people who tend to be encouraging with every piece of feedback and others who see that as sugarcoating of criticism and are insulted by it and refuse to do it themselves - I even use both methods depending on who I'm interacting with. Learning to successfully deal with all those different personalities is part of the challenge and fun of working in Open Source. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com | 303-800-5623 Growing Venture Solutions, LLC | http://growingventuresolutions.com From robloach at gmail.com Tue Sep 9 16:55:27 2008 From: robloach at gmail.com (Rob Loach) Date: Tue, 09 Sep 2008 12:55:27 -0400 Subject: [documentation] Search Module In-Reply-To: References: Message-ID: <48C6AA7F.4030503@gmail.com> Hi, You already seem to know more then me about the search stuff! Take a look at the project module and see how it adds the advanced search stuff for issues. Thanks a lot and sorry for not being much help, -- Rob Loach http://www.robloach.net Vishakha Tambe wrote: > Hello all, > Acually i a implementing search module in my site. I want > some extra functionality in "Advanced Search". > For example, if i want to search a particular person, but i > dont know his name. Bu i know the address. So i will search him > according to the address. > Means i want particula fieldwise search, like citywise, > countrywise, statewise etc. > So how can i add that in the serch module? > > Regards, > Vishakha. > ------------------------------------------------------------------------ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From ronaldmulero at drupal.org Tue Sep 9 21:13:38 2008 From: ronaldmulero at drupal.org (Ronald Mulero) Date: Tue, 09 Sep 2008 16:13:38 -0500 Subject: [documentation] commentary Message-ID: christopher calicott wrote: > > ... > > The more important point I wanted to make > > overall was about us considering more carefully the approach that we > > take to encourage newcomers to contribute - in a way that is more > > inviting and fostering of productivity. If someone wants to > > contribute, encourage them, and show them how. Really simple, > > really. This approach, here, in any corporation would identify a need > > for restructuring. > > > > -=- christopher > > +1 christopher :) Yes. I agree. Our approach to newbies needs a little more social polish. It isn't completely broken, nor is it any one person's or small group of people's fault. There is neither blame nor hidden insult here, just some healthy organizational criticism that needs to be addressed every now and then. Everyone remember webchick's first interaction with #drupal? http://drupal.org/webchick-wins-best-contributor-open-source-awards I doubt she was the last newb to feel that way--whether warranted or not. We are all fortunate that she came out from under that blanket. :) So, anyone know of any specific techniques that we can all apply to foster a more inclusive social environment for drupal newbs? Maybe it'd be worthwhile to collect them all and post them under a new subheading at: http://drupal.org/contribute/support Ron From purrin at binary.net Tue Sep 9 22:09:30 2008 From: purrin at binary.net (christopher calicott) Date: Tue, 9 Sep 2008 15:09:30 -0700 Subject: [documentation] commentary In-Reply-To: <3861c6770809090623r11d2092h5429715b0b7a9862@mail.gmail.com> References: <60A4A5EE-8F42-4A3A-A102-F0830BE7841D@binary.net> <093611C9-D33A-4E87-B74D-E05E308F4140@binary.net> <3861c6770809090623r11d2092h5429715b0b7a9862@mail.gmail.com> Message-ID: <854EBBD2-E1F9-4217-A928-2FEE586C3A63@binary.net> On Sep 9, 2008, at 6:23 AM, Greg Knaddison - GVS wrote: > > Beyond this I'm not having anything further to say: I'm not going to be forced into some corner by a very few people and made to felt humiliated because I mentioned something that has happened both to me in the past and to a couple of other people that I have personally observed, and the mere passing, non-specific suggestion that we try to improve our attitudes with these people incites a flame war response at my expense. I've never "slanderously libeled" anyone. That's an asinine statement. If a simple criticism of the spirit in which new people are occasionally dealt with by someone(s) in something of a leadership position can not be handled with a little more grace than this ugly situation, then it only illustrates the problem I alluded to. -=- christopher From drupal at rocktreesky.com Tue Sep 9 22:26:53 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Tue, 9 Sep 2008 18:26:53 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: References: Message-ID: I wanted to summarize the discussion around the proposal to open editing rights to all authenticated users. There were a lot of ideas that came up (and not all are in this summary because they may have veered off the target topic. Don't fear they are still being compiled, just not on this topic. :-)) So, the proposal as originally put forth: Open up general handbook page editing to authenticated users for a trial period of one month. Publicize what the deal is, and then assess the number of reversions needed, and decide if we will continue or close back up. We can extend the test a month at a time until we are sure of our decision and just keep communicating with the community about what the progress is. There were two overall sentiments in reaction to the proposal. If I can be broad for a moment, we basically had one reaction of "Yes, let's give it a whirl." and a second reaction of "Maybe, if we can "control" it somewhat." I got the overall feeling that those who responded were generally in favor of exploring it, though with some with hesitation. Here are some ideas that were put forth in terms of people's reservations/ways to make it a more successful run: "a mechanism to keep an eye on the diffs" We do have the Recent updates page at http://drupal.org/handbook/ updates and thanks to Moshe there is a patch to add a direct link to a page's diff from that table (http://drupal.org/node/304667). "adding some verbiage about the style guide and anything else that would be helpful in the node form for book pages" We can definitely add something using hook_form_alter or a theme override. We would need to provide the patch for infra to apply, so anyone willing to pop up and take that on, would be appreciated. Related (in a hook_form_alter kind of way): Making revision logs required. Again, we should be able to add a simple validation rule to the drupalorg.module. We just need someone with a little bit of time to make a patch. There was also a feeling from quite a few of wanting to have some sort of "speed bumps" built in to the process. One suggestion was to have even more restrictive access to the current doc team rights. Though I got the feeling most did not agree with that direction. Some suggestions put forth for regular authenticated users being "moderated" or otherwise not directly given access were: - revision moderation where edits could be made but the edits needed to be approved by the doc team before going "live" - "assigning each doc team member a manageable number of random handbook pages to "adopt for life" and monitor for spam/vandalism." the "owner (or owners?) would then be notified when chnages are made to their pages. - a "time delay" for new accounts. So that new auth users would have to wait a certain period prior to gaining creat/edit rights. We could also institute a rating/flagging system on the pages. Something like: - "This is so good we're calling it 'Official' and locking it." - "This has been through loads of edits, vote to make it 'Official.'" - "Brand new page, edit me and make me better." Another suggestion for fast-tracking certain users, if speed bumps are in place, is to "automatically add module authors to the documentation permissions." There are a lot of ideas here and the thing is we need to decide is if instituting these restrictions is necessary in order to proceed. It isn't just a matter of how we feel about open access, but all of these "more restrictive" suggestions/enhancements will require signicificant coding and working with infrastructure to get them into place. that is, it won't happen any time soon and definitely won't happen with some real elbow grease. These go well beyond a few lines of hook_form_alter. The current infrastructure is not set up to do these kinds of things. I'm not saying they can't happen ever, but simply that they can't happen now and we would need to dedicate ourselves to underlying grunt work to get any of these systems in place. Regardless of "speed bumps" or not, we also touched upon the notion (also in the original proposal) that there will be restricted access to certain sections of the handbooks. The getting started guide is a primary target for this, although the Them guide was also raised as a candidate. I think this topic bears a touch of thought to have a clear list of "restricted areas" before we open editing. So, with all of that here is what I see as the next steps: 1) I think any way we go that the two modifications to the node edit form suggested should be implemented. These two can be opened as issues on the infra queue and patches need to be rolled: --- Make revision logs mandatory. --- Add additional "help text" on the book node add/edit screen. 2) We should also identify which areas of the handbook will be considered "restricted" (e.g. the Getting started guide) 3) Decide if we wish to proceed without "speed bumps" for the one month trial period or wait until we determine which to pursue AND get them implemented on d.o. My personal feeling is that we give it a try for the trial period and if things seem too chaotic, close it up and then pursue the more restrictive options. We can leave item #3 open for discussion the rest of this week and make a final decision on Sunday, Sept. 14. Feel free to argue back and forth all you want but also please give your clear vote for or against the original proposal as it stands (open editing to all auth users) before Sunday. We will tally responses from the mail list and those present at the IRC meeting on Sunday for a final decision by the team. - Addi (add1sun) On Aug 29, 2008, at 5:31 AM, Addison Berry wrote: > I'll start by apologizing for the long email here but I think this > deserves more than a few sentences. Also note that at the end I've got > a deadline for responses of Sept. 8. ;-) > > So I have a proposal to put out to the team regarding opening up > editing rights to all authenticated users on d.o. This would be a big > change and I'd like us to really hammer this out in discussion so that > we identify and address pitfalls ahead of time as well as possible. I > have long been a proponent of absolutely *not* opening this up and I > still have concerns about it, but I'd like to see what the community > would really do with it. The Drupal community is very different now > than it was several years ago, whether it is different in a way that > would make open editing successful this time remains a question. > > Before I get to it, a bit of history: > This has been done in the past and failed. Years ago all auth users > were allowed to edit the handbook and there was too much vandalism and > spam to be caught and cleaned up by the community. This is still a > concern and not one to be taken lightly. > > But there are some definite points to be looked at: > * It requires MUCH less knowledge and time to fix a typo than it does > to author a new page. Same with rolling in comments, another common > task that the docs team is stretched a bit thin on. > * New users are the best poised to ferret out errors in documentation, > but also the least likely to create new pages. > * While the barrier to joining the documentation team is low, it is a > barrier nonetheless, and one that is non-obvious to new users, whose > input we need the most. I've also found that many new people just > won't take the step to ask because they feel that it means they have a > certain time obligation that they don't feel they can "commit" to. > > Some issues we will need to look at: > * We have a mix of input formats out there and anything above Filtered > HTML needs to be restricted for security reasons. So even if we open > it up there will definitely be many pages that folks can't edit unless > they join the team, particularly pages with images. We can explain > this and make it clear what is going on but there will still be a lot > of folks that don't read wherever we happen to explain it and will > complain a lot. So we need to be ready for lots of forum posts/issues/ > irc pings about this unless someone has any other brilliant ideas > about it. ;-) We should have a standard explanation written up that we > can point people to and/or copy/paste into emails, etc. > * We are going to get vandalism, no doubt. So the trick is to see if > the community can actually self-maintain fairly well and keep up with > it. The doc team in particular will need to make an extra effort to > keep an eye on things and be as responsive as possible about reverting > things and helping clean it up. this is the kicker and if this doesn't > happen, then this fail. Any and all ideas about ways to help us track > what is happen and deal with it quickly are welcome. One thing that > comes to mind is that we do have a Recent updates page (http://drupal.org/handbook/updates > ) and it would reduce a click if the table included a link directly to > the revisions tab of the page in question so you could easily review > the list, see the revision history and get a quick diff on changes. > This would require a patch to the d.o module so I'll write up a patch > for that either Sunday or next week. > * Any other issues we are missing here? > > The idea is to try this out as a test. Here is my general plan. Help > me shore it up: > Open up general handbook page editing to authenticated users (since > they can only edit Filtered HTML nodes, the Getting Started Guide and > other more "official" resources would be off-limits) for a trial > period of one month. Publicize what the deal is, and then assess the > number of reversions needed, and decide if we will continue or close > back up. We can extend the test a month at a time until we are sure of > our decision and just keep communicating with the community about what > the progress is. Basically, the community has asked for this and I > want to see if we can really handle it. If it works, awesome, if it > doesn't then this will give us some recent experience and data to > consider when the request is raised again. > > So, let's talk about this on the mail list for a week or so and get > ourselves aligned about whether to agree to the proposal or not and > also hash out idea for how to actually deal with it. Please respond > with your thoughts to this list by September 8. > > Thanks > - Addi (add1sun) > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From larry at garfieldtech.com Wed Sep 10 04:40:33 2008 From: larry at garfieldtech.com (Larry Garfield) Date: Tue, 9 Sep 2008 23:40:33 -0500 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: References: Message-ID: <200809092340.33936.larry@garfieldtech.com> On Tuesday 09 September 2008 5:26:53 pm Addison Berry wrote: > I wanted to summarize the discussion around the proposal to open > editing rights to all authenticated users. There were a lot of ideas > that came up (and not all are in this summary because they may have > veered off the target topic. Don't fear they are still being compiled, > just not on this topic. :-)) > > So, the proposal as originally put forth: > Related (in a hook_form_alter kind of way): Making revision logs > required. Again, we should be able to add a simple validation rule to > the drupalorg.module. We just need someone with a little bit of time > to make a patch. Even if we don't end up opening edit rights more widely, this is a good thing. I keep forgetting to fill in revision info even when I should do so, so having the system poke me about it would be appreciated. :-) > Regardless of "speed bumps" or not, we also touched upon the notion > (also in the original proposal) that there will be restricted access > to certain sections of the handbooks. The getting started guide is a > primary target for this, although the Them guide was also raised as a > candidate. I think this topic bears a touch of thought to have a clear > list of "restricted areas" before we open editing. I'd mentally divide the handbooks into 3 general conceptual areas: 1) A person's first few days in Drupal. 2) Reference material for specific systems or modules. (Views API, D6 Menu API, D6 theming guide, etc.) 3) Other. #1 I'd say should be restricted. The "first impression" is something we want to be very careful with, and I have no doubt the language there will be heavily influenced by the redesign process. That should not be opened globally. #3 is, I think, the easy "yes" for opening up globally, if anything is. That's the wiki-esque parts of the handbook, where wide-edit ability makes sense. #2 is up for debate. Ideally, those docs would be written by the people who wrote that API and actively maintained by them, so we don't want just anyone adding incorrect information. In practice, we know that doesn't always happen so we may or may not want to allow anyone to tweak the menu API docs, for instance. Perhaps those can either have a dedicated "owner" or be public, case-by-case? (Eg, we have a "maintainer" for the theming API docs so that's not open, but menu isn't be actively watched by chx and pwolanin so that's open to all, as a possible example.) -- Larry Garfield larry at garfieldtech.com From djun.kim at cielosystems.com Wed Sep 10 05:55:59 2008 From: djun.kim at cielosystems.com (Djun Kim) Date: Tue, 9 Sep 2008 22:55:59 -0700 Subject: [documentation] Search Module In-Reply-To: <48C6AA7F.4030503@gmail.com> References: <48C6AA7F.4030503@gmail.com> Message-ID: <839974FF-61CF-4BC6-A1B6-E1A91A1478FC@raincitystudios.com> I think that this documentation list is probably not the right place to have a discussion about implementation questions. But, you probably want to have a look at something like ApacheSolr module - this will give you all of the capabilities you want. Cheers, Djun On 9-Sep-08, at 9:55 AM, Rob Loach wrote: > Hi, > > You already seem to know more then me about the search stuff! Take a > look at the project module and see how it adds the advanced search > stuff > for issues. > > Thanks a lot and sorry for not being much help, > > -- > Rob Loach > http://www.robloach.net > > > > Vishakha Tambe wrote: >> Hello all, >> Acually i a implementing search module in my site. I want >> some extra functionality in "Advanced Search". >> For example, if i want to search a particular person, but i >> dont know his name. Bu i know the address. So i will search him >> according to the address. >> Means i want particula fieldwise search, like citywise, >> countrywise, statewise etc. >> So how can i add that in the serch module? >> >> Regards, >> Vishakha. >> ------------------------------------------------------------------------ >> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From vishakhatambe.mcs at gmail.com Wed Sep 10 06:36:32 2008 From: vishakhatambe.mcs at gmail.com (Vishakha Tambe) Date: Wed, 10 Sep 2008 12:06:32 +0530 Subject: [documentation] Search Module Message-ID: Hello all, Sorry for the inconvenience. And thanx a lot for all your help. Regards, Vishakha. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080910/c4730609/attachment.htm From vishakhatambe.mcs at gmail.com Wed Sep 10 08:09:23 2008 From: vishakhatambe.mcs at gmail.com (Vishakha Tambe) Date: Wed, 10 Sep 2008 13:39:23 +0530 Subject: [documentation] Search module Message-ID: Hello all, And sorry once again for asking implementation question on Documentation mailing list. Actually i've downloaded Apache Solr module but i am not getting how to use it. So can anybody give me proper documentation? Regards, Vishakha. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080910/9a1c93cd/attachment.htm From andrewberry at sentex.net Wed Sep 10 18:34:52 2008 From: andrewberry at sentex.net (Andrew Berry) Date: Wed, 10 Sep 2008 14:34:52 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: <200809092340.33936.larry@garfieldtech.com> References: <200809092340.33936.larry@garfieldtech.com> Message-ID: <7CAE3A58-9274-4AA0-B8D2-8C2D3EC9E4A0@sentex.net> On 10-Sep-08, at 12:40 AM, Larry Garfield wrote: >> Related (in a hook_form_alter kind of way): Making revision logs >> required. Again, we should be able to add a simple validation rule to >> the drupalorg.module. We just need someone with a little bit of time >> to make a patch. > > Even if we don't end up opening edit rights more widely, this is a > good thing. > I keep forgetting to fill in revision info even when I should do so, > so > having the system poke me about it would be appreciated. :-) Actually, this would probably be a good feature to add to the workflow section in Drupal core. I know I have quite a few sites that could use that feature. Making revision logs required would be a nice feature for D7. I don't see an open issue for it, but doing it both ways (through form_alter and a patch) should be pretty easy. If I can find the time I'll take a look at it. --Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2692 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080910/6d5bf8f2/attachment.bin From andrewberry at sentex.net Wed Sep 10 18:40:34 2008 From: andrewberry at sentex.net (Andrew Berry) Date: Wed, 10 Sep 2008 14:40:34 -0400 Subject: [documentation] Search module In-Reply-To: References: Message-ID: On 10-Sep-08, at 4:09 AM, Vishakha Tambe wrote: > Hello all, > And sorry once again for asking implementation question on > Documentation mailing list. > Actually i've downloaded Apache Solr module but i am not getting > how to use it. > So can anybody give me proper documentation? There are pretty reasonable instructions on the module page, though I imagine you've gone through them: http://drupal.org/project/apachesolr If they don't help, follow up by filing a support request in the module's issue queue (http://drupal.org/project/issues/apachesolr), or asking in #drupal-support on the freenode IRC network (http://drupal.org/irc ). --Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2692 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080910/4ced7185/attachment.bin From drupal-docs at webchick.net Wed Sep 10 18:49:43 2008 From: drupal-docs at webchick.net (Angela Byron) Date: Wed, 10 Sep 2008 14:49:43 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: <7CAE3A58-9274-4AA0-B8D2-8C2D3EC9E4A0@sentex.net> References: <200809092340.33936.larry@garfieldtech.com> <7CAE3A58-9274-4AA0-B8D2-8C2D3EC9E4A0@sentex.net> Message-ID: <48C816C7.8090709@webchick.net> Andrew Berry wrote: > On 10-Sep-08, at 12:40 AM, Larry Garfield wrote: > >>> Related (in a hook_form_alter kind of way): Making revision logs >>> required. Again, we should be able to add a simple validation rule to >>> the drupalorg.module. We just need someone with a little bit of time >>> to make a patch. >> >> Even if we don't end up opening edit rights more widely, this is a >> good thing. >> I keep forgetting to fill in revision info even when I should do so, so >> having the system poke me about it would be appreciated. :-) > > Actually, this would probably be a good feature to add to the workflow > section in Drupal core. I know I have quite a few sites that could use > that feature. Making revision logs required would be a nice feature for > D7. I don't see an open issue for it, but doing it both ways (through > form_alter and a patch) should be pretty easy. If I can find the time > I'll take a look at it. Just a quick note that I would gladly accept such a patch into D7. :) -Angie From emmajane at xtrinsic.com Wed Sep 10 19:14:11 2008 From: emmajane at xtrinsic.com (Emma Jane Hogbin) Date: Wed, 10 Sep 2008 15:14:11 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: References: Message-ID: <48C81C83.2040703@xtrinsic.com> Addison Berry wrote: > My personal feeling is that we give it a try for the trial period and > if things seem too chaotic, close it up and then pursue the more > restrictive options. We can leave item #3 open for discussion the rest +1. In my own words I think this means: allow d.o users to edit the lowest-access pages and/or the lowest-context pages for the trial period of one month. "Restrict" editing access to the high profile pages such as the handbook (and theme guide) for now. There are bells and whistles I'd like to see implemented, but I'd also like to see how the masses deal with individual, contributed pages that don't really fit "well" right now. Will they expand the content, will they re-write the pages to make them better? Will they be inspired to write new pages to fill in the blanks? WHO KNOWS! Let's give the community the benefit of the doubt on the pages we think could use the most TLC and see what kinds of awesome they come up with. :) regards, emma -- Emma Jane Hogbin, B.Sc. Founder, xtrinsic phone: (519) 371-2665 web: www.xtrinsic.com From sepeck at gmail.com Wed Sep 10 20:52:32 2008 From: sepeck at gmail.com (Steven Peck) Date: Wed, 10 Sep 2008 13:52:32 -0700 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: <48C81C83.2040703@xtrinsic.com> References: <48C81C83.2040703@xtrinsic.com> Message-ID: It's not 'lowest access' or 'lowest context' pages. It's all that do not use Full HTML filter, which is most of them ( I think over a thousand pages). We have better tools now then the last time this was tried so it will be interesting to see the results. On Wed, Sep 10, 2008 at 12:14 PM, Emma Jane Hogbin wrote: > Addison Berry wrote: >> My personal feeling is that we give it a try for the trial period and >> if things seem too chaotic, close it up and then pursue the more >> restrictive options. We can leave item #3 open for discussion the rest > > +1. > > In my own words I think this means: allow d.o users to edit the > lowest-access pages and/or the lowest-context pages for the trial period > of one month. "Restrict" editing access to the high profile pages such > as the handbook (and theme guide) for now. > > There are bells and whistles I'd like to see implemented, but I'd also > like to see how the masses deal with individual, contributed pages that > don't really fit "well" right now. Will they expand the content, will > they re-write the pages to make them better? Will they be inspired to > write new pages to fill in the blanks? WHO KNOWS! Let's give the > community the benefit of the doubt on the pages we think could use the > most TLC and see what kinds of awesome they come up with. :) > > regards, > emma > > -- > Emma Jane Hogbin, B.Sc. > Founder, xtrinsic > phone: (519) 371-2665 > web: www.xtrinsic.com > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > From vishakhatambe.mcs at gmail.com Thu Sep 11 09:29:33 2008 From: vishakhatambe.mcs at gmail.com (Vishakha Tambe) Date: Thu, 11 Sep 2008 14:59:33 +0530 Subject: [documentation] Chat Module Message-ID: Hello all, Is there any module for chatting? I just want one way communication like Administrator ------> User. I've tried searching on google bt not getting proper module. Regards, Vishakha. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080911/f3346e13/attachment.htm From wolf.zirbs at gmail.com Thu Sep 11 10:20:14 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Thu, 11 Sep 2008 12:20:14 +0200 Subject: [documentation] Chat Module In-Reply-To: References: Message-ID: Hi, http://drupal.org/project/chatroom the project is under dev to port to D6 take a look also here http://groups.drupal.org/node/5036 cheers On Thu, Sep 11, 2008 at 11:29 AM, Vishakha Tambe < vishakhatambe.mcs at gmail.com> wrote: > Hello all, > Is there any module for chatting? I just want one way communication > like Administrator ------> User. I've tried searching on google bt not > getting proper module. > > Regards, > Vishakha. > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080911/afc4a182/attachment.htm From hdeelstra at gmail.com Thu Sep 11 11:07:26 2008 From: hdeelstra at gmail.com (Heine Deelstra) Date: Thu, 11 Sep 2008 13:07:26 +0200 Subject: [documentation] Chat Module In-Reply-To: References: Message-ID: <2b508f910809110407w1fca883ubcc9c38e8ca2110b@mail.gmail.com> Please do not use the documentation mailing list for support requests. Use the support mailing list instead (http://lists.drupal.org/listinfo/support). http://drupal.org/support lists all the options you have. Regards, Heine Deelstra From wolf.zirbs at gmail.com Thu Sep 11 12:29:45 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Thu, 11 Sep 2008 14:29:45 +0200 Subject: [documentation] Chat Module In-Reply-To: <2b508f910809110407w1fca883ubcc9c38e8ca2110b@mail.gmail.com> References: <2b508f910809110407w1fca883ubcc9c38e8ca2110b@mail.gmail.com> Message-ID: Hi, sorry, newbie, how do I re-root people that sen support request throughout "Documentation" ? On Thu, Sep 11, 2008 at 1:07 PM, Heine Deelstra wrote: > Please do not use the documentation mailing list for support requests. > > Use the support mailing list instead ( > http://lists.drupal.org/listinfo/support). > > http://drupal.org/support lists all the options you have. > > Regards, > > Heine Deelstra > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080911/3e0f254f/attachment.htm From drupal at rocktreesky.com Thu Sep 11 12:31:22 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 11 Sep 2008 08:31:22 -0400 Subject: [documentation] Chat Module In-Reply-To: References: <2b508f910809110407w1fca883ubcc9c38e8ca2110b@mail.gmail.com> Message-ID: On Sep 11, 2008, at 8:29 AM, Wolf Zirbs wrote: > Hi, sorry, newbie, how do I re-root people that sen support request > throughout "Documentation" ? > The same way that Heine just did. :-) > > On Thu, Sep 11, 2008 at 1:07 PM, Heine Deelstra > wrote: > Please do not use the documentation mailing list for support requests. > > Use the support mailing list instead (http://lists.drupal.org/listinfo/support > ). > > http://drupal.org/support lists all the options you have. > > Regards, > > Heine Deelstra > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > > > > -- > Sincerely Best Regards > Wolf J. Zirbs > > P.S. > You may contact me by Mobil - Handy > between 10am and 10pm Vienna Local Time (+43 676 9286735) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080911/f85bddbb/attachment.htm From drupal at rocktreesky.com Fri Sep 12 18:18:01 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Fri, 12 Sep 2008 14:18:01 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: References: Message-ID: <753D89AA-A7F6-44AD-A171-9CB26CCED217@rocktreesky.com> Snipped up: On Sep 9, 2008, at 6:26 PM, Addison Berry wrote: > There were two overall sentiments in reaction to the proposal. If I > can be broad for a moment, we basically had one reaction of "Yes, > let's give it a whirl." and a second reaction of "Maybe, if we can > "control" it somewhat." > > There was also a feeling from quite a few of wanting to have some sort > of "speed bumps" built in to the process. > > - a "time delay" for new accounts. So that new auth users would have > to wait a certain period prior to gaining creat/edit rights. I think this one is a good idea generally for d.o, not just in the context of editing pages that we are discussing here, but also for the right to create new pages which everyone gets immediately right now. I have created a webmasters' issue about it, if anyone is interested in chiming in and/or helping: http://drupal.org/node/307650 - Addi (add1sun) From wolf.zirbs at gmail.com Sat Sep 13 14:32:45 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Sat, 13 Sep 2008 16:32:45 +0200 Subject: [documentation] Want to help more as I get more confident with "Doc-Team" Tasks Message-ID: Hi Team, During the last few month I got more confident with maintaining and helping out with the Documentation and I just want to help out a bit more. If there is anything in addition of what already I can contribute you may evaluate to relay on my collaboration for more. Thanks -- Sincerely Best Regards Wolf J. Zirbs (@wolfflow) P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080913/01d5196f/attachment.htm From drupal at rocktreesky.com Sun Sep 14 12:57:21 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sun, 14 Sep 2008 08:57:21 -0400 Subject: [documentation] REMINDER: IRC meeting on Sept. 14 In-Reply-To: <2FB92256-026E-4571-88AB-A4427697745E@rocktreesky.com> References: <6553B637-B4F1-407B-81ED-427A99EED43D@rocktreesky.com> <2FB92256-026E-4571-88AB-A4427697745E@rocktreesky.com> Message-ID: <2E180642-96D9-469C-B20C-B7420D937949@rocktreesky.com> Just a reminder that there is an IRC meeting today at 17:00 GMT, details below. On Sep 4, 2008, at 12:13 PM, Addison Berry wrote: > OK, the Doodle is done. :-) Next IRC meeting will be on the FreeNode > IRC network in #drupal-docs on > > Sunday, September 14 at 17:00 GMT (1 pm EDT, 10 am PDT) > > Feel free to post to the list with agenda items you would like > covered. The main things to discuss right now: > > - Getting involved book > - Open editing to all auth users > > An event post was created on the group page as well (http://groups.drupal.org/node/145700 > ). See you there! > > On Sep 2, 2008, at 7:59 AM, Addison Berry wrote: > >> I am planning some time later today to do a brain dump of the Doc >> sprint, which was totally awesome. I have a lot to write up and >> limited time right now though. I do however want to get us >> scheduling the next IRC meeting so we can keep our momentum going. >> >> I have set up a Doodle for Sep 11 - Sep 14: http://www.doodle.ch/7dx3823d582rxgsk >> . Everyone needs to vote on the doodle by *September 4 at 18:00 >> GMT*. As usual we will keep the meeting to one hour long and >> determine the agenda ahead of time on the mail list. >> >> Addi (add1sun) >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080914/f3ece27d/attachment-0001.htm From joshua at brauerranch.com Sun Sep 14 13:51:42 2008 From: joshua at brauerranch.com (Joshua Brauer) Date: Sun, 14 Sep 2008 07:51:42 -0600 Subject: [documentation] REMINDER: IRC meeting on Sept. 14 In-Reply-To: <2E180642-96D9-469C-B20C-B7420D937949@rocktreesky.com> References: <6553B637-B4F1-407B-81ED-427A99EED43D@rocktreesky.com> <2FB92256-026E-4571-88AB-A4427697745E@rocktreesky.com> <2E180642-96D9-469C-B20C-B7420D937949@rocktreesky.com> Message-ID: Today is a travel day so I'll be missing the meeting. Here are my votes: 1) Opening up doc to all... I have reservations about this but vote that we should try it on a time-limited basis and see how it goes. 2) Required log notes field gets a No vote. While it would be handy to have it remind us what is going on I think this would be outweighed by the number of times that non-meaningful things get put in there just because something has to be put in. As it is if I make several successive edits on a page to accomplish a goal there may not be a meaningful message on the second or third edits in rapid succession. --------------------------- Joshua Brauer Our lives as we lead them are passed on to others, whether in physical or mental forms, tingeing all future lives together. This should be enough for one who lives for truth and service to his fellow passengers on the way. --- Luther Burbank On Sep 14, 2008, at 6:57 AM, Addison Berry wrote: > Just a reminder that there is an IRC meeting today at 17:00 GMT, > details below. > > On Sep 4, 2008, at 12:13 PM, Addison Berry wrote: > >> OK, the Doodle is done. :-) Next IRC meeting will be on the >> FreeNode IRC network in #drupal-docs on >> >> Sunday, September 14 at 17:00 GMT (1 pm EDT, 10 am PDT) >> >> Feel free to post to the list with agenda items you would like >> covered. The main things to discuss right now: >> >> - Getting involved book >> - Open editing to all auth users >> >> An event post was created on the group page as well (http://groups.drupal.org/node/145700 >> ). See you there! >> >> On Sep 2, 2008, at 7:59 AM, Addison Berry wrote: >> >>> I am planning some time later today to do a brain dump of the Doc >>> sprint, which was totally awesome. I have a lot to write up and >>> limited time right now though. I do however want to get us >>> scheduling the next IRC meeting so we can keep our momentum going. >>> >>> I have set up a Doodle for Sep 11 - Sep 14: http://www.doodle.ch/7dx3823d582rxgsk >>> . Everyone needs to vote on the doodle by *September 4 at 18:00 >>> GMT*. As usual we will keep the meeting to one hour long and >>> determine the agenda ahead of time on the mail list. >>> >>> Addi (add1sun) >>> -- >>> Pending work: http://drupal.org/project/issues/documentation/ >>> List archives: http://lists.drupal.org/pipermail/documentation/ >> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080914/ea8c5cf2/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2427 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080914/ea8c5cf2/attachment.bin From emmajane at xtrinsic.com Mon Sep 15 02:45:54 2008 From: emmajane at xtrinsic.com (Emma Jane Hogbin) Date: Sun, 14 Sep 2008 22:45:54 -0400 Subject: [documentation] scheduling and calendars Message-ID: <48CDCC62.9070500@xtrinsic.com> Hi everyone, One of the things we talked about today in the meeting was having a visual calendar to show current doc team projects as well as (arbitrary) deadlines for different projects. At this point it seems we rely on brute force brain power to remember all of the things that are happening. Add1sun is awesome at giving us reminders, but I'd like to feel a little more in control of all the stuff that's happening (remembering URLs is also not my strength). I'm a visual thinker so I'd like this information to be contained in a calendar display (and/or available as a feed that I can import into my own calendar system). Assuming that I'm not the only person who (1) works well to deadlines and (2) would appreciate being able to "see" the future plans for the doc team, what would you like to see on the calendar: [ ] current projects [ ] future meetings [ ] theme of the week for tasks (e.g. this week is focused on cleaning up the ____ documents or issue queue or ??) [ ] (deadline for) request for comments (e.g. the Knight Initiative proposal that Add1sun has put forward) [ ] other? I don't have a lot of experience with g.d.o, so I'm not entirely sure what's installed and more to the point, what would be useful /to/ install if there are specific tools that might be useful...one suggestion was to create events everything along with some basic taxonomy to filter different kinds of events (maybe using the different categories listed above?). (Add1sun has also opened an issue to see why the doc team meeting didn't show up in the main calendar for g.d.o... we should at least be able to get meetings showing up in the main calendar.) Suggestions? Questions? Thoughts on what might help you keep all the doc team activities a little clearer in your brain? regards, emma -- Emma Jane Hogbin, B.Sc. work: www.xtrinsic.com learn: www.hicktech.com play: www.emmajane.net From andrewberry at sentex.net Mon Sep 15 03:38:00 2008 From: andrewberry at sentex.net (Andrew Berry) Date: Sun, 14 Sep 2008 23:38:00 -0400 Subject: [documentation] scheduling and calendars In-Reply-To: <48CDCC62.9070500@xtrinsic.com> References: <48CDCC62.9070500@xtrinsic.com> Message-ID: On 14-Sep-08, at 10:45 PM, Emma Jane Hogbin wrote: > [ ] future meetings This would be very useful; I know local group meetings have an iCal feed, so I'm sure it can be done with the existing g.d.o setup. I don't really feel that most of the other items fit well in a calendar, unless they have due dates. They might fit better as an RSS feed, since they really are more like announcements than specific timed events. Perhaps "tasks of the week" postings to the read only feed would be helpful. --Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2692 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080914/d00fa2cc/attachment.bin From drupal at rocktreesky.com Mon Sep 15 13:15:40 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 15 Sep 2008 09:15:40 -0400 Subject: [documentation] scheduling and calendars In-Reply-To: <48CDCC62.9070500@xtrinsic.com> References: <48CDCC62.9070500@xtrinsic.com> Message-ID: <7457F48C-9518-48C2-86FB-57F15A442593@rocktreesky.com> On Sep 14, 2008, at 10:45 PM, Emma Jane Hogbin wrote: > Hi everyone, > > One of the things we talked about today in the meeting was having a > visual calendar to show current doc team projects as well as > (arbitrary) > deadlines for different projects. > > At this point it seems we rely on brute force brain power to remember > all of the things that are happening. Add1sun is awesome at giving us > reminders, but I'd like to feel a little more in control of all the > stuff that's happening (remembering URLs is also not my strength). > I'm a > visual thinker so I'd like this information to be contained in a > calendar display (and/or available as a feed that I can import into my > own calendar system). Definitely something we need to sort out if we are ging to make it easier for people to jump in. Thanks for taking this on emmajane. > > > Assuming that I'm not the only person who (1) works well to deadlines > and (2) would appreciate being able to "see" the future plans for the > doc team, what would you like to see on the calendar: > [ ] current projects > [ ] future meetings > [ ] theme of the week for tasks (e.g. this week is focused on cleaning > up the ____ documents or issue queue or ??) > [ ] (deadline for) request for comments (e.g. the Knight Initiative > proposal that Add1sun has put forward) > [ ] other? > These sound good to me (with current projects being set with those arbitrary deadlines). The events on g.d.o will allow us to do multi- day events, so we can do the theme of the week ones as well. My only thought on the list is that people may not want *all* of those different things showing up in their calendars. USing taxonomy gives us handy RSS feeds so people can follow the feeds that they want. I'm not sure that the iCal calendar would do the same thing for us. > I don't have a lot of experience with g.d.o, so I'm not entirely sure > what's installed and more to the point, what would be useful /to/ > install if there are specific tools that might be useful...one > suggestion was to create events everything along with some basic > taxonomy to filter different kinds of events (maybe using the > different > categories listed above?). I've added you as an admin to the docs group (http://groups.drupal.org/documentation-team ) so you can get in and see what we have to work with. Feel free to ping me about what is set up so far. We do have a vocabulary, which we can expand/change, that currently just has "meetings" and "sprints" in it. > (Add1sun has also opened an issue to see why the doc team meeting > didn't > show up in the main calendar for g.d.o... we should at least be able > to > get meetings showing up in the main calendar.) > Yeah, I hope to get to the bottom of that one, since that should just be happening for us AFAIK. - Addi (add1sun) From drupal at rocktreesky.com Mon Sep 15 13:42:27 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 15 Sep 2008 09:42:27 -0400 Subject: [documentation] SUMMARY for Proposal to open up editing rights In-Reply-To: <48C816C7.8090709@webchick.net> References: <200809092340.33936.larry@garfieldtech.com> <7CAE3A58-9274-4AA0-B8D2-8C2D3EC9E4A0@sentex.net> <48C816C7.8090709@webchick.net> Message-ID: On Sep 10, 2008, at 2:49 PM, Angela Byron wrote: > Andrew Berry wrote: >> On 10-Sep-08, at 12:40 AM, Larry Garfield wrote: >> >>>> Related (in a hook_form_alter kind of way): Making revision logs >>>> required. Again, we should be able to add a simple validation >>>> rule to >>>> the drupalorg.module. We just need someone with a little bit of >>>> time >>>> to make a patch. >>> >>> Even if we don't end up opening edit rights more widely, this is a >>> good thing. >>> I keep forgetting to fill in revision info even when I should do >>> so, so >>> having the system poke me about it would be appreciated. :-) >> >> Actually, this would probably be a good feature to add to the >> workflow >> section in Drupal core. I know I have quite a few sites that could >> use >> that feature. Making revision logs required would be a nice feature >> for >> D7. I don't see an open issue for it, but doing it both ways (through >> form_alter and a patch) should be pretty easy. If I can find the time >> I'll take a look at it. > > Just a quick note that I would gladly accept such a patch into D7. :) There is now and issue with a patch for review to get this into core for D7 (http://drupal.org/node/308352). I also created an issue to get this modification onto d.o, since we won't be using 7 for a while. :-) http://drupal.org/node/308675 - Addi (add1sun) From info at 33rdprime.com Mon Sep 15 14:08:40 2008 From: info at 33rdprime.com (Patrick Teglia) Date: Mon, 15 Sep 2008 08:08:40 -0600 Subject: [documentation] scheduling and calendars In-Reply-To: <7457F48C-9518-48C2-86FB-57F15A442593@rocktreesky.com> References: <48CDCC62.9070500@xtrinsic.com> <7457F48C-9518-48C2-86FB-57F15A442593@rocktreesky.com> Message-ID: Why don't we setup a Google Calendar? It will supply RSS, can be made public, and can cover categories. Thanks, Patrick Teglia On Mon, Sep 15, 2008 at 7:15 AM, Addison Berry wrote: > On Sep 14, 2008, at 10:45 PM, Emma Jane Hogbin wrote: > > > Hi everyone, > > > > One of the things we talked about today in the meeting was having a > > visual calendar to show current doc team projects as well as > > (arbitrary) > > deadlines for different projects. > > > > At this point it seems we rely on brute force brain power to remember > > all of the things that are happening. Add1sun is awesome at giving us > > reminders, but I'd like to feel a little more in control of all the > > stuff that's happening (remembering URLs is also not my strength). > > I'm a > > visual thinker so I'd like this information to be contained in a > > calendar display (and/or available as a feed that I can import into my > > own calendar system). > > Definitely something we need to sort out if we are ging to make it > easier for people to jump in. Thanks for taking this on emmajane. > > > > > > > Assuming that I'm not the only person who (1) works well to deadlines > > and (2) would appreciate being able to "see" the future plans for the > > doc team, what would you like to see on the calendar: > > [ ] current projects > > [ ] future meetings > > [ ] theme of the week for tasks (e.g. this week is focused on cleaning > > up the ____ documents or issue queue or ??) > > [ ] (deadline for) request for comments (e.g. the Knight Initiative > > proposal that Add1sun has put forward) > > [ ] other? > > > These sound good to me (with current projects being set with those > arbitrary deadlines). The events on g.d.o will allow us to do multi- > day events, so we can do the theme of the week ones as well. My only > thought on the list is that people may not want *all* of those > different things showing up in their calendars. USing taxonomy gives > us handy RSS feeds so people can follow the feeds that they want. I'm > not sure that the iCal calendar would do the same thing for us. > > > > I don't have a lot of experience with g.d.o, so I'm not entirely sure > > what's installed and more to the point, what would be useful /to/ > > install if there are specific tools that might be useful...one > > suggestion was to create events everything along with some basic > > taxonomy to filter different kinds of events (maybe using the > > different > > categories listed above?). > > I've added you as an admin to the docs group ( > http://groups.drupal.org/documentation-team > ) so you can get in and see what we have to work with. Feel free to > ping me about what is set up so far. We do have a vocabulary, which we > can expand/change, that currently just has "meetings" and "sprints" in > it. > > > (Add1sun has also opened an issue to see why the doc team meeting > > didn't > > show up in the main calendar for g.d.o... we should at least be able > > to > > get meetings showing up in the main calendar.) > > > Yeah, I hope to get to the bottom of that one, since that should just > be happening for us AFAIK. > > - Addi (add1sun) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080915/83210bea/attachment.htm From emmajane at xtrinsic.com Mon Sep 15 14:21:44 2008 From: emmajane at xtrinsic.com (Emma Jane Hogbin) Date: Mon, 15 Sep 2008 10:21:44 -0400 Subject: [documentation] scheduling and calendars In-Reply-To: References: <48CDCC62.9070500@xtrinsic.com> <7457F48C-9518-48C2-86FB-57F15A442593@rocktreesky.com> Message-ID: <48CE6F78.1090904@xtrinsic.com> Patrick Teglia wrote: > Why don't we setup a Google Calendar? It will supply RSS, can be made > public, and can cover categories. I'd really like to see us working within the Drupal toolset first. Part of my thinking behind the iCal option was for people who do want to use another calendar program (I have to admit that I mostly use paper and downloaded templates from www.diyplanner.com). I'm happy to explore g.d.o first. I'm sure if I've got this itch to scratch there will be other groups who might benefit from having a similar toolset. Of course if it all comes up fail we should look at using an offsite option as well. :) regards, emma PS Thanks for adding me as an admin, Add1sun, I'll play around with things this week and report back on my findings. -- Emma Jane Hogbin, B.Sc. work: www.xtrinsic.com play: www.emmajane.net learn: www.hicktech.com From drupal at rocktreesky.com Mon Sep 15 19:55:23 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 15 Sep 2008 15:55:23 -0400 Subject: [documentation] Summary and log of Sept. 14 IRC meeting Message-ID: <07CD96D6-C3F4-497F-8938-A20BE59F4CC0@rocktreesky.com> Here is the IRC log from the meeting: http://pastebin.com/f183bcc8d We had several announcements at the beginning of the meeting and then we hit the two agenda items. As usual if I missed anything in here or others have feedback/thoughts, feel free to add to this summary. Thanks to all who attended. ANNOUNCEMENTS ================ New read-only group page: http://groups.drupal.org/documentation-team KDI proposal for doc sprints: http://groups.drupal.org/node/14669 The d.o redesign underway: http://groups.drupal.org/drupal-org-redesign-analysis - Ways to help out with the redesign: http://groups.drupal.org/node/14643 - D.o Wireframe game: http://www.disambiguity.com/drupalorg-come-wireframe-with-me/ Webchick wants feedback on the D7 help text system. She'll be posting to the list soon with more details, but one issue to jump in on is at http://drupal.org/node/299050 AGENDA ======= Getting involved handbook ------------------------------------- The Getting involved book needs to get pushed over the finish line. We need to flech out the issues for it. Many people are unsure of exactly what to do, so we decided that having a few short virtual sprints specifically focused on the Getting involved book would help. We will be scheduling those later this week. The goal is to officially create the new book and announce it to the community by Sept 28. A discussion that arose from this was how difficult it is to keep track of all of the projects and dates for doc team work. We agreed that getting a more streamlined and public way of our ongoing work and meetings would be desired. We will create a small "working group" of folks interested in sorting that out and implementing. emmajane has started a thread for that. Opening editing rights to auth. users ------------------------------------------------- The majority decision on this point is to open the editing rights to all auth users for a one month test period. There are a few things we would like in place prior to doing that, namely getting Moshe's path linking to diffs from the Latest updates page and requiring the revision log to be filled out when editing. We also looked at an issue on the idea of having a delay period for new users http://drupal.org/node/307650 , though this will take a while to implement and so won't happen before the initial trial. Anyone interested in this feature should chime in on the thread so we can nail down a direction and work on the code to make it happen on d.o. The biggest thing that needs to happen now is getting the infra team on board to implement the change. NEXT STEPS ========== Getting involved (GI): - Get GI issues filled out: http://drupal.org/project/issues?projects=18753&text=Contrib%20Redesign : - Set new docs vocab: http://drupal.org/node/304826 - Do some GI sprints: I'll send a followup email out re: sprint scheduling - Post to d.o front page re: handbook reorg: We can write this up once we get closer Opening edit rights: - Check with infra about the next steps to implement: I'll do that this week - Get recent updates patch going: http://drupal.org/node/304667 (need to check with Moshe on this) - Get required revision log patch done: http://drupal.org/node/308675 - Write up an announcement for d.o front page New tasks: mechfish created an issue for a Recent updates RSS feed: http://drupal.org/node/308354 emmajane has started a thread about schedule/calendar issues: http://lists.drupal.org/pipermail/documentation/2008-September/006267.html - Addi (add1sun) From wolf.zirbs at gmail.com Mon Sep 15 23:16:11 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Tue, 16 Sep 2008 01:16:11 +0200 Subject: [documentation] Build a Contrib Redisign: Coomon Terminology Message-ID: Hi All, going thru Getting Involved I want propose to build a Contrib Redisign: Common Terminology page-project I sure am not the best english writer to summarize the general motivations that may lead to motivate contribution and support for our Drupa.org site Visitors and members. Therefore before doing to much and not properly I ask you to submit your opinion about: The items I would focus on are: 1. Every member can contribute posting comments on Common expressions & acronyms used on D.O. suggesting terms, Expressions, Acronyms that are used on Drupal.org and for no-native English would be usefully to list. 2. Expanding the "Terminology" listed items adding links to "more information on subject (Terms, Expressions, Acronyms) with page/nodes present on Drupal.org 3. Grow the interest to participate on the Community efforts to make Drupal.org a reach resource for all Visitors even no-native English to Drupal. Please if you want add more points and vote on this behalf. KindRegards -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/967156a8/attachment.htm From shubhada.mcs at gmail.com Tue Sep 16 07:33:26 2008 From: shubhada.mcs at gmail.com (shubhada litke) Date: Tue, 16 Sep 2008 13:03:26 +0530 Subject: [documentation] How can I add an attachment or upload field to the custom profiles? Message-ID: <726fcdb80809160033v24677e30wbbfcf57439822ad9@mail.gmail.com> hello, I am using drupal 5. I created registration form using profile but I want to upload resume field on registration form. which module i download or which changes i will do so i can see upload field on registration form (or say user profile). Regards shubhada -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/e7602007/attachment-0001.htm From shubhada.mcs at gmail.com Tue Sep 16 09:41:27 2008 From: shubhada.mcs at gmail.com (shubhada litke) Date: Tue, 16 Sep 2008 15:11:27 +0530 Subject: [documentation] [profile][upload file] Message-ID: <726fcdb80809160241v29a82329x4766ed4c6abe72dc@mail.gmail.com> ---------- Forwarded message ---------- From: shubhada litke Date: Tue, Sep 16, 2008 at 1:03 PM Subject: How can I add an attachment or upload field to the custom profiles? To: documentation at drupal.org hello, I am using drupal 5. How can I add an attachment or upload field to the custom profiles? I created registration form using profile but I want to upload resume field on registration form. which module i download or which changes i will do so i can see upload field on registration form (or say user profile). Regards shubhada -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/b8ad618a/attachment.htm From hdeelstra at gmail.com Tue Sep 16 10:15:08 2008 From: hdeelstra at gmail.com (Heine Deelstra) Date: Tue, 16 Sep 2008 12:15:08 +0200 Subject: [documentation] How can I add an attachment or upload field to the custom profiles? In-Reply-To: <726fcdb80809160033v24677e30wbbfcf57439822ad9@mail.gmail.com> References: <726fcdb80809160033v24677e30wbbfcf57439822ad9@mail.gmail.com> Message-ID: On Tue, 16 Sep 2008 09:33:26 +0200, shubhada litke wrote: > hello, > I am using drupal 5. > I created registration form using profile but I want to upload resume > field on registration form. > which module i download or which changes i will do so i can see upload > field > on registration form (or say user profile). > > > > Regards > shubhada Dear Shubhada, Please do not use - the Drupal.org mailing lists, save the actual support list on http://lists.drupal.org/listinfo/support - the Drupal.org contact form to get support. For a full overview of the available support options, see http://drupal.org/support. Kind regards, Heine Deelstra From drupal at rocktreesky.com Tue Sep 16 12:52:52 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Tue, 16 Sep 2008 08:52:52 -0400 Subject: [documentation] [profile][upload file] In-Reply-To: <726fcdb80809160241v29a82329x4766ed4c6abe72dc@mail.gmail.com> References: <726fcdb80809160241v29a82329x4766ed4c6abe72dc@mail.gmail.com> Message-ID: <75F5CE8F-53EE-40DA-8117-D8090E22DDB2@rocktreesky.com> Hi there shubhada, Unfortunately this is a list to discuss maintaining the documentation for Drupal, not a support resource. You can find a list of Drupal support resources at http://drupal.org/support. - Addi (add1sun) On Sep 16, 2008, at 5:41 AM, shubhada litke wrote: > > > ---------- Forwarded message ---------- > From: shubhada litke > Date: Tue, Sep 16, 2008 at 1:03 PM > Subject: How can I add an attachment or upload field to the custom > profiles? > To: documentation at drupal.org > > > hello, > I am using drupal 5. > How can I add an attachment or upload field to the custom profiles? > I created registration form using profile but I want to upload > resume field on registration form. > which module i download or which changes i will do so i can see > upload field on registration form (or say user profile). > > > > Regards > shubhada > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/985703b4/attachment.htm From drupal at rocktreesky.com Tue Sep 16 13:46:07 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Tue, 16 Sep 2008 09:46:07 -0400 Subject: [documentation] Getting involved sprint scheduling Message-ID: <19C98E1B-265B-4419-9BA3-88A30FA76A4E@rocktreesky.com> The new Getting involved handbook needs some focused attention to get it going. I'd like to create the book and announce it to the larger community by Sept. 28. During the last IRC meeting we thought that maybe a few short virtual sprints focused just on this task might help since many folks aren't quite sure what needs to be done, or just have a hard time setting time aside for it. I've set up a (large) Doodle at http://www.doodle.ch/participation.html?pollId=weeh8anybfx9fe54 for folks to indicate times next week that would be good. We'll schedule it out to overlap with as many people's schedules as we can. I'll post the sprint schedule on this list and on g.d.o on September 20. Keep in mind that the sprint times will be broad (2+ hours each) but that each person can show up for whatever time they happen to have available in the window; be it 15 minutes or 2 hours. - Addi (add1sun) From zirvap at gmail.com Tue Sep 16 17:55:22 2008 From: zirvap at gmail.com (Hilde Austlid) Date: Tue, 16 Sep 2008 19:55:22 +0200 Subject: [documentation] Redesign discussion from docs point of view Message-ID: Hi! There are a lot of interesting discussions going on right now about the redesign of drupal.org. I'd like to do some brainstorming on the redesign from a docs point of view: What do the doc team want from the redesign? Do we want docs.drupal.org as a separate site? New functionality? New ideas for navigation? What works well and not-so-well in the current docs? This discussion should be in a place where it's easy to find both for doc team members and for the people doing the redesign. I suggest that a discussion is started and cross posted in http://groups.drupal.org/drupal-org-redesign-analysis and http://groups.drupal.org/documentation-team. If we keep such discussions on the mailing list, it's much harder to find and follow for others. Hilde (zirvap) From catch56 at googlemail.com Tue Sep 16 18:00:50 2008 From: catch56 at googlemail.com (Nathaniel Catchpole) Date: Tue, 16 Sep 2008 19:00:50 +0100 Subject: [documentation] Redesign discussion from docs point of view In-Reply-To: References: Message-ID: I think the redesign group is the best place for this to happen - where documentation fits into everything else, affects everything else as much as it affects documentation :) There's also a couple of discussions which include documentation on there already from earlier this year: http://groups.drupal.org/node/10223 and http://groups.drupal.org/node/10003 - might worth looking at for people who haven't already seen them. Nat On Tue, Sep 16, 2008 at 6:55 PM, Hilde Austlid wrote: > Hi! > There are a lot of interesting discussions going on right now about > the redesign of drupal.org. I'd like to do some brainstorming on the > redesign from a docs point of view: What do the doc team want from the > redesign? Do we want docs.drupal.org as a separate site? New > functionality? New ideas for navigation? What works well and > not-so-well in the current docs? > > This discussion should be in a place where it's easy to find both for > doc team members and for the people doing the redesign. I suggest that > a discussion is started and cross posted in > http://groups.drupal.org/drupal-org-redesign-analysis and > http://groups.drupal.org/documentation-team. If we keep such > discussions on the mailing list, it's much harder to find and follow > for others. > > Hilde > (zirvap) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/942b3ed5/attachment.htm From drupal at rocktreesky.com Tue Sep 16 21:05:45 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Tue, 16 Sep 2008 17:05:45 -0400 Subject: [documentation] g.d.o working group invite Message-ID: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> During the Sept. 14 meeting it came up that we have a lot going on and it is hard to keep track of it all. My poor little head can't hold all of it (nor it that a safe idea anyway ;-)). Emmajane has started a thread about calendars (http://lists.drupal.org/pipermail/documentation/2008-September/006267.html ) and we talked about making a little working group to sort that out. This is a public invite to see if anyone is interested in forming a small working group to specifically work on setting up the g.d.o page (http://groups.drupal.org/documentation-team ) to be a bit more useful to our group. This would involve getting together online and poking at the tools we have on g.d.o. The schedule bit is the first order, but we can also create our own taxonomy and use OG panels, so we can create various tabs and organize the front page to highlight things. I'd also like to figure out ways to get all of our info together without excessive cross-posting, if possible. ;-) We don't need a ton of people, but a few would be nice. If you are interested, please just respond to this thread by this Friday. Please also include your g.d.o username if you have one. Once we know who is here, we'll set up a time to dig in together. - Addi (add1sun) From info at 33rdprime.com Tue Sep 16 21:47:20 2008 From: info at 33rdprime.com (Patrick Teglia) Date: Tue, 16 Sep 2008 15:47:20 -0600 Subject: [documentation] g.d.o working group invite In-Reply-To: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> References: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> Message-ID: I would love to have a more active role, count me in! Thanks, Patrick Teglia (CrashTest_ is my g.d.o name) On Tue, Sep 16, 2008 at 3:05 PM, Addison Berry wrote: > During the Sept. 14 meeting it came up that we have a lot going on and > it is hard to keep track of it all. My poor little head can't hold all > of it (nor it that a safe idea anyway ;-)). Emmajane has started a > thread about calendars ( > http://lists.drupal.org/pipermail/documentation/2008-September/006267.html > ) and we talked about making a little working group to sort that out. > This is a public invite to see if anyone is interested in forming a > small working group to specifically work on setting up the g.d.o page ( > http://groups.drupal.org/documentation-team > ) to be a bit more useful to our group. This would involve getting > together online and poking at the tools we have on g.d.o. The schedule > bit is the first order, but we can also create our own taxonomy and > use OG panels, so we can create various tabs and organize the front > page to highlight things. > > I'd also like to figure out ways to get all of our info together > without excessive cross-posting, if possible. ;-) > > We don't need a ton of people, but a few would be nice. If you are > interested, please just respond to this thread by this Friday. Please > also include your g.d.o username if you have one. Once we know who is > here, we'll set up a time to dig in together. > > > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/c1b4c0dc/attachment.htm From purrin at binary.net Tue Sep 16 23:42:59 2008 From: purrin at binary.net (christopher calicott) Date: Tue, 16 Sep 2008 16:42:59 -0700 Subject: [documentation] g.d.o working group invite In-Reply-To: References: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> Message-ID: Me as well! :) -=- christopher On Sep 16, 2008, at 2:47 PM, Patrick Teglia wrote: > I would love to have a more active role, count me in! > > Thanks, > > Patrick Teglia > (CrashTest_ is my g.d.o name) > > On Tue, Sep 16, 2008 at 3:05 PM, Addison Berry > wrote: > During the Sept. 14 meeting it came up that we have a lot going on and > it is hard to keep track of it all. My poor little head can't hold all > of it (nor it that a safe idea anyway ;-)). Emmajane has started a > thread about calendars (http://lists.drupal.org/pipermail/documentation/2008-September/006267.html > ) and we talked about making a little working group to sort that out. > This is a public invite to see if anyone is interested in forming a > small working group to specifically work on setting up the g.d.o > page (http://groups.drupal.org/documentation-team > ) to be a bit more useful to our group. This would involve getting > together online and poking at the tools we have on g.d.o. The schedule > bit is the first order, but we can also create our own taxonomy and > use OG panels, so we can create various tabs and organize the front > page to highlight things. > > I'd also like to figure out ways to get all of our info together > without excessive cross-posting, if possible. ;-) > > We don't need a ton of people, but a few would be nice. If you are > interested, please just respond to this thread by this Friday. Please > also include your g.d.o username if you have one. Once we know who is > here, we'll set up a time to dig in together. > > > - Addi (add1sun) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080916/90ff340e/attachment.htm From emmajane at xtrinsic.com Wed Sep 17 04:00:12 2008 From: emmajane at xtrinsic.com (Emma Jane Hogbin) Date: Wed, 17 Sep 2008 00:00:12 -0400 Subject: [documentation] g.d.o working group invite In-Reply-To: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> References: <7AD3F0A9-5A26-4635-81C8-3140481A8AE9@rocktreesky.com> Message-ID: <48D080CC.7040508@xtrinsic.com> Addison Berry wrote: > This is a public invite to see if anyone is interested in forming a > small working group to specifically work on setting up the g.d.o page (http://groups.drupal.org/documentation-team > ) to be a bit more useful to our group. This would involve getting > together online and poking at the tools we have on g.d.o. The schedule > bit is the first order, but we can also create our own taxonomy and > use OG panels, so we can create various tabs and organize the front > page to highlight things. Please add me to this list (obviously). :) regards, emma aka emmajane -- Emma Jane Hogbin, B.Sc. ramble: www.emmajane.net work: www.xtrinsic.com learn: www.hicktech.com From drupal at rocktreesky.com Wed Sep 17 21:27:55 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 17 Sep 2008 17:27:55 -0400 Subject: [documentation] Redesign discussion from docs point of view In-Reply-To: References: Message-ID: <88CE7722-4868-4388-80DF-9A3836367CA7@rocktreesky.com> Yeah, I've been thinking about the best way to sort of consolidate "docs" redesign ideas. I definitely agree that trying to keep it on the list is too limiting. Everyone should definitely check out the threads that catch pointed to, but I'd also like to try to have a more distilled brainstorm list like Hilde is shooting for I think. Perhaps we should create a doc-specific wiki page on the redesign group (which is easy to cross-post to the docs list)? Or should we have a discussion (like revive http://groups.drupal.org/node/10223) and then distill that conversation into a list that can be posted? We should also take part directly in the open redesign discussion that is happening more than anything. Things like the discussion of a separate site are already happening (http://www.disambiguity.com/drupalorg-one-site-or-many/ ) and folks can (should) give direct feedback. Also, I would really, really encourage folks to work up some wireframes around the handbook (http://www.disambiguity.com/drupalorg-come-wireframe-with-me/ ), especially ones that include new feature ideas. Things like versioning the docs (how would that look in order to use it?) and how to add more prominent info on what you can and cannot do a page ("how to make this page better!" or whatnot.) - Addi (add1sun) On Sep 16, 2008, at 2:00 PM, Nathaniel Catchpole wrote: > I think the redesign group is the best place for this to happen - > where documentation fits into everything else, affects everything > else as much as it affects documentation :) > > There's also a couple of discussions which include documentation on > there already from earlier this year: http://groups.drupal.org/node/10223 > and http://groups.drupal.org/node/10003 - might worth looking at > for people who haven't already seen them. > > Nat > > On Tue, Sep 16, 2008 at 6:55 PM, Hilde Austlid > wrote: > Hi! > There are a lot of interesting discussions going on right now about > the redesign of drupal.org. I'd like to do some brainstorming on the > redesign from a docs point of view: What do the doc team want from the > redesign? Do we want docs.drupal.org as a separate site? New > functionality? New ideas for navigation? What works well and > not-so-well in the current docs? > > This discussion should be in a place where it's easy to find both for > doc team members and for the people doing the redesign. I suggest that > a discussion is started and cross posted in > http://groups.drupal.org/drupal-org-redesign-analysis and > http://groups.drupal.org/documentation-team. If we keep such > discussions on the mailing list, it's much harder to find and follow > for others. > > Hilde > (zirvap) > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080917/dd47c676/attachment.htm From shubhada.mcs at gmail.com Thu Sep 18 07:35:28 2008 From: shubhada.mcs at gmail.com (shubhada litke) Date: Thu, 18 Sep 2008 13:05:28 +0530 Subject: [documentation] [profile][upload file field] Message-ID: <726fcdb80809180035x6c9ad818id8775ad166d63f52@mail.gmail.com> hello, i installed drupal-5.9 I want users to be able to upload their resume when they register. I downloaded the profile module.. using which i was able to add additional fields when member is registering... but the upload file option is not there... plz tell me which module is there and which are steps? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080918/6780a0f4/attachment-0001.htm From drupal at rocktreesky.com Thu Sep 18 12:43:08 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 18 Sep 2008 08:43:08 -0400 Subject: [documentation] [profile][upload file field] In-Reply-To: <726fcdb80809180035x6c9ad818id8775ad166d63f52@mail.gmail.com> References: <726fcdb80809180035x6c9ad818id8775ad166d63f52@mail.gmail.com> Message-ID: <97DDCC51-C514-449F-9C90-2E4A0FC3B64D@rocktreesky.com> This is your third support email to this list. You have been told several times that this is not the correct place for these questions and you need to seek support in the support channels: http://drupal.org/support Please be respectful of this list or we may need to remove you from the mailing list. Thanks - Addi (add1sun) On Sep 18, 2008, at 3:35 AM, shubhada litke wrote: > hello, > i installed drupal-5.9 > I want users to be able to upload their resume when they register. I > downloaded the profile module.. using which i was able to add > additional fields when member is registering... but the upload file > option is not there... > plz tell me which module is there and which are steps? > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From nan_wich at bellsouth.net Thu Sep 18 12:55:15 2008 From: nan_wich at bellsouth.net (Nancy Wichmann) Date: Thu, 18 Sep 2008 08:55:15 -0400 Subject: [documentation] [profile][upload file field] In-Reply-To: <726fcdb80809180035x6c9ad818id8775ad166d63f52@mail.gmail.com> Message-ID: Try the resume module. -----Original Message----- From: documentation-bounces at drupal.org [mailto:documentation-bounces at drupal.org]On Behalf Of shubhada litke Sent: Thursday, September 18, 2008 3:35 AM To: documentation at drupal.org; doc-bugs-sc.1219140303.odhllfohbebdaagclfif-shubhada.mcs=gmail.com at lists.php net; drupal Subject: [documentation] [profile][upload file field] hello, i installed drupal-5.9 I want users to be able to upload their resume when they register. I downloaded the profile module.. using which i was able to add additional fields when member is registering... but the upload file option is not there... plz tell me which module is there and which are steps? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080918/848d8a80/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: multipart/alternative Size: 0 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080918/848d8a80/attachment.bin -------------- next part -------------- No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1677 - Release Date: 9/17/2008 5:07 PM From ronaldmulero at drupal.org Thu Sep 18 16:49:57 2008 From: ronaldmulero at drupal.org (Ronald Mulero) Date: Thu, 18 Sep 2008 11:49:57 -0500 Subject: [documentation] g.d.o working group invite Message-ID: I'd like to help, too. Ron (ronaldmulero) christopher calicott wrote: > Me as well! :) > > -=- christopher > > > > > On Sep 16, 2008, at 2:47 PM, Patrick Teglia wrote: > >> I would love to have a more active role, count me in! >> >> Thanks, >> >> Patrick Teglia >> (CrashTest_ is my g.d.o name) >> >> On Tue, Sep 16, 2008 at 3:05 PM, Addison Berry wrote: >> >> During the Sept. 14 meeting it came up that we have a lot going on and >> it is hard to keep track of it all. My poor little head can't hold all >> of it (nor it that a safe idea anyway ;-)). Emmajane has started a >> thread about calendars (http://lists.drupal.org/pipermail/documentation/2008-September/006267.html >> ) and we talked about making a little working group to sort that out. >> This is a public invite to see if anyone is interested in forming a >> small working group to specifically work on setting up the g.d.o page (http://groups.drupal.org/documentation-team >> ) to be a bit more useful to our group. This would involve getting >> together online and poking at the tools we have on g.d.o. The schedule >> bit is the first order, but we can also create our own taxonomy and >> use OG panels, so we can create various tabs and organize the front >> page to highlight things. >> >> I'd also like to figure out ways to get all of our info together >> without excessive cross-posting, if possible. ;-) >> >> We don't need a ton of people, but a few would be nice. If you are >> interested, please just respond to this thread by this Friday. Please >> also include your g.d.o username if you have one. Once we know who is >> here, we'll set up a time to dig in together. >> >> >> - Addi (add1sun) > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From zirvap at gmail.com Fri Sep 19 07:40:59 2008 From: zirvap at gmail.com (Hilde Austlid) Date: Fri, 19 Sep 2008 09:40:59 +0200 Subject: [documentation] Redesign discussion from docs point of view In-Reply-To: <88CE7722-4868-4388-80DF-9A3836367CA7@rocktreesky.com> References: <88CE7722-4868-4388-80DF-9A3836367CA7@rocktreesky.com> Message-ID: Hi! 2008/9/17 Addison Berry : > Perhaps we should create a > doc-specific wiki page on the redesign group (which is easy to cross-post to > the docs list)? Or should we have a discussion (like > revive http://groups.drupal.org/node/10223) and then distill that > conversation into a list that can be posted? I think a discussion is better for brainstorming. From the wikis I've started, I get the feeling that people are a lot more reluctant to edit a wiki than to add a comment. > Also, I would really, really encourage folks to work up some wireframes > around the handbook > (http://www.disambiguity.com/drupalorg-come-wireframe-with-me/), especially > ones that include new feature ideas. Very good point! I've thought a bit about navigation and about multilanguage handbooks, I'll try to get some wireframes done this weekend. Hilde From shubhada.mcs at gmail.com Fri Sep 19 12:55:05 2008 From: shubhada.mcs at gmail.com (Shubhada Litke) Date: Fri, 19 Sep 2008 12:55:05 +0000 (UTC) Subject: [documentation] My birthday calendar Message-ID: <20080919125505.47CF9109E45@whitealder.osuosl.org> An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080919/485a65e5/attachment.htm From drupal at rocktreesky.com Fri Sep 19 13:26:59 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Fri, 19 Sep 2008 09:26:59 -0400 Subject: [documentation] My birthday calendar In-Reply-To: <20080919125505.47CF9109E45@whitealder.osuosl.org> References: <20080919125505.47CF9109E45@whitealder.osuosl.org> Message-ID: Bye bye. On Sep 19, 2008, at 8:55 AM, Shubhada Litke wrote: > Shubhada Litke (shubhada.mcs at gmail.com) is a member of > BirthdayTime.com and wants to know your birthday. > > Shubhada Litke says: > > Hi !! > I'm inviting you to enter your birthday into my calendar at > BirthdayTime. > You will help me remember it! > Click here to enter your birthday into my list: > http://www.birthdaytime.com/add_birthday/Shubhada Litke > > Thanks! > Shubhada Litke > > ----------------------------------------------------------- > What is BirthdayTime? > BirthdayTime is a free birthday/holiday reminder service that > notifies you about upcoming dates before it is too late! > > ----------------------------------------------------------- > Why did I receive this email? > Shubhada Litke (shubhada.mcs at gmail.com) wants to be notified when > your birthday is near. It's safe, fast, and provides a valuable > service! > > ----------------------------------------------------------- > I don't know who Shubhada Litke is! > It's possible that you were included in someone's birthday request > because you appear in his/her email contact list. > > ----------------------------------------------------------- > This email was sent by Shubhada Litke (shubhada.mcs at gmail.com) > To stop receiving emails from birthdaytime, please click here: > http://www.birthdaytime.com/cancelfollow.php?id=zM5OdPjmPuYPE5T8op7F9aq15B7NqacKajk%2B6vY%2Fg9sbnvJcGZvrYw%3D%3D&data=Yrms1ZYGZnF%2BGO2xib3HydXmn0MUGUdtGnDtejexyqQZ5COk5b2eG36oMpaO5Mb%2F%2FifCcHfAXx0%3D > BirthdayTime's offices are located at 2202 S.Figueroa St, Los > Angeles, CA 90007. -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080919/ec874d38/attachment.htm From drupal at rocktreesky.com Fri Sep 19 15:49:50 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Fri, 19 Sep 2008 11:49:50 -0400 Subject: [documentation] g.d.o working group invite In-Reply-To: References: Message-ID: <5ED71E7D-A5D9-4905-91C3-0D67C0A36854@rocktreesky.com> Groovy. Ok, I have: Josh Pat Chris Emma Ronald We can take the rest of our communication off list so as to not spam everyone with our back-and-forth. Thanks! - Addi (add1sun) On Sep 18, 2008, at 12:49 PM, Ronald Mulero wrote: > I'd like to help, too. > > Ron > (ronaldmulero) > > christopher calicott wrote: >> Me as well! :) >> >> -=- christopher >> >> >> >> >> On Sep 16, 2008, at 2:47 PM, Patrick Teglia wrote: >> >>> I would love to have a more active role, count me in! >>> >>> Thanks, >>> >>> Patrick Teglia >>> (CrashTest_ is my g.d.o name) >>> >>> On Tue, Sep 16, 2008 at 3:05 PM, Addison Berry >> > wrote: >>> >>> During the Sept. 14 meeting it came up that we have a lot going >>> on and >>> it is hard to keep track of it all. My poor little head can't >>> hold all >>> of it (nor it that a safe idea anyway ;-)). Emmajane has >>> started a >>> thread about calendars (http://lists.drupal.org/pipermail/documentation/2008-September/006267.html >>> ) and we talked about making a little working group to sort >>> that out. >>> This is a public invite to see if anyone is interested in >>> forming a >>> small working group to specifically work on setting up the >>> g.d.o page (http://groups.drupal.org/documentation-team >>> ) to be a bit more useful to our group. This would involve >>> getting >>> together online and poking at the tools we have on g.d.o. The >>> schedule >>> bit is the first order, but we can also create our own taxonomy >>> and >>> use OG panels, so we can create various tabs and organize the >>> front >>> page to highlight things. >>> >>> I'd also like to figure out ways to get all of our info together >>> without excessive cross-posting, if possible. ;-) >>> >>> We don't need a ton of people, but a few would be nice. If you >>> are >>> interested, please just respond to this thread by this Friday. >>> Please >>> also include your g.d.o username if you have one. Once we know >>> who is >>> here, we'll set up a time to dig in together. >>> >>> >>> - Addi (add1sun) >> >> >> -- >> Pending work: http://drupal.org/project/issues/documentation/ >> List archives: http://lists.drupal.org/pipermail/documentation/ > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at ryancross.com Sat Sep 20 00:05:10 2008 From: drupal at ryancross.com (Ryan Cross) Date: Sat, 20 Sep 2008 10:05:10 +1000 Subject: [documentation] g.d.o working group invite In-Reply-To: <5ED71E7D-A5D9-4905-91C3-0D67C0A36854@rocktreesky.com> References: <5ED71E7D-A5D9-4905-91C3-0D67C0A36854@rocktreesky.com> Message-ID: <4e983be00809191705g6b35183eq879279c219d488c1@mail.gmail.com> A bit late, but I can help too! :) On Sat, Sep 20, 2008 at 1:49 AM, Addison Berry wrote: > Groovy. Ok, I have: > > Josh > Pat > Chris > Emma > Ronald > > We can take the rest of our communication off list so as to not spam > everyone with our back-and-forth. > > Thanks! > - Addi (add1sun) > > > On Sep 18, 2008, at 12:49 PM, Ronald Mulero wrote: > > > I'd like to help, too. > > > > Ron > > (ronaldmulero) > > > > christopher calicott wrote: > >> Me as well! :) > >> > >> -=- christopher > >> > >> > >> > >> > >> On Sep 16, 2008, at 2:47 PM, Patrick Teglia wrote: > >> > >>> I would love to have a more active role, count me in! > >>> > >>> Thanks, > >>> > >>> Patrick Teglia > >>> (CrashTest_ is my g.d.o name) > >>> > >>> On Tue, Sep 16, 2008 at 3:05 PM, Addison Berry >>> > wrote: > >>> > >>> During the Sept. 14 meeting it came up that we have a lot going > >>> on and > >>> it is hard to keep track of it all. My poor little head can't > >>> hold all > >>> of it (nor it that a safe idea anyway ;-)). Emmajane has > >>> started a > >>> thread about calendars ( > http://lists.drupal.org/pipermail/documentation/2008-September/006267.html > >>> ) and we talked about making a little working group to sort > >>> that out. > >>> This is a public invite to see if anyone is interested in > >>> forming a > >>> small working group to specifically work on setting up the > >>> g.d.o page (http://groups.drupal.org/documentation-team > >>> ) to be a bit more useful to our group. This would involve > >>> getting > >>> together online and poking at the tools we have on g.d.o. The > >>> schedule > >>> bit is the first order, but we can also create our own taxonomy > >>> and > >>> use OG panels, so we can create various tabs and organize the > >>> front > >>> page to highlight things. > >>> > >>> I'd also like to figure out ways to get all of our info together > >>> without excessive cross-posting, if possible. ;-) > >>> > >>> We don't need a ton of people, but a few would be nice. If you > >>> are > >>> interested, please just respond to this thread by this Friday. > >>> Please > >>> also include your g.d.o username if you have one. Once we know > >>> who is > >>> here, we'll set up a time to dig in together. > >>> > >>> > >>> - Addi (add1sun) > >> > >> > >> -- > >> Pending work: http://drupal.org/project/issues/documentation/ > >> List archives: http://lists.drupal.org/pipermail/documentation/ > > > > > > -- > > Pending work: http://drupal.org/project/issues/documentation/ > > List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080920/f72a0208/attachment.htm From drupal at rocktreesky.com Sun Sep 21 16:48:05 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sun, 21 Sep 2008 12:48:05 -0400 Subject: [documentation] Getting involved sprint scheduling In-Reply-To: <19C98E1B-265B-4419-9BA3-88A30FA76A4E@rocktreesky.com> References: <19C98E1B-265B-4419-9BA3-88A30FA76A4E@rocktreesky.com> Message-ID: Sorry about posting this late. We'll go ahead and do two sprints this week to work on Getting Involved (we'll coordinate and discuss in the #drupal-docs IRC channel on the Freenode network): Tuesday, Sept. 23 from 20:00 - 23:00 GMT (4pm - 7pm EDT) Thursday, Sept 25 from 14:00 - 17:00 GMT (10am - 1pm EDT) We will basically focus our time on fleshing out the contrib redesign issues to identify where all of the "getting involved" docs are in the exsting handbooks. We will also try to fill in gaps that we find and finally, draft up the front page announcement about the new book. Feel free to swing by #drupal-docs at any point during those windows to help out for however long you happen to have available. Someone will be in the channel to answer questions during those windows. I'll post events on the group site later this evening. - Addi (add1sun) On Sep 16, 2008, at 9:46 AM, Addison Berry wrote: > The new Getting involved handbook needs some focused attention to get > it going. I'd like to create the book and announce it to the larger > community by Sept. 28. During the last IRC meeting we thought that > maybe a few short virtual sprints focused just on this task might help > since many folks aren't quite sure what needs to be done, or just have > a hard time setting time aside for it. > > I've set up a (large) Doodle at http://www.doodle.ch/participation.html?pollId=weeh8anybfx9fe54 > for folks to indicate times next week that would be good. We'll > schedule it out to overlap with as many people's schedules as we can. > I'll post the sprint schedule on this list and on g.d.o on September > 20. Keep in mind that the sprint times will be broad (2+ hours each) > but that each person can show up for whatever time they happen to have > available in the window; be it 15 minutes or 2 hours. > > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Wed Sep 24 12:38:33 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 24 Sep 2008 08:38:33 -0400 Subject: [documentation] Redesign Initial Information Architecture Message-ID: The redesign is moving along and they have posted some initial information architecture thoughts at http://www.disambiguity.com/drupalorg-initial-thoughts-on-the-information-architecture If you are interested in how the redesign will effect docs, please take a look. Of particular note, other than the previously discussed breaking out of sub-sites (of which docs is one) there is some interesting stuff on the placement of Getting started and Getting involved being on the main d.o site. Perhaps crossover with the doc site, or totally moved? Dunno. If you have thoughts or questions, please leave comments on the blog post (rather than here) so that the people who need to know can get your ideas. Thanks - Addi (add1sun) From drupal at rocktreesky.com Wed Sep 24 12:40:33 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 24 Sep 2008 08:40:33 -0400 Subject: [documentation] Recent updates, now with Diff! Message-ID: Hey all, just wanted to let everyone know that Moshe's patch to add a link to diffs on the recent updates page is in. Go check it out. :-) http://drupal.org/handbook/updates - Addi -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080924/9126ca5e/attachment.htm From drupal at rocktreesky.com Wed Sep 24 13:53:21 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 24 Sep 2008 09:53:21 -0400 Subject: [documentation] Which books/pages to restrict? Message-ID: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> Wheeee! Spamming the docs list today. :-) The move to open editing rights is going to be on us soon. The attendant issues are getting cleared up so once the Getting Involved book is done this weekend, we should turn our attention to preparing for opening edit rights. The last big task before we can is to identify what should be "locked" and only accessible to the docs team, and then change the input format for them. We have already talked about the Getting Started guide, but do we mean the whole book or just sections of it (like the version stuff and Features, mission, etc)? Are there other sections of the handbook we want to limit? I'd like to try to not limit very much stuff. The idea here is to let people help. :-) So, please respond with your thoughts so we can get a specific list of pages to locked. Thanks - Addi (add1sun) From nan_wich at bellsouth.net Wed Sep 24 14:37:01 2008 From: nan_wich at bellsouth.net (Nancy Wichmann) Date: Wed, 24 Sep 2008 10:37:01 -0400 Subject: [documentation] Which books/pages to restrict? In-Reply-To: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> Message-ID: Addison Berry wrote: > The last big task before we can is to identify what should be "locked" > and only accessible to the docs team, and then change the input format If our page already uses the "Documentation" format, is it already "locked?" Is this a way the author can set her/his pages to locked? Is there an easy way to get a list of all my handbook pages? Track is not adequate for this because it mixes all my issues into list. Nancy E. Wichmann, PMP -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: multipart/alternative Size: 0 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080924/23b6fbc5/attachment.bin -------------- next part -------------- No virus found in this outgoing message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.7.0/1685 - Release Date: 9/22/2008 4:08 PM From joelfarris at mac.com Wed Sep 24 16:34:50 2008 From: joelfarris at mac.com (Joel Farris) Date: Wed, 24 Sep 2008 09:34:50 -0700 Subject: [documentation] Which books/pages to restrict? In-Reply-To: References: Message-ID: <42CBD13C-7B26-467A-964E-36845DAD3179@mac.com> No, I don't thing there is. Not without a custom query, anyway. The best you're gonna get is the Top Contributors page at http://drupal.org/node/14205 which only helps you know how many of the little buggers you're looking for. -- Joel Farris "Drupal Core doesn't have bugs. It has unimplemented features." ~ wwwebernet On Sep 24, 2008, at 7:37 AM, Nancy Wichmann wrote: > Addison Berry wrote: >> The last big task before we can is to identify what should be >> "locked" >> and only accessible to the docs team, and then change the input >> format > > If our page already uses the "Documentation" format, is it already > "locked?" > Is this a way the author can set her/his pages to locked? > > Is there an easy way to get a list of all my handbook pages? Track > is not > adequate for this because it mixes all my issues into list. > > Nancy E. Wichmann, PMP > > > No virus found in this outgoing message. > Checked by AVG - http://www.avg.com > Version: 8.0.169 / Virus Database: 270.7.0/1685 - Release Date: > 9/22/2008 4:08 PM > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2419 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080924/5f4845ff/attachment-0001.bin From stella at stellapower.net Wed Sep 24 14:48:26 2008 From: stella at stellapower.net (Stella Power) Date: Wed, 24 Sep 2008 15:48:26 +0100 Subject: [documentation] Which books/pages to restrict? In-Reply-To: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> References: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> Message-ID: I think anything in relation to coding standards, etc, should be locked. I know the main coding standards page is in CVS and is therefore locked already, but most of the others aren't. Cheers, Stella On Wed, Sep 24, 2008 at 2:53 PM, Addison Berry wrote: > Wheeee! Spamming the docs list today. :-) > > The move to open editing rights is going to be on us soon. The > attendant issues are getting cleared up so once the Getting Involved > book is done this weekend, we should turn our attention to preparing > for opening edit rights. > > The last big task before we can is to identify what should be "locked" > and only accessible to the docs team, and then change the input format > for them. > > We have already talked about the Getting Started guide, but do we mean > the whole book or just sections of it (like the version stuff and > Features, mission, etc)? Are there other sections of the handbook we > want to limit? I'd like to try to not limit very much stuff. The idea > here is to let people help. :-) So, please respond with your thoughts > so we can get a specific list of pages to locked. > > Thanks > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080924/7853e15a/attachment.htm From joelfarris at mac.com Wed Sep 24 17:42:53 2008 From: joelfarris at mac.com (Joel Farris) Date: Wed, 24 Sep 2008 10:42:53 -0700 Subject: [documentation] Which books/pages to restrict? In-Reply-To: References: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> Message-ID: <0589B88E-5F75-493D-88BC-402552C22B89@mac.com> On Sep 24, 2008, at 7:48 AM, Stella Power wrote: > I think anything in relation to coding standards, etc, should be > locked. I know the main coding standards page is in CVS and is > therefore locked already, but most of the others aren't. > > Cheers, > Stella In addition to the Getting Started guide(s), and the Coding Standards guides, may I propose that the Programming Best Practices guide be locked? http://drupal.org/node/287350 is the developer's complement to http://drupal.org/best-practices , the latter of which already lives inside the Getting Started guide and thus would already be protected. On that note, are we locking individual nids, url paths, or input filters? I've totally forgotten what the plan was. -- Joel Farris "While it is possible that you are the first person to notice an obvious deficiency in system calls and libraries heavily used by hundreds or thousands of people, it is rather more likely that you are utterly clueless." ~ Eric S. Raymond -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2419 bytes Desc: not available Url : http://lists.drupal.org/pipermail/documentation/attachments/20080924/4f71ade6/attachment.bin From wolf.zirbs at gmail.com Wed Sep 24 19:28:01 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Wed, 24 Sep 2008 21:28:01 +0200 Subject: [documentation] Which books/pages to restrict? In-Reply-To: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> References: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> Message-ID: It would be carefully to lock "Terminology" http://drupal.org/node/937 and "Common expressions & acronyms used on D.O." http://drupal.org/node/302232 and ? "Drupal Jargon" http://drupal.org/node/122018 as for users, members, visitors can supply feedback and we do not risk to have to much spam and breaking layout on those pages. This because I suppose that the traffic on those reference will grow surely and also because the "Redesign-Team" will sure point a special attention to propose more accessibility to this kind of "Beginner Reference" On Wed, Sep 24, 2008 at 3:53 PM, Addison Berry wrote: > Wheeee! Spamming the docs list today. :-) > > The move to open editing rights is going to be on us soon. The > attendant issues are getting cleared up so once the Getting Involved > book is done this weekend, we should turn our attention to preparing > for opening edit rights. > > The last big task before we can is to identify what should be "locked" > and only accessible to the docs team, and then change the input format > for them. > > We have already talked about the Getting Started guide, but do we mean > the whole book or just sections of it (like the version stuff and > Features, mission, etc)? Are there other sections of the handbook we > want to limit? I'd like to try to not limit very much stuff. The idea > here is to let people help. :-) So, please respond with your thoughts > so we can get a specific list of pages to locked. > > Thanks > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080924/3fce304d/attachment.htm From drupal at rocktreesky.com Wed Sep 24 20:43:38 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Wed, 24 Sep 2008 16:43:38 -0400 Subject: [documentation] Which books/pages to restrict? In-Reply-To: <0589B88E-5F75-493D-88BC-402552C22B89@mac.com> References: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> <0589B88E-5F75-493D-88BC-402552C22B89@mac.com> Message-ID: <78A0061C-D4F8-409D-8115-D69CE5C33CEC@rocktreesky.com> We will need to change the input format to Documentation on every page that we want to restrict. On Sep 24, 2008, at 1:42 PM, Joel Farris wrote: > On Sep 24, 2008, at 7:48 AM, Stella Power wrote: > >> I think anything in relation to coding standards, etc, should be >> locked. I know the main coding standards page is in CVS and is >> therefore locked already, but most of the others aren't. >> >> Cheers, >> Stella > > > In addition to the Getting Started guide(s), and the Coding > Standards guides, may I propose that the Programming Best Practices > guide be locked? http://drupal.org/node/287350 is the developer's > complement to http://drupal.org/best-practices, the latter of which > already lives inside the Getting Started guide and thus would > already be protected. > > On that note, are we locking individual nids, url paths, or input > filters? I've totally forgotten what the plan was. > -- > Joel Farris > "While it is possible that you are the first person to notice an > obvious deficiency in system calls and libraries heavily used by > hundreds or thousands of people, it is rather more likely that you > are utterly clueless." > ~ Eric S. Raymond-- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From wolf.zirbs at gmail.com Wed Sep 24 21:14:07 2008 From: wolf.zirbs at gmail.com (Wolf Zirbs) Date: Wed, 24 Sep 2008 23:14:07 +0200 Subject: [documentation] Which books/pages to restrict? In-Reply-To: <78A0061C-D4F8-409D-8115-D69CE5C33CEC@rocktreesky.com> References: <1D42E164-62B5-437C-AC91-C798A12F90D7@rocktreesky.com> <0589B88E-5F75-493D-88BC-402552C22B89@mac.com> <78A0061C-D4F8-409D-8115-D69CE5C33CEC@rocktreesky.com> Message-ID: Ok, just to clear, If we Plan later to define a special Handbook "Section" for a "Terminology" reference for Drupal.org taking in consideration of the new "Redesign Project" we should consider to restrict modifications to the "Terminology" section only to "Site Maintainers". I also see the possibility to link many of the "Terminology" terms to descriptive images, tables, and "summary of content" best and simple informations "Handbook" pages that leads visitors to the aimed resources. Because of the importance of the "Terminology" Section and also that requires to have access to statistical informations to see where it needs to change, modify, improve linking to the right references I think that this "Terminology Section" should be accessible only to "Site Maintainers" I have no Idea how many page will come to consider to be part of this "Terminology Section" yet and also when this "project" will be discussed and reconsidered for valuable. I just continue to work on it and if there is at the moment no need to restrict access to this pages that's ok for me at the moment. List of pages to take in consideration to build/rebuild/improve in a "Terminology Section": http://drupal.org/node/937 http://drupal.org/node/302232 http://drupal.org/node/122018 On Wed, Sep 24, 2008 at 10:43 PM, Addison Berry wrote: > We will need to change the input format to Documentation on every page > that we want to restrict. > > > On Sep 24, 2008, at 1:42 PM, Joel Farris wrote: > > > On Sep 24, 2008, at 7:48 AM, Stella Power wrote: > > > >> I think anything in relation to coding standards, etc, should be > >> locked. I know the main coding standards page is in CVS and is > >> therefore locked already, but most of the others aren't. > >> > >> Cheers, > >> Stella > > > > > > In addition to the Getting Started guide(s), and the Coding > > Standards guides, may I propose that the Programming Best Practices > > guide be locked? http://drupal.org/node/287350 is the developer's > > complement to http://drupal.org/best-practices, the latter of which > > already lives inside the Getting Started guide and thus would > > already be protected. > > > > On that note, are we locking individual nids, url paths, or input > > filters? I've totally forgotten what the plan was. > > -- > > Joel Farris > > "While it is possible that you are the first person to notice an > > obvious deficiency in system calls and libraries heavily used by > > hundreds or thousands of people, it is rather more likely that you > > are utterly clueless." > > ~ Eric S. Raymond-- > > Pending work: http://drupal.org/project/issues/documentation/ > > List archives: http://lists.drupal.org/pipermail/documentation/ > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- Sincerely Best Regards Wolf J. Zirbs P.S. You may contact me by Mobil - Handy between 10am and 10pm Vienna Local Time (+43 676 9286735) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080924/ff9069a9/attachment-0001.htm From drupal at rocktreesky.com Thu Sep 25 18:50:57 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 25 Sep 2008 14:50:57 -0400 Subject: [documentation] Which books/pages to restrict? In-Reply-To: References: Message-ID: <0847D13E-65AF-416F-98BF-4B39426A63EF@rocktreesky.com> On Sep 24, 2008, at 10:37 AM, Nancy Wichmann wrote: > Addison Berry wrote: >> The last big task before we can is to identify what should be >> "locked" >> and only accessible to the docs team, and then change the input >> format > > If our page already uses the "Documentation" format, is it already > "locked?" > Is this a way the author can set her/his pages to locked? Yes the Documentation format will mean that regular authenticated users can't edit the page. You need to edit each page you wish to lock and set the format. I don't know of any other way to do it. That is why I'd like us to compile a list as a group and then run a little focused sprint to go through and set all of the ones we deem needing it so no one person is stuck with a hugely tedious task on their own. We should try, as much as possible, to identify "sections" to be locked rather than individual pages. We need to explain to people why they can't edit certain pages and "groups" or "types" of pages makes a lot more sense. Ones with images or tables is easy to explain. The Getting started guide is easy. Random individual pages with no images or tables in them is not so easy. > Is there an easy way to get a list of all my handbook pages? Track > is not > adequate for this because it mixes all my issues into list. No way that I know of right now without a custom DB query. You'd have to write up a query and post it to the infra queue to get someone with rights to run it for you. - Addi > > > Nancy E. Wichmann, PMP > > > No virus found in this outgoing message. > Checked by AVG - http://www.avg.com > Version: 8.0.169 / Virus Database: 270.7.0/1685 - Release Date: > 9/22/2008 4:08 PM > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Thu Sep 25 22:45:43 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Thu, 25 Sep 2008 18:45:43 -0400 Subject: [documentation] Log field now required on all edits Message-ID: <2DDC5864-78DB-4D0E-AD25-E83EF4190AC8@rocktreesky.com> Just to keep everyone up to date, thanks to oadaeh and dww, the log field is now required on all handbook page edits. http://drupal.org/node/308675 Try to keep 'em short and useful. If you are doing lots of minor tweaking to a page, feel free to use "Minor edits" or "Minor tweaks" but if you make real changes please say what they were. This is especially important if you move a page since diff won't show anything. - Addi (add1sun) From drupal at rocktreesky.com Sat Sep 27 11:35:30 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sat, 27 Sep 2008 07:35:30 -0400 Subject: [documentation] New vocabulary for handbook pages Message-ID: <51726982-4216-4A7D-A2D2-BEA950A2E0DB@rocktreesky.com> We've added a new vocabulary for handbook pages to indicate the status, pursuant to this issue: http://drupal.org/node/304826 It is under the existing Drupal version vocab on the node add/edit page and is optional. This will allow us to give some indication to folks of what is going on with the page as well as letting us create lists of pages that "need love". Please note that if you mark a page with Insecure code, you should unpublish the page until it gets fixed. Now that we have mandatory logs, that is a prime place to put an explanation of the reason for changing the status, if it isn't apparent. ;-) If you think that there are other tags which may be useful, please open a new issue in the webmasters queue. Thanks to all that help hash this one out. :-) - Addi (add1sun) From drupal at rocktreesky.com Sat Sep 27 14:53:53 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Sat, 27 Sep 2008 10:53:53 -0400 Subject: [documentation] Getting Involved book is born Message-ID: <4DCE1948-8E3B-475D-BDDC-A06365A4DECF@rocktreesky.com> I have gotten the bulk of moving and stub page creation done for the Getting Involved book. There is a list of issues with work still to do on the main landing page now: http://drupal.org/getting-involved. The most important tasks are getting incomplete pages filled out and continuing to reorganize the Contribute code section. i am going to keep chipping away at that over the weekend so if you would like to help with that, please coordinate with me. Thanks for everyone's help on this. We are almost there. :-) I will be in and out over the weekend but feel free to ping me if you have questions and use the #drupal-docs IRC channel to work on things together. Thanks - Addi (add1sun) From pwgdarchive at gmail.com Sun Sep 28 13:44:43 2008 From: pwgdarchive at gmail.com (=?ISO-8859-1?Q?Benjamin_Melan=E7on?=) Date: Sun, 28 Sep 2008 09:44:43 -0400 Subject: [documentation] New vocabulary for handbook pages In-Reply-To: <51726982-4216-4A7D-A2D2-BEA950A2E0DB@rocktreesky.com> References: <51726982-4216-4A7D-A2D2-BEA950A2E0DB@rocktreesky.com> Message-ID: <1406bb8f0809280644q4fe831r3119b050458d6e70@mail.gmail.com> Excellent! > Now that we have mandatory logs, that is a prime place to put an > explanation of the reason for changing the status, if it isn't > apparent. ;-) Or even if it is apparent :-) From hjames at gmail.com Mon Sep 29 01:14:53 2008 From: hjames at gmail.com (Heather) Date: Mon, 29 Sep 2008 01:14:53 +0000 Subject: [documentation] Getting Involved book is born In-Reply-To: <4DCE1948-8E3B-475D-BDDC-A06365A4DECF@rocktreesky.com> References: <4DCE1948-8E3B-475D-BDDC-A06365A4DECF@rocktreesky.com> Message-ID: <1002357056-1222651035-cardhu_decombobulator_blackberry.rim.net-831132815-@bxe070.bisx.produk.on.blackberry> I was looking for a page in Getting Involved on What is a good question, and What is a good thread title. (to direct someone to) There is sort of something in the IRC page, but I seem to remember having seen this... and cannot find it. I'd be glad to have a crack at it if there wasn't anything yet. But I just know there is. Thanks! - Heather -----Original Message----- From: Addison Berry Date: Sat, 27 Sep 2008 10:53:53 To: Subject: [documentation] Getting Involved book is born I have gotten the bulk of moving and stub page creation done for the Getting Involved book. There is a list of issues with work still to do on the main landing page now: http://drupal.org/getting-involved. The most important tasks are getting incomplete pages filled out and continuing to reorganize the Contribute code section. i am going to keep chipping away at that over the weekend so if you would like to help with that, please coordinate with me. Thanks for everyone's help on this. We are almost there. :-) I will be in and out over the weekend but feel free to ping me if you have questions and use the #drupal-docs IRC channel to work on things together. Thanks - Addi (add1sun) -- Pending work: http://drupal.org/project/issues/documentation/ List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Mon Sep 29 11:32:21 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 29 Sep 2008 07:32:21 -0400 Subject: [documentation] Getting Involved book is born In-Reply-To: <1002357056-1222651035-cardhu_decombobulator_blackberry.rim.net-831132815-@bxe070.bisx.produk.on.blackberry> References: <4DCE1948-8E3B-475D-BDDC-A06365A4DECF@rocktreesky.com> <1002357056-1222651035-cardhu_decombobulator_blackberry.rim.net-831132815-@bxe070.bisx.produk.on.blackberry> Message-ID: We do have the "tips for posting to the Drupal forums" http://drupal.org/forum-posting . Is that what you are looking for or is this something more general? - Addi (add1sun) On Sep 28, 2008, at 9:14 PM, Heather wrote: > > I was looking for a page in Getting Involved on What is a good > question, and What is a good thread title. (to direct someone to) > There is sort of something in the IRC page, but I seem to remember > having seen this... and cannot find it. > > I'd be glad to have a crack at it if there wasn't anything yet. But > I just know there is. > > Thanks! > > - Heather > > -----Original Message----- > From: Addison Berry > > Date: Sat, 27 Sep 2008 10:53:53 > To: > Subject: [documentation] Getting Involved book is born > > > I have gotten the bulk of moving and stub page creation done for the > Getting Involved book. There is a list of issues with work still to do > on the main landing page now: http://drupal.org/getting-involved. The > most important tasks are getting incomplete pages filled out and > continuing to reorganize the Contribute code section. i am going to > keep chipping away at that over the weekend so if you would like to > help with that, please coordinate with me. > > Thanks for everyone's help on this. We are almost there. :-) I will be > in and out over the weekend but feel free to ping me if you have > questions and use the #drupal-docs IRC channel to work on things > together. > > Thanks > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ From drupal at rocktreesky.com Mon Sep 29 14:57:54 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 29 Sep 2008 10:57:54 -0400 Subject: [documentation] Schedule October IRC meeting Message-ID: <63FB03E6-618E-469B-91CC-7F32ADEE11C5@rocktreesky.com> Hello all, Now that the Getting Involved book is started up, I wanted to set up a time for the next IRC meeting. Let' s shoot for something next week with the top agenda items being: 1. Wrap up discussion on Getting Involved. I hope we get a fair bit of cleanup done during this week but we should touch on important remaining items, if there are any. 2. Talk about opening the editing rights up. Two helper issues we wanted are now done and so we need to just get our ducks in a row before we flip the switch. We can talk about what ducks need ordering, what the change entails for the team and set a firm date. Here is ye old doodle to pick a time: http://www.doodle.ch/2rgcqb6tmmik2yck - Addi (add1sun) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080929/3890cbed/attachment-0001.htm From drupal at rocktreesky.com Mon Sep 29 15:01:36 2008 From: drupal at rocktreesky.com (Addison Berry) Date: Mon, 29 Sep 2008 11:01:36 -0400 Subject: [documentation] Schedule October IRC meeting In-Reply-To: <63FB03E6-618E-469B-91CC-7F32ADEE11C5@rocktreesky.com> References: <63FB03E6-618E-469B-91CC-7F32ADEE11C5@rocktreesky.com> Message-ID: <314E8E8E-3EF5-4391-87F4-2D826CD3F271@rocktreesky.com> Oops, I always forget to add the "info". The meeting will be for one hour in the #drupal-docs IRC channel on the Freenode network. On Sep 29, 2008, at 10:57 AM, Addison Berry wrote: > Hello all, > > Now that the Getting Involved book is started up, I wanted to set up > a time for the next IRC meeting. Let' s shoot for something next > week with the top agenda items being: > > 1. Wrap up discussion on Getting Involved. I hope we get a fair bit > of cleanup done during this week but we should touch on important > remaining items, if there are any. > 2. Talk about opening the editing rights up. Two helper issues we > wanted are now done and so we need to just get our ducks in a row > before we flip the switch. We can talk about what ducks need > ordering, what the change entails for the team and set a firm date. > > Here is ye old doodle to pick a time: http://www.doodle.ch/2rgcqb6tmmik2yck > > - Addi (add1sun) > > > > > > -- > Pending work: http://drupal.org/project/issues/documentation/ > List archives: http://lists.drupal.org/pipermail/documentation/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.drupal.org/pipermail/documentation/attachments/20080929/bcbe0386/attachment.htm From esmerel at logrus.com Mon Sep 29 16:46:44 2008 From: esmerel at logrus.com (Lynette) Date: Mon, 29 Sep 2008 09:46:44 -0700 Subject: [documentation] Schedule October IRC meeting In-Reply-To: <314E8E8E-3EF5-4391-87F4-2D826CD3F271@rocktreesky.com> References: <63FB03E6-618E-469B-91CC-7F32ADEE11C5@rocktreesky.com> <314E8E8E-3EF5-4391-87F4-2D826CD3F271@rocktreesky.com> Message-ID: <48E10674.80807@logrus.com> FYI, BADcamp is that weekend, so if the meeting ends up on the weekend itself, I'll try to attend, but I make no promises:) - Lynette