HAVE FUN | SOFARegistry source code analysis

About SOFARegistry source code analysis series

The SOFARegistry source code analysis activity is an open source activity hosted by the SOFAStack team. We hope to create an active and transparent open source activity based on GitHub collaboration that everyone can participate in.

This event aims to enhance everyone's understanding and cognition of SOFARegistry, promote exchanges in the open source community, and allow everyone to better understand, learn and use open source projects. It is for everyone to learn and use SOFARegistry and communicate directly with the core developers of SOFARegistry. A good opportunity.

The articles produced by this event will be first published on the SOFARegistry project homepage, and will also be promoted online through omni-channels. Some of the sorted content will be published on the SOFAStack official blog and published in all channels.

Activity role division

• Initiator: responsible for operational collaboration
• Participants: All developers interested in community projects.
• Reviewer: dzdx , the core developer of the project, gives guidance and advice in source code analysis.

Reviewer is both a reviewer and a mentor, and is the core developer of SOFARegistry.

Activity flow

Activities are collaborative on GitHub. The flow chart is as follows:

• Participants log in to their GitHub accounts, and reply to [/assign] on the GitHub page of the source code analysis activity to claim the issue.
• The Reviewer assigns the issue to the corresponding participant.
• Participants submit PR within the specified time after claiming the issue successfully.
• Reviewer reviews submitted PRs.
• After the PR is approved, it will be published on the project homepage by the Reviewer.
• The participant closes the issue.

Rules Description

One person one issue

Each participant can only claim one issue at a time. For example, if you claim an issue by mistake, you need to close the issued issue before re-claiming it. One person can claim multiple times.

task classification

The difficulty of this task is divided into 3 levels

🌟、🌟🌟 quests are elementary

🌟🌟🌟 stars are medium

🌟🌟🌟🌟、🌟🌟🌟🌟🌟 are high-level stars.

issue submission deadline

• The initial issue is claimed and submitted within 7 days
• The intermediate issue is claimed and submitted within 15 days
• High-level issue claims must be submitted within 20 days

If the issue is not submitted after the expiration date, it will be regarded as abandoning the issue, and the issue will be re-assigned and claimed.

issue progress synchronization

The sponsor will keep track of the progress with the participants every week, and synchronize the progress of the activities externally through the "Financial-level Distributed Architecture" public account.

Activity Award

According to the community promotion rules:

• You can be promoted to Community Contributor after completing 1 preliminary task;
• Complete 1 entry level + 1 intermediate level to be promoted to Community Member ;
• Complete 1 high-level to be promoted to Community Member ;

Rights enjoyed by community Contributors: exclusive Contributor customized certificates (both electronic and physical), community gifts (T-shirts, sweaters, mugs, stickers, calendars, etc.)

Rights enjoyed by community members: exclusive membership certificates (electronic and physical), community gifts (T-shirts, sweaters, mugs, stickers, calendars, etc.)

After completing the source code analysis task of any difficulty, you can get the opportunity to choose your own books, books worth 100 yuan within , you can choose , each person is limited to one time.

title	Reviewer	Issue	difficulty
Overview	dzdx	#204
Lossless operation and maintenance	dzdx	#198	🌟🌟🌟🌟🌟
SlotTable	dzdx	#197	🌟🌟🌟🌟🌟
data synchronization	dzdx	#196	🌟🌟🌟🌟
publish subscribe push	dzdx	#195	🌟🌟🌟🌟🌟
data table monitor	dzdx	#203	🌟🌟
Data inverted index	dzdx	#202	🌟🌟
push switch	dzdx	#201	🌟🌟🌟
Communication data compression	dzdx	#200	🌟🌟
push delay trace	dzdx	#199	🌟🌟🌟

👏 Welcome to click the link below

View the task details to receive the task

Links 🔗: https://github.com/sofastack/sofa-registry/issues/20