News items have been completely imported so importing of old
translations can resume. Again, to all translators, do NOT attempt to
edit the English version. You need to use the Translate tab to create
new pages.
Do NOT attempt to edit the existing English page when trying to create
a translated page. Select the Translation tab instead and create a new
translation. Attempting to save the English page as a different
language breaks the main English page, which results in breaking the
site for many other people.
Again, do not translate the news items yet. They were not imported
correctly and I need to dump all of them to do a new import. The
newsletter reimport has been completed and translators may begin
copying over the old translations. However, I ask that you preserve
the original publishing date and translator in the publishing info
section if possible.
We pulled the trigger a bit too quickly and translations for a lot of
content was not migrated over. First, translations are still there and
will be accessible once DNS propagation finally finishes, and I and
the other admins can get access to the old content to migrate them
over. Second, I'd like all of the current website language maintainers
and translators to get in touch with me. I need to grant you guys your
permissions again on the new site. Yes I could get a list of you guys
from the old site, but I want to know who is still around. Third,
several parts of the site were significantly changed, hence they will
need outright new translations. Apologies on how messy the transition
is, the abruptness caught not just you guys off guard.
Also note that we are severely parring down the number of languages we
intend to support. If you are currently a maintainer and do not see
your language currently on the list on the site, it does not mean we
dropped it or intend to drop it, it might mean I have just not gotten
around to adding your language to the list. However, some of you guys
I will respond to if you email me directly asking if you feel up to
translating everything, as we do not want an incomplete translation of
the site.
Hi,
we are currently facing some issues with mails delivery on
www.reactos.org website. This means that any mail cannot be delivered at
the moment. We are working on the issue.
The other sites (jira for instance) are not affected by this issue.
With my best regards,
--
Pierre Schweitzer<pierre(a)reactos.org>
System Administrator
ReactOS Foundation
At this point, do NOT attempt to translate the news items or
newsletters! I need to do a reimport of them this evening.
On Mon, Feb 18, 2013 at 8:58 AM, Javier Agustìn Fernàndez Arroyo
<elhoir(a)gmail.com> wrote:
> hello from spain,
>
> im here, and i would want to continue translating into Spanish
>
> However, please forgive me if cannot translate the whole website myself :)
>
> On Sun, Feb 17, 2013 at 9:55 PM, Zachary Gorden <drakekaizer666(a)gmail.com>
> wrote:
>>
>> We pulled the trigger a bit too quickly and translations for a lot of
>> content was not migrated over. First, translations are still there and
>> will be accessible once DNS propagation finally finishes, and I and
>> the other admins can get access to the old content to migrate them
>> over. Second, I'd like all of the current website language maintainers
>> and translators to get in touch with me. I need to grant you guys your
>> permissions again on the new site. Yes I could get a list of you guys
>> from the old site, but I want to know who is still around. Third,
>> several parts of the site were significantly changed, hence they will
>> need outright new translations. Apologies on how messy the transition
>> is, the abruptness caught not just you guys off guard.
>>
>> Also note that we are severely parring down the number of languages we
>> intend to support. If you are currently a maintainer and do not see
>> your language currently on the list on the site, it does not mean we
>> dropped it or intend to drop it, it might mean I have just not gotten
>> around to adding your language to the list. However, some of you guys
>> I will respond to if you email me directly asking if you feel up to
>> translating everything, as we do not want an incomplete translation of
>> the site.
>>
>> _______________________________________________
>> Ros-web mailing list
>> Ros-web(a)reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-web
>
>
>
> _______________________________________________
> Ros-web mailing list
> Ros-web(a)reactos.org
> http://www.reactos.org/mailman/listinfo/ros-web
Hello and Merry Christmas!
I know there are people from various technical universities around the
world subscribed to this list.
If you work there, please reply to me, as I'm looking for some
collaboration related to Operating Systems theory course and ReactOS.
Thank you,
Aleksey Bragin
P.S. Crossposting to both ros-dev and ros-general is a bad idea, but I'm
doing this to reach out all our subscribers. Sorry for inconvinience.
IMPORTANT REPORTthe webmaster of www.mensaj.in has contacted us by the Latin American ReactOS facebook fanpage and has written the next in a message:
Would you give me a Like? ... Free SMS www.mensaj.in are, if you like we could put a banner of ReactOS ...www.facebook.com/FundacionReactosMexico
I think this has to be approved first by the Foundation
Hi,
due to a hardware migration ongoing on one of our hypervisors, the
following services are currently down:
- Fisheye
- Jira
- DNS
- Experimental web sites
Those will be back as fast as possible. Regarding DNS report your
requests to our secondary DNS server on ns2.reactos.org
With my best regards,
--
Pierre Schweitzer <pierre(a)reactos.org>
Systems Administrator
ReactOS Foundation
Greetings!
I'm having some trouble with my eMail client, it seems the digest mode of the mailing
list confuses it somehow, so I'll quote this part manually, sorry for that. I switched
digest off now, hopefully the list will now deliver your eMails individually. :)
Copying my test file to ReactOS is not that problematic, I can just boot Knoppix in the
same VM, mount the ReactOS FAT32 filesystem, mount an external USB stick or something
and copy it over, reboot to ReactOS, problem solved.
But generally it would be nice to have stable FTP (or HTTP or SCP) transfers in ReactOS,
so I kept trying different programs etc. I thought that this is such a basic thing that
it just has to work! But yeah, BSOD every time. File size btw. is 668MBytes.
Now the second thing is, I would like to run x264 (a H.264/AVC video encoder linked
against the libav codec library for decoding) to transcode a video stream (that 668MB
file).
That part works for a few minutes and then crashes.
If it helps I can generate logs, maybe you could tell me what exactly I could do that
helps you.
About that VMware Player configuration I just noticed that I gave you wrong info. I was
indeed using the original setting set up by the 0.3.14 VMware image that I had
downloaded. The vmx/vmxf configuration files are attached to this eMail, here are some
settings beforehand:
* Mem: 512MB
* CPUs: 1
* HDD: 8GB
* USB: Present
* Display: Autodetect
* OS Type: XP Pro
I just tried it again a few times, and build #57337 boots into BSOD every single time
using those settings on VMware Player "4.0.1 build-528992". Host OS is CentOS 6.3 Linux
x86_64 in case it matters..
So if you require any specific tests or anything, just let me know. :) I might not be
able to test on weekends though, as the machine I am testing on might not be available
on weekends.
Thanks!
-Michael
> Hi Michael!
> Well...We can try several tricks to make it work :)
> If your main objective is to "copy" the File into ReactOS, then the best option is to
> "Mount" the Virtual HardDisk of your VirtualMachine. Mounting will let you place the
> file inside ReactOS without issues and from your host OS.Then when booting ReactOS you
> will see the file inside "magically".
>
> If your main objective is to test the MM and overall ReactOS behavior in Vmware then
> thanks a lot, because your help could be really really helpful. :)
> I've to say that lately ReactOS has improved a lot its stability under Vbox but seems
> it didn't do the same under Vmware as your tests shows.
> It would be really nice if you can share which is your Virtual Machine
> configuration(Ram, HDD, etc) so maybe we can try to replicate the issue to find
> something useful in the logs.
> Or maybe you can create useful Logs for us :)
> I have tried Filezilla under VBOX and seems to fail.Reason under this line:
> (Trace cut out)
>
> If this didnt happen in 0.3.14 then we are in front of a regression. Nice catch!
> We can try to find the guilty commit via Binary Search.
> Thanks a lot!
--
Michael Lackner
Lehrstuhl für Informationstechnologie (CiT)
Montanuniversität Leoben
Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at
Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech
