#45 Welcome to Fedora t0xic0der
Closed: C: Complete 3 years ago by alciregi. Opened 3 years ago by ankursinha.

Hello @t0xic0der ! Welcome to Fedora!

Before we begin, please subscribe to the Fedora join mailing list at
fedora-join@lists.fedoraproject.org
.
We use this list for general discussion, and it is also where the community
shares tasks that need help.

Then, could you please introduce yourself (preferably on the list) so that the
community can get to know you? (interests, skills, anything you wish to say
about yourself really)

In the meantime, these links would be a good read. They tell you what the
Free/Open Source community is about, and then they'll introduce you to Fedora:
what Fedora is all about, and what we do, and of course, how we do it:

If you have any questions at all, please ask! We'll use this ticket to keep in
touch! :)

The process we follow is documented in the Readme


Metadata Update from @alciregi:
- Issue untagged with: C: Introduction requested
- Issue tagged with: S: Introduced myself

3 years ago

Done. Let me know where to move on to.

A note to myself

  • Addressed issue #238 from Quick Docs
  • Made PR #239 to Quick Docs
  • Redid PR #240 to Quick Docs
  • Merged by @ankursinha on 5th May 2020, 16:08:37 IST

A note to myself

  • Addressed issue #230 from Quick Docs
  • Made PR #241 to Quick Docs
  • Waiting on review and merge

A note to myself

  • Addressed issue #186 from Fedora Commops
  • Made PR #5 to Fedora Commops
  • Merged by @bt0dotninja on 19th May 2020, 06:01:47 IST

A note to myself

  • Asked for assignment of #243 from Quick Docs
  • Made PR #244 to add reviewed changes
  • Waiting on review and merge

A note to myself

  • Asked for assignment of #165 from Quick Docs

Thank you @t0xic0der your commitment is amazing.

Done. Let me know where to move on to.

From the links, did you find an area of Fedora that interests you perhaps? (apart from docs?)

Metadata Update from @ankursinha:
- Issue tagged with: I: Documentation-Writing

3 years ago

Done. Let me know where to move on to.

From the links, did you find an area of Fedora that interests you perhaps? (apart from docs?)

Umm. Apart from this, every link kind of talked about what Fedora is and how is everything organized here - so did not quite get to explore the things I can be interested in.

I would love to hear your suggestions about what I can/should do.

Also, I am working on this with @ferdnyc's and @kwizart 's assistance.

Also, I am working on this with @ferdnyc's and @kwizart 's assistance.

Metadata Update from @alciregi:
- Custom field Temporary membership granted on adjusted to 2020-06-02
- Issue tagged with: C: Temporary membership approved

3 years ago

A note to myself.

  • Was offered reviewing PR #171 by @ankursinha on 27 May 2020, 13:42IST
  • Asked for assignment of PR #171 on 27 May 2020, 19:20IST
  • Finished commenting suggested changes on 5 Jun 2020, 19:50IST

A note to myself

v0.3.0 released (04 June 2020, 20:12IST)
Check the build here.

Added tons of new features here.

  • Combined RPM Fusion pinging, checking, installing into a single module
  • Combined driver installer and existing package checking into a single module
  • Combined host detection with GPU support checking into a single module
  • Revamped installation mode using command line arguments
  • Withdrew x86 libraries from the default installation mode
  • Added a new x86 libraries mode of installation for Xorg
  • Added integrated CUDA module for repository checking, adding and installing
  • Added support for FFMPEG acceleration using NVENC/NVDEC
  • Added dedicated privilege check for each installation mode
  • Added video hardware acceleration using VDPAU/VAAPI
  • Added support for installation of Vulkan renderer
  • Placeholder added for install everything mode of installation (Yet to be completed)
  • Converged all low-level module operations into a single file for speed
  • All print operations have been replaced by click-echo for optimization
  • Added checks for NVIDIA repository and RPM Fusion repository availability
  • Added network availability check before pinging respective repo servers
  • Improved handling of interrupt . halt and suspend system calls for tool

The tool now functions differently based on the command line modes.

Modes of installation
Active internet connection and superuser privilege is required to execute the following installation modes.
- sudo ./NVAutoInstFedora32 --rpmadd
This mode enables the RPM Fusion NVIDIA drivers repository.
- sudo ./NVAutoInstFedora32 --driver
This mode simply installs the NVIDIA drivers (with x86_64 deps only). Enabling the RPM Fusion NVIDIA drivers repository is mandatory before doing this.

  • sudo ./NVAutoInstFedora32 --x86lib
    This mode installs only the x86 libraries for Xorg. Enabling the RPM Fusion NVIDIA drivers repository and installing the basic drivers are mandatory before doing this.
  • sudo ./NVAutoInstFedora32 --nvrepo
    This mode enables the official NVIDIA repository for CUDA software.
  • sudo ./NVAutoInstFedora32 --plcuda
    This mode installs only the CUDA support softwares. Enabling the RPM Fusion NVIDIA drivers and NVIDIA official repository, and installing the basic drivers are mandatory before doing this.
  • sudo ./NVAutoInstFedora32 --ffmpeg
    This mode installs only the FFMPEG accleration. Enabling the RPM Fusion NVIDIA drivers repository and installing the basic drivers are mandatory before doing this.
  • sudo ./NVAutoInstFedora32 --vulkan
    This mode installs only the Vulkan renderer. Enabling the RPM Fusion NVIDIA drivers repository and installing the basic drivers are mandatory before doing this.
  • sudo ./NVAutoInstFedora32 --vidacc
    This mode installs only the VDPAU/VAAPI acceleration. Enabling the RPM Fusion NVIDIA drivers repository and installing the basic drivers are mandatory before doing this.
  • sudo ./NVAutoInstFedora32 --getall
    This mode installs all the above packages. (Not been implemented yet)
  • sudo ./NVAutoInstFedora32 --cheksu
    This mode allows you to check the current user privilege level. You can use this tool effectively only when you have logged in as a root or sudo user.
  • sudo ./NVAutoInstFedora32 --compat
    This mode allows you to check your hardware and host compatiblity. The tool would check your hardware and host and tell if your device is supported by the tool or not.
  • sudo ./NVAutoInstFedora32 --version
    This mode would show the tool version and exit out.
  • sudo ./NVAutoInstFedora32 --help
    This mode would show the help message and exit out.

