I'm currently working on a project which, until yesterday, was going to happen in Drupal. I'm now considering using RoR but since I'm not a programmer I'm in the market for one.
The project in question is a workflow solution for a series of scripts for a childrens' animated TV series (26 episodes). Each script/episode goes through a series of stages/phases requiring approval to progress from one stage to the next. The series has a number of writers assigned to it, each writer being responsible for a few of the scripts. Overseeing the script-writing process are a few script-editors (whose approval will be required to move a script from one stage to the next stage). Overseeing the entire process is a producer whose approval will be required for the final draft version of the script ie. the final approval on each script will reside with the producer. In addition to this there are a number of other personnel who will need to be notified on occasion, though not as regularly as the above.
Access to the material would be limited on a per-episode basis ie. each writer and script editor have access only to the scripts which they are in charge of. Some personnel will have global access ie. to all levels whilst some instances will require access on a per node basis ie. the user has access only to a specific node.
The overall workflow consists of a series of cycles. Typically such a cycle will consist of
1. the writer submits material 2. the system sends out an e-mail to all personnel with access to that script 3. the script editor downloads the material and reviews it 4. if the material requires no further work the editor approves it - based on this action the system sends out an e-mail to all involved 5. if the material requires further work the editor uploads notes - based on this action the system sends out an e-mail to all involved
Most of the users of the site will have very little computer experience (other than script-writing and e-mail software) and as such the process needs to be as simple as possible.
I have a budget of US$2,000 available for this project.
If you're interested and would like to know more please contact me directly on graph...@olesturm.com.
> I'm currently working on a project which, until yesterday, was going to > happen in Drupal. I'm now considering using RoR but since I'm not a > programmer I'm in the market for one.
> The project in question is a workflow solution for a series of scripts for > a childrens' animated TV series (26 episodes). Each script/episode goes > through a series of stages/phases requiring approval to progress from one > stage to the next. The series has a number of writers assigned to it, each > writer being responsible for a few of the scripts. Overseeing the > script-writing process are a few script-editors (whose approval will be > required to move a script from one stage to the next stage). Overseeing the > entire process is a producer whose approval will be required for the final > draft version of the script ie. the final approval on each script will > reside with the producer. In addition to this there are a number of other > personnel who will need to be notified on occasion, though not as regularly > as the above.
> Access to the material would be limited on a per-episode basis ie. each > writer and script editor have access only to the scripts which they are in > charge of. Some personnel will have global access ie. to all levels whilst > some instances will require access on a per node basis ie. the user has > access only to a specific node.
> The overall workflow consists of a series of cycles. Typically such a cycle > will consist of
> the writer submits material > the system sends out an e-mail to all personnel with access to that > script > the script editor downloads the material and reviews it > if the material requires no further work the editor approves it - based > on this action the system sends out an e-mail to all involved > if the material requires further work the editor uploads notes - based > on this action the system sends out an e-mail to all involved > Most of the users of the site will have very little computer experience > (other than script-writing and e-mail software) and as such the process > needs to be as simple as possible.
> I have a budget of US$2,000 available for this project.
> If you're interested and would like to know more please contact me directly > on graph...@olesturm.com.
Sorry, not to be a giant prick (hi guys), but for 2000USD (2001.50AUD
as Matt puts it) its going to be very hard to work in that budget. The
initial specs will eat at that immensely. If they test it might be a
little lower. ;)
I'd recommend using something that already exists or getting some real
cash out and putting it on the table.
Also, this list is pretty dead. PORN ADS COME TO OURS!
On Feb 20, 2:55 pm, "ole sturm" <odst...@gmail.com> wrote:
> I'm currently working on a project which, until yesterday, was going to
> happen in Drupal. I'm now considering using RoR but since I'm not a
> programmer I'm in the market for one.
> The project in question is a workflow solution for a series of scripts for a
> childrens' animated TV series (26 episodes). Each script/episode goes
> through a series of stages/phases requiring approval to progress from one
> stage to the next. The series has a number of writers assigned to it, each
> writer being responsible for a few of the scripts. Overseeing the
> script-writing process are a few script-editors (whose approval will be
> required to move a script from one stage to the next stage). Overseeing the
> entire process is a producer whose approval will be required for the final
> draft version of the script ie. the final approval on each script will
> reside with the producer. In addition to this there are a number of other
> personnel who will need to be notified on occasion, though not as regularly
> as the above.
> Access to the material would be limited on a per-episode basis ie. each
> writer and script editor have access only to the scripts which they are in
> charge of. Some personnel will have global access ie. to all levels whilst
> some instances will require access on a per node basis ie. the user has
> access only to a specific node.
> The overall workflow consists of a series of cycles. Typically such a cycle
> will consist of
> 1. the writer submits material
> 2. the system sends out an e-mail to all personnel with access to
> that script
> 3. the script editor downloads the material and reviews it
> 4. if the material requires no further work the editor approves it
> - based on this action the system sends out an e-mail to all involved
> 5. if the material requires further work the editor uploads notes
> - based on this action the system sends out an e-mail to all involved
> Most of the users of the site will have very little computer experience
> (other than script-writing and e-mail software) and as such the process
> needs to be as simple as possible.
> I have a budget of US$2,000 available for this project.
> If you're interested and would like to know more please contact me directly
> on graph...@olesturm.com.
> On Feb 20, 2008 2:55 PM, ole sturm <odst...@gmail.com> wrote: >> Hi everyone,
>> I'm currently working on a project which, until yesterday, was >> going to >> happen in Drupal. I'm now considering using RoR but since I'm not a >> programmer I'm in the market for one.
>> The project in question is a workflow solution for a series of >> scripts for >> a childrens' animated TV series (26 episodes). Each script/episode >> goes >> through a series of stages/phases requiring approval to progress >> from one >> stage to the next. The series has a number of writers assigned to >> it, each >> writer being responsible for a few of the scripts. Overseeing the >> script-writing process are a few script-editors (whose approval >> will be >> required to move a script from one stage to the next stage). >> Overseeing the >> entire process is a producer whose approval will be required for >> the final >> draft version of the script ie. the final approval on each script >> will >> reside with the producer. In addition to this there are a number of >> other >> personnel who will need to be notified on occasion, though not as >> regularly >> as the above.
>> Access to the material would be limited on a per-episode basis ie. >> each >> writer and script editor have access only to the scripts which they >> are in >> charge of. Some personnel will have global access ie. to all levels >> whilst >> some instances will require access on a per node basis ie. the user >> has >> access only to a specific node.
>> The overall workflow consists of a series of cycles. Typically such >> a cycle >> will consist of
>> the writer submits material >> the system sends out an e-mail to all personnel with access to >> that >> script >> the script editor downloads the material and reviews it >> if the material requires no further work the editor approves it >> - based >> on this action the system sends out an e-mail to all involved >> if the material requires further work the editor uploads notes - >> based >> on this action the system sends out an e-mail to all involved >> Most of the users of the site will have very little computer >> experience >> (other than script-writing and e-mail software) and as such the >> process >> needs to be as simple as possible.
>> I have a budget of US$2,000 available for this project.
>> If you're interested and would like to know more please contact me >> directly >> on graph...@olesturm.com.
>> Thanks in advance,
>> Ole
/************************************************/ Steven Holloway Programmer, Web Developer, IT Consultant Composer, Producer, Performer, DJ p. 0437 541 276 e. impur...@gmail.com /************************************************/
> I'm currently working on a project which, until yesterday, was going to > happen in Drupal. I'm now considering using RoR but since I'm not a > programmer I'm in the market for one.
> The project in question is a workflow solution for a series of scripts for > a childrens' animated TV series (26 episodes). Each script/episode goes > through a series of stages/phases requiring approval to progress from one > stage to the next. The series has a number of writers assigned to it, each > writer being responsible for a few of the scripts. Overseeing the > script-writing process are a few script-editors (whose approval will be > required to move a script from one stage to the next stage). Overseeing the > entire process is a producer whose approval will be required for the final > draft version of the script ie. the final approval on each script will > reside with the producer. In addition to this there are a number of other > personnel who will need to be notified on occasion, though not as regularly > as the above.
> Access to the material would be limited on a per-episode basis ie. each > writer and script editor have access only to the scripts which they are in > charge of. Some personnel will have global access ie. to all levels whilst > some instances will require access on a per node basis ie. the user has > access only to a specific node.
> The overall workflow consists of a series of cycles. Typically such a > cycle will consist of
> 1. the writer submits material > 2. the system sends out an e-mail to all personnel with access > to that script > 3. the script editor downloads the material and reviews it > 4. if the material requires no further work the editor approves > it - based on this action the system sends out an e-mail to all involved > 5. if the material requires further work the editor uploads > notes - based on this action the system sends out an e-mail to all involved
> Most of the users of the site will have very little computer experience > (other than script-writing and e-mail software) and as such the process > needs to be as simple as possible.
> I have a budget of US$2,000 available for this project.
> If you're interested and would like to know more please contact me > directly on graph...@olesturm.com.
|
