Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove some Lightbend references #471

Merged
merged 5 commits into from
Jan 20, 2022

Conversation

mkurz
Copy link
Member

@mkurz mkurz commented Jan 20, 2022

It's time.
The reason why I would like to remove most references to Lightbend is to make clear to potential sponsors the project is now community maintained.

There are other things to update (just grep for Lightbend in the repo), however lets do that step-by-step.

def support = Action { implicit request =>
Ok(html.support())
}

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I completely removed the support page because it just promotes Lightbend's commercial offering regarding Play (which does not exist anymore). The other links to Discuss, Discord and Stack Overflow are just duplicated with the "Get Involved" page.

@@ -14,7 +14,6 @@
<li><a href="https://discuss.playframework.com">Discuss Play Forum</a></li>
<li><a href="//discord.gg/g5s2vtZ4Fa">Discord Server</a></li>
<li><a href="https://stackoverflow.com/questions/tagged/playframework">Stack Overflow</a></li>
<li><a href="https://www.lightbend.com/lightbend-platform-subscription">Lightbend Platform Subscription</a></li>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bye bye last point:

@@ -53,7 +53,7 @@ <h3 class="bugs">Report bugs</h3>
</p>

<h3 class="patch">Patch the core</h3>
<a href="//github.com/playframework/playframework/graphs/contributors">600+ committers</a>
<a href="//github.com/playframework/playframework/graphs/contributors">900+ committers</a>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

git shortlog -sn | wc -l

@@ -144,7 +144,7 @@ <h2>Proven in production.</h2>
From startups to enterprises, Play powers some of the most innovative web sites. Play is proven, reliable and scalable.
</p>
<ul>
<li>Production support by Lightbend</li>
<li>Easy to deploy and scale</li>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you have a better idea, let me know.

@@ -48,19 +48,12 @@

</head>
<body class="@scope">
<!--[if lt IE 7]>
<p class="outdated">You are using an outdated browser. <a href="http://browsehappy.com/">Upgrade your browser today</a> or <a href="//www.google.com/chrome/browser/">install Google Chrome Frame</a> to better experience this site.</p>
<![endif]-->
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh crap, I have to upgrade to IE 7 now.

<header id="navigation">
<div class="wrapper">
<a href="/" id="logo">Lightbend</a>
<a href="/" id="logo">Play Framework</a>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is invisible anyway, seems like SEO.

<![endif]-->

@lightbendBanner()

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing the "Akka Serverless" banner.

<a href="https://www.lightbend.com/legal/licenses" target="_blank">Licenses</a> |
<a href="https://www.lightbend.com/legal/terms" target="_blank">Terms</a> |
<a href="https://www.lightbend.com/legal/privacy" target="_blank">Privacy Policy</a> |
<a href="@routes.Application.cookie">Cookie Listing</a> |
<a class="optanon-toggle-display">Cookie Settings</a>
</p>
<p>
&copy; 2011-2021 Lightbend Inc., since 2022 the original author or authors from the Play Framework project
</p>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's the copyright we came up with in the slack channel a couple of weeks ago.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I use 2011 instead of 2009, because that's when Typesafe came in. Also the first commit to Play 2 was in Sept. 2011

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -19,8 +19,7 @@ Before making a contribution, it is important to make sure that the change you w

### Procedure

1. Make sure you have signed the [Lightbend CLA](http://www.lightbend.com/contribute/cla); if not, sign it online.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@octonato octonato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, except for the copyright header. I don't know what needs to be done.

@@ -41,10 +40,10 @@ Before making a contribution, it is important to make sure that the change you w
* Features are forever, always think about whether a new feature really belongs to the core framework or if it should be implemented as a module
* Code must conform to standard style guidelines and pass all tests (see [Run tests](documentation/latest/BuildingFromSource#run-tests))
6. New files must:
* Have a Lightbend copyright header in the style of ``Copyright (C) 2009-2019 Lightbend Inc. <https://www.lightbend.com>``.
* Have a copyright header in the style of ``2011-2021 Lightbend Inc., since 2022 the original author or authors from the Play Framework project``.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get that this sentence means.

I also don't know what we should do with the copyright header. I guess all existing files should keep the Lightbend copyright. After they are edited, they should include Lightbend and something else, eg: Play Framework Organisation.

New files can have Play Framework Organisation only.

We need to learn more about it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentence is similar to what JHipster uses, please see our conversation on slack we had 2 month ago: https://typesafe.slack.com/archives/CFPVDLR41/p1637077983073200

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about changing the copyright of all files on the play master branch to this wording (or similiar). So the 2.8.x branch still is "under control" by Lightbend, however upcoming 2.9 is community. Also the sentences says "unitl 2021 this is Lightbend stuff, after that community"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyway, I will revert this sentence for now but deploy the rest already.

Copy link
Member Author

@mkurz mkurz Jan 20, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renato look here:
https://github.com/jhipster/generator-jhipster/blob/9f8da38a6251416c9b700f35b9533b157d537b4d/cli/commands.js#L2-L5

 * Copyright 2013-2022 the original author or authors from the JHipster project.
 *
 * This file is part of the JHipster project, see https://www.jhipster.tech/
 * for more information.
 *

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets track that here: playframework/play-meta#211

@mkurz mkurz force-pushed the remove_some_lb_references branch from 08a7f82 to 247b0b0 Compare January 20, 2022 22:27
@mkurz
Copy link
Member Author

mkurz commented Jan 20, 2022

Alright, the copyright isn't touched anymore, we can change it later.

@mkurz mkurz merged commit feab0d8 into playframework:master Jan 20, 2022
@mkurz mkurz deleted the remove_some_lb_references branch January 20, 2022 22:32
@mkurz
Copy link
Member Author

mkurz commented Jan 20, 2022

Almost forgot: deployed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants