From 610d416312e4bc2385787ac875daece926ca457e Mon Sep 17 00:00:00 2001 From: Akashdeep Dhar Date: Mar 24 2021 05:45:06 +0000 Subject: [PATCH 1/3] Added pages for 2021 Outreachy Idea List --- diff --git a/modules/ROOT/pages/outreachy/2021/ideas.adoc b/modules/ROOT/pages/outreachy/2021/ideas.adoc new file mode 100644 index 0000000..464e34e --- /dev/null +++ b/modules/ROOT/pages/outreachy/2021/ideas.adoc @@ -0,0 +1,179 @@ +== Ideas + +NOTE: Fedora is participating in the link:https://www.outreachy.org/[Outreachy] +round running from May to August 2021 and we are yet to the participants for +this season. + +If you are a student looking to participate in +xref:outreachy/2021/index.adoc[Outreachy], please feel free to +browse this idea list. There may be additional ideas added during the +application period. + +Do not hesitate to contact the mentors or contributors listed on this +page for any questions or clarification. You can find helpful people on +the IRC channel, or use the mailing list. can be used for getting help +with programming problems. + +== Idea list +NOTE: Ideas are subject to change as additional mentors are onboarded. + +* <> +* <> +* <> +* <> + +=== Develop Designs for the Fedora Community Outreach Revamp + +Back to <> + +The Fedora Design Team is Fedora's in-house design agency. We provide artwork, user experience, usability, and general design services to the Fedora project. This internship will focus on the development & design of assets for the Revamp, including team logos, promotional materials, badges, and swag. + +==== Sample plan of work for the 12 week internship. + +. **Week 1**: + * Design and get approval on sub-team logos. Learn about the Community Outreach Revamp. Meet with the Revamp co-leads. +. **Week 2**: + * Start on layout for Role Handbook pages. Blog post to community blog. +. **Week 3**: + * Work on layout for role handbooks and begin badges. +. **Week 4**: + * Complete layout for role handbooks, and start making versions for each role. Continue work on badges. +. **Week 5**: + * Revisions on role handbook pages. Continue work on badges. Meet with the Revamp co-leads. +. **Week 6**: + * Finish up badges & role handbook pages. Blog post to community blog. +. **Week 7**: + * Begin swag designs & drafting marketing plan. +. **Week 8**: + * Revise swag designs. Incorporate feedback into marketing plan, and begin sketching ideas. +. **Week 9**: + * Finalize swag designs. Begin to create assets for marketing plan such as social media posts, blog posts, HDYF? videos. Meet with the Revamp co-leads. +. **Week 10**: + * Work on assets for marketing plan, and start to publish as produced. Create some one of designs for CommOps docs page. +. **Week 11**: + * Work on marketing plan assets & revise designs for CommOps page. +. **Week 12**: + * Finalize and upload all work. Continue publishing marketing materials. Blog post to community blog. + +=== Improve Fedora QA Dashboard + +Back to <> + +Fedora QA dashboard is an idea of a web application that would be the landing page for QA related activities. The current state, as we see it, is that we have tons of helpful documents, tools, and processes, but these are scattered, or sometimes hard to reach/understand without some preliminary knowledge. We identified this as the major obstacle in bootstrapping new members of the community. Goal for this project is making the learning curve less steep. We have basic PoC, that could serve as a base to build from, or an inspiration for a rework. + +==== Sample plan of work for the 12 week internship. + +. **Week 1** + * Create final design from provided mock up ideas + * Getting feedback from Fedora QA team + * Design changes based on feedback + +. **Week 2** + * Project structure and components based on final design + * Coding (crating a component one at a time, e.g. + * Fedora schedule, blocker summary, contributing guide, ...) + +. **Week 3** + * Coding + +. **Week 4** + * Coding (components are "done", they work individually, but don't necessarily form an app) + +. **Week 5** + * Coding (putting components together to form an app) + * Fedora community blog post + * Getting feedback from "general public" + +. **Week 6** + * Changes based on feedback + * Coding + +. **Week 7** + * Coding (from now on, the app generally represents final design from week 1) + * Getting feedback from Fedora QA team + +. **Week 8** + * Changes based on feedback + * Coding + +. **Week 9** + * Coding and finalizing + +. **Week 10** + * Final touches and deployment + * Fedora community blog post + +=== Improve Fedora\'s automated community metrics + +Back to <> + +Many activities in Fedora generate activity on the Fedora Message bus. (More about this here: https://communityblog.fedoraproject.org/moving-from-fedmsg-to-fedora-messaging/). These messages can be used to measure and graph community engagement. + +Rudimentary Python code to do this is at: https://pagure.io/fedora-contributor-trends + +I have used this data in talks (https://mattdm.org/fedora/2016devconf/) and to help inform project decision making. I also have a weekly-updated version here: https://mattdm.org/fedora/fedora-contributor-trends/. + +This project would be to improve and update this code in up to six different ways: + +1. As outlined in the blog post above, the Fedora Message bus is in the midst of transitioning to new technology, which may make the way the current script gets data obsolete. See https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/message/6NRUH7EP6ERTBUEVTTXYLA25QUSHTKBE/ for possible plans. The upside is that some of the new options could be much better; the current code hits the server very hard. +2. The code really is hacky and ugly. It could use refactoring and beautification. +3. There are some data sources we're not using and could be: there are messages from pagure and will be ones from discourse that would be excellent candidates. +4. The visualizations I created for my presentation in 2016 are nice, but there are many other ways to look at the data. Come up with new ways to look at it which may show more insights. +5. Find an official place for this to run rather than on mattdm's personal server. +6. Simply put, the graphs and reports could be prettier. + +Completion of all six is not necessary for project success. An applicant could choose to focus on two or three of these and that would still be hugely beneficial. + +==== Sample plan of work for the 12 week internship. + +. **Week 1**: + * Familiarity with concepts +. **Week 2**: + * Local instance of existing code +. **Week 3**: + * Adding new data sources +. **Week 4**: + * Code cleanup and refactoring +. **Week 5-6**: + * Porting to theoretical new datagrepper replacement +. **Week 7**: + * More code cleanup and refactoring +. **Week 8**: + * Deploy to somewhere in Fedora infrastructure for manual testing +. **Week 9**: + * Automate daily or weekly updates +. **Week 10-11**: + * Explore new things to graph and present +. **Week 12**: + * Make the graphs and reports pretty + +=== Support repo overrides in rpm-ostree + +Back to <> + +Today, rpm-ostree support overrides from locally downloaded RPM files. For example: + +``` +rpm-ostree override replace kernel.rpm +``` + +This works great, but is limiting. There are many situations where one would rather have an RPM override from yum repos, the same way one would usually simply yum install on a traditional system. + +We want to teach rpm-ostree this ability. The command-line UX would be similar, for example: + +``` +rpm-ostree override replace kernel +``` + +Except that rpm-ostree would look for the specified package(s) in enabled yum repos. + +==== Sample plan of work for the 12 week internship. + +. **Week 1-2**: + * Ramp up and set up developer environment. +. **Week 3-4**: + * Finalize approach of implementation. +. **Week 5-9**: + * Work on implementation, iterate based on feedback from mentors. +. **Week 10-12**: + * Stretch goals based on interest. Some ideas include better overrides integration with COPR, Bodhi, and/or Koji, and writing a fedmag blog post about the new feature.Week 1-2: Ramp up and set up developer environment. diff --git a/modules/ROOT/pages/outreachy/2021/index.adoc b/modules/ROOT/pages/outreachy/2021/index.adoc new file mode 100644 index 0000000..a7a2178 --- /dev/null +++ b/modules/ROOT/pages/outreachy/2021/index.adoc @@ -0,0 +1,146 @@ +== Outreachy + +NOTE: Fedora is participating in the link:https://www.outreachy.org/[Outreachy] +round running from May to August 2021. + +=== What is Outreachy + +image::outreachy_logo.png[float="right"] +Outreachy is an internship program for people from group underrepresented in free and open source software, including women internationally and underrepresented people of color in the U.S. Our goal is to increase participation in Fedora. Please see the link:https://www.outreachy.org/apply/[main page with program details] for the general information, such as timeline, background information, eligibility, requirements, and the application form. + +This page contains information about Fedora's participation Outreachy. Please feel free to contact us via the mailing list below for clarifications and more information. You can also use the IRC channel. + +=== Student Information +NOTE: We are yet to select the participants for 2021, please stay posted to the +mailing list link:https://lists.fedoraproject.org/admin/lists/summer-coding@lists.fedoraproject.org/[summer-coding@lists.fedoraproject.org] +for announcements regarding the selections and about the information regarding the projects. +You can read the accepted project for this year at xref:outreachy/2021/ideas.adoc[ideas]. + +=== Why spend your summer working on FOSS? + +When you work in the open on free software, you create a body of work +that follows you for the rest of your life. Rather than a coding +assignment done by thousands of other students and relegated to the +bottom of the drawer at semester's end, working in FOSS is a chance to +contribute to a living project. + +Working in FOSS gives you a chance to: + +* Work with real-world, large codebases. +* Collaborate with real engineers and other professionals. +* Contribute to something meaningful while learning and earning. +* Learn tools and processes that are just like what you are going to use + if you work in technology after graduation. +* Make friends and contacts around the globe. +* Attract attention that can lead to an internship or job after + graduation. +* Create lifetime connections and associations. + +If you are new to the Fedora Project, the following material will help +you to get started. + +* link:https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html[Fedora Project Overview] +* link:https://docs.fedoraproject.org[Fedora Technical and Community Documentation] +* link:https://fedoraproject.org/wiki/How_to_use_IRC[How to use IRC] +* link:https://fedoraproject.org/wiki/Development[Information about Development in Fedora] + +=== Student Responsibilities + +You are the key ingredient for your project's success. This project is +important to you, your mentor, and the entire Fedora Community. + +Your responsibilities include: + +* Communicating early and often with your mentor. +* Blogging every week about what you're learning, how you're doing, + challenges and successes. This is key way to keep the entire Fedora + Community informed. +* Working with your mentor on realistic achievable milestones that + provide for regular deliverables and feedback. +* Attending the brief student calls, as announced +* Being accountable for your success and your actions + +=== Mentor Information + +NOTE: If you are contacted directly by a student, we encourage you +to reply and include the mailing list and/or IRC channel to keep the +process transparent and to ensure the inquiry is able to be answered by +more people than just you. + +=== How to Propose a Project + +If you want to mentor a specific project, think carefully about several things: + +1. Do you have enough time to work on this with the student during the + entire project. You will be helping someone else when they get stuck. + You don't want to become a blocker because you're busy. + +2. It is harder to find success when you are completely certain of how an + idea needs to be implemented; finding a student with the skills and + interest to implement a specific solution is a lot harder than finding + a student with enough skills to respond to a use case need. Also, + students learn more when they help design and guide the project. In + other words, provide guidance and direction but let the student do + some of the "driving." + +3. Where you can have looser ideas, you may be able to find a student + who works as a sort-of intern who can implement a solution to a use + case you have. In past experiences, students going after a use case are + more likely to get somewhere with self-direction and support from you. + +4. Who can help you? Try to find a second mentor for the project. + +If you're interested in working with a student on a specific project you should post your idea to the https://pagure.io/mentored-projects/issues[Mentored Projects Issue Tracker]. Your issue should be tagged *Outreachy* and use the *Outreachy - Proposed Project* template. We strongly encourage you to find a second person to help with mentoring and to solicit feedback on your proposal + +=== Can I be a Mentor Without a Project? + +Yes! You can either: + +* Work with a student who brings an idea to your sub-project. This + requires a different level of communication throughout the project, + but can be the most rewarding. + +* Be a general mentor. This is a person who works with all students + regardless of their project. To become a general mentor please open + an issue in the https://pagure.io/mentored-projects/issues[Mentored + Projects Issue Tracker] offering your help. Please ask for tagging + the issue with the *Outreachy* label. + +=== Mentor Responsibilities + +You are an essential part of the student's success, the project's +success, and the success for the Fedora Project. + +Your responsibilities include: + +* Being an interface for an identified sub-project or SIG in Fedora. +* Helping students communicate with the overall project and any + upstream. +* Helping the student plan realistic achievable milestones that provide + for regular deliverables and feedback. +* Regular communication with your student. This means you must be + regularly available for the entire project. If you take a holiday you + need to know early and help your student be ready for your brief + absence. +* Attending a brief mentors call, as scheduled. +* Be the final, accountable person for deciding if the student is + successful or not. This is responsibility akin to being a professor or + boss. + + +* Read about mentor and their responsiblity in the + link:https://www.outreachy.org/mentor/#mentor[Outreachy mentor page] + +=== Communication + +* *Mailing List (Outreachy):* +* *Mailing List (devel list):* link:https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org] +* *IRC:* link:https://webchat.freenode.net/?channels=#fedora-outreachy[#fedora-outreachy] or link:https://webchat.freenode.net/?channels=#fedora-devel[#fedora-devel] on Freenode + +=== Administration + +In order to get questions answered or obtain more information related to +this year's Outreachy with Fedora, please contact the administrators or ask on +the Outreachy list. + +1. link:https://fedoraproject.org/wiki/User:riecatnor[Marie Nordin] From 6a9e226eefb305712c057cc9e29732ce5640f579 Mon Sep 17 00:00:00 2001 From: Akashdeep Dhar Date: Mar 24 2021 05:45:36 +0000 Subject: [PATCH 2/3] Fixed cross-reference and added links to navbar --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 85e05da..67b74ba 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -70,3 +70,6 @@ ** 2020 *** xref:outreachy/2020/index.adoc[Information] *** xref:outreachy/2020/ideas.adoc[Ideas] +** 2021 +*** xref:outreachy/2021/index.adoc[Information] +*** xref:outreachy/2021/ideas.adoc[Ideas] diff --git a/modules/ROOT/pages/outreachy/2020/ideas.adoc b/modules/ROOT/pages/outreachy/2020/ideas.adoc index f56406e..b1ce672 100644 --- a/modules/ROOT/pages/outreachy/2020/ideas.adoc +++ b/modules/ROOT/pages/outreachy/2020/ideas.adoc @@ -1,9 +1,11 @@ +== Ideas + NOTE: Fedora is participating in the link:https://www.outreachy.org/[Outreachy] round running from May to August 2020 and we have already selected our interns for this season. If you are a student looking to participate in -xref:outreacy/2020/index.adoc[Outreachy], please feel free to +xref:outreachy/2020/index.adoc[Outreachy], please feel free to browse this idea list. There may be additional ideas added during the application period. From a4d5868a041c4ea0f4c75dfbabf543040366af5f Mon Sep 17 00:00:00 2001 From: Akashdeep Dhar Date: Mar 25 2021 07:09:02 +0000 Subject: [PATCH 3/3] Added a list of general mentors --- diff --git a/modules/ROOT/pages/outreachy/2021/index.adoc b/modules/ROOT/pages/outreachy/2021/index.adoc index a7a2178..c6da8fc 100644 --- a/modules/ROOT/pages/outreachy/2021/index.adoc +++ b/modules/ROOT/pages/outreachy/2021/index.adoc @@ -127,10 +127,16 @@ Your responsibilities include: successful or not. This is responsibility akin to being a professor or boss. - * Read about mentor and their responsiblity in the link:https://www.outreachy.org/mentor/#mentor[Outreachy mentor page] +=== General Mentors + +The general mentors for this round of Outreachy are + + * link:https://fedoraproject.org/wiki/User:T0xic0der[Akashdeep Dhar] (FAS/IRC: `t0xic0der`) + * link:https://fedoraproject.org/wiki/User:Mobrien[Mark O' Brien] (FAS/IRC: `mobrien`) + === Communication * *Mailing List (Outreachy):*