env-and-stacks February 2014

env-and-stacks@lists.fedoraproject.org

20 participants
19 discussions

System Wide Changes
by Marcela Mašláňová 05 Mar '14

05 Mar '14

Hi, I thought we could prepare all our goals as system wide changes and some could be left out for addition in next Fedora if we can't make it. We discussed only additional repo and SCL, but other goals can be also prepared by people from our group even if we didn't discuss it yet. For example Reviews or Taskotron don't depend on small group going to meetings. Do you want to pick tasks and start working on proposals right now or discuss everything on meetings? Marcela

3 4

Playground Repo Requirements Document
by Toshio Kuratomi 05 Mar '14

05 Mar '14

Okay, I started a requirements document for the playground repository: https://fedoraproject.org/wiki/Env_and_Stacks/Playground_repository_%28draf… There's three things that we need to do with this to make it useful for FESCo: 1) Add other things we need to decide on to the Open Questions. We especially need things that will affect the work needed to implement the repository but we can decide which things those are later. 2) Decide which features from the Open Questions we want to apply to the Playground repository. Update the description section as we make decisions. 3) Analyze what will be needed to implement the features we've decided the Playground repository needs to have and fill in the Identified Needs sections with that information. -Toshio

9 24

Git for Copr
by Bohuslav Kabrda 03 Mar '14

03 Mar '14

Hi all, at last Env and Stacks WG meeting I've promised to talk to Mirek Suchy, Copr maintainer, about providing sort-of-dist-git (*), perhaps with a web interface, for Copr. The result of the discussion from Mirek's side is, that he's ok with it as long as he doesn't have to do it, since he's fully occupied with Copr. Also, Copr should still provide the option to build packages as it does now, e.g. sort-of-dist-git should be just a frontend application (not part of Copr), not really something that would be tied directly into Copr. However, few other people also joined the discussion and the responses to this idea were more like: - Why do we want to do this? This seems to be like creating Koji from Copr. Copr should remain lightweight. - Why would we need web interface? People don't need/want it. - If we really need web interface, why don't we utilize fedorahosted.org? - Why don't we just allow people to utilize any git (private git repo, git hosting like Github) and provide just tool that would allow users to do "copr build" and it would work automatically (actually it seems that Tito already knows how to do this [1]). My opinion on this is: - Utilizing git for tracking changes is important for example for the "fedora-ugly" idea, where we would like to easily track/view specfile history. - Having a single central place for git repos and offering it to Fedora contributors to use would be a nice addition. Utilizing fedorahosted.org for this usecase might be nice and we could reuse what we already have (although personally I find fedorahosted user experience pretty clumsy). - At the very least, we could extend the Tito Copr releaser to add some sort of meta-tag to specfile (someone mentioned that this should be possible) containing git url and hash. This way, we would be able to track the repo that srpm came from and the commit hash - again, this would improve the experience for potential contributors, who would be able to easily find where to send pull requests/patches. Overall, I think this would improve Copr user experience and soften the sharp edges that might otherwise scare potential Fedora contributors. Also, having git repos would IMO significantly improve the possibilities of collaboration and tracking - compared to throwing bunch of srpms into Copr by hand. I don't think that we necessarily need to provide the hosting for this, but we should definitely provide a howto guide that would describe how to _easily_ achieve this with e.g. Github/Bitbucket repos and so on. Again, we should show an easy way for potential contributors, who may enter Fedora by building in Copr. Regards, Slavek. (*) By sort-of-dist-git, I mean a place for git repos that would hold specfiles/patches, etc., e.g. what Fedora's dist-git holds, but possibly without the lookaside cache... Details to be discussed. [1] http://miroslav.suchy.cz/blog/archives/2013/12/29/how_to_build_in_copr/inde…

6 10

PRDs/Tech Specs to formal Change Proposals and Change submission deadline
by Jaroslav Reznik 27 Feb '14

27 Feb '14

Hi, at yesterday's FESCo meeting, it was agreed on setting deadlines for Change submission for Fedora 21 [1] and to process PRDs into Change proposals. "AGREED: Fedora Changes Process submission deadline for system-wide changes is April 7th. Deadline for true standalone changes will be sometime later than that. Changes to how fedora is produced for fedora.next are still due on March 3rd. (+7,0,0) (nirik, 18:29:42)" Current deadlines: * March 3rd: Technical Specifications for products & and changes needed for products and deliverables --- very soon! * April 7th: System Wide Changes submission deadline Working Groups teams, please, try to "transform" required changes for your products from PRDs/Technical Specifications into standalone Change proposals (between March 3rd and April 7th). It will help us to scope the release. Also all changes would be trackable the standard way we do it and it's going to help transparency (as Change announcements are being to be part of the process). Self Contained Changes submission deadline will be set later, after the System Wide deadline. If you expect your proposed Self Contained Change will be on the edge and could be escalated to the System Wide, please try to submit it as early as possible too. As some Fedora.next details will be clarified later in the process, System Wide Changes submitted after the deadline will be approved case by case, even after submission deadline. For the details about the Change process, see my previous email to the devel announce list [2]. Thank you for your help with Change process and let me know in case of any questions. Jaroslav [1] https://fedorahosted.org/fesco/ticket/1178 [2] https://lists.fedoraproject.org/pipermail/devel-announce/2014-February/0013…

1 0

Agenda for Env-and-Stacks WG meeting (2014-02-25)
by Marcela Mašláňová 26 Feb '14

