Remove mentoring development site

"Need review" seems so strange, changed it to "active". It is active too, I just created the http://groups.drupal.org/padawan-initiative for discussions

In some future a synergy may be expected, but there is a clear difference between the two projects.

We aim at updating d.o. by exploring quick wins, we need a d.o. clone to create some demos for it. The Guild aims at creating an grassroots certifications site.

Considering the posible synergy, I will take contact with that group after making some demos. Thanks for point it to me .

Ok, considering the comments, I've changed the title again. The Padawan Initiative is not to compete with the many good things that are happening, but to find a way to mediate all the efforts. We like more visibility for the projects, aggregate them back to d.o. and while we are at it, create tools and visibility for mentoring efforts.

Gusaus, I'm sorry to hear that, I've tried to created a better explanation here: http://groups.drupal.org/node/172079#comment-572714

I need to stress, I don't think this is a discussion for the current infrastructure-issue. The request here is simple, can we have a d.o. clone to explore features and created demos? I'm sorry about the initial confusing title.

We like a sandbox as new features ask some tryout.

The actual request of infrastructure improvement will only happen if enough people agree on some of the demos explored in the Padawan group. After tryouts and discussion we shall create concrete infrastructure improvement issues.

I'll put the status back to need review as this was the way it got generated by "Make Drupal.org awesome"

So I request both a development site and SSH access to staging.drupal.org, thanks very much !

Hi Neil,

Thanks for the SSH access. I'm planning to give a demo's, but it will take a lot more time because my work just exploded in my face.

I was planning to create a demon about mentoring by adapting the issue queue first, the aggregation of external resources would indeed be a bigger problem as it requires cross-site communication. Still the mentoring queue looks like a quick win. There is a very short description here: http://groups.drupal.org/node/171729

I like the idea of an other documentation iteration, but for showing activities from the issue queue. What I like to add to the user profile for this is something like "fixed XXX issues", or better show per category and priority the amount of contributions. For code this is not so relevant as you have git data, but for mentoring this seems a simple way to create visibility.

I've been playing with the project module locally to figure out how to use it for mentoring and peer-learning in our course (software for management) . The course will staring in 18 oktober (with 300 students), so I'll be generating some experience for peer-learning. I had to change category and priority, but no admin for it exist.

Priority got changed to "level" because the issues would not be about some improvement but about learning. The level of learning is relevant for a possible mentor (or in the course case a reviewer). The level allows people to help out at their own level of knowledge. I include a picture of how it is currently done for our course. For the mentor queue the level would be similar but the categories would be: code, theming, documentation, tutorial, etc.

I've got the feeling I may be kicking open doors and lack knowledge of ongoing improvement to the project module because the changes are too simple. For example, the absence of an admin level to change category and priority. While some part I could change with views, other things I had to change in the code (issue_node_form.inc, issue.inc). I wasn't willing to create an admin interface if there would be a good reason why it does not exist, so I just changed the code directly:

function project_issue_priority($priority = 0) {
//mixel-change-MS from ...
//  $priorities = array(1 => t('critical'), t('normal'), t('minor'));
  $priorities = array(1 => t('basic'), t('normal'), t('advanced'));
  return $priority ? $priorities[$priority] : $priorities;
}

function project_issue_category($category = 0, $plural = 1) {
  if ($plural) {
//mixel-change-MS from ...
//    $categories = array('bug' => t('bug reports'), 'task' => t('tasks'), 'feature' => t('feature requests'), 'support' => t('support requests'));
$categories = array('data' => t('Data sets'), 'model' => t('Management Models'), 'sensitivity' => t('Sensitivity Analyses'), 'MC' => t('Monte Carlos Simulations'));
  }
  else {
//mixel-change-MS from ...
//    $categories = array('bug' => t('bug report'), 'task' => t('task'), 'feature' => t('feature request'), 'support' => t('support request'));
$categories = array('data' => t('Data set'), 'model' => t('Management Model'), 'sensitivity' => t('Sensitivity Analysis'), 'MC' => t('Monte Carlos Simulation'));
  }
  return $category ? $categories[$category] : $categories;
}

I'm guessing a performance issue may be the reason for not having an admin for this part, right? Isn't there a bigger change to project module going on?

Also the required component field confuse me a lot, why isn't it an option like version? I'm wondering why this whole part is not just a CCK that we can change as we like. ... I have the feeling this is probably discussed some where ...

Thanks a lot !

I've really got a lot of work for the coming months, so I sadly will be moving slow, I hope that is not a problem.