Hey,
I'd like to ask the community if it's alright to officially move to pagure. I should have probably asked earlier but I haven't thought about it, I must admit. Pagure is an open-source project tight to Fedora Infrastructure, which COPR can use to its advantage. Auto-rebuilds launched on new commits are already working by employing great fedmsg infrastructure bus. I think there might be more possibilities there that I cannot see at the moment. Another advantage is that we can move our COPR wiki to Pagure from fedorahosted.org (going to be sunset) and have both code base and wiki on pagure.io and therefore use only one platform for these two. I probably won't be able to move closed pull requests from Github, which I wanted to do, but I have already started (really just started) working on that feature into pagure-importer so that other projects can have this. If you have any objections against moving to Pagure, please, tell.
Thanks clime
On Monday, November 7, 2016 1:36:11 PM CET Michal Novotny wrote:
Hey,
I'd like to ask the community if it's alright to officially move to pagure. I should have probably asked earlier but I haven't thought about it, I must admit. Pagure is an open-source project tight to Fedora Infrastructure, which COPR can use to its advantage. Auto-rebuilds launched on new commits are already working by employing great fedmsg infrastructure bus. I think there might be more possibilities there that I cannot see at the moment. Another advantage is that we can move our COPR wiki to Pagure from fedorahosted.org (going to be sunset) and have both code base and wiki on pagure.io and therefore use only one platform for these two. I probably won't be able to move closed pull requests from Github, which I wanted to do, but I have already started (really just started) working on that feature into pagure-importer so that other projects can have this.
I have a suggestion then. Please let the github repo live indefinitely, without pushing anything which is not in pagure. Only edit project description.
It would be nice to have that github repo synced automatically as an mirror, for marketing purposes (for both Copr and Pagure).
If you have any objections against moving to Pagure, please, tell.
I'm fine, but still would like to have this done WRT @coprgit FAS group.
Pavel
On Mon, Nov 07, 2016 at 03:07:38PM +0100, Pavel Raiskup wrote:
On Monday, November 7, 2016 1:36:11 PM CET Michal Novotny wrote:
Hey,
I'd like to ask the community if it's alright to officially move to pagure. I should have probably asked earlier but I haven't thought about it, I must admit. Pagure is an open-source project tight to Fedora Infrastructure, which COPR can use to its advantage. Auto-rebuilds launched on new commits are already working by employing great fedmsg infrastructure bus. I think there might be more possibilities there that I cannot see at the moment. Another advantage is that we can move our COPR wiki to Pagure from fedorahosted.org (going to be sunset) and have both code base and wiki on pagure.io and therefore use only one platform for these two. I probably won't be able to move closed pull requests from Github, which I wanted to do, but I have already started (really just started) working on that feature into pagure-importer so that other projects can have this.
I have a suggestion then. Please let the github repo live indefinitely, without pushing anything which is not in pagure. Only edit project description.
It would be nice to have that github repo synced automatically as an mirror, for marketing purposes (for both Copr and Pagure).
There is a feature that is WIP (but no ETA) to allow mirroring code from pagure to another git server. One of the idea is of course to allow automatic mirroring of code to github, gitlab, your own git server... :)
Pierre
On Mon, Nov 7, 2016 at 3:07 PM, Pavel Raiskup praiskup@redhat.com wrote:
On Monday, November 7, 2016 1:36:11 PM CET Michal Novotny wrote:
Hey,
I'd like to ask the community if it's alright to officially move to
pagure.
I should have probably asked earlier but I haven't thought about it, I
must
admit. Pagure is an open-source project tight to Fedora Infrastructure, which COPR can use to its advantage. Auto-rebuilds launched on new
commits
are already working by employing great fedmsg infrastructure bus. I think there might be more possibilities there that I cannot see at the moment. Another advantage is that we can move our COPR wiki to Pagure from fedorahosted.org (going to be sunset) and have both code base and wiki
on
pagure.io and therefore use only one platform for these two. I probably won't be able to move closed pull requests from Github, which I wanted to do, but I have already started (really just started) working on that feature into pagure-importer so that other projects can have this.
I have a suggestion then. Please let the github repo live indefinitely, without pushing anything which is not in pagure. Only edit project description.
It would be nice to have that github repo synced automatically as an mirror, for marketing purposes (for both Copr and Pagure).
Keeping the Github repo as a pointer might be a good idea.
If you have any objections against moving to Pagure, please, tell.
I'm fine, but still would like to have this done WRT @coprgit FAS group.
Contributing people from this group or from any other group will be added.
Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On Tuesday, November 8, 2016 7:52:07 AM CET Michal Novotny wrote:
On Mon, Nov 7, 2016 at 3:07 PM, Pavel Raiskup praiskup@redhat.com wrote:
I'm fine, but still would like to have this done WRT @coprgit FAS group.
Contributing people from this group or from any other group will be added.
ETA for this?
Pavel
Dne 7.11.2016 v 15:07 Pavel Raiskup napsal(a):
It would be nice to have that github repo synced automatically as an mirror, for marketing purposes (for both Copr and Pagure).
Why? I am really curious. IMHO it may just confuse developers where is the correct upstream.
I would love to see the github repo wiped and just put there the readme.txt as we done when we went away from fedorahosted.org: https://git.fedorahosted.org/cgit/copr.git/tree/README.txt
On Tuesday, November 8, 2016 9:52:26 AM CET Miroslav Suchý wrote:
Dne 7.11.2016 v 15:07 Pavel Raiskup napsal(a):
It would be nice to have that github repo synced automatically as an mirror, for marketing purposes (for both Copr and Pagure).
Why? I am really curious.
* For marketing purposes. Nobody (except for Fedora contributors) uses Pagure (but it's a pitty). People will search through github repos for copr and there will be nothing. Having a carbon copy makes sense to advertise both projects.
* The pull request database won't disappear. There are references to the database from git :(. It is very, very ugly that we have several merge commits referencing pull request database in git, so there's potential data loss. (I hate merge commits because those are there just to make git-log ugly, and moving from github just underlines it's worse than that).
* You can use github's features, e.g. Travis CI for free.
IMHO it may just confuse developers where is the correct upstream.
There's lot of mirrors on github and nobody is confused, because that's explicitly said in project's description. Maybe we should clearly say *why* we are working in Pagure, so others might move too.
Pavel
On Tuesday, November 8, 2016 12:22:47 PM CET Pavel Raiskup wrote:
Why? I am really curious.
For marketing purposes. Nobody (except for Fedora contributors) uses Pagure (but it's a pitty). People will search through github repos for copr and there will be nothing. Having a carbon copy makes sense to advertise both projects.
The pull request database won't disappear. There are references to the database from git :(. It is very, very ugly that we have several merge commits referencing pull request database in git, so there's potential data loss. (I hate merge commits because those are there just to make git-log ugly, and moving from github just underlines it's worse than that).
You can use github's features, e.g. Travis CI for free.
* people on github might still fork up2date code, without having FAS account.
Pavel
+1 for visibility
Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
On Tue, Nov 8, 2016 at 12:26 PM, Pavel Raiskup praiskup@redhat.com wrote:
On Tuesday, November 8, 2016 12:22:47 PM CET Pavel Raiskup wrote:
Why? I am really curious.
For marketing purposes. Nobody (except for Fedora contributors) uses Pagure (but it's a pitty). People will search through github repos for copr and there will be nothing. Having a carbon copy makes sense to advertise both projects.
The pull request database won't disappear. There are references to the database from git :(. It is very, very ugly that we have several merge commits referencing pull request database in git, so there's potential
data
loss. (I hate merge commits because those are there just to make
git-log
ugly, and moving from github just underlines it's worse than that).
- You can use github's features, e.g. Travis CI for free.
- people on github might still fork up2date code, without having FAS
account.
Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Can you send a link or translate? :)
Pavel
On Tue, Nov 08, 2016 at 02:22:22PM +0100, Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Can you send a link or translate? :)
A picture is worth a 1000 words they say: http://ambre.pingoured.fr/public/pagure_cal_heatmap.png
:)
Pierre
On Tuesday, November 8, 2016 2:46:43 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 02:22:22PM +0100, Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Can you send a link or translate? :)
A picture is worth a 1000 words they say: http://ambre.pingoured.fr/public/pagure_cal_heatmap.png
Nice! :) I would fix one nit: There's not obvious what row represents Monday/Sunday.
This probably doesn't resolve the concerns completely, but it is still very nice thing.
Yet another point: * Availability: in case of outage window in {pagure,github}, people can fetch from the counterpart.
Pavel
Let me then continue the transition and we can decide what to do with the Github repo later.
On Tue, Nov 8, 2016 at 2:56 PM, Pavel Raiskup praiskup@redhat.com wrote:
On Tuesday, November 8, 2016 2:46:43 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 02:22:22PM +0100, Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for
contributions! That
may motivate them to send pull-requests.
Check the next pagure release ;-)
Can you send a link or translate? :)
A picture is worth a 1000 words they say: http://ambre.pingoured.fr/public/pagure_cal_heatmap.png
Nice! :) I would fix one nit: There's not obvious what row represents Monday/Sunday.
This probably doesn't resolve the concerns completely, but it is still very nice thing.
Yet another point:
- Availability: in case of outage window in {pagure,github}, people can
fetch from the counterpart.
Pavel _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
Pavel
On Tue, Nov 15, 2016 at 08:41:26AM +0100, Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
There was a bug in forking projects with a namespace, this has been fixed in git but not deployed yet. The PR issue we'll need to take a closer look though, it might be fix but that doesn't ring a clear bell right now.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
We can't hot-fix before F25 is released :(
Pierre
On Tuesday, November 15, 2016 8:41:26 AM CET Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
@pingou,
bug #2: No email notifications are sent to my INBOX.
bug #3: Updating e.g. pull-request does not refresh the page, so it seems like there was nothing sent.
Pavel
On Tue, Nov 15, 2016 at 12:21:13PM +0100, Pavel Raiskup wrote:
On Tuesday, November 15, 2016 8:41:26 AM CET Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
@pingou,
bug #2: No email notifications are sent to my INBOX.
None at all or? For your actions or someone else's?
bug #3: Updating e.g. pull-request does not refresh the page, so it seems like there was nothing sent.
The diff or ? The diff isn't refreshed automatically, you need to reload, but the notifications about the rebase/new commits should be added automatically (modulo the SSE server running into too many open files)
Pierre
On Tuesday, November 15, 2016 12:26:26 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 15, 2016 at 12:21:13PM +0100, Pavel Raiskup wrote:
On Tuesday, November 15, 2016 8:41:26 AM CET Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
@pingou,
bug #2: No email notifications are sent to my INBOX.
None at all or? For your actions or someone else's?
Argh. Scratch #2 :) and sorry, I had full INBOX -> I hope I'll get all the messages in queue with slight delay .. without data loss.
bug #3: Updating e.g. pull-request does not refresh the page, so it seems like there was nothing sent.
The diff or ? The diff isn't refreshed automatically,
No no, not about asynchronous javascript ...
you need to reload, but the notifications about the rebase/new commits should be added automatically (modulo the SSE server running into too many open files)
I mean -> I've commented pull request, hit the "Update Issue" button, the text disappeared from textarea, and no text appeared (which means no page refresh occured).
Please redirect to a proper (pagure oriented) mailing list.
Pavel
On Tue, Nov 15, 2016 at 01:49:46PM +0100, Pavel Raiskup wrote:
On Tuesday, November 15, 2016 12:26:26 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 15, 2016 at 12:21:13PM +0100, Pavel Raiskup wrote:
On Tuesday, November 15, 2016 8:41:26 AM CET Pavel Raiskup wrote:
On Tuesday, November 8, 2016 1:03:05 PM CET Pierre-Yves Chibon wrote:
On Tue, Nov 08, 2016 at 12:53:28PM +0100, Adam Samalik wrote:
+1 for visibility Also, GitHub gives people credit on their profiles for contributions! That may motivate them to send pull-requests.
Check the next pagure release ;-)
Bug report: I've moved one pull request from github to pagure.
Forking the project caused 404, but apparently the project was forked under 'praiskup/' namespace. So I pushed the commits into separate branch and requested pull request -> and I received 404 again.
Seems like pagure thinks I clonned from 'copr/copr/copr' instead from 'copr/copr'. Can this be hot-fixed?
@pingou,
bug #2: No email notifications are sent to my INBOX.
None at all or? For your actions or someone else's?
Argh. Scratch #2 :) and sorry, I had full INBOX -> I hope I'll get all the messages in queue with slight delay .. without data loss.
bug #3: Updating e.g. pull-request does not refresh the page, so it seems like there was nothing sent.
The diff or ? The diff isn't refreshed automatically,
No no, not about asynchronous javascript ...
you need to reload, but the notifications about the rebase/new commits should be added automatically (modulo the SSE server running into too many open files)
I mean -> I've commented pull request, hit the "Update Issue" button, the text disappeared from textarea, and no text appeared (which means no page refresh occured).
Sounds like: https://pagure.io/pagure/issue/1333
Fixed in git :)
Pierre
copr-devel@lists.fedorahosted.org
-
Adam Samalik -
Michal Novotny -
Miroslav Suchý -
Pavel Raiskup -
Pierre-Yves Chibon