Skip to content
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

A blog post for building the ocaml gpt library #1478

Merged
merged 10 commits into from
Aug 23, 2023
Merged

A blog post for building the ocaml gpt library #1478

merged 10 commits into from
Aug 23, 2023

Conversation

PizieDust
Copy link
Contributor

As part of my outreachy internship, I have written this blog article on how I developed the ocaml-gpt library.

@PizieDust
Copy link
Contributor Author

cc @pitag-ha

@tmattio tmattio added the outreachy Outreachy contributions and blog posts label Aug 9, 2023
@tmattio tmattio requested a review from pitag-ha August 9, 2023 05:58
Copy link
Contributor Author

@PizieDust PizieDust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the corrections @tmattio 👍

@sabine
Copy link
Collaborator

sabine commented Aug 9, 2023

@tmattio @pitag-ha to me this implies the creation of an "Outreachy blog" that is hosted on OCaml.org. Is that the intention?

Currently, only the posts from the Opam blog are hosted on OCaml.org. I would be inclined to merge #1459 first, and then merge this blog post as part of a new "Outreachy blog" where Outreachy mentors, interns, etc. can publish blog posts.

@pitag-ha
Copy link
Member

@PizieDust and I have discussed a few days ago that he'll set up his own medium blog, move this post there, and link to the post from here (just as done for other Outreachy posts). We should have communicated that here.

If instead you prefer the "Outrachy blog on ocaml.org" solution, let us know, and we'll discuss it. It has both up- and downsides.

@sabine
Copy link
Collaborator

sabine commented Aug 10, 2023

Treating all the posts the same sounds reasonable to me. That's why I was wondering if you wanted to change how we handle the outreachy posts. Publishing elsewhere and adding a link is entirely fine

@christinerose
Copy link
Collaborator

christinerose commented Aug 21, 2023

Hi @PizieDust!

Great article! I went through and fixed any grammar/formatting discrepancies to match our style guide so as not to inundate you with comma, spelling, and capitalisation changes.

I did have one suggestions about writing MirageOS like this rather than "Mirage operative system." The other instances where you had Mirage, I changed to MirageOS, as I've been instructed that's the official way to write it. :)

Maybe we can get this ready for publication this or next week!
Oh! I see now it's not for publication on Tarides.com or OCaml.org? I think we published Outreachy posts on Tarides.com before. I'll double check with the Comms supervisor.

What do you think @sabine & @tmattio?

@PizieDust
Copy link
Contributor Author

PizieDust commented Aug 22, 2023

I created a medium account and will just port over the article on there and link to it from here, as most interns have done in the past.

https://medium.com/@playersrebirth/building-the-ocaml-gpt-library-650c00b4d72b

@christinerose
Copy link
Collaborator

I spoke with my team yesterday, and they like the idea of putting it on Tarides.com. We have published several intern blogs there before. Now that you've published it on Medium, I've checked in with my supervisor to see if we want to crosspost it or write a short introduction and link to it.

@sabine
Copy link
Collaborator

sabine commented Aug 23, 2023

Thanks @PizieDust! I'll be taking it from here and merging. Nice blog post!

@sabine sabine merged commit 66c13f6 into ocaml:main Aug 23, 2023
3 checks passed
@sabine sabine removed the outreachy Outreachy contributions and blog posts label Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants