Post by @stani • Hey

Interesting LIP to migrate LIPs from GitHub to CharmVerse https://github.com/lens-protocol/LIPs/blob/978a2bf068895a3a6d2670712d7baf8d17966c7b/LIPs/lip-14.m

Stats

Comments

Please. Idk what charmverse is but anything is better than GitHub right now. I have no clue what a commit is and I don’t think I ought to just yet.
Yes plz, GitHub UI is too technical for community-based discussions. Something easier to navigate will bring more conversation imo
I use charmverse for a while. It can be slightly improved if more people will use it and push them
I totally agree, github is not ideal for LIPs. I would like to see LIPs natively on lens though (instead of going to another third party tool). “As Lens Protocol is a neutral and flexible technology stack for social networking use-cases, LIPs provides the basis to ensure that Lens Protocol remains flexible and uniform across all potential use-cases, improvements and ideas within the community.” … and therefore the home for LIPs should be @lens/lens . **advantages**: (1) accessibility: literally every lens user can join discussions and add ideas without any barrier of entry. (Status quo: setup of a GitHub/Charmverse profile, getting used to the app and the (technical) workflow coming with the process currently implemented). (2) visibility: based on the amount of comments and the profiles participating in the discussions so far, LIPs will get an amazing visibility in the broader lens community. **to be improved**: LIPs won’t be easily accessible as soon as they are in the lower end of the feed. workaround: use of the #LIP hashtag eg #LIP14 . solution(s): #LIP15 ;-) full content search on lens. https://github.com/lens-protocol/LIPs/pull/37#issuecomment-1962175161
I agree with you, it is quite technical for anyone to use GitHub and we are losing out many good advice and proposals from many non-technical people who can help make @lens/lens much better than now. Even though GitHub is too technical it has enough tools for LIP kind of thing, so need to be sure before migrating to any such solution.