Marshall Cottrell

@CarminaBarreiro @gitlab We use @GoHugoIO with a modified Docsy theme: docsy.dev

Hello @marshall007 and @gitlab team. Could any of you tell me wich tool was used to do your handbook? handbook.gitlab.com/handbook/about…

@jschnatterer @stefanprodan @nagyviktor We can still dispatch git repository change notifications from kas to agents. Not sure what the path towards integration is yet. Perhaps a custom controller implementing `GitLabRepository` or maybe a native integration with provider-specific config on `GitRepository`.

@marshall007 @stefanprodan @nagyviktor The agent always stood out among other GitOps operators because it also allowed for pushing changes. While this might not strictly be GitOps, it sure was a pragmatic approach. So the future will be Flux for proper GitOps with pull principle and Agent for pushing changes to k8s?

Have some great news about @fluxcd and @gitlab. In todays dev meeting, @nagyviktor shared with us that GitLab has chosen Flux to offer #GitOps to their users. The Flux team is super excited about collaborating with GitLab 🎉 gitlab.com/gitlab-org/git…

@user_ops @ChrisShort @gitlab @fluxcd ArgoCD aims to be a complete end-user facing delivery solution. This includes its own APIs and web interface with features like user/project management, RBAC. This would all have to be reconciled with existing platform functionality, leaves very little headroom to add any value.

@ChrisShort @gitlab @fluxcd I'm surprised they picked flux considering argocd has a bigger userbase and more features 🤔

@jschnatterer @stefanprodan @nagyviktor We're still working out the technical details, but it's likely that we'll decouple the GitLab Agent from GitOps entirely. This will give users flexibility to use any tooling they wish, but our focus will be on providing a great experience around Flux.

@stefanprodan @nagyviktor How will this fit in with GitLab Agent for Kubernetes? Will flux be an alternative or will the agent use the GOTK?

Yesterday I helped my bestie Kira, a NASA employee in Houston, with this letter she wrote following passage of Texas’ abortion ban. Her ideas resonated with me & I think they are worth a read. Voices are stronger together, so if you can, share this to show your support.

Specifically looking for #Kubernetes engineers to help us build out our Zero Trust K8 Platform. We want to make it easier for @NASA to work with our international, commercial, academic and public partners. mricompany.applicantpro.com/jobs/1513520.h…

@spakhm Make sure you enable all the strictest compiler options right from the start. Easier to do it in a single pass and worth it in the long run.

@tayloramurphy @danielmintz @sethrosen @rob_ferguson It wasn't there intentionally, which is what I think @danielmintz meant. It was just embedded in the HTML of some web page we were scraping and we had to sanitize it out.

@danielmintz @sethrosen @marshall007 @rob_ferguson y'all remember how we found this or where it was?

Finally - the few weeks a year when your CSVs can be Christmastree separated values.

@mrkurt I find the same or worse to be true for AWS. They didn't even write their own ingress controller for EKS, it was first developed by Ticketmaster and CoreOS... and don't even get me started on that Open Distro for Elasticsearch shit.

The amount of work OSS devs are doing to support Apple is bonkers. I hope the people working on Brew and other tools are making an appropriate amount of money.

Next time you hear Zuck tell Congress content moderation "is a really hard problem" just remind yourself that Facebook can't even be bothered to translate their "Community Standards" to the native languages of all countries they operate in vice.com/en/article/xg8…

@eofpi @Usili1 @pilliarscreatio @eofpi fyi, we no longer redirect to presigned S3 urls. We proxy the downloads directly though the API now. Hope that helps and is less confusing for everyone! ex. ntrs.nasa.gov/api/citations/…

@Usili1 @pilliarscreatio @pilliarscreatio @marshall007 Corrected link should be this: ntrs.nasa.gov/citations/1972… which goes to the citation page, from which the one-time Amazon link can be obtained unique per user. It's a silly setup, but it's what the database needs, apparently.

A fair bit of information on Dyna-Soar in this paper - …s-prod.s3.us-gov-west-1.amazonaws.com/19720063745/19…

@eofpi @ArnieHolmes @NASA_STI @NASA @JimBridenstine @NASA_Marshall Yea we are working on returning exact counts for queries that return >10,000 results.

@marshall007 @ArnieHolmes @NASA_STI @NASA @JimBridenstine @NASA_Marshall The pagination fix is already a major improvement there back to the status quo, but I notice when I try very common search results like "moon base" or "mars mission" they always show the quantity as "of 10,000". Is this a software limit on how many results can be returned? 2/2

Did you know… @NASA has a public repository, the #NTRS: a world-class collection of scientific and technical information, growing with over a MILLION bibliographic records and full-text documents. Start exploring today! > go.nasa.gov/2HQy5Q5

@sirkut @ArnieHolmes @NASA_STI @NASA @JimBridenstine We are working on documenting the available search syntax but you can wrap your original query like so to accomplish what you are asking: (<original query>) + <refinement> Yea, we will be improving the filter UI across the board, particularly the date inputs.

@marshall007 @ArnieHolmes @NASA_STI @NASA @JimBridenstine Will you be bringing back the "search within the results" text box. That comes in real handy when your initial results are 300 and want to trim it down? Also, is it possible to make the date picker text editable? The user experience for it is pretty cumbersome.

@Robotbeat @SWGlassPit @TurbulentSphere @KevZag We do have a public API now as well. Full docs are coming soon but the OpenAPI schema definition is available here if anyone wants to play around: ntrs.nasa.gov/api/openapi-js…

@Robotbeat @SWGlassPit @TurbulentSphere @KevZag Hey guys, one of the devs here. I really appreciate the feedback. Many of the things mentioned in this thread have been addressed since the initial release. Feel free to reach out to me anytime. We intend to stay engaged with the community as we continue to make enhancements.

Ok, who fucked up NTRS?

@cyberpupk No worries, I totally get it (you can pry "old reddit" out of my cold dead hands) Would have loved to run both the old and new in parallel to solicit feedback... just isn't budget to do that. In fact, saving NASA money by eliminating licensed/proprietary software was a key goal.

@bahstgwamt @ToughSf We have a public API now! Full documentation is coming soon but you can get a sneak peak and view the OpenAPI schema definition here: ntrs.nasa.gov/api/openapi-js… We are also working on options for easily downloading full copies of the archive.

@ToughSf Fuck. Does the Archive have a full backup? Can we get them from there?

The NASA Technical Reports Server has been updated today. It brings a new format, easier search options... but you can no longer access more than the first 10 results?! Also, direct links to documents have been replaced with this sort of Amazon URL: …s-prod.s3.us-gov-west-1.amazonaws.com/19690014076/19…

@ToughSf @NASA_STI We have made further improvements to relevancy, pagination, and sorting this evening. See my reply in another thread regarding permalinks to documents: twitter.com/marshall007/st… We really appreciate your feedback! This is just the beginning!

It has now been fixed! You can access more than the first 10 results on the @NASA_STI NTRS server.