|
1 | 1 | <img src="https://repository-images.githubusercontent.com/384455580/fc80d841-e285-4238-981d-c40e45772469" alt="near-logo" width="600" border="0" /> |
2 | 2 |
|
3 | | -This repository is the data source for the community-sourced, core team curated NEAR Ecosystem page. |
| 3 | +# Ecosystem Organizations |
4 | 4 |
|
5 | | -**You can also use [this form](https://nearprotocol1001.typeform.com/submit-project) to submit a project to this database.** |
| 5 | +This document lists various NEAR ecosystem nodes and workgroups, their responsibilities and a way to contact them. |
6 | 6 |
|
7 | | -Our aim is to curate an accurate, up-to-date database of all entities in the NEAR ecosystem. Therefore, we have made this an open, community-driven repo which anyone can contribute to. |
| 7 | +Contributions: send PR to add your organization with responsibility and contact details. |
8 | 8 |
|
9 | | -This is a living, breathing document and repo that will evolve over time as the community helps to maintain the map going forward. |
| 9 | +## Nodes |
10 | 10 |
|
11 | | -# How To Contribute & Guidelines |
| 11 | +| Node | Responsibility | Contact | |
| 12 | +| [NEAR Foundation](https://near.foundation) | TBD | TBD | |
| 13 | +| [Pagoda](https://pagoda.co) | Development of various core components of NEAR ecosystem | - | |
| 14 | +| [NEAR Dev Hub](https://neardevhub.org/) | Supporting open source development on NEAR from developer education to maintaining core components | [Create proposl](https://near.social/devhub.near/widget/app?page=create-proposal) | |
| 15 | +| [Proximity](https://proximity.dev/) | Chain Abstraction go to market team | [Email](mailto:Hello@proximity.dev) | |
12 | 16 |
|
13 | | -We want to ensure the submission process captures as much information as possible pertaining to the entities added, while also remaining straightforward to contribute. |
| 17 | +## Work groups |
14 | 18 |
|
15 | | -All submissions to the NEAR Ecosystem are composed of two files: a Markdown file (.md), and a .svg or .png image. |
| 19 | +| Work group | Responsibility | Contact | |
| 20 | +| [Protocol Work Group](https://github.com/near/neps) | Responsible for decisions about NEAR blockchain protocol improvements and updates | [New issue](https://github.com/near/NEPs/issues/new) | |
| 21 | +| Infrastructure Work Group | Responsible for funding core infrastructure of NEAR protocol | TBD | |
16 | 22 |
|
17 | | -Adding a new entity to the ecosystem page only consists of two simple steps: |
18 | | -1. Create both a new markdown file in the `entities` directory with headers pertaining to each data field, and a detailed description of the entity outside the table |
19 | | -2. Add a new .svg or .png logo image in the `img` directory. (To upload a .png logo - 1. Fork 2. Upload 3. Create PR) |
20 | | - |
21 | | - |
22 | | -<b>Logo Submission Guidelines</b> |
23 | | - |
24 | | -All .svg/.png files must be 100x100px. Do not embed any excessive raster image files: svg file sizes over 500kb will be rejected. |
25 | | - |
26 | | -Below is an example submission for Skyward Finance: |
27 | | - |
28 | | -``` |
29 | | ---- |
30 | | -slug: "skyward-finance" |
31 | | -title: "Skyward Finance" |
32 | | -oneliner: "Enable fair token distribution and price discovery for projects built on NEAR Protocol." |
33 | | -website: "https://skyward.finance/" |
34 | | -app: "https://app.skyward.finance/" |
35 | | -whitepaper: "https://skyward.finance/whitepaper/" |
36 | | -twitter: "https://twitter.com/skywardfinance" |
37 | | -telegram: "https://t.me/skywardfinance" |
38 | | -discord: "https://discord.gg/KKjQwCRvbV" |
39 | | -medium: "https://medium.com/nearprotocol/everything-you-need-to-know-about-skyward-finance-before-the-first-token-sale-6e82fe305e1a" |
40 | | -github: "https://github.com/skyward-finance/" |
41 | | -ticker: "SKYWARD" |
42 | | -logo: /img/skywardfinancelogo.png |
43 | | -category: defi, app |
44 | | -status: launched |
45 | | -contract: skyward.near |
46 | | ---- |
47 | | -
|
48 | | -“Detailed description... (Up to 350 characters max)” |
49 | | -
|
50 | | -``` |
51 | | - |
52 | | - |
53 | | -### Markdown Headers |
54 | | - |
55 | | -Below are the available markdown headers for adding entities with guidelines for each header (only input what is applicable for what you are adding): |
56 | | - |
57 | | -- `slug`: The page URL that follows after near.org/ecosystem/ |
58 | | -- `title`: The title of the project |
59 | | -- `oneliner`: The one line summary |
60 | | -- `website`: A URL to direct users to the page |
61 | | -- `app`: A URL directly to the app |
62 | | -- `whitepaper`: A URL directly to white/lite paper |
63 | | -- `twitter`: A URL to the twitter page |
64 | | -- `telegram`: A URL to the telegram channel |
65 | | -- `discord`: A URL to the discord channel |
66 | | -- `youtube`: A URL to the YouTube channel |
67 | | -- `medium`: A URL to the medium page |
68 | | -- `github`: A URL to the github page |
69 | | -- `ticker`: Token ticker |
70 | | -- `logo`: A relative path to the corresponding SVG/PNG image |
71 | | -- `category`: A comma separated list of categories describing the project, see below for accepted list |
72 | | -- `country`: country/region of the guild |
73 | | -- `language`: native launguage of the guild |
74 | | -- `status`: 'building', 'launched', 'mainnet', 'testnet' |
75 | | -- `funded`: 'true' if project recieved a grant from NF |
76 | | -- `contract`: Project contract id |
77 | | -- `jobs`: Jobs available |
78 | | -- `community asks`: What they could use help with from community? |
79 | | - |
80 | | - |
81 | | -### Categories |
82 | | - |
83 | | -Available classifications for 'category' header: |
84 | | -Please add multiple tags if needed and include the header category as well. |
85 | | - |
86 | | -* 'partner' classification for if $NEAR is used on other networks for something |
87 | | - |
88 | | -| infrastructure | ecosystem | defi | funding | nft | gaming | app | guild | partner * | |
89 | | -| :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | :---: | |
90 | | -| exchange | education | amm | accelerator | marketplace | metaverse | | geographical | |
91 | | -| oracle | guild | dex | vc | | | | validator | |
92 | | -| wallet | marketing | stablecoin | grants | | | | ecosystem project | |
93 | | -| validator | devshop | lending | | | | | awareness | |
94 | | -| indexer | social | derivatives | | | | | theme based guild | |
95 | | -| analytics | utility | | | | | | education | |
96 | | -| tools | dao | | | | | | open web aligned community | |
97 | | -| payments | event | | | | | | service | |
98 | | -| | | | | | | | music | |
99 | | -| | | | | | | | art | |
100 | | -| | | | | | | | earn | |
101 | | -| | | | | | | | creative | |
102 | | -| | | | | | | | content | |
103 | | -| | | | | | | | social media | |
104 | | -| | | | | | | | swag | |
105 | | -| | | | | | | | growth hacking | |
106 | | -| | | | | | | | design | |
107 | | -| | | | | | | | trading | |
108 | | -| | | | | | | | legal | |
109 | | -| | | | | | | | development | |
110 | | -| | | | | | | | privacy | |
111 | | -| | | | | | | | data | |
0 commit comments