Ros-general

ros-general@reactos.org

1050 discussions

Must Read!!!! Msi.dll and Bison Alert!!!!
by James Tabor 03 Dec '04

03 Dec '04

Hi All! Jim Tabor wrote: > CVSROOT: /CVS/ReactOS > Module name: reactos > Repository: reactos/lib/msi/ > Changes by: jimtabor(a)mok.osexperts.com 04/11/30 11:10:55 > > Added files: > reactos/lib/msi/: .cvsignore Makefile Makefile.in > Makefile.ros-template action.c cond.y create.c > distinct.c handle.c insert.c msi.c msi.spec > msipriv.h msiquery.c order.c package.c query.h > record.c regsvr.c select.c sql.y string.c > suminfo.c table.c tokenize.c update.c > version.rc where.c winehq2ros.patch > > Log message: > First port of Wine projects msi.dll > With this commit, we will be using bison to build cond.y and sql.y. Okay, for those using a Window 32 based system 8^p you will need *bison*! http://gnuwin32.sourceforge.net/packages/bison.htm http://www.mingw.org Good luck, James

11 19

South African TV show evangelises open source
by KJK::Hyperion 25 Nov '04

25 Nov '04

<URL: http://news.zdnet.co.uk/software/linuxunix/0,39020390,39174917,00.htm > Jason, did you know about this? can you try to get interviewed?

3 2

FW: Ekush / ReactOS
by Ge van Geldorp 24 Nov '04

24 Nov '04

