Improved issue/task management

Thomas De Schampheleire patrickdepinguin at
Mon Oct 24 19:24:27 UTC 2016

On Mon, Oct 24, 2016 at 9:11 PM, Dominik Ruf <dominikruf at> wrote:
> Thomas De Schampheleire <patrickdepinguin at> schrieb am Mo., 24.
> Okt. 2016 um 20:34 Uhr:
>> Hi Dominik, all,
>> On Sun, Oct 23, 2016 at 1:38 PM, Dominik Ruf <dominikruf at> wrote:
>> > Hi all,
>> >
>> > I strongly believe we need to improve the issue and task management in
>> > our
>> > project.
>> > Currently we use a mix of bitbucket wiki pages, bitbucket/kallithea pull
>> > request/changeset comments and bitbucket issue tracker.
>> I agree that the current situation is not optimal. While it works in
>> this 'unorganized' way, it could perhaps be made better. Some of this
>> has also been discussed on the developer gathering we held in the
>> beginning of this year (present were Mads, Søren, Andrew, Jan Heylen,
>> Mathias De Maré and myself).
>> Some points I think about:
>> - for code contribution, the goal should be to use Kallithea itself.
>> People like to call it 'eat your own dog food'. So while currently
>> some people use Bitbucket pull requests or to a lesser extent send
>> patches to the mailing list, I have been using this method and so far
>> it worked fine. An open point here was how users would get access:
>> auto-registration with automatic acceptance, manual acceptance, or
>> admin-only sign-up ? I think this is something we should unblock and
>> continue with. As a result, Bitbucket PRs would no longer be used.
> +10 for eating our own dog food
> But in my view there 2 things that need to be done before we can do that.
> 1. open auto-registration.
> 2. everyone needs a personal space/folder where he/she can create a fork and
> there be able to create a pull request.

For point 2 I don't know if it is really necessary: it is the github
way, but there existed life before github :) What I mean is that users
can have a repository on their own pc, and push into our Kallithea to
start a PR. This is what I do. You don't need a hosted Kallithea to
fork. One of the risks of many public 'forks' is that the main project
is less visible.

Allowing such personal space on 'our own kallithea' means that we need
more resources on the server, I assume there are restrictions there.
Perhaps some of us should form a company and offer hosted Kallithea,
free for basic usage but paying for others?

More information about the kallithea-general mailing list