-
Notifications
You must be signed in to change notification settings - Fork 42
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
TODO: use template for issue #3
Comments
I would love to help create the structure of a template based on some of the formatting/content structure issues I have with make-node-meeting. Would you be interested in this? |
@bnb sure. If I understand correctly you'd like to propose a standard template that each WG could start with ? |
@mhdawson just want to ask what do i have to do? (I have no idea.) |
@cPhost the steps I'd suggest are:
Does that make sense ? |
I will start working on it. Thanks. |
@mhdawson i can get the date with out |
@cPhost we can either call make-node-meeting and extract the date info, or look at how it gets it and duplicate it in Node.js so we can put it directly into create-node-meeting-artifacts and not have to call make-node-meeting at all. I'd prefer removing the call to create-node-meeting-artifacts if that is possible. In terms of what to change in step 2, the current code calls make-node-meeting and uses the string returned as the content for the issue. What we want to do instead is to read a new template from a file, If this does not make sense from what you can see in the code then we should try to schedule a time to do a hangout and walk through it together. |
Currently uses make-node-meeting for content of github issue.
Would be better if a template was used. Extract the part which creates the time from make-node-meeting and use templates instead for the issue generation.
The text was updated successfully, but these errors were encountered: