10 a.m.
I finally managed to get all our tickets migrated over to Pagure.
https://pagure.io/design/issues
Can you please check your open tickets to make sure all your attachments etc made it
over.
Sorry for the spam in IRC, I forgot to disable fedmsg :)
1:24 p.m.
Does this mean we should update in-progress tickets at pagure.io
instead of fedorahosted.org? If we do, will everyone on the CC: list in
the original ticket still receive notifications?
On Tue, 2016-10-25 at 15:00 +0000, Micah Denn wrote:
> I finally managed to get all our tickets migrated over to Pagure.
>
> https://pagure.io/design/issues
>
> Can you please check your open tickets to make sure all your
> attachments etc made it over.
>
> Sorry for the spam in IRC, I forgot to disable fedmsg :)
> _______________________________________________
> design-team mailing list -- design-team(a)lists.fedoraproject.org
> To unsubscribe send an email to design-team-leave(a)lists.fedoraproject
> .org
2:59 p.m.
Does this mean we should update in-progress tickets at pagure.io
instead of fedorahosted.org? If we do, will everyone on the CC: list in
the original ticket still receive notifications?
Will it be possible to migrate all tarball containing all Fedora
release wallpapers? I uploaded the latest version of f25-backgrounds few days ago
Yes notifications should be working. I don't know if we are read to move completely
yet. I just offered to handle migrating the tickets. mizmo any ideas?
Luya where did you upload the tarball? If it was attached to a ticket it should be there
already.
4:59 p.m.
On 25/10/16 12:59 PM, Micah Denn wrote:
Luya where did you upload the tarball? If it was attached to a ticket it should be there
already.
The tarball aren't on https://pagure.io/releases/design
Here is the current location of the wallpapers:
https://fedorahosted.org/released/design-team/
--
Luya Tshimbalanga
Graphic & Web Designer
E: luya(a)fedoraproject.org
W: http://www.coolest-storm.net
5:14 p.m.
It looks like Pagure releases only allows for tarballs up to 4MB.
Maybe we can ask for permission to upload bigger files? Otherwise we'll have to find
somewhere else to put them.
5:20 p.m.
On 10/25/2016 06:14 PM, Micah Denn wrote:
It looks like Pagure releases only allows for tarballs up to 4MB.
Maybe we can ask for permission to upload bigger files? Otherwise we'll have to find
somewhere else to put them.
Seeing as how design resources can be pretty large, you might need to
see if anything can be done to raise the limit for the repo (not sure if
this sort of granular change is possible). The best place to go would be
the Fedora Infrastructure list.
https://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedorapr...
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
12:24 a.m.
On Tue, Oct 25, 2016 at 06:20:30PM -0400, Justin W. Flory wrote:
On 10/25/2016 06:14 PM, Micah Denn wrote:
> It looks like Pagure releases only allows for tarballs up to 4MB.
>
> Maybe we can ask for permission to upload bigger files? Otherwise we'll have to
find somewhere else to put them.
>
Seeing as how design resources can be pretty large, you might need to see if
anything can be done to raise the limit for the repo (not sure if this sort
of granular change is possible). The best place to go would be the Fedora
Infrastructure list.
It should be a simple configuration change to do in ansible.
Raise the question either on the list or on fedora-infrastructure on pagure and
we'll see to bump it :)
Pierre
5:02 p.m.
On 10/25/2016 02:24 PM, Palmer G. Pattison wrote:
Does this mean we should update in-progress tickets at pagure.io
instead of fedorahosted.org? If we do, will everyone on the CC: list in
the original ticket still receive notifications?
I would assume now it would be best to add comments in Pagure. As far as
CC lists go, unless the person has actually commented in the ticket AND
already has a Pagure account, they will not continue to receive
notifications.
To notify someone in a ticket, you can tag them by their username to get
their attention, e.g. "Hey @jflory7, how does this look?" But note that
for this to work, they will have to already have a Pagure account (which
should only maybe be a problem for old tickets, not future tickets).
On Tue, 2016-10-25 at 15:00 +0000, Micah Denn wrote:
> I finally managed to get all our tickets migrated over to Pagure.
>
> https://pagure.io/design/issues
>
> Can you please check your open tickets to make sure all your
> attachments etc made it over.
>
> Sorry for the spam in IRC, I forgot to disable fedmsg :)
>
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
12:15 a.m.
On Tue, Oct 25, 2016 at 06:02:46PM -0400, Justin W. Flory wrote:
On 10/25/2016 02:24 PM, Palmer G. Pattison wrote:
> Does this mean we should update in-progress tickets at pagure.io
> instead of fedorahosted.org? If we do, will everyone on the CC: list in
> the original ticket still receive notifications?
>
I would assume now it would be best to add comments in Pagure. As far as CC
lists go, unless the person has actually commented in the ticket AND already
has a Pagure account, they will not continue to receive notifications.
To notify someone in a ticket, you can tag them by their username to get
their attention, e.g. "Hey @jflory7, how does this look?" But note that for
this to work, they will have to already have a Pagure account (which should
only maybe be a problem for old tickets, not future tickets).
Accounts are created on the fly for the users involved in tickets during the
import from git.
Pierre
1:05 a.m.
On 10/26/2016 01:15 AM, Pierre-Yves Chibon wrote:
On Tue, Oct 25, 2016 at 06:02:46PM -0400, Justin W. Flory wrote:
> On 10/25/2016 02:24 PM, Palmer G. Pattison wrote:
>> Does this mean we should update in-progress tickets at pagure.io
>> instead of fedorahosted.org? If we do, will everyone on the CC: list in
>> the original ticket still receive notifications?
>>
>
> I would assume now it would be best to add comments in Pagure. As far as CC
> lists go, unless the person has actually commented in the ticket AND already
> has a Pagure account, they will not continue to receive notifications.
>
> To notify someone in a ticket, you can tag them by their username to get
> their attention, e.g. "Hey @jflory7, how does this look?" But note that
for
> this to work, they will have to already have a Pagure account (which should
> only maybe be a problem for old tickets, not future tickets).
Accounts are created on the fly for the users involved in tickets during the
import from git.
Pierre
Oh, awesome, I didn't know about this until now! Thanks for clarifying
this point, Pierre. :)
--
Cheers,
Justin W. Flory
jflory7(a)gmail.com
2:40 p.m.
On 25/10/16 08:00 AM, Micah Denn wrote:
I finally managed to get all our tickets migrated over to Pagure.
https://pagure.io/design/issues
Can you please check your open tickets to make sure all your attachments etc made it
over.
Sorry for the spam in IRC, I forgot to disable fedmsg :)
_______________________________________________
design-team mailing list -- design-team(a)lists.fedoraproject.org
To unsubscribe send an email to design-team-leave(a)lists.fedoraproject.org
Will it be possible to migrate all tarball containing all Fedora release
wallpapers? I uploaded the latest version of f25-backgrounds few days ago
--
Luya Tshimbalanga
Graphic & Web Designer
E: luya(a)fedoraproject.org
W: http://www.coolest-storm.net
2737
days inactive
2738
days old
design-team@lists.fedoraproject.org
10 comments
5 participants
participants (5)
-
Justin W. Flory -
Luya Tshimbalanga -
Micah Denn -
Palmer G. Pattison -
Pierre-Yves Chibon