New ticketing system
David Pollak
We switched to GitHub's ticketing system a bunch of months ago and, well, it's not making the grade. It's slow. It's limited (no unclosing tickets, no attachments, weak discussion capaibilities). It doesn't allow easy planning/prioritization.
I'd like to switch to something more powerful. Derek was working on LiftTicket. I'd like to use that, but don't know the state of the project. Alternatively, we could use Assembla's ticketing system.
Does anyone have thoughts/input on the issue?
Thanks,
David
--
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
Marius
heaven't heard of it in a while and I know Derek currently has some
other stuff to do. I'm not sure if someone else took it over but no
news yet.
So unless someone has really good news about Derek's stuff Asssmbla
sounds pretty good. So you got my vote.
Br's,
Marius
On Jan 26, 7:46 pm, David Pollak <feeder.of.the.be...@gmail.com>
wrote:
> Folks,
>
> We switched to GitHub's ticketing system a bunch of months ago and, well,
> it's not making the grade. It's slow. It's limited (no unclosing tickets,
> no attachments, weak discussion capaibilities). It doesn't allow easy
> planning/prioritization.
>
> I'd like to switch to something more powerful. Derek was working on
> LiftTicket. I'd like to use that, but don't know the state of the project.
> Alternatively, we could use Assembla's ticketing system.
>
> Does anyone have thoughts/input on the issue?
>
> Thanks,
>
> David
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
Jeppe Nejsum Madsen
> Folks,
>
> We switched to GitHub's ticketing system a bunch of months ago and, well,
> it's not making the grade. It's slow. It's limited (no unclosing tickets,
> no attachments, weak discussion capaibilities). It doesn't allow easy
> planning/prioritization.
>
> I'd like to switch to something more powerful. Derek was working on
> LiftTicket. I'd like to use that, but don't know the state of the project.
> Alternatively, we could use Assembla's ticketing system.
>
> Does anyone have thoughts/input on the issue?
We're using Assembla. Seems to work fine for our small shop. It has a
lot of features that we don't use but which I think could be handy for
Lift.
Have a look at the clojure space to see how it may look for an OSS
project.
Also, it seems (haven't tried) that it's possible to import tickets:
http://i1t2b3.com/2009/08/26/how-to-import-tickets-assembla/
/Jeppe
Naftoli Gugenheim
In addition, after all the work Derek put into it, it would be sad not to use it.
Derek said that it's pretty near functional. G-d willing I will try to download it today and see where it's holding, and see if I can move it forward. David, what features does Assembla have that you would like to see in LiftTicket (or even if Assembla doesn't)?
In any case once it's basically usable we can start using it, and add features along the way. Also, importing tickets from GitHub should be a matter of a trivial scala script.
-------------------------------------
David Pollak <feeder.of...@gmail.com> writes:
http://i1t2b3.com/2009/08/26/how-to-import-tickets-assembla/
/Jeppe
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
Daniel Truemper
so far I have been a passive reader of this group. Lift is just a (very)
smal time project, but I like it a lot! Anyways:
>> We switched to GitHub's ticketing system a bunch of months ago and, well,
>> it's not making the grade. It's slow. It's limited (no unclosing tickets,
>> no attachments, weak discussion capaibilities). It doesn't allow easy
>> planning/prioritization.
>>
>> I'd like to switch to something more powerful. Derek was working on
>> LiftTicket. I'd like to use that, but don't know the state of the project.
>> Alternatively, we could use Assembla's ticketing system.
>>
>> Does anyone have thoughts/input on the issue?
I see many projects on GitHub using Lighthouse:
And if I remember correctly, the github's service hook for lighthouse
will enable the 'closes #123' type of commit messages...
Best
Daniel
David Pollak
Hi,
so far I have been a passive reader of this group. Lift is just a (very)
smal time project, but I like it a lot! Anyways:
I see many projects on GitHub using Lighthouse:
>> We switched to GitHub's ticketing system a bunch of months ago and, well,
>> it's not making the grade. It's slow. It's limited (no unclosing tickets,
>> no attachments, weak discussion capaibilities). It doesn't allow easy
>> planning/prioritization.
>>
>> I'd like to switch to something more powerful. Derek was working on
>> LiftTicket. I'd like to use that, but don't know the state of the project.
>> Alternatively, we could use Assembla's ticketing system.
>>
>> Does anyone have thoughts/input on the issue?
We used Lighthouse briefly and it was a seriously suboptimal user experience for me and others... thus the switch to GitHub.
http://lighthouseapp.com/
And if I remember correctly, the github's service hook for lighthouse
will enable the 'closes #123' type of commit messages...
Best
Daniel
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
David Pollak
I think it would be a *major* wasted opportunity not to invest in LiftTicket.
I agree.
It would be an excellent real life showcase of Lift. And of course it wouldn't make sense to switch to Assembla only temporarily.
In addition, after all the work Derek put into it, it would be sad not to use it.
I agree.
Derek said that it's pretty near functional. G-d willing I will try to download it today and see where it's holding, and see if I can move it forward. David, what features does Assembla have that you would like to see in LiftTicket (or even if Assembla doesn't)?
This is pretty compelling:
http://www.assembla.com/spaces/clojure/tickets?batch=false&tickets_report_id=1&ticket_id=
As is:
http://www.assembla.com/spaces/tickets/metrics/b4-TTcvBSr3RAZeJe5aVNr
Being able to plan and in other ways communicate among the committers as well as with the community is very powerful.
In any case once it's basically usable we can start using it, and add features along the way.
I'm all for that!
Daniel Truemper
> We used Lighthouse briefly and it was a seriously suboptimal user experience for me and others... thus the switch to GitHub.
Naftoli Gugenheim
Download it from www.github.com/dchenbecker/LiftTicket
Extract it into a directory and open a command prompt or shell there
mvn -Dorg.liftticket.config.masterpass=xxx jetty:run
Open a browser to http://localhost:8080/config/initial and enter your password (what you wrote for xxx above).
Navigate to User Administration and create a user with full permisions.
Terminate jetty
mvn jetty:run
Login as that user and set up all your settings
There doesn't seem to be a way to configure default permissions.
-------------------------------------
David Pollak<feeder.of...@gmail.com> wrote:
I agree.
I agree.
This is pretty compelling:
http://www.assembla.com/spaces/clojure/tickets?batch=false&tickets_report_id=1&ticket_id=
As is:
http://www.assembla.com/spaces/tickets/metrics/b4-TTcvBSr3RAZeJe5aVNr
> liftweb+u...@googlegroups.com<liftweb%2Bunsu...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Lift" group.
> To post to this group, send email to lif...@googlegroups.com.
> To unsubscribe from this group, send email to
> liftweb+u...@googlegroups.com<liftweb%2Bunsu...@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/liftweb?hl=en.
>
>
--
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
--
Thad
It's FREE for Open Source Projects, and as a bonus you'd probably get
more widespread appeal from Java / Scala development camps.
2cents,
Thad
On Jan 26, 11:46 am, David Pollak <feeder.of.the.be...@gmail.com>
wrote:
> Folks,
>
> We switched to GitHub's ticketing system a bunch of months ago and, well,
> it's not making the grade. It's slow. It's limited (no unclosing tickets,
> no attachments, weak discussion capaibilities). It doesn't allow easy
> planning/prioritization.
>
> I'd like to switch to something more powerful. Derek was working on
> LiftTicket. I'd like to use that, but don't know the state of the project.
> Alternatively, we could use Assembla's ticketing system.
>
> Does anyone have thoughts/input on the issue?
>
> Thanks,
>
> David
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net
> Beginning Scalahttp://www.apress.com/book/view/1430219890
David Pollak
Why not a proven workhorse in this arena, such as JIRA by Atlassian ?
It's FREE for Open Source Projects, and as a bonus you'd probably get
more widespread appeal from Java / Scala development camps.
Personally, I think Jira's UI and performance is awful. I'd rather start with GitHub than go to Jira. But that's just me.
2cents,
Thad
On Jan 26, 11:46 am, David Pollak <feeder.of.the.be...@gmail.com>
wrote:
> Folks,
>
> We switched to GitHub's ticketing system a bunch of months ago and, well,
> it's not making the grade. It's slow. It's limited (no unclosing tickets,
> no attachments, weak discussion capaibilities). It doesn't allow easy
> planning/prioritization.
>
> I'd like to switch to something more powerful. Derek was working on
> LiftTicket. I'd like to use that, but don't know the state of the project.
> Alternatively, we could use Assembla's ticketing system.
>
> Does anyone have thoughts/input on the issue?
>
> Thanks,
>
> David
>
> --
> Lift, the simply functional web frameworkhttp://liftweb.net> Beginning Scalahttp://www.apress.com/book/view/1430219890
--
You received this message because you are subscribed to the Google Groups "Lift" group.
To post to this group, send email to lif...@googlegroups.com.
To unsubscribe from this group, send email to liftweb+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
--
David Bernard
http://www.acunote.com/promo
(also provide full access for OSS)
But to the job with a LiftTicket should be a better match (for current
and futur need).
Sorry no time to work on.
/davidB
Heiko Seeberger
Folks,
We switched to GitHub's ticketing system a bunch of months ago and, well, it's not making the grade. It's slow. It's limited (no unclosing tickets, no attachments, weak discussion capaibilities). It doesn't allow easy planning/prioritization.
I'd like to switch to something more powerful. Derek was working on LiftTicket. I'd like to use that, but don't know the state of the project. Alternatively, we could use Assembla's ticketing system.
Does anyone have thoughts/input on the issue?
Blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: scalamodules.org
Lift, the simply functional web framework: liftweb.net
Naftoli Gugenheim
-------------------------------------
Heiko Seeberger<heiko.s...@googlemail.com> wrote:
2010/1/26 David Pollak <feeder.of...@gmail.com>
Heiko
--
Naftoli Gugenheim
- File attachments
- Possibly user comments (changes are logged), may be just lack of UI
- Ticket changes are not yet emailed
- Milestone support may need redesign? Currently has Module and ModuleRelease; Module allows multiple projects in same LiftTicket instance. Is that desirable?
David Pollak
Could some people take LiftTicket for a spin and comment? To clarify, it's already pretty functional.Here are some things not yet working or partially working, according to Derek:
- File attachments
- Possibly user comments (changes are logged), may be just lack of UI
- Ticket changes are not yet emailed
- Milestone support may need redesign? Currently has Module and ModuleRelease; Module allows multiple projects in same LiftTicket instance. Is that desirable?
However as a basic tool I think it's decent. I would love to hear comments. Maybe someone could host an instance of LiftTicket to track its progress? :)
I can host an instance. The big issue as I see it is have a reliable maintainer. In order to use LiftTicket, we need someone who is around most of the time (46+ weeks a year), can fix bugs in a few days, has a solid Internet connection, etc. If we can find a reliable maintainer, I'm all for moving forward with LiftTicket.
Heiko Seeberger
I can host an instance. The big issue as I see it is have a reliable maintainer. In order to use LiftTicket, we need someone who is around most of the time (46+ weeks a year), can fix bugs in a few days, has a solid Internet connection, etc. If we can find a reliable maintainer, I'm all for moving forward with LiftTicket.
Blog: heikoseeberger.name
Follow me: twitter.com/hseeberger
OSGi on Scala: scalamodules.org