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:

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"


I am for #2&&#4 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.
 
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?


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.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.fedoraproject.org



--
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.fedoraproject.org


--
Stephen J Smoogen.