Explore using hackmgm-notes similar to INN docs

[jacquelineIO]

https://github.com/INN/docs -- is a good example of having online documentation in github. I'm not sure if this is ideal for us, but I would like to explore this option.

[jacquelineIO]

markdown cheatsheet https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf

[jacquelineIO]

Create agenda list, you can bullet the issues into markdown, might be a good idea to create an agenda.
https://guides.github.com/features/mastering-markdown/

Issue references within a repository

Any number that refers to an Issue or Pull Request will be automatically converted into a link.

#1
mojombo#1
mojombo/github-flavored-markdown#1

[jacquelineIO]

https://help.github.com/categories/writing-on-github/

[jacquelineIO]

Milestones, good way to group meeting-agenda items entered via issues. https://help.github.com/articles/about-milestones/

[wohlford]

I like this solution a lot. +1 Jacqueline.

[netelysis]

I found it interesting to have seen Ms Flemming's Markdown post due to my having recently read an interesting perspective from another developer on the Markdown language and its functionality. For those who may be interested in an in depth markup language(s) functionality discussion you will probably enjoy perusing the contents. Please enjoy the read New mandoc -mdoc -T markdown converter - http://www.undeadly.org/cgi?action=article&sid=20170304230520

…

On 03/07/17 13:27, jacquelineflemming wrote: markdown cheatsheet https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATQRY8XPMnxK_Dvq-VcsdhTr53zzGMjcks5rja-qgaJpZM4MV6T->.

-- Boyd Stephens Network Engineering Division Netelysis, LLC PO Box 230546 Montgomery, AL 36123 tel. 334.213.1128 web. www.netelysis.com email. bstephens@netelysis.com The information contained in this communication is confidential, may be subject to legal privileges, may constitute inside information, and is intended only for the use of the addressee. It is the property of Netelysis or its relevant affiliate. Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify Netelysis immediately by return e-mail and destroy this communication and all copies thereof, including all attachments.

[wohlford]

Lol

[jacquelineIO]

@netelysis is this your way of saying you won't be doing markdown? :) haha

[wohlford]

On Mar 7, 2017, at 3:12 PM, netelysis ***@***.***> wrote: I found it interesting to have seen Ms Flemming's Markdown post due to my having recently read an interesting perspective from another developer on the Markdown language and its functionality. For those who may be interested in an in depth markup language(s) functionality discussion you will probably enjoy perusing the contents. Please enjoy the read New mandoc -mdoc -T markdown converter - http://www.undeadly.org/cgi?action=article&sid=20170304230520

@netelysis, I looked over that article and I think there is some merit in what the author is saying. Markdown as a language is…not that great. But in I also think what @jacquelineflemming has brought is good too. The difference here is in the implementation. What you have here is theory and practice. Theory being the Markdown lang; practice being GitHub’s implementation. I’ve used Markdown on Github before and it was more helpful in communicating my idea better than plain text. The nice thing is if you don’t want to use Markdown, then *DON’T!*. Lol. Plain text away, my friend.

[jacquelineIO]

@elijahlofgren and @wohlford OK, checkout the notes front now. https://github.com/HackMGM/hackmgm-notes/

We can completely remove this stuff... but just an idea of trying to keep our ducks in a row until we get a better way... or keep this.

[elijahlofgren]

@jacquelineflemming - looking good! Thanks for taking the initiative to try to start organizing this information. You could maybe add a link to this on the website homepage so it is easy to get to.

[netelysis]

No ma'am. I am simply a fan of viewing a set of circumstances from every conceivable angle. 8^) I am actually a big fan of markUP languages due to their allowing one to fully focus on content and substance and then having a entirely different vehicle for adjusting layouts, presentation choices, etc. Superly cool stuff. If you desire to explore this subject matter future and you are not already aware of the details I would encourage your investigating the TeX/LaTeX combination. I originally ran across these guys a number of years ago while working at a university. There is genuinely no better way to format any form of a scientific/technology oriented paper that is full of sub and super scripts and mathematical formulas. Again, superly cool stuff.

…

On 03/07/17 19:10, jacquelineflemming wrote: @netelysis <https://github.com/netelysis> is this your way of saying you won't be doing markdown? :) haha — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATQRYwYjp0tXeaRB0OOkp5HlaH-8vcL-ks5rjf_6gaJpZM4MV6T->.

-- Boyd Stephens Network Engineering Division Netelysis, LLC PO Box 230546 Montgomery, AL 36123 tel. 334.213.1128 web. www.netelysis.com email. bstephens@netelysis.com The information contained in this communication is confidential, may be subject to legal privileges, may constitute inside information, and is intended only for the use of the addressee. It is the property of Netelysis or its relevant affiliate. Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify Netelysis immediately by return e-mail and destroy this communication and all copies thereof, including all attachments.

