- What's GCI?

- ~~~~~~~~~~

- Google Code-in (GCI) is an annual programming competition hosted by Google Inc. that allows pre-university students to complete tasks specified by various, partnering open source organizations. The contest was originally the Google Highly Open Participation Contest, but in 2010, the format was modified into its current state. Students that complete tasks win certificates and T-shirts. Each organization also selects two grand prize award winners who will earn a trip to Google's Headquarters located in Mountain View, California.

- Task Themes

- ~~~~~~~~~~~

- Current Mentors

- ~~~~~~~~~~~~~~~

- Org Admins

- ~~~~~~~~~~

- * Bex 

- Task List

- ~~~~~~~~~

- * Dave Arter <davea@sucs.org> - user backups (work in progress is at

- https://sucs.org/~davea/trac/)

- * Mateusz Berezecki <mateuszb@gmail.com> - atheros driver:

- http://www.ath-driver.org/

- * Other items on the

- http://git.fedorahosted.org/git/mirrormanager?p=mirrormanager;a=blob;f=TODO;hb=HEAD[TODO

- list]

- 3.  Can pull sources from any version control system/stored tarballs to

- make a very upto-date package. (See blog entry for an example)

- * Bare mind - Remember to contact your mentor before you submit the

- application.

- |Notes | The rise of DevOps has been swift. Sysadmins are increasingly

- * Collaboration with Fedora Council and Leadership on Project Objectives

- and Initiatives

- * Effective Communication Skills; written and verbal, synchronous and

- asynchronous.

- * Experience writing for the web (Content only is ok, HTML/CSS even

- better)

- |Notes | Fedora has been in the process of creating a new web presence for all

- * Triaging and processing new widget ideas submitted by the community at

- large.

- * Implementing existing (and thoroughly detailed) mockups from previous

- UI/UX interns and team members.

- * Bonus: Experience with Bootstrap, jinja templates, Fedmsg,

- datanommer/grepper, or other fedora infrastructure projects a HUGE plus.

- |Notes |Pagure is a forge written in python and offering the possibility of

- * Participating in the effort to make of pagure the official front-end

- to Fedora's packages git repositories (currently being the read-only

- cgit)

- * Figuring out how/if pagure can be a front-end for Fedora's git repo

- now that they are namespaced (to offer more than just rpms, for example

- docker containers)

- * Effective Communication Skills; written and verbal, synchronous and

- asynchronous.

- * Implement ability for user to install flannel, etcd, and other

- bootstrap containers and manage them easily

- * New super-priv containers are accepted into planned design of Atomic

- Host

- * https://github.com/projectatomic/rpm-ostree/pull/107[Atomic Host

- package layering]: Improve the package layering design, support more

- RPMs, ensure %post scripts are safe, etc.]

- * https://github.com/projectatomic/rpm-ostree/issues/190[Bootstrap with

- gpgcheck in kickstart]: Add a way for importing a GPG key from the

- kickstart `ostreesetup` command before the download starts.

- https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/appe-kickstart-syntax-reference.html["ostreesetup"

- is described here]

- * https://github.com/projectatomic/rpm-ostree/issues/210[Improve ability

- to monitor running/canceled transactions]: The rpm-ostree client

- termination doesn't block the command execution on the rpm-ostreed. This

- will cause new rpm-ostree clients to fail immediately because there is a

- transaction in progress. Change rpm-ostree to be notified of the status

- of the current transaction and possibly attach to it.

- * Ability to create Virtual Machines (VMs) or have access to spare PC

- nearby for testing.

- * Ability for project to better understand transactions happening in the

- deamon

- * https://github.com/projectatomic/rpm-ostree/issues/142[Support for

- end-of-life notification]: Add support for having an `end-of-life`

- notification to inform users if a particular branch is not supported

- anymore.

- * rpm-ostree and atomic command output explaining when a version of an

- upgraded tree branch is end of life (EoL)

- * https://github.com/projectatomic/rpm-ostree/issues/85[rpm-ostree

- operation history support]: Add support for `atomic history` to display

- the transactions history. It should work in a similar way to `yum

- history`.

- * Duplication of support for history in the atomic command, similar to

- "yum history"

- * Strong command history and output on the system, possibly in systemd

- journal

- * https://bugzilla.gnome.org/show_bug.cgi?id=729388[Support metalink for

- OSTree]: Add support for metalink files and support downloads from a

- list of mirrors and fetch objects from multiple sources.

- * https://bugzilla.gnome.org/show_bug.cgi?id=730037[Drop privileges for

- HTTP fetches]: The HTTP fetcher code is running in the same process of

- OSTree. Move the HTTP fetcher code to another process with less

