Hi all!
Let me invite you to the November 2018 meeting, taking place next Thursday, November 29, 2018 at 19:00 UTC. Invited members will again receive their credentials shortly before the meeting.
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
Best regards,
Colin
I'm at work but I will do my best to attend!
El sáb., 24 nov. 2018 21:38, Colin Finck colin@reactos.org escribió:
Hi all!
Let me invite you to the November 2018 meeting, taking place next Thursday, November 29, 2018 at 19:00 UTC. Invited members will again receive their credentials shortly before the meeting.
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
Best regards,
Colin
Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev
Hi all! I'd like to propose some discuss points too.
1. Web projects roadmap
I think we should write down some kind of roadmap about what we need/want about web services surrounding ReactOS. This can attract people which are not into systems programming by more than just doing translations and issue reporting. (But only if written down in wiki, for example) This can also be converted into list of GSoC ideas in future.
There are two things we need so far: - (higher priority) Updated developer web interface. This is described quite well on GSoC 2018 ideas page ( https://reactos.org/wiki/Google_Summer_of_Code_2018_Ideas#Website) but still can be improved though :)
- (lower priority) AppDB similar to Wine's. This can potentially lower our effort on maintaining Jira tickets. There is already one such thing from our community: https://github.com/ROS-AppDB/ReactOS-AppDB Maybe we should think about supporting it officially
Feel free to add&correct this list!
2. Jira tickets workflow. It looks like don't follow our own convention regarding issues workflow in Jira. According to scheme every new ticked is created with UNTRIAGED status and supposed to be moved to OPEN or RESOLVED state by someone from Devs. But nobody does it for a while and there is no easy way to distinguish "accepted" tickets from others.
I think we should return back to following this scheme or create a new one if this is not convenient.
Cheers, Victor Perevertkin
сб, 24 нояб. 2018 г., 23:38 Colin Finck colin@reactos.org:
Hi all!
Let me invite you to the November 2018 meeting, taking place next Thursday, November 29, 2018 at 19:00 UTC. Invited members will again receive their credentials shortly before the meeting.
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
Best regards,
Colin
Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev
Am 24.11.2018 um 21:37 schrieb Colin Finck:
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
The current agenda is as follows:
1. Status Reports since August (everyone) ====================================== Please prepare your Status Reports now, so we get this done quickly.
2. Web and Infrastructure Projects (Victor P. and Colin) ===================================================== In particular: - Updated developer web interface (Victor P.) - AppDB similar to Wine's (Victor P. and Colin) - BuildBot (Victor P. and Colin) - New website (Colin) - Mattermost (Colin) - Nextcloud (Colin)
3. Jira tickets workflow (Victor P.) =================================
4. ReactOS 0.5 Planning (everyone) =============================== - From a user perspective (i.e. what shall work?) - From a technical perspective (i.e. who needs to implement what components?)
I don't think anybody has already prepared a detailed plan, so we should collect our ideas and expectations for a 0.5 release and write them down at https://reactos.org/wiki/0.5_Planning Let's also try to define responsible persons and timeframes for each task, otherwise a plan is useless.
5. ReactOS Deutschland e.V. Update and ReactOS Hackfest(s) 2019 (Colin) ==================================================================== Will just give a quick update on the German foundation as we will have a General Assembly in 2 weeks and reelect all Board members. Also a quick survey if it makes sense to have 2 Hackfests each year and your preferred dates for that.
6. All-in-one ISOs combining Live-CD and GUI Installer (Hermes) ============================================================ Will only be discussed if Hermes is present.
7. Miscellaneous (everyone) ======================== If you disagree with me excluding a topic from the agenda, we can discuss it here.
In my opinion, "Selecting a new coordinator" makes no sense as long as nobody announces to spend significantly more time on ReactOS and comes up with a clear vision for the project, just like an election program. Otherwise, a new coordinator cannot really make a difference and we can just leave the situation as is. "USB / Storage" was merged with 0.5 Planning. "Wine Syncs" will or will not be a topic depending on the presence of Amine Khaldi. We can probably discuss it shortly as part of his Status Report.
This may look like a tough schedule, however as many points depend on me, I'll do my best to prepare my statements and get this done quickly. All of you, please do the same. This should hopefully give us enough time for 0.5 Planning.
See you this evening!
Colin
let me add a last topic: website translations
Old website could be translated, current one can not. And i think its good for the final user to see the webpage in his/her own language...
On Thu, Nov 29, 2018 at 10:40 AM Colin Finck colin@reactos.org wrote:
Am 29.11.2018 um 10:28 schrieb Colin Finck:
Web and Infrastructure Projects (Victor P. and Colin)
Addendum to these:
- Community.ReactOS.org (Colin)
- Doxygen (Colin)
Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev
Am 29.11.2018 um 11:05 schrieb Javier Agustìn Fernàndez Arroyo:
let me add a last topic: website translations
Old website could be translated, current one can not. And i think its good for the final user to see the webpage in his/her own language...
I agree and this is one of the reasons why we chose Hugo for the new website.
While there is no reason to translate technical developer content on the Wiki, the website is geared towards the end-user and should be available in multiple languages to account for our international community.
I don't think we need to put this on the agenda of today's meeting, but I can reaffirm this during my report about the new website.
- Colin
I don't think anybody has already prepared a detailed plan, so we should collect our ideas and expectations for a 0.5 release and write them down at https://reactos.org/wiki/0.5_Planning
There is already page for 0.5 - https://reactos.org/wiki/0.5.0
On Thu, Nov 29, 2018 at 12:28 PM Colin Finck colin@reactos.org wrote:
Am 24.11.2018 um 21:37 schrieb Colin Finck:
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
The current agenda is as follows:
Status Reports since August (everyone)
Please prepare your Status Reports now, so we get this done quickly.
Web and Infrastructure Projects (Victor P. and Colin)
In particular:
- Updated developer web interface (Victor P.)
- AppDB similar to Wine's (Victor P. and Colin)
- BuildBot (Victor P. and Colin)
- New website (Colin)
- Mattermost (Colin)
- Nextcloud (Colin)
Jira tickets workflow (Victor P.)
ReactOS 0.5 Planning (everyone)
- From a user perspective (i.e. what shall work?)
- From a technical perspective (i.e. who needs to implement what components?)
I don't think anybody has already prepared a detailed plan, so we should collect our ideas and expectations for a 0.5 release and write them down at https://reactos.org/wiki/0.5_Planning Let's also try to define responsible persons and timeframes for each task, otherwise a plan is useless.
ReactOS Deutschland e.V. Update and ReactOS Hackfest(s) 2019 (Colin)
Will just give a quick update on the German foundation as we will have a General Assembly in 2 weeks and reelect all Board members. Also a quick survey if it makes sense to have 2 Hackfests each year and your preferred dates for that.
All-in-one ISOs combining Live-CD and GUI Installer (Hermes)
Will only be discussed if Hermes is present.
Miscellaneous (everyone)
If you disagree with me excluding a topic from the agenda, we can discuss it here.
In my opinion, "Selecting a new coordinator" makes no sense as long as nobody announces to spend significantly more time on ReactOS and comes up with a clear vision for the project, just like an election program. Otherwise, a new coordinator cannot really make a difference and we can just leave the situation as is. "USB / Storage" was merged with 0.5 Planning. "Wine Syncs" will or will not be a topic depending on the presence of Amine Khaldi. We can probably discuss it shortly as part of his Status Report.
This may look like a tough schedule, however as many points depend on me, I'll do my best to prepare my statements and get this done quickly. All of you, please do the same. This should hopefully give us enough time for 0.5 Planning.
See you this evening!
Colin
Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev
Mails have been sent and IRC server started. Please check your inboxes and join!
See you at 19:00 UTC
Colin
Am 24.11.2018 um 21:37 schrieb Colin Finck:
Hi all!
Let me invite you to the November 2018 meeting, taking place next Thursday, November 29, 2018 at 19:00 UTC. Invited members will again receive their credentials shortly before the meeting.
This will be the first meeting since August and I hope we get some more topics than just the obligatory Status Reports. Please send your proposals by replying to this mail.
Best regards,
Colin
Ros-dev mailing list Ros-dev@reactos.org http://reactos.org/mailman/listinfo/ros-dev