text stringlengths 0 2.67k |
|---|
[1712.60 --> 1719.10] continuously improving our security posture and you know being diligent to keep on top of that stuff |
[1719.10 --> 1723.32] i think that's really cool because i think people only think about security when something goes wrong |
[1723.32 --> 1730.38] you know and the fact that like more and more people are i feel like champion opening source but like |
[1730.38 --> 1736.26] maybe it is harder when people are all working for different companies and working for you know |
[1736.26 --> 1742.18] trying to like beginning people trying to learn how to like contribute to open source and you've got |
[1742.18 --> 1747.02] people from all over the world and it kind of gives you like a nice measurement for everybody to kind of |
[1747.02 --> 1755.06] look over into like a goal to meet for security you know it does and i think it introduces a new set of norms |
[1755.06 --> 1764.24] about how projects are expected to work so if we look at contributing to open source it can be a very uneven |
[1764.24 --> 1770.76] process at the moment every different open source project has got a different set of customs a different |
[1770.76 --> 1777.54] approach to doing continuous integration different standards around you know what they expect to see |
[1777.54 --> 1784.26] and commit messages and and that sort of thing and i think one of the the things that scorecard |
[1784.26 --> 1790.90] will hopefully achieve here is as more and more people are adopting scorecard it'll level things out |
[1790.90 --> 1797.36] a little bit in terms of common approaches are typically going to be needed to achieve good scores |
[1797.36 --> 1804.02] so then as you're moving from one open source project to another you'll find that they're doing things |
[1804.02 --> 1811.02] in similar ways and it's you know kind of less of a learning curve to continue that open source |
[1811.02 --> 1815.26] contribution journey that's a really good perspective i do want to give a little bit idea |
[1815.26 --> 1820.28] here for like people that like what what is this cli i literally just downloaded and installed the cli |
[1820.28 --> 1825.90] and ran it against i have a bash scheduler for kubernetes like it's just it's written in bash it's like |
[1825.90 --> 1831.46] 100 lines of bash and i ran it i'm like what what is my score for this thing that i've never touched the |
[1831.46 --> 1835.84] repo on and it never tried to make it secure and it doesn't even have releases all that stuff and |
[1835.84 --> 1841.20] i got a 2.8 out of 10 so that'd be a red badge for sure and this would be good like i do not run |
[1841.20 --> 1845.54] this in production like this is not a thing that you should ever be trying but it's interesting seeing |
[1845.54 --> 1851.20] almost every one of my scores is either a question mark a zero out of 10 or a 10 out of 10 like i have |
[1851.20 --> 1855.76] nothing in the middle nothing of like oh like you're okay on this which is kind of interesting |
[1855.76 --> 1860.16] where it's like i have zero vulnerabilities i got 10 out of 10 there's no vulnerabilities in my bash |
[1860.16 --> 1865.36] code no known vulnerabilities in my bash code and that's kind of amazing right there when i think about |
[1865.36 --> 1872.76] it um but in like contributors is another one which is an interesting thought for how does something |
[1872.76 --> 1878.48] become secure with contributors and in this case in just the cli output it says there's how many |
[1878.48 --> 1884.72] different organizations have contributed to this repo and my bash repo has four different organizations |
[1884.72 --> 1890.42] found two four different people have contributed to the tool so it's like oh that's actually pretty |
[1890.42 --> 1895.00] good like for what this is like you're it's not one company it's not one org it's four different |
[1895.00 --> 1899.94] people have actually uh committed code to this so that's kind of neat yeah some of the checks are |
[1899.94 --> 1906.30] really binary you either pass them or fail them but others are very much more on some kind of spectrum |
[1906.30 --> 1913.12] so one of the checks is open ssf best practices and you might see it there is cii best practices |
[1913.12 --> 1918.92] which is this huge questionnaire which feels to me like it's somewhat aligned with something like the |
[1918.92 --> 1924.30] nist cyber security framework so there's lots and lots and lots of stuff in there including the kind of |
[1924.30 --> 1930.18] you know run over by a bus problem of have you only got one maintainer for this thing or have you got |
[1930.18 --> 1936.06] a bunch of people that can step in to look after it the score for that is you know kind of five if |
[1936.06 --> 1941.50] you get passing and then i think seven if you get to silver and then ten if you get to gold and zero if |
[1941.50 --> 1947.64] you haven't tried anything and zero if you haven't even started but i think you can get a three for being |
[1947.64 --> 1953.42] in progress so if you've if you've completed a bunch of the questionnaire you're not passing yet but at least |
[1953.42 --> 1958.16] you're trying to get there it's interesting here seeing just like what is because like i don't have |
[1958.16 --> 1961.62] a license file in this repo which i should i generally put license files but i don't have a |
[1961.62 --> 1967.64] license file so it's a zero uh fuzzing zero maintained zero but i also have no packaging |
[1967.64 --> 1972.50] there's no binary so i have no binary artifacts which is a 10 i was like hey cool you have you don't |
[1972.50 --> 1977.60] have any binary so this is a good thing because we can see all the code available in the repo so it's |
[1977.60 --> 1982.40] interesting yeah because you could i don't want to say you could game this but i could not run this on |
[1982.40 --> 1986.16] certain things uh to make sure like oh you know what like i don't want to have to deal with that |
[1986.16 --> 1990.54] right now i mean just like you were saying to get the eight score like i could pick and choose the |
[1990.54 --> 1994.76] things that are going to get me a better average to get me to that eight point of saying like hey |
[1994.76 --> 2001.06] this has again those best practices these are the things that as of today in 2024 this is a good idea |
[2001.06 --> 2005.56] for you to have and let's make sure that you have those things in place and we'll give you a decent |
[2005.56 --> 2010.36] enough score so people can trust that you're at least doing the basics so gaming's an interesting |
[2010.36 --> 2017.20] aspect to this so you know one challenge for us was our docs repos how do you do ci against a docs |
[2017.20 --> 2022.50] repo what sort of testing should you be doing there and you have to be a little bit creative with this |
[2022.50 --> 2028.82] so what we've ended up doing in that particular case is we have a markdown linter as one of the ci |
[2028.82 --> 2035.12] checks initially i kind of felt a little icky about it because it's like oh i'm just putting that in there to |
[2035.12 --> 2039.12] make sure that you know we've got something that's checking the box so that we can get our nice |
[2039.12 --> 2046.14] green badge but actually it's ended up changing the culture of the organization around how we use |
[2046.14 --> 2049.98] markdown and people are starting to lint their markdown even in the repos where we've not done |
[2049.98 --> 2056.92] that because it's become the norm to lint markdown and actually the markdown is all really nice now |
[2056.92 --> 2063.52] and really consistent rather than as it was before i also really think that maybe this could be a gateway |
[2063.52 --> 2067.74] into contributing to open source because when you first start wanting to contribute to open source |
[2067.74 --> 2072.48] you're like well what do i even contribute like how do i even and the fact that you know something |
[2072.48 --> 2079.08] as simple as like fixing docs or you know linting stuff or you know maybe if there are like low-hanging |
[2079.08 --> 2083.80] things that you could do and contribute to make the scorecard better could be somebody's first couple |
[2083.80 --> 2089.30] contributions you know because it helps you figure out where to implement these things and then you can |
[2089.30 --> 2094.04] go and figure out how to do that you know so there's like a lot of debate about like how to get into |
[2094.04 --> 2099.66] open source right now and how to do your first contribution so maybe scorecard gives not only |
[2099.66 --> 2105.42] the best practices that we start to learn you know but also is a new way for the next generation of |
[2105.42 --> 2109.48] people that want to contribute to open source and then they can start that journey with best practices |
[2109.48 --> 2116.30] yeah and i always encourage people to start with the documentation prs and i think it's so frequently the |
[2116.30 --> 2124.30] case that uh the creator of a project and especially sort of small projects it worked on their environment |
[2124.30 --> 2131.58] and they've tried to document it as they think somebody you know needs to for using it but you come along |
[2131.58 --> 2136.64] and try and use it you know let's say it's a ruby project you find that there's a whole bunch of gems |
[2136.64 --> 2142.12] that you need that they had on their laptop but that weren't actually documented and so you can then |
[2142.12 --> 2147.20] make a contribution to readme to say you know dependencies you actually need to install these |
[2147.20 --> 2152.30] gems and then it's going to work and that's going to be really useful for the next person coming along |
[2152.30 --> 2156.36] wanting to use that that's such a good thought too because how many times have you tried a project or |
[2156.36 --> 2160.20] done something and then it doesn't work the way that you think it is and it's like so frustrating |
[2160.20 --> 2165.80] but that's really an opportunity to for one make better software for the next person but also be that |
[2165.80 --> 2171.18] contribution to open source so that's really good perspective yeah we've done hacktoberfest for the last few |
[2171.18 --> 2176.26] years and it was a bit different this past year because of the not giving away t-shirts anymore |
[2176.26 --> 2183.00] i saw you know less activity as a result of that i didn't know they'd stop the t-shirts yeah i know it |
[2183.00 --> 2188.90] was kind of positioned as being a sustainability thing that they didn't want to be using all the cotton |
[2188.90 --> 2194.60] and mailing them t-shirts all over the world but yeah i did like the t-shirts um you know even though |
[2194.60 --> 2200.60] they gave people options previously to have a tree planted or whatever instead yeah i chose the t-shirt |
[2200.60 --> 2208.20] but um past years i've been entirely happy with people coming along with you know typo corrections |
[2208.20 --> 2214.68] on readmes and stuff like that to to score a commit for their uh hacktoberfest that's absolutely fair |
[2214.68 --> 2220.88] game and i think there's a little bit of gatekeeping sometimes happens around that of oh it's not a |
[2220.88 --> 2226.34] you know a serious contribution because i even if you're putting a full stop in the right place to |
[2226.34 --> 2232.38] correct something it's good enough for me i feel like docs do not get enough like having good |
[2232.38 --> 2237.00] documentation is so underrated and it helps people to use your product like you can have the best |
[2237.00 --> 2242.56] product ever but if it's hard to use people aren't going to use it you know so i feel like people should |
[2242.56 --> 2247.76] appreciate people that write good documentation and add to documentation because like you said like |
[2247.76 --> 2251.72] people have been usually when you're building something you've been using that technology for a |
[2251.72 --> 2257.30] while you know or you're so deep in it that you can't see what you need or what you know like how |
[2257.30 --> 2263.10] to explain it and having a new person come behind you or a new engineer on your team try to use |
[2263.10 --> 2269.88] something is so important because it's so easy to assume knowledge you know it's a context right it is |
[2269.88 --> 2275.88] that like how much do i need to know ahead of learning this and there's a lot of assumptions in |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.