[netelysis]

As I shared earlier with Sis McKinney, my sending the additional info was not reflection on whether or not I DESIRED TO UTILIZE MARKDOWN. I had simply read an interesting perspective on markdown a few days prior to McKinney making the suggestion and decided to share the content of my reading with the rest of the crew. Everything, no scratch that, most things in life are not an either/or. As to plain text, it has its place as does working with markUP languages.

…

On 03/07/17 20:38, Jason Wohlford wrote: > On Mar 7, 2017, at 3:12 PM, netelysis ***@***.***> wrote: > > I found it interesting to have seen Ms Flemming's Markdown post due to > my having recently read an interesting perspective from another > developer on the Markdown language and its functionality. For those who > may be interested in an in depth markup language(s) functionality > discussion you will probably enjoy perusing the contents. > > Please enjoy the read > > New mandoc -mdoc -T markdown converter > - http://www.undeadly.org/cgi?action=article&sid=20170304230520 @netelysis, I looked over that article and I think there is some merit in what the author is saying. Markdown as a language is…not that great. But in I also think what @jacquelineflemming has brought is good too. The difference here is in the implementation. What you have here is theory and practice. Theory being the Markdown lang; practice being GitHub’s implementation. I’ve used Markdown on Github before and it was more helpful in communicating my idea better than plain text. The nice thing is if you don’t want to use Markdown, then *DON’T!*. Lol. Plain text away, my friend. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATQRYz-3EIInNpOxHC6RQ7DkqehVomU7ks5rjhSrgaJpZM4MV6T->.

-- Boyd Stephens Network Engineering Division Netelysis, LLC PO Box 230546 Montgomery, AL 36123 tel. 334.213.1128 web. www.netelysis.com email. bstephens@netelysis.com The information contained in this communication is confidential, may be subject to legal privileges, may constitute inside information, and is intended only for the use of the addressee. It is the property of Netelysis or its relevant affiliate. Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify Netelysis immediately by return e-mail and destroy this communication and all copies thereof, including all attachments.

[jacquelineIO]

I knew it was a read for entertainment. I was just teasing you. I actually wrote an algorithm paper while I was getting my masters in LaTEX mainly because it was free :) it's a beast. I haven't used it since however.

…

Sent from my iPhone

On Mar 8, 2017, at 9:31 AM, netelysis ***@***.***> wrote: As I shared earlier with Sis McKinney, my sending the additional info was not reflection on whether or not I DESIRED TO UTILIZE MARKDOWN. I had simply read an interesting perspective on markdown a few days prior to McKinney making the suggestion and decided to share the content of my reading with the rest of the crew. Everything, no scratch that, most things in life are not an either/or. As to plain text, it has its place as does working with markUP languages. On 03/07/17 20:38, Jason Wohlford wrote: > > On Mar 7, 2017, at 3:12 PM, netelysis ***@***.***> wrote: > > > > I found it interesting to have seen Ms Flemming's Markdown post due to > > my having recently read an interesting perspective from another > > developer on the Markdown language and its functionality. For those who > > may be interested in an in depth markup language(s) functionality > > discussion you will probably enjoy perusing the contents. > > > > Please enjoy the read > > > > New mandoc -mdoc -T markdown converter > > - http://www.undeadly.org/cgi?action=article&sid=20170304230520 > > @netelysis, I looked over that article and I think there is some merit > in what the author is saying. Markdown as a language is…not that > great. But in I also think what @jacquelineflemming has brought is > good too. The difference here is in the implementation. What you have > here is theory and practice. Theory being the Markdown lang; practice > being GitHub’s implementation. I’ve used Markdown on Github before and > it was more helpful in communicating my idea better than plain text. > > The nice thing is if you don’t want to use Markdown, then *DON’T!*. > Lol. Plain text away, my friend. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ATQRYz-3EIInNpOxHC6RQ7DkqehVomU7ks5rjhSrgaJpZM4MV6T->. > -- Boyd Stephens Network Engineering Division Netelysis, LLC PO Box 230546 Montgomery, AL 36123 tel. 334.213.1128 web. www.netelysis.com email. ***@***.*** The information contained in this communication is confidential, may be subject to legal privileges, may constitute inside information, and is intended only for the use of the addressee. It is the property of Netelysis or its relevant affiliate. Unauthorized use, disclosure or copying of this communication or any part thereof is strictly prohibited and may be unlawful. If you have received this communication in error, please notify Netelysis immediately by return e-mail and destroy this communication and all copies thereof, including all attachments. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[wohlford]

I knew it was a read for entertainment. I was just teasing you. I actually wrote an algorithm paper while I was getting my masters in LaTEX mainly because it was free :) it's a beast. I haven't used it since however.

+1 @jacquelineflemming