<div><br>Because Drupal is an open-source and collaborative CMS, I think it is very interesting if schools start adopting it. <br>For my school's project I've chosen to work with Drupal and I was hoping to learn from it, giving my time in return. <br>
So I leave here my (so far) experience with Drupal use.<br>This is my school project and this is the way it was planned to be carried out.</div>
<div><br>==DRUPAL'S APPROACH</div>
<div> </div>
<div>1 - DRUPAL| INTRODUCTION: First steps</div>
<div><br>Reading / viewing tutorials and handbooks..</div>
<p> >Studying Drupal's API<br> >…</p>
<p>Installing different Drupal versions</p>
<p> >Requirements <br> >5 and 6</p>
<p>Install different modules</p>
<p> >Download<br> >Activate<br> >Use<br> <br>Create new simple modules</p>
<p> >New content types<br> >…</p>
<div>2 - DRUPAL| COMMUNITY: Interaction with drupal members</div>
<div><br>Enter Drupal community:<br>>Create a user account</div>
<p>>Install development versions: 5.x, 6.x and 7.x </p>
<p>>Entering Forum:</p>
<p> >>Make some simple forum maintenance: Close old issues<br> Critera:version: x.y.z >active/patch/task <br> <br> >>>Read all active issues of x.y.z version<br> >>>Bump all feature requests (x.y.z), why? </p>
<p> >This version is no longer maintained <br> >Feature requests are placed against the most current dev version.<br> >Give these feature requests one last chance of being reviewed<br> >Clean up old issues that are no longer useful<br>
>Understand which of these feature requests have been implemented in more recent versions</p>
<p> >>>Review all bumped issues and see community response to them<br> >>>Participate on finding solutions to this issues<br> >>>Is this useful?</p>
<p> >It's good for learning<br> >x.y.z feature requests become a closed chapter<br> >Some good forgotten ideas can be reconsidered once again</p>
<p> >>>Downsides?<br> >Users get spammed with old issues</p>
<p><br> >>>"Bug hunting": </p>
<p> >Read/understand <br> >Reproduce <br> >Solve some simple bugs by patching</p>
<p> </p>
<p>3 - DRUPAL| DEVELOPMENT: Improve or enhance the software</p>
<div> Two possible ways:<br> <br> >Create new contributed modules<br> >Start a new Drupal Site</div>
<div> </div>
<div>4 - CONCLUSION<br> </div>
<div>My current status is at "bump all feature requests", so I have aprox. 80 x.y.z. issues left.<br>But at this moment, I can't bring this task to an end using my first account (because it's blocked), so I would like to have some community <br>
feedback about my Drupal Approach:</div>
<p> >Is it worth taking?<br> >Does it bring any value to Drupal community?<br> >What can be done to improve it?</p>
<p> <br>Once this is a community I think this as place of debate: ideas / work methodology etc. <br>So it's my understanding that all opinions and different approaches should be respected and discussed. <br>Because of my recent block account experience (which I'm having a difficulty to understand it's reasons) I would also like to know what <br>
the general opinion on blocking user accounts is:</p>
<p> >Criteria (when does it applies?)<br> >Procedures (how should be the process conducted?)</p>
<p> <br>I'll end now, leaving a couple of suggestions concerning the reason that brought me a blocked account:<br>By bump x.y.z feature requests, I "disturbed(chx)" Drupal's users. What if:<br> <br> >We could add a subscribe functionality in issue posts, in order to allow users keeping track <br>
of the issues each one was interested in, avoiding to be popped up with old issues or topics they have no interest in. </p>
<p> Or<br> <br> >Create a forum maintenance routine that places all feature requests from non-maintained versions against the most current <br>dev version.</p>
<div>By doing this I hope to bring to discussion some questions I find important to any person considering using and learning with Drupal.</div>
<div><br>I appreciate the time you took reading this mail and any opinion/suggestion or whatever, I consider it valuable to my Drupal's experience.<br>(Any difficulty understanding my English, just ask me that I'll clarify) </div>
<p> </p>
<p> </p>