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 .
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.
github.com/lens-protocol/LIPs/pull/37#issuecomment-1962175161