This is an automated email from the ASF dual-hosted git repository.
Bukama pushed a commit to branch master
in repository
https://gitbox.apache.org/repos/asf/maven-doxia-book-maven-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 5eda635 Fix README.md for retired (#17)
5eda635 is described below
commit 5eda635dfbb8832a09e93cb117c98a5fd12569af
Author: Matthias Bünger <[email protected]>
AuthorDate: Mon May 25 18:23:17 2026 +0200
Fix README.md for retired (#17)
---
README.md | 48 ------------------------------------------------
1 file changed, 48 deletions(-)
diff --git a/README.md b/README.md
index df45fea..61c9a0e 100644
--- a/README.md
+++ b/README.md
@@ -14,54 +14,6 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-Contributing to [Apache Maven Doxia Book Maven
Plugin](https://maven.apache.org/doxia/doxia-tools/doxia-book-maven-plugin/)
-======================
-
-[][license]
-[](https://search.maven.org/artifact/org.apache.maven.doxia/doxia-book-maven-plugin)
-[][build]
-[][test-results]
-
-
-You have found a bug, or you have an idea for a cool new feature? Contributing
-code is a great way to give something back to the open source community. Before
-you dig right into the code, there are a few guidelines that we need
-contributors to follow so that we can have a chance of keeping on top of
-things.
-
-Getting Started
----------------
-
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature, it makes sense to discuss
your changes
- on the [dev list][ml-list] first.
- This way you can make sure you're not wasting your time on something that
isn't
- considered to be in Apache Maven's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
- + Clearly describe the issue, including steps to reproduce when it is a bug.
- + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
-
-Making and Submitting Changes
---------------
-
-We accept Pull Requests via GitHub. The [developer mailing list][ml-list] is
the
-main channel of communication for contributors.
-There are some guidelines which will make applying PRs easier for us:
-+ Create a topic branch from where you want to base your work (this is usually
the master branch).
- Push your changes to a topic branch in your fork of the repository.
-+ Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
- patches should only highlight the actual difference, not being disturbed by
any formatting issues:
- + Only use spaces for indentation.
- + Create minimal diffs - disable on save actions like reformat source code
or organize imports.
- If you feel the source code should be reformatted, create a separate PR
for this change.
- + Check for unnecessary whitespace with `git diff --check` before committing.
-+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was
accidentally broken.
-+ Submit a pull request to the repository in the Apache organization.
-
-If you plan to contribute on a regular basis, please consider filing a
[contributor license agreement][cla].
RETIRED - [Apache Maven Doxia Book Maven
Plugin](https://maven.apache.org/doxia/doxia-tools/doxia-book-maven-plugin/)
======================
