[Lift] Re: Proposal : Lift ticketing system
On 29/10/2009 15:07, george wrote: > > The things I find really useful in redmine are: [...] > - the git integration. For what it worth, Redmine + git + gitosis is my forge of choice nowaday, for internal needs. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
The things I find really useful in redmine are: - the contextual menu when you right click an issue. Speeds up quite a few actions by reducing clicks. http://www.redmine.org/projects/redmine/issues - the git integration. You can update the status of your issues by putting keywords in the commit message http://www.redmine.org/wiki/redmine/RedmineSettings#Referencing-issues-in-commit-messages george --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
If you use SQL Server there's a program called xSql Object that's great for migrating schemas. But if you need to migrate data along with the schema it could probably get very tricky, I'm guessing, depending on how big of a change. Like, once you add custom fields will you change the "special" fields to be like built in custom fields? If you do you will eliminate coding special cases everywere but it will be harder to upgrade the database. Anyway, how many different screens will there be? What areas do you anticipate being tricky? Technically a milestone could be a basically useable app consisting of a list of all tickets and a screen to edit them using the mapper's toForm -- or could it? - Derek Chen-Becker wrote: I had actually thought about the upgrade paths for DB schemas and I was thinking of coding up a schema executor that would store a schema version in the db and could then be used to apply appropriate "diff" or "clean" schemas against the DB as needed. I think schemifier generally does a very good job, but this would give more control over exactly what's going on in the DB. As for the custom fields, I think it sounds interesting but I think I want to start with the basic fields as I have them defined and I can look at it more in phase 2. Derek On Wed, Oct 28, 2009 at 3:20 PM, Naftoli Gugenheim wrote: > > I hear that. > Personally I think it would be more maintainable, not less; there's just a > bit more upfront complexity, although it's something I've already done and I > can share my code. You could trivially have flexible user-defined fields. In > my project you can edit the fields and the lookup tables via the web > interface. > Another consideration is, if you add more hardcoded MappedFields at some > point and a user installs the new version, it will have to schemify. So > you're running Schemifier on a populated production database. There isn't > necessarily anything wrong with that though. (Although recently I corrupted > a database that way: maven had upgraded H2 to a newer beta, which thought my > tables didn't exist. So Schemifier created new ones, wiping it out!) > But again, it depends what you want it to be. > > > - > Derek Chen-Becker wrote: > > The goal is to have a system that we can use for Lift's issue tracking. I > don't know that it has to be as big and bad as, say, JIRA, but it needs to > work well, have a reasonable set of features, and be usable by other people > if they want it. I'm open to suggestions on architecture, but at this point > I would like to keep things relatively simple so that this doesn't grow > into > something that I can't finish. > > Derek > > On Wed, Oct 28, 2009 at 2:39 PM, Naftoli Gugenheim >wrote: > > > > > What is the goal of this system? Is it to be a nice, useful ticketing > > system that will serve as a demo to Lift? Or is it also to be a product > that > > will eventually compete with other issue trackers such as Lift? > > If you're thinking big then I would suggest to think in terms of > > flexibility and extensibility. In particular I would not hard code > > attributes of the ticket but, at the cost of more starting complexity, I > > would have the fields be looked up in a table. I have done this more or > less > > in two projects. It's tricky with Mapper but when you get it right is > very > > powerful. I'll try to upload my code later this week if you wish. > Basically > > the idea is that you have a table or tables of fields. Fields come in > > different types, including lookup, which is what priority would be, > except > > that instead of the choices being hard coded they are in a table that is > > editable. So lookup fields specify a lookup table. There can be number > > fields, etc. This way plugins can add fields. For example Trac has a > plugin > > that tracks hours. Of course you could just include every single possible > > field hard coded. It all depends what you're aiming for. > > > > > > > > - > > Derek Chen-Becker wrote: > > > > OK, I just pushed the initial revision of my model to GitHub at > > http://github.com/dchenbecker/LiftTicket. I think that this covers most > of > > the features that Marius discussed in his response. I agree with all of > it, > > although I'm not 100% sure about having both a severity and priority > field > > on the ticket. This was kind of a code vomit, so I'm going to split the > > classes out into separate Scala files once I get some feedback and a > better > > idea of what needs to be done. > > > > Cheers, > > > > Derek > > > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > > wrote: > > > > > 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 a
[Lift] Re: Proposal : Lift ticketing system
Thanks, I've never seen that before. I'll take a look at it. If you've used it, are there any features that it has that you really like? On Thu, Oct 29, 2009 at 4:11 AM, george wrote: > > It might be worth taking a look at Redmine (http://www.redmine.org) > for some inspiration. > > I think it has the features you want and a very nice, simple UI. > > george > > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
It might be worth taking a look at Redmine (http://www.redmine.org) for some inspiration. I think it has the features you want and a very nice, simple UI. george --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
I had actually thought about the upgrade paths for DB schemas and I was thinking of coding up a schema executor that would store a schema version in the db and could then be used to apply appropriate "diff" or "clean" schemas against the DB as needed. I think schemifier generally does a very good job, but this would give more control over exactly what's going on in the DB. As for the custom fields, I think it sounds interesting but I think I want to start with the basic fields as I have them defined and I can look at it more in phase 2. Derek On Wed, Oct 28, 2009 at 3:20 PM, Naftoli Gugenheim wrote: > > I hear that. > Personally I think it would be more maintainable, not less; there's just a > bit more upfront complexity, although it's something I've already done and I > can share my code. You could trivially have flexible user-defined fields. In > my project you can edit the fields and the lookup tables via the web > interface. > Another consideration is, if you add more hardcoded MappedFields at some > point and a user installs the new version, it will have to schemify. So > you're running Schemifier on a populated production database. There isn't > necessarily anything wrong with that though. (Although recently I corrupted > a database that way: maven had upgraded H2 to a newer beta, which thought my > tables didn't exist. So Schemifier created new ones, wiping it out!) > But again, it depends what you want it to be. > > > - > Derek Chen-Becker wrote: > > The goal is to have a system that we can use for Lift's issue tracking. I > don't know that it has to be as big and bad as, say, JIRA, but it needs to > work well, have a reasonable set of features, and be usable by other people > if they want it. I'm open to suggestions on architecture, but at this point > I would like to keep things relatively simple so that this doesn't grow > into > something that I can't finish. > > Derek > > On Wed, Oct 28, 2009 at 2:39 PM, Naftoli Gugenheim >wrote: > > > > > What is the goal of this system? Is it to be a nice, useful ticketing > > system that will serve as a demo to Lift? Or is it also to be a product > that > > will eventually compete with other issue trackers such as Lift? > > If you're thinking big then I would suggest to think in terms of > > flexibility and extensibility. In particular I would not hard code > > attributes of the ticket but, at the cost of more starting complexity, I > > would have the fields be looked up in a table. I have done this more or > less > > in two projects. It's tricky with Mapper but when you get it right is > very > > powerful. I'll try to upload my code later this week if you wish. > Basically > > the idea is that you have a table or tables of fields. Fields come in > > different types, including lookup, which is what priority would be, > except > > that instead of the choices being hard coded they are in a table that is > > editable. So lookup fields specify a lookup table. There can be number > > fields, etc. This way plugins can add fields. For example Trac has a > plugin > > that tracks hours. Of course you could just include every single possible > > field hard coded. It all depends what you're aiming for. > > > > > > > > - > > Derek Chen-Becker wrote: > > > > OK, I just pushed the initial revision of my model to GitHub at > > http://github.com/dchenbecker/LiftTicket. I think that this covers most > of > > the features that Marius discussed in his response. I agree with all of > it, > > although I'm not 100% sure about having both a severity and priority > field > > on the ticket. This was kind of a code vomit, so I'm going to split the > > classes out into separate Scala files once I get some feedback and a > better > > idea of what needs to be done. > > > > Cheers, > > > > Derek > > > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > > wrote: > > > > > 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, > a
[Lift] Re: Proposal : Lift ticketing system
I hear that. Personally I think it would be more maintainable, not less; there's just a bit more upfront complexity, although it's something I've already done and I can share my code. You could trivially have flexible user-defined fields. In my project you can edit the fields and the lookup tables via the web interface. Another consideration is, if you add more hardcoded MappedFields at some point and a user installs the new version, it will have to schemify. So you're running Schemifier on a populated production database. There isn't necessarily anything wrong with that though. (Although recently I corrupted a database that way: maven had upgraded H2 to a newer beta, which thought my tables didn't exist. So Schemifier created new ones, wiping it out!) But again, it depends what you want it to be. - Derek Chen-Becker wrote: The goal is to have a system that we can use for Lift's issue tracking. I don't know that it has to be as big and bad as, say, JIRA, but it needs to work well, have a reasonable set of features, and be usable by other people if they want it. I'm open to suggestions on architecture, but at this point I would like to keep things relatively simple so that this doesn't grow into something that I can't finish. Derek On Wed, Oct 28, 2009 at 2:39 PM, Naftoli Gugenheim wrote: > > What is the goal of this system? Is it to be a nice, useful ticketing > system that will serve as a demo to Lift? Or is it also to be a product that > will eventually compete with other issue trackers such as Lift? > If you're thinking big then I would suggest to think in terms of > flexibility and extensibility. In particular I would not hard code > attributes of the ticket but, at the cost of more starting complexity, I > would have the fields be looked up in a table. I have done this more or less > in two projects. It's tricky with Mapper but when you get it right is very > powerful. I'll try to upload my code later this week if you wish. Basically > the idea is that you have a table or tables of fields. Fields come in > different types, including lookup, which is what priority would be, except > that instead of the choices being hard coded they are in a table that is > editable. So lookup fields specify a lookup table. There can be number > fields, etc. This way plugins can add fields. For example Trac has a plugin > that tracks hours. Of course you could just include every single possible > field hard coded. It all depends what you're aiming for. > > > > - > Derek Chen-Becker wrote: > > OK, I just pushed the initial revision of my model to GitHub at > http://github.com/dchenbecker/LiftTicket. I think that this covers most of > the features that Marius discussed in his response. I agree with all of it, > although I'm not 100% sure about having both a severity and priority field > on the ticket. This was kind of a code vomit, so I'm going to split the > classes out into separate Scala files once I get some feedback and a better > idea of what needs to be done. > > Cheers, > > Derek > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > wrote: > > > 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 >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 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 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
[Lift] Re: Proposal : Lift ticketing system
The goal is to have a system that we can use for Lift's issue tracking. I don't know that it has to be as big and bad as, say, JIRA, but it needs to work well, have a reasonable set of features, and be usable by other people if they want it. I'm open to suggestions on architecture, but at this point I would like to keep things relatively simple so that this doesn't grow into something that I can't finish. Derek On Wed, Oct 28, 2009 at 2:39 PM, Naftoli Gugenheim wrote: > > What is the goal of this system? Is it to be a nice, useful ticketing > system that will serve as a demo to Lift? Or is it also to be a product that > will eventually compete with other issue trackers such as Lift? > If you're thinking big then I would suggest to think in terms of > flexibility and extensibility. In particular I would not hard code > attributes of the ticket but, at the cost of more starting complexity, I > would have the fields be looked up in a table. I have done this more or less > in two projects. It's tricky with Mapper but when you get it right is very > powerful. I'll try to upload my code later this week if you wish. Basically > the idea is that you have a table or tables of fields. Fields come in > different types, including lookup, which is what priority would be, except > that instead of the choices being hard coded they are in a table that is > editable. So lookup fields specify a lookup table. There can be number > fields, etc. This way plugins can add fields. For example Trac has a plugin > that tracks hours. Of course you could just include every single possible > field hard coded. It all depends what you're aiming for. > > > > - > Derek Chen-Becker wrote: > > OK, I just pushed the initial revision of my model to GitHub at > http://github.com/dchenbecker/LiftTicket. I think that this covers most of > the features that Marius discussed in his response. I agree with all of it, > although I'm not 100% sure about having both a severity and priority field > on the ticket. This was kind of a code vomit, so I'm going to split the > classes out into separate Scala files once I get some feedback and a better > idea of what needs to be done. > > Cheers, > > Derek > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > wrote: > > > 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 >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 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 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 > >>
[Lift] Re: Proposal : Lift ticketing system
What is the goal of this system? Is it to be a nice, useful ticketing system that will serve as a demo to Lift? Or is it also to be a product that will eventually compete with other issue trackers such as Lift? If you're thinking big then I would suggest to think in terms of flexibility and extensibility. In particular I would not hard code attributes of the ticket but, at the cost of more starting complexity, I would have the fields be looked up in a table. I have done this more or less in two projects. It's tricky with Mapper but when you get it right is very powerful. I'll try to upload my code later this week if you wish. Basically the idea is that you have a table or tables of fields. Fields come in different types, including lookup, which is what priority would be, except that instead of the choices being hard coded they are in a table that is editable. So lookup fields specify a lookup table. There can be number fields, etc. This way plugins can add fields. For example Trac has a plugin that tracks hours. Of course you could just include every single possible field hard coded. It all depends what you're aiming for. - Derek Chen-Becker wrote: OK, I just pushed the initial revision of my model to GitHub at http://github.com/dchenbecker/LiftTicket. I think that this covers most of the features that Marius discussed in his response. I agree with all of it, although I'm not 100% sure about having both a severity and priority field on the ticket. This was kind of a code vomit, so I'm going to split the classes out into separate Scala files once I get some feedback and a better idea of what needs to be done. Cheers, Derek On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker wrote: > 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 > 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 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 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 -~--
[Lift] Re: Proposal : Lift ticketing system
I'm not by an internet connection now (won't be for a while). Would it be possible for you to paste your code in an email to me (in the body)? Thanks. - Derek Chen-Becker wrote: OK, I just pushed the initial revision of my model to GitHub at http://github.com/dchenbecker/LiftTicket. I think that this covers most of the features that Marius discussed in his response. I agree with all of it, although I'm not 100% sure about having both a severity and priority field on the ticket. This was kind of a code vomit, so I'm going to split the classes out into separate Scala files once I get some feedback and a better idea of what needs to be done. Cheers, Derek On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker wrote: > 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 > 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Derek Chen-Becker writes: > OK, I just pushed the initial revision of my model to GitHub at > http://github.com/dchenbecker/LiftTicket. I think that this covers most of > the features that Marius discussed in his response. I agree with all of it, > although I'm not 100% sure about having both a severity and priority field > on the ticket. One thing about priority: I much prefer an open ended "importance" field. This makes it (at least in theory :-) possible to have a well defined ordering of all tickets. (And if you put an unique index on it you force people to make a decision. Just kidding :-) /Jeppe --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Makes sense :) On Tue, Oct 27, 2009 at 3:28 PM, Marius wrote: > > In my mind the severity says the level of impact for the submitter, > and priority is the result of comitters' bandwidth. But it's not a big > issue. > > Br's, > Marius > > On Oct 27, 11:23 pm, Derek Chen-Becker wrote: > > OK, I just pushed the initial revision of my model to GitHub athttp:// > github.com/dchenbecker/LiftTicket. I think that this covers most of > > the features that Marius discussed in his response. I agree with all of > it, > > although I'm not 100% sure about having both a severity and priority > field > > on the ticket. This was kind of a code vomit, so I'm going to split the > > classes out into separate Scala files once I get some feedback and a > better > > idea of what needs to be done. > > > > Cheers, > > > > Derek > > > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > > wrote: > > > > > 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
In my mind the severity says the level of impact for the submitter, and priority is the result of comitters' bandwidth. But it's not a big issue. Br's, Marius On Oct 27, 11:23 pm, Derek Chen-Becker wrote: > OK, I just pushed the initial revision of my model to GitHub > athttp://github.com/dchenbecker/LiftTicket. I think that this covers most of > the features that Marius discussed in his response. I agree with all of it, > although I'm not 100% sure about having both a severity and priority field > on the ticket. This was kind of a code vomit, so I'm going to split the > classes out into separate Scala files once I get some feedback and a better > idea of what needs to be done. > > Cheers, > > Derek > > On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker > wrote: > > > 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 > > 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
OK, I just pushed the initial revision of my model to GitHub at http://github.com/dchenbecker/LiftTicket. I think that this covers most of the features that Marius discussed in his response. I agree with all of it, although I'm not 100% sure about having both a severity and priority field on the ticket. This was kind of a code vomit, so I'm going to split the classes out into separate Scala files once I get some feedback and a better idea of what needs to be done. Cheers, Derek On Mon, Oct 26, 2009 at 12:29 AM, Derek Chen-Becker wrote: > 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 > 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
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 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Did my Peek cause it to go in a separate thread? If so, sorry! - Marius wrote: Should this topic be correlated with Derek's http://groups.google.com/group/liftweb/browse_thread/thread/a3d046c7159a4f39?hl=en ? On Oct 25, 5:17 am, Naftoli Gugenheim 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Should this topic be correlated with Derek's http://groups.google.com/group/liftweb/browse_thread/thread/a3d046c7159a4f39?hl=en ? On Oct 25, 5:17 am, Naftoli Gugenheim 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
+1, good pr Proposal. On 10月25日, 上午11时17分, Naftoli Gugenheim 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Seems to be a good idea, Glen is working on one... http://github.com/glennSilverman/democritus his could be folded over and fleshed out... On Oct 25, 2:17 pm, Naftoli Gugenheim 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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
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 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Derek, I'd love to see your excellent talents pointed toward a ticketing system. Think the idea of a ticketing system that's less modal and a lot more ajaxy (and comety with live updates) would be a stellar thing to show off Lift's goodies... plus I think it would lead to improving/enhancing Lift. Good for it and whatever support I can give, I'm there! Thanks, David On Sat, Oct 24, 2009 at 6:56 AM, Derek Chen-Becker wrote: > Hi, > I feel like I need to take a break from working *on* Lift for a little > while, but I'd like to do something with my time that would still benefit > Lift. Since we had a recent discussion on ticketing systems, and we had > talked a long time ago about dogfooding a ticket system, I thought that this > might make a good project to work on. I like the simplicity of the GitHub > issue tracking, but I think it's missing some important things: > >1. Email notifications >2. Duplicate tracking >3. Release planning fields like milestones, etc > > I do like the integration with Git commit hashes and other intelligent > hyperlinking in the comment space, but I'm on the fence as to whether I like > using tags as a generic tool for things like ownership and component > classification. I could probably be persuaded either way. In any case, does > this seem like a good project, and if so, do people have requirements, > suggestions, comments, etc. on the functionality that should be in it? > > Thanks, > > Derek > > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
ERP systen or parts, which is what I'm working over on sourceforge. Ill post a link when I get home. The models are built and just need apps in front of them. Sent on the Now Network™ from my Sprint® BlackBerry -Original Message- From: jlist9 Date: Sat, 24 Oct 2009 11:20:43 To: Subject: [Lift] Re: Proposal : Lift ticketing system CMS, wiki, blog, forum also sound more interesting than bug tracking system to me :-) On Sat, Oct 24, 2009 at 11:13 AM, aw 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
Feel free to suggest other ideas or vote on the ones proposed so far :) On Sat, Oct 24, 2009 at 12:20 PM, jlist9 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 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
CMS, wiki, blog, forum also sound more interesting than bug tracking system to me :-) On Sat, Oct 24, 2009 at 11:13 AM, aw 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
I think it's a great idea. I'm not sure if this would work, but if it appeared on github, we could use it as an example app that new Lifters could study. Like what we hoped PocketChange would be, but we have more of a need for a ticket system, than a budget app. On Oct 24, 10:21 am, Marius wrote: > I'd LOVE TO SEE a ticketing system built in lift even though there are > so many other solutions out there. > > The things that I'd like to see are: > > 1. When opening a Ticket I'd like to see fields like: > - Summary > - Description > - Severity > - Priority > - Assign to > - Followers. Submitter would add himself/herself as a follower > - Tester > - area/module > - ability to upload content logs, screenshots etc > - ability to specify code snippets that will then be rendered with > syntax highlight. Also links specified in free text to be rendered as > real links. > - Found in version & build > - Seen on branch > > 2. A commiter can: > > - Specify Internal and external dependencies. Such as a defect > depends on a known Scala compiler ticket. > - Mark the ticket as fixed, unreproducible, not a bug, 3-rd party, > deferred etc. and other statuses that can be managed by an admin. > - Ask more questions etc. > - Upload content > - Change priority and even severity ? > - Close a defect ... usually QA closes the defect so in this case > the persons in the Terster section would be able to close it ... > - Build & version when the fix will appear > > 3. General > > - Query defects by owner, severity, priority etc. > - Ability for users to create queries and save those queries. > - Stats & charts about the defect, fix rate etc. Would be nice to > put a link to this stats when we do a release. > - Separate feature requests than actual defects ... to have a visual > distinction. > - Admin site. > - Email notifications. > > This I guess would be a minimum from my perspective. > > Br's, > Marius > > On Oct 24, 4:56 pm, Derek Chen-Becker wrote: > > > Hi, > > I feel like I need to take a break from working *on* Lift for a little > > while, but I'd like to do something with my time that would still benefit > > Lift. Since we had a recent discussion on ticketing systems, and we had > > talked a long time ago about dogfooding a ticket system, I thought that this > > might make a good project to work on. I like the simplicity of the GitHub > > issue tracking, but I think it's missing some important things: > > > 1. Email notifications > > 2. Duplicate tracking > > 3. Release planning fields like milestones, etc > > > I do like the integration with Git commit hashes and other intelligent > > hyperlinking in the comment space, but I'm on the fence as to whether I like > > using tags as a generic tool for things like ownership and component > > classification. I could probably be persuaded either way. In any case, does > > this seem like a good project, and if so, do people have requirements, > > suggestions, comments, etc. on the functionality that should be in it? > > > Thanks, > > > Derek > > --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[Lift] Re: Proposal : Lift ticketing system
I'd LOVE TO SEE a ticketing system built in lift even though there are so many other solutions out there. The things that I'd like to see are: 1. When opening a Ticket I'd like to see fields like: - Summary - Description - Severity - Priority - Assign to - Followers. Submitter would add himself/herself as a follower - Tester - area/module - ability to upload content logs, screenshots etc - ability to specify code snippets that will then be rendered with syntax highlight. Also links specified in free text to be rendered as real links. - Found in version & build - Seen on branch 2. A commiter can: - Specify Internal and external dependencies. Such as a defect depends on a known Scala compiler ticket. - Mark the ticket as fixed, unreproducible, not a bug, 3-rd party, deferred etc. and other statuses that can be managed by an admin. - Ask more questions etc. - Upload content - Change priority and even severity ? - Close a defect ... usually QA closes the defect so in this case the persons in the Terster section would be able to close it ... - Build & version when the fix will appear 3. General - Query defects by owner, severity, priority etc. - Ability for users to create queries and save those queries. - Stats & charts about the defect, fix rate etc. Would be nice to put a link to this stats when we do a release. - Separate feature requests than actual defects ... to have a visual distinction. - Admin site. - Email notifications. This I guess would be a minimum from my perspective. Br's, Marius On Oct 24, 4:56 pm, Derek Chen-Becker wrote: > Hi, > I feel like I need to take a break from working *on* Lift for a little > while, but I'd like to do something with my time that would still benefit > Lift. Since we had a recent discussion on ticketing systems, and we had > talked a long time ago about dogfooding a ticket system, I thought that this > might make a good project to work on. I like the simplicity of the GitHub > issue tracking, but I think it's missing some important things: > > 1. Email notifications > 2. Duplicate tracking > 3. Release planning fields like milestones, etc > > I do like the integration with Git commit hashes and other intelligent > hyperlinking in the comment space, but I'm on the fence as to whether I like > using tags as a generic tool for things like ownership and component > classification. I could probably be persuaded either way. In any case, does > this seem like a good project, and if so, do people have requirements, > suggestions, comments, etc. on the functionality that should be in it? > > Thanks, > > Derek --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
