#Hi everyone! Iโve been following the
1 messages ยท Page 1 of 1 (latest)
hi!
i appreciate the contribution! soon I will make a general sort of "china tech" channel btw, our current approach is not scaling
let me explain my thoughts a bit
- i'm not based in mainland china and can't speak proper chinese (only HSK2 lol), so evaluating these platforms as a whole is hard for me
- my main goal herre is to get support for Chinese platforms up - first quickly, then reliably, as well as other fixes necessary to make it work well for mainland users (e.g. being resilient to flaky networks)
- i like the community support approach, and I think that (until we/i open a CN office ๐ ) this is the best way and fastest way to get everything online
sorry no, im tired and my throat hurts from yelling at clawcon last night ๐ ๐ ๐ฅฒ
sooo with that in mind, i dont really want to be in a place where I have to say X implementation is better than Y implementation - because I feel that neither option will please everyone, and therefore i prefer to collaborate on upstreaming features into the core repo for now
plus, i am too overwhelmed to assess correctly which option is better; so my preference is that the community can collaborate on finding the best way
does that make sense?
well i think the m1heng plugin is already a superset (just added some missing features), so merging it could be thought as a upgrade, not regression
well, it also makes sense to gradually add missing features to the upstream, i think that could also work, just a bit more time required
thanks for your guidance!
you're welcome! the way i am trying to think of it is not as person A's plugin or person B's plugin: but the community's implementation. this should be for all of us and all our users ๐
i think with AI this should be very easy honestly. if we say X is missing but Y plugin has implemented it, upstream the feature -> this should be a oneshot in a modern coding model