26 Feb '14

WG meeting will be at 16:00 UTC in #fedora-meeting on Freenode. == Topic == # additional repository fedora-{incubator,ugly} * better name than ugly based on content of repo * github-like frontend for copr * discuss policies/procedures for accepting copr repo #SCL in Fedora * base on needs for products * FPC - what's needed now See you tomorrow, Marcela

3 4

Re: env-and-stacks post from drago01@gmail.com requires approval
by Honza Horak 25 Feb '14

25 Feb '14

I'm actually not sure why we do have a policy to allow everybody new explicitly, is there any reason for that or shouldn't we rather open the mailing list for every-one? Another point for today's talk? Honza On 02/24/2014 08:57 PM, env-and-stacks-owner(a)lists.fedoraproject.org wrote: > As list administrator, your authorization is requested for the > following mailing list posting: > > List: env-and-stacks(a)lists.fedoraproject.org > From: drago01(a)gmail.com > Subject: Re: Agenda for Env-and-Stacks WG meeting (2014-02-25) > Reason: Post by non-member to a members-only list > > At your convenience, visit: > > https://lists.fedoraproject.org/mailman/admindb/env-and-stacks > > to approve or deny the request. >

3 3

Summary/Minutes from today's Env-and-Stacks WG meeting (2014-02-18)
by Bohuslav Kabrda 24 Feb '14

24 Feb '14

============================================= #fedora-meeting: Env and Stacks (2014-02-18) ============================================= Meeting started by bkabrda at 13:02:21 UTC. The full logs are available at http://meetbot.fedoraproject.org/fedora-meeting/2014-02-18/env-and-stacks.2… . Meeting summary --------------- * init process (bkabrda, 13:03:08) * additional repository - fedora-{incubator,ugly} (bkabrda, 13:05:15) * AGREED: only one repo should be created at the start (mmaslano, 13:37:55) * does malware automatic check exist? (mmaslano, 13:52:20) * ACTION: bkabrda will talk to msuchy about his thoughts on providing github-like frontend for copr (implement in copr itself vs. do it as a standalone app) and post discussion result on our mailing list (bkabrda, 14:30:18) * ACTION: all: discuss policies/procedures for accepting copr repo into "fedora-ugly" on our ML (bkabrda, 14:33:41) * ACTION: all: propose better names for "fedora-ugly" on our ML (bkabrda, 14:35:14) Meeting ended at 14:42:05 UTC. Action Items ------------ * bkabrda will talk to msuchy about his thoughts on providing github-like frontend for copr (implement in copr itself vs. do it as a standalone app) and post discussion result on our mailing list * all: discuss policies/procedures for accepting copr repo into "fedora-ugly" on our ML * all: propose better names for "fedora-ugly" on our ML Action Items, by person ----------------------- * bkabrda * bkabrda will talk to msuchy about his thoughts on providing github-like frontend for copr (implement in copr itself vs. do it as a standalone app) and post discussion result on our mailing list * **UNASSIGNED** * all: discuss policies/procedures for accepting copr repo into "fedora-ugly" on our ML * all: propose better names for "fedora-ugly" on our ML People Present (lines said) --------------------------- * juhp (112) * mmaslano (71) * tjanez (71) * bkabrda (49) * pingou (35) * samkottler (27) * hhorak (26) * jreznik (25) * zodbot (5) * handsome_pirate (2) * abadger1999 (0) * pkovar (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

5 6

Meeting logs accessible easily now
by Honza Horak 24 Feb '14

24 Feb '14

Hi there, it wasn't very convenient to seek for logs from our meetings for me, since I always had to either go through mailing list or through all possible dates at http://meetbot.fedoraproject.org/fedora-meeting So I created a script that generates a list of our meetings and placed the list here: https://fedoraproject.org/wiki/Env_and_Stacks/Meeting_Logs I'll try to keep this page updated but if anybody has idea how to edit the wiki automatically somehow easily, I'm open to Regards, Honza

3 4

Env and Stacks wiki has been updated
by Deborah Rieden 18 Feb '14

18 Feb '14

Hello, I finally had some time to work on the Environment and Stacks wiki [1]. I organized it similar to some of the other Fedora.Next wikis. If you have any comments, please let me know. If something is not correct, please feel free to update it. [1] https://fedoraproject.org/wiki/Env_and_Stacks Thanks! Debi -- Debi Rieden Engineering Program Manager (Developer Toolset (DTS), Software Collections (RHSCL), LPC Pilot and some other projects), Fedora Environment and Stacks Working Group Westford (2S719) Office: 978-392-1023; Cell 617-669-2934 drieden(a)redhat.com #devtoolset, #boston, #software-collections, #fedora-stacks

3 3

Agenda for Env-and-Stacks WG meeting (2014-02-18)
by Marcela Mašláňová 17 Feb '14

17 Feb '14

WG meeting will be at 13:00 UTC in #fedora-meeting on Freenode. == Topic == # additional repository fedora-{incubator,ugly} * prepare proposal for additional repository based on discussion from mailing list https://lists.fedoraproject.org/pipermail/env-and-stacks/2014-February/0001… https://lists.fedoraproject.org/pipermail/devel/2014-February/195483.html We can change proposal if we receive more input from other WG. #SCL in Fedora Speak with Server and Cloud - what do they need. FPC - what's needed now See you tomorrow, Marcela

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

env-and-stacks February 2014