hello,
Thank you very much for all the help guys. I am interested in the Fast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me.
Thanks & Regards, sudhir.
Hello sudhir, since you're interested in the fastfat_new project, you might want to approach Aleksey. He's the maintainer of that part of ReactOS, but has recently turned his attention to other things. He should give you some background information, and maybe an outline of things that have to be done for fastfat_new to be fully functional.
The following links may also be of interest to you: http://wiki.fullfat-fs.co.uk/ http://www.reactos.org/en/newsletter_66.html#sec1
Since you currently don't have commit access to SVN, I suggest that you submit any changes to us via our Bugzilla. Please see http://www.reactos.org/wiki/Submitting_Patches for more information.
On Thu, Jan 14, 2010 at 10:55 PM, sudheer kumar sudheer_viz@yahoo.comwrote:
hello,
Thank you very much for all the help guys. I am interested in theFast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me.
Thanks & Regards, sudhir.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Before this goes too far and no one steps in, I would suggest this was a personal project being developed in a certain way to make it extensible to other modules.
Any patches to this area which don't fit this niche spec would probably be rejected.
In my opinion, it would be better to pick an area that wasn't being actively developed, especially in a very particular way such as this is.
Ged.
From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Alwyn Tan Sent: 15 January 2010 17:56 To: ReactOS Development List Subject: Re: [ros-dev] Request for a project
Hello sudhir, since you're interested in the fastfat_new project, you might want to approach Aleksey. He's the maintainer of that part of ReactOS, but has recently turned his attention to other things. He should give you some background information, and maybe an outline of things that have to be done for fastfat_new to be fully functional.
The following links may also be of interest to you: http://wiki.fullfat-fs.co.uk/ http://www.reactos.org/en/newsletter_66.html#sec1
Since you currently don't have commit access to SVN, I suggest that you submit any changes to us via our Bugzilla. Please see http://www.reactos.org/wiki/Submitting_Patches for more information.
On Thu, Jan 14, 2010 at 10:55 PM, sudheer kumar sudheer_viz@yahoo.com wrote:
hello,
Thank you very much for all the help guys. I am interested in the Fast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me.
Thanks & Regards, sudhir.
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Agreed, which was why I told Sudhir to approach Aleksey so that Sudhir can be properly briefed.
On Sat, Jan 16, 2010 at 4:40 AM, Ged Murphy gedmurphy@gmail.com wrote:
Before this goes too far and no one steps in, I would suggest this was a personal project being developed in a certain way to make it extensible to other modules.
Any patches to this area which don’t fit this niche spec would probably be rejected.
In my opinion, it would be better to pick an area that wasn’t being actively developed, especially in a very particular way such as this is.
Ged.
*From:* ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] *On Behalf Of *Alwyn Tan *Sent:* 15 January 2010 17:56 *To:* ReactOS Development List *Subject:* Re: [ros-dev] Request for a project
Hello sudhir, since you're interested in the fastfat_new project, you might want to approach Aleksey. He's the maintainer of that part of ReactOS, but has recently turned his attention to other things. He should give you some background information, and maybe an outline of things that have to be done for fastfat_new to be fully functional.
The following links may also be of interest to you: http://wiki.fullfat-fs.co.uk/ http://www.reactos.org/en/newsletter_66.html#sec1
Since you currently don't have commit access to SVN, I suggest that you submit any changes to us via our Bugzilla. Please see http://www.reactos.org/wiki/Submitting_Patches for more information.
On Thu, Jan 14, 2010 at 10:55 PM, sudheer kumar sudheer_viz@yahoo.com wrote:
hello,
Thank you very much for all the help guys. I am interested in theFast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me.
Thanks & Regards, sudhir.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
I explained briefly, however I warned that this project requires extensive IFS knowledge, while actual underlying filesystem skills may not be so useful (since FullFAT/ntfs-3g is being used).
Thinking about it I agree with Ged that it's better for Sudhir to try to pick another area. Though, of course, he's free to develop his own fastfat_new as his university work, if he feels like it. But I won't guarantee we will accept all patches, or that we stop working on that module ourselves.
WBR, Aleksey Bragin.
On Jan 16, 2010, at 12:12 PM, Alwyn Tan wrote:
Agreed, which was why I told Sudhir to approach Aleksey so that Sudhir can be properly briefed.
On Sat, Jan 16, 2010 at 4:40 AM, Ged Murphy gedmurphy@gmail.com wrote: Before this goes too far and no one steps in, I would suggest this was a personal project being developed in a certain way to make it extensible to other modules.
Any patches to this area which don’t fit this niche spec would probably be rejected.
In my opinion, it would be better to pick an area that wasn’t being actively developed, especially in a very particular way such as this is.
Ged.
From: ros-dev-bounces@reactos.org [mailto:ros-dev- bounces@reactos.org] On Behalf Of Alwyn Tan Sent: 15 January 2010 17:56 To: ReactOS Development List Subject: Re: [ros-dev] Request for a project
Hello sudhir, since you're interested in the fastfat_new project, you might want to approach Aleksey. He's the maintainer of that part of ReactOS, but has recently turned his attention to other things. He should give you some background information, and maybe an outline of things that have to be done for fastfat_new to be fully functional.
The following links may also be of interest to you: http://wiki.fullfat-fs.co.uk/ http://www.reactos.org/en/newsletter_66.html#sec1
Since you currently don't have commit access to SVN, I suggest that you submit any changes to us via our Bugzilla. Please see http:// www.reactos.org/wiki/Submitting_Patches for more information.
On Thu, Jan 14, 2010 at 10:55 PM, sudheer kumar sudheer_viz@yahoo.com wrote:
hello,
Thank you very much for all the help guys. I am interestedin the Fast FAT project. Also arty and colibri gave me an idea to work on partmgr.sys. I am more interested towards Fast FAT as I have prior experience on file systems and I can show something concrete to my professor. The other thing is for partmgr.sys I need to start from the scratch and there isnt much info about it. Is it fine for others ??(since some one might be working on it).The idea of adding list of all the medium sized task to the wiki is good as its going to help people like me.
Thanks & Regards, sudhir.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
Then,Aleksey,as Coordinator,May you suggest any area,or any task,that we do really need to have done,and that Sudhir can help in? All of you were saying that you like the sincerity.Ok,this is my small point of sincerity about this situation(jump it if you wish):
[Small-Point-of-Sincerity] I´m really worried about finding that this team is unable to tell him a small list of possible tasks to be accomplished,or even more, just ONE.
If i recall correctly one of the points we are interested in,is introducing ReactOS in the University,so students get interested in helping ROS for their Career Projects,and maybe continuing here as Developers when finishing their studies. How are we going to do that when we arent able to write a List of Concise Tasks??Are we going to lose the opportunity of introducing ReactOS in Sudhir University, so maybe we can create a relationship with that University and his Teacher for future PR??
OKAY. Sudhir,give a look to this page: http://www.reactos.org/wiki/Missing_ReactOS_Functionality It is maybe quite general, but i hope maybe you can find an interesting place to work in. I´m quite dissapointed with finding that Testers(thanks Elhoir,thanks Gabriel) are trying to give answers to this guy from our limited knowledge,while our Devs still remains in the most complete silence.And the few Devs that have answered were just to say a "No,No" instead a "No,no,but you can try to implement XXXX".Discouraging instead Redirecting. Quite interesting to discover that People here tends towards answering Dramas instead Helping the project.
We are in 0.3.11, we want to reach 1.0, that means (1.0-0.3.X=)0.7 releases-full-of-implementations ahead.Can´t we tell him just ONE of them? [/Small-Point-of-Sincerity]
Swallow the sincerity as you wish or throw it to the Delete folder ignoring that something has to change here for the Project Welfare.
Best regards and hammering yours.. _________________________________________________________________ ¡Nuevo MSN Noticias! Vive la información las 24 horas, con un análisis profundo de la actualidad que más te interesa. http://noticias.es.msn.com/
- Windows 2003-compatible USB drivers stack, or any part of it. Host controller is now done by Michael Martin, however HUGE amount of other parts is not, but can be done in parallel using Win2003 as development target. Example - HID, mouse, keyboard, audio, storage. Any of these parts (if implemented against a real Windows 2003 or, with exceptions, later versions) will be useful - Windows 2003 or higher compatible storage stack, or any part of it. Including partition manager, volume manager, controller drivers, anything. Requires substantial PnP and storage devices knowledge. Very advanced. - Windows 2003 compatible network stack, or any part of it. Pick what you like - from lower level NIC drivers, to NDIS, to the intermediate kernelmode layer, up to usermode Winsock implementation. Everything could be done and tested in a real Windows installation without the need to touch ReactOS. - WiFi support, comes as a standalone task because it needs some special services and applications to manage WiFi connection, independent from the network stack. Also, should be modelled after Windows 2003 or later. - Implementing ACPI support (driver, testing functionality, etc). - Improving general usability: Making proper partitioning support in ReactOS; testing, debugging and finishing the filesystem checker; - Improving general look&feel: Second stage installation should be reworked to look modern, not as an OS from 1998. - Making integration with existing Windows servers possible - implement SMB sharing support, Active Directory, etc. - Shell rewrite (finishing explorer_new and all required components, ash77 is currently working on that though) - Improving the kernel: writing regression tests for the Native API - Improving the kernel: writing missing modules (e.g. implementing Se, Wmi, etc) - requires advanced NT kernel knowledge!
That's for a start. This list doesn't include any Win32 subsystem related tasks, because I am going to send out a separate email outlining all issues we have in the Win32 subsystem, how Arwinss could help solve part of them, what to do with other, etc.
Victor - don't be so critical, not every dev has an overview, and those who have knowledge about any specific part already commented on that. Though I agree that when it comes to drama, mailing list receives tens of messages per day, but when a real issue needs commenting, everyone is passive.
WBR, Aleksey Bragin.
On Jan 16, 2010, at 3:40 PM, victor martinez wrote:
Then,Aleksey,as Coordinator,May you suggest any area,or any task,that we do really need to have done,and that Sudhir can help in?
- Windows 2003 or higher compatible storage stack, or any part of it.
Including partition manager, volume manager, controller drivers, anything. Requires substantial PnP and storage devices knowledge. Very advanced.
Cameron (irc: aicom) is working on this, AFAIK. You should talk with him for synchronization
Thanks Aleksey for pointing out these achievable needs ;)
Aleksey wrote: Victor - don't be so critical, not every dev has an overview, and those who have knowledge about any specific part already commented on that.
I hope sometimes a criticism is positive for the wellfare of the Project. If you look carefully the only Devs which answered this guy was GedMurphy,JoseCatena(quite recent dev)and You. And really noone of you(except JoseCatena) were pointing Sudhir to places to work on. In a Drama more than 10 Devs attacks one against others with spoons and plastic helmets. To create an overview we just need to know the needs of a Dev in his particular area. I can tell to the community what needs to be fixed in my house, my neighbor can tell to the community which room needs a re-paint or need to be construct(I can´t say what needs to be fixed in my neighbor apartment).If the neighborhood write the needs in a list, and a Free-as-a-beer Developer arrives to the Community, he can pick a task and try to fix it. As Developers werent showing their own needs(Plan A),neither general needs, i asked you for an Overview as Coordinator(this was the Plan B).I´m pretty sure each Dev could have told us a thing to be solved in their houses.That would have created a Whole Overview quite easy.
***************************
Ged wrote: I'm not really sure what you expect anyone to say. There's thousands of
things that need doing, we can't start listing everything.
I didnt ask for a Thousand list of items,just a couple.Until this morning(and before my latest Email) i did not see a single one need sent from a Developer email. Just Jose Catena´s.
Contrary
to your beliefs, we aren't available to walk every interested person through the process of working out what they are interested in, what their skill set allows and what they can work on.
I didnt ask for a List of Personalized Tasks for this guy, I asked for a List of "Achievable and Concise Tasks" as Aleksey sent in his latest email. Btw, my beliefs are exactly the same as Jose Catena: "He’s who can tell if it fits his interest and abilities or not.", so he will choose the tasks, not we.So we dont need to go through any working out process. The request was much simpler: "A-List-of-Tasks"
The general rule is 'you can work on anything that interests you'.
Everything needs work, there's virtually no module that's complete.
1)How a newcomer knows that all the modules are not complete?A newcomer is someone that wants to help but doesnt know which Apartment needs a fix. Put in the Main Door a list of tasks and he will choose one that fits his interest and he will go directly to the apartament number 124,room "Kitchen". But the sentence "you can work on anything that interests you" really means NOTHING,or worse,it means that the newcomer needs to go appartment through appartment searching room through room,what needs to be fixed inside of each one,totally clueless. As boring task for a newcomer Dev as working on Documentation for Devs.So newcomers will end leaving totally bored. And we would have lost a Dev.
2)Guiding. Thanks to the "you can work on anything that interests you" rule, one newcomer can begin working in preparing ReactOS to give support to "Veritas File System",something that is maybe not critical or needed in our current state.And maybe it will,indeed,be rejected.We will lose a valuable Dev that maybe could have work in other areas of the System,and a potential foe after refusing his 100hours-patch. So having a List of tasks in the "Main Door" that we consider basics for now will help to: A)Newcomer will know that is really helping us, with a high possibility of having his work commited. B)It guides newcomers to have an operative OS asap thanks to a positive discrimation made when writting a task in the Main Door and deciding not writting other tasks because not needed now.Or writting the latter ones to a Non-prioritary List.
"Easier newcomers find what they need,Easier they will join the project".And currently we can´t apply this rule to ReactOS.
Sorry the big wall of text ;)
_________________________________________________________________ Hotmail es capacidad. ¡Descubre sus ventajas y llévate un Mazda 2 gratis! http://www.vivelive.com/historiasdehotmail/
I'm not really sure what you expect anyone to say. There's thousands of things that need doing, we can't start listing everything.
Contrary to your beliefs, we aren't available to walk every interested person through the process of working out what they are interested in, what their skill set allows and what they can work on. This is something developers work out for themselves.
The general rule is 'you can work on anything that interests you'. Everything needs work, there's virtually no module that's complete.
Ged.
If someone came along and said "I'm
On Sat, Jan 16, 2010 at 12:40 PM, victor martinez vicmarcal@hotmail.comwrote:
Then,Aleksey,as Coordinator,May you suggest any area,or any task,that we do really need to have done,and that Sudhir can help in? All of you were saying that you like the sincerity.Ok,this is my small point of sincerity about this situation(jump it if you wish):
[Small-Point-of-Sincerity] I´m really worried about finding that this team is unable to tell him a small list of possible tasks to be accomplished,or even more, just ONE.
If i recall correctly one of the points we are interested in,is introducing ReactOS in the University,so students get interested in helping ROS for their Career Projects,and maybe continuing here as Developers when finishing their studies. How are we going to do that when we arent able to write a List of Concise Tasks??Are we going to lose the opportunity of introducing ReactOS in Sudhir University, so maybe we can create a relationship with that University and his Teacher for future PR??
OKAY. Sudhir,give a look to this page: http://www.reactos.org/wiki/Missing_ReactOS_Functionality It is maybe quite general, but i hope maybe you can find an interesting place to work in. I´m quite dissapointed with finding that Testers(thanks Elhoir,thanks Gabriel) are trying to give answers to this guy from our limited knowledge,while our Devs still remains in the most complete silence.And the few Devs that have answered were just to say a "No,No" instead a "No,no,but you can try to implement XXXX".Discouraging instead Redirecting. Quite interesting to discover that People here tends towards answering Dramas instead Helping the project.
We are in 0.3.11, we want to reach 1.0, that means (1.0-0.3.X=)0.7 releases-full-of-implementations ahead.Can´t we tell him just ONE of them? [/Small-Point-of-Sincerity]
Swallow the sincerity as you wish or throw it to the Delete folder ignoring that something has to change here for the Project Welfare.
Best regards and hammering yours..
Windows 7 es fácil, cómodo y sin complicaciones. ¡Conócelo!http://www.sietesunpueblodeexpertos.com/index_windows7.html
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
On Sat, Jan 16, 2010 at 1:57 PM, Ged Murphy gedmurphy@gmail.com wrote:
If someone came along and said "I'm
Err, that wasn't meant to be there.
I was going to say, if someone comes along and says "Hi, I'm a kernel dev and I'm interested in implementing support for an ext3 file system" or "I'm a system dev and I'm interested in improving usermode support for networking, can you give me some information on the current status before I start to read through the code", then it's pretty certain that they would get quick replies relating to their questions.
When someone comes along and says, "Hi, I want to help, what needs doing", where do you go with that? The fact that said person hasn't bothered to do any background research on either their own interests or the project doesn't speak too highly IMO.
btw Sudhir, this mail isn't targeted at you, I speaking in general as to the best way to go about things to get the most useful results. Anyway, I seem to have 'gone off on one' again. Hopefully it helps though.
Ged.