Great idea!<br><br>1. Should include Earl Miles' new <a href="http://drupal.org/project/update_status">Update Status</a> module for constant module status.<br>2. Should include some software development process plugins on a simple level. I am thinking of adding some kind of xp (extreme programming) tracker stuff, which could be as simple as an alternative set of issue status and types, plus some way of indicating issues by teams.
<br>3. Along these lines, some way of integrating the following concepts with issues:<br> a. User Stories (node type with additional fields (cck) and view)<br> b. Test Cases (node type with additional fields (cck) and view)
<br><br>That way this could come with an "XP Tracker" option built in as another layer without changing anything "core".<br><br>saludos,<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar
</a><br>(upgrade to 5.0 awaiting upgrade data path for projects and project issues modules from 4.7: sorry I don't have time to help more :( )<br><br><div><span class="gmail_quote">On 2/28/07, <b class="gmail_sendername">
Derek Wright</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
while waiting for Dries to officially RTBC the issue for hosting<br>install profiles on d.o , i just had an idea for a install<br>profile: the development profile. things it could do:<br><br>1) install/configure devel.module
<br><br>2) setup some standard roles for testing (non-uid-1 admin, content<br>admin, a role that only has "switch users" permission, etc), and<br>configure all perms appropriately.<br><br>3) create a small pool of users in each of the roles, all of which
<br>are also in the "switch users" role, enable the switch users block<br>from devel.module, etc. <br><br>4) also create a bunch of random users with the generate script from<br>devel.module...<br><br>5) create a bunch of test content with the generate script.
<br><br>6) create a bunch of malicious (XSS-seeking) content: node titles,<br>taxonomy terms, anything we can think of that some module might not<br>be escaping properly somewhere. basically, wrap js alert boxes<br>around just about any possible user-input we can find. ;)
<br><br>7) install as much of the simpletest.module and framework as<br>possible, and otherwise prompt/warn the user about the external<br>library they should download and install.<br><br>8) perhaps install some per-node-access module(s) (tac_lite,
<br>simpleaccess, etc) and configure some of the auto-generated content<br>to be private.<br><br>9) optionally install some other handy modules folks use for testing<br>(i'm a big fan of diff.module and dba.module, but there might be
<br>others that would be useful).<br><br>10) perhaps install/configure some kind of benchmarking tools (if any<br>exist that would be appropriate).<br><br>...<br><br><br>this would:<br><br>a) save a ton of time whenever one of us needs to setup a local test
<br>site<br><br>b) make it *much* easier for newer developers to get a standard test<br>environment up and running<br><br>c) facilitate being able to reproduce bugs, since everyone could be<br>working from a more standardized test environment most of the time
<br><br>d) lower the barrier to developers running (and therefore writing)<br>simpletests for their code<br><br>e) help find XSS more quickly, since folks (and automated tests)<br>would be navigating through a site that was trying to XSS-ify itself
<br>all over the place. just having the per-node-privacy content auto-<br>generated would help remind folks to test those sorts of edge cases<br>in their code, too.<br><br><br>i don't have time to work on this, but i'd be willing to help someone
<br>(s) else. or, if anyone thinks this is such a good idea, they want<br>to pay me to work on it instead of my other consulting gigs, that<br>might work, too. ;) if we could stand to wait that long, this might<br>make a nice SoC 2007 project, too.
<br><br>thoughts?<br>-derek<br><br><br> <a href="http://drupal.org/node/113939">http://drupal.org/node/113939</a><br><br> it'd be nice if there was a setting in devel.module to restrict<br>the choices in the switch user block to users that have 'switch
<br>users' permission, so that such a test environment would always allow<br>you to quickly switch back and forth across differently perm'ed<br>users, without ever getting "stuck" on a random user that didn't have