You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@buildstream.apache.org by Tristan Van Berkom <tr...@codethink.co.uk> on 2022/01/13 08:45:17 UTC

BuildStream now under the Apache License 2.0 [Was: Migration to Apache next steps: License change]

Hi all,

As a follow up to this thread, which is linked here[0], I'm touching
base to announce that I've finally merged the PR[1] which updates all
repository level documentation required to complete the license change.

From this point forward in the master branch, we can consider the code
to be cleanly licensed under the Apache License 2.0.

Thanks to all of those who have helped with this effort, for signing
your ICLAs and helping us to properly track code ownership in master.
    
Best Regards,
    -Tristan

[0]: https://lists.apache.org/thread/8objz1q1n2h4949xn3l6gmq4tbh5hpzr
[1]: https://github.com/apache/buildstream/pull/1464


On Tue, 2021-03-23 at 13:30 +0900, Tristan Van Berkom wrote:
> Hi all,
> 
>    As it was announced last year[0], BuildStream is moving to the
> Apache Software Foundation and the next step in this long processes is
> to finally update the license notices, effectively licensing the code
> in the master branch under the Apache License 2.0[1].
> 
> Today, before sending this email, I have sent individual direct emails
> to all individual copyright holders requesting these contributors to
> sign a statement explicitly granting approval to distribute their
> contributions under the new license.
> 
> You are a copyright holder and will have been contacted if:
> 
>   * Your contributions were made individually, and not on behalf of
>     your employer (in which case your employer will have already been
>     contacted some time ago).
> 
>   * Your contributions are material changes (i.e. spelling error
>     corrections or documentation formatting fixes will not be counted).
> 
>   * Your contributions exist in the history of the master branch, and
>     your name or email shows up in `git shortlog -s` on the master
>     branch.
> 
>     We are only seeking to relicense code that is pertinent to the
>     eventual release of BuildStream 2, current releases of
>     BuildStream 1 or future tags on the `bst-1` stable branch will
>     remain under LGPL v2.1.
> 
> If you did not receive an email and you believe this to be in error,
> please do not hesitate to reply to contact us (by replying to this
> email or directly contacting me or any of the BuildStream core
> developers).
> 
> 
> Once we have received approvals from the remaining individual copyright
> holders, I will go ahead and merge this pull request[2] which I have
> prepared for the occasion.
> 
> We ask that individual copyright holders please send in your replies
> promptly, hopefully within one month we will have received all of the
> needed replies, and we can go ahead and close this chapter, and turn
> our attention back to nailing down the blockers to BuildStream 2.0.
> 
> Best regards,
>     -Tristan
> 
> [0]: https://mail.gnome.org/archives/buildstream-list/2020-April/msg00010.html
> [1]: http://www.apache.org/licenses/LICENSE-2.0
> [2]: https://github.com/apache/buildstream/pull/1464
> 
> 
>