x
Loading . . .
Logistics Office Report, May 2008
":)
Well, it's been an up and down month for me. I'm not sure much has happened on the macroscopic level, but with the inclusion of a few more members of the office . . . well, next month should be interesting. :)
David Vaughan
For me personally, I went out of town on leave, which, as is customary for me . . . means that I got a HEAP of Logistics works done. Mostly to do with the locations project, which I'll get into below. Oh yeah, and I also had a mini-burn out, which was not fun for anyone involved.
Things done since the last report:
> Mapped out all but the most recent historical missions in the major/minor scheme of battles/engagements (in the context of the mapping projects, we need names for all historical locations; before we can put names to places, we need to sort the important locations from the trivial ones . . . this has now been done, which means we can assign GOOD- and OKAY-class names to the locations and get the mapping project moving forward)
> Worked out GDF105 and SSF111 results to determine GDF106 and SSF112 narrative details
> Supplied ship names for SSF112 missions (I was very late with this)
> Wrote SSF112 narrative
> Co-wrote GDF106 narrative with Max and Dave; edited co-writers Max and Dave's scenes
> Provided Seeks and Max with news articles to work on
> Assigned projects to officers requiring them, and acquired some more personnel (mostly through their voluntary efforts, more than my recruitment skills)
> Ship names project --- this project was finished, but I had more contributions . . . I just have to process them, and thank the contributor (Gavin Kravis)
> Mapped out a system for making the day to day running of the Logistics Office less Vaughan-dependent. Expect more about this next month.
Michael Raven
As is the norm from now on, Raven is ever busy with work and uni, so his Logistics work will primarily be behind the scenes, generally only in an advisory capacity. However, he has pledged to finish the first Unified ITOD of the RS with another exceptional narrative to bookend the tour, as he wrote the excellent Malicious Intentions which began the tradition of decent-length, high-quality narratives accompanying EVERY mission launch of the Unified ITOD. If you've been following the GDF and SSF narratives, except plot points to be tied up and/or together in the next narrative, which will link both campaigns.
Kaz Falcion
Kaz is now the FC, so I don't expect much from him since he's already busy. That said, he has expressed interest in working on more news articles (if memory serves), so I'll hopefully have more to report next month (or if not next month, then definitely the one after --- news articles for RS201 won't be written until the start of July, I expect)
Gavin Starseeker
Apart from his mission building duties in TacOps, as well as co-ordinating the development of new missions, he has done the following:
> Created the 44:4, 44:5 and 44:6 conflict maps. You can see his efforts on the RS wiki; article Conflict Maps.
> Created graphics for TacOps / Logistics Medals, which are still in development
> Co-ordinated development and release of SSF112
> Co-ordinated development and release of GDF106
> Agreed to write a Mediator News article
David Pasiechnyk
In addition to his extensive mission building duties, Heavy has completed extensive work on his XvT mission building training programme, and worked with Carlos on updating and developing the RS BoP patch. Beyond that, he has not done any logistics duties this month (to my knowledge), because he's done a hell of a lot of non-logistics work. Heavy, if you want any Logistics work, just let me know. If not, I understand --- you're already doing heaps. :)
Adam Mieter
Adam has proven himself consistently to be a great asset to the office in the realm of wiki work. But as he is looking for additional duties, I have found some minor management/co-ordination tasks to keep him busy for the coming month. If that goes well, I have more related duties that I'm happy to hand over, if Adam is willing. But that's getting ahead of myself, for now, here are the duties I have assigned to Adam:
> Remind me to prepare the "in between tours" narrative outline two week before VSG112 ends (i.e. around the Twenty-First of June)
> Update and maintain the Narratives of the Unified ITOD article on the RS wiki (feel free to contact me for any information you might need)
> Maintain the TacOps discussion backup forum (contact me when you're ready to begin)
Mathow Bizegar
Mathow had agreed to work on a warship involvement investigation project for R2F campaigns, but I have not heard from him for about three months. Therefore, I am given no choice but to remove him from the group. Mathow: if you're around, and want to resume work in the Logistics Office, let me know.
Kane Redron
Kane successfully completed the warship investigation project he signed up for. However, due to extraordinary circumstances, Kane has been removed from the Logistics Office. Thank you very much for your efforts in the office before this point, Kane, they are greatly appreciated.
Michael Dreadman
Michael agreed to help out with the RgF warship involvement investigation project, along with Kane. He succeeded at this, but the project was cancelled, and I have not been able to contact Michael since then. So Michael: if you want to remain in the Logistics Office, please contact me and we'll find something for you to work on. :)
Himm El-Syna
Himm signed up for the IBG craft verification project and the IBG warship involvement investigation project. But he is far too busy working on XWA missions as far as I can tell. Himm, if you think you'll have time in the next two months to work on logistics projects let me know, otherwise I'll take you off the roster until you have enough of a break from XWA building to play through the old IBG missions. I know RS201A is going to slam you something serious (and yeah, I need to get off my ass and get that outline to you!). Let me know whether you expect to have any logistics time anytime soon. I will understand completely if you don't, just let me know either way, please. :)
Max Cal
One of our new writers. I don't know if Max intends to sign on for the long haul, or just help out when needed, but I realised that he deserved some recognition for his efforts in the GDF106 narrative, which he co-wrote. He has also agreed to write one of the Mediator News articles. Max: let me know if you want this to be a permanent position, or whether you just want to help out on occasion. Things Max has done:
> Co-wrote the GDF106 narrative with Dave and I
> Agreed to write a news article
Teu Veld
The Logistics Office's most recent acquisition, Teu has signed up to work on management/co-ordination related tasks. For the first month or so I have assigned her relatively simple tasks, with higher-level duties available after that point should she not be scared off my me before then. Here are Teu's duties for the coming month and a bit:
> Remind me to prepare the RS201 narrative outline one week before VSG112 ends (i.e. around the Twenty-Eighth of June)
> Remind me to process the results of GDF106 and SSF112 when VSG112 ends (i.e. around the Fifth of July)
> Track down potential writers for the RS-wide narratives and in-universe news service
Below is a list of things that I was expecting members of the office would do in May (with notes detailing outcomes):
David Vaughan ->
1. Write and distribute outline for RS201 -- not done yet, in fact I cannot emphasise how much of a failure I am for not having this out by now. The damned thing was due about THREE CHAPTERS ago. I really suck.
2. Determine fictional outcomes for SSF111 from first-run reports -- done!
3. Determined fictional outcomes for GDF105 from first-run reports -- done!
4. Provide fiction for SSF112 -- done!
5. Provide fiction for GDF106 -- done!
6. Write or co-write the SSF112 narrative -- done!
7. Co-write the GDF106 narrative -- done!
8. Write or organise writing effort of Mediator articles for SSF112 -- done!, but the article writing process is still ongoing
9. Document all Logistics members' activities -- done!, but almost a week late. Very poor.
10. Find project for Adam to work on -- done!, took me a long time, though
11. Find project for Heavy to work on -- not done yet, I couldn't think of anything
12. Delegate more (find more writers for future narratives and news articles) -- done!, I have projects in place to make the Logistics Office less Vaughan-dependent which are currently in motion; have found two writers so far, but hopefully Teu will do better
13. Write and distribute outline for RS202 -- not done yet, again, fail --- I suck
14. Determine historical battles/skirmishes for the location names project -- done!, mostly . . . still have some of the more recent missions (current campaigns) to finalise yet
15. Write and distribute outline for RS203 -- not done yet, again, fail --- I suck
16. Copy the remaining timeline data to the wiki, and prune inappropriate information from all pages (check to see how much of this I have already done, and then continue on from that) -- not done yet, haven't got time until I delegate more, which I am working on
17. Keep updating the craft database from members' investigations of historical missions -- not done yet, haven't got time until I delegate more, which I am working on
18. Push the establishment of TacOps medals -- not done yet, however Seeks has been working on graphics for the medals
19. Possibly document RID missions of RID Tour 1 -- not done yet, not sure if I will even do this myself, or if I'll delegate . . . wait . . . did someone else do this, and I've just forgotten? If you're reading this, speak up!
Michael Raven ->
1. Provide logistics advice as usual -- done!
Kaz Falcion ->
1. Push development of TacOps medals -- unsure, I think he has, but I can't be sure
Gavin Starseeker ->
1. Co-ordinate the release of SSF112 in TacOps -- done!
2. Co-ordinate the release of GDF106 in TacOps -- done!
3. Co-ordinate the development of RS201 in TacOps (once I release the outline) -- not done yet, my fault, not his, since I haven't released the damned outline yet . . .
4. Write news articles (once I provide outlines for them) -- not done yet, I only just provided him with the outline
David Pasiechnyk ->
1. Let me know if you want to work on any more projects (maybe find some more mission builders? ;)) -- not done yet, I don't think . . . Heavy, if you have communicated to me projects you want to work on, please correct me . . . oh, and you have found at least one mission builder; that's more than I have!
Adam Mieter ->
1. Let me know if you want more projects . . . I will try and think of wiki projects for you to work on :) -- done!, I came up with projects for him to work on
Mathow Bizegar ->
1. Report your current and future status. -- not done yet, and at this stage I'm not expecting him to; removed from the Logistics Office until he contacts me
Kane Redron ->
1. Await orders until further notice. -- done!, removed from the Logistics Office
Alexander Vandross ->
1. Die in a fire, you fucking softcock loser. Serve as an example to everyone else of a dickless wanker with no balls. For anyone who thinks I'm being unduly harsh, consider this: if he had told me that he was struggling, I could have organised everything to accommodate his situation. Instead he just pussed out and played World of WarCraft and quit without notifying me or leaving any evidence of the work he lied about doing, which meant that Heavy had to break his back creating a mission from scratch at the last minute. What a fucking pansy. -- unsure, not sure if this soft-cock pansy did die in a fire or not, but I hope he did. Note to anyone else: I'm not likely to rip you apart if you can't get your work done, only if you keep saying you can, while not doing it, and then quitting without letting me know. Sure-fire way to make me go on a rampage, for future reference. If you can't get something done, let me know as soon as possible I can plan around it. :)
Michael Dreadman ->
1. Let me know if you want any more projects to work on, and I'll see what we can find you. :) -- not done yet, but please contact me ASAP if you still want to work on projects
Himm El-Syna ->
1. Get VSG112A done -- done!, fucking legend!
2. Work on RS201A (once the above is done, and I get the outline out) -- not done yet, my fault, because I'm slack and suck and haven't got the damned outline to him yet
3. (Optional) Document warship involvement in historical IBG campaigns, and confirming craft database notes -- not done yet, not really expecting it to be done until RS201 is out of the road at the very least
So here's what I'm expecting members of the office to do in June:
David Vaughan ->
1. Write and distribute outline for RS201
2. Prepare the "between tours" narrative outline
3. Write and distribute outline for RS202
4. Document all Logistics members' activities
5. Write and distribute outline for RS203
6. Determine historical battles/skirmishes for the last few missions in the location names project
7. Write and distribute outline for RS204
8. Copy the remaining timeline data to the wiki, and prune inappropriate information from all pages (check to see how much of this I have already done, and then continue on from that)
9. Keep updating the craft database from members' investigations of historical missions
10. Push the establishment of TacOps medals
11. Possibly document RID missions of RID Tour 1
Michael Raven ->
1. Provide logistics advice as usual
Kaz Falcion ->
1. Push development of TacOps medals
Gavin Starseeker ->
1. Co-ordinate the development of RS201 in TacOps (once I release the outline)
2. Write news article
David Pasiechnyk ->
1. Let me know if you want to work on any more projects or not
Adam Mieter ->
1. Contact me with confirmation of orders, and questions regarding the second and third duties
2. Remind me to prepare the "in between tours" narrative outline on the Twenty-First of June
3. Update and maintain the Narratives of the Unified ITOD article on the RS wiki
4. Maintain the TacOps discussion backup forum
Michael Dreadman ->
1. Let me know if you want any more projects to work on or not
Himm El-Syna ->
1. Work on RS201A (once I get the outline out)
2. (Optional) Document warship involvement in historical IBG campaigns, and confirming craft database notes
Max Cal ->
1. Write the news article you agreed to
Teu Veld ->
1. Contact me to confirm acknowledgement of orders
2. Remind me to prepare the RS201 narrative outline on the Twenty-Eighth of June
3. Remind me to process the results of GDF106 and SSF112 on the Fifth of July
4. Track down potential writers for the RS-wide narratives and in-universe news service
As always, if anyone has any queries or concerns, please contact me. I will reply as soon as I can.
":)
Cdre. David Vaughan
Logistics Officer
Well, it's been an up and down month for me. I'm not sure much has happened on the macroscopic level, but with the inclusion of a few more members of the office . . . well, next month should be interesting. :)
David Vaughan
For me personally, I went out of town on leave, which, as is customary for me . . . means that I got a HEAP of Logistics works done. Mostly to do with the locations project, which I'll get into below. Oh yeah, and I also had a mini-burn out, which was not fun for anyone involved.
Things done since the last report:
> Mapped out all but the most recent historical missions in the major/minor scheme of battles/engagements (in the context of the mapping projects, we need names for all historical locations; before we can put names to places, we need to sort the important locations from the trivial ones . . . this has now been done, which means we can assign GOOD- and OKAY-class names to the locations and get the mapping project moving forward)
> Worked out GDF105 and SSF111 results to determine GDF106 and SSF112 narrative details
> Supplied ship names for SSF112 missions (I was very late with this)
> Wrote SSF112 narrative
> Co-wrote GDF106 narrative with Max and Dave; edited co-writers Max and Dave's scenes
> Provided Seeks and Max with news articles to work on
> Assigned projects to officers requiring them, and acquired some more personnel (mostly through their voluntary efforts, more than my recruitment skills)
> Ship names project --- this project was finished, but I had more contributions . . . I just have to process them, and thank the contributor (Gavin Kravis)
> Mapped out a system for making the day to day running of the Logistics Office less Vaughan-dependent. Expect more about this next month.
Michael Raven
As is the norm from now on, Raven is ever busy with work and uni, so his Logistics work will primarily be behind the scenes, generally only in an advisory capacity. However, he has pledged to finish the first Unified ITOD of the RS with another exceptional narrative to bookend the tour, as he wrote the excellent Malicious Intentions which began the tradition of decent-length, high-quality narratives accompanying EVERY mission launch of the Unified ITOD. If you've been following the GDF and SSF narratives, except plot points to be tied up and/or together in the next narrative, which will link both campaigns.
Kaz Falcion
Kaz is now the FC, so I don't expect much from him since he's already busy. That said, he has expressed interest in working on more news articles (if memory serves), so I'll hopefully have more to report next month (or if not next month, then definitely the one after --- news articles for RS201 won't be written until the start of July, I expect)
Gavin Starseeker
Apart from his mission building duties in TacOps, as well as co-ordinating the development of new missions, he has done the following:
> Created the 44:4, 44:5 and 44:6 conflict maps. You can see his efforts on the RS wiki; article Conflict Maps.
> Created graphics for TacOps / Logistics Medals, which are still in development
> Co-ordinated development and release of SSF112
> Co-ordinated development and release of GDF106
> Agreed to write a Mediator News article
David Pasiechnyk
In addition to his extensive mission building duties, Heavy has completed extensive work on his XvT mission building training programme, and worked with Carlos on updating and developing the RS BoP patch. Beyond that, he has not done any logistics duties this month (to my knowledge), because he's done a hell of a lot of non-logistics work. Heavy, if you want any Logistics work, just let me know. If not, I understand --- you're already doing heaps. :)
Adam Mieter
Adam has proven himself consistently to be a great asset to the office in the realm of wiki work. But as he is looking for additional duties, I have found some minor management/co-ordination tasks to keep him busy for the coming month. If that goes well, I have more related duties that I'm happy to hand over, if Adam is willing. But that's getting ahead of myself, for now, here are the duties I have assigned to Adam:
> Remind me to prepare the "in between tours" narrative outline two week before VSG112 ends (i.e. around the Twenty-First of June)
> Update and maintain the Narratives of the Unified ITOD article on the RS wiki (feel free to contact me for any information you might need)
> Maintain the TacOps discussion backup forum (contact me when you're ready to begin)
Mathow Bizegar
Mathow had agreed to work on a warship involvement investigation project for R2F campaigns, but I have not heard from him for about three months. Therefore, I am given no choice but to remove him from the group. Mathow: if you're around, and want to resume work in the Logistics Office, let me know.
Kane Redron
Kane successfully completed the warship investigation project he signed up for. However, due to extraordinary circumstances, Kane has been removed from the Logistics Office. Thank you very much for your efforts in the office before this point, Kane, they are greatly appreciated.
Michael Dreadman
Michael agreed to help out with the RgF warship involvement investigation project, along with Kane. He succeeded at this, but the project was cancelled, and I have not been able to contact Michael since then. So Michael: if you want to remain in the Logistics Office, please contact me and we'll find something for you to work on. :)
Himm El-Syna
Himm signed up for the IBG craft verification project and the IBG warship involvement investigation project. But he is far too busy working on XWA missions as far as I can tell. Himm, if you think you'll have time in the next two months to work on logistics projects let me know, otherwise I'll take you off the roster until you have enough of a break from XWA building to play through the old IBG missions. I know RS201A is going to slam you something serious (and yeah, I need to get off my ass and get that outline to you!). Let me know whether you expect to have any logistics time anytime soon. I will understand completely if you don't, just let me know either way, please. :)
Max Cal
One of our new writers. I don't know if Max intends to sign on for the long haul, or just help out when needed, but I realised that he deserved some recognition for his efforts in the GDF106 narrative, which he co-wrote. He has also agreed to write one of the Mediator News articles. Max: let me know if you want this to be a permanent position, or whether you just want to help out on occasion. Things Max has done:
> Co-wrote the GDF106 narrative with Dave and I
> Agreed to write a news article
Teu Veld
The Logistics Office's most recent acquisition, Teu has signed up to work on management/co-ordination related tasks. For the first month or so I have assigned her relatively simple tasks, with higher-level duties available after that point should she not be scared off my me before then. Here are Teu's duties for the coming month and a bit:
> Remind me to prepare the RS201 narrative outline one week before VSG112 ends (i.e. around the Twenty-Eighth of June)
> Remind me to process the results of GDF106 and SSF112 when VSG112 ends (i.e. around the Fifth of July)
> Track down potential writers for the RS-wide narratives and in-universe news service
Below is a list of things that I was expecting members of the office would do in May (with notes detailing outcomes):
David Vaughan ->
1. Write and distribute outline for RS201 -- not done yet, in fact I cannot emphasise how much of a failure I am for not having this out by now. The damned thing was due about THREE CHAPTERS ago. I really suck.
2. Determine fictional outcomes for SSF111 from first-run reports -- done!
3. Determined fictional outcomes for GDF105 from first-run reports -- done!
4. Provide fiction for SSF112 -- done!
5. Provide fiction for GDF106 -- done!
6. Write or co-write the SSF112 narrative -- done!
7. Co-write the GDF106 narrative -- done!
8. Write or organise writing effort of Mediator articles for SSF112 -- done!, but the article writing process is still ongoing
9. Document all Logistics members' activities -- done!, but almost a week late. Very poor.
10. Find project for Adam to work on -- done!, took me a long time, though
11. Find project for Heavy to work on -- not done yet, I couldn't think of anything
12. Delegate more (find more writers for future narratives and news articles) -- done!, I have projects in place to make the Logistics Office less Vaughan-dependent which are currently in motion; have found two writers so far, but hopefully Teu will do better
13. Write and distribute outline for RS202 -- not done yet, again, fail --- I suck
14. Determine historical battles/skirmishes for the location names project -- done!, mostly . . . still have some of the more recent missions (current campaigns) to finalise yet
15. Write and distribute outline for RS203 -- not done yet, again, fail --- I suck
16. Copy the remaining timeline data to the wiki, and prune inappropriate information from all pages (check to see how much of this I have already done, and then continue on from that) -- not done yet, haven't got time until I delegate more, which I am working on
17. Keep updating the craft database from members' investigations of historical missions -- not done yet, haven't got time until I delegate more, which I am working on
18. Push the establishment of TacOps medals -- not done yet, however Seeks has been working on graphics for the medals
19. Possibly document RID missions of RID Tour 1 -- not done yet, not sure if I will even do this myself, or if I'll delegate . . . wait . . . did someone else do this, and I've just forgotten? If you're reading this, speak up!
Michael Raven ->
1. Provide logistics advice as usual -- done!
Kaz Falcion ->
1. Push development of TacOps medals -- unsure, I think he has, but I can't be sure
Gavin Starseeker ->
1. Co-ordinate the release of SSF112 in TacOps -- done!
2. Co-ordinate the release of GDF106 in TacOps -- done!
3. Co-ordinate the development of RS201 in TacOps (once I release the outline) -- not done yet, my fault, not his, since I haven't released the damned outline yet . . .
4. Write news articles (once I provide outlines for them) -- not done yet, I only just provided him with the outline
David Pasiechnyk ->
1. Let me know if you want to work on any more projects (maybe find some more mission builders? ;)) -- not done yet, I don't think . . . Heavy, if you have communicated to me projects you want to work on, please correct me . . . oh, and you have found at least one mission builder; that's more than I have!
Adam Mieter ->
1. Let me know if you want more projects . . . I will try and think of wiki projects for you to work on :) -- done!, I came up with projects for him to work on
Mathow Bizegar ->
1. Report your current and future status. -- not done yet, and at this stage I'm not expecting him to; removed from the Logistics Office until he contacts me
Kane Redron ->
1. Await orders until further notice. -- done!, removed from the Logistics Office
Alexander Vandross ->
1. Die in a fire, you fucking softcock loser. Serve as an example to everyone else of a dickless wanker with no balls. For anyone who thinks I'm being unduly harsh, consider this: if he had told me that he was struggling, I could have organised everything to accommodate his situation. Instead he just pussed out and played World of WarCraft and quit without notifying me or leaving any evidence of the work he lied about doing, which meant that Heavy had to break his back creating a mission from scratch at the last minute. What a fucking pansy. -- unsure, not sure if this soft-cock pansy did die in a fire or not, but I hope he did. Note to anyone else: I'm not likely to rip you apart if you can't get your work done, only if you keep saying you can, while not doing it, and then quitting without letting me know. Sure-fire way to make me go on a rampage, for future reference. If you can't get something done, let me know as soon as possible I can plan around it. :)
Michael Dreadman ->
1. Let me know if you want any more projects to work on, and I'll see what we can find you. :) -- not done yet, but please contact me ASAP if you still want to work on projects
Himm El-Syna ->
1. Get VSG112A done -- done!, fucking legend!
2. Work on RS201A (once the above is done, and I get the outline out) -- not done yet, my fault, because I'm slack and suck and haven't got the damned outline to him yet
3. (Optional) Document warship involvement in historical IBG campaigns, and confirming craft database notes -- not done yet, not really expecting it to be done until RS201 is out of the road at the very least
So here's what I'm expecting members of the office to do in June:
David Vaughan ->
1. Write and distribute outline for RS201
2. Prepare the "between tours" narrative outline
3. Write and distribute outline for RS202
4. Document all Logistics members' activities
5. Write and distribute outline for RS203
6. Determine historical battles/skirmishes for the last few missions in the location names project
7. Write and distribute outline for RS204
8. Copy the remaining timeline data to the wiki, and prune inappropriate information from all pages (check to see how much of this I have already done, and then continue on from that)
9. Keep updating the craft database from members' investigations of historical missions
10. Push the establishment of TacOps medals
11. Possibly document RID missions of RID Tour 1
Michael Raven ->
1. Provide logistics advice as usual
Kaz Falcion ->
1. Push development of TacOps medals
Gavin Starseeker ->
1. Co-ordinate the development of RS201 in TacOps (once I release the outline)
2. Write news article
David Pasiechnyk ->
1. Let me know if you want to work on any more projects or not
Adam Mieter ->
1. Contact me with confirmation of orders, and questions regarding the second and third duties
2. Remind me to prepare the "in between tours" narrative outline on the Twenty-First of June
3. Update and maintain the Narratives of the Unified ITOD article on the RS wiki
4. Maintain the TacOps discussion backup forum
Michael Dreadman ->
1. Let me know if you want any more projects to work on or not
Himm El-Syna ->
1. Work on RS201A (once I get the outline out)
2. (Optional) Document warship involvement in historical IBG campaigns, and confirming craft database notes
Max Cal ->
1. Write the news article you agreed to
Teu Veld ->
1. Contact me to confirm acknowledgement of orders
2. Remind me to prepare the RS201 narrative outline on the Twenty-Eighth of June
3. Remind me to process the results of GDF106 and SSF112 on the Fifth of July
4. Track down potential writers for the RS-wide narratives and in-universe news service
As always, if anyone has any queries or concerns, please contact me. I will reply as soon as I can.
":)
Cdre. David Vaughan
Logistics Officer