Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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
On 09/16/2016 11:09 AM, Jakub Hrozek wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/sssd-devel@lists.fedorahosted.org
I would love to see SSSD on Pagure.
Michal
On (16/09/16 11:20), Michal Židek wrote:
On 09/16/2016 11:09 AM, Jakub Hrozek wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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
I would love to see SSSD on Pagure.
+1 I can help with transition to Pagure. git hosting is not a problem and Nikolai voluntered to convert wiki to markdown in git
The question is which way would we use for tracking bugs/issues. I would wait for decision in freeIPA team.
LS
On Fri, Sep 16, 2016 at 12:21:40PM +0200, Lukas Slebodnik wrote:
+1 I can help with transition to Pagure. git hosting is not a problem and Nikolai voluntered to convert wiki to markdown in git
Sorry to restart an old thread, but..
I bought the sssd.io domain name. The intent is to have a simple but pretty homepage like libssh.org or cmocka.org with links to documentation which can itself be rendered from some git repository. The pages should have zero or next-to-zero maintenance cost, so mostly static.
btw for now the domain is owned by me, but I'm totally fine transferring the ownership to some shared account.
On 09/16/2016 11:09 AM, Jakub Hrozek wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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
Can't we just host custom trac instance and maybe create a nicer webpage such as FreeIPA's?
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
However, the issue tracker seems to be a point of contention. I know little of requirements here, but personally would be OK with GitHub tracker, and think tighter integration and better visibility could win over deficiencies.
I don't think Pagure is going to be a smooth ride at this point.
Nick
On 09/16/2016 01:18 PM, Nikolai Kondrashov wrote:
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
Oh, and I can help with remaking the website for github.io hosting, if you decide to go there. At least starting it up, if not going all the way. I would also advocate putting any documentation and design documents from the wiki into the source tree as Markdown, regardless whether we go to GitHub or Pagure.
Nick
On (16/09/16 13:21), Nikolai Kondrashov wrote:
On 09/16/2016 01:18 PM, Nikolai Kondrashov wrote:
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
Oh, and I can help with remaking the website for github.io hosting, if you decide to go there. At least starting it up, if not going all the way. I would also advocate putting any documentation and design documents from the wiki into the source tree as Markdown, regardless whether we go to GitHub or Pagure.
I would prefer as small dependencies as possible on github.
LS
On (16/09/16 13:18), Nikolai Kondrashov wrote:
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
That is just a temporary solution. I plan to move it to Pagure (later not now :-)
However, the issue tracker seems to be a point of contention. I know little of requirements here, but personally would be OK with GitHub tracker, and think tighter integration and better visibility could win over deficiencies.
I don't think Pagure is going to be a smooth ride at this point.
Tracker in github is not better. But we have a power to influence improvementes in Pagure.
LS
On 09/16/2016 01:25 PM, Lukas Slebodnik wrote:
On (16/09/16 13:18), Nikolai Kondrashov wrote:
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
That is just a temporary solution. I plan to move it to Pagure (later not now :-)
However, the issue tracker seems to be a point of contention. I know little of requirements here, but personally would be OK with GitHub tracker, and think tighter integration and better visibility could win over deficiencies.
I don't think Pagure is going to be a smooth ride at this point.
Tracker in github is not better. But we have a power to influence improvementes in Pagure.
I will be on your side if you decide to go to Pagure, but I wouldn't be too enthusiastic about the speed with which we can expect improvements and features to come and stabilize. To me Pagure seems very raw and I'm cautious about it.
It is a construction site right now, there's basically nobody there (compared to GitHub and other similar services), and potential contributors would need to jump over an additional hurdle of registering another account, which, most likely, will be of little use to them otherwise.
It would be nice to help Pagure improve and grow, but the question is can we afford it?
Nick
On Fri, Sep 16, 2016 at 12:25:41PM +0200, Lukas Slebodnik wrote:
On (16/09/16 13:18), Nikolai Kondrashov wrote:
On 09/16/2016 12:09 PM, Jakub Hrozek wrote:
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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..
Alright, here comes my opinion :)
GitHub seems to me the path of least resistance, as we already have hooks and started doing the pull requests. Especially considering the recent addition of a review process.
That is just a temporary solution. I plan to move it to Pagure (later not now :-)
However, the issue tracker seems to be a point of contention. I know little of requirements here, but personally would be OK with GitHub tracker, and think tighter integration and better visibility could win over deficiencies.
I don't think Pagure is going to be a smooth ride at this point.
Tracker in github is not better.
Well, no, the tracker at pagure is absolutely awful right now. I couldn't even see milestones there. But I hope we can ask to add some fields..
The first step imo is -- define what exactly we miss from pagure's tracker. For me it's: - milestones - a way to link to RHBZ - priority (could be solved with tags I guess) - patch submmitted (could be solved with tags) - link to a design document (not totally needed, but if could be added together with RHBZ link hopefully)
So milestone and a link to external tracker are missing and need to be added before pagure is useful.
But we have a power to influence improvementes in Pagure.
Right. Github is missing links to RHBZ, but I don't see a way to add it there..
On Fri, Sep 16, 2016 at 12:50:54PM +0200, Jakub Hrozek wrote:
The first step imo is -- define what exactly we miss from pagure's tracker. For me it's: - milestones
Apparently, pagure has a creative way to deal with milestones: https://docs.pagure.org/pagure/usage/roadmap.html
On 09/16/2016 01:19 PM, Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:50:54PM +0200, Jakub Hrozek wrote:
The first step imo is -- define what exactly we miss from pagure's tracker. For me it's: - milestones
Apparently, pagure has a creative way to deal with milestones: https://docs.pagure.org/pagure/usage/roadmap.html
This maps our current processes pretty well. New tickets have no roadmap tags, so they are "Unplanned" (NEEDS_TRIAGE), and adding them to a certain milestone is a matter of setting a tag.
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/sssd-devel@lists.fedorahosted.org
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.
Best Regards, -- Fabiano Fidêncio
On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 _______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://lists.fedorahosted.org/admin/lists/sssd-devel@lists.fedorahosted.org
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 PHP..), but IMO we shouldn't host our own project tracker, we just don't have the manpower..
On (16/09/16 12:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 PHP..),
I do not really mind which language was used; if I do not need to administrate it.
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 (e.g. Phabricator)
LS
On Fri, Sep 16, 2016 at 12:58:38PM +0200, Lukas Slebodnik wrote:
On (16/09/16 12:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 PHP..),
I do not really mind which language was used; if I do not need to administrate it.
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 (e.g. Phabricator)
I asked explicitly if there is an option of hosting something like gitlab or phabricator..
On (21/09/16 11:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:58:38PM +0200, Lukas Slebodnik wrote:
On (16/09/16 12:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 PHP..),
I do not really mind which language was used; if I do not need to administrate it.
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 (e.g. Phabricator)
I asked explicitly if there is an option of hosting something like gitlab or phabricator..
Do you have a link to mailing-list/trac ... or it was a IRC discussion
LS
On Wed, Sep 21, 2016 at 11:58:23AM +0200, Lukas Slebodnik wrote:
On (21/09/16 11:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:58:38PM +0200, Lukas Slebodnik wrote:
On (16/09/16 12:52), Jakub Hrozek wrote:
On Fri, Sep 16, 2016 at 12:34:26PM +0200, Fabiano Fidêncio wrote:
Howdy!
On Fri, Sep 16, 2016 at 11:09 AM, Jakub Hrozek jhrozek@redhat.com wrote:
Hi,
fedorahosted.org is being decomissioned: https://lists.fedoraproject.org/archives/list/announce@lists.fedoraproject.o... 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 PHP..),
I do not really mind which language was used; if I do not need to administrate it.
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 (e.g. Phabricator)
I asked explicitly if there is an option of hosting something like gitlab or phabricator..
Do you have a link to mailing-list/trac ... or it was a IRC discussion
Direct mail.
sssd-devel@lists.fedorahosted.org
-
Fabiano Fidêncio -
Jakub Hrozek -
Lukas Slebodnik -
Michal Židek -
Nikolai Kondrashov -
Pavel Březina