fix: rename kraken to webf

Author: andycall

GOVERNANCE.md

@@ -1,4 +1,4 @@
-# OpenKraken Project Governance
+# OpenWebF Project Governance
 
 <!-- TOC -->
 
@@ -15,14 +15,14 @@
 
 ## Collaborators
 
-OpenKraken Core Collaborators maintain the [openkraken/kraken][] GitHub repository.
-The GitHub team for OpenKraken Core Collaborators is @openkraken/collaborators.
+OpenWebF Core Collaborators maintain the [openwebf/webf][] GitHub repository.
+The GitHub team for OpenWebF Core Collaborators is @openwebf/collaborators.
 Collaborators have:
 
-* Commit access to the [openkraken/kraken][] repository
-* Access to the OpenKraken continuous integration (CI) jobs
+* Commit access to the [openwebf/webf][] repository
+* Access to the OpenWebF continuous integration (CI) jobs
 
-Both Collaborators and non-Collaborators may propose changes to the OpenKraken
+Both Collaborators and non-Collaborators may propose changes to the OpenWebF
 source code. The mechanism to propose such a change is a GitHub pull request.
 Collaborators review and merge (_land_) pull requests.
 
@@ -50,31 +50,31 @@ status. Emeriti may request that the TSC restore them to active status.
 
 ### Collaborator nominations
 
-Existing Collaborators can nominate someone to become a Collaborator. Nominees should have significant and valuable contributions across the OpenKraken organization.
-
-To nominate a new Collaborator, open an issue in the [openkraken/kraken][] repository. Provide a summary of the nominee's contributions. For example:
-
-* Commits in the [openkraken/kraken][] repository
-  * Use the link `https://github.com/openkraken/kraken/commits?author=GITHUB_ID`
-* Pull requests and issues opened in the [openkraken/kraken][] repository
-  * Use the link `https://github.com/openkraken/kraken/issues?q=author:GITHUB_ID`
-* Comments on pull requests and issues in the [openkraken/kraken][] repository
-  * Use the link `https://github.com/openkraken/kraken/issues?q=commenter:GITHUB_ID`
-* Reviews on pull requests in the [openkraken/kraken][] repository
-  * Use the link `https://github.com/openkraken/kraken/pulls?q=reviewed-by:GITHUB_ID`
-* Pull requests and issues opened throughout the OpenKraken organization
-  * Use the link  `https://github.com/search?q=author:GITHUB_ID+org:openkraken`
-* Comments on pull requests and issues throughout the OpenKraken organization
-  * Use the link `https://github.com/search?q=commenter:GITHUB_ID+org:openkraken`
+Existing Collaborators can nominate someone to become a Collaborator. Nominees should have significant and valuable contributions across the OpenWebF organization.
+
+To nominate a new Collaborator, open an issue in the [openwebf/webf][] repository. Provide a summary of the nominee's contributions. For example:
+
+* Commits in the [openwebf/webf][] repository
+  * Use the link `https://github.com/openwebf/webf/commits?author=GITHUB_ID`
+* Pull requests and issues opened in the [openwebf/webf][] repository
+  * Use the link `https://github.com/openwebf/webf/issues?q=author:GITHUB_ID`
+* Comments on pull requests and issues in the [openwebf/webf][] repository
+  * Use the link `https://github.com/openwebf/webf/issues?q=commenter:GITHUB_ID`
+* Reviews on pull requests in the [openwebf/webf][] repository
+  * Use the link `https://github.com/openwebf/webf/pulls?q=reviewed-by:GITHUB_ID`
+* Pull requests and issues opened throughout the OpenWebF organization
+  * Use the link  `https://github.com/search?q=author:GITHUB_ID+org:openwebf`
+* Comments on pull requests and issues throughout the OpenWebF organization
+  * Use the link `https://github.com/search?q=commenter:GITHUB_ID+org:openwebf`
 * Help provided to end-users and novice contributors
-* Participation in other projects, teams, and working groups of the OpenKraken organization
+* Participation in other projects, teams, and working groups of the OpenWebF organization
 
-Mention @openkraken/collaborators in the issue to notify other Collaborators about the nomination.
+Mention @openwebf/collaborators in the issue to notify other Collaborators about the nomination.
 The nomination passes if no Collaborators oppose it after one week. Otherwise, the nomination fails.
 
 ## Technical Steering Committee
 
