RE: [hackers] Notes From Meeting
I want to pile on to Lynn's question. I haven't seen what she's been writing, yet, but I believe it is really crucial. I've been working on making my site something that would be good for the State of Connecticut. As I've worked on it a little, I've been thinking about the sort of questions that I imagine Lynn will have to answer. 1) How do I make the site look the way I want? I imagine a start to this question talks about Themes, lists the themes that have been developed etc. One question it leads to is: 1a) How do I get other themes? A pointer on how to get the themes, how to unpack them, where to store them, how to turn them on and how to make them defaults needs to be described. 2) I really like the (whichever) theme, but I really want my site to have a graphic specific to my state (group, whatever). How do I change the graphic for (whichever) theme. I imagine comments about the graphic for each theme is stored under drupal/themes/(themename)/images It might be nice to list what the key images for each theme are, as well as recommended sizes if you want to replace them. In my case, I create an Aldon4Dean theme as an early test. It turns out that replacing header.jpg had it particularly easy to make my theme State specific. As a side question, should we recommend that themes use specific names to make such changes easier? 3) The page looks good for me, but when my friend logs in, she just gets 'not authorized' (or whatever that message is. How do I set up permissions some everyone can see what I want them to, and a few people can even get in and change it? A simple description of user roles and permissions needs to be provided. 4) Okay, now that I have the general page layout looking the way I want, should I use books, stories, blog entries, static pages, or what to store my content. Personally, I'm still trying to decide this myself. I would love to hear other peoples comments on that. I'm still experimenting. 5) Related to that, if I want to allow others to write stuff, should I use blogs? Forums? or what? My guess is that this ends up being a personal preference. I've done a little with blogs in drupal. They seem to fit in very nicely. I've also set up a forum, and they seem to appeal to a different type of audience. You might want to use one, the other, both, or none. What are others thinking about how people can write stuff? 5a) How do I set up forums? To the extent that you want to set up forums, you need to understand taxonomy. I managed to find my way through this with some experimentation, but it was too much for my wife and I imagine it is likely to be a bit much for other admins. 6) How do I get specific information to be on the side of every page? Here, blocks need to be explained, and especially, creating new blocks. In particular, creating a block that has an image, which links to some other site (e.g. back to the dfa site, or to the meetup site) should be explained. 7) Hey, this is starting to look like something. I've heard that there is some way to pull in articles from other sites. Something called Syndication. How does that work? I think it is important to have information on how to pull in a single site, how to pull in multiple sites, and perhaps even, explain how to link in Yahoo Groups. My concern here, is that I've done this using the standard syndication functionality. This uses 'bundles' and works quite well for my purposes. It seems that the proposed new import module works a bit different, and requires taxonomy, and also really needs some way of keeping the feeds from over running the server. The old version apparently deletes anything except the most recent 50 items from the feeds. 7a) I think the feeds are set up, but they aren't updating automatically. How do I get that to work? Talk about how to get cron running. Like with other areas, this should include both a Unix appraoch and a Windows approach. 8) Of course this leads to, I hear that the folks at DeanSpace have written, and are continuing to write a lot of neat addtions to Drupal. How do I get them and load them on my system? Describe a repository that is simple to use. CVS, SourceForge, etc, are probably a bit much. Also, we probably need to make sure we have modules (and themes) both as tarballs, but also as ZIP files for the Windows users. I think this covers a lot of the issues that I've run into so far. I would love to hear other peoples comments. I would also like to encourage people to consider helping get initial sites up and running now. I think it will help formulate the real issues, as well as get some sites running. Comments? Aldon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joshua Koenig Sent: Saturday, August 02, 2003 12:21 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [hackers] No
Re: [hackers] Notes From Meeting
When I was writing documentation, I made a different list. I looked at the module page from the perspective: "what features will help build community." i.e. relationships between data and between people The list is on: Configure Drupal http://deanspace.org/node/view/67 I expect that this list, made in the wee hours, will probably be changed: blog comment - allows users to comment on nodes drupal - allows id transfer between sites help - might help the grandmas before coming to the help desk import - aggregation - though we're creating a supped up version, locale - enables translation (hope all of the developers are using the t function to allow this to work!) node - allows core content to be contributed page - same as above, probably only give permissions to administrators though ping - think trackback profile search statistics - to help admins story - user submission (we're going to have to explain the differen to people in laymens terms) taxonomy tracker - what better for community than to read one article, then click to find all the other stuff they've written recently? Forum should be added to this list along with an explanation of forum/mailing list issues. Not sure if book is essential unless we want to promote each site making it's own Campaign Diary - How Dean Won Lake County. I would hope that work like "How to Outreach Offline" et cetera would be centrally located so there aren't 5,000 versions for people to try to collect ideas from. ~Alison > > Excellent point Lynn. I think the stock drupal modules we're including > are: > > - forum > - blog > - profile (which will be modded) > - book > - poll > > We may want to include more and/or have some of the above installed but > "turned off" by default in our kit. This will allow administrators to > add functionality not by installing anything, but by activating what > already shipped with their kit. > > cheers > -josh > >>> 7) Setting milestones >>> DRUPAL/KIT: >>> - A vanilla release >>> - Feature list: >>> - endorse >>> - event (calendar) >>> - export (rss transmitter) >>> - import (rss recieving) >>> - mailinglist (mailing lists) >>> - make_block (makes a node into a block) >>> - postcard (ecard/graphic endorsement) >> >> Sorry to be so late on this--this has been Hell Week. These are the >> features >> we're writing, basically; what about "native" drupal modules already >> extant >> in the vanilla kit and encourage admins to enable? Are we going to >> ship with >> forum? blog? weblink? book? profile? poll? wha? Is it more a matter of >> stripping some modules out? Just trying to figure out what us tech >> writers >> have got to explain. >> >> Lynn S. >> >> >> > > Politics is the art of controlling your environment. Participate! > Elect Howard Dean President in 2004! > http://www.outlandishjosh.com/politics/dean/ -- "...somebody came along and said liberal means soft on crime, soft on drugs, soft on Communism, soft on defense. And we're going to tax you back to the stone age because people shouldn't have to work if they don't want to. And instead of saying 'Well, excuse me, you right-wing reactionary, xenophobic, homophobic, anti-education, anti-choice, pro-gun Leave it to Beaver trip back to the '50s'. We cowered in the corner and say, 'Please don't hurt me'. . . . Let's have two parties. . . ." The West Wing: "Gone Quiet"
Re: [hackers] Notes From Meeting
Excellent point Lynn. I think the stock drupal modules we're including are: - forum - blog - profile (which will be modded) - book - poll We may want to include more and/or have some of the above installed but "turned off" by default in our kit. This will allow administrators to add functionality not by installing anything, but by activating what already shipped with their kit. cheers -josh 7) Setting milestones DRUPAL/KIT: - A vanilla release - Feature list: - endorse - event (calendar) - export (rss transmitter) - import (rss recieving) - mailinglist (mailing lists) - make_block (makes a node into a block) - postcard (ecard/graphic endorsement) Sorry to be so late on this--this has been Hell Week. These are the features we're writing, basically; what about "native" drupal modules already extant in the vanilla kit and encourage admins to enable? Are we going to ship with forum? blog? weblink? book? profile? poll? wha? Is it more a matter of stripping some modules out? Just trying to figure out what us tech writers have got to explain. Lynn S. Politics is the art of controlling your environment. Participate! Elect Howard Dean President in 2004! http://www.outlandishjosh.com/politics/dean/
Re: [hackers] Notes From Meeting
> 7) Setting milestones > DRUPAL/KIT: > - A vanilla release > - Feature list: > - endorse > - event (calendar) > - export (rss transmitter) > - import (rss recieving) > - mailinglist (mailing lists) > - make_block (makes a node into a block) > - postcard (ecard/graphic endorsement) Sorry to be so late on this--this has been Hell Week. These are the features we're writing, basically; what about "native" drupal modules already extant in the vanilla kit and encourage admins to enable? Are we going to ship with forum? blog? weblink? book? profile? poll? wha? Is it more a matter of stripping some modules out? Just trying to figure out what us tech writers have got to explain. Lynn S.
RE: [hackers] Notes From Meeting
A few comments from my side. First, I'm sorry I had to idle when you got around to talking about migrating Wikki to DeanSpace. I don't know the particulars of my schedule this weekend. I have to spend some time with kids and grandparents, etc. However, the goal of Porting the Wikki starting sometime Friday, and having it done by the end of the weekend seems very reasonable. My expectation is that it is likely to be a page at a time. As such, instead of blacking out updates on the Wikki as a whole, my thought would be to black out pages at a time. e.g. As a page starts to be migrated, put in a header "Please do not update this page, it is currently being migrated" and when the migration is done, changing the header to "Please do not update this page, it has been migrated to http://www.deanspace.com/?q=node/view/23"; I do have a few concerns about the migration. My Drupal experience is okay, but not great, so I might not be thinking of the best way to do this. Suggestions are encouraged. My guess is that the Wikki becomes a Collaborative book. Is this right or is there a better way? My guess is that I will need to translate the Wikki codes into HTML. Again, is this right, or can Drupal support Wikki code? I'm not sure how best to do the links. One of the things I like best about Wiki is it's ability to automaticially link. Is there an equivalent in Drupal? Anyone have any other ideas on how best to migrate? I have started giving the migration a test in my sandbox. Go to http://ahynes1.homeip.net:8180/drupal/index.php?q=node/view/25 to take a look and to provide any comments. Aldon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Joshua Koenig Sent: Thursday, July 31, 2003 12:28 AM To: [EMAIL PROTECTED] Subject: [hackers] Notes From Meeting Here are the high points from tonights IRC meeting; it was long but productive. Mostly I've taken note of things that seem "actionable" or which affect our immediate progress. The most important thing that happened was a hashing out of our "vanilla" site kit feature list. This is what we're working towards for releast ASAP. The High Points 1) LynnS needs a module list and a central place to store documentation. Drumm suggests the book module. A feature-list was decided on later in the meeting (see below). 2) Zacker points out that there's already been some talk about install scripts and that some people have volunteered to coordinate. http://www.hack4dean.org/phpwiki/index.php?InstallationScripting 3) Josh_k would like a mailing list or something similar to help organize the MetaDean crew. Ditto for DeanSter. These will go up along with the new DeanSpace home for 4) eponics suggest a "fixed" taxonomy for the kit, ping suggests the same for people's interests/skills on deanster. The kit vanilla taxonomy (and other vanilla concerns) will be discussed on sunday at 3pm EST in the IRC channel. 5) Madoc volunteers to be a press/PR coordinator; he will post things to the wiki for collab-edit and send pointers to the wiki to an editorial-committee mailing list. 6) Milestones: people will self-set specific milestones. We will agree on general milestones in meetings, and rely on people to report on progress. We also need to be mindful of "external" milestones. - Zack will be a "nudger". - Jeffk points us to phpCollab: http://phpcollab.sourceforge.net/ - Ping suggests our milestones be specific - Zephyr points out that having a reliable sense of when things will be done is very important for the campaign - aldon: milestones should be tied to the needs of others 7) Setting milestones DRUPAL/KIT: - A vanilla release - Feature list: - endorse - event (calendar) - export (rss transmitter) - import (rss recieving) - mailinglist (mailing lists) - make_block (makes a node into a block) - postcard (ecard/graphic endorsement) - Not included: - Action (may end up being part of DeanSter) - Media (not necessary, potential hold-up)) - Needs tech support to be ready 8) DeanSpace: - Polycot is donating server jail. THANKS! - Neil is admin - He'll be around IRC and IM tomorrow as the site goes up - Josh, Zack, Madoc will work site copy - Aldon has volunteered to port the wiki - Neil will hack up a quick template, ask list for more support - Timeline for switch-over of h4d activity: site ready for migration on friday, migration finished by midnight sunday. Aldon will set blackout dates for wiki migration.
[hackers] Notes From Meeting
Here are the high points from tonights IRC meeting; it was long but productive. Mostly I've taken note of things that seem "actionable" or which affect our immediate progress. The most important thing that happened was a hashing out of our "vanilla" site kit feature list. This is what we're working towards for releast ASAP. The High Points 1) LynnS needs a module list and a central place to store documentation. Drumm suggests the book module. A feature-list was decided on later in the meeting (see below). 2) Zacker points out that there's already been some talk about install scripts and that some people have volunteered to coordinate. http://www.hack4dean.org/phpwiki/index.php?InstallationScripting 3) Josh_k would like a mailing list or something similar to help organize the MetaDean crew. Ditto for DeanSter. These will go up along with the new DeanSpace home for 4) eponics suggest a "fixed" taxonomy for the kit, ping suggests the same for people's interests/skills on deanster. The kit vanilla taxonomy (and other vanilla concerns) will be discussed on sunday at 3pm EST in the IRC channel. 5) Madoc volunteers to be a press/PR coordinator; he will post things to the wiki for collab-edit and send pointers to the wiki to an editorial-committee mailing list. 6) Milestones: people will self-set specific milestones. We will agree on general milestones in meetings, and rely on people to report on progress. We also need to be mindful of "external" milestones. - Zack will be a "nudger". - Jeffk points us to phpCollab: http://phpcollab.sourceforge.net/ - Ping suggests our milestones be specific - Zephyr points out that having a reliable sense of when things will be done is very important for the campaign - aldon: milestones should be tied to the needs of others 7) Setting milestones DRUPAL/KIT: - A vanilla release - Feature list: - endorse - event (calendar) - export (rss transmitter) - import (rss recieving) - mailinglist (mailing lists) - make_block (makes a node into a block) - postcard (ecard/graphic endorsement) - Not included: - Action (may end up being part of DeanSter) - Media (not necessary, potential hold-up)) - Needs tech support to be ready 8) DeanSpace: - Polycot is donating server jail. THANKS! - Neil is admin - He'll be around IRC and IM tomorrow as the site goes up - Josh, Zack, Madoc will work site copy - Aldon has volunteered to port the wiki - Neil will hack up a quick template, ask list for more support - Timeline for switch-over of h4d activity: site ready for migration on friday, migration finished by midnight sunday. Aldon will set blackout dates for wiki migration.
