Thoughts about the suricata style guide #24
Replies: 4 comments
-
IMO it seems the style guide would be a nice addition to the collection of "community held" information presented at sidallocation.org. If we end up going that route, I'll redo the look and feel of http://sidallocation.org to be a bit more github-like and a little less template-like. |
Beta Was this translation helpful? Give feedback.
-
I just wanted to expand/explain this a bit more:
My thought process around using a separate repo within the sidallocation Github org was largely based on understanding that a community style guide is a totally different effort/project than sidallocaiton. As such, it would likely have different contributors, have different permissions, workflows, issue templates, different and isolated discussion threads, etc. As a result, using a separate repo would allow for all of these things to occur. IMO, I like the idea of keeping it under "sidallocation" github org, but not connected to the current efforts' repo. I do like the idea of providing cross links between the two efforts on which ever webpages are published, etc. Either way, i think it's a great idea and am looking forward to seeing it done. thanks @travisbgreen for the continued push on it. |
Beta Was this translation helpful? Give feedback.
-
I agree that SID allocation and a community style guide are different efforts. However, would be nice if they could be managed under one umbrella github org. |
Beta Was this translation helpful? Give feedback.
-
Hey all, I think the major edits have wrapped up on the suricata style guide.
I had intended to add it as a markdown file to this repo and serve it as part of gh-pages here on the sidallocation.org repo, but in talking to @zoomequipd he mentioned a separate repo might be better.
What do you think, should this be a separate
repo
+gh-pages
or does it make sense to add it here?0 votes ·
Beta Was this translation helpful? Give feedback.
All reactions