www-gitlab-com merge requestshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests2017-03-09T21:43:36Zhttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5274Update pets.yml2017-03-09T21:43:36ZJohn MayUpdate pets.ymlI probably messed this one up too!I probably messed this one up too!John MayJohn Mayhttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5300feature launch task suggestions2017-08-30T16:01:15ZChad Malchowfeature launch task suggestionscc @amaracc @amara๐ Job van der Voort ๐๐ Job van der Voort ๐https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5315Added Kubernetes topics to CI curriculum2017-03-27T16:34:28Zusername-removed-260236abuango@live.comAdded Kubernetes topics to CI curriculumThe existing CI Curriculum has the item: "Deploy your application to Kubernetes using the Docker container you built.", from the experience with my CI boot camp, I believe a brief background of Kubernetes is necessary before the stage. I...The existing CI Curriculum has the item: "Deploy your application to Kubernetes using the Docker container you built.", from the experience with my CI boot camp, I believe a brief background of Kubernetes is necessary before the stage. I have added Kubernetes topics related to CI/CD.
/cc @dewetblomerus @gl-supportLee MatosLee Matoshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5379Kubernetes curriculum2018-06-08T18:42:21Zusername-removed-260236abuango@live.comKubernetes curriculum/cc @gl-support
Based on materials I have encountered and discovered, I have put together this curriculum. Suggestions are welcome./cc @gl-support
Based on materials I have encountered and discovered, I have put together this curriculum. Suggestions are welcome.Lee MatosLee Matoshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5388Clarify that customer agreements and NDAs should be placed in SFDC2017-03-20T20:59:01ZPaul MachleClarify that customer agreements and NDAs should be placed in SFDCThis MR makes it clear that once both signatures have been obtained the executed doucment should be stored in SFDC.This MR makes it clear that once both signatures have been obtained the executed doucment should be stored in SFDC.Francis AquinoFrancis Aquinohttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5466Refresh license faq content2017-05-01T16:03:15ZRรฉgis Freyd (GitLab)Refresh license faq contenthttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5514Clarifying the deal types and steps for Submitting an Opportunity for Approval.2018-08-13T19:36:06ZSimon WilliamsClarifying the deal types and steps for Submitting an Opportunity for Approval.Just clarifying some of the language and the steps required before you can submit an opportunity for approval.Just clarifying some of the language and the steps required before you can submit an opportunity for approval.Francis AquinoFrancis Aquinohttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5546Update sales demo to align more closely with enterprise buyers2017-08-30T16:01:14ZAmara NwaigweUpdate sales demo to align more closely with enterprise buyersI've made the following changes to the demo script to address the feedback we received [in this doc](https://docs.google.com/document/d/1nK2kfZOaAXeV7cZ-0vBC8_93ndkIG6449i_YHvel14I/edit#)
The changes were focused on
* Adding more of a ...I've made the following changes to the demo script to address the feedback we received [in this doc](https://docs.google.com/document/d/1nK2kfZOaAXeV7cZ-0vBC8_93ndkIG6449i_YHvel14I/edit#)
The changes were focused on
* Adding more of a top level story that explains why integrated CI/CD is better. (this is in the new overview section that I suggest we start saying in our recorded demo to ensure that we are giving viewers context)
* Adding an explanation to features that we show in the demo
* Making certain a number of sections optional to focus our script on the things we think will most closely resonate with enterprises
* Making the project permissions and workflow management section mandatory since most buyers are buying us to consolidate and control their source code
Some of the changes I made would require edits to the demo environment and to other sections in the script
- [ ] The demo user should be an admin user so they have full control in the account
- [ ] Since we agreed to make the ChatOps section optional we'll need another way to deploy to production. Should we edit the CI YAML file to add production as an environment? This would give us the opportunity to talk more about the strength of our CI/CD offering.
- [ ] The review apps section only mention Kubernetes since we know k8s adoption is only just beginning should we mention some alternatives to running Review Apps on k8s. (No need to demo them but perhaps we should mention more common enterprise options.)
NICE TO HAVE: The demo would feel a lot smoother and more real if the demo environment was already setup and pre-filled with some things. Perhaps that is something we consider for a second iteration.https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5549Docker with bash functions test env2017-04-10T07:51:22ZDe WetDocker with bash functions test envThese instructions enable an ultra-quick way to pick the docker tag for a specific version and spin up a container from it.These instructions enable an ultra-quick way to pick the docker tag for a specific version and spin up a container from it.Lee MatosLee Matoshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5556simplify support regression escalation process2017-04-10T14:46:53ZLee Matossimplify support regression escalation processThe last iteration of this was a little wordy and duplicated things from the product resource. Removed the fluff and made it more direct and actionable.The last iteration of this was a little wordy and duplicated things from the product resource. Removed the fluff and made it more direct and actionable.Lee MatosLee Matoshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5691Update events.yml2017-05-12T16:43:21ZEmilyUpdate events.ymlEmilyEmilyhttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5705WIP: Vacancy description formatting2017-07-31T00:15:15ZSasha BannisterWIP: Vacancy description formattinghttps://gitlab.com/gitlab-com/www-gitlab-com/issues/1295https://gitlab.com/gitlab-com/www-gitlab-com/issues/1295Sasha BannisterSasha Bannisterhttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5739WIP: Implement a trademark policy2017-04-26T12:46:01ZDrew BlessingWIP: Implement a trademark policycc/ @pmachle @lbot
This is an early WIP. Input welcomed.cc/ @pmachle @lbot
This is an early WIP. Input welcomed.https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5761Adding additional opinions around 1on1 format, activities and purpose.2017-04-22T00:04:08Zusername-removed-301052Adding additional opinions around 1on1 format, activities and purpose.Hey @sashab & @stanhu, as promised I added a few thoughts related to 1:1s. Feel free to take all, part or none of itโI have no ego attached.
If you have feedback for me, I'm happy to take another crack at editing.
Thanks to both of yo...Hey @sashab & @stanhu, as promised I added a few thoughts related to 1:1s. Feel free to take all, part or none of itโI have no ego attached.
If you have feedback for me, I'm happy to take another crack at editing.
Thanks to both of you for making the time to meet with me today.https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5765add brent_caldwell to team page2017-04-22T23:51:04ZBrent Caldwellbcaldwell@gitlab.comadd brent_caldwell to team pageadd brent_caldwell to team pageadd brent_caldwell to team pagehttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5799WIP: Test gifs vs videos2017-04-28T22:32:59Zusername-removed-236961WIP: Test gifs vs videos## NOT TO BE MERGED
This is just a test for https://gitlab.com/gitlab-com/www-gitlab-com/issues/1317
ANYONE - pls feel free to tweak this MR as much as you want. It's a shared test-MR and won't be merged.## NOT TO BE MERGED
This is just a test for https://gitlab.com/gitlab-com/www-gitlab-com/issues/1317
ANYONE - pls feel free to tweak this MR as much as you want. It's a shared test-MR and won't be merged.https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5803Update gitlab_vs_jenkins.yml with information about missing build reports.2017-05-31T04:44:24Zusername-removed-116443Update gitlab_vs_jenkins.yml with information about missing build reports.It would be great if GitLab let you view build reports in the browser, but it currently does not. Until it does, the comparison should reflect the actual situation.
(https://gitlab.com/gitlab-org/gitlab-ce/issues/13227, https://gitlab.c...It would be great if GitLab let you view build reports in the browser, but it currently does not. Until it does, the comparison should reflect the actual situation.
(https://gitlab.com/gitlab-org/gitlab-ce/issues/13227, https://gitlab.com/gitlab-org/gitlab-ce/issues/18664, https://gitlab.com/gitlab-org/gitlab-ce/issues/17081, https://gitlab.com/gitlab-org/gitlab-ce/issues/10982, https://gitlab.com/gitlab-org/gitlab-ce/issues/23618, etc)https://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5844WIP- Sales Qualified Process2017-05-01T13:05:56ZFrancis AquinoWIP- Sales Qualified ProcessWIP, updating the Sales Qualification Process.WIP, updating the Sales Qualification Process.Francis AquinoFrancis Aquinohttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5876Improve `bin/pick-random-team-members`2017-08-10T14:26:28ZToon ClaesImprove `bin/pick-random-team-members`Added some options to `bin/pick-random-team-members`.
New docstring:
```
Pick some random team members!
Usage:
bin/pick-random-team-members <n> [--reports-to=<reports-to>]... [--role=<role>]...
[--project=...Added some options to `bin/pick-random-team-members`.
New docstring:
```
Pick some random team members!
Usage:
bin/pick-random-team-members <n> [--reports-to=<reports-to>]... [--role=<role>]...
[--project=<project>]... [--assignment=<assignment>]...
bin/pick-random-team-members -h | --help
Options:
-h --help Show this message.
--reports-to=<reports-to> Pick team members who report to the given team members.
--role=<role> Pick team members with the given role (case-insensitive partial match).
--project=<project> Pick team members responsible for the given project.
--assignment=<assignment> Pick team members with the given assignment for project.
```
cc @smcgivernToon ClaesToon Claeshttps://staging.gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/5887Added vagrant and EE license instructions2017-05-09T05:56:35ZAdam MulvanyAdded vagrant and EE license instructionsAdded automated Vagrant install, removed references to Digital Ocean, added instructions for getting a GitLab-EE shared license.Added automated Vagrant install, removed references to Digital Ocean, added instructions for getting a GitLab-EE shared license.Lee MatosLee Matos