Christopher asked about reducing friction in the topic paper submission process, and that I share my results here, @kimdhamilton.
I’m good at research, but am still a newb to web development. Probably there are others, here, more qualified to implementing a solution, than I.
(not sure if this is relevant)
This doesn’t involve uploads but gives a basic example runthru of using netlify forms:
I followed this the other day to create an account and use that account as a bot to submit pull-requests… the end result is for comments… but doesnt support files, only text. However, the first part of creating an account to make a “bot” (to submit the pull-request w file uploads) with would be the same.
I can’t invest any more time on this right now, and I’m not sure if any of this is to the point, because I haven’t found specifically how to use the form to generate a pull-request. Really I’m still not 100% I understand the problem I’m trying to solve here… but this is a good starting point.
My personal thought is that if there is friction with submitting a pull-request, the community would be better served by a thorough set of HowTos, introducing new users to GitHub by walking them through the process of creating an account forking the repository, adding their submission, and submitting a pull-request.
I would be happy to work on some documetation for that, as I’ve been doing for @DIDecentral
using issue\pull-request templates could also help: