{{#fedoradocs: https://docs.fedoraproject.org/fedora-project/council/fpl.html}}
+From 176f1b20a5609301253b28b6120e1f4458a60d71 Mon Sep 17 00:00:00 2001
From: Brian (bex) Exelbierd ASP.NET Core web application for /r/Fedora subreddit and Discord. Atomic IoT (likely useful in numerous other Atomic ideas) host upgrade daemon Fedora Dockerfile linter leveraging Container Best Practices Advanced test cases for images running in OpenShift using conu
Technology : Java, Android, Experience with REST APIs, Android Studio, etc
Mentors: Kanika Murarka, [https://fedoraproject.org/wiki/User:Sumantrom]Sumantro Mukherjee
+Mentors: Kanika Murarka, Sumantro Mukherjee
Fedora has an android app which lets a user to browse Fedora Magazine, Fedora Ask, Fedocal etc within it. However, most of the functions rely on an in-app browser to render content and requires speed optimization and native integration. As a SoC intern, you will be responsible for the following :
+Fedora has an android app which lets a user to browse Fedora Magazine, Fedora Ask, Fedocal etc within it. However, most of the functions rely on an in-app browser to render content and requires speed optimization and native integration. As a Summer of Code intern, you will be responsible for the following :
Replace web views and build a more native Android experience like Immersive view, etc.
+Replace web views and build a more native Android experience like immersive mode, etc.
Fully functional Android app
@@ -349,7 +365,6 @@ using the new method.Technology : Python, More Python, Understanding of data processing, Python libraries
Mentors : Sachin S. Kamath, Justin W. Flory
+Mentors : Sachin S. Kamath (skamath), Justin W. Flory (jwf)
During the course of the project, you will be closely working with the Fedora Community Operations (CommOps) Team to build a metrics dashboard for the community. For building the dashboard, we will be using Grimoirelab suite of tools to build the backend as well as the frontend.
Perceval is a tool that collects data from a given data source and has a lot of pre-defined plugins. The aim of this project is to add fedmsg support to it so that metrics can be pulled out of it, suitable for the Fedora community.
+Perceval is a tool that collects data from a given data source and has a lot of pre-defined plugins. The aim of this project is to add fedmsg support to it so that metrics can be pulled out of it, suitable for the Fedora community.
Primary Objectives:
+A plugin for perceval to pull metrics from fedmsg directly
Documentation for the plugin
+Secondary Objectives: +- Additional plugins to support Wordpress, Twitter and other data sources
+Pagure is a git-centered forge, python based using pygit2.
+With pagure you can host your project with its documentation, let your users report issues or request enhancements using the ticketing system and build yourcommunity of contributors by allowing them to fork your projects and contributeto it via the now-popular pull-request mechanism.
@@ -425,7 +450,7 @@ Applicants interested in Pagure must contribute by solvingHomepage: https://pagure.io/pagure
+Repo: https://pagure.io/pagure
Issues: https://pagure.io/pagure/issues
@@ -433,7 +458,7 @@ Applicants interested in Pagure must contribute by solvingProjects in Pagure will be selected by the student in concert with the mentor. They will be drawn from the non-easyfix issues in the issue queue. Students are expected to guide the mentor in htelping them select areas of interest.
+Projects in Pagure will be selected by the student in concert with the mentor. They will be drawn from the non-easyfix issues in the issue queue. Students are expected to guide the mentor in helping them select areas of interest.
Skill level: Intermediate
+Skills required: Python, containers
+Mentor(s): Tomas Tomecek, Eliska Slobodova
+Contacts (IRC & email): ttomecek (ttomecek @redhat.com), eslobodo (eslobodo @redhat.com)
+Fedora infrastructure for container image delivery is lacking any kind of automated testing of the images or underlying Dockerfiles. The Container Best Practices document is a digest of recommended practices for writing and deploying images.
+With Container Best Practices serving as a “cheatsheet”, you will create a tool to perform basic and advanced checks on Dockerfiles and images that can be applicable generally regardless of an image. In cooperation with the Fedora infrastructure team, you will deploy the tool in the container infrastructure so that the tests can be executed automatically upon a new build/commit or locally before the developer pushes the changes remotely.
+Skill level: Intermediate
+Skills required: Python, containers, OpenShift
+Mentor(s): Tomas Tomecek, Dominika Hodovska
+Contacts (IRC & email): ttomecek (ttomecek @redhat.com), dhodovsk (dhodovsk @redhat.com)
+Conu is a library which provides Python API to interact with a selected container runtime. It simplifies writing of tests for container images. However, the project currently lacks support for OpenShift.
+Your primary goal will be to deliver at least 10 new functions that will enable the users to write tests for OpenShift scenarios.
+Your secondary goal will be to write test for at least 5 images (eg mariadb, mysql, postgresql, golang, rust) using conu’s full capabilities.
+Skill level: Intermediate - Expert
+Skills required: python, containers
+Mentor(s): Tomas Tomecek
+Contacts (IRC & email): ttomecek (ttomecek @redhat.com)
+conu defines a generic API to interact with containers and container engines. To make the project more usable, we would like add implementation of another container runtimes, such as Container Runtime Interface (see the Kubernetes blog post and the Github repo) of Kubernetes project. CRI is a generic interface defined by Kubernetes project which container engines need to implement in order to communicate with Kubernetes. Adding implementation for this interface into conu project will make it easy for conu users to interact with variety of container runtimes and perform operations which would be executed inside Kubernetes.
+In addition to the above list of ideas, you may want to check out ideas diff --git a/quick-docs/en-US/index.html b/quick-docs/en-US/index.html index 83f3dee..0f9aaa9 100644 --- a/quick-docs/en-US/index.html +++ b/quick-docs/en-US/index.html @@ -123,7 +123,9 @@
This repository represents asciidoc documents roughly (semi-automatically) converted from the top 50 @@ -134,9 +136,11 @@ format with a PR-based workflow.
So, this is kind of a seed project. Your help wanted!
Please:
Make your changes to the .adoc
file you want to improve.
Update _topic_map.yml
to remove "(FIX ME!)
"
Update _topic_map.yml
to remove “(FIX ME!)”
Submit a pull request with your improvements.
Update the original wiki page with {{old}}
and a link to the shiny new document
Create a redirect on the old wiki page — see below.
Usually, wikis do not allow redirects to external sites, because the
+potential for abuse is very high. We’ve developed a plugin for the Fedora
+Wiki which allows redirects to only pages on this site,
+https://docs.fedoraproject.org/. To create such a link, use the
+#fedoradocs
macro by putting something like this at the top of the wiki
+page you are obsoleting:
{{#fedoradocs: https://docs.fedoraproject.org/fedora-project/council/fpl.html}}
+Of course, you will want to replace that specific URL with the one for your
+new target page. The URL can’t be something arbitrary — it must begin with
+https://docs.fedoraproject.org/
.
Once the redirect is in place, visitors to that wiki page will be instantly
+whisked (well, redirected, with the code 301 Moved Permanently
) to the
+docs site. If you need to edit such a page to correct the URL, or to remove
+the redirect completely, use a form like:
+https://fedoraproject.org/w/index.php?title=Project_Leader&action=edit
Note that there is no validation that the target exists or is correct — +please double-check that any redirects you create work properly before +moving on.
+