Improved issue/task management

[Dominik Ruf]

Sathishkumar Duraisamy <bewithsathish at gmail.com> schrieb am Mo., 24. Okt.
2016 um 19:08 Uhr:

> Hi,
>
> Can you add me to the project, (mysathishkumar.duraisamy at yahoo.com e-mail
> id: sathishkumar.duraisamy at yahoo.com) . Instead of kanban, it would be
> good to use the sprint.
>

Since we are all volunteers I don't think that would work.


>
> On Mon, Oct 24, 2016 at 7:26 PM, Andrew Shadura <andrew at shadura.me> wrote:
>
> Hi,
>
> On 24 October 2016 at 15:47, Mads Kiilerich <mads at kiilerich.com> wrote:
> > On 10/23/2016 01:38 PM, Dominik Ruf wrote:
> >
> >> A quick web search lead me to taiga.io. I don't know if anybody already
> >> knows it, but it seems it supports my requirements above and it is open
> >> source.
> >
> > I doubt a different tool automatically would make a big difference. But
> it
> > can make a big difference if it makes a difference to key people and can
> > make them make a difference ;-)
>
> I agree. However organising the processes or cleaning up existing
> issues may help us working on things.
>
> > Besides you and and Andrew, Thomas has also done quite a bit of triaging
> and
> > support on the existing bug tracker - his opinion also matters.
> >
> > I dont' have much opinion on it - fine with me ... assuming someone
> (you?)
> > do the work, including:
> >
> >  * issues are migrated from the old system (or we decide not to)
>
> *Iff* we decided to migrate to Taiga, we wouldn’t need to fully
> migrate our issues, as it could be used as a complementary tool.
> However, I am not sure regarding Taiga itself: compared to issue
> tracking/organising features of Phabricator, a system we use at work,
> it’s not much better (is it better at all?), but I like the appearance
> of Phabricator more than of Taiga.
>
> I’m not sure Phabricator itself is what we need either, as it seems to
> be more of a all-in-one integrated solution, where bits fit to each
> other but don’t really integrate well with external software.
>
> >  * web pages are updated to point to the new system
> >  * the user facing documentation is updated
> >  * the contributing guidelines are updated - also regarding commit
> messages closing issues
> >  * perhaps some hooks on https://kallithea-scm.org/repos/kallithea/ for
> > closing / commenting on issues
> >  * perhaps some hook for posting new issues on the mailing list
>
> --
> Cheers,
>   Andrew
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>
>
>
>
> --
> Regards,
> Sathishkumar D
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> http://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20161024/5290c15f/attachment.html>