On Thu, 2010-07-22 at 15:27 +0200, david blanchard wrote: > - You can access it through here > (http://community.hackit.cx/wiki/Sandbox:Project#Production_follow-up ) to > check the new proposed structure of the wiki, or directly here : > http://community.hackit.cx/wiki/Tasks_follow-up
Cool, thanks! : ) > - I'm still unclear how to display tags. I'd like to use them for two things > : the milestone (alpha 1.2 in our case), and the feature to which the task > is related (for instance, 'leaderboard' or 'List of websites') - until now, > I've included the name of the feature in the title of the task. I've fixed the issue in your list description - the property name was "tag" instead of "tags". Btw, in addition to "tag", there is another field, "Project", that may be good to use too here, it would help to only use one field for one thing. We could have "tag" for the release name, and "project" for the feature it is related to. I've also added this: "See requirements and deliverables for patch submission to see the detail of what is expected for each patch/feature submission." - it's something important to keep in mind, and I'd like to make sure this is written explicitly on each list of features - this should avoid some bad surprises. > Is a tag a page on the wiki ? That would be good because if it's the case, > we can include the overall description of a feature in the page of the tag > that holds the name of the feature. I think it is, and that you can simply click on it to create the related page. > (by the way give me a hint, a first > link, on how to use this semantic thing, and I'll bother you less :)). Hop: http://semantic-mediawiki.org/wiki/Help:User_manual > - To avoid confusion and too many tools, I think we should remove the > milestones management from launchpad. We need it to handle bugs - they need to be targeted against specific releases. > For the blueprints I'm not sure because there might be some good practices > we want from Launchpad, but it > makes more sense to me to have the blueprint of the task in the task itself > on the wiki. And the overall description of the feature in the page of the > corresponding tag. What is your opinion ? Sounds good to me! > - Because the current tasks might not be enough for one complete iteration, > I was looking at uservoice to see what additional task we could add for this > milestone. The problem is that the features I see there are either 1) > postponed because they are related to strategy (we must think about what we > do with AIs first) 2) or not really urgent (and not voted for) according to > me, more like nice to have. So, given that we plan to have the missions in > the 1.3, I was wondering if we could cut the missions feature into blocks > and do a first block for the 1.2 - given that the missions is going to be a > big feature, it would give us more chances to have it done by the version > 1.3. What do you think ? Yup, I see - then probably the first thing is the Ajax chat feature, taken from ajaxim http://ajaxim.com/ The mission system relies heavily on it, and implementing it first as a chat (allowing to contact other players and having a common chatroom) would be very useful IMHO. Xavier. _______________________________________________ Hackit Bar mailing list - [email protected] Wiki: http://community.hackit.cx/ List: http://community.hackit.cx/ml/ Forum: http://community.hackit.cx/forum/ Ideas: http://community.hackit.cx/ideas/ IRC: irc://irc.freenode.net/#politis
