If the job includes post matter yaml it should be used to fill in the missing parameters of the job

[ogt]

The most common way that we use nodesk is via
the [post for github issue] button.

I think there is value in capturing the associated budget, question, skill in the issue itself.
I would suggest that we use the "post matter yaml" model (http://jekyllrb.com/docs/frontmatter/) and allow defaults for these params to be set at the end of the issue.

Ie, we add a [retrieve defaults] button next to the issue. When pressed the issue is fetched and we look for text after the last line that starts with 3 dashes. ---
The text that follows is treated as yaml, read and parsed.
We look for attributes Question, Skills, Price (or budget) and we fetch the corresponding values and use them to fill in the subsequent fields

---

Issue [       ]  [retrieve defaults]
Question
Skills
Price

[dglittle]

Sounds good: I'm thinking of a model to address some other issues as well
where pasting the issue url automatically fetches it, and fills in
information, including showing what the oDesk job will look like, so that
it can be edited (to address "preview" issue, and "add additional
questions" issue)

On Sun, May 19, 2013 at 5:43 PM, ogt notifications@github.com wrote:

The most common way that we use nodesk is via
the [post for github issue] button.

I think there is value in capturing the associated budget, question, skill
in the issue itself.
I would suggest that we use the "post matter yaml" model (
http://jekyllrb.com/docs/frontmatter/) and allow defaults for these
params to be set at the end of the issue.

Ie, we add a [retrieve defaults] button next to the issue. When pressed
the issue is fetched and we look for text after the last line that starts
with 3 dashes. ---
The text that follows is treated as yaml, read and parsed.
We look for attributes Question, Skills, Price (or budget) and we fetch

the corresponding values and use them to fill in the subsequent fields

Issue [ ] [retrieve defaults]
Question
Skills
Price

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22
.

[ogt]

yes,
one issue to keep in mind is that

• some inputs are repeated (e.g. questions)
• some inputs have to be given in a very specific way e.g. skills, where odesk wants node.js and not nodejs no commas etc.

The above two mean that it is better to copy the exact text somewhere as opposed to be entering it free text.
Ideally I would need to open

• github to enter the issue
• nodesk to post it

Not having to look for prior jobs, open up editor with saved text etc... would be great.
Still (as I have pointed out in issue #17 , links to the odesk job would be very useful..)

[dglittle]

right..

On Sun, May 19, 2013 at 7:03 PM, ogt notifications@github.com wrote:

yes,
one issue to keep in mind is that

• some inputs are repeated (e.g. questions)
• some inputs have to be given in a very specific way e.g. skills,
  where odesk wants node.js and not nodejs no commas etc.

The above two mean that it is better to copy the exact text somewhere as
opposed to be entering it free text.
Ideally I would need to open

• github to enter the issue
• nodesk to post it

Not having to look for prior jobs, open up editor with saved text etc...
would be great.
Still (as I have pointed out in issue #17#17, links to the odesk job would be very useful..)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-18129260
.