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
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,
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
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 geo...@mattandgeorge.com wrote:
It might be worth taking a look at Redmine (http://www.redmine.org)
for some
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
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
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
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
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
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
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 dchenbec...@gmail.com wrote:
OK, I just pushed the initial revision of my model to GitHub
Makes sense :)
On Tue, Oct 27, 2009 at 3:28 PM, Marius marius.dan...@gmail.com 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
Derek Chen-Becker dchenbec...@gmail.com 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
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-Beckerdchenbec...@gmail.com wrote:
OK, I just pushed the initial revision of my model to
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
+1, good pr Proposal.
On 10月25日, 上午11时17分, 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
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 naftoli...@gmail.com wrote:
How about we integrate the wiki, blog, forum, and issue tracker into the CMS?
;)
Seriously,
Did my Peek cause it to go in a separate thread? If so, sorry!
-
Mariusmarius.dan...@gmail.com 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,
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
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
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
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
Feel free to suggest other ideas or vote on the ones proposed so far :)
On Sat, Oct 24, 2009 at 12:20 PM, 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:
:20:43
To: liftweb@googlegroups.com
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 anth...@whitford.com wrote:
I don't mean to be negative, but are other options
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
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.
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 naftoli...@gmail.com wrote:
How about we integrate the wiki, blog, forum, and issue tracker into the CMS?
;)
27 matches
Mail list logo
