> On Tue, 2017-01-17 at 06:26 -0500, Kamil Paral wrote:
> > We can't do that easily in Pagure. We could use a different
> > namespace, but namespaces are not browseable (at least not yet; only
> > user groups are browseable which is a different thing).
>
> Send patches ;)
>
> I've had quite a few
On Tue, 2017-01-17 at 06:26 -0500, Kamil Paral wrote:
> We can't do that easily in Pagure. We could use a different
> namespace, but namespaces are not browseable (at least not yet; only
> user groups are browseable which is a different thing).
Send patches ;)
I've had quite a few patches merged
On Tue, 17 Jan 2017 08:49:03 +0100
Martin Krizek wrote:
> On Tue, Jan 17, 2017 at 4:40 AM, Tim Flink wrote:
>
> > The following projects have been moved to pagure.io:
> >
> > https://pagure.io/taskotron/libtaskotron
> > https://pagure.io/taskotron/resultsdb
> > https://pagure.io/taskotron/resul
> On Tue, Jan 17, 2017 at 4:40 AM, Tim Flink < tfl...@redhat.com > wrote:
> > The following projects have been moved to pagure.io :
>
> > https://pagure.io/taskotron/libtaskotron
>
> > https://pagure.io/taskotron/resultsdb
>
> > https://pagure.io/taskotron/resultsdb_api
>
> > https://pagure.i
> The following projects have been moved to pagure.io:
>
> https://pagure.io/taskotron/libtaskotron
> https://pagure.io/taskotron/resultsdb
> https://pagure.io/taskotron/resultsdb_api
> https://pagure.io/taskotron/resultsdb_frontend
> https://pagure.io/taskotron/execdb
> https://pagure.io/taskotro
On Tue, Jan 17, 2017 at 4:40 AM, Tim Flink wrote:
> The following projects have been moved to pagure.io:
>
> https://pagure.io/taskotron/libtaskotron
> https://pagure.io/taskotron/resultsdb
> https://pagure.io/taskotron/resultsdb_api
> https://pagure.io/taskotron/resultsdb_frontend
> https://pagu
The following projects have been moved to pagure.io:
https://pagure.io/taskotron/libtaskotron
https://pagure.io/taskotron/resultsdb
https://pagure.io/taskotron/resultsdb_api
https://pagure.io/taskotron/resultsdb_frontend
https://pagure.io/taskotron/execdb
https://pagure.io/taskotron/taskotron-trig
On Fri, Jan 13, 2017 at 5:49 PM, Adam Williamson wrote:
> On Fri, 2017-01-13 at 14:16 +0100, Josef Skladanka wrote:
> > > I am personaly against issues/pull requests on Pagure - logging into
> Phab
> > is about as difficult as logging into Pagure, and I don't see the benefit
> > of "allowing peop
On Fri, 2017-01-13 at 14:16 +0100, Josef Skladanka wrote:
> > I am personaly against issues/pull requests on Pagure - logging into Phab
> is about as difficult as logging into Pagure, and I don't see the benefit
> of "allowing people to do it, since it's possible" even balancing out the
> problem o
On Fri, Jan 13, 2017 at 2:11 PM, Kamil Paral wrote:
> > I don't have any serious issues, as long as we only use pagure as git
> host. I
> > hate that "we wanted to copy github, but stopped just after we found out
> > it's too much functionality" thing (also don't like how github works on
> top
>
> I don't have any serious issues, as long as we only use pagure as git host. I
> hate that "we wanted to copy github, but stopped just after we found out
> it's too much functionality" thing (also don't like how github works on top
> of that, so even a 1:1 clone would be awful from my perspective)
I don't have any serious issues, as long as we only use pagure as git host.
I hate that "we wanted to copy github, but stopped just after we found out
it's too much functionality" thing (also don't like how github works on top
of that, so even a 1:1 clone would be awful from my perspective).
Just
> This came up in the qadevel meeting today and I wanted to put a bit
> more detail out.
>
> Bitbucket was never intended to be the long-term home for our git
> projects - I think we're about the only folks in Fedora using it and
> it's not free software. As fedorahosted is closed down, we need to
On Tue, 2017-01-10 at 11:13 -0700, Tim Flink wrote:
> On Mon, 9 Jan 2017 09:21:16 -0700
> Tim Flink wrote:
>
> > This came up in the qadevel meeting today and I wanted to put a bit
> > more detail out.
> >
> > Bitbucket was never intended to be the long-term home for our git
> > projects - I thi
On Mon, 9 Jan 2017 09:21:16 -0700
Tim Flink wrote:
> This came up in the qadevel meeting today and I wanted to put a bit
> more detail out.
>
> Bitbucket was never intended to be the long-term home for our git
> projects - I think we're about the only folks in Fedora using it and
> it's not free
5:21:16 PM
>> Subject: Proposal: Migrating More Git Projects to Pagure
>>
>> This came up in the qadevel meeting today and I wanted to put a bit
>> more detail out.
>>
>> Bitbucket was never intended to be the long-term home for our git
>> projects - I
- Original Message -
> From: "Tim Flink"
> To: qa-devel@lists.fedoraproject.org
> Sent: Monday, January 9, 2017 5:21:16 PM
> Subject: Proposal: Migrating More Git Projects to Pagure
>
> This came up in the qadevel meeting today and I wanted to put a bit
>
On Mon, 2017-01-09 at 09:21 -0700, Tim Flink wrote:
> This came up in the qadevel meeting today and I wanted to put a bit
> more detail out.
>
> Bitbucket was never intended to be the long-term home for our git
> projects - I think we're about the only folks in Fedora using it and
> it's not free
This came up in the qadevel meeting today and I wanted to put a bit
more detail out.
Bitbucket was never intended to be the long-term home for our git
projects - I think we're about the only folks in Fedora using it and
it's not free software. As fedorahosted is closed down, we need to find
a new
19 matches
Mail list logo
