Project Structure - Contact Information

[Steven Edwards]

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

[Casper Hornstrup]

> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Steven Edwards
> Sent: 17. november 2004 05:09
> To: [e-mail]; [e-mail]; 
> [e-mail]
> Subject: [ros-general] Project Structure - Contact Information
>
> 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

The Subversion team has successfully used the following voting system:
http://svn.collab.net/repos/svn/trunk/HACKING
Search for "voting system". I think we can modify this for our use.

I also believe that area maintainers is the way to go. We have 2M lines
of code to maintain. Its a bit much for one person to track.

Casper

[Steven Edwards]

Hi Casper,

--- Casper Hornstrup [e-mail] wrote:
> The Subversion team has successfully used the following voting
> system:
> http://svn.collab.net/repos/svn/trunk/HACKING
> Search for "voting system". I think we can modify this for our use.
>
> I also believe that area maintainers is the way to go. We have 2M
> lines
> of code to maintain. Its a bit much for one person to track.

Very cool. This may be just what we need.

Thanks
Steven

__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com

[Zach]

Hi,

I would like to announce that the first Splash newsletter has been 
published.  Splash is ReactOS newsletter, and hopefully will get 
"official" approval by the management.  Until then, it is hosted at my site:

http://www.tong-web.com/splash/index.xml

It follows the format that is used by by Kernel Traffic, so should 
integrate there as well.  Please contact me if you have information 
regarding getting the newsletter on the official ReactOS site (if it is 
deemed worthy, that is).

Thanks,
Zach Tong

[K McI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Zach wrote:
| Hi,
|
| I would like to announce that the first Splash newsletter has been
| published.  Splash is ReactOS newsletter, and hopefully will get
| "official" approval by the management.  Until then, it is hosted at my
| site:
|
| http://www.tong-web.com/splash/index.xml
|
| It follows the format that is used by by Kernel Traffic, so should
| integrate there as well.  Please contact me if you have information
| regarding getting the newsletter on the official ReactOS site (if it is
| deemed worthy, that is).
|
| Thanks,
| Zach Tong

Not bad! It reminds me of the Freesite I tried, but yours is much more
clear and nice. I also like the CVS summary. While I'm not connected @
all with ROS, and can't give any approval, I still think that even as an
unofficial publication it can become "The Mozillazine" of ROS. Well,
maybe with ReactSoft.com as the forum ;)

@anyrate, GOOD WORK!

~         -uniQ
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFBm/7E7mze81O92HkRAmAQAJkB2GkvMAj3jPQWo3gJJsH3+4NpcgCeM4ST
> d7jkaXeXl3nRua0dOPeH0kw=
> =rxX0
> -----END PGP SIGNATURE-----

[Steven Edwards]

Hi Zach,

--- Zach [e-mail] wrote:
> It follows the format that is used by by Kernel Traffic, so should 
> integrate there as well.  Please contact me if you have information 
> regarding getting the newsletter on the official ReactOS site (if it
> is 
> deemed worthy, that is).

This is perfect. Have you forwarded it on to Zak Brown?

Thanks
Steven

__________________________________ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.com

[Zach]

Hi Steven,

No, not yet.  I was going to get approval first before sending it off to 
the masses, just in case there were problems or things to be changed, etc.

-Zach

Steven Edwards wrote:
> Hi Zach,
>
> --- Zach [e-mail] wrote:
> > It follows the format that is used by by Kernel Traffic, so should 
> > integrate there as well.  Please contact me if you have information 
> > regarding getting the newsletter on the official ReactOS site (if it
> > is 
> > deemed worthy, that is).
>
> This is perfect. Have you forwarded it on to Zak Brown?
>
> Thanks
> Steven
>
> __________________________________ 
> Do you Yahoo!? 
> Meet the all-new My Yahoo! - Try it today! 
> http://my.yahoo.com
>
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Casper Hornstrup]

I like it. Its very well carried out.

Casper
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Zach
> Sent: 18. november 2004 05:32
> To: ReactOS General List
> Subject: [ros-general] Splash Issue #1
>
> Hi,
>
> I would like to announce that the first Splash newsletter has 
> been published.  Splash is ReactOS newsletter, and hopefully 
> will get "official" approval by the management.  Until then, 
> it is hosted at my site:
>
> http://www.tong-web.com/splash/index.xml
>
> It follows the format that is used by by Kernel Traffic, so 
> should integrate there as well.  Please contact me if you 
> have information regarding getting the newsletter on the 
> official ReactOS site (if it is deemed worthy, that is).
>
> Thanks,
> Zach Tong
> _______________________________________________
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[KJK::Hyperion]

At 05.32 18/11/2004, you wrote:
> http://www.tong-web.com/splash/index.xml

please don't create XML documents that require a validating parser (e.g. 
with an XSL stylesheet). Several clients (notably Opera) don't use a 
validating parser, so us poor saps only see random undelimited text. I'll 
try making you a CSS stylesheet, it doesn't look hard
> It follows the format that is used by by Kernel Traffic, so should 
> integrate there as well

