Hi,

this is  known issue (which has been handled 13 minutes after it happened - just for the record ;-)). Unfortunately, so far, it is not going very well.

This affects: www.reactos.org, jira.reactos.org, dev.reactos.org, code.reactos.org, ns1.reactos.org (use NS2 for the moment).

We're sorry for the caused inconvenience.

With my best regards,
Pierre

On 13/10/2013 18:20, Александр wrote:

-- 
Pierre Schweitzer<pierre at reactos.org>
System Administrator
ReactOS Foundation