docs: community docs for Repository creation and project donation #816
Conversation
I created an empty file for documenting the configuring release pipeline for both Nodejs and Non-Nodejs.
This folder will hold documentations for the new AsyncAPI community section
…i/website#903] This folder holds documentations for the new AsyncAPI community section
…/website#903) This folder holds documentations for the new AsyncAPI community section
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Co-authored-by: Lukasz Gornicki <[email protected]>
Dule-martins
requested review from
fmvilas,
quetzalliwrites,
derberg,
asyncapi-bot-eve and
thulieblack
as code owners
Dule-martins
changed the title
Dule-martins
changed the title
|
@Dule-martins, you have commits that don't belong to yours, you need to rebase your branch |
On it! |
I updated my branch and here is what happened |
There was a problem hiding this comment.
- please also remove https://github.com/asyncapi/community/blob/master/repository-settings.md in this PR
- accept my edits suggestions
forget about cleaning the commits history, I see you had some issues with it #852
luckily we squash and merge so your strange PR history should have no effect on master after we merge.
Accepted suggestion coming from @derberg Co-authored-by: Lukasz Gornicki <[email protected]>
Same action taken with this Co-authored-by: Lukasz Gornicki <[email protected]>
|
Hi @derberg I can seem to trace https://github.com/asyncapi/community/blob/master/repository-settings.md in this PR so I can remove it. |
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Description
I removed the Donate-a-project.md file and included the suggested example on how to donate an existing project and also how to start a new project under AsyncAPI
Here is a suggestion made by @derberg "this document can be removed and instead, in Getting-a-new-AsyncAPI-repository-approved.md file just add a note that https://github.com/orgs/asyncapi/discussions/223 is an example project that shows how donation of existing project looked like and https://github.com/orgs/asyncapi/discussions/300 is an example of new project started under AsyncAPI"
Related issue(s)
Resolves #903