This is an automated email from the ASF dual-hosted git repository. seanglover pushed a commit to branch seglo/artifact-id-rename2 in repository https://gitbox.apache.org/repos/asf/incubator-pekko-connectors.git
commit 077b31ae57fb974686525ead63d8cf8bca8313c4 Author: Sean Glover <[email protected]> AuthorDate: Tue Dec 27 23:19:02 2022 -0500 cleanup --- CONTRIBUTING.md | 9 ++------- README.md | 2 +- build.sbt | 2 +- 3 files changed, 4 insertions(+), 9 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a89d617a..81e9af54 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -14,9 +14,7 @@ You may also check out these [other resources](https://akka.io/get-involved/). ## General Workflow -This is the process for committing code into master. - -1. Make sure you have signed the Lightbend CLA, if not, [sign it online](http://www.lightbend.com/contribute/cla). +This is the process for committing code into main. 1. To avoid duplicated effort, it might be good to check the [issue tracker](https://github.com/apache/incubator-pekko-connectors/issues) and [existing pull requests](https://github.com/apache/incubator-pekko-connectors/pulls) for existing work. - If there is no ticket yet, feel free to [create one](https://github.com/apache/incubator-pekko-connectors/issues/new) to discuss the problem and the approach you want to take to solve it. @@ -25,15 +23,12 @@ This is the process for committing code into master. 1. When the feature or fix is completed you should open a [Pull Request](https://help.github.com/articles/using-pull-requests) on [GitHub](https://github.com/apache/incubator-pekko-connectors/pulls). Prefix your PR title with a marker to show which module it affects (eg. "JMS", or "AWS S3"). -1. The Pull Request should be reviewed by other maintainers (as many as feasible/practical). Note that the maintainers can consist of outside contributors, both within and outside Lightbend. Outside contributors are encouraged to participate in the review process, it is not a closed process. +1. The Pull Request should be reviewed by other maintainers (as many as feasible/practical). Outside contributors are encouraged to participate in the review process, it is not a closed process. 1. After the review you should fix the issues (review comments, CI failures, compiler warnings) by pushing a new commit for new review, iterating until the reviewers give their thumbs up and CI tests pass. 1. If the branch merge conflicts with its target, rebase your branch onto the target branch. -In case of questions about the contribution process or for discussion of specific issues please visit the [akka/dev gitter chat](https://gitter.im/akka/dev). - - ## Alpakka specific advice We've collected a few notes on how we would like Alpakka modules to be designed based on what has evolved so far. diff --git a/README.md b/README.md index 1842a23a..ed1fa078 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ To keep up with the latest Alpakka releases check out [Pekko connectors releases Community --------- -You can join these forums and chats to discuss and ask Akka and Alpakka related questions: +You can join these forums and chats to discuss and ask Pekko and Pekko connector related questions: - [GitHub discussions](https://github.com/apache/incubator-pekko/discussions): for questions and general discussion. - [Pekko dev mailing list](https://lists.apache.org/[email protected]): for Pekko connectors development discussions. diff --git a/build.sbt b/build.sbt index 4be134d2..a245e243 100644 --- a/build.sbt +++ b/build.sbt @@ -1,4 +1,4 @@ -lazy val pekkoConnectors = project +lazy val `pekko-connectors` = project .in(file(".")) .enablePlugins(ScalaUnidocPlugin) .disablePlugins(MimaPlugin, SitePlugin) --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