-A subset of the Collaborators forms the Technical Steering Committee (TSC). The TSC is responsible for all technical development within the OpenKraken project, including:
+A subset of the Collaborators forms the Technical Steering Committee (TSC). The TSC is responsible for all technical development within the OpenWebF project, including:
 
 * Setting release dates.
 * Release quality standards.
@@ -85,7 +85,7 @@ A subset of the Collaborators forms the Technical Steering Committee (TSC). The
 * Maintaining the list of additional Collaborators.
 * Development process and any coding standards.
 * Mediating technical conflicts between Collaborators projects.
-* The TSC will define OpenKraken project’s release vehicles.
+* The TSC will define OpenWebF project’s release vehicles.
 
 ### Establishment TSC
 
@@ -99,7 +99,7 @@ TSC members are expected to regularly participate in TSC activities. If a TSC me
 
 ### TSC elections
 
-Leadership roles in the OpenKraken project will be peer elected representatives of the community.
+Leadership roles in the OpenWebF project will be peer elected representatives of the community.
 
 The TSC will elect from amongst voting TSC members a TSC Chairperson to work on building an agenda for TSC meetings.
 The TSC shall hold annual elections to select a TSC Chairperson and
@@ -146,11 +146,11 @@ meeting, the TSC chair ensures that someone opens a pull request with the
 minutes.
 
 The TSC seeks to resolve as many issues as possible outside meetings using
