🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The installation documentation of AdoptOpenJDK that can be found at https://adoptopenjdk.net/installation.html
must be migrated to Temurin and stored as Asciidoc documentation in this repository.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

Adoptium and all it repos belong to the Eclipse Foundation since Adoptium is a top level project at Eclipse. To contribute to an Eclipse project the Eclipse Contributor Agreement must be (digitally) signed. To do so an account at Eclipse is needed. The ECA is checked at GitHub in each pull request. Eclipse provides some general information regarding GIT and ECA but it would make sense to have a newcomer friendly documentation that is made directly for GitHub and pull requests.
Additional Information can be found here and here.
The goal of this issue is to provide a tutorial / step by step guide for newcomers as an adoc in this repo.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The documentation regarding the BumbleBench benchmark can be found at https://github.com/adoptium/bumblebench/wiki/BumbleBench-and-HumbleBench The documentation must be migrated and stored as Asciidoc documentation in this repository.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

We want to have a CONTRIBUTING.md file in the repo. A good example of such file can be found here. The must must contain the section regarding the "Eclipse Contributor Agreement".

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

Currently we have 3 different logos: Adoptium, Temurin & AQAvit. The design agency provided a small styleguide. The style guide should be migrated to AsciiDoc.
A styleguide of the Eclipse logo can be found here. That is a good reference about text and infos that should be part of a styleguide.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The infrastructure documentation of Adoptium that can be found at https://github.com/adoptium/infrastructure/blob/master/FAQ.md
It must be migrated to Temurin and stored as Asciidoc documentation in this repository.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The information that can be found at https://adoptium.net/support.html must be converted to asciidoc and stored as a document in this repository.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

It is really helpful to have a set of icons that can be used in documentation. AsciiDoc provides support for icons and this doc already uses some of them. We want to use vector based icons and not image / pixel based icons in our documentations. Therefore the support for font based icons in AsciiDoc sounds like a good idea. This is based on Font Awesome. We should provide a short documentation regarding the usage of such icons in the documentation. Next to this an information of the supported Font Awesome version would be good.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

We want to have information about the "code of conduct" directly in the repo. This is done by providing a CODE_OF_CONDUCTION.md file. Since this is a project under the umbrella of the Eclipse Foundation we can easily link to the "code of conduct" of the foundation as it is done here: https://github.com/adoptium/api.adoptium.net/blob/main/CODE_OF_CONDUCTION.md

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

We need a documentation and "getting started" guide regarding our ZenHub board for newcomers.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The PR #13 introduced custom style classes for the documentation. To support such classes a new css file needs to be added. Asciidoc provides different ways how such CSS file can be loaded. Some documentation can be found here:

https://docs.asciidoctor.org/asciidoc/latest/text/custom-inline-styles/
https://docs.asciidoctor.org/asciidoctor/latest/html-backend/default-stylesheet/#customize-extend
https://docs.asciidoctor.org/asciidoctor/latest/html-backend/custom-stylesheet/

Currently the new style sheet is defined directly on the asciidoc files and internally does an css import to include the original asciidoc stylesheet. We need to check if this is the best way to do it or if we better add such informational parameters to the asciidoctor command (see build.sh file).

As a result this issue should provide a short overview of the different possibilities and their benefits. Based on a simple discussion in this issue a PullRequest with the best possibility should be provided.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

In this Issue the prior work of PR #13 and issue #16 should be combined.

Description of the issue

In PR #13 @hendrikebbers provides a basic styling for the Adoptium documentation.
These classes have to be applied to all adoc files in the repository.

In issue #16 @hendrikebbers and @MBoegers aggreed on:

• linking the CSS files at build/render-time
• stick with Ascidoctors default behavior
  For an example, see section specify the custom stylesheet.

Acceptance

• configure build.sh to use the stylesheets
• configure GitHub Action build to use the stylesheets

Questions

If you have any questions, just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open-source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

In the migration documentation (https://github.com/AdoptOpenJDK/website-adoptium-documentation/blob/main/migration/index.adoc) several links direct to the migration page of AdoptOpenJDK. Instead of doing so such links should be defined as internal cross references in Asciidoc since all this paragraphs are part of the same documentation file.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

Since some people are interested in working on the Adoptium documentation I plan to create a bi-weekly community meeting to sync between all the awesome volunteers 🚀

I created a Doodle to find a good day & time. This is not to define a specific date within the next week but to find a general slot that will work for most people. If we can not find a good slot I will add more options to the doodle.

The meetings will be open for all and should be used to present results, sync work and help other volunteers to get into the project. I will create an issue for each meeting that can be used to simple add topics to the agenda and store the minutes of the meeting.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The content of the Adoptium 'Supported Platforms' page should be migrated to AsciiDoc.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

In the last meeting (#29) @Plexar mentioned that he had some problems setting up the system. I Copied the comment from the meeting minutes:

There are some pitfalls for new developers in this project:

• when you claimed an issue by commenting, you should start work on the issue after you have been assigned to be properly mentionned as contributor
• your Eclipse Adoptium email address, your Github email address AND the email address doing a commit with should be equal

This is the agenda and documentation of a community meeting for the Adoptium homepage and documentation. If you plan to attend please leave a comment in this issue :)

📌 Date
We will meet on Monday, 25 Oct. 2021 at 16:30 GMT+2 (Germany/Berlin).
For the first meeting I plan to use Google Meet: Link to the meeting

📄 Agenda

• Introduce Adoptium Slack
• Check if everybody can create PR for Eclipse projects
• We need to check if our PRs are already counted for Hacktoberfest
• Update of the Mockups for the integrated documentation in the new adoptium.net layout & design (see attached images) + HTML mockups: https://github.com/HanSolo/Marketplace and https://deploy-preview-217--eclipsefdn-adoptium.netlify.app
• Discussion regarding the Java service for rendering then pages (frameworks & architecture)
• https://github.com/Plexar not mentioned as assignee in the repo
• GitHub Action for https://github.com/adoptium/documentation-services not triggered for pull requests

👥 How to attend?
The meeting is open for everyone :) If you want to contribute to the Adoptium documentation or just want to know what we are doing just join the meeting. If possible please add a short comment to this issue that you plan to attend the meeting. This meeting is managed in the Adoptium Community calendar. An ICAL link to integrate the calendar in other tools can be found here. If you plan to attend please leave a comment in this issue :)

🎉 Achievements since last meeting

• PR #22 merged
• PR #23 merged
• PR #24 merged
• PR adoptium/documentation-services#6 merged
• PR adoptium/documentation-services#21 merged
• PR adoptium/documentation-services#20 merged
• PR adoptium/documentation-services#18 merged
• Repository for Java service has been created: https://github.com/adoptium/documentation-services
• Issues regarding the Java service have been created: https://github.com/adoptium/documentation-services/issues
• Documentation Repo migrated to https://github.com/adoptium/documentation
• Issue #16 solved
• Wiki page with general information about our bi-weekly meetings.
• Info about ECA added to "good first issue" template. See adoptium/documentation-services#10 as example.
• Community Activity at JavaLand: https://github.com/ijug-ev/JavaLand/tree/main/Community-Aktivitäten#ijug-open-source-stipendium-jug-goldstadt-markus-karg

✏️ Minutes

• https://github.com/Plexar will take care of GitHub Action for repo
• https://github.com/Plexar contribution is now mentioned
• "Good First Issue" template -> Some changes are needed. https://github.com/Plexar had some problems to start.
• "Good First Issue" template should be added to documentation
• Results like #16 should be created as adoc files in our documentation
• We will shift the bi-weekly one week. Next meeting will be in 3 weeks.

We should move the repository to https://github.com/adoptium and create a second one for the java based services to render the HTML output of the documentation.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The PR #13 introduced custom style classes for the documentation. We need to provide a documentation of such classes (and some common asciidoc basic classes) that can be used in the documentation.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

The content of the FAQ page should be migrated to the AsciiDoc based documentation.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.

First meeting of the community 🎉

📌 Date
We will meet on Monday, 11 Oct. 2021 at 16:30 GMT+2 (Germany/Berlin).
For the first meeting I plan to use Google Meet: Link to the meeting

📌 Agenda

• Meet and great of all members can that join the meeting
• Short presentation of the vision regarding the project (@hendrikebbers )
• Update on the current state (@hendrikebbers )
• Info about Hacktoberfest

📌 How to attend?
The meeting is open for everyone :) If you want to contribute to the Adoptium documentation or just want to know what we are doing just join the meeting. If possible please add a short comment to this issue that you plan to attend the meeting.

📌 Minutes

• Introduction of team members
• Vision: https://docs.google.com/document/d/1AHxz5hSr4MJApAuPOYzjY7CLRTOHJgh7gxgGFUV2WAk/edit
• Action Item: Creation of repository for micro-service
• Action Item: Issues for micro-service repo
• @MBoegers mentioned that it might be a good solution to render HTML output directly in the doc repo by using github actions instead of doing this in the micro-service. We need to check the different options.
• Q&A regarding next weeks

