From Fedora Project Wiki
(Add filtered mirrors task)
 
(20 intermediate revisions by 7 users not shown)
Line 13: Line 13:
! Owner
! Owner
|-
|-
| testing additional repositories  
| testing additional repositories
| Playground repo  
| Playground repo  
| [https://fedoraproject.org/wiki/Changes/Playground_repository]
| [https://fedoraproject.org/wiki/Changes/Playground_repository]
| F-22
| F-22
| [https://bugzilla.redhat.com/show_bug.cgi?id=1107529 obs-signd],  
| [https://bugzilla.redhat.com/show_bug.cgi?id=1107529 obs-signd],  
tests for automatic inclusion into repo (Taskotron),  
[https://fedoraproject.org/wiki/User:Hhorak/Draft/task-rpmgrill-copr tests for automatic inclusion into repo (Taskotron)],  


stats of downloads
stats of downloads
Line 52: Line 52:
| msuchy
| msuchy
|-
|-
| Software Collections in Fedora
| [[Env_and_Stacks/Projects/SoftwareCollectionsInFedora|Software Collections in Fedora]]
| SCL
| SCL
| [https://fedoraproject.org/wiki/Changes/SCL]
| [https://fedoraproject.org/wiki/Changes/SCL]
| F-21?
| F-24?
| [https://fedorahosted.org/fpc/ticket/339#comment:50 FPC ticket]
| [https://fedorahosted.org/fpc/ticket/339#comment:50 FPC ticket], new proposal needed
| [https://www.softwarecollections.org/ upstream] location of SCLs
| [https://www.softwarecollections.org/ upstream] location of SCLs
|
|
| mmaslano
| hhorak
|-
|-
| DevAssistant
| DevAssistant
Line 75: Line 75:
|
|
|
|
| [http://msimacek.fedorapeople.org/koschei/ koschei]
| [[Koschei]]
[http://copr.fedoraproject.org/coprs/churchyard/python3-nightly/ python-nightly]
[http://copr.fedoraproject.org/coprs/churchyard/python3-nightly/ python-nightly]


Line 84: Line 84:
| Docker
| Docker
|  
|  
| F-21?
| F-22+
|  
| https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
| We could have layered images for different stacks (e.g. LAMP), see https://github.com/fedora-cloud/Fedora-Dockerfiles
| We could have layered images for different stacks (e.g. LAMP), see https://github.com/fedora-cloud/Fedora-Dockerfiles
|
|
Line 97: Line 97:
| Build package(s), create layered image, pull image, run container
| Build package(s), create layered image, pull image, run container
|
|
| sicampbell
|
|-
|-
| Continuous Integration
| Continuous Integration
| rpmgrill
| rpmgrill
|
|
| F-22
| F-23
|  
|  
| We need to integrate rpmgrill into Taskotron as one of the tests
| We need to integrate rpmgrill into Taskotron as one of the tests
| [https://phab.qadevel.cloud.fedoraproject.org/T281 Fedora QA issue]
| hhorak
|-
| Continuous Integration
| [[Env_and_Stacks/Projects/FunctionalAndIntegrationTests|Functional tests that cannot be run during build]]
|
|
| F-23
|
| Idea behind this task is basically just define a place for such tests and at least some few guidelines or best practices how the tests would be called.
|
| hhorak
| hhorak
|-
|-
Line 113: Line 122:
| F-22 ?
| F-22 ?
|
|
| Set up a filtered miror for PyPI to make Fedora wheels available and to split license review from repackaging
| [[Env_and_Stacks/Projects/LanguageSpecificRepositories]] [[User:Mizdebsk/FedoraMavenRepository]]
|
|
| bkabrda, ncoghlan
| bkabrda, ncoghlan
|-
| mapping CVEs to Docker images that need rebuilding
| Docker
|
| F-22/23
|
| we do not need to solve the CVE vs. layered image for now, as we are going to ship Docker files first, but it will come up in the future
|
| vpavlin/sochotni
|-
| [[User:Hhorak/Draft/task-dockerfile-rules|Dockerfiles recommended tips]]
| Docker
|
| F-23
|
| we need to have recommended practices documented on the wiki (or somewhere else?), so people interested in writing their own dockerfiles have enough information
|
| phracek
|-
| [[Env_and_Stacks/Projects/DeveloperPortal|Developer portal]]
| Documentation
| [https://developer.fedoraproject.org/]
| F-23
|
| we want to provide a software developer focused entry point into Fedora technologies, current content: https://github.com/developer-portal/content
|
| phracek,ncoghlan
|}
|}

Latest revision as of 09:35, 25 November 2015

Tasklist

This document track status of projects developer or co-operated. Feel free to contact us on the mailing list or directly contact owner features. Another possibility is work on bugzillas related to features.

Area Feature Fedora Change Aim Blockers Comment What do to Owner
testing additional repositories Playground repo [1] F-22 obs-signd,

tests for automatic inclusion into repo (Taskotron),

stats of downloads

Playground plugin is similar to Copr plugin [2] mmaslano
automation Automated packages review tools [3] F-22 ? design of the whole thing, only parts are ready pingou
automation Taskotron F-22 ? development plan tflink
Build Systems Copr upstream F21 bz msuchy
Software Collections in Fedora SCL [4] F-24? FPC ticket, new proposal needed upstream location of SCLs hhorak
DevAssistant [5] F-21 bkabrda
Continuous Integration prototype of few projects Koschei

python-nightly

bkabrda
Layered Docker images Docker F-22+ https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service We could have layered images for different stacks (e.g. LAMP), see https://github.com/fedora-cloud/Fedora-Dockerfiles vpavlin
Docker integration with copr Docker F-22 Build package(s), create layered image, pull image, run container
Continuous Integration rpmgrill F-23 We need to integrate rpmgrill into Taskotron as one of the tests Fedora QA issue hhorak
Continuous Integration Functional tests that cannot be run during build F-23 Idea behind this task is basically just define a place for such tests and at least some few guidelines or best practices how the tests would be called. hhorak
Language specific filtered mirrors devpi (pilot) F-22 ? Env_and_Stacks/Projects/LanguageSpecificRepositories User:Mizdebsk/FedoraMavenRepository bkabrda, ncoghlan
mapping CVEs to Docker images that need rebuilding Docker F-22/23 we do not need to solve the CVE vs. layered image for now, as we are going to ship Docker files first, but it will come up in the future vpavlin/sochotni
Dockerfiles recommended tips Docker F-23 we need to have recommended practices documented on the wiki (or somewhere else?), so people interested in writing their own dockerfiles have enough information phracek
Developer portal Documentation [6] F-23 we want to provide a software developer focused entry point into Fedora technologies, current content: https://github.com/developer-portal/content phracek,ncoghlan