RITlug / tasks

Real-life issue tracker for tasks, goals, and objectives for RITlug
https://ritlug.com
Creative Commons Attribution Share Alike 4.0 International
6 stars 1 forks source link

Write a blog post on TigerOS recap / overview of Flock 2018 #15

Closed jwflory closed 6 years ago

jwflory commented 6 years ago

Summary

Writing about TigerOS in the public is important to build awareness. We should establish a precedent for regular blog posts / updates about TigerOS.

Description

This could be done in a few different ways.

Our own blog

We could host our own blog, like blog.ritlug.com, where we could write content about the club to share with the world.

Pros:

Cons:

Personal blogs

Team members can use their own personal blogs for updates about TigerOS.

Pros:

Cons:

Publishing elsewhere

We could use sites like Fedora Magazine or Opensource.com to talk about the work we're doing with TigerOS.

Pros:

Cons:

Assignees

I'm assigning this to @axk4545 primarily to take into consideration as Project Coordinator. This is important for TigerOS planning and he should discuss with the team to figure out frequency and what works best for the team.

I'm also assigned to this issue to help support and coordinate the promotion of written material on TigerOS.

Tjzabel commented 6 years ago

@jflory7 sounds like a great idea! Would be a good way for newcomers to glance over the changes we have made in a more readable format.

ct-martin commented 6 years ago

Personally I think we should have the blog on the new (WIP) TigerOS website, similar to how the RITlug one is now, except that we have a static homepage

jwflory commented 6 years ago

@Tjzabel Agreed. It also has the benefit of bringing more exposure for the project, which helps both the project and the people involved with it. I see this as a helpful way to grow awareness too.

@ct-martin If we did host it ourselves, we'd probably need to host it separate from the WIP project site. If we're self-hosting, I'd prefer a WordPress installation on Titan. However, I'm most in favor of the third option of publishing elsewhere.

jwflory commented 6 years ago

We decided to pick back up on this in the spring.

Tjzabel commented 6 years ago

I am thinking we can release a TigerOS intro in September or so, which is when we are planning on having our official working Beta release.

Thoughts?

axk4545 commented 6 years ago

FWIW I wrote one post of my own on TigerOS. It is at https://axk4545.me/2018/03/28/TigerOS/

On Sun, Apr 15, 2018, 3:19 AM Tim Zabel notifications@github.com wrote:

I am thinking we can release a TigerOS intro in September or so, which is when we are planning on having our official working Beta release.

Thoughts?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/RITlug/tasks/issues/15#issuecomment-381385769, or mute the thread https://github.com/notifications/unsubscribe-auth/ADUyLHRl0wv-eTZUbUKR5Lz-Fa67Ohkkks5tovRkgaJpZM4QCDrE .

jwflory commented 6 years ago

@Tjzabel I like the idea of drafting a new article to introduce the entire project around a beta release. We should aim to publish on Opensource.com. We can use @axk4545's as a reference and revisit for any information next semester.

jwflory commented 6 years ago

I talked with @Tjzabel about this. We decided to make this ticket focus on writing a development update about the TigerOS recap from Flock 2018. The format will be something like a 300-500 word blog post. If possible, we can post it as a static document to our website; otherwise, we can send it as an email to our list.

The goal is to have the write-up done before the end of September. The draft can start as a shared Google Drive document.

axk4545 commented 6 years ago

What about a guest post on your blog Justin?

On Sun, Sep 9, 2018, 10:39 PM Justin W. Flory notifications@github.com wrote:

I talked with @Tjzabel https://github.com/Tjzabel about this. We decided to make this ticket focus on writing a development update about the TigerOS recap from Flock 2018. The format will be something like a 300-500 word blog post. If possible, we can post it as a static document to our website; otherwise, we can send it as an email to our list.

The goal is to have the write-up done before the end of September. The draft can start as a shared Google Drive document.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RITlug/tasks/issues/15#issuecomment-419771038, or mute the thread https://github.com/notifications/unsubscribe-auth/ADUyLLGD-Pt3xdz1q34KPaVQfLrh6gD8ks5uZdDNgaJpZM4QCDrE .

jwflory commented 6 years ago

@axk4545 A guest post on my blog (or even the Fedora Community Blog) isn't a bad idea (since I can cross-post it to the Fedora Planet). We can review where to put it once the draft is written and we have clarification on #51.

jrtechs commented 6 years ago

Eboard Comment(9-10-18): @Tjzabel is going to draft the blog post in google drive sometime in September. We will then later decide where to post it and how to send it to club members as an announcement.

Tjzabel commented 6 years ago

After reassessing my September schedule, it seems highly unlikely that I will be able to fully complete this task during September. I will be able to at least jot down an overview or outline, but a full essay does not seem to be in scope for this month.

jwflory commented 6 years ago

@Tjzabel Given the conference is in August, I think it will be harder to write the post in October. Since this issue has been open for eleven months, I am going to close it and we can re-open or file a new ticket to discuss new writing opportunities later on. Since this is your ticket, feel free to reopen it if you really do want to work on it.