Update issue templates epic<>milestone rename

[fryorcraken]

Trying to make things simpler and aligned with what the Insight dashboard can do:

In short, Key Milestones are historical milestones for the project that we will broadcast, celebrate and demonstrate key achievement to Waku's progress.
I suggest to clear up the existing "milestones" and keep the following:

• Launch of Waku Network Gen 0
• Quality Assurance processes are in place
  • extend the scope to js-waku, and all non-regression testing forms such as functional and performance
  • Likely achieved in 2024
  • Strong signal for the quality of the software, collaboration with DST and for mature projects
• Support Many Platforms
  • We can extend the scope based on a survey we will do. And this must include docs for each SDK and examples. To be achieved in 2024

See at the end for the proposed tidy up of existing milestones.

Future milestones are likely to be:

• launching first incentivization protocol on mainnet
• Fully decentralized store services
  Depending on the timing, this actually just be a "Waku Network Gen 1" milestone.

Each "X.X" item in waku-org/research#3 become an Epic with a corresponding issue in pm repo and a matching E:... label.
For example 1.2: Autosharding for autoscaling gets:

• issue in pm repo "1.2: Autosharding for autoscaling"
• label in all repos E:Autosharding
• Issue is added to GH milestone (in pm repo) "Waku Network Gen 0"

Then, work for each client is tracked with one or several issues in the client's repo.

For example:

• go-waku: "autosharding issue", it has label E:Autosharding assigned
• nwaku: autosharding,, it has label E:Autosharding assigned
• etc

---

Clean-up of current milestones:

• Support Many Platforms (key milestone for 2024)
  - Make it a key milestone
  • scope a number of languages (NodeJS, Python, C, Golang, Java?, Mobile platforms!)
  • Based on upcoming survey
  • Scope docs+example+library+docs
  • to be achieved in 2024
• First protocol to incentivize operators
  • replaced/becomes "Further milestones: Basic design for service incentivization" (epic of epics)
  • Will be part of a Key Milestone: incentivization protocol is mainnet/Waku Gen 1
• Dogfooding of RLN
  • close it, replaced with epics of "3. DoS Protection track"
• Execute an array of community growth activies
  • Close this one once all eco dev activities are tracked in notion
• Metrics
  • This becomes an Epic (not part of a key milestone)
• QA processes
  • Keep it as a milestone.
  • scope js-waku
  • scope non-regression performance test
  • Will be achieved in 2024
• peer management strategy
  • close this one
  • remaining work should be tracked under epics for Waku Network Gen 0
• Basic dev rel assets
  • Close this one once all eco dev activities are tracked in notion
• waku network supports 1 million users
  • close it, in favour of Waku network Gen 0 milestone (or it becomes it?)
  • 10k simulations are now part of the Waku Network Gen 0 milestone, as it is used to drive parameter selection for Waku network (e.g. number of members in RLN)
• Restricted-run protoocls are proudction ready
  • Close it once peer-exchange is done next week
• Waku network support 10k users
  • Close it once remaining work is done.

[fryorcraken]

Example:

Milestone: Waku Network Gen 0

• https://github.com/waku-org/pm/milestone/1
• [Milestone] Waku Network Gen 0 #50

Epic: 2.1: Production testing of existing protocols

• [Epic] 2.1: Production testing of existing protocols #49
• label E:2.1: Production testing of existing protocols

nwaku task (not an epic anymore): PostgreSQL stress testing and optimisation

• PostgreSQL nwaku#1888
• has label E:2.1: Production testing of existing protocols

[fryorcraken]

Remove epic of epics concept.
Now, weekly update can be done on any issue.

I also propose to remove "devex" and "maintenance" epic/issues (that we recently created).
Well defined labels (bug, api, documentation), should be used instead.

[jm-clius]

I think we're getting to something I can wrap my head around. Thanks! :)

[chair28980]

LGTM 🍏

[fryorcraken]

Remove epic of epics concept. Now, weekly update can be done on any issue.
I also propose to remove "devex" and "maintenance" epic/issues (that we recently created). Well defined labels (bug, api, documentation), should be used instead.

Are you making a comment on that?

[fryorcraken]

After the weekly update I'll play with the script see if I can do something useful when a weekly update can be in any issue. If so then I think we can go forward with this proposal.

[chair28980]

Are you making a comment on that?

Please disregard, I was going to quote reply and it failed to include my own text.