- privileges than the main process.

- * Main OSTree process communicates through Inter Process Communication

- (IPC) with fetcher process

- * https://github.com/projectatomic/rpm-ostree/issues/118[Support

- kpatch]: Support live update for the kernel without rebooting or

- restarting any processes.

- * https://github.com/projectatomic/rpm-ostree/issues/177: implement a

- service that automatically upgrades the system when a new image is

- available. If the system is not restarting correctly, the rollback to

- the previous working version.

- * Systemd provides timers for calendar time events and monotonic time

- events

- (http://www.freedesktop.org/software/systemd/man/systemd.timer.html,

- https://wiki.archlinux.org/index.php/Systemd/Timers). A major

- component of the Fedora Server is the Cockpit Project, a web-based

- management console for servers.

- * Some designs for timers in Cockpit exist at

- https://trello.com/c/1B2lZViZ/74-timers-and-cron.

- * A user of the Cockpit UI is able to view existing timers, edit

- existing ones or create new timers while providing the minimum set of

- necessary information to the UI

- * Functionality of added features is tested via unit and/or integration

- tests

- * Cockpit provides an interface for updating the installed software on

- Atomic systems using rpm-ostree. Admins should be able to examine the

- OSTree repos enabled on a machine, and add/edit/remove them via Cockpit.

- * A user of the Cockpit UI is able to examine the OSTree repos enabled

- on a machine, and add/edit/remove them.

- * Functionality of added features is tested via unit and/or integration

- tests

- * Cockpit provides an interface for updating the installed software on

- Atomic systems using rpm-ostree. Admins should be able to 'rebase' to a

- different operating system channel or timeline via Cockpit.

- * A user of the Cockpit UI is able to be able to 'rebase' to a different

- operating system channel or timeline via Cockpit.

- * Functionality of added features is tested via unit and/or integration

- tests

- * FreeIPA is a domain and directory server. This task implements a UI

- for setting it up.

- * The Rolekit Project provides a platform API for deploying Server Roles

- such as FreeIPA onto a system. Currently, it supports creating a Domain

- Controller (based on FreeIPA) or a Database Server (based on

- PostgreSQL). A major component of the Fedora Server is the Cockpit

- Project, a web-based management console for servers. The goal of this

- effort would be to enhance the Cockpit UI so that an administrator could

- deploy the FreeIPA role.

- https://trello.com/c/7CZqL9AQ/54-rolekit-integration-for-domain-controller.

- * A user of the Cockpit UI is able to deploy a Domain Controller while

- providing the minimum set of necessary information to the UI

- * The UI also provides a link post-deployment that allows the user to

- browse to the Domain Controller administration UI

- * Mentoring from seasoned sysadmins, veteran technical writers, and free

- software advocates.

- * Learning the Open Source Way, the practice of transparent positive

- collaboration that forms bedrock of Fedora's Foundations.

- * Learn some of the functions of 389 DS (account policy, plugin

- management).

- * Extend the python tools dsconf to support enabling / disabling /

- configuration of modules in Directory Server to replace our legacy

- tools.

- * Engineering principles expected of a project with high quality

- demands.

- * To teach you good community engagement, and engineering skills. The

- coding project is a means to help us teach you to interact effectively

- with a team, and to learn engineering principles.

- * Come and talk to wibrown on #389 in irc on freenode, or email our

- mailing list 389-devel@lists.fedoraproject.org

- * ASP.NET Core web application for our

- link:https://www.reddit.com/r/Fedora[/r/Fedora subreddit] to let the user

- choose a flair, based on their FAS Group memberships, written in C# and

- deployed on a Fedora production server as systemd service.

- * You will create and deploy an ASP.NET Core application on our Fedora

- production server as systemd service, with secure Apache in front of it.

- * .NET Standard library wrapping systemd, written in C# and published on

- NuGet.

- * By utilizing systemd, we can control various aspects of the system

- underneath directly from C# (eg. stopping or starting services,

- scheduling reboots)

- * _Persistent storage_. To explain how it works, I'll start with how

- live media works now for us: After booting into the live system, you can

- do whatever you want, install programs, save files to your home folder

- or even modify the root filesystem, as much as your free memory permits

- you. However, after rebooting you lose all those changes because the

- partitions on the drive are not touched. Persistent storage adds the

- possibility to retain those changes through reboots so you would be able

- to install new apps to your live environment or work with files stored

- on the flash drive.

- * Being able to write the images without destroying the data that was

- already present on the flash drive before.

- * Having a Fedora ARM image resized to fit the size of your SD card

- immediately after having it written.

- * Proper privilege escalation through launchd for the helper process on

- macOS.