-[the TSC issue tracker](https://github.com/openkraken/TSC/issues). The process in
+[the TSC issue tracker](https://github.com/openwebf/TSC/issues). The process in
 the issue tracker is:
 
 * A TSC member opens an issue explaining the proposal/issue and @-mentions
-  @openkraken/tsc.
+  @openwebf/tsc.
 * The proposal passes if, after 72 hours, there are two or more TSC approvals
   and no TSC opposition.
 * If there is an extended impasse, a TSC member may make a motion for a vote.
@@ -161,7 +161,7 @@ For internal project decisions, Collaborators shall operate under [Lazy Consensu
 The TSC shall establish appropriate guidelines for implementing Lazy Consensus
 (e.g. expected notification and review time periods) within the development process.
 
-The TSC follows a [Consensus Seeking][] decision making model. When an agenda 
+The TSC follows a [Consensus Seeking][] decision making model. When an agenda
 item has appeared to reach a consensus the moderator will ask "Does anyone object?"
 as a final call for dissent from the consensus.
 
@@ -173,7 +173,7 @@ For all votes, a simple majority of all TSC members for, or against, the issue w
 A TSC member may choose to participate in any vote through abstention.
 
 
-[openkraken/kraken]: https://github.com/openkraken/kraken
+[openwebf/webf]: https://github.com/openwebf/webf
 [Lazy Consensus]: https://community.apache.org/committers/lazyConsensus.html
 [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making
 [Condorcet]: https://en.wikipedia.org/wiki/Condorcet_method

GOVERNANCE.zh-CN.md

@@ -1,4 +1,4 @@
-# OpenKraken 项目协同
+# OpenWebF 项目协同
 
 <!-- 目录 -->
 
@@ -15,14 +15,14 @@
 
 ## 协作者
 
-OpenKraken 的协作者将共同维护 [openkraken/kraken] 仓库，协作者在 GitHub 上的小组名称为 @openkraken/collaborators。
+OpenWebF 的协作者将共同维护 [openwebf/webf] 仓库，协作者在 GitHub 上的小组名称为 @openwebf/collaborators。
 
 协作者拥有以下权限：
 
-* [openkraken/kraken] 仓库的 Commit 权限
-* OpenKraken 持续集成（CI）任务的权限
+* [openwebf/webf] 仓库的 Commit 权限
+* OpenWebF 持续集成（CI）任务的权限
 
-无论协作者还是非协作者都可以提交 OpenKraken 的更改，提交更改的机制是通过 Pull Request (PR)。
+无论协作者还是非协作者都可以提交 OpenWebF 的更改，提交更改的机制是通过 Pull Request (PR)。
 
 PR 至少两个协作者 Review 通过后才能 Merge，但如果 PR 已经打开超过 7 天，则获得一个协作者的 Review 通过就可以 Merge。
 
@@ -34,38 +34,38 @@ PR 至少两个协作者 Review 通过后才能 Merge，但如果 PR 已经打
 
 * 帮助新手贡献者
 * 贡献代码和更新文档
-* 审查和评论 Issue 并提交 Pull Request 
+* 审查和评论 Issue 并提交 Pull Request
 * 参加工作组
 * 合并 Pull Request
 
 技术委员会可以移除不活跃的协作者或将他们转移到**荣誉组**，荣誉组成员可以让技术委员会将他们恢复为协作者。
 
 ### 协作者提名
 
-现有的协作者可以提名某人成为协作者，被提名人应当是在整个 OpenKraken 生态上做出贡献的组织或个人。
+现有的协作者可以提名某人成为协作者，被提名人应当是在整个 OpenWebF 生态上做出贡献的组织或个人。
 
-要提名新的协作者，需要到 [openkraken/kraken][] 仓库中提出一个 Issue，并提供被提名人相关贡献的概述。例如：
+要提名新的协作者，需要到 [openwebf/webf][] 仓库中提出一个 Issue，并提供被提名人相关贡献的概述。例如：
 
-* 在 [openkraken/kraken][] 仓库中的 Commits
-  * 链接格式 `https://github.com/openkraken/kraken/commits?author=GITHUB_ID`
-* 在 [openkraken/kraken][] 仓库中提交的 Pull requests 和 Issues
-  * 链接格式 `https://github.com/openkraken/kraken/issues?q=author:GITHUB_ID`
-* 在 [openkraken/kraken][] 仓库中对 Pull requests 和 Issues 的评论
-  * 链接格式 `https://github.com/openkraken/kraken/issues?q=commenter:GITHUB_ID`
-* 在 [openkraken/kraken][] 仓库中的 Reviews
-  * 链接格式 `https://github.com/openkraken/kraken/pulls?q=reviewed-by:GITHUB_ID`
-* 在整个 OpenKraken 组织下提交的 Pull requests 和 Issues
-  * 链接格式 `https://github.com/search?q=author:GITHUB_ID + org:openkraken`
-* 在整个 OpenKraken 组织下对 Pull requests 和 Issues 的评论
-  * 链接格式 `https:////github.com/search?q=commenter:GITHUB_ID + org:openkraken`
-* 向 OpenKraken 用户和新手贡献者提供的帮助
-* 参加 OpenKraken 的其他项目，团队、工作组或组织
+* 在 [openwebf/webf][] 仓库中的 Commits
+  * 链接格式 `https://github.com/openwebf/webf/commits?author=GITHUB_ID`
+* 在 [openwebf/webf][] 仓库中提交的 Pull requests 和 Issues
+  * 链接格式 `https://github.com/openwebf/webf/issues?q=author:GITHUB_ID`
+* 在 [openwebf/webf][] 仓库中对 Pull requests 和 Issues 的评论
+  * 链接格式 `https://github.com/openwebf/webf/issues?q=commenter:GITHUB_ID`
+* 在 [openwebf/webf][] 仓库中的 Reviews
+  * 链接格式 `https://github.com/openwebf/webf/pulls?q=reviewed-by:GITHUB_ID`
+* 在整个 OpenWebF 组织下提交的 Pull requests 和 Issues
+  * 链接格式 `https://github.com/search?q=author:GITHUB_ID + org:openwebf`
+* 在整个 OpenWebF 组织下对 Pull requests 和 Issues 的评论
+  * 链接格式 `https:////github.com/search?q=commenter:GITHUB_ID + org:openwebf`
+* 向 OpenWebF 用户和新手贡献者提供的帮助
+* 参加 OpenWebF 的其他项目，团队、工作组或组织
 
-在 Issue 中 `@openkraken/collaborators` 以通知其他协作者。如果一周后没有任何协作者反对，则提名通过，否则提名失败。
+在 Issue 中 `@openwebf/collaborators` 以通知其他协作者。如果一周后没有任何协作者反对，则提名通过，否则提名失败。
 
 ## 技术委员会
 
-一部分协作者组成了技术委员会（TSC），以下简称委员会。委员会为 OpenKraken 项目内的所有技术开发行为负责，其职责包括：
+一部分协作者组成了技术委员会（TSC），以下简称委员会。委员会为 OpenWebF 项目内的所有技术开发行为负责，其职责包括：
 
 * 设置发布日期
 * 发布质量标准
@@ -76,7 +76,7 @@ PR 至少两个协作者 Review 通过后才能 Merge，但如果 PR 已经打
 * 维护协作者列表
 * 维护开发过程和任何编码标准
 * 协调技术冲突
-* 委员会将提供 OpenKraken 项目的发布工具
+* 委员会将提供 OpenWebF 项目的发布工具
 
 ### 组建委员会
 
@@ -110,10 +110,10 @@ PR 至少两个协作者 Review 通过后才能 Merge，但如果 PR 已经打
 
 在会议期间，委员会主席需要确保有人在记录会议纪要。在会议结束后，委员会主席需要保证会议纪要被上传。
 
-委员会可以使用[委员会问题跟踪区](https://github.com/openkraken/TSC/issues) 在会议之外解决尽可能多的问题。 问题跟踪区的运行机制是：
+委员会可以使用[委员会问题跟踪区](https://github.com/openwebf/TSC/issues) 在会议之外解决尽可能多的问题。 问题跟踪区的运行机制是：
 
 * 委员会成员打开一个问题，解释提案/问题和 @提及
-  @openkraken/tsc
+  @openwebf/tsc
 * 如果 72 小时后获得两个或更多委员会成员批准，且没有委员会成员的反对，则提案通过
 * 如果不能够达成共识，委员会成员可以提出发起投票
 
@@ -127,6 +127,6 @@ PR 至少两个协作者 Review 通过后才能 Merge，但如果 PR 已经打
 
 对于所有投票，绝大多数委员会成员同意则该提议通过，委员会成员也可以选择放弃投票。
 
-[openkraken/kraken]: https://github.com/openkraken/kraken
+[openwebf/webf]: https://github.com/openwebf/webf
 [Lazy Consensus]: https://community.apache.org/committers/lazyConsensus.html
 [Consensus Seeking]: https://en.wikipedia.org/wiki/Consensus-seeking_decision-making

bridge/CMakeLists.txt

@@ -1,6 +1,6 @@
 cmake_minimum_required(VERSION 3.10.0)
 set(CMAKE_OSX_DEPLOYMENT_TARGET 10.11)
-project(KrakenBridge)
+project(WebF)
 
 set(CMAKE_CXX_STANDARD 17)
 set(CMAKE_CXX_STANDARD_REQUIRED ON)
@@ -151,7 +151,7 @@ list(APPEND BRIDGE_INCLUDE
 
 set(BINDING_DIR ${CMAKE_CURRENT_LIST_DIR}/bindings)
 
-if ($ENV{KRAKEN_JS_ENGINE} MATCHES "quickjs")
+if ($ENV{WEBF_JS_ENGINE} MATCHES "quickjs")
   add_compile_options(-DKRAKEN_QUICK_JS_ENGINE=1)
 
   execute_process(
@@ -299,10 +299,10 @@ list(APPEND PUBLIC_HEADER
   include/kraken_bridge.h
   )
 
-add_library(kraken SHARED ${BRIDGE_SOURCE})
-add_library(kraken_static STATIC ${BRIDGE_SOURCE})
+add_library(webf SHARED ${BRIDGE_SOURCE})
+add_library(webf_static STATIC ${BRIDGE_SOURCE})
 
-target_compile_definitions(kraken PUBLIC -DFLUTTER_BACKEND=1)
+target_compile_definitions(webf PUBLIC -DFLUTTER_BACKEND=1)
 
 add_library(gumbo_parse_static STATIC ${GUMBO_PARSER})
 list(APPEND BRIDGE_LINK_LIBS gumbo_parse_static)
@@ -320,30 +320,30 @@ elseif(${IS_IOS})
   add_definitions(-DIS_IOS=1)
 endif()
 
-### Kraken
-target_include_directories(kraken PRIVATE
+### webf
+target_include_directories(webf PRIVATE
   ${BRIDGE_INCLUDE}
   ${CMAKE_CURRENT_SOURCE_DIR} PUBLIC ./include)
-target_link_libraries(kraken PRIVATE ${BRIDGE_LINK_LIBS})
+target_link_libraries(webf PRIVATE ${BRIDGE_LINK_LIBS})
 
-if ($ENV{KRAKEN_JS_ENGINE} MATCHES "quickjs")
+if ($ENV{WEBF_JS_ENGINE} MATCHES "quickjs")
   if (${CMAKE_BUILD_TYPE} STREQUAL "Release" OR ${CMAKE_BUILD_TYPE} STREQUAL "RelWithDebInfo")
-    target_compile_options(kraken PRIVATE -fno-exceptions -fvisibility=hidden -fno-rtti)
+    target_compile_options(webf PRIVATE -fno-exceptions -fvisibility=hidden -fno-rtti)
   else ()
     ### remove dynamic_cast and exceptions
-    target_compile_options(kraken PRIVATE -fno-exceptions -fno-rtti)
+    target_compile_options(webf PRIVATE -fno-exceptions -fno-rtti)
   endif ()
 endif ()
 
 ### KrakenStatic
-target_include_directories(kraken_static PRIVATE
+target_include_directories(webf_static PRIVATE
   ${BRIDGE_INCLUDE}
   ${CMAKE_CURRENT_SOURCE_DIR} PUBLIC ./include)
-target_link_libraries(kraken_static ${BRIDGE_LINK_LIBS})
+target_link_libraries(webf_static ${BRIDGE_LINK_LIBS})
 
 execute_process(
   COMMAND grep version: ./pubspec.yaml
-  WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/../kraken
+  WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}/../webf
   OUTPUT_VARIABLE APP_VER
 )
 string(SUBSTRING ${APP_VER} 9 30 APP_VER)
@@ -365,13 +365,13 @@ if (${ENABLE_TEST})
 endif ()
 
 if (DEFINED ENV{LIBRARY_OUTPUT_DIR})
-  set_target_properties(kraken
+  set_target_properties(webf
     PROPERTIES
     LIBRARY_OUTPUT_DIRECTORY "$ENV{LIBRARY_OUTPUT_DIR}"
     )
-  set_target_properties(kraken_static PROPERTIES ARCHIVE_OUTPUT_DIRECTORY "$ENV{LIBRARY_OUTPUT_DIR}")
+  set_target_properties(webf_static PROPERTIES ARCHIVE_OUTPUT_DIRECTORY "$ENV{LIBRARY_OUTPUT_DIR}")
 
-  if ($ENV{KRAKEN_JS_ENGINE} MATCHES "quickjs")
+  if ($ENV{WEBF_JS_ENGINE} MATCHES "quickjs")
     set_target_properties(quickjs PROPERTIES LIBRARY_OUTPUT_DIRECTORY "$ENV{LIBRARY_OUTPUT_DIR}")
   endif ()
 elseif (IS_ANDROID)
@@ -382,11 +382,11 @@ if (${CMAKE_SYSTEM_NAME} MATCHES "iOS")
   set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGNING_REQUIRED "NO")
   set(CMAKE_XCODE_ATTRIBUTE_CODE_SIGN_IDENTITY "")
 
-  set_target_properties(kraken PROPERTIES
-    OUTPUT_NAME kraken_bridge
+  set_target_properties(webf PROPERTIES
+    OUTPUT_NAME webf_bridge
     FRAMEWORK TRUE
     FRAMEWORK_VERSION C
-    MACOSX_FRAMEWORK_IDENTIFIER com.openkraken.kraken-bridge
+    MACOSX_FRAMEWORK_IDENTIFIER com.openwebf.webf-bridge
     MACOSX_FRAMEWORK_BUNDLE_VERSION 1.0
     MACOSX_FRAMEWORK_SHORT_VERSION_STRING 1.0
     PUBLIC_HEADER ${KRAKEN_PUBLIC_HEADERS}
@@ -398,7 +398,7 @@ if (${CMAKE_SYSTEM_NAME} MATCHES "iOS")
       OUTPUT_NAME quickjs
       FRAMEWORK TRUE
       FRAMEWORK_VERSION C
-      MACOSX_FRAMEWORK_IDENTIFIER com.openkraken.quickjs
+      MACOSX_FRAMEWORK_IDENTIFIER com.openwebf.quickjs
       MACOSX_FRAMEWORK_BUNDLE_VERSION 1.0
       MACOSX_FRAMEWORK_SHORT_VERSION_STRING 1.0
       PUBLIC_HEADER ${QUICKJS_PUBLIC_HEADERS}