Bug 1685051

Summary: New Project create request
Product: [Community] GlusterFS Reporter: Aravinda VK <avishwan>
Component: project-infrastructureAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: mainlineCC: atumball, avishwan, bugs, dkhandel, gluster-infra, mscherer
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-10 13:25:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aravinda VK 2019-03-04 09:11:44 UTC
Description of problem:

Please create a new project under Github Gluster organization

Name: devblog
Description: Gluster Developer Blog posts
Admins: 
    @aravindavk  Aravinda VK
    @amarts      Amar Tumballi

Comment 1 Deepshikha khandelwal 2019-03-04 09:26:26 UTC
Done.

Comment 2 Aravinda VK 2019-03-04 09:36:31 UTC
Thanks

Comment 3 M. Scherer 2019-03-04 10:09:27 UTC
Wait, what is the plan for that ? 

And why isn't gluster-infra in the loop sooner or with more details ?

Comment 4 Amye Scavarda 2019-03-04 16:20:18 UTC
I have concerns. 
What is this for?

Comment 5 Aravinda VK 2019-03-05 03:00:32 UTC
This project is for hosting Developer blog posts using Github pages. Developers are more familiar with Markdown format to write documentation or blog post, so this will be easy to contribute compared to using UI and write blog posts.

Based on discussion with other developers, they find it difficult to set up a blog website than writing. This project aims to simplify that

- Official Gluster org blog continue to exists to make announcements or release highlights or any other blog posts
- This will only host developer blog posts(More technical, developer tips, feature explanation etc)

Comment 6 Amye Scavarda 2019-03-05 04:31:03 UTC
This is exactly what should be on gluster.org's blog! 
You write wherever you want, we can set WordPress to take Markdown with no issues. 
We should not be duplicating effort when gluster.org is a great platform to be able to create content on already. 
We should get a list of the people who want to write developer blogs and get them author accounts to publish directly on Gluster.org and publicize from there through social media.

Comment 7 Amar Tumballi 2019-03-14 07:34:23 UTC
Amye,

> This is exactly what should be on gluster.org's blog! 

I guess there were a lot of question about where to write blogs from many gluster developers in office, and hence the request for this.

> You write wherever you want, we can set WordPress to take Markdown with no issues. 
> We should not be duplicating effort when gluster.org is a great platform to be able to create content on already. 
> We should get a list of the people who want to write developer blogs and get them author accounts to publish directly on Gluster.org and publicize from there through social media.

The way I liked the github static pages is, developers are used to local md (or hackmd way of writing), and the process of doing git push. This also allows some of us to proof read this, and merge. And considering there are already available tools/themes for this, this shouldn't be hard to setup.

Whether this is going to be a long term solution? Don't know, but having this option increases possibilities of people posting is what I thought.

Comment 9 Red Hat Bugzilla 2023-09-14 05:24:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days