create call for submissions

[dcwalk]

Sorry, had to go the academic tooling route, drafting here: https://docs.google.com/document/d/14-N79UdKsayX995NPaNj4a2snVqs3aP2rFS2MfKoHVI/edit

At 2018-02-24 call we identified the remaining TODOs for this:

• test prose for templating (@patcon) and @benhylau did a issue-based flow for submissions
• make decision on submission mechanism (&co) -- github issues new repo
• review CFP text (@dcwalk &co)
• final CFP polish (@dcwalk) -- final markdown-formatted CFP: https://hackmd.io/s/S1wc8p-OG#
• set up submission repo (@dcwalk) - 2018-submissions
• up on website (handled in Update website with CFP in FEB #25)

will finish by weekend!

[dcwalk]

Some portion of submissions process will be addressed in #31

[patcon]

After like a half-hour of testing and digging into code, I'm pretty sure that customizing the content area of the prose.io "new file" page isn't possible :(
Re: prose/prose#437

So I think the best it could be is that we say "copy this text into a new file and fill in the blanks". It's a small step, but I'd understand if that makes prose not worth it.

Alternatively, I also have push access on the prose repo, and it's hosted on github pages. So if we do it respectfully, we technically have the ability to make this work for us

[benhylau]

The main issue I have with using prose.io is that it would require me to let prose.io access all my public repositories. There is no granularity to let it only access this one repo. So the minimal requirement now for me to submit a proposal becomes:

1. Have a GitHub account
2. Authorize prose.io to access all of my public repositories

I think it is much simpler to file a Github Issue with an Github Issue Template. See example repository I made for this: https://github.com/benhylau/issue-template/issues/new

[dcwalk]

@benhylau -- I didn't think prose would be presented as a requirement to submit, more an option for people who are unfamiliar with the github PR flow, (edit: but I see the point about complexity)

[dcwalk]

Thanks people for reviewing CFP, I did another pass yesterday and this morning. There are lingering comments in the middle para I will polish tonight, and then all that is left is WORKFLOW!!!!!

So can we do a basic vote on this issue comment?
🎉 = PR with optional prose submission in 2018 repo
❤️ = Github issue and template in 2018-submissions standalone repo

attn: @patcon @benhylau @garrying @jkms

[patcon]

@benhylau see my comment to the hacks/hackers folks: hackshackers/hackshackers-hugo#86 (comment)

the one additional bit of new info since then is that it's been non-https up until now, but that's getting resolved this week apparently: prose/prose#825 (comment)

[dcwalk]

great thanks for voting! Looks like issue route, I'll set up the process this evening :)

[dcwalk]

okay I lied, anyone wanna take a look make sure I'm not missing something: https://github.com/ournetworks/2018-submissions?

Also added some signage (and issue template, sorry! not-sorry!) for this repo to steer people over there hopefully

[patcon]

Looks rad! My one thought might be to use ournetworks.ca/cfp and just use jekyll redirects to the front page while it's there? Feels less link rotty, I suppose :)

If sounds good, happy to submit PR

[dcwalk]

Hey @patcon if I understand correctly I think 👍 from me! Only thought is whether ournetworks.ca/2018 rather than cfp would make sense? (the previous year lives on /2017) let's move convo to a PR in ournetworks.ca tho! 🙏