[[BackLinksMenu]]

[[TicketQuery(summary=PLATFORM_STANDARDS_REPOSITORY_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|)]]

= Analysis =
== Overview ==
Improves [wiki:PLATFORM_STANDARDS_ANALYSIS]
== Task requirements ==
 * Discuss comments in the comments section of the document.
 * Apply approved improvements.
 * See implementation idea for more detailed information

== Task result ==
Updated [wiki:PLATFORM_STANDARDS_REPOSITORY]
== Implementation idea ==
Implement this task after the [wiki:SCS_WIKI_SETUP_R3]. Use following code for the internal information. Protected Macto should be installed and enabled during SCS_WIKI_SETUP. Example code for hiding internal information:
{{{
{{{                                                
#!protected                                        
#:This is what an unauthorized user sees (optional)
This is what an authorized user sees               
}}}
}}}
Comments of the document (until now) with some feedback
{{{
Since most of the release team is remote, it is hardly possible to have your task reviewed without a commit. --boyan@2009-01-12
}}}
Implementing a task includes commiting of it without breaking another things (or modifying another code). This seems to solve that issue.

{{{
Not explained how the registered users can download the "manage" directory. For example, with tortoiseSVN you have to use the repo-browser, since it does not ask you for username/password. --kyli
}}}
Explain how tho download the "manage" directory. In windows - using repo browser. In linux, username and password can be added as command line parameters I guess.

{{{
I think that it should be noted that one should not branch/tag the whole repo.  --pap@2009-01-15
}}}
Note what should be branched/tagged.

{{{
I think that the "Deploying a project in a Repository" section is not correctly named and the first bullet should be deleted. I think it was broken in some of the previous docs rearangements as deploying into repository and checking out of it are two different things.  --pap@2009-01-15
}}}
Correct listed things.

{{{
You should add a section describing how to checkout the manage folder under Linux. I did this via Eclipse but I don't think it is the best way. I did so because my svn client refused to use the creditentials I gave it.  --pap@2009-01-15
}}}
Related to a previous comment. Research how to checkout and add this information.

{{{
There is no such thing as the Sophie-JR project anymore or at least they don't have place in this document.  --pap@2009-01-15
}}}
Remove the Sophie-JR references.

{{{
Probably internal information as manage directory should not be noted here - it is internal information, not needed by the community. This can be placed somewhere else, not exactly sure where --deyan@2009-02-03
}}}
This will be solved if the ProtectedMacro is used (should be installed in [wiki:SCS_WIKI_SETUP_R3]

== Related ==
[wiki:PLATFORM_STANDARDS_REPOSITORY_R1][[BR]]
[wiki:PLATFORM_STANDARDS_REPOSITORY_R0][[BR]]
[wiki:SCS_WIKI_SETUP_R3]

== How to demo ==
Show modified [wiki:PLATFORM_STANDARDS_REPOSITORY] logged and not logged in.
= Design =
^(Describe your design here.)^

= Implementation =
^(Describe and link the implementation results here (from the wiki or the repository).)^

= Testing =
^(Place the testing results here.)^

= Comments =
^(Write comments for this or later revisions here.)