On 6/26/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 25 Jun 07, at 7:11 PM 25 Jun 07, John Casey wrote: > I like this approach, and I think it's just a slightly more > detailed version > of what some of us are already trying to do when we put together > major new > pieces for Maven. I agree with Eric that any API or behavioral > change should > probably follow this process, basically anything that could change > what the > user experiences. > Yah, really just to surface the information. I know that there are only a few of us know where everything is because we look at it everyday but the casual contributor wouldn't have a chance. I think this really facilitates contribution. Someone who has a particular need can see if there is anything vaguely related to what he needs.
agreed, so much of this material been beat around on irc and the back rooms of sleazy gin joints around the world...its good to get it all formally pulled into one area.. What would be the mechanism for ranking these in terms of priority or popularity or is that an concept we don't want to apply at this phase? My primary concern would be that given the wide variety of communication channels that maven folks operate under is this material becoming old or stale. Wiki's are notoriously easy to let languish. There has to be a concerted effort to make one place be the final resting place of all this sort of information. Its super easy to pay lipservice to this, 'oh, I'll just have the conversation on irc, or the mailing list and go back and update that wiki page later' and not follow through... of course, my stated primary concern there doesn't offer a better solution or alternative...just stating the obvious a bit anyway, +1, I like it :) -- jesse mcconnell [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
