Re: [ros-dev] Status Meeting (May 2018) - topic "get the demo laptop running completly and enable automated tests"

[Daniel Reimer]

If this does not count, then I vote for this topic, too. Fun fact here, 
I am listed as core developer :P

Greetings

Daniel


Am 30.05.2018 um 09:39 schrieb michael(a)fritscher.net:
>   Good day,
>
>  just as a suggestion for this or a following meeting (I'm no "core 
>  developer", so I can not attend to it):
>
>  Additional topic: "Get the demo laptop running completely and add it 
>  into our testbot"
>
>  As the main lesson learnt from the CLT18, we have almost no visible 
>  advantages (albeit we progressed very well in the last years!).
>  Most people complained that we dumbing almost at the same level as 
>  years ago - and lost interest.
>
>  This is particulary bad as most things are already at the 90-100% level.
>
>  So my suggestion is to get the demo laptop (the Dell D531) running to 
>  a stage that "normal usage" can be demonstrated:
>
>    * Browsing the internet (already possible)
>    * (Libre or Open or MS) Office working
>    * 2D and simple 3D games running
>      * Have the ATI driver running for decent performance (From my 
>  experience at the CLT, I think this is at the 90-95% stage - see 
>  https://jira.reactos.org/browse/CORE-14464 and the root issue 
>  https://jira.reactos.org/browse/CORE-10456 (which has already patches 
>  provided by vga1)
>    * Sound (listening to music ("works seldom")
>    * Access to a NFS server (already working, but not tested on real hw)
>    * (unformated) printing (already working)
>    * usb thumb sticks (already working with patches)
>
>  I would like having this on the next CLT so we can indeed show the 
>  impressive progress.
>
>  I think the main stumbling is the lack of automated tests on the 
>  laptop. So I would suggest to enable one of the laptops to do 
>  automated testing. At one point, ros could even be booted via PXE, so 
>  it should be fairly easy.
>
>  Either we could put it into the data center rack, or I'm willing to 
>  build and host such a setup at home.
>  Either way, I'm willing to donate a IP KVM switch and a network power 
>  switch to make such setup possible.
>
>  Best regards,
>  Michael Fritscher
>
>  P.S. Timely speaking, I've time tomorrow.
>
>  Am 2018-05-28 09:15, schrieb Colin Finck:
> >   Hi all!
> >
> >  Let me invite you to the May 2018 meeting, taking place this Thursday,
> >  May 31, 2018 at 19:00 UTC.
> >  Invited members will again receive their credentials shortly before the
> >  meeting.
> >
> >  Based on requests and current topics, the agenda looks like this:
> >
> >
> >  1. Status Reports
> >     ==============
> >     Like last time, participants are requested to just post their
> >     prepared reports again to not waste any minute.
> >
> >  2. Improving our handling of PRs and JIRA reports
> >     ==============================================
> >     The global JIRA permissions have been changed this month and there
> >     has been a lot of bad blood regarding issues marked as "trivial".
> >     On the one hand, trivial PRs waste a lot of time of our core
> >     developers as long as they are the only ones able to commit them.
> >     On the other hand, trivial PRs still add minor improvements to the
> >     code, so it would be wrong to just close them as invalid.
> >     Let's have an open discussion on this topic and try to establish
> >     rules we can all work with without taking this problem to a personal
> >     level.
> >
> >  3. Google Summer of Code
> >     =====================
> >     This will be the first meeting, which could be joined by our GSoC
> >     student Victor Perevertkin. If he or the mentors have questions that
> >     are better discussed with all developers in the monthly meeting,
> >     let's do this here.
> >
> >  4. Changes affecting base addresses
> >     ================================
> >     Robert Naumann has requested adding this topic to the agenda.
> >     He couldn't merge several PRs translating .mc files, because that
> >     would blow up the kernel and require a regeneration of all base
> >     addresses. He requested a brainstorming session in this meeting
> >     to get to a conclusion how to deal with this problem.
> >     I know that Joachim Henze has also attempted to change base addresses
> >     lately to fix Photoshop CS2, so this is probably the right time to
> >     deal with this problem.
> >
> >
> >  Further topics can be requested by replying to this mail.
> >  See you all on Thursday!
> >
> >
> >  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