Discussion: How to contribute and integrate SRS. Make sure to maintain the markdown structure.

[qingmang]

Is there any plan to expand the development of the HTTP API, such as: managing the live streaming status through the API, creating and deleting live streams, providing a rich set of HTTP API interfaces to expand the SRS ecosystem, and allowing developers who are not familiar with SRS to participate? This would enrich the construction of various live streaming platforms formed by the SRS ecosystem.

TRANS_BY_GPT3

[winlinvip]

Generally, we don't discuss issues in the Issue section, but this issue involves the expansion of SRS and everyone's participation, and many friends may want to know about it. This is both a technical issue and a community collaboration issue, so I changed the title because it is not necessarily limited to HTTP-API, but rather the issue of how everyone can conveniently expand and participate in SRS.

I would like to discuss this topic in detail in several parts:

• Contribution: How to contribute to SRS and whether it is easy to participate in contributions.
• Extension: How to extend SRS and whether the technical architecture is easy to extend.
• Economy: How SRS interacts with open-source ecosystem projects and how to improve the capabilities of the SRS ecosystem.

Contribution

For English users, please follow Contribute.

First of all, we warmly welcome everyone to participate in the SRS community and build open-source projects together. Please understand that we are an open-source community without full-time staff, and our main time is spent on work, participating in open-source projects during business hours. Therefore, our response to issues may not be as timely as you might expect. Please do not treat other community developers like cloud service customer service. We are equal and in similar situations, so please remember that this is the most critical premise.

For Chinese developers at present (2022), participating in the open-source community requires understanding the background and working mechanism of open-source, as well as what contribution is and why we should contribute. In fact, for SRS, answering questions in the group, discussing technology, updating documentation, replying to Issues, looking at unresolved Issues together, improving code even if it's just a variable typo or comment, testing new versions and providing feedback, solving Issues, submitting Patches, submitting major features, maintaining modules, promoting and sharing SRS are all considered contributions, and are basically the steps to participate in the community.

If you want to submit an Issue or Patch, you first need to understand whether this is a problem that has been solved or does not need to be solved. Be sure to check the FAQ and Wiki first, which lists common issues. If you find that it is not in the FAQ, you can search for it in Issues and PR to see if it already exists. If you are sure it is a bug but there is no existing Issue or PR, you can submit a new one.

Note: It is important to note that Questions (such as inquiries and doubts) cannot be raised in Issues; Issues are limited to Features and Bugs. So where should we raise Questions? First, it is recommended to search in the FAQ, Wiki, Issues, and PRs. If you still have questions, you can join the live chat room, where you can find me every Saturday night. If it is determined to be a new question and not an existing issue, I will guide you to submit it to StackOverflow. Please remember not to submit directly to StackOverflow, as not all questions can be submitted.

Note: I would like to explain further that contributing to SRS, especially submitting code, seems to be quite cumbersome and not as simple as making a quick change and submitting it. Yes, the community is essentially a team, albeit a distributed, loosely organized team working during business hours. Please do not assume that the open-source community responds like cloud vendor after-sales service. However, this is precisely the fun of open source, isn't it? The entire community is very robust and continuously developing.

For new developers, it is strongly recommended to start by solving Bugs. You can take a look at Issues: good first issue. These Bugs are more suitable for new friends to participate in, and we have specially marked them. Then you can follow How to File PR to submit a Patch.

New developers should pay special attention to this point: submitting Bugfixes can quickly establish contact with us, adapt to each other's habits and working methods, and the way we treat code. In these aspects, we generally have different opinions, so submitting bugfixes is an easy way to get through this stage.

If you are a developer who has submitted bugfixes and wants to contribute to SRS during business hours, you can also contact me privately on WeChat, and I will give you more advice.

Once again, welcome everyone to participate. SRS is a project for all developers.

Extension

Extension.

Economy

Economy.