I'm not familiar with the concept - is the newsletter supposed to be 
readable from a browser?

[KJK::Hyperion]

At 14.33 18/11/2004, you wrote:
> I'll try making you a CSS stylesheet, it doesn't look hard

in fact, it's impossible. Too many headings are attributes in the original 
XML, and CSS doesn't like attributes a lot. If subject, posts, etc. were 
elements it may work. And there's the issue that CSS-2 can only do 
presentation, not semantics, so either you serve it as XHTML or you get no 
hyperlinks. I give up. This means I'm not overly enthusiast about it. Oh, 
and please don't use pixel sizes in CSS

[Zach]

Hi all,

KJK::Hyperion -  The reason that this format was chosen was because I 
*had* do follow the format imposed by Kernel Traffic (their XML 
format).  I have no idea how Zack Brown of Kernel Traffic parses his XML 
into XHTML/HTML, so I did what I could.  At first I tried using CSS like 
you mentioned, and also learned just as you did that it is impossible.  
As you said, CSS doesnt like attributes, and IE dislikes those 
attributes in CSS even more.  It was a disastor in IE.

So I started looking for other means to display this XML format (which I 
have no control over) in a browser.  XSLT seemed the choice, though I 
don't know much about it (nor do I do much CSS work either).  So the 
result is as you see, apologies for those that have Opera.

Anyhow, there is an easy, simple fix for the problem.  XSL 
transformations just need to take place at the server instead of the 
client.  Unfortunately, my hosting doesn't give me root access to 
install xsltproc, nor will they install it themselves.  This was one of 
the issues I wanted to talk to the ReactOS web dev's about, since it 
would make everyone's life a lot easier (getting XHTML over the line 
instead of XML to be transformed).

And yes, it is supposed to be read from the browser.

Stefan Pfluger:  Thanks for the mistake.  As to RSS, that should not be 
difficult.  Just create another XSL sheet to transform the XML into RSS 
instead of XHTML (lots of acronyms in that sentence!).  I'll look into 
doing it when I get some time.

Which brings up a point I was thinking about.  Kernel Traffic and WineHQ 
publish weekly "issues".  I was going to do this, but it might not be 
the best.  Instead of issues, I could just post continuous news items 
"blog style".  Please let me know which you would prefer.

Thanks for all the feedback,
-Zach

KJK::Hyperion wrote:
> At 05.32 18/11/2004, you wrote:
> > http://www.tong-web.com/splash/index.xml
>
> please don't create XML documents that require a validating parser 
> (e.g. with an XSL stylesheet). Several clients (notably Opera) don't 
> use a validating parser, so us poor saps only see random undelimited 
> text. I'll try making you a CSS stylesheet, it doesn't look hard
> > It follows the format that is used by by Kernel Traffic, so should 
> > integrate there as well
>
> I'm not familiar with the concept - is the newsletter supposed to be 
> readable from a browser?

[Devin Smith]

On Thu, 18 Nov 2004 12:19:01 -0800, Zach [e-mail] wrote:
> Hi all,
>
> Which brings up a point I was thinking about.  Kernel Traffic and WineHQ
> publish weekly "issues".  I was going to do this, but it might not be
> the best.  Instead of issues, I could just post continuous news items
> "blog style".  Please let me know which you would prefer.
>
> Thanks for all the feedback,
> -Zach

Hi Zach,

I like the idea of weekly reports, or if time doesn't permit weekly,
then biweekly, or even monthly is fine too. It's more like a
newsletter/magazine in that sense.

By the way, good work. The first version looks great under IE6 and Mozilla 1.7

Thanks,
Devin

[Robert Köpferl]

Concerning me, I would use an imperative programming language in order 
to transform the 'kernel-xml' into q'n'd HTML. I'd for example use ruby.
However this is mostly due to my miserable understanding of xslt and 
other methods.

KJK::Hyperion wrote:
> At 05.32 18/11/2004, you wrote:
> > http://www.tong-web.com/splash/index.xml
>
> please don't create XML documents that require a validating parser (e.g. 
> with an XSL stylesheet). Several clients (notably Opera) don't use a 
> validating parser, so us poor saps only see random undelimited text. 
> I'll try making you a CSS stylesheet, it doesn't look hard
> > It follows the format that is used by by Kernel Traffic, so should 
> > integrate there as well
>
> I'm not familiar with the concept - is the newsletter supposed to be 
> readable from a browser?
> _______________________________________________
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Zach]

Until I get server-side XSL (via xsltproc) working, you can see the same 
content here at Kernel Traffic:

http://kerneltraffic.org/reactos/ros20041114_1.html

-Zach

