WG meeting will be at 16:00 UTC in #fedora-meeting on Freenode.
== Topic == https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Tasks
Those who can't attend the meeting should comment the draft on mailing list. The deadline for document is next Monday (20th January).
https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Tasks
Those who can't attend the meeting should comment the draft on mailing list. The deadline for document is next Monday (20th January).
Thanks - I am afraid I won't be able to attend tonight's late meeting (in my timezone), so let me post some comments on the current draft here.
Overall I feel the document is good and sets a good direction for the WG. I added a small user story for developers needs multiple development environments for different projects with different build requirements. Probably more details and examples could be added.
I just have some minor queries/comments about some parts/sentences:
* QA automation
** 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. ** Develop new tools for Fedora QA that will help achieving high standards of software in Fedora. *** 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. As soon as it is ready for deployment, it should be introduced to Fedora QA.
Is this sentence needed? Does it just mean "QA can start using it as soon as it is ready." or something more?
=== Build systems === * COPR & koji ** COPR able to build an SCL ** koji - a number of improvements for developers ( buildlogs , etc.), in co-operation with the koji upstream.
What about buildlogs??
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?
=== Documentation, guidelines ===
=== DevAssistant ===
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.
Thanks, Jens
On 01/14/2014 05:01 PM, Jens Petersen wrote:
https://fedoraproject.org/wiki/User:Mmaslano/Draft:Env_and_Stack_PRD#Tasks Those who can't attend the meeting should comment the draft on mailing list. The deadline for document is next Monday (20th January).
Thanks - I am afraid I won't be able to attend tonight's late meeting (in my timezone), so let me post some comments on the current draft here.
Overall I feel the document is good and sets a good direction for the WG. I added a small user story for developers needs multiple development environments for different projects with different build requirements. Probably more details and examples could be added.
I just have some minor queries/comments about some parts/sentences:
- QA automation
** 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. ** Develop new tools for Fedora QA that will help achieving high standards of software in Fedora. *** 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. As soon as it is ready for deployment, it should be introduced to Fedora QA.
Is this sentence needed? Does it just mean "QA can start using it as soon as it is ready." or something more?
=== Build systems ===
- COPR & koji
** COPR able to build an SCL ** koji - a number of improvements for developers (buildlogs, etc.), in co-operation with the koji upstream.
What about buildlogs??
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?
=== Documentation, guidelines ===
=== DevAssistant ===
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.
Thanks, Jens
env-and-stacks mailing list env-and-stacks@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/env-and-stacks
I guess we mainly agreed with you on the meeting.
Marcela
Hi!
On Tue, 2014-01-14 at 11:01 -0500, Jens Petersen wrote:
I just have some minor queries/comments about some parts/sentences:
- QA automation
As soon as it is ready for deployment, it should be introduced to Fedora QA.
Is this sentence needed? Does it just mean "QA can start using it as soon as it is ready." or something more?
I removed the sentence.
=== Build systems ===
- COPR & koji
** COPR able to build an SCL ** koji - a number of improvements for developers (buildlogs, etc.), in co-operation with the koji upstream.
This section has been reworded and expanded, please see the PRD.
Regards, Tadej
=============================================== #fedora-meeting: env and stacks wg (2014-01-14) ===============================================
Meeting started by mmaslano at 16:04:30 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-01-14/env_and_stacks.20... .
Meeting summary --------------- * init process (mmaslano, 16:08:53) * AGREED: add tjanez vission and mission statement (+7,-0,0) (mmaslano, 16:21:13) * ACTION: tjanez will add section about vision and mission statement (mmaslano, 16:22:00) * schedule will contain dates, not the actual PRD (mmaslano, 16:37:52) * ACTION: abadger1999 to send out RFC about the SCL direction (abadger1999, 17:36:26)
Meeting ended at 17:47:34 UTC.
Action Items ------------ * tjanez will add section about vision and mission statement * abadger1999 to send out RFC about the SCL direction
Action Items, by person ----------------------- * abadger1999 * abadger1999 to send out RFC about the SCL direction * tjanez * tjanez will add section about vision and mission statement * **UNASSIGNED** * (none)
People Present (lines said) --------------------------- * abadger1999 (48) * tjanez (48) * mmaslano (33) * hhorak (23) * pkovar (15) * drieden (15) * jwb (8) * zodbot (6) * samkottler (3) * pkovar1 (1) * pingou (1) * bkabrda (0) * juhp (0) * handsome_pirate (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
env-and-stacks@lists.fedoraproject.org