Create a new slogan for GitProxy

[maoo]

At the moment, the Git Proxy slogan on git-proxy.finos.org is "Deploy custom push protections and policies on top of Git".

I'd propose to update it, in order to stress more the power of running behind a corporate firewall; here's what I had in mind...

"Pluggable Git Pipeline that can run behind the corporate firewall"

What do you think? Shall we update it? Any ideas/suggestions?

[JamieSlome]

1. A secure framework for deploying and running server side push protections
2. A standard framework for implementing custom push protections
3. Ready to deploy server side push protections
4. A framework for running server side push protections securely
5. A framework for defining and implementing server side push protections

[maoo]

1. A secure framework for deploying and running server side push protections
2. A standard framework for implementing custom push protections
3. Ready to deploy server side push protections
4. A framework for running server side push protections securely
5. A framework for defining and implementing server side push protections

Like it! Few observations that I'd love to hear your feedback on:

1. maybe we can omit the "framework" part, as it may not be relevant whether it's a lib or a FW... I think we should focus more on the "end/net result"
2. I like the "server side" and "push protection" concepts, though for the latter I was wondering if "Git Pipeline" is something more generic, given that with git-proxy we could potentially manage notification use cases, rather than protection. I'd also like to convey the configurable/pluggable nature of this component.

[msagi]

Git Proxy: The guardian of your Enterprise embracing Open Source.
Git Proxy: Streamline your git compliance, effortlessly.
Git Proxy: Secure pushes, seamless compliance, no compromises.

[maoo]

Git Proxy: The guardian of your Enterprise embracing Open Source. Git Proxy: Streamline your git compliance, effortlessly. Git Proxy: Secure pushes, seamless compliance, no compromises.

Love them all, though I'd probably vote for the second.

Also like the third, however it's worth noting that if we want to try expanding into issues, PRs and comments, maybe the term "push" does not represent the full scope.

[JamieSlome]

I think this issue is quickly becoming "define a brand identity for Git Proxy".

Also thoughts on removing the space?

"GitProxy"

[JamieSlome]

I see your point about expanding the functionality to support issues, PRs and comments. That said GitProxy should try to be non-opinionated in so far as we can run all sorts of wild and wonderful plugins as code (and more) flows through, but ultimately, we are providing you with the toolset that makes it easy to choose, define and run those plugins.

This is why framework comes to mind. Wikipedia definition:

In computer programming, a software framework is an abstraction in which software, providing generic functionality, can be selectively changed by additional user-written code (our plugins), thus providing application-specific software.

Inspo 🤗

https://nuxt.com/

[msagi]

@maoo Re "to stress more the power of running behind a corporate firewall", can you give us a bit more context and details on the goal to achieve?.

I mean, who is the target persona the message is intended to connect to? E.g., if it is a developer then a "how technically cool, easy to use, innovative" type slogan can be a good message... vs if it is the OSPO lead or Head of platform then the value it brings would be better fit. Something like CircleCI.com - "Build anything fast. The CI/CD platform for the AI future.

Start for free. Scale without limits."

[maoo]

@maoo Re "to stress more the power of running behind a corporate firewall", can you give us a bit more context and details on the goal to achieve?.

I mean, who is the target persona the message is intended to connect to? E.g., if it is a developer then a "how technically cool, easy to use, innovative" type slogan can be a good message... vs if it is the OSPO lead or Head of platform then the value it brings would be better fit. Something like CircleCI.com - "Build anything fast. The CI/CD platform for the AI future.

Start for free. Scale without limits."

The value of running behind a corporate firewall is definitely targeted to OSPO/CIOs of financial institutions.

But after seeing all the very valid proposals that we're gathering here, I'm not sure this is something we should necessarily force into the slogan. On the other hand, I wonder if we should decide on the right "keywords" to use; I personally like "Pipeline" , "Open Source", "compliance", "security", "git" and "guardian", so taking inspiration from @msagi , these are just 2 examples on how these keywords can be composed:

1. Git Proxy: The guardian of your Open Source contribution pipeline
2. Git Proxy: Streamline security and compliance of your Git pipeline

WDYT of the keyword-driven approach? And what would be the keywords you'd choose?

[JamieSlome]

@maoo - agree with a keyword driven approach.

A couple more suggestions:

1. Control
2. Assess
3. Customise
4. Scan
5. GitOps

"Pipeline" is flip flop for me. It's extremely synonymous with CI/CD but Git Proxy introduces a whole process flow (pipeline) that isn't yet available to the DevOps market.

[maoo]

@maoo - agree with a keyword driven approach.

A couple more suggestions:

1. Control
2. Assess
3. Customise
4. Scan
5. GitOps

"Pipeline" is flip flop for me. It's extremely synonymous with CI/CD but Git Proxy introduces a whole process flow (pipeline) that isn't yet available to the DevOps market.

Thanks for the feedback @JamieSlome , I think we're making progress.

WDYT of adding flow to the list then? 😄

[maoo]

@maoo - agree with a keyword driven approach.
A couple more suggestions:

1. Control

+1

2. Assess

0 - less powerful than other keywords being mentioned IMO

3. Customise

+1 - though I'd also consider Pluggable as alternative

4. Scan

0 - less powerful than other keywords being mentioned IMO

5. GitOps

+1

"Pipeline" is flip flop for me. It's extremely synonymous with CI/CD but Git Proxy introduces a whole process flow (pipeline) that isn't yet available to the DevOps market.

Thanks for the feedback @JamieSlome , I think we're making progress.

WDYT of adding flow to the list then? 😄

[msagi]

@maoo @JamieSlome what comes to my mind for a "value statement": GitProxy provides "competitive advantage" for large enterprises in the financial services sector to "unlock value" from the Open Source ecosystem, in a "risk free", "compliant" and "easy to use" way.

[maoo]

@maoo @JamieSlome what comes to my mind for a "value statement": GitProxy provides "competitive advantage" for large enterprises in the financial services sector to "unlock value" from the Open Source ecosystem, in a "risk free", "compliant" and "easy to use" way.

I like it, as is; in the future we can reiterate, and I think this would make it a good first paragraph, to explain what GitProxy is in one paragraph.

I'd consider this as additional/parallel to the subtitle , though I'm ok to iterate on it in this issue; as @JamieSlome suggested earlier, it's all part of a branding identity exercise.

My 2 cents 😉