Make a public version of the milestone internal document about landing HOT 18 CLOSED

I need to discuss with @curquiza but as you all know, I don't like duplicating content so I would suggest a hybrid approach where everything we can share goes in this markdown, and the real private stuff (like when you give me one million euros to approve this PR) will go in Notion, what do you think?

from landing.

Yes, I don't like duplicated content either. However I started the private document for fun, I don't want this to become another responsibility for me just because I started to do fun stuff for Meili 🙂
I already know if it's too complicated for me (thinking every time "is it sharable or not?" + having two places to fill the information) I'll naturally stop doing it 😂
I can keep doing the one I currently fill because I like it, but we definitely need someone else to fill the public part 🙂

from landing.

@CaroFG are you comfortable enough in English to do the translation? In any cases, Tommy would review them before we merge.

from landing.

@ferdi05 could be great to have it next to the about us page in the landing, I agree :)

from landing.

This was an amazing activity!

from landing.

The translation of the Milestones in English I worked on was published on the Meili Handbook (private link) in September 2022. For reference, there's another version of the translation on Hackmd.io. If the Handbook becomes public, the Milestones may be published as a part of it too; at this time it's not planned to add the Milestones to the landing.

from landing.

I didnt translate everything yet but I sorted what could be public and what not ^^ https://www.notion.so/meilisearch/Publishable-milestones-f4b8ce4b18974baaa846576fae5d8a5a
I wonder how we will maintain this as I suspect curqui will update only the private one in Notion for now ^^

from landing.

Is there a lot of things that are private? As in do we need a private version?

from landing.

Not that much, since @curquiza started it for fun and she don't want to get this new responsibility if we do make this public we would need someone else to take ownership for the public version ^^

from landing.

I think it should be a company responsibility, like everyone can add items in it by doing a PR. WDYT?

from landing.

I'm afraid "everyone's responsibility" will become "no one responsibility". A lot of teams have this issue when requesting a team instead of a unique person on a PR for example. But maybe it's the best solution to start.

from landing.

@curquiza is it that more complicated for you to just do a PR for new things that can be public and forget the rest? I would assume we don't have news every week?

from landing.

P1 since we will need that information for the rebranding

from landing.

I can do it

from landing.

Perfect, thanks!

from landing.

I love this idea and @curquiza too. I think that would be great content for the new website.
Something I can work on with our new developer advocate, it's a funny way to tell the story of the company (additionally to what is done by the founder's team during the onboarding of new team members).

@qdequele wdyt?

from landing.

We translated it in bad English.
@shivaylamba should find a way to add images to it :)

from landing.

I should have given an update on this earlier.
A while ago, @davelarkan helped translate this document.
Since then, @laurenemeili said she would be interested in using it, and I sent her the document. I don't really know where things are at the moment, this could be worth considering adding to the landing. I will try to send this issue to the related repo.

from landing.