Collect judge data interactively instead of hand-editing judges.json? #3
Comments
|
I think the pull-request workflow is sufficiently painful for images that putting any effort into a web form would be much preferable. |
|
Totally agree @johnhawkinson, and I want to move away from that process. One process I've been tinkering with is to use Github issues as a submission form. For example, this link is kind of insane, but also kind of effective: Oddly, bit.ly and goo.gl both think it's an invalid link, but it does seem to work, providing a form for you to fill out and a way you can drag and drop your photos into Github. One issue is that it crashes github if you're not logged in. Another is that it's an insane link. Two other thoughts:
Where this needs to land is that anybody with two wits can do a submission without knowing the first thing about code. |
|
The other reason we haven't moved forward on this process in a material way is that we need to be very careful about copyright. One stupid infraction and we're sunk. Ideally, we find a way for DMCA to protect us, but if we're reviewing people's submissions I don't think we can even use that shield. cc: @brianwc |
|
@mlissner I think the feature you're looking for is issue templates: https://github.com/blog/2111-issue-and-pull-request-templates |
|
@anseljh Yeah, but those always apply to every issue in a repo, which isn't what we want. |
Seems we could eliminate the hand-editing-JSON step in the contribution guidelines by adding some interactive prompts in the
convert_images.pyscript, or a wrapper around it. That might make it a little easier for novices to contribute. On the other hand, the effort might better spent making a web form instead.The text was updated successfully, but these errors were encountered: