<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Tasks<br><div><br></div>Those who can't attend the meeting should comment the draft on mailing <br>list. The deadline for document is next Monday (20th January).</blockquote><div>Thanks - I am afraid I won't be able to attend tonight's late meeting (in my timezone),</div><div>so let me post some comments on the current draft here.</div><div><br></div><div>Overall I feel the document is good and sets a good direction for the WG.</div><div>I added a small user story for developers needs multiple development environments</div><div>for different projects with different build requirements. Probably more details</div><div>and examples could be added.</div><div><br></div><div>I just have some minor queries/comments about some parts/sentences:</div><div><p style="padding-left: 60px;"><span style="font-size: 12pt;">* QA automation</span></p><p style="padding-left: 60px;">** Join the [[QA|Fedora QA]] and help them with the [[User:Tflink/taskotron_development_plan|Taskotron]] project concerning the future of QA automation in Fedora.<br>** Develop new tools for Fedora QA that will help achieving high standards of software in Fedora.<br>*** An example of such a tool is [https://git.fedorahosted.org/git/rpmgrill.git rpmgrill], a set of analysis tests that run against a particular RPM build. Its main difference to [[Common_Rpmlint_issues|rpmlint]] is that rpmgrill handles *builds*, that is, the entire sets of RPMs built from one source RPM file instead of single RPM files. <span style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 0);">As soon as it is ready for deployment, it should be introduced to Fedora QA.</span></p><p style=""><span style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 0);"><span data-mce-bogus="1" style=""><span style="background-color: rgb(255, 255, 255);">Is this sentence needed? Does it just mean "QA can start using it as soon as it is ready." or something more?</span></span></span></p><p style="padding-left: 60px;">=== Build systems ===<br>* COPR & koji<br>** COPR able to build an SCL<br>** koji - a number of improvements for developers (<span style="background-color: rgb(255, 255, 0);">buildlogs</span>, etc.), in co-operation with the koji upstream.</p><p style="">What about buildlogs??</p><p style="">I need to look at COPR again, but I wonder if it is worth looking at the features of OBS and seeing if there is any low-hanging fruit that we could steal^Wbring to Fedora too?</p><p style="padding-left: 60px;"><span style="font-size: 12pt;">=== Documentation, guidelines ===</span></p><p style="padding-left: 60px;"><span style="font-size: 12pt;">=== DevAssistant ===</span></p><p style=""><span style="font-size: 12pt;">I kind of wondered if these two are not slightly out of scope but I guess it is fine to include them if people in the WG are planning to work on them this year.</span></p><p style=""><span style="font-size: 12pt;">Thanks, Jens</span></p><p style="padding-left: 60px;"></p></div></div></body></html>