here is a letter from JvA.
As most people know we have talk to move svn to another place.
Dear ReactOS Crew,
I spoke today with Lysators highest administrator Kalle, and he told me
that there should be no problem what so ever for Lysator to host you.
However, in order for us to host you we need a letter from you where you
ask us to host you, and specify what you want to use the server for.
This letter is needed for bureaucratic reasons.
The root group needs to officially grant you the right to be hosted in
our server hall, and marked as a Lysator-project. What the root group
wants to know is what you intend to use the server for and what ports
you need open in the firewall. The security rules in Lysator strictly
says that only Lysator members are allowed to have administrator/root
accounts on the servers in the server hall. The person who would
administrate your server would be me. People outside Lysator, like the
ReactOS developers, are however allowed to have normal SSH-accounts.
Bandwidth is not a problem. Kalle told me that Lysator has been granted
a secondary gbit-connection if the current one isn't enough. By the way,
the server hall has UPS:es to make sure the servers are online even if
there are would be electrical difficulties.
When you have had a meeting and decided what you want hosted in the
Lysator server hall, send me a letter where you ask us to host you and
I'll give it to Kalle. When you officially have been granted to be
hosted by us, you need to supply us with a server, 1U or 2U. If you
want, I could build it for you here in Linköping if you collect money
and let GreatLord buy the parts. The OS that the server would run would
be Gentoo Linux. I will of course install Apache, SVN, cross-compile GCC
and whatever you need on the server for you.
Best regards,
Fredrik Smedberg (JvA)
Rick Langschultz wrote:
> I think ReactOS should have no Reverse Engineered code within it.
> Reverse Engineering could be bad for the projects publicity and code-base.
> I think that reverse engineering of the Microsoft Code is wrong!!!
> And if programmers within this project want to reverse engineer they
> should start their own projects, with their own names, and use their
> own code. How would you like your product(s) to be stolen?
It's not wrong, and it's not illegal. If Microsoft provided better
documentation for their internal interfaces, then it wouldn't be required.
Without reversing to discover how various parts work, ReactOS would struggle
to make a fully compatable system.
You don't think that writing an operating system to effectively clone the
Windows methodologies is wrong, yet you think that reversing various parts
to discover how it works is. That doesn't make sense to me.
As long as there is no code copying, there is no problem. One person
reverses and documents how something works, another person reads the docs
and reimplements it. It's just like reading a book.
It's no different than dismantling an engine, or a calculator, or a toy to
understand how it works.
Ged
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
Sorry about that, It seems like my mail-client automatically used the same style as the original mail I responded to...
Regards
Johannes
> Från: Alex Buell <alex.buell(a)munted.org.uk>
> Till: ReactOS Development List <ros-dev(a)reactos.org>
> Rubrik: Re: [ros-dev] Moving svn to another contrury or not
> Datum: Thu, 2 Feb 2006 14:25:18 +0000
> On Thu, 2 Feb 2006 13:37:24 +0000 (GMT) "Johannes Olofsson"
> <johannes_olofsson(a)spray.se> waved a wand and this message magically
> appeared:
>
> Your message was full of html tags. Can you make sure your mailer uses
> plain text instead of html. Some of us don't use clients that likes
> html, you know.
>
> --
> <a href=http://www.munted.org.uk>http://www.munted.org.uk</a>
> "Honestly, what can I possibly say to get you into my bed?" - Anon.
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> <a
> href=http://www.reactos.org/mailman/listinfo/ros-dev>http://www.reactos.org/
> mailman/listinfo/ros-dev</a>
Hi all,
Steven Edwards wrote at http://www.reactos.org/xhtml/ru/news_page_14.html:
"One final note, this audit of the code is going to take a long time. It
could take years, but it will happen, this project will come out better
than it was before".
Whether means it, what all development will be suspended for the period
of audit? I understand necessity of audit, but I am afraid, that in a
year the urgency of the project will catastrophically fall, and it will
hopelessly lag behind from Microsoft :(.
I want, that ReactOS have survived...
WBR,
DarkHobbit
I'd like to put this amendment to the IP policy to a vote, but first let's
start with the 7 day discussion period.
"If an API or a particular behaviour of an API which is part of the
Windows(R) operating system is not publicly documented by Microsoft, then
the API or the particular behaviour of the API may only be implemented in
ReactOS if there is documentation of published software which depend on the
API or the particular behaviour of the API, and which is not only
distributed with the Windows(R) operating system. The documentation must be
available in the repository."
I argue that the more ReactOS differ from Windows, the harder it will be to
prove that ReactOS is a derivative work of Windows.
Med venlig hilsen / best regards
Casper Hornstrup
Chief Executive Officer @ Eudicon
ch(a)eudicon.com / www.eudicon.com
(+45) 27 29 36 20
Casper Hornstrup wrote:
> "If an API or a particular behaviour of an API which is part of the
> Windows(R) operating system is not publicly documented by
> Microsoft, then
> the API or the particular behaviour of the API may only be
> implemented in
> ReactOS if there is documentation of published software which
> depend on the
> API or the particular behaviour of the API, and which is not only
> distributed with the Windows(R) operating system. The
> documentation must be
> available in the repository."
>
What if a particular API is required for a particular program to work, but
that API is undocumented by both Microsoft and the owner of the said
program?
Also, what about using code from 3rd parties which might contain
undocumented API's, like Wine for instance?
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
art yerkes wrote:
> > Which is of course fine, but since ReactOS has no use for
> it, why commit it?
> > It isn't needed to meet the goals of ReactOS.
> >
> > Casper
>
> I don't agree with this sentiment at all. We've always
> before been proactive
> about implementing at least visible parts of the API to make
> it more likely
> that applications we didn't know about would have a chance to
> work. I think
> that's a reasonable way to work, especially if you're working
> in an area you've
> got a good understanding of.
I completely agree with this. Some of the rules being proposed seem to be a
little over cautious.
This 'shake up' shouldn't put a strangle hold on the project.
Ged
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
> Too vague in my book. I request a reformulation. I sort of get what you
> try to indicate, but it's too easy to explain incorrectly and the
> meaning as I understand it doesn't include enough APIs to be of any
> significance to note down in the IP policy. There are also arguments
> against it, like the educational purpose of being able to lecture at
> universities on the subject of NT using ReactOS.
Why would you want to lecture on the subject "alternative ways to implement undocumented APIs that are not used by any 3rd party software"?
/Johannes Olofsson
