Ticket #1437 (closed planned_task: obsolete)

Opened 14 years ago

Last modified 13 years ago


Reported by: Astea Owned by: todor
Priority: 3 Milestone: M03_PRE3
Component: PROJECT_COMMUNITY Version: 2.0
Keywords: Cc:
Category: SCS Effort: 1
Importance: 60 Ticket_group:
Estimated Number of Hours: Add Hours to Ticket:
Billable?: Total Hours:
Analysis_owners: kyli Design_owners: todor
Imp._owners: todor Test_owners:
Analysis_reviewers: todor Changelog:
Design_reviewers: kyli Imp._reviewers: danvisel
Test_reviewers: Analysis_score: 3
Design_score: 3.5 Imp._score: 3
Test_score: 0


wiki page: SCS_PROJECT_BLOG_R2 - effort: 1d

Change History

comment:1 Changed 14 years ago by deyan

  • Category set to SCS
  • Design_score set to 0
  • Imp._score set to 0
  • Test_score set to 0
  • Analysis_score set to 0

Adding category and importance

comment:2 Changed 14 years ago by kyli

  • Owner changed from Astea to kyli
  • Status changed from new to s1a_analysis_started
  • Analysis_owners set to kyli

comment:3 Changed 14 years ago by kyli

  • Status changed from s1a_analysis_started to s1b_analysis_finished


comment:4 Changed 14 years ago by todor

  • Status changed from s1b_analysis_finished to s1c_analysis_ok
  • Analysis_reviewers set to todor
  • Analysis_score changed from 0 to 3

maybe the first release and the new teams should be mentioned, and not so much emphasize on the used technologies, because the technologies we're using are common for the whole project and there is information about them in the development overview. the emphasize should be on our current status and our progress during the last iteration.

comment:5 Changed 14 years ago by kyli

I was just using the structure, defined in the first revision of this task :)

comment:6 Changed 14 years ago by todor

  • Design_owners set to todor
  • Owner changed from kyli to todor
  • Status changed from s1c_analysis_ok to s2a_design_started


comment:7 Changed 14 years ago by todor

  • Status changed from s2a_design_started to s2b_design_finished

finished in only 1h, because the contents of the mail were used.

comment:8 Changed 14 years ago by kyli

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 0 to 3.5
  • Design_reviewers set to kyli

Is it necessary to send two different posts? The second is just 3 sentences long.. However, this is not fatal :) 3.5p

comment:9 Changed 14 years ago by todor

  • Status changed from s2c_design_ok to s3a_implementation_started
  • Imp._owners set to todor


comment:10 Changed 14 years ago by todor

  • Status changed from s3a_implementation_started to s3b_implementation_finished

there are two posts, because the one is progress report and the other gives information to the developer community about the videos

comment:11 Changed 14 years ago by danvisel

  • Status changed from s3b_implementation_finished to s3c_implementation_ok
  • Imp._score changed from 0 to 3
  • Imp._reviewers set to danvisel

Same thing that I said on the 1461:

I think this is basically pretty good. I do suggest that in the future we proofread it in English first - I'd be happy to go over things, I'm sure Nick wouldn't mind either - just to make sure that there aren't any big errors. You could flag me down on the Skype chat or send me an email - it would only take me five minutes to go over things, and I don't mind doing it.

I do think proofreading is important because this is how the world finds out about what we're doing & we don't want them to jump to the wrong conclusions because of typos.

The video post is a little bit confusing in English - Nick had me edit this to straighten out the sentences so that USC wouldn't be confused when they looked at the site.

comment:12 Changed 13 years ago by deyan

  • Status changed from s3c_implementation_ok to closed
  • Resolution set to obsolete

Batch update from file query-obsoleted.csv

Note: See TracTickets for help on using tickets.