what is it and what is the why behind it?
this is somehow a byproduct of medx. this is not an independent thing. this is medx, from the inside. but why we're pursuing it? does it come from an idea outside of medx? no. we pursue it because one of our principles is that we're open. open startup, open source, open x, y, z. so we should apply that principle to organizational communication. why? because as we go ahead, we'll have more and more stakeholders (including users, outside contributions, team members, investors, etc) and these people need to know about medx. but without a solution, they'll be bored or even confused about medx and this is going to solve their problem. we also need to tell medx's stories, before others. so we write monthly reports to whom may it concern.
who is gonna do it? is there a way to contribute?
i myself will do all of its work and nobody has to be in. but if you're interested, you can contribute to the "inside medx." newsletter and telegram channel by sharing your stories as medx contributors. i will share them with inside medx channels and you'll be seen. share your experiences about things you do in medx, from solving the problem to even a single outside collaboration you do, anywhere you want with any type of content you prefer. i will reshare it with the "inside medx." telegram channel and newsletter and this is gonna be huge.
FAQs:
should we write in english? -- no. write how you want, in persian or in english or any other language you prefer.
--------- caution:
if you created your medx-related experiences, please tell me here, right under this message in this issue. I'll just check here and publish them, regularly.
responsible: @sinusealpha deadline: life-time description:
what is it and what is the why behind it? this is somehow a byproduct of medx. this is not an independent thing. this is medx, from the inside. but why we're pursuing it? does it come from an idea outside of medx? no. we pursue it because one of our principles is that we're open. open startup, open source, open x, y, z. so we should apply that principle to organizational communication. why? because as we go ahead, we'll have more and more stakeholders (including users, outside contributions, team members, investors, etc) and these people need to know about medx. but without a solution, they'll be bored or even confused about medx and this is going to solve their problem. we also need to tell medx's stories, before others. so we write monthly reports to whom may it concern.
who is gonna do it? is there a way to contribute? i myself will do all of its work and nobody has to be in. but if you're interested, you can contribute to the "inside medx." newsletter and telegram channel by sharing your stories as medx contributors. i will share them with inside medx channels and you'll be seen. share your experiences about things you do in medx, from solving the problem to even a single outside collaboration you do, anywhere you want with any type of content you prefer. i will reshare it with the "inside medx." telegram channel and newsletter and this is gonna be huge.
FAQs:
--------- caution: if you created your medx-related experiences, please tell me here, right under this message in this issue. I'll just check here and publish them, regularly.