This is the agenda and documentation of a community meeting for the Adoptium homepage and documentation. If you plan to attend please leave a comment in this issue :)

📌 Date

We will meet on Monday, 13 Dec. 2021 at 16:30 GMT+2 (Germany/Berlin).
For the meeting use Google Meet: Link to the meeting

📄 Agenda

TODO

👥 How to attend?

The meeting is open for everyone :) If you want to contribute to the Adoptium documentation or just want to know what we are doing just join the meeting. If possible please add a short comment to this issue that you plan to attend the meeting. This meeting is managed in the Adoptium Community calendar. An ICAL link to integrate the calendar in other tools can be found here. If you plan to attend please leave a comment in this issue :)

🆕🐥 Newcomer support

We assume that this project is a very good opportunity to start with open source contributions. Therefore we always provide several "good first" issues. More information can be found here.

🎉 Achievements since last meeting

TODO

✏️ Minutes

TODO

This is the agenda and documentation of a community meeting for the Adoptium homepage and documentation. If you plan to attend please leave a comment in this issue :)

📌 Date

We will meet on Monday, 29 Nov. 2021 at 16:30 GMT+2 (Germany/Berlin).
For the meeting use Google Meet: Link to the meeting

📄 Agenda

• Discuss coding rules (examples: https://github.com/rico-projects/rico/blob/master/JAVA_STYLE_GUIDE.md, https://google.github.io/styleguide/javaguide.html)
• Discuss formatting rules / should we provide https://editorconfig.org support?
• Discuss test workflow rules (given-when-then)
• Milestone 1 of documentation service (adoptium/documentation-services#42)
• Review of the service architecture (https://github.com/adoptium/documentation-services)
• Discuss Microprofile usage ([at]Singleton, https://github.com/mirkosertic/cdicron)
• Open topics: Codacy, new issues, pair programming sessions?

👥 How to attend?

The meeting is open for everyone :) If you want to contribute to the Adoptium documentation or just want to know what we are doing just join the meeting. If possible please add a short comment to this issue that you plan to attend the meeting. This meeting is managed in the Adoptium Community calendar. An ICAL link to integrate the calendar in other tools can be found here. If you plan to attend please leave a comment in this issue :)

🆕🐥 Newcomer support

We assume that this project is a very good opportunity to start with open source contributions. Therefore we always provide several "good first" issues. More information can be found here.

🎉 Achievements since last meeting

• PR #18 merged
• PR adoptium/documentation-services#23 merged
• PR adoptium/documentation-services#24 merged
• PR adoptium/documentation-services#25 merged
• PR adoptium/documentation-services#26 merged
• Projects setup in Codacy: https://app.codacy.com/gh/adoptium/documentation-services/
• PR adoptium/documentation-services#33 merged
• PR adoptium/documentation-services#31 merged
• PR adoptium/documentation-services#29 merged
• PR #38 merged

✏️ Minutes

• We will plan bi-weekly pair programming sessions
• Milestone 1 will be reached with the merge of adoptium/documentation-services#42
• Milestone 2 will be a hosted service that is ready for integration in adoptium.net
• Code formating, Coding rules & test workflows: We will add some definitions to contibutions.md (links), we like hoe we currently work and will continue

🆕🐥 First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

👾 Description of the issue

Asciidoc supports attributes in documents. A document can contain predefined attributes or custom attributes.

We should define a list of attributes that should be specified in the document headers. A good starting point is the document metadata like the description that is be used to automatically generate HTML metadata. Next to the header attributes there will be some attributes that are the same for all documents (like copyright or orgname). Such attributes must be defined too since they will be set when rendering the documents.

📋 Step by Step

To solve this issue and contribute a fix you should check the following step-by-step list. A more detailed documentation of the workflow can be found here.

• Claim this issue: Comment below.
• Fork the repository in github by simply clicking the 'fork' button.
• Check out the forked repository
• Create a feature branch for the issue. We do not have any naming definition for branches.
• Commit your changes.
• Start a Pull Request.
• Done 👍 Ask in comments for a review :)
• If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
• You did it 🎉 We will merge the fix in the master branch.
• Thanks, thanks, thanks for being part of this project as an open source contributor ❤️

🎉 Contribute to Hacktoberfest

Solve this issue as part of the Hacktoberfest event and get a change to receive cool goodies like a T-Shirt. 🎽

🤔❓ Questions

If you have any questions just ask us directly in this issue by adding a comment. You can join our community chat at Slack. Next to this you can find a general manual about open source contributions here.