You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now KubeEdge has many examples, while they are not updated as soon as the new version release, which results in some examples fail to run and new users are confused about those failures.
Due to some examples are complicated and need more expertise, could kubeedge/examples only store repo links of those examples? On one hand, the example owner has more expertise to maintain it, on the other hand, it would be good for KubeEdge maintainers to reduce the maintenance burden and get more time to focus on new wonderful features.
In this way, users can always get available examples and quickly know how to play with KubeEdge.
Now KubeEdge has many examples, while they are not updated as soon as the new version release, which results in some examples fail to run and new users are confused about those failures.
Due to some examples are complicated and need more expertise, could
kubeedge/examples
only store repo links of those examples? On one hand, the example owner has more expertise to maintain it, on the other hand, it would be good for KubeEdge maintainers to reduce the maintenance burden and get more time to focus on new wonderful features.In this way, users can always get available examples and quickly know how to play with KubeEdge.
It is my idea, maybe not imperfect, WDYT?
@kubeedge/maintainers
Also, ping related examples writers @kadisi @edisonxiang @maurya-anuj @sujithsimon22 @m1093782566 @trilokgm @SupriyaSupu, if miss someone, please ping me and I will update ASAP :)
The text was updated successfully, but these errors were encountered: