Re: [ros-dev] Postponing the July Meeting

[Giannis Adamopoulos]

Hi, 
I really like this idea. Actually i was thinking something similar about user mode apps
like paint or even the file browser of the shell which can be used from windows xp to
windows 10. (You need just these three files from us: filebrowser.exe, rshell.dll and
browseui.dll).


Ged Murphy <gedmurphy.maillists(a)gmail.com> wrote on Wed, August 1st, 2018, 11:30
PM:
>   We could keep components in the reactos git project
> and just create a new repo for them, however it might still get lost/overshadowed slightly
> by the main reactos codebase. Another option would be to create a new separate project
> with one\multiple repos. This would allow us to truly separate components from the reactos
> project and try to generate interest on their own merit.
>  
>  We'd need to maximize their visibility by adding a good README.rd files with plenty
> of buzzwords for the google crawler bot to pick up.
>  
>  If it was successful and we decide to do more, then we'd need to come up with a
> format as to how to best manage multiple components.
>  Do we have individual repos for each component, which allows dedicated README.rd files?
> This would give maximum flexibility and allow us to have a separate README.rd for each
> component.
>  Do we bundle everything into one repo similar to how the WDK samples are setup? This is
> easier to manage, but less convenient for end users, and won't be as visible for
> people to find in google searches.
>  
>  Ged.
>  
>  
>  -----Original Message-----
>  From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Hermès BÉLUSCA-MAÏTO
>  Sent: Wednesday, 01 August 2018 20:20
>  To: 'ReactOS Development List' <ros-dev(a)reactos.org>
>  Subject: Re: [ros-dev] Postponing the July Meeting
>  
>  Hi,
>  
>  This sounds interesting, for potential developers wanting just to work on some module,
> but not wanting to deal with the whole OS thing.
>  Would this mean that we also have to think about git submodules? Because (in the case of
> the NTFS driver for example) it would be in a different git repo, and then it would have
> to be automatically downloaded and updated whenever one of the core ROS dev updates his
> own ROS git repo.
>  
>  Cheers,
>  Hermes
>  
> >   -----Message d'origine-----
> >  De : Ros-dev [mailto:[e-mail]] De la part de Ged 
> >  Murphy Envoyé : mercredi 1 août 2018 20:16 À : 'ReactOS Development 
> >  List'
> >  Objet : Re: [ros-dev] Postponing the July Meeting
> >  
> >  I have an item for the agenda. I'd like to discuss the possibility of 
> >  moving some of our drivers out of the main repo and into something more convenient.
> >  
> >  In case I don't make the meeting, I'll put forward some of my reasons here:
> >  
> >  This thought has come about due to the btrfs driver which we use from 
> >  Mark Harmstone. Mark's project receives quite a bit of interest on 
> >  github, and I'm assuming one of the reasons is that it's so easy to 
> >  find and build. Searching for 'btrfs windows' lists his project as the 
> >  top hit in google, and building is as simple as cloning, opening the 
> >  project in VS and clicking build (assuming you have the
> >  WDK)
> >  
> >  I'm wondering if we did the same thing to some of our drivers, we 
> >  might generate more interest in them. A good example would be our NTFS driver.
> >  When searching for open source NTFS solutions you're only really given 
> >  Linux and Max options. The reactos driver is buried deep in the search 
> >  list, and you only see it if you know what you're looking for. Next if 
> >  you want to build it, you need to clone the main reactos repo, install 
> >  the build tools, setup and build the environment, build the tool 
> >  chain, build the linkers libs, etc, etc. There are so many barriers 
> >  for people who aren't part of the reactos development team that the chance of getting
> > anyone interested in it are practically zero.
> >  
> >  This process would be much simpler if the code was available to clone 
> >  as a separate project, and could simply build with the WDK and VS. 
> >  There's then a chance that it might start to generate interest, and 
> >  people may start working on it instead of it just bit-rotting deep in our main repo.
> >  
> >  If we're going to do that, why not consider others too. Network cards, 
> >  sound stack, USB, boot loaders, printer drivers, directx, etc, There's 
> >  lots of things that people might be interested in working on and using 
> >  if they weren't tied to the reactos code base. We obviously benefit 
> >  from any external interest, and simply pull/import it back into the reactos project.
> >  
> >  Ged.
> >  
> >  
> >  
> >  -----Original Message-----
> >  From: Ros-dev <ros-dev-bounces(a)reactos.org> On Behalf Of Colin Finck
> >  Sent: Thursday, 26 July 2018 17:58
> >  To: 'ReactOS Development List' <ros-dev(a)reactos.org>
> >  Subject: [ros-dev] Postponing the July Meeting
> >  
> >  Hi all!
> >  
> >  Looking at the calendar, it would be time for the July Meeting today.
> >  However, I didn't receive any agenda proposals and also forgot to 
> >  announce it in the course of releasing 0.4.9.
> >  So I suggest we postpone the meeting to next week's Thursday, August 2.
> >  
> >  Please send agenda proposals by then.
> >  That meeting also allows us to handle last-minute planning regarding 
> >  the Hackfest.
> >  
> >  Best regards,
> >  
> >  Colin
> >  
> >  
> >  
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev 
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev