<div dir="auto"><div>Hi.<div dir="auto"><br></div><div dir="auto">Company I work for has been using both Kallithea and Redmine for a several years now.</div><div dir="auto"><br></div><div dir="auto">Redmine works well - it has a lot of options but still relatively easy to setup and use. </div><div dir="auto"><br></div><div dir="auto">We mainly use it's issue tracker and wiki.</div>I don't remember having any major issues.</div><div dir="auto"><br></div><div dir="auto">If you want to know spesifics I can try to answer.</div><div dir="auto"><div class="gmail_extra" dir="auto"><br><div class="gmail_quote">21.7.2017 16.12 "Andrew Miller" <<a href="mailto:a.miller@neath-porttalbot.gov.uk">a.miller@neath-porttalbot.gov.uk</a>> kirjoitti:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Has anyone looked at Redmine for project management? It supports issue tracking and has built in wiki capabilities.<br>
<br>
(I've never used JIRA or Taiga, and only briefly looked at Redmine, so I don't know how they compare feature-wise).<br>
<div class="elided-text"><br>
-----Original Message-----<br>
From: kallithea-general [mailto:<a href="mailto:kallithea-general-bounces@sfconservancy.org">kallithea-general-<wbr>bounces@sfconservancy.org</a>] On Behalf Of Thomas De Schampheleire<br>
Sent: 20 July 2017 21:00<br>
To: Dominik Ruf<br>
Cc: Kallithea<br>
Subject: Re: PR webhooks to trigger automation?<br>
<br>
2017-07-19 21:23 GMT+02:00 Dominik Ruf <<a href="mailto:dominikruf@gmail.com">dominikruf@gmail.com</a>>:<br>
><br>
><br>
> Thomas De Schampheleire <<a href="mailto:patrickdepinguin@gmail.com">patrickdepinguin@gmail.com</a>> schrieb am Mi., 19.<br>
> Juli 2017 um 19:55 Uhr:<br>
>><br>
[..]<br>
>><br>
>> I think we should decide upon some kind of roadmap after 1.0 and<br>
>> start discussing and implementing such features one by one.<br>
>> That is, I think we should try getting out 0.9 and 1.0 soon, with 0.9<br>
>> being current default + bootstrap, and 1.0 being 0.9 with some of the<br>
>> near-ready PRs finalized, and avoid diverting into new territory too<br>
>> much before 1.0 is out.<br>
><br>
> I agree.<br>
> And I'd like to use this occasion to re-iterate on my suggestion to<br>
> use JIRA to manage the project.<br>
> I think JIRA could really help with planning releases.<br>
> It is also much easier, to discuss ideas, like the ones above, in<br>
> JIRA, then in a wiki, don't you think?<br>
><br>
> I'd also volontiere to manage JIRA.<br>
><br>
<br>
I dug up the old discussion on the topic:<br>
<a href="https://lists.sfconservancy.org/pipermail/kallithea-general/2016q4/002150.html" rel="noreferrer" target="_blank">https://lists.sfconservancy.<wbr>org/pipermail/kallithea-<wbr>general/2016q4/002150.html</a><br>
<br>
At the time it felt a bit overkill to me, but right now I agree that it could perhaps help us and I think we should try it.<br>
Nevertheless, most of my comments from the previous thread still hold.<br>
[<a href="https://lists.sfconservancy.org/pipermail/kallithea-general/2016q4/002161.html" rel="noreferrer" target="_blank">https://lists.sfconservancy.<wbr>org/pipermail/kallithea-<wbr>general/2016q4/002161.html</a>]<br>
In particular, I think we should migrate completely from old issues on Bitbucket to the new system.<br>
<br>
Regarding JIRA vs something else:<br>
- I prefer open-source projects if possible<br>
- Storyboard:<br>
- is it somewhat mature, will it stay? (It would be a pity if we need to switch to something else many times)<br>
- does the openstack instance allow hosting for non-openstack projects like Kallithea, or do we need to set up our own instance?<br>
- does anyone have experience with it already?<br>
<br>
- As stated in the previous mail thread, I'd like to get rid of Bitbucket completely: code hosting and pull requests should move to our own kallithea, what is left are issues and wiki. If we move issues to something new that does not have a wiki capabability, perhaps we should find something else for wiki.<br>
(although much of the existing wiki can be seen as tasks/issues and thus be moved, I think there is still content that better lives in a real wiki).<br>
<br>
- Andrew and you looked at Taiga previously, what was the conclusion of that?<br>
<br>
Thanks,<br>
Thomas<br>
______________________________<wbr>_________________<br>
kallithea-general mailing list<br>
<a href="mailto:kallithea-general@sfconservancy.org">kallithea-general@<wbr>sfconservancy.org</a><br>
<a href="https://lists.sfconservancy.org/mailman/listinfo/kallithea-general" rel="noreferrer" target="_blank">https://lists.sfconservancy.<wbr>org/mailman/listinfo/<wbr>kallithea-general</a><br>
______________________________<wbr>_________________<br>
kallithea-general mailing list<br>
<a href="mailto:kallithea-general@sfconservancy.org">kallithea-general@<wbr>sfconservancy.org</a><br>
<a href="https://lists.sfconservancy.org/mailman/listinfo/kallithea-general" rel="noreferrer" target="_blank">https://lists.sfconservancy.<wbr>org/mailman/listinfo/<wbr>kallithea-general</a><br>
</div></blockquote></div><br></div></div></div>