Greetings.
We are currently running modernpaste for paste.fedoraproject.org.
It's pretty dead upstream. The primary maintainer said they wanted to make a v2 version that was a complete re-write. That was about a year ago and nothing has happened since. ;( We have several outstanding issues against it and some folks don't really like it. It's one of the few things left we have that is using mariadb instead of postgres. It collects spam and has to be cleaned up all the time.
So, we need a plan. I think our options are:
1) Just keep using modernpaste and hope it stays working/secure.
2) Reach out to CentOS folks and see if we can work out some way to share a pastebin. Either rebrand things for both, have some way of branding per virthost or at least run the same code so we can share knowledge about it.
3) Just stop providing a pastebin and ask people to use any of the other ones out there.
4) Find another supported open source one and run it in OpenShift. (perhaps the community openshift since it should have a low SLE)
5) Your clever idea here.
Thoughts?
kevin
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post things (pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post things (pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also makes more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others' does not break.
On Mon, May 20, 2019 at 1:20 PM Justin W. Flory jflory7@gmail.com wrote:
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post things (pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also makes more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others' does not break.
+1
langdon
-- Cheers, Justin W. Flory justinwflory.com TZ=America/New_York Pronouns: he/him/his
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote:
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post things (pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also makes more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others' does not break.
Agreed, as long as fpaste continues to be working and puts the pasted text somewhere sensible all would be more or less fine.
BTW, fpaste is available in the installation environment (both live & netinst images) and is pretty handy for debugging various installation related issues as you can't simply fpaste the relevant logs/error messaages and retrieve it on a different computer by re-typing the URL. This is likely the easiest method for extracting logs from a failed/invalid installation, others are more complicated (scp, mounting a flash drive, filling in a libreport form).
Actually, if any fpaste changes can give us a shorter to type URL, this would be very welcome. :)
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Mon, May 20, 2019 at 7:36 PM Martin Kolman mkolman@redhat.com wrote:
On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote:
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post things (pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also makes more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others' does not break.
Agreed, as long as fpaste continues to be working and puts the pasted text somewhere sensible all would be more or less fine.
I am seeing lots of early love for Option #3 - I am also great with this but I'd like to see two things:
1) Can we pick a suggested one that is the fpaste default to try and make it easy for infrequent users to not just be told "pick on"
2) Can we do something to help what ever paste bin we do use with their resourcing, perhaps a donation or sponsorship as a thank you?
regards,
bex
BTW, fpaste is available in the installation environment (both live & netinst images) and is pretty handy for debugging various installation related issues as you can't simply fpaste the relevant logs/error messaages and retrieve it on a different computer by re-typing the URL. This is likely the easiest method for extracting logs from a failed/invalid installation, others are more complicated (scp, mounting a flash drive, filling in a libreport form).
Actually, if any fpaste changes can give us a shorter to type URL, this would be very welcome. :)
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Mon, 20 May 2019 at 13:47, Brian (bex) Exelbierd bexelbie@redhat.com wrote:
On Mon, May 20, 2019 at 7:36 PM Martin Kolman mkolman@redhat.com wrote:
On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote:
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post
things
(pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs team to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also
makes
more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others'
does
not break.
Agreed, as long as fpaste continues to be working and puts the pasted
text somewhere sensible
all would be more or less fine.
I am seeing lots of early love for Option #3 - I am also great with this but I'd like to see two things:
- Can we pick a suggested one that is the fpaste default to try and
make it easy for infrequent users to not just be told "pick on"
I am for #2& myself. I think getting the CentOS one setup and into our Community OpenShift would be a good solution for 3 things. 1 set of tools to update, 1 set of systems to clean out and 2 no need to worry that our paste of the week has turned into the GoatPornHub we are sending users too.
- Can we do something to help what ever paste bin we do use with
their resourcing, perhaps a donation or sponsorship as a thank you?
This is a good idea, but will have to come from the council. I have found that trying for our department to try and give funding/sponsorship etc is almost impossible :/.
regards,
bex
BTW, fpaste is available in the installation environment (both live &
netinst images)
and is pretty handy for debugging various installation related issues as
you can't
simply fpaste the relevant logs/error messaages and retrieve it on a
different
computer by re-typing the URL. This is likely the easiest method for
extracting logs
from a failed/invalid installation, others are more complicated (scp,
mounting a flash drive,
filling in a libreport form).
Actually, if any fpaste changes can give us a shorter to type URL, this
would be very welcome. :)
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
-- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexelbie@redhat.com | bex@pobox.com _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Mon, May 20, 2019 at 8:13 PM Stephen John Smoogen smooge@gmail.com wrote:
On Mon, 20 May 2019 at 13:47, Brian (bex) Exelbierd bexelbie@redhat.com wrote:
On Mon, May 20, 2019 at 7:36 PM Martin Kolman mkolman@redhat.com wrote:
On Mon, 2019-05-20 at 13:11 -0400, Justin W. Flory wrote:
On 5/20/19 12:56 PM, Ben Cotton wrote:
I don't see that running our own pastebin is valuable to the community. There are plenty of other options for people to post
things
(pastebin.com, GitHub gists, put a file in your web space on Fedora people, etc). I'm in favor of option 3, with a long enough timeline for the fpaste maintainers to handle the change and for the docs
team
to make sure we update any docs that refer to pase.fp.o accordingly (if any)
+1 to Option 3.
My biggest use for paste.fp.o is via fpaste in CLI. To me, it also
makes
more sense to use an existing service and point the fpaste tool there. So long as fpaste continues to work, my use case and likely others'
does
not break.
Agreed, as long as fpaste continues to be working and puts the pasted
text somewhere sensible
all would be more or less fine.
I am seeing lots of early love for Option #3 - I am also great with this but I'd like to see two things:
- Can we pick a suggested one that is the fpaste default to try and
make it easy for infrequent users to not just be told "pick on"
I am for #2& myself. I think getting the CentOS one setup and into our Community OpenShift would be a good solution for 3 things. 1 set of tools to update, 1 set of systems to clean out and 2 no need to worry that our paste of the week has turned into the GoatPornHub we are sending users too.
If we have this capacity in infra I’m fully onboard with a shared pastebin. I also think we should simply the install and maintenance with shared or neutral branding.
- Can we do something to help what ever paste bin we do use with
their resourcing, perhaps a donation or sponsorship as a thank you?
This is a good idea, but will have to come from the council. I have found that trying for our department to try and give funding/sponsorship etc is almost impossible :/.
I’m separating source of funds from willingness :)
Regards,
bex
regards,
bex
BTW, fpaste is available in the installation environment (both live &
netinst images)
and is pretty handy for debugging various installation related issues
as you can't
simply fpaste the relevant logs/error messaages and retrieve it on a
different
computer by re-typing the URL. This is likely the easiest method for
extracting logs
from a failed/invalid installation, others are more complicated (scp,
mounting a flash drive,
filling in a libreport form).
Actually, if any fpaste changes can give us a shorter to type URL, this
would be very welcome. :)
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to
infrastructure-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
-- Brian "bex" Exelbierd (he/him/his) Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org bexelbie@redhat.com | bex@pobox.com _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
-- Stephen J Smoogen.
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Mon, May 20, 2019 09:47:56 -0700, Kevin Fenzi wrote:
<snip>
- Just stop providing a pastebin and ask people to use any of the other
ones out there.
<snip>
I see preference for this option given that fpaste continues to work. Unfortunately, fpaste cannot just paste to any server out there since they don't all speak the same API.
We can support one, maybe two servers with help from the community, but not all the servers there are out there. So, we do need to pick one if fpaste is to stay alive. We will also need to ensure that whoever is hosting it communicates with us when they make changes so that fpaste can be kept up to date.
The CentOS folks had opened a ticket here for supporting "Stikked" a while ago, but since we've been on modernpaste, I've not put any resources on adding support for it yet.
https://pagure.io/fpaste/issue/40
More information on things:
https://pagure.io/fedora-infrastructure/issue/5780 https://pagure.io/fpaste/issue/21
On Mon, May 20, 2019 at 09:47:56AM -0700, Kevin Fenzi wrote:
Greetings.
We are currently running modernpaste for paste.fedoraproject.org.
It's pretty dead upstream. The primary maintainer said they wanted to make a v2 version that was a complete re-write. That was about a year ago and nothing has happened since. ;( We have several outstanding issues against it and some folks don't really like it. It's one of the few things left we have that is using mariadb instead of postgres. It collects spam and has to be cleaned up all the time.
So, we need a plan. I think our options are:
Just keep using modernpaste and hope it stays working/secure.
Reach out to CentOS folks and see if we can work out some way to
share a pastebin. Either rebrand things for both, have some way of branding per virthost or at least run the same code so we can share knowledge about it.
- Just stop providing a pastebin and ask people to use any of the other
ones out there.
- Find another supported open source one and run it in OpenShift.
(perhaps the community openshift since it should have a low SLE)
- Your clever idea here.
IMHO a refinement of 3) would be to redirect people to the CentOS pastebin:
- redirect paste.fedoraproject.org to paste.centos.org - make fpaste work with paste.centos.org
This still makes it possible to do 2) if someone wants to do the work.
Kind regards Till
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But I do not care to which service it will communicate.
On Tue, Jun 04, 2019 11:01:52 +0200, Miroslav Suchý wrote:
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But I do not care to which service it will communicate.
I think this is the simplest option at the moment.
I'll start working on making fpaste work with their API soon (PRs always welcome, of course). Is there a timeline on pulling the plug on paste.fp.o that I should adhere to?
On Tue, 4 Jun 2019 at 07:27, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:01:52 +0200, Miroslav Suchý wrote:
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But I do not care to which service it will communicate.
I think this is the simplest option at the moment.
I'll start working on making fpaste work with their API soon (PRs always welcome, of course). Is there a timeline on pulling the plug on paste.fp.o that I should adhere to?
CentOS has a cpaste application which might help on that.
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
If we are going with the approach of just one paste platform, we could just retire fpaste, add cpaste with an fpaste alias and provides on rpm spec, retire paste.fp.o and redirect it to paste.centos =)
On June 4, 2019 2:25:01 PM GMT+02:00, Stephen John Smoogen smooge@gmail.com wrote:
On Tue, 4 Jun 2019 at 07:27, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:01:52 +0200, Miroslav Suchý wrote:
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But
I
do not care to which service it will communicate.
I think this is the simplest option at the moment.
I'll start working on making fpaste work with their API soon (PRs
always
welcome, of course). Is there a timeline on pulling the plug on paste.fp.o that I should adhere to?
CentOS has a cpaste application which might help on that.
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Julen Landa Alustiza jlanda@fedoraproject.org
On Tue, 2019-06-04 at 16:41 +0200, Julen Landa Alustiza wrote:
If we are going with the approach of just one paste platform, we could just retire fpaste, add cpaste with an fpaste alias and provides on rpm spec, retire paste.fp.o and redirect it to paste.centos =)
Just a note - if we go this way, the templates used for intallation image creation will have to be adjusted to pull in cpaste instead of fpaste (unless cpaste starts to provide fpaste, which should hopefully pull it in).
On June 4, 2019 2:25:01 PM GMT+02:00, Stephen John Smoogen smooge@gmail.com wrote:
On Tue, 4 Jun 2019 at 07:27, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:01:52 +0200, Miroslav Suchý wrote:
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But
I
do not care to which service it will communicate.
I think this is the simplest option at the moment.
I'll start working on making fpaste work with their API soon (PRs
always
welcome, of course). Is there a timeline on pulling the plug on paste.fp.o that I should adhere to?
CentOS has a cpaste application which might help on that.
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Julen Landa Alustiza jlanda@fedoraproject.org _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
On Tue, Jun 04, 2019 17:12:06 +0200, Martin Kolman wrote:
On Tue, 2019-06-04 at 16:41 +0200, Julen Landa Alustiza wrote:
If we are going with the approach of just one paste platform, we could just retire fpaste, add cpaste with an fpaste alias and provides on rpm spec, retire paste.fp.o and redirect it to paste.centos =)
Just a note - if we go this way, the templates used for intallation image creation will have to be adjusted to pull in cpaste instead of fpaste (unless cpaste starts to provide fpaste, which should hopefully pull it in).
cpaste will have to be packaged up before that can be done too.
I think it's fine to have two different tools here. CentOS and Fedora still move at different speeds, so each tool can be tweaked as per the distro's requirements.
While we are looking at this, we have not talked with and gotten agreement with the person who runs cpaste server. We would need to make sure they have the resources to hold our extra load etc before we do anything like htis.
On Tue, 4 Jun 2019 at 10:41, Julen Landa Alustiza jlanda@fedoraproject.org wrote:
If we are going with the approach of just one paste platform, we could just retire fpaste, add cpaste with an fpaste alias and provides on rpm spec, retire paste.fp.o and redirect it to paste.centos =)
On June 4, 2019 2:25:01 PM GMT+02:00, Stephen John Smoogen < smooge@gmail.com> wrote:
On Tue, 4 Jun 2019 at 07:27, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:01:52 +0200, Miroslav Suchý wrote:
Dne 28. 05. 19 v 9:00 Till Maas napsal(a):
- make fpaste work with paste.centos.org
+1 I use fpaste a lot. So please keep the functionality of fpaste. But
I
do not care to which service it will communicate.
I think this is the simplest option at the moment.
I'll start working on making fpaste work with their API soon (PRs
always
welcome, of course). Is there a timeline on pulling the plug on paste.fp.o that I should adhere to?
CentOS has a cpaste application which might help on that.
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London _______________________________________________ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro...
Julen Landa Alustiza jlanda@fedoraproject.org
On Tue, Jun 04, 2019 11:15:24 -0400, Stephen John Smoogen wrote:
While we are looking at this, we have not talked with and gotten agreement with the person who runs cpaste server. We would need to make sure they have the resources to hold our extra load etc before we do anything like htis.
Would infra do this? I've always only been in-charge of the client and usually am informed of any infra changes that require changes to fpaste.
On Thu, 6 Jun 2019 at 03:36, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:15:24 -0400, Stephen John Smoogen wrote:
While we are looking at this, we have not talked with and gotten agreement with the person who runs cpaste server. We would need to make sure they have the resources to hold our extra load etc before we do anything like htis.
Would infra do this? I've always only been in-charge of the client and usually am informed of any infra changes that require changes to fpaste.
Would infra change to a different server? - Maybe after we have gotten agreement.. and worked out what the affects are.
Or would infra make changes to the fpaste client? - No. That is not something infra would take from a contributor
I was just seeing a lot of people assuming we were doing both and trying to say 'Woah! we haven't even talked to these people yet to make sure it is possible. we are just trying to find out what uses it currently.'
-- Thanks, Regards, Ankur Sinha "FranciscoD" (He / Him / His) | https://fedoraproject.org/wiki/User:Ankursinha Time zone: Europe/London
On Thu, Jun 06, 2019 10:58:49 -0400, Stephen John Smoogen wrote:
On Thu, 6 Jun 2019 at 03:36, Ankur Sinha sanjay.ankur@gmail.com wrote:
On Tue, Jun 04, 2019 11:15:24 -0400, Stephen John Smoogen wrote: > > While we are looking at this, we have not talked with and gotten > agreement with the person who runs cpaste server. We would need to > make sure they have the resources to hold our extra load etc before we > do anything like htis. Would infra do this? I've always only been in-charge of the client and usually am informed of any infra changes that require changes to fpaste.
Would infra change to a different server?
- Maybe after we have gotten agreement.. and worked out what the affects are.
OK. I'll keep an eye out for any news on this front.
Or would infra make changes to the fpaste client?
- No. That is not something infra would take from a contributor
No, I continue to maintain and update fpaste as needed. I can't do the
I was just seeing a lot of people assuming we were doing both and trying to say 'Woah! we haven't even talked to these people yet to make sure it is possible. we are just trying to find out what uses it currently.'
Sure. My info only comes from this ticket that they filed saying they're using "Stikked":
https://pagure.io/fpaste/issue/40
I've got no other data on their setup at all.
On Tue, Jun 04, 2019 16:41:22 +0200, Julen Landa Alustiza wrote:
If we are going with the approach of just one paste platform, we could just retire fpaste, add cpaste with an fpaste alias and provides on rpm spec, retire paste.fp.o and redirect it to paste.centos =)
It really depends on how good of a drop-in replacement cpaste is to fpaste. Ideally, given fpaste is kind of a standard now in the Fedora eco-system, changes should be pushed to it instead of new clients being written. This was a special scenario, though, so it didn't happen.
Luckily, the tools we're dealing with here are so simple that duplication of code isn't much of an issue. I've got a few features requests for fpaste too. So I'll take this opportunity to re-write bits and improve the codebase to implement what can be done.
On Tue, Jun 04, 2019 08:25:01 -0400, Stephen John Smoogen wrote:
<snip>
CentOS has a cpaste application which might help on that.
Yes. I'll look at that as a reference implementation. They did inform us, and at some point the plan was for them to look at doing it with fpaste instead of a new client, but that hasn't happened yet:
https://pagure.io/fpaste/issue/40#comment-531226
On Mon, May 20, 2019 at 12:48 PM Kevin Fenzi kevin@scrye.com wrote:
We are currently running modernpaste for paste.fedoraproject.org.
It's pretty dead upstream. The primary maintainer said they wanted to make a v2 version that was a complete re-write. That was about a year ago and nothing has happened since. ;( We have several outstanding issues against it and some folks don't really like it. It's one of the few things left we have that is using mariadb instead of postgres. It collects spam and has to be cleaned up all the time.
So, we need a plan. I think our options are:
- Your clever idea here.
We could also tell people "use ffsend[1] instead". The main drawback at this point is that it cannot read from stdin, which is a big deal, but it's also something the developer wants to implement[2], and potentially something we could help with as a way of getting paste entirely off our hands.
[1] https://fedoramagazine.org/use-firefox-send-with-ffsend-in-fedora/ [2] https://github.com/timvisee/ffsend/issues/39
On 5/31/19 8:54 AM, Ben Cotton wrote:
On Mon, May 20, 2019 at 12:48 PM Kevin Fenzi kevin@scrye.com wrote:
We are currently running modernpaste for paste.fedoraproject.org.
It's pretty dead upstream. The primary maintainer said they wanted to make a v2 version that was a complete re-write. That was about a year ago and nothing has happened since. ;( We have several outstanding issues against it and some folks don't really like it. It's one of the few things left we have that is using mariadb instead of postgres. It collects spam and has to be cleaned up all the time.
So, we need a plan. I think our options are:
- Your clever idea here.
We could also tell people "use ffsend[1] instead". The main drawback at this point is that it cannot read from stdin, which is a big deal, but it's also something the developer wants to implement[2], and potentially something we could help with as a way of getting paste entirely off our hands.
[1] https://fedoramagazine.org/use-firefox-send-with-ffsend-in-fedora/ [2] https://github.com/timvisee/ffsend/issues/39
Not a bad idea... although firefox send is kind of anoying. Having to download the thing when you just want to look at some text, and mozilla is known for killing things off, so no telling how long it will be around for. That said, it's not a bad idea to look at promoting that service more.
kevin
infrastructure@lists.fedoraproject.org
-
Ankur Sinha -
Ben Cotton -
Brian (bex) Exelbierd -
Julen Landa Alustiza -
Justin W. Flory -
Kevin Fenzi -
Langdon White -
Martin Kolman -
Miroslav Suchý -
Stephen John Smoogen -
Till Maas