#195 Welcome to Fedora @cappyishihara!
Closed: C: Complete 2 years ago by alciregi. Opened 2 years ago by ankursinha.

Hello @cappyishihara ! 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! :)


Hello @cappyishihara
This is a simple check for this ticket. It's a while that it is not updated.
How are you? Did you find anything interesting?

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

2 years ago

Metadata Update from @alciregi:
- Issue untagged with: C: Progress check 1
- Issue tagged with: C: Progress check 2

2 years ago

Oh hey, I'm fine, thanks.

Hi, I'm Cappy Ishihara. I'm from Thailand and I'm most known for being the lead developer of Ultramarine Linux. A recent downstream RPM Fusion-based fork of Fedora Linux that tracks Fedora directly.

I look forward to helping out on the Release Engineering, the Build system, and other inner workings of Fedora itself, what makes Fedora Fedora, I guess. And maybe some package maintenance.

I'm also actually now part of the Pantheon SIG now shortly after this introduction was posted, so that's kind of nice.

Good! Very good.
So we can close this ticket, I guess.

Metadata Update from @alciregi:
- Issue untagged with: C: Progress check 2
- Issue tagged with: S: I am Fedora, S: Introduced myself

2 years ago

+1! Welcome to the community!

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

2 years ago

Login to comment on this ticket.

Metadata