Re: Introduction - Dominic Geevarghese

2017-08-21 Thread Dominic P Geevarghese 
Hi Sumantrom,

Thank you very much for warm welcome :-)

Thanks,
Dominic Geevarghese
4096R/43EACB09


On Mon, Aug 21, 2017 at 12:11 PM, Sumantro Mukherjee 
wrote:

>
>
> - Original Message -
> > From: "Dominic P Geevarghese" 
> > To: test@lists.fedoraproject.org
> > Sent: Friday, August 18, 2017 9:15:45 PM
> > Subject: Introduction - Dominic Geevarghese
> >
> >
> > Fellow members,
> >
> > I am excited to meet the QA community and I would like to be part of
> Fedora
> > QA contributors.
> >
> > I am Dominic Geevarghese ( 4096R/43EACB09 ) , using various distros
> including
> > RHEL/CentOS/Fedora/Suse in professional life and Fedora on my personal
> > hardware. My irc nick is dominicpg and I am available on most of the
> > #fedora-* channels.
> >
> > --
> > Cheers,
> > Dominic Geevarghese
> >
> > ___
> > test mailing list -- test@lists.fedoraproject.org
> > To unsubscribe send an email to test-le...@lists.fedoraproject.org
> >
>
> Hey Dominic,
>
> First of all, Welcome and thanks for showing your interest in Fedora QA. I
> have sponsored your QA group request.
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
> for Fedora 25 and Fedora 26.  Update testing is where a tester tests a
> package and gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go
> to bodhi.fedoraproject.org where you can sort the packages with Fedora
> Releases and tags viz "pending" & "testing" . You can read much about
> update testing here [1]. You can also, use fedora-easy-karma for giving out
> feedbacks.
>
>
> you can start with  Release Validation testing. In Release Validation all
> you need to do is to check the nightly/TC/RC against certain criteria. For
> example, let's take the latest compose (Fedora 27 Branched 20170817.n.3),
> you can run test cases which are mentioned [2] and submit your results in
> the test matrix.
> Note that each of the test cases[3] will have "How to test" section which
> will have the steps (to be executed sequentially) and if the results match
> with the expected results you can mark it as pass by editing the wiki page
> {{result|PASS|}} . Always make sure to check for "Associated
> release criterion" which can be found on the top of test case page , if
> your test case fails you can mark it fail by editing the wiki page
> {{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.
>
>
>  You can always find the ‘current’ validation pages using these addresses:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>
>
> For Automation, you can start looking at Taskotron [
> https://fedoraproject.org/wiki/Taskotron]
> and Open QA[https://fedoraproject.org/wiki/OpenQA].
>
>
>
> [1]https://fedoraproject.org/wiki/QA:Updates_Testing
> [2]https://fedoraproject.org/wiki/Test_Results:Fedora_27_
> Branched_20170817.n.3_Summary
> [3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
> [4]https://bugzilla.redhat.com/
>
> We have a test day coming up for testing major changes in F27. You can
> find the announcements on @test-announce list and community blog.
>
> Thanks
> //sumantrom
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>



-- 
Regards,
Dominic.P.Geevarghese
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self-introduction: Andreas Nazlidis

2017-08-21 Thread Sumantro Mukherjee 


- Original Message -
> From: "Andreas Nazlidis" 
> To: test@lists.fedoraproject.org
> Sent: Monday, August 14, 2017 12:33:11 AM
> Subject: Self-introduction: Andreas Nazlidis
> 
> Hi! I want to start contributing to the QA team. I have been using fedora for
> about one year and linux since 2011. I think it's time to start contributing
> to the fedora project because i really like the distro.
> 
> I have basic knowledge in C/C++ and Python with which i implement numerical
> methods.
> 
> My name is Andreas Nazlidis, i am 33 years old and i currently live in
> Munich, Germany. I am a computational physicist.
> 
> I should mention that my laptop doesn't support virtualization so i want to
> have a productive system and at the same time the ability to help the QA
> team. I would appreciate any suggestions. Thank you very much in advance!
> 
> my IRC: anazli9
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Andreas,

First of all, Welcome and thanks for showing your interest in Fedora QA. You 
can start by sending a qa group membership.

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for 
Fedora 25 and Fedora 26.  Update testing is where a tester tests a package and 
gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to 
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases 
and tags viz "pending" & "testing" . You can read much about update testing 
here [1]. You can also, use fedora-easy-karma for giving out feedbacks.


you can start with  Release Validation testing. In Release Validation all you 
need to do is to check the nightly/TC/RC against certain criteria. For example, 
let's take the latest compose (Fedora 27 Branched 20170817.n.3), you can run 
test cases which are mentioned [2] and submit your results in the test matrix.

Note that each of the test cases[3] will have "How to test" section which will 
have the steps (to be executed sequentially) and if the results match with the 
expected results you can mark it as pass by editing the wiki page 
{{result|PASS|}} . Always make sure to check for "Associated 
release criterion" which can be found on the top of test case page , if your 
test case fails you can mark it fail by editing the wiki page 
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.


 You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test


For Automation, you can start looking at Taskotron 
[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].



[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_27_Branched_20170817.n.3_Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

We have a test day coming up for testing major changes in F27. You can find the 
announcements on @test-announce list and community blog.

Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Self-introduction: Yoann E. A. Le Bihan

2017-08-21 Thread Sumantro Mukherjee 


- Original Message -
> From: "YLB" 
> To: test@lists.fedoraproject.org
> Sent: Wednesday, August 16, 2017 6:27:12 PM
> Subject: Self-introduction: Yoann E. A. Le Bihan
> 
> Hello QA team,
> 
> I'm new here, so I'm following the onboarding process I was referred
> to at the IRC meeting on Monday... to begin with, a quick intro on the
> list! (My IRC handle is vbird.)
> 
> As I did the same last week on the infrastructure list (looks like
> what I do for a living at $DAYJOB, so I started there), I'm reusing
> the same bullet points (sorry for the repetition if you've already
> read that before:)).
> 
>   - Skills I have: Linux sysadmin for roughly 15 years (including 13+
> in a professional capacity); PHP developer in my early years; system
> scripting (mostly bash and Perl); VoIP / SIP with Asterisk (at a time
> it still looked like a revolution!); virtualisation (but mostly
> proprietary products).
> 
>   - Skills I'd like to learn (or improve): Python (a bit rusty), Ruby,
> Ansible, Docker & OpenShift, KVM, OpenStack, anything else that could
> be fun playing with.
> 
>   - Location & timezone: Luxembourg, CET/UTC+1 (or CEST/UTC+2 in the summer.)
> 
> I spent most (all?) of my professional life self-employed working with
> open source techno but I never actively participated in any open
> source project before. This year, I decided it was time for me to give
> back to the community, and so... here I am! ;)
> 
> At this stage, I haven't read all the intro material of the QA section
> of the wiki but I'm on it now.
> 
> Hope to join/help soon!
> 
> Cheers,
> 
> Yoann E. A. Le Bihan
> [[ www.Yoann.info ]]

Hey,

First of all, Welcome and thanks for showing your interest in Fedora QA. I 
would like you to send a QA group request , I will sponsor you :).

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for 
Fedora 25 and Fedora 26.  Update testing is where a tester tests a package and 
gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to 
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases 
and tags viz "pending" & "testing" . You can read much about update testing 
here [1]. You can also, use fedora-easy-karma for giving out feedbacks.


you can start with  Release Validation testing. In Release Validation all you 
need to do is to check the nightly/TC/RC against certain criteria. For example, 
let's take the latest compose (Fedora 27 Branched 20170817.n.3), you can run 
test cases which are mentioned [2] and submit your results in the test matrix.

Note that each of the test cases[3] will have "How to test" section which will 
have the steps (to be executed sequentially) and if the results match with the 
expected results you can mark it as pass by editing the wiki page 
{{result|PASS|}} . Always make sure to check for "Associated 
release criterion" which can be found on the top of test case page , if your 
test case fails you can mark it fail by editing the wiki page 
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.


 You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test


For Automation, you can start looking at Taskotron 
[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].



[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_27_Branched_20170817.n.3_Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

We have a test day coming up for testing major changes in F27. You can find the 
announcements on @test-announce list and community blog.

Thanks
//sumantrom 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Re: Introduction - Dominic Geevarghese

2017-08-21 Thread Sumantro Mukherjee 


- Original Message -
> From: "Dominic P Geevarghese" 
> To: test@lists.fedoraproject.org
> Sent: Friday, August 18, 2017 9:15:45 PM
> Subject: Introduction - Dominic Geevarghese
> 
> 
> Fellow members,
> 
> I am excited to meet the QA community and I would like to be part of Fedora
> QA contributors.
> 
> I am Dominic Geevarghese ( 4096R/43EACB09 ) , using various distros including
> RHEL/CentOS/Fedora/Suse in professional life and Fedora on my personal
> hardware. My irc nick is dominicpg and I am available on most of the
> #fedora-* channels.
> 
> --
> Cheers,
> Dominic Geevarghese
> 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> 

Hey Dominic,

First of all, Welcome and thanks for showing your interest in Fedora QA. I have 
sponsored your QA group request.

You can start off by testing updates in [http://bodhi.fedoraproject.org/] for 
Fedora 25 and Fedora 26.  Update testing is where a tester tests a package and 
gives out a +1 Karma for PASS and -1 Karma for FAIL. You can go to 
bodhi.fedoraproject.org where you can sort the packages with Fedora Releases 
and tags viz "pending" & "testing" . You can read much about update testing 
here [1]. You can also, use fedora-easy-karma for giving out feedbacks.


you can start with  Release Validation testing. In Release Validation all you 
need to do is to check the nightly/TC/RC against certain criteria. For example, 
let's take the latest compose (Fedora 27 Branched 20170817.n.3), you can run 
test cases which are mentioned [2] and submit your results in the test matrix. 
Note that each of the test cases[3] will have "How to test" section which will 
have the steps (to be executed sequentially) and if the results match with the 
expected results you can mark it as pass by editing the wiki page 
{{result|PASS|}} . Always make sure to check for "Associated 
release criterion" which can be found on the top of test case page , if your 
test case fails you can mark it fail by editing the wiki page 
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.


 You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test


For Automation, you can start looking at Taskotron 
[https://fedoraproject.org/wiki/Taskotron]
and Open QA[https://fedoraproject.org/wiki/OpenQA].



[1]https://fedoraproject.org/wiki/QA:Updates_Testing
[2]https://fedoraproject.org/wiki/Test_Results:Fedora_27_Branched_20170817.n.3_Summary
[3]https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4]https://bugzilla.redhat.com/

We have a test day coming up for testing major changes in F27. You can find the 
announcements on @test-announce list and community blog.

Thanks
//sumantrom
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org