Lesson and project wishlists/suggestions

This is a different idea from, but could be closely related to, this issue (http://drupal.org/node/201898) that is about teacher lesson submissions. Much of the "base" info of a lesson could be the same whether it is a suggestion from the public or someone who wishes to teach it. The details can be added by a teacher in that pipeline. So that if it starts life as a plain suggestion, a teacher can pick it up and fill in details saying they want to teach it or a teacher can just create a suggestion and add all the details upon initial submission. This could get sticky and we don't want to confuse people who are just suggesting and have them feel like they have to fill in everything for actual teaching. Anyway, an idea to help steamline things. We would obviously need to really work out the details, UI and workflow.

I posted a similar issue here (http://drupal.org/node/201622). I 'think' the same submission/suggestion system should be able to work for lessons AND tasks/projects.

...took this from the issue mentioned above.

Possibly we can take a look at the GHOP task format as something that would work for Drupal Dojo.

GHOP Template for submissions

• Title
  • A short description of what the task entails
• Description
  • An initial sentence or two that describes what the task entails and the value prop (emphasize importance to project, transferable skills...).
  • Several sentences/bullets that provide more detail into the task: What approach should students use? What level of detail are you looking for?
  • A sentence about what the expected deliverable is (a tutorial reviewed by at least one member of the documentation team and posted to the handbook, a patch in the core issue queue marked ready to be
    committed...)
• Resources
  • Bulleted list of resources specific to the task.
    
  • This includes handbook pages, off-site resources, IRC channels, related groups on groups.drupal.org, etc.
• Estimated time - a "day" range of how long you think the task will take to complete
• Primary contact
• The person we should list as the "owner" of the task, who will monitor student submissions and give the final sign-off.
  
• This should be either you or someone who you've talked to about taking this on.
  

Relevant GHOP pages:
How to write a good task - could a similar set of guidelines/template work for Dojo?
Instructions on how to submit a task idea - similar thing for dojo lessons, tasks and workshops?
Notes for administrators - A lot of these ideas/examples might work mentors and ninjas? These also are guidelines on how folks in the Dojo could help.
Possibly this template could be the basis for our own CCK type? - http://drupal.org/node/202086

@add1sun

if it starts life as a plain suggestion, a teacher can pick it up and fill in details saying they want to teach it or a teacher can just create a suggestion and add all the details upon initial submission. This could get sticky and we don't want to confuse people who are just suggesting and have them feel like they have to fill in everything for actual teaching.

I'd be thinkin' that if we made a CCK content type just right, users could start it's life as a "suggestion", teachers within an different role could add their availability and scheduled dates to the fields that they were allowed to see, and then site admins could approve the node by changing the fields they were allowed to see, such as scheduling the node for a live broadcast date on the calendar, thus allowing users to Signup.module the node!

Oooooh. I *like* this!

Druplicon> http://drupal.org/node/207042 => Lesson and project wishlists/suggestions => Drupal Dojo 2.0, Website, normal, active, 1 IRC mention
[14:29] +1
[14:29] A way for anyone to submit a lesson suggestion.
[14:30] +2
[14:30] +1
[14:30] +1
[14:30] heh
[14:30] I'm in agreement though, that these three are all really tied together.
[14:30] agree
[14:30] Since it sounds like the same node will be doing all three
[14:30] Senpai, yes, that is one way to do it
[14:30] * Senpai hugs nodeAPI
[14:30] and ideal
[14:31] but we shouldn't vote on that - just the ideas
[14:31] ;)
[14:31] +1

Project is abandoned. Closing all issues.

This form can be used as a proof of concept -
http://spreadsheets.google.com/viewform?key=pcGm-G-g986oxj9Q7F9RnIg&hl=e...

There are several good examples that could serve the basis for a solution -

* http://badcamp.net/sessions
* http://drop.cwgordon.com/tasks/open
* http://boston2008.drupalcon.org/sessions

Until a system is implemented on the new site, there are a set of potential lesson/session ideas, guidelines, and submission forms on the 'Lesson Ideas and Interactive workshop wiki' - http://groups.drupal.org/node/2433

Consolidating with other issues