wiki:SCS_WIKI_SETUP_R2
Last modified 16 years ago Last modified on 02/07/09 15:43:14

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_WIKI_SETUP_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

Wiki setup solves unsolved or unscheduled wiki issues. In this revision the videos that contain design concepts or meetings should be uploaded to a public location. These videos contain very important concepts of the project such as plugin structure, libraries used, etc. These videos are useful not only for the people trying to get into the project, but also for the team members as the project is huge. Some of the videos contain common code mistakes and current project issues.

Task requirements

  • Choose an appropriate appliance to store videos
  • Create a webpage containing discussion and meeting videos (this may be a wiki page)
    • For each item define what information about the video it will contain.
  • Add the webpage to the backup script (if not a wiki page)
    • Webpage should be backed up but the videofiles require a huge amount of disc space.
  • Suggest and discuss where to backup the videos. It might be a hard disk of another computer. Document what is decided.
  • Create an overview for the videos page - few sentences are enough.
  • Link the webpage in main page or developers home page.
  • Announce it using blog and maillist.

Task result

A webpage with downloadable video files.

Implementation idea

Useful information might be

  • Discussion topic
  • tags
  • date of the discussion
  • Comments section might come handy

Thumbnails may look good but not very useful. The actual upload of the videos should be done in SCS_WIKI_MAINTENANCE_R3, so you may decide to implement these tasks at once.

SCS_WIKI_MAINTENANCE_R3

How to demo

Present the page containing video files.

Design

  • After the discussion took place we've came up with some decisions:
  • Back up copy of each video will be created and stored on DVD disks
    • when we gather enough videos to fill one DVD - back up image should be created and so on
    • the back up DVDs will be stored in the office
  • The structure of the wiki page linking all videos:
    = Discussions =
     * '''[http://asteasolutions.net/videos/2009-01-27%20General%20Discussion.mpg (2009-01-27) General Discussion]'''
    In this video are explained our goals, what we strive to achieve, our challenges and how we shall proceed in order to create a product with high quality. It is recommended everyone to be familiar with this discussion.
    
     * [http://asteasolutions.net/videos/2009-01-20%20Design%20Discussion.mpg (2009-01-20) Design Discussion]
    {{{
    Topics:
    
    = pro_lib = - designed to help people! If they are not helping, either something should be fixed or people do not understand how to use it.
     * attibute - self responsible.
     * do not care about initializing order.
     * good practices:
      * defaulty constructors.
      * avoid final properties.
      * push updates - instead of updating things manually, provide these things the ability to auto-update.
      * avoid trying to use unconventionally the pro_lib since this is error prone.
     * Property improper use cases:
      * accessing an AutoProperty WILL NOT invoke its compute() method!
      * resource properties:
       * create method should depend on NOTHING => it is invoked once and will not update things.
       * setup methods are designed to keep things synchronized for people. @Setup may be put to split setup things in different methods, so that they are updated in groups.
       * destroy methods are not working.
     * List properties.
    
    = core_modularity =
     * extensions are now sortable by comparator.
    
    = base_visual =
     == layout ==
     == menus ==
     * this is a new module to split the layout and menus from the main.view things.
    
    = base_skins =
     * provides things to simplify things that are registered for a single skin => currently a map with (id, value) entries.
    
    = global things  =
     * few people have a global vision about things.
      * people should get a better overall idea.
     * supercool model.
       * not only implement a great library but find a task to actually use it and also do that task.
        * this will improve the library.
        * things that are error prone will appear.
     * the "not my task/class" problem (people tend to do only things that are tracked and planned):
      * the code is owned by everyone!
      * fix things that need to fixed in order to implement you things, otherwise the next revision of the task will fail.
      * if the things are complicated to be fixed, ask the others, make discussions about it.
    }}}
    
     * AsteaCon 2008
      * [http://asteasolutions.net/~parlev/AsteaCon2008/2008-11-19/ 2008-11-19 1st Day Discussions]
      * [http://asteasolutions.net/~parlev/AsteaCon2008/2008-11-20/ 2008-11-20 2nd Day Discussions]
      * [http://asteasolutions.net/~parlev/AsteaCon2008/2008-11-21/ 2008-11-21 3rd Day Discussions]  
    {{{
    During the three days of discussions at Sheraton Hotel between Astea Team and some of our oversea partners detailed information about all aspects of the project was given.
    }}}
    
     * Branding discussions with Robert Abbott from ''Shift Global''
      * [http://asteasolutions.net/videos/2009-01-30%20Milo%27s%20Project%20Overview.mpg (2009-01-30) Milo's Project Overview]
    {{{
    Project overview of Sophie 2.0 by the team leader which aims to introduce the product to Robert Abbott from Shift Global.
    }}}
      * [http://asteasolutions.net/videos/2009-01-30%20Robert%27s%20Branding%20Discussion.mpg (2009-01-30) Robert's Branding Discussion]
    {{{
    Discussion between Robert Abbott and Astea Team on which they discussed Sophie 2.0 logo drafts and basic visual wireframes of the future product.
    }}}
      * [http://asteasolutions.net/videos/2009-01-31%20Robert%27s%20UI%20Discussion.mpg (2009-01-31) Robert's UI DIscussions]
    {{{
    Discussion about Sophie 2.0 user interface and some internal aspects of the project.
    }}}
      * [http://asteasolutions.net/videos/2009-01-31%20Sophie2%20Website%20Discussion.mpg (2009-01-31) Sophie2 Website Discussion]
    {{{
    Discussion between Astea team and Robert Abbott about the vision and functionality of Sophie 2 website.
    }}}
    
     * [http://asteasolutions.net/videos/2009-02-03%20Milo%27s%20Refactoring%20Discussion.mpg (2009-02-03) Milo's Refactoring Discussion]
    {{{
    Milo gives details about the modules that he refactored, and explains his vision about improvement of the code quality.
    }}}
    ----
    = Weekly Meetings =
    ITERATION_03
     * [http://asteasolutions.net/~boyan/sprint03_week1/ 1st Weekly Meeting]
     * [http://asteasolutions.net/~parlev/sprint03_week2/ 2nd Weekly Meeting]
     * [http://asteasolutions.net/~boyan/sprint03_week3/ 3rd Weekly Meeting]
    
    ITERATION_04
     * [http://asteasolutions.net/videos/2009-01-27%20Weekly%20Meeting.mpg (2009-01-27) 3rd Weekly Meeting]
     * [http://asteasolutions.net/videos/2009-02-03%20Weekly%20Meeting.mpg (2009-02-03) 4th Weekly Meeting]
    
  • Create post and mail for the maillist with the link for the videos:
    As announced earlier a wiki page with links to useful videos is available at http://sophie2.org/trac/wiki/Videos .
    We hope that you will find answers to most your questions about the project there.
    

Implementation

  • The result of this task is the page Videos
    • The comments were fixed only the log of the discussion is left in "frame" because of the wiki formating
  • Back up of the videos was made
  • There's no need to add them in the backup script because they're not changing we can only add new ones on new DVDs.
  • Post and mail were sent to notify about the new page.

Testing

Comments

(Write comments for this or later revisions here.)