Re: Web site maintenance.

[Lucio Diaz]

> Today's Topics:
> Re: What I have learned on my time off
>
> (LinuxWorld) (Jason Filby)

----------------------------------------------------------------------
> Message: 1
> Date: Sat, 6 Nov 2004 10:07:57 +0200
> From: Jason Filby [e-mail]
> Subject: Re: [ros-dev] What I have learned on my
> time off (LinuxWorld)
> To: ReactOS Development List [e-mail]
> Message-ID:
> [e-mail]
> Content-Type: text/plain; charset=US-ASCII
>
> Steven
> > We need a roadmap for the future.
>
> Agreed.
> > We have to have regression testing in place.
>
> Yes - Casper's doing a lot of great work on this;
> with regards to
> WineHQ tests, well, we'll have to see if we can't
> find a way to
> integrate them. Right now let's just focus on
> getting the Continuous
> Integration System going.
> > We need to improve our documentation and
>
> website.
>
> I've already thought about this a lot; definitely a
> wiki for the
> Library - with access only to devs to make changes;
> a wiki doesn't
> have to allow just anyone to make a change and I
> don't think that's a
> good idea. I've already introduced MedaWiki at work
> (it powers
> Wikipedia.com) and would really want to get this on
> reactos.com for
> our Library -- probably a few other pages as well.
>
> I don't want to see a wiki only site. A wiki doesn't
> enforce
> structure, which is nice for something like a blog
> or list of
> compatible hardware/software, or forum. We'll use
> the best software
> suited to the job -- this means that a lot of effort
> will have to go
> into integration: search but more importantly login.
>
> It's just that to get there is a ton of work! The
> website needs its
> own roadmap, for sure.

Mr. Filby, i have ofered twice to colaborate with my
limited capabilities in the proyect, i have offered to
 actualize the website from time to time, and the made
of a FAQ (this will be more difficult, as i will have
to test and ask many howtos on reactos) if you find
this could be usefull.

I am still waiting for an answer.

Best regards,
Lucio Diaz-Flores.

______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es

[Jason Filby]

Lucio
> Mr. Filby, i have ofered twice to colaborate with my limited

capabilities in the proyect, i have
> offered to actualize the website from time to time, and the madeof a

FAQ (this will be more
> difficult, as i will haveto test and ask many howtos on reactos) if

you find this could be
> usefull.

Thanks for your interest in the site; please subscribe to ros-web if
you have not already done so. A plan to move the site forward is being
drawn up and things should soon start happening.

Thanks for the FAQ; I've kept your email for when I have more time to
post it on the site.

Regards
Jason

[Robert Köpferl]

responding to library doc.

I recendly came over the mono website and it impressed me when I saw 
their "msdn". They built a tree like MS did and baked the leaves with 
generated or written doc.
Maybe we should just knock on their dor and ask them for the source and 
methods they use.

Lucio Diaz wrote:
> > Today's Topics:
> > Re: What I have learned on my time off
> >
> > (LinuxWorld) (Jason Filby)
> > Message: 1
> > Date: Sat, 6 Nov 2004 10:07:57 +0200
> > From: Jason Filby [e-mail]
> > Subject: Re: [ros-dev] What I have learned on my
> > time off (LinuxWorld)
> > To: ReactOS Development List [e-mail]
> > Message-ID:
> > [e-mail]
> > Content-Type: text/plain; charset=US-ASCII
> >
> > Steven
> > > We need a roadmap for the future.
> >
> > Agreed.
> > > We have to have regression testing in place.
> >
> > Yes - Casper's doing a lot of great work on this;
> > with regards to
> > WineHQ tests, well, we'll have to see if we can't
> > find a way to
> > integrate them. Right now let's just focus on
> > getting the Continuous
> > Integration System going.
> > > We need to improve our documentation and
> >
> > website.
> >
> > I've already thought about this a lot; definitely a
> > wiki for the
> > Library - with access only to devs to make changes;
> > a wiki doesn't
> > have to allow just anyone to make a change and I
> > don't think that's a
> > good idea. I've already introduced MedaWiki at work
> > (it powers
> > Wikipedia.com) and would really want to get this on
> > reactos.com for
> > our Library -- probably a few other pages as well.
> >
> > I don't want to see a wiki only site. A wiki doesn't
> > enforce
> > structure, which is nice for something like a blog
> > or list of
> > compatible hardware/software, or forum. We'll use
> > the best software
> > suited to the job -- this means that a lot of effort
> > will have to go
> > into integration: search but more importantly login.
> >
> > It's just that to get there is a ton of work! The
> > website needs its
> > own roadmap, for sure.
>
> Mr. Filby, i have ofered twice to colaborate with my
> limited capabilities in the proyect, i have offered to
>  actualize the website from time to time, and the made
> of a FAQ (this will be more difficult, as i will have
> to test and ask many howtos on reactos) if you find
> this could be usefull.
>
> I am still waiting for an answer.
>
> Best regards,
> Lucio Diaz-Flores.
>
> ______________________________________________
> Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
> Nuevos servicios, más seguridad
> http://correo.yahoo.es
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Filip Navara]

Robert Köpferl wrote:
> responding to library doc.
>
> I recendly came over the mono website and it impressed me when I saw 
> their "msdn". They built a tree like MS did and baked the leaves with 
> generated or written doc.
> Maybe we should just knock on their dor and ask them for the source 
> and methods they use.

They're using their tool MonoDoc which is something like JavaDoc for C#. 
It builds documentation from comments embedded in the source code or 
from separate files with markups. We're doing the same with doxygen 
(http://reactos.com/doxygen/), but it's not much usefull without the 
source code being annotated...

Regards,
Filip