Re: Outreachy Final Application help
Thanks, timeline looks good. On Thu, Apr 29, 2021 at 3:09 PM Ngulefac Queeniva wrote: > i updated the recent one even more and came up with this. pls review it > sir > > > > Week 1-2 > -Discussion with mentors team members and finalizing the approach of the > project implementation > -Refactor Code: > -making components more reusable, that is : Moving class components to > separate files > -Make code look cleaner > -Translate untranslated words. > > > Week 3-4 > -Restructure and order information on the landing page > -Make content on the page more presentable, that is > -using more infographics > -Changing the way the links and buttons look(making use of iconography) > -Including additional information and using familiar terms that could be > easily understood by newcomers > > > Week 5-6 > -Make the wizard section a lot more interactive and user friendly by : > -Including proper navigations > -Including clear instructions, code snippets and results where necessary. > > > Week 7-8 > -Make user experience a lot better and also improve UI > > > Week 9-11 > -Translate the application to the several new languages suggested > -Period for any pending task > > > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outreachy Final Application help
Hi Ngulefac, thank you for submitting the timeline proposal. We see a couple of issues with it, most importantly the first several weeks you plan on spending getting to know the codebase. Since you already proposed some PRs to the project you should be fairly knowledgeable of the codebase already. Thus, the timeline would have to be changed to reflect this, in order for us to deem it viable. I’m sure you’ll be able to make the changes without any issues, but should you encounter serious troubles, we are, of course, here to help. L. On Wed, Apr 28, 2021 at 7:10 AM Ngulefac Queeniva wrote: > Hello Lukas Brabec > > pls review this internship task timeline and let me know if i can use it > > > Week 1 -2 > -Onboarding and learning the ropes > -Get more details on the project requirements > -Familiarize with the structure of the codebase of Fedora QA landing page > > > Week 3-4 > -Finalize approach of the project implementation > > > Week 5-6 > -Refactor Code > -Restructure and order information on the landing page > -Make the wizard section a lot more interactive and user friendly > -Make user experience a lot simpler and also improve UI > > > > Week 7-8 > -Test and get feedback from mentors > -Optimise features based on feedback > > > Week 9-11 > -Translate the application to the several languages suggested > -Update documentation for the application > -Period for any pending task > > > > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outreachy 2021 applicant
There really isn't a reason, it is a quick and dirty code I did to have a proof of concept. Feel free to fix it. L. On Wed, Apr 21, 2021 at 10:52 AM KUNAL PRAKASH wrote: > Hello again Lukas Brabec, > I have one query that despite of having state store which contain all the > state. Why we are passing state as a props to component like Timeline.js, > Event.js etc. Why don't we use mapStateToProps for directly using the > particular state that component want to use. > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outreachy 2021 applicant
Hi Kunal, good to hear you made it through C19. Feel free to solve the issue and open pull request when you are done. Currently we don't assign any issues and we don't merge pull requests. In this way, everyone can work on any issue and we can compare the communication, code in pull requests, etc... L. On Tue, Apr 13, 2021 at 8:47 PM KUNAL PRAKASH wrote: > Hello Lukas Brabec, > > I was in quarantine for 12 days because I was tested COVID positive. Due > to which I was unable to contribute to this project. But from now I want to > contribute to the project consistently. > > I like to solve the issue which shows on console tab in developers tool. > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outreachy Applicant Introduction
Hi Shreya, welcome to Fedora QA and thanks for showing interest in our project. There shouldn't be any issues with Ubuntu - the javascript dependencies are not distro specific. Lukas On Sat, Apr 3, 2021 at 11:39 AM wrote: > Hello everyone, > I am Shreya Gupta, a sophomore at IIT Patna, India. I am having a keen > interest in Open Source. I am highly interested in your Outreachy project > 'Improve Fedora QA dashboard'. I am primarily interested in Web > development. I have the knowledge and prior experience of developing > websites in Nodejs, React, and Javascript. I have gone through the project > Readme file and project details where there is information about system > requirements. I am using Ubuntu and all other system requirements are > satisfied by my PC. will I be able to set up this project on ubuntu? Kindly > reply. > > Thank you. > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Important to Outreachy applicants
This mail is addressed to Outreachy applicants interested in contributing or already contributing to Fedora QA Dashboard. Due to public holiday in Czech Republic mentors will not be available in these dates: * lbrabec: Apr 1 - Apr 5 * jskladan: Apr 2 - Apr 5 Lukas ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Introduction
Hi Odinaka, thanks for showing interest in our project. There are tips for Outreachy applicants in readme [1] of the project. If anything is unclear feel free to ping me on IRC or send me an email. L. [1] https://pagure.io/fedora-qa/landingpage On Tue, Mar 30, 2021 at 12:40 PM Joy Odinaka wrote: > Hi, > I am Odinaka Joy, an outreachy applicant for the 2021 session. I am a web > developer based in Nigeria. > > I would love to join the Fedora team and contribute to the project - Improve > Fedora QA Dashboard. > > I have experience with JavaScript, React and Redux and would love to > improve my skills by contributing to this project. > > My contacts: > IRC Username: dinakajoy > Email: odinaka...@gmail.com > > I would appreciate any guidance to help me get started with my > contribution. > > Thank you. > > Best regards, > Odinaka Joy > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outreachy 2021 applicant
Hi Kunal, thanks for showing interest in our project, I see you already found our pagure repo and an issue you like to work on. I'll assign that issue to you. For any more questions feel free to post here or contact me directly via email lbra...@redhat.com L. On Tue, Mar 30, 2021 at 7:36 AM KUNAL PRAKASH wrote: > Hello everyone :) > I hope everyone is doing good in this pandemic. > Myself Kunal Prakash. 2nd year student from NIT Patna. I am experienced > with Javascript, React, Redux, CSS. I come across "Improve Fedora QA > Dashboard" project. I really liked the project and want to contribute to it. > Thank you. > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/qa-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora Packager Dashboard available for testing
On Wed, Jun 24, 2020 at 9:05 AM Josef Skladanka wrote: > Bob, > from what I've heard from Frantisek and Lukas, the teeny VPS is under > constant load since yesterday, since we have _a lot_ of tasks in the > celery queues. It might well be that it will take some time to get to > sync your data. IIRC the ouroboros is shown at the beginning when we > wait for information about your groups and packages to be downloaded > from Pagure, which was one of the really slow bits during our testing. > Once that is loaded, the other information is being loaded and shown > progressively. > > Frantisek/Lukas please correct me if I'm wrong about this. > > J. > > There are two spinners. The first one is on a splash screen (spinning thingy on a field of gray) which indicates fetching of packages and groups. The second one is small grey on the stats line, next to the fas username. Dashboard is usable at that moment, it just indicates that bugs and PRs are still fetched in background and progressively added. The first complete sync can take a long time to finish. But spinning for an extended period of time (e.g. overnight) could mean something got stuck. L. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Change proposal discussion - Optimize SquashFS Size
On Mon, Feb 3, 2020 at 5:55 PM Kevin Fenzi wrote: > So, I propose: > reduce install time > reduce image size > reduce compose time +1 Sounds very reasonable. On Tue, Feb 4, 2020 at 1:22 PM Kamil Paral wrote: > ... > Exactly what Kamil wrote. Few percent grow is negligible, but install time reduction is huge. On Tue, Feb 4, 2020 at 4:44 PM Kevin Kofler wrote: > The areas where hundreds of installations are performed from an image are > hardly the common case, and those installations should really consider > composing their own images with exactly the package set that they need > (including site packages that Fedora cannot ship), images which they can > then compress with a faster-to-decompress algorithm. I think that we > should > optimize for the standard user who installs exactly once. > It is pretty common for us in Fedora QA (well, I'm quite biased in this case). And no, we cannot compose our images, we have to test the exact same images that will be shipped. We cannot test custom images and pretend the results are going to be the same for official images. And finally, those few percent can make the difference between fitting on a > given fixed-size physical media or not. The original change proposal of > trying to minimize the size might actually make at least the smaller spins > fit on a DVD again. > All current Fedora spins [1] are well within the DVD size limit (4.7GB), even if the images grow a few percent. This is also true for optical boot release blocking images [2][3][4]. [1] https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Spins/x86_64/iso/ [2] https://fedoraproject.org/wiki/Releases/32/ReleaseBlocking [3] https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/x86_64/iso/ [4] https://dl.fedoraproject.org/pub/fedora/linux/releases/31/Workstation/x86_64/iso/ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Fedora 32 System-Wide Change proposal: Drop Optical Media Release Criterion
I'm +1. The oldest laptops I have experience with are HP 4520s and Lenovo X201i, both from 2010, both support USB boot. Two biggest online stores in Czechia: - CZC.cz lists 1422 laptops without optical drive, 128 with. - Alza.cz lists 2223 without optical drive filter, 138 with. Every autumn, we do Fedora Installfest and I don't even think we met someone with a laptop that doesn't support USB boot. On Fri, Dec 13, 2019 at 12:03 PM Miro Hrončok wrote: > > Juts a random idea, not very thought-out: > > Could we keep optical media bugs reported by users as blocking, but not > require > it during validation testing? > > > aka: Fedora QE would no longer have to verify optical media works. > but: If a tester finds an optical media bug, it is still blocking. > Well, not ideal, but if this should be the middle ground we agree on, I'd be okay with it. On Mon, Dec 16, 2019 at 5:36 AM John M. Harris Jr wrote: > > On Sunday, December 15, 2019 9:03:06 PM MST Chris Murphy wrote: > > https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria#OS_X_dual_boot > > Thank you, I'll see if anyone actually tests that, and see if we can get a > Change proposal to drop that requirement if not. > I'm the one who usually does it [1][3][4][5], sometimes it is cmurf [2]. [1] https://fedoraproject.org/wiki/Test_Results:Fedora_27_RC_1.2_Installation#Fedora_Media_Writer [2] https://fedoraproject.org/wiki/Test_Results:Fedora_28_RC_1.1_Installation#Fedora_Media_Writer [3] https://fedoraproject.org/wiki/Test_Results:Fedora_29_RC_1.2_Installation#Fedora_Media_Writer [4] https://fedoraproject.org/wiki/Test_Results:Fedora_30_RC_1.1_Installation#Fedora_Media_Writer [5] https://fedoraproject.org/wiki/Test_Results:Fedora_31_RC_1.3_Installation#Fedora_Media_Writer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Ansiblizing Questions
Hey, gang! As I read through standard interface and tried ansiblized branch of libtaskotron, I found things that were not exactly clear to me and I have some questions. My summer afternoon schedule involves feeding rabbits (true story!) and I keep missing people on IRC, hence this email. = Test output and its format = Standard test interface specifies that [1]: 1) "test system must examine the exit code of the playbook. A zero exit code is successful test result, non-zero is failure" and 2) "test suite must treat the file test.log in the artifacts folder as the main readable output of the test" ad 1) Examining the exit code is pretty straight forward. The mapping to outcome would be zero to PASSED and non-zero to FAILED. Currently we use more than these two outcomes, i.e. INFO and NEEDS_INSPECTION. Are we still going to use them, if so, what would be the cases? The playbook can fail by itself (e.g. fail like command not found, or permission denied), but I presume this failure would be reported to ExecDB not to ResultsDB. Any thoughts on this? ad 2) The standard interface does not specify the format of test output, just that the test.log must be readable. Does this mean that the output can be in any arbitrary format and the parsing of it would be left to people who care, i.e. packagers? Wouldn't be this a problem with if, for example, bodhi wanted to extract/parse this information from ResultsDB and show it on update page? = Triggering generic tasks = Standard interface is centered around dist-git style tasks and doesn't cover generic tasks like rpmlint or rpmdeplint. As these tasks are Fedora QA specific, are we going to create custom extension to standard interface, used only by our team, to be able to run generic tasks? = Reporting to ResultsDB = Gating requirements for CI and CD contains [2]: "It must be possible to represent CI test results in resultsdb." However standard interface does not speak about resultsdb. Does this mean, that task playbook won't contain something like ResultsDB module (in contrast to ResultsDB directive in formulae), as the task playbook should be agnostic to system in which it is run, and the reporting will be done by our code in runtask? = Output of runtask = Libtaskotron's output is nice and readable, but output of the parts, handled by ansible now, is not. My knowledge of ansible is still limited, but as far as my experience goes, debuging ansible playbooks or even asnible modules is kind of PITA. Are we going to address this in some way, or just bite the bullet and move along? = Params of runtask = When I tried ansiblized branch of libtaskotron, I ran into issues such as unsupported params: ansible told me to run it with "-vvv" param, which runtask does not understand. Is there a plan on how are we going to forward such parameters (--ansible-opts= or just forward any params we don't understand)? Runtask, at the moment, maps our params to ansible-playbook params and those defined by standard interface. Are we going to stick with this or change our params to match the ones of ansible-playbook and standard interface (e.g. item would become subject, etc)? = Future of runtask = For now, runtask is user-facing part of Taskotron. However, standard interface is designed in such way, that authors of task playbooks shouldn't care about Taskotron (or any other system that will run their code). They can develop the tasks by simply using ansible-playbook. Does this mean that runtask will become convenient script for us that parses arguments and spins up a VM? Because everything else is in wrapping ansbile playbook... Lukas [1] https://fedoraproject.org/wiki/Changes/InvokingTests [2] https://fedoraproject.org/wiki/Fedora_requirements_for_CI_and_CD ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: stats-bodhi license
I'm fine with GPL2+ ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
libtaskotron: terminology changes, yaml format changes
New naming convention was introduced in commit [1d21976]. Task YAML files are now called formulae and key `task:` in task formula was replaced with key `actions:` which better describes its meaning. This change means that task formulae with old 'task:' key won't work and will raise TaskotronYamlError (unfortunately at this moment this applies to all tasks in our bitbucket repo, but do not worry, patches will come). LB [1d21976] https://bitbucket.org/fedoraqa/libtaskotron/commits/1d21976465253e77d4a8d0323ac00ef3f248d0a8 ___ qa-devel mailing list qa-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/qa-devel
