Re: [ros-dev] Fwd: Status update and voting

[Steven Edwards]

Hi Royce,

--- Royce Mitchell III <royce3(a)ev1.net> wrote:
>   I don't think anybody would agree to me taking it
> on, my ability to 
>  contribute seems to come and go, and we need somebody who's going to be 
>  around more often than not. 
Thats the only reason I didn't put your name on my list, not because of any lack for
faith in your
ability and leadership.

My leaning still goes to Alex for his knowledge on the kernel. He and I have discussed
what I view
to be attitude and professionalism (which I think we can agree most of us on IRC lack
sometimes)
that the Kernel Cordinator needs to have. Because of the voting system we have some have
also
suggested just not having a KC but I don't really think this is a good idea because
sometimes we
need a point person to send patches to, direct media and new developer questions, and
settle
disputes that cannot be fixed via voting.

Thanks
Steven



		
__________________________________ 
Do you Yahoo!? 
Read only the mail you want - Yahoo! Mail SpamGuard. 
http://promotions.yahoo.com/new_mail

[Rick Langschultz]

I know I haven't really contributed much/or any code to the ReactOS project
but I think that the voting portion of the decisions should be online based.
If ReactOS provided a portal site for developers, contributers, and testers
the ReactOS project would be more likely to retain votes partially because
email and IRC are not always accessible on machines, or can often times fail
to transmit. There is no telling when I get disconnected from IRC because of
some of the programs I run on my personal computer. I also feel that ReactOS
is doing a fine job with the development but a portal system that uses
authentication would provide a more than stable platform for developing
ideas and knowledge that will drive it's development force.

Here is what I propose:

Change the overall background of the site. Add a portal system that allows
users to login and logoff when they see fit. Because portals are becoming
increasingly popular with businesses ReactOS can use an Access Control
Manager to decide what specific users can do on the portal. It would also
allow users to upload debug reports into a database or a file that can be
viewed or downloaded.

A driver resource directive can also be added for testing. With a small or
large forum site to allow users to post comments and reports of what they
have found to work, and not work for them. Then the information can be
mailed out in the form of "There is a new patch for the via (insert model
number here) chipset please download it". This would accomplish many things,
greater productivity in email reading. There is often times I can not sit
and read 300 emails about a debug report.

A personal inventory system: when users set up ReactOS on their personal
machines they can click on boxes to allow personalized profiles to be shared
about their test machines. If a user uses a 64bit machine with 256mb of ram
and a via (something) chipset customized emails with driver updates and
patches can be sent to them.

Sure the site is great not. I just think it could be better given what other
operating system companies employ on their respective websites.

Tell me what you all think. I would love to hear the feedback on this one!!!

If you would like I could start on such a site and donate it as part of the
Tax free project that you are working on. It would have to be html, php, and
mysql or xml files. Thanks for reading this!!!

[Klemens Friedl]

>   ...It would also
>  allow users to upload debug reports into a database or a file that can be
>  viewed or downloaded ... 
>  A driver resource directive can also be added for testing. With a small 
>  or large forum site to allow users to post comments and reports of what 
>  they have found to work, ...
>  ... personal inventory system: when users set up ReactOS on their 
>  personal machines ... 
I created (last summer) such a page that include some of the feature
(http://reactosde.re.funpic.de/index.php).
Currently, I redesign the inner structur and will combine it with the new
upcoming hp design (and login system).

A first alpha version of the flexible new page:
http://frik85.fr.funpic.de/packmgr/

with the flexible system it is possible to generate 
* app-, driver-, hardware-, ect. reports
* view packages for the Ros Package Manager online datbase
* ...
all with the same database => picture:
http://reactosde.re.funpic.de/mediadetail.php?sec=Articles&cat=ideas&am…
(click download to view the picture)

-- 
Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

[Gedi]

Rick Langschultz wrote:

>  Sure the site is great not. I just think it could be
> better given what other
> operating system companies employ on their respective websites.
>   
>  
The website is in the process of being redesigned, although it is in the 
early stages.

>  If you would like I could start on such a site and
> donate it as part of the
> Tax free project that you are working on. It would have to be html, php, and
> mysql or xml files. Thanks for reading this
>   
>  
It might be worth waiting until the user interface team is up and 
running (soon) as they will be taking control of the website design.
You could then express your interest in helping develop it and possibly 
join the team

Ged.

[Rick Langschultz]

Another feature I would like to see enabled would be an "install update
queue" providing users to login under an account and choose which updates to
install based on information provided. The updates would later be installed
by an update type program that would connect to the host server daily or
perhaps hourly to retrieve updates and check mail by the development team.
This would provide a great way to remotely administrate updates to a
personal system as well as be a great way to test some sort of XML-RPC
compatibility of ReactOS when a stable network implementation occurs. To
allow this someone has to also get onto a port of ipchains or some other
firewalling service. Both of which (services and networking) need to be
compatible and completed before implementation.

-----Original Message-----
From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On
Behalf Of Rick Langschultz
Sent: Wednesday, May 25, 2005 4:37 PM
To: 'ReactOS Development List'
Subject: [ros-dev] Portal Site (A little long)

I know I haven't really contributed much/or any code to the ReactOS project
but I think that the voting portion of the decisions should be online based.
If ReactOS provided a portal site for developers, contributers, and testers
the ReactOS project would be more likely to retain votes partially because
email and IRC are not always accessible on machines, or can often times fail
to transmit. There is no telling when I get disconnected from IRC because of
some of the programs I run on my personal computer. I also feel that ReactOS
is doing a fine job with the development but a portal system that uses
authentication would provide a more than stable platform for developing
ideas and knowledge that will drive it's development force.

Here is what I propose:

Change the overall background of the site. Add a portal system that allows
users to login and logoff when they see fit. Because portals are becoming
increasingly popular with businesses ReactOS can use an Access Control
Manager to decide what specific users can do on the portal. It would also
allow users to upload debug reports into a database or a file that can be
viewed or downloaded.

A driver resource directive can also be added for testing. With a small or
large forum site to allow users to post comments and reports of what they
have found to work, and not work for them. Then the information can be
mailed out in the form of "There is a new patch for the via (insert model
number here) chipset please download it". This would accomplish many things,
greater productivity in email reading. There is often times I can not sit
and read 300 emails about a debug report.

