I'm a fan of Trac, which is one incarnation of Wiki+Tracking+Planning. I've set up a repo here:
http://github.com/dchenbecker/LiftTicket My preference is for this to be an issue tracking system first and a Wiki/CMS second, but I'm open to any and all ideas on how this can be fleshed out. I would also like to plan on doing a couple of iterations to get it all working. I like Marius' list of features but I'd like to start with a subset of those and expand it. My first "milestone" would be getting it to the point where it could self-host its own planning for enhancements and bug tracking, and I think I can do that with a small set of initial features. Derek On Sat, Oct 24, 2009 at 9:17 PM, Naftoli Gugenheim <naftoli...@gmail.com>wrote: > > How about we integrate the wiki, blog, forum, and issue tracker into the > CMS? ;) > Seriously, maybe it would be a good idea to create a repo and list, and > start serious discussion on all aspects of its design. Maybe it could become > a big community project, with lots of feedback to Lift. > > > ------------------------------------- > jlist9<jli...@gmail.com> wrote: > > > CMS, wiki, blog, forum also sound more interesting than bug tracking > system to me :-) > > On Sat, Oct 24, 2009 at 11:13 AM, aw <anth...@whitford.com> wrote: > > > > I don't mean to be negative, but are other options being considered > > besides a ticketing system? I kind of wonder if the effort is worth > > it when excellent alternatives exist (like JIRA -- their Git > > integration may interest you: > https://plugins.atlassian.com/plugin/details/4984 > > -- I have used their Subversion integration and was very pleased). > > > > I would be far more interested in seeing something done for the > > benefit of the Lift Web Site. (Is it written with Lift?) I don't see > > a Lift CMS -- and that is something that could evolve well over time. > > I think it is important for a web framework to use their own stuff, > > and it should be indicative of the cool things that it can do, > > stability, scale, and performance... (I am amazed that I have seen > > rather poor demonstrations of this, specifically by Adobe and JBoss -- > > but again, I'm not trying to be negative...) > > > > I see the Lift site integrating Google Analytics... Is that something > > that could be "out of the box" with Lift? That could be a selling > > point to people making external web sites. > > > > Another area that would be neat to develop is instrumentation. Sort > > of the JMX-Console equivalent for Lift. For scalability and sizing > > analysis, this would be really useful. > > > > > > Having said that, one major feature that I feel is missing from github > > is the lack of attachments for an issue. How do you attach test cases > > or patches for an issue? > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
