-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add mention to Mdev@kbin.run magazine in README #425
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know if the "For developers" section is the best place to put it. Though I did not find a better suited place for it either...
if we're treating it as mbin equivalent of kbinMeta (which seems to be the case) then it would be rather counterintuitive if it's mainly focused for developers rather than the users. and for that I think it can stay in the contributing section. I'm not even sure if I understand this right... |
Right now it is in the "For developers" section. What I meant is basically I don't know if it is at the right place at the moment |
wait I'm quite sure I put this under the "Contributing" section? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My bad. Was weird appearance bug from GitHub, sorry
add a mention to Mdev@kbin.run magazine in README for discussions about mbin within fediverse although unofficial, it's the kind of place that means nothing if no people knows about it, especially when we don't have the luxury of flagship instance like kbinMeta@kbin.social have, and having to spread it essentially by word of mouth hinders its usefulness
000a661
to
55c8b22
Compare
add a mention to Mdev@kbin.run magazine in README for discussions about mbin within fediverse
although unofficial, it's the kind of place that means nothing if no people knows about it, especially when we don't have the luxury of flagship instance like kbinMeta@kbin.social have, and having to spread it essentially by word of mouth hinders its usefulness