This makes this tool almost comprehensive and complete after the fix made by v0.2.5 to remove the troublesome sleep time and kernel module read forcing. I had to work almost 12 plus hours a day to design, test and build the tool to the state it is currently in.

There are tons of issues to work on and any assistance in testing and building things is more than appreciated. Like I said before, I would like to pay equal amounts of attention to all the issues so feel free to comment under the issue you would want to work on.

Awesome @t0xic0der , As it's quite some time, you're here. Did you find something interesting to work on ?

P.S: I'm marking this ticket as Progress Check 1

Metadata Update from @nasirhm:
- Issue tagged with: C: Progress check 1

3 years ago

I was thinking we close this ticket. @toxic0der has a great idea of how
Fedora works and what they can do. :)

What do you think @t0xic0der?

Thanks for the check @nasirhm.

I have been lingering about and have found a lots of things to work on (some of which include working on the easyfixes one-by-one - starting with WordCloudBot, reviewing and writing docs on quick-docs, actively responding to questions on ask.fedoraproject.org and (trying to) package my tool into a COPR)

I am also preparing for the Git 101 with Pagure Fedora Classroom session that you must be aware about. :wink: (though it might take some time). I have discovered lots of places where I can be of assistance, though this never stops and I would certainly keep on discovering more.

The only way is up :smile:

Yes @ankursinha, I think I now know how Fedora works and what I can do.

(P.S. As there is stuff that I am doing apart from Document Writing, could you please modify the metadata before closing the ticket to note the same? Like the tasks I have picked and have been doing lately mostly fall under App Development, Infrastructure, QA and Packaging.)

Feel free to go ahead and close the ticket. :smile:

Great @t0xic0der
I hope you will have great satisfactions in your contributions.
I'm happy you are here.

Metadata Update from @alciregi:
- Issue tagged with: I: App development, I: Development, I: Infrastructure, I: QA

3 years ago

@ankursinha, @nasirhm, @hhlp, everyone.
There is a point.
@t0xic0der is now contributing, he knows a lot about the community, he is doing a great work, but... he is not CLA+1 (oh well, he actually is CLA+1, but because of fedora-join temporary membership). It is ok that everyone can contribute without being formally part of any team. But CLA+1 is required for various things in Fedora (voting, mail alias, etc.), but first of all, IMHO, it is a (maybe formal or bureaucratic) way for people to think, feel and say "hey, I'm part of Fedora".

In this particular case, I'd say that @t0xic0der is contributing to the Fedora Join SIG (with classrooms etc.) and so their temporary membership should be converted to a permanent one? I'd also support their sponsorship to the docs team, since they've worked with quick-docs. @t0xic0der : any preferences? :P

In general, though, you are right. i guess we keep the ticket open until the newcomers get added to another group to be CLA +1? But then we need to modify our process to make CLA+1 a goal then: we don't particularly focus on that yet, we're just happy for folks to contribute here and there.

Mmmh, I don't think it should be a goal.
However I think that teams should take care of this process. It is a formality, you can contribute without CLA+1, it is true, ok, but I think that it is an important aspect of the community (like badges).
Btw maybe this is not the right place to discuss this topic.

@ankursinha, @nasirhm, @hhlp, everyone.
There is a point.
@t0xic0der is now contributing, he knows a lot about the community, he is doing a great work, but... he is not CLA+1 (oh well, he actually is CLA+1, but because of fedora-join temporary membership). It is ok that everyone can contribute without being formally part of any team. But CLA+1 is required for various things in Fedora (voting, mail alias, etc.), but first of all, IMHO, it is a (maybe formal or bureaucratic) way for people to think, feel and say "hey, I'm part of Fedora".

Understandable. The temporary membership was provided during the elections so that I could vote. Being a part of a group, and (only then) being able to contribute kind of feels constricted.

In this particular case, I'd say that @t0xic0der is contributing to the Fedora Join SIG (with classrooms etc.) and so their temporary membership should be converted to a permanent one? I'd also support their sponsorship to the docs team, since they've worked with quick-docs. @t0xic0der : any preferences? :P
In general, though, you are right. i guess we keep the ticket open until the newcomers get added to another group to be CLA +1? But then we need to modify our process to make CLA+1 a goal then: we don't particularly focus on that yet, we're just happy for folks to contribute here and there.

Docs is certainly something that I started from but since then, I have been doing things here and there in Infra and Classroom (not being restricted to contribute in a single place as I follow "If you can, then you should" :smile:).

@ankursinha Is there a rule that being sponsored to one team makes you ineligible for another? For I would want to be (and contribute) in multiple areas, if at all it is possible.

Mmmh, I don't think it should be a goal.
However I think that teams should take care of this process. It is a formality, you can contribute without CLA+1, it is true, ok, but I think that it is an important aspect of the community (like badges).
Btw maybe this is not the right place to discuss this topic.

Something I had been doing so far. :grin:

(What is it going to be?)

A note to myself

Hey @t0xic0der
I think that we can close this ticket :-D
You are Fedora!

Metadata Update from @alciregi:
- Issue tagged with: C: Closed, S: I am Fedora

3 years ago

Metadata Update from @alciregi:
- Issue close_status updated to: C: Complete
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.