New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commencing Dev/Testing Stage (v0.0.1fork) #7
Comments
Sorry, I'm slightly confused with what you want here. Do you just want me to define cleat steps on how others can contribute to html.md? If so, I can create a CONTRIBUTING.md file, as I believe is thwarted standard and document this. If not, I'm going to need some more help understanding. Note: Honestly, I'm mot developing html.md the best way I could in terms of process as I'm just pushing directly to the master, but time constraints have forced me. After the next release I will follow a set process personally as well as require others to do so. |
Sorry for the confusion. I see now how it would be. In a nutshell I was trying to (first time at that ie. An experiment): • Give notice to you that I'll be forking and testing on my side That's it. Nothing needed from you for this in particular - just an FYI thing, if I can call it that. Hope that makes sense? -----Original Message----- Sorry, I'm slightly confused with what you want here. Do you just want me to define cleat steps on how others can contribute to html.md? If so, I can create a CONTRIBUTING.md file, as I believe is thwarted standard and document this. If not, I'm going to need some more help understanding. Note: Honestly, I'm mot developing html.md the best way I could in terms of process as I'm just pushing directly to the master, but time constraints have forced me. After the next release I will follow a set process personally as well as require others to do so. Reply to this email directly or view it on GitHub: |
Ps. You mentioned a "get to a protocol later on" aspect. That's fine, but (IMO and IME) later never comes soon enough. I am backlogged with work because I star the mails for todo:later. Just something to consider. Not implying you're incapable or won't get to it later... Not at all. I honestly am in awe of your projects. We should chat sometime maybe? Are you on gtalk or skype? -----Original Message----- Sorry for the confusion. I see now how it would be. In a nutshell I was trying to (first time at that ie. An experiment): • Give notice to you that I'll be forking and testing on my side That's it. Nothing needed from you for this in particular - just an FYI thing, if I can call it that. Hope that makes sense? -----Original Message----- Sorry, I'm slightly confused with what you want here. Do you just want me to define cleat steps on how others can contribute to html.md? If so, I can create a CONTRIBUTING.md file, as I believe is thwarted standard and document this. If not, I'm going to need some more help understanding. Note: Honestly, I'm mot developing html.md the best way I could in terms of process as I'm just pushing directly to the master, but time constraints have forced me. After the next release I will follow a set process personally as well as require others to do so. Reply to this email directly or view it on GitHub: |
#12 - "Fresh, more issue-looking issue". Close this pseudo-issue... |
Aside: Not really an issue per se, but is it not the best way to induce notifications in that blue dot box next to the Github... uh Octocat logo (what happened to the Github one?) - if not the only way?*
Workflow (Tips, suggestions welcome)
If I got any of the terminology wrong, please correct me - I'm more concerned about the thing doing its thing than I am what I termed it.
I don't think I can "assign" myself on your repo, but if you want to you can assign me and/or whoever else
The text was updated successfully, but these errors were encountered: