On (16/09/16 12:52), Jakub Hrozek wrote:
>On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
>> On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek <jhro...@redhat.com> wrote:
>> > Hi,
>> > fedorahosted.org is being decomissioned:
>> > https://lists.fedoraproject.org/archives/list/annou...@lists.fedoraproject.org/thread/RLL3LFUPLYMAUKGZ5B3O64XKJXBT24KZ/
>> > so we need to find a new home for SSSD..
>> > I wanted to ask:
>> > 1) anyone from the core development team who is interested in
>> > finding a new home to raise a hand, we need someone to "own" this
>> > work
>> > 2) anyone from outside or inside the team who has an opinion to
>> > voice it :) so far we haven't even thought about the requirements
>> > in too much detail, though..
>> > In the meantime I just wrote up what fields we use from Trac and
>> > therefore what info we need to keep in the new system:
>> > https://fedorahosted.org/sssd/wiki/ticket_fields
>> So, I've seen that both pagure and github have pretty much the same
>> "issues" system and, AFAIR, it doesn't fit as well.
>> Considering Pavel's suggestion (something self-hosted), why not
>> Phabricator? Phabricator's trac seems to fit pretty much what we need.
>I've also heard good things about Phabricator (except being written in
I do not really mind which language was used; if I do not need to administrate
>but IMO we shouldn't host our own project tracker, we just don't
>have the manpower..
Maybe fedora-infra would be interested in hosting Phabricator.
It might be good to combine Phabricator + Pagure. The question
is whether they would be interested in hosting hosting another service
if they decide to get rid of servidces in fedorahosted
BTW the deadline is on 2017-02-28. So we still have time to persuade
them to either improve pagure issues tracker or to deply something else
sssd-devel mailing list -- firstname.lastname@example.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org