Funny you should bring this up. Gary and I had a discussion in Breeze about the exact same thing.
I think the Current Needs page is malleable and can be whatever we want it to. I'm all for keeping the admin overhead low, so perhaps keeping all the content confined to a single page is the best approach. Labels are great, but it adds another thing for Wiki authors to remember when authoring content. - Jonathan. --- Jonathan Hung / [EMAIL PROTECTED] University of Toronto - ATRC Tel: (416) 946-3002 2008/7/18 Jess Mitchell <[EMAIL PROTECTED]>: > I was equally worried about this, but impressed by the functionality. I'm > less impressed if it causes additional administrative overhead. Can the > page support both? In other words, if someone makes a fully-contextualized > page explaining the current need and labels it, it will appear -- and if > someone just edits the "current needs" page it will also appear? > J > > > ~~~~~~~~~~~~~~~~~~~~~~ > Jess Mitchell > Project Manager / Fluid Project > [EMAIL PROTECTED] > / w / 617.326.7753 / c / 919.599.5378 > jabber: [EMAIL PROTECTED] > http://www.fluidproject.org > ~~~~~~~~~~~~~~~~~~~~~~ > > > > On Jul 18, 2008, at 3:23 PM, Daphne Ogle wrote: > > I just added some things to the current needs page. > While there I noticed that some of the categories of work are being filled > by adding labels to pages like user testing and design overviews. My > question is do we want to give more context about the work we'd like to have > done than just a pointer to a page? I feel like we do. I'm all for having > information automatically updated on the wiki but I'm also a little > concerned about using labels in this. It means that in order to keep the > current needs page up to date, people need to remember to change labels on > individual pages and I could see at least myself not remembering to remove > the "needs work" label. > > What do others think? > > -Daphne > > On Jul 16, 2008, at 8:12 AM, Jess Mitchell wrote: > > Dear All, > I just wanted to put a reminder out there about a few things that have no > doubt flown past you in the last few weeks, but deserve further mention: > > 1. We're working in JIRA this iteration (both developer and designer > iterations) and we'll benefit from keeping JIRA updated to reflect what > we're doing, what we're completing, and what our priorities are. > 2. Also, there's a great wiki page for any current needs we feel volunteers > could help out with. Take a second to add anything you've got on your > mind... > http://wiki.fluidproject.org/display/fluid/Current+Needs > > Best, > Jess > ~~~~~~~~~~~~~~~~~~~~~~ > Jess Mitchell > Project Manager / Fluid Project > [EMAIL PROTECTED] > / w / 617.326.7753 / c / 919.599.5378 > jabber: [EMAIL PROTECTED] > http://www.fluidproject.org > ~~~~~~~~~~~~~~~~~~~~~~ > > > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > > > Daphne Ogle > Senior Interaction Designer > University of California, Berkeley > Educational Technology Services > [EMAIL PROTECTED] > cell (510)847-0308 > > > > > > _______________________________________________ > fluid-work mailing list > [email protected] > http://fluidproject.org/mailman/listinfo/fluid-work > >
_______________________________________________ fluid-work mailing list [email protected] http://fluidproject.org/mailman/listinfo/fluid-work