Robert Köpferl wrote:
> Concerning me, I would use an imperative programming language in order 
> to transform the 'kernel-xml' into q'n'd HTML. I'd for example use ruby.
> However this is mostly due to my miserable understanding of xslt and 
> other methods.
>
> KJK::Hyperion wrote:
> > At 05.32 18/11/2004, you wrote:
> > > http://www.tong-web.com/splash/index.xml
> >
> > please don't create XML documents that require a validating parser 
> > (e.g. with an XSL stylesheet). Several clients (notably Opera) don't 
> > use a validating parser, so us poor saps only see random undelimited 
> > text. I'll try making you a CSS stylesheet, it doesn't look hard
> > > It follows the format that is used by by Kernel Traffic, so should 
> > > integrate there as well
> >
> > I'm not familiar with the concept - is the newsletter supposed to be 
> > readable from a browser?
> > _______________________________________________
> > ros-general mailing list
> > [e-mail]
> > http://reactos.com/mailman/listinfo/ros-general
>
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Matt Grab]

Wow, that is nice.  Keep up the good work.
Matt

On Wednesday 17 November 2004 11:32 pm, Zach wrote:
> Hi,
>
> I would like to announce that the first Splash newsletter has been
> published.  Splash is ReactOS newsletter, and hopefully will get
> "official" approval by the management.  Until then, it is hosted at my
> site:
>
> http://www.tong-web.com/splash/index.xml
>
> It follows the format that is used by by Kernel Traffic, so should
> integrate there as well.  Please contact me if you have information
> regarding getting the newsletter on the official ReactOS site (if it is
> deemed worthy, that is).
>
> Thanks,
> Zach Tong
> _______________________________________________
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

[Stefan Pflüger]

On Wed, 17 Nov 2004 20:32:03 -0800
Zach [e-mail] wrote:
> Hi,
>
> I would like to announce that the first Splash newsletter has been 
> published.  Splash is ReactOS newsletter, and hopefully will get

[...]

Really nice, I like it :)

Just a little fix:
"The content of Splash is contained in an <a href="main.xml">XML</a> file, 
 according to the XML format at KernelTraffic."
The file main.xml is non-existant. I'm sure you meant index.xml ;)

And another idea: Wouldn't it be possible to provide an RSS feed like many
blogs do? That would make it possible to use the headlines as live-bookmarks
in Firebird.

Best regards, 
Stefan Pflüger

[Jason Filby]

On Wed, 17 Nov 2004 20:32:03 -0800, Zach [e-mail] wrote:
> I would like to announce that the first Splash newsletter has been
> published.  Splash is ReactOS newsletter, and hopefully will get
> "official" approval by the management.  Until then, it is hosted at my site:

Great work Zack - hope you don't mind - but I've linked to that URL
from reactos.com.

Cheers
Jason

[Zach]

Jason Filby wrote:
> On Wed, 17 Nov 2004 20:32:03 -0800, Zach [e-mail] wrote:
> > I would like to announce that the first Splash newsletter has been
> > published.  Splash is ReactOS newsletter, and hopefully will get
> > "official" approval by the management.  Until then, it is hosted at my site:
>
> Great work Zack - hope you don't mind - but I've linked to that URL
> from reactos.com.
>
> Cheers
> Jason

Thats fine with me, and much appreciated.  I will contact you in private 
to discuss some other matters.

Thanks again,
-Zach

[Maritn "E.T." Misuth]

Zach wrote:
> Hi,
>
> I would like to announce that the first Splash newsletter has been 
> published.  Splash is ReactOS newsletter, and hopefully will get 
> "official" approval by the management.  Until then, it is hosted at my 
> site:
>
> http://www.tong-web.com/splash/index.xml
>
> It follows the format that is used by by Kernel Traffic, so should 
> integrate there as well.  Please contact me if you have information 
> regarding getting the newsletter on the official ReactOS site (if it 
> is deemed worthy, that is).
>
> Thanks,
> Zach Tong
> _______________________________________________
> ros-general mailing list
> [e-mail]
> http://reactos.com/mailman/listinfo/ros-general

I think it's great, definitely some actual and official resource 
dedicated to ReactOS only, but I would like to suggest some cosmetic 
changes. What about using png or some other format for image at the top 
of the site to avoid jpg compression artefacts? It would be nice to have 
most recent posts at the top too. And excuse my poor english, I know 
it's not very good .

E.T.

"Zach" [e-mail] wrote:
> I would like to announce that the first Splash newsletter has been
> published.  Splash is ReactOS newsletter, and hopefully will get
> "official" approval by the management.  Until then, it is hosted at my

site:
> http://www.tong-web.com/splash/index.xml
>
> It follows the format that is used by by Kernel Traffic, so should
> integrate there as well.  Please contact me if you have information
> regarding getting the newsletter on the official ReactOS site (if it is
> deemed worthy, that is).

The newsletter looks very good!

Could you use the encoding "iso-8859-1" for index.xml instead of "us-ascii"?
Otherwise IE5.5 shows an error message.

Regards,
Eric