This repository was archived by the owner on Jan 28, 2025. It is now read-only.
add faq #2
Open
add faq #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@a-m-zill You are the deploy-master, could you check and publish this? |
|
@javahippie and @Kungi can you both give me a thumb up if the FAQs from the content are Ok for you. |
Kungi
reviewed
Dec 5, 2024
| <h2>Frequently Asked Questions</h2> | ||
| <p> | ||
| <strong>Q: What is the correct capitalization for the project name: "Operaton" or "OPERATON"?</strong><br/> | ||
| A: The correct capitalization is "Operaton." While some early communications used the all-uppercase "OPERATON," this led to inconsistencies. The trademark is registered as "Operaton," and the community has agreed to use this capitalization consistently to avoid confusion. |
There was a problem hiding this comment.
The trademark is currently "being" registered. The registration process is not finished yet.
Kungi
reviewed
Dec 5, 2024
| </p> | ||
| <p> | ||
| <strong>Q: Why doesn't Operaton simply clone existing repositories instead of changing the namespace, and what challenges are associated with this approach?</strong><br/> | ||
| A: While cloning existing repositories might seem straightforward, Operaton faces both legal and technical challenges with this method. Legally, certain constraints necessitate changes beyond mere cloning. Technically, platforms like Maven Central prohibit publishing packages outside one's designated namespace. To address these issues and facilitate a smooth transition, Operaton is developing OpenRewrite scripts to assist users in migrating to the new namespace. |
There was a problem hiding this comment.
Can we link the open rewrite scripts here?
Kungi
reviewed
Dec 5, 2024
| </p> | ||
| <p> | ||
| <strong>Q: What is the planned scope for Operaton version 1.0.0, and how is the development team approaching its release?</strong><br/> | ||
| A: We are committed to ensuring that version 1.0.0 is robust and fully featured. To achieve this, we are focusing on comprehensive documentation and thorough testing. The team is open to releasing multiple beta versions to address any issues and incorporate feedback. Contributors are encouraged to assist, particularly with build-related issues. |
There was a problem hiding this comment.
Can we link to the roadmap here?
Kungi
reviewed
Dec 5, 2024
| <h2>Häufig gestellte Fragen</h2> | ||
| <p> | ||
| <strong>F: Wie lautet die korrekte Schreibweise des Projektnamens: "Operaton" oder "OPERATON"?</strong><br/> | ||
| A: Die korrekte Schreibweise ist "Operaton". Während in frühen Kommunikationsphasen die Großschreibung "OPERATON" verwendet wurde, führte dies zu Inkonsistenzen. Die Marke ist als "Operaton" registriert, und die Community hat sich darauf geeinigt, diese Schreibweise konsequent zu verwenden, um Verwirrung zu vermeiden. |
There was a problem hiding this comment.
"Kommunikationsphasen" finde ich ein seltsames Wort. Wollen wir vielleicht schreiben:
Während früher auch die Großschreibung "OPERATON" verwendet wurde, ...
There was a problem hiding this comment.
Die Marke ist aktuell noch nicht registriert sondern nur "angemeldet".
Kungi
reviewed
Dec 5, 2024
| </p> | ||
| <p> | ||
| <strong>F: Warum klont Operaton nicht einfach bestehende Repositories, anstatt den Namespace zu ändern, und welche Herausforderungen sind damit verbunden?</strong><br/> | ||
| A: Obwohl das Klonen bestehender Repositories einfach erscheinen mag, stehen Operaton rechtliche und technische Herausforderungen im Weg. Rechtlich erfordern bestimmte Einschränkungen Änderungen über das bloße Klonen hinaus. Technisch verbieten Plattformen wie Maven Central die Veröffentlichung von Paketen außerhalb des eigenen Namespaces. Um diese Probleme zu lösen und einen reibungslosen Übergang zu ermöglichen, entwickelt Operaton OpenRewrite-Skripte, die Benutzer bei der Migration in den neuen Namespace unterstützen. |
There was a problem hiding this comment.
Siehe meine Anmerkungen im Englischen Teil zur Verlinkung der OpenRewrite Skripte.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.