> From: Refaz Anam [mailto:refazanam@yahoo.com] > Sent: Tuesday, November 23, 2004 06:34 > To: Ge van Geldorp > Subject: Re: Ekush / ReactOS > > > Dear Ge van Geldorf, > > Thank you very much for asking the clarification. I know, > still so many questions are there and need to be answered > accordingly. But before proceed I need to introduce myself. > > I'm a 40 years old attorney and completed my final education > in UK. I'm looking after the Lianasoft Foundation, a > non-profit organization and eventually the solicitor from > Project 21 side. But I'll try to answer to your questions in > normal way and not as a lawyer. :) > I involved to the Project 21 just from few months back. > Pleaese forgive me if I made wrong answers to the technical > questions as I'm not a technical person. > > Anyway............. > > ------------- > Your account of the events after the Ekush release somewhat > conflicts with my memories of those events. Also, you make it > sound like it was impossible to publish the source because of > technical reasons. However, in EPC/doc/Readme.rtf (part of > the binary package released last week) the following > statement was made: > > "Q. You guys says "Project published under the GPL" but why > don't you published sources? A. Initially we decided that, > EKUSH should be published under the GPL. But, still there is > some confusion within the team. We are now sharing sources > between team members only and unless the confusion goes > removed we cannot publish sources" > ------------- > > > You are right. > Actually, the main problem comes from a few percentage of > non-GPL compatible code, some of them are propitery or some > are not compatible with GPL policy. But basically those > sources came from some other projects and not coded/written > by our devs. I personally was afraid to publish these sources > publicly without owners written permission. And due to the > fact, team was confused to publish the source tree. But > Geldorf, I can assure you more than 100% about its > cleanliness and there is NO LEAKED SOURCES FROM WINDOWS/WINDOWS 2000. > > Sorry Geldorf, I cannot write more for now as I'm going to > outside and will be back tomorrow. I'll come with more > clarifications when back. > > Thanks and regards, > > > Refaz Anam > Lianasoft Foundation > > > Ge van Geldorp <gvg(a)reactos.com> wrote: > Dear Mr. Anam, > > I've read your announcement that appeared on > http://www.ekush.com and on the ReactOS forum at > http://www.reactos.com/en/content/view/full/7336. First of > all, let me say I'm happy that you've decided to respect the > GPL by publishing your source along with the binaries. > > The relationship between Ekush and ReactOS has had a very bad > start. Personally, I'm willing to forget about this and make > a fresh start. This would require honest and open > communication from now on. Unfortunately, I have doubts about > some of the statements in your announcement, specifically: > > "Initial release of Ekush (binary) recently has been > published to the Akshor.com and available for download and > also started uploading weekly binary snapshot. But it was > impossible to make the source downloadable because of the > limited bandwidth issue. Site exceeds its maximum bandwidth > within 3/4 days after the binary made downloadable; a few GB > bandwidth has been increased but reached again to its maximum > limit within another 2/3 days and gone down permanently." > > Your account of the events after the Ekush release somewhat > conflicts with my memories of those events. Also, you make it > sound like it was impossible to publish the source because of > technical reasons. However, in EPC/doc/Readme.rtf (part of > the binary package released last week) the following > statement was made: > > "Q. You guys says "Project published under the GPL" but why > don't you published sources? A. Initially we decided that, > EKUSH should be published under the GPL. But, still there is > some confusion within the team. We are now sharing sources > between team members only and unless the confusion goes > removed we cannot publish sources" > > This doesn't sound like a techical issue but a deliberate > decision by the Ekush team. Again, I'm willing to forget this > decision and leave it behind us, but the fact that you seem > to distort the truth in your recent announcement worries me. > > As some people on the ReactOS mailing list have noted, we > need to be sure none of the leaked Microsoft Windows 2000 > source makes its way into our code. Since we cannot compare > submitted code against the leaked source (that would mean > looking at the leaked source ourselves, which would "taint" > us) there has to be a level of trust towards the people who > submit code. I have to say, so far Ekush has done little to > earn that trust. > > Just for the record, I'm just one of the developers of > ReactOS. I don't (and > can't) speak for the other developers, or for the project as a whole. > > Best regards, Ge van Geldorp. > > > > --------------------------------- > Do you Yahoo!? > Discover all that's new in My Yahoo! >

5 6

Ekush / ReactOS
by Ge van Geldorp 22 Nov '04

22 Nov '04

Dear Mr. Anam, I've read your announcement that appeared on http://www.ekush.com and on the ReactOS forum at http://www.reactos.com/en/content/view/full/7336. First of all, let me say I'm happy that you've decided to respect the GPL by publishing your source along with the binaries. The relationship between Ekush and ReactOS has had a very bad start. Personally, I'm willing to forget about this and make a fresh start. This would require honest and open communication from now on. Unfortunately, I have doubts about some of the statements in your announcement, specifically: "Initial release of Ekush (binary) recently has been published to the Akshor.com and available for download and also started uploading weekly binary snapshot. But it was impossible to make the source downloadable because of the limited bandwidth issue. Site exceeds its maximum bandwidth within 3/4 days after the binary made downloadable; a few GB bandwidth has been increased but reached again to its maximum limit within another 2/3 days and gone down permanently." Your account of the events after the Ekush release somewhat conflicts with my memories of those events. Also, you make it sound like it was impossible to publish the source because of technical reasons. However, in EPC/doc/Readme.rtf (part of the binary package released last week) the following statement was made: "Q. You guys says Project published under the GPL but why dont you published sources? A. Initially we decided that, EKUSH should be published under the GPL. But, still there is some confusion within the team. We are now sharing sources between team members only and unless the confusion goes removed we cannot publish sources" This doesn't sound like a techical issue but a deliberate decision by the Ekush team. Again, I'm willing to forget this decision and leave it behind us, but the fact that you seem to distort the truth in your recent announcement worries me. As some people on the ReactOS mailing list have noted, we need to be sure none of the leaked Microsoft Windows 2000 source makes its way into our code. Since we cannot compare submitted code against the leaked source (that would mean looking at the leaked source ourselves, which would "taint" us) there has to be a level of trust towards the people who submit code. I have to say, so far Ekush has done little to earn that trust. Just for the record, I'm just one of the developers of ReactOS. I don't (and can't) speak for the other developers, or for the project as a whole. Best regards, Gé van Geldorp.

2 1

Mails...
by nick_journals 21 Nov '04

21 Nov '04

Hi guys, I'm getting for the second time this week, a message from ros_dev & ros_general that mails are bouncing and I have to re-activate. However when I click on the link in the link in the mail it gives an error that the confirmation string is wrong, manually filling it in doesn't help either. Any ideas why I'm getting these messages? Currently my mailbox has a size of 250Mb with 200kb used... I can't imagin that space is the problem? Anyone else having this problem? Greets, Nick

1 0

Project Structure - Contact Information
by Steven Edwards 20 Nov '04

20 Nov '04

Hello, Some of the recent problems we have had with design issues and with roles in the project have led me to the idea of our current project structure. I think we need to overhaul the system and would like to hear some feedback. If anyone wants to jump in please do so. Note the kernel discussion regarding ntoskrnl just made me think about it but that situation is resolving itself. In the past we have discussed having a single person that reviews and commits all patches to check for breakages and such but the CI system will take care of this issue for us. The big problem we face are disagreements on design decisions and direction so I propose the following change, Right now we have 4 or 5 really well defined roles Project Coordinator - Jason Filby Kernel Coordinator - vizzini Application Coordinator - Brian Palmer Translation Team Coordinator - Fireball Release Coordinator - Robert And a possible webmaster. - ?? T ???? I think we also need to look at clearly defining the role of developers that maintain certain key modules. Maybe we need a new page on the website that lists this. The following should be added to the project structure ntoskrnl component managers - Filip, Hartmut explorer.exe - Martin Fuchs the installation system - Eric Kohl Win32 subsystem - GvG networking - Arty build system maintainer - Casper This seems to be the natural evolution the project is taking. This will help if someone new joins the project and has questions and will give us someone to go to in the event of a problem. Thanks Steven __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com

12 19

Ekush part II
by James Tabor 10 Nov '04

10 Nov '04

Hi all! Ros Kernel task switcher, http://blight.eu.org/reactos/ekush-tskswitch.html Great job Blight! On slashdot.org! http://slashdot.org/article.pl?sid=04/11/10/1320231&tid=201&tid=190&tid=1 Thanks a mil GvG! Kick'en A$$ mode, "Lets get our hate on"! )8^| James ps Moven it over to the General list.

1 0

hi all
by iván vodopiviz 04 Nov '04

04 Nov '04

hi, my name is iván vodopiviz (aka BlueSteel), i'm from argentina (that's in south america...) and this is my first post to this list. here's my question: i'd like to run an app coded in VB wich uses gdi+. will this run in reactos by just dropping gdi+.dll the system folder? ps. sorry for my english, my native language is spanish. -- BlueSteel | | Merkoth

5 6

ReactOS 0.2.4 Released
by Robert Köpferl 01 Nov '04

01 Nov '04

The final version of ROS 0.2.4 has been uploaded to sourceforge and is now available to you.

12 22

ReactOS on XBox?
by Al Hartman 30 Oct '04

30 Oct '04

Wow.. I just got present to something... Imagine... "ReactOS on an XBox"? Wouldn't that be cool? Al

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Ros-general