- * Making this theme selected by default when the app runs in GNOME

- (probably C++, in the QGnomePlatform project)

- * link:https://fedoraproject.org/wiki/User:Bex[Brian (bex) Exelbierd] (Fedora Community Action and Impact

-   Coordinator, FCAIC, 🎂, containers, general development, general Linux)

- * link:https://fedoraproject.org/wiki/User:Sumantrom[Sumantro Mukherjee] (General development, general Linux,

-   Fedora community, GSoC alumnus, questions about program, misc. advice)

- * <<Packit can work with GitLab>>

- - Code in Packit service repository which makes packit understand the gitlab events

- - Packit is able to talk to a GitLab server API and:

- -- Comment on merge request

- --Report check results (builds, tests)

- - On-board at least a single project from GNOME gitlab instance (https://gitlab.gnome.org/explore/groups) to use packit.

- Ideally, kubernetes-nmstate should be update to use varlink. This is not a must.

- * Within two weeks of announcing accepted students (by Google Summer of Code 

- and Outreachy committee), Mindshare coordinates with mentors, students, and 

- general mentors to publish intern introduction blog posts on the community 

- blog for the respective programs.

- 

- * Mentors ensure that Students are posting a post every 2-3 weeks once the 

- coding period starts. (Can we use fedocal to set reminder and send an email 

- to the summer-coding/outreachy list? - needs discussion)

- 

- 

- Read the project description on the link:https://www.outreachy.org/[Outreachy website] thoroughly. Make a Fedora Account, join the Outreachy mailing list, Fedora's Outreachy communication channels, and project communication channels. You can introduce yourself on the mailing list or in channel.

- Detailed instructions on creating a Fedora Account found link:https://docs.fedoraproject.org/en-US/fedora-accounts/user/#newaccounts[here].

- Check the project description on the link:https://www.outreachy.org/[Outreachy website] to see details on communication mentors and contact information.

- The best places to ask questions you may have are the public project channels and Fedora's link:https://lists.fedoraproject.org/admin/lists/outreachy.lists.fedoraproject.org/[Outreachy mailing list]. Often you will get an answer faster if you ask on the public communication channels, rather than waiting for a mentor to answer your email. Applicants often have similar questions, so asking them in a public place helps everyone out. For public project channel information check project the project description on the link:https://www.outreachy.org/[Outreachy website]. If you have questions after communicating in these channels, then reach out to the mentor through direct message or email.

- If you need assistance and have exhausted all other avenues of communication, you can reach out to the Fedora Project Outreachy Coordinators. The coordinators are currently link:mailto:mnordin@redhat.com[Marie Nordin] and link:mailto:siddharthvipul1@fedoraproject.org[Vipul Siddharth].

- Outreachy related announcements will be published on Fedora's Outreachy mailing list.

- The review procedure will differ according to the project and mentor.

- Pagure is our own in-house Git-centered source code management forge. It is incredibly lightweight and based on PyGit2.

- Email link:mailto:logo@fedoraproject.org[logo@fedoraproject.org] following the instructions found link:https://fedoraproject.org/wiki/Logo#Can_I_use_this_logo.3F[here] and note that you are an Outreachy applicant.

- The best options are to use graphics made by the Fedora Design Team or original graphics made by yourself.You can use artwork that is licensed Creative Commons(there are a couple variations of this license), but the specifics of the license will apply for each piece of art you use.For example, if it requires attribution, you would need to include their name in the design.

- It is okay to use whatever software you are most comfortable with during the application period.This is not how the Fedora Design Team usually works, this is a special instance so that applicants can show off their developed skillsets.

- You will be required to use free software for the duration of the internship, such as Inkscape and GIMP.Your mentor will help guide you in learning any new pieces of software.

- Yes, absolutely.Collaboration with the Design Team and other applicants is encouraged.

- There are a couple places you can find Fedora design materials.The link:https://pagure.io/design/issues[fedora-design] repo on Pagure contains a lot of historical work.There is a dropdown on the left hand side that says "XX Open Issues", click that dropdown and set to "XX Open & Closed Issues" to see a complete list of tickets.You can then search under the "Filter" dropdown.The same applies to the https://pagure.io/fedora-badges/issues[fedora-badges] repo on Pagure.

- Please limit yourself to 2 tickets. You can work on a third if it is a Fedora Badges ticket. Although we appreciate the enthusiasm of our applicants, we also only have a certain capacity to provide reviews. This helps to ensure that applicants are receiving reviews equally and at regular intervals.

- This is a known error with Pagure caused by a migration from Trac to Pagure. But, no worries! There is a fix. Files that have that issue will look like this, with two identical comments.