A personal inventory system: when users set up ReactOS on their personal
machines they can click on boxes to allow personalized profiles to be shared
about their test machines. If a user uses a 64bit machine with 256mb of ram
and a via (something) chipset customized emails with driver updates and
patches can be sent to them.

Sure the site is great not. I just think it could be better given what other
operating system companies employ on their respective websites.

Tell me what you all think. I would love to hear the feedback on this one!!!

If you would like I could start on such a site and donate it as part of the
Tax free project that you are working on. It would have to be html, php, and
mysql or xml files. Thanks for reading this!!!


_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev

[Jason Filby]

Hi Rick

The ros-web list is probably the best place to post this, or at least cc.

The current plan for the web is to:
1) Redesign the look (Mikko's mock-up will likely be used, thanks
Brandon for converting to HTML)
2) Largely move to a Wiki based system except for specialized apps
(eg. Bugzilla for issues)

The wiki is an uncomplicated and scalable solution which should be
fine for our purposes. There's also a move towards software already
written to reduce maintenance.

Specialized apps still have a place (eg. the update queue - which is
actually being worked on as the Package Manager).

Regards
Jason

On 5/26/05, Rick Langschultz <rlangschultz(a)cox.net> wrote:
>   Another feature I would like to see enabled would be
> an "install update
>  queue" providing users to login under an account and choose which updates to
>  install based on information provided. The updates would later be installed
>  by an update type program that would connect to the host server daily or
>  perhaps hourly to retrieve updates and check mail by the development team.
>  This would provide a great way to remotely administrate updates to a
>  personal system as well as be a great way to test some sort of XML-RPC
>  compatibility of ReactOS when a stable network implementation occurs. To
>  allow this someone has to also get onto a port of ipchains or some other
>  firewalling service. Both of which (services and networking) need to be
>  compatible and completed before implementation.
>  
>  -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On
>  Behalf Of Rick Langschultz
>  Sent: Wednesday, May 25, 2005 4:37 PM
>  To: 'ReactOS Development List'
>  Subject: [ros-dev] Portal Site (A little long)
>  
>  I know I haven't really contributed much/or any code to the ReactOS project
>  but I think that the voting portion of the decisions should be online based.
>  If ReactOS provided a portal site for developers, contributers, and testers
>  the ReactOS project would be more likely to retain votes partially because
>  email and IRC are not always accessible on machines, or can often times fail
>  to transmit. There is no telling when I get disconnected from IRC because of
>  some of the programs I run on my personal computer. I also feel that ReactOS
>  is doing a fine job with the development but a portal system that uses
>  authentication would provide a more than stable platform for developing
>  ideas and knowledge that will drive it's development force.
>  
>  Here is what I propose:
>  
>  Change the overall background of the site. Add a portal system that allows
>  users to login and logoff when they see fit. Because portals are becoming
>  increasingly popular with businesses ReactOS can use an Access Control
>  Manager to decide what specific users can do on the portal. It would also
>  allow users to upload debug reports into a database or a file that can be
>  viewed or downloaded.
>  
>  A driver resource directive can also be added for testing. With a small or
>  large forum site to allow users to post comments and reports of what they
>  have found to work, and not work for them. Then the information can be
>  mailed out in the form of "There is a new patch for the via (insert model
>  number here) chipset please download it". This would accomplish many things,
>  greater productivity in email reading. There is often times I can not sit
>  and read 300 emails about a debug report.
>  
>  A personal inventory system: when users set up ReactOS on their personal
>  machines they can click on boxes to allow personalized profiles to be shared
>  about their test machines. If a user uses a 64bit machine with 256mb of ram
>  and a via (something) chipset customized emails with driver updates and
>  patches can be sent to them.
>  
>  Sure the site is great not. I just think it could be better given what other
>  operating system companies employ on their respective websites.
>  
>  Tell me what you all think. I would love to hear the feedback on this one!!!
>  
>  If you would like I could start on such a site and donate it as part of the
>  Tax free project that you are working on. It would have to be html, php, and
>  mysql or xml files. Thanks for reading this!!!
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>