Skip to content
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

Rebaselining the nodeMCU Lua official FAQ #937

Closed
TerryE opened this issue Jan 14, 2016 · 4 comments
Closed

Rebaselining the nodeMCU Lua official FAQ #937

TerryE opened this issue Jan 14, 2016 · 4 comments
Assignees

Comments

@TerryE
Copy link
Collaborator

TerryE commented Jan 14, 2016

If we are going to move the FAQ into the distro, then we can hardly call it unofficial (see #449 for previous issue). This is to discuss the necessary changes to prepare the FAQ for moving into the official document set.

@TerryE TerryE changed the title Creating a nodeMCU Lua official FAQ Rebaselining the nodeMCU Lua official FAQ Jan 16, 2016
@TerryE TerryE self-assigned this Feb 17, 2016
@marcelstoer
Copy link
Member

"How to write a new module" (inspiration from http://desperate-programmers.com/2016/01/19/creating-a-new-nodemcu-user-module/) would be a page of its own rather than an FAQ question, right?

Update I knew we had talked about this before: #1026

@TerryE
Copy link
Collaborator Author

TerryE commented Apr 11, 2016

Yes I t hunk that we need to split the FAQ into two parts: one for Lua developers and one for C module developers. I am still working one these as a b/g activity.

@TerryE
Copy link
Collaborator Author

TerryE commented Jun 19, 2017

@marcelstoer Marcel, thanks for this. What I suggest is that we open a new issue to role forward any open points and to act as a discussion framework for the next round of enhancements. What would be good is if we could get an active discussion going with some of the more experienced Lua developers to get their feedback on the issues that trip them up and address these within a FAQ framework, but let's have this discussion on the new issue.

@marcelstoer
Copy link
Member

Sure, I wouldn't mind, feel free to open a new issue. For the stuff I am interested in I opened and will continue to open dedicated issues (#1861 & #1862 for now).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants