Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discord developer restructure #427

Open
Dr-Electron opened this issue Jun 9, 2024 · 3 comments
Open

Discord developer restructure #427

Dr-Electron opened this issue Jun 9, 2024 · 3 comments
Assignees

Comments

@Dr-Electron
Copy link

Dr-Electron commented Jun 9, 2024

To adapt to the current devs and future development we should think about a new concept on how to restructure the discord for developers

@Dr-Electron Dr-Electron self-assigned this Jun 9, 2024
@Dr-Electron Dr-Electron converted this from a draft issue Jun 9, 2024
@Dr-Electron Dr-Electron moved this from Product Backlog to Sprint Backlog in Developer Experience Jun 9, 2024
@Dr-Electron Dr-Electron moved this from Sprint Backlog to In Progress in Developer Experience Jun 9, 2024
@Dr-Electron
Copy link
Author

Current structure:

DEV COMMUNITY/
├── development
├── zebra-community-dev
├── php
├── stack-exchange
├── hardware
├── javascript
├── java
├── python
├── nft-marketplace
└── developer-lounge
NODE SOFTWARE/
├── hornet-node
├── iota-core/
│   └── iota-core
├── wasp-shimmer-ops
├── nodesharing
└── chronicle-discussion
SMART CONTRACTS/
├── smart-contracts/
│   ├── isc-discussion
│   ├── evm-contract-dev
│   └── wasm-contract-dev
└── tokenization-framework
GITHUB FEEDS/
└── Keep as is
IOTA PROJECTS/
├── iota-sdk
├── identity
├── oracles
├── explorer
└── Meeting Room
DEVEX AND EDUCATION/
├── iota-wiki
├── iota-wiki-discussion
├── iota-on-wikipedia
└── Wiki - lounge

My proposal:

DEV COMMUNITY/
├── general
├── iota-sdk
├── identity
├── iota-wiki
├── stack-exchange
└── developer-lounge
NODE SOFTWARE/
├── hornet-node
├── iota-core
├── wasp-shimmer-ops
└── nodesharing
SMART CONTRACTS/
├── general
├── evm
└── wasmvm (probably can be removed for now or kept a thread.)
GITHUB FEEDS/
└── Keep as is 

So let's remove unused channels, move threads to channels and also keep Move in mind

@Phyloiota
Copy link

I would even suggest to go further:

  • Rename the category from "Dev-Community" to "Developers"
  • Name it "Dev-general" to avoid confusing it with the normal "general."
  • remove stack exchange (no one uses it, does not need or deserve its own channel)
  • probably integrate SDK into the "dev-general" or create a "Wallet dev" channel that involves Firefly development and SDK development-related topics
  • Rename IOTA Wiki to "Documentation-Wiki"
  • Agree to just let the WASM thread get quiet but not give it a new channel
  • same here, name it "SC-General" instead of only general
  • And "EVM - Dev" instead of EVM

@Dr-Electron
Copy link
Author

Dr-Electron commented Jun 10, 2024

  1. Yeah we can do that
  2. I thought about just keeping the name development. Makes more sense.
  3. We should really focus more on stack exchange, now that we have a bigger team. At least for indexing questions imo
  4. Please don't. These are different topics. Especially in the future when we have smart contracts, there will be people that we need to forward to smart contracts and others that will use the SDKs to interact with these contracts 🤔 . And what is Firefly development?
  5. Good point. I thought I called it something like iota-wiki/documentation, but seems like I forgot that
  6. 👍
  7. Fine to me
  8. Also works for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants