Hello @gavin-zheng ! 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.
These links are a good read to begin with. 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:
Next, when you're ready, 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).
Finally, could you let us know how you learned about the Fedora project? Was it from a colleague, or social media, for example?
If you have any questions at all, please ask! We'll use this ticket to keep in touch! :)
In addition, could you provide some information to understand your requirements better? (You can write them in the introduction, or answer here if you feel more comfortable).
For example:
your experience with Free/Open Source Software (FOSS) communities/ecosystems:
your background/skills, for example:
your experience in communication platforms:
how much time are you looking to/are you able to spend on volunteering (approximate hours per week)?
Remember that this is not a job interview at all. This is just an icebreaker to help all your new friends get to know you quicker. The better we know you, the better we can support you in identifying Fedora activities that promise to be relevant for you.
Please write how much/whatever you wish. :).
Gavin's introduction on the list is here: https://lists.fedoraproject.org/archives/list/fedora-join@lists.fedoraproject.org/message/CCWMAD57NO7AMY32IZI57YCQYKLXZXIU/
Welcome Gavin, I've replied to you on the mailing list too. The idea of this ticket is to give you some information on how/what/where/why/when the community does things, and you can use to make notes, provide feedback, ask questions---whatever you wish. Please feel free to change the tags on the ticket and so on too. It's all for you to tinker with.
Metadata Update from @gavin-zheng: - Assignee reset
Metadata Update from @ankursinha: - Issue assigned to gavin-zheng
Thank you very much to ankursinha, he is very friendly. I have introduced myself on the mailing list, but I still need to make some additions.
First of all, I joined the Fedora community with great excitement, and this is my first attempt to fully participate in FOSS. Before that, I was more of an onlooker. My participation in open source was limited to raising issues (although this is also very important) or writing emails to the maintainers of open source software to tell them about the problems in their software, but I don't want to stop there. Joining Fedora gave me this opportunity. When others mention or use projects that I have participated in, I can proudly say: There is code written by me here! I think this is enough, and it is also my motivation to continue participating in open source.
As I said in my introduction, the operating system I use daily is not Linux, but macOS running on Apple Silicon, but this does not mean that I am clueless about the use of Linux.
I am very willing to write code or documentation for Fedora, and in my opinion, this is as important as the two of them.
I have a lot of experience using git, but I lack experience in rpm and testing, which stems from my lack of experience in programming projects, but I am willing to invest time to learn here.
Regarding the time to participate in community work, as I said in my introduction, I am a junior high school student from Hangzhou, China. The academic pressure in China is not small, which also means that I can only participate in community work on weekends. The time I spend on community activities is only about 4 hours.
At the same time, my native language is Chinese, which leads to my English not being as good as that of native speakers. I need to rely on translation tools to read documents, read conversations, and speak in many places. So if there is a problem with my words in the future and even cause misunderstandings, please tell me directly.
Finally, if you want to learn Chinese and understand Chinese culture and society, you can also chat with me, which will help us eliminate prejudices and cultural barriers between each other.
I have seen many tags starting with 'I' in tags, but I still have some questions about them. How can I further understand them?
Metadata Update from @gavin-zheng: - Issue tagged with: C: Needs response
Hi Gavin,
The "I" tags are stand for "interest", so they can be used to note in your ticket what you are interested in. For example, if you are interested in documentation, you can use the "I: Documentation" tag and so on. They sort of related to the different activities in Fedora. If you find something that doesn't have an "I" tag, do let us know and we can add it.
You write very well, by the way, so I wouldn't worry too much about it :)
Metadata Update from @gavin-zheng: - Issue untagged with: C: Needs response - Issue tagged with: I: Documentation, I: Translation
I noticed there's a channel related to Rust in the Project Teams, but I couldn't seem to find the corresponding tag that starts with 'I'.
There's one for it now :)
Metadata Update from @gavin-zheng: - Issue tagged with: I: Rust
Hi @gavin-zheng, just wanted to check in on how it's going? Did you happen to find a team you're interested in contributing to? If you haven't, is there anything we can do to help you or guide your decision?
Metadata Update from @markrosenbaum: - Issue tagged with: C: Progress check 1
I am currently in the channel of the localization team, and I am not sure if they have recognized me as an official member, but I have made some translation contributions. And I am also on Rust's SIG channel, but I haven't made any actual code contributions yet
That's great to hear! Glad you were able to find a team to contribute to!
Metadata Update from @markrosenbaum: - Issue tagged with: S: I am Fedora
Metadata Update from @theprogram: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.