This is an attempt at clarifying the chronology of the contribution process.
make it explicit that authors should host their scripts on a public git repo
now that we have ;install <git_url>, I feel like creating a lines thread could occur before declaring it on the maiden community repo
more explicit explanation of the role of a script inline header documentation
mention about the wiki and that it can be linked to in the maiden community repo entry
I initially tried to keep the contribute & gather section separated, but had a hard time given how interleaved they were.
It's certainly due to the "chicken & egg problem" between publishing a script and communicating about it on lines + the wiki (w/ all the X-referencing).
I kinda feel that this whole process might be worth having it's own how-to documentation page separated from this maiden page (with maybe a small flowchart showing which steps are optional) but didn't want to make too many changes at once.
This is an attempt at clarifying the chronology of the contribution process.
;install <git_url>
, I feel like creating a lines thread could occur before declaring it on the maiden community repoI initially tried to keep the
contribute
&gather
section separated, but had a hard time given how interleaved they were. It's certainly due to the "chicken & egg problem" between publishing a script and communicating about it on lines + the wiki (w/ all the X-referencing).I kinda feel that this whole process might be worth having it's own how-to documentation page separated from this maiden page (with maybe a small flowchart showing which steps are optional) but didn't want to make too many changes at once.