| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
LANDAU officially stands for "Linux And Neo-Depositorium Associated
Unity". Update the site title and description in both README.md and
_config.yml to reflect the correct acronym and remove outdated "Kernel"
references.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
For upstream hugo the only possiblity for mermaid rendering is using
external js script.
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
- add opening meta delimeter as required
- s/published/draft/ as `published` is an alias to `publishDate` and
requires correct date and not boolean type
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Convert links to canonical as per vanilla hugo.
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Currently make simple:
- no tags or categories
- disable footer copyright
- just a few section: mainpage, about and subscribe
- landau-hacker theme (embedded)
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Upstream hugo can't work with content separated from templates, config
and other stuff. So move all content files to subdirectory.
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Let's wrap the text up on the 80-char column since it's visually very hard
to track changes in the long lines. 80-char must be enough and has got to
be a de-facto standard in the Linux-related projects.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
First of all the using the slang word "hardware" in Russian is
inappropriate. Secondly the project is dedicated not only for the Russian
hardware but for any specialized device, which support couldn't be sent
upstream for some reason. Finally the project might be useful not only for
the IP-core or electronic device manufacturer, but also for the OS
distribution vendors. Let's add all of that to the LANDAU Linux main page.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
Signed-off-by: Dmitry Rokosov <ddrokosov@salutedevices.com>
|
|
These words are inappropriate in the Russian text and can be easily
converted just "Linux kernel", "Linux kernel repo", etc. Let's do that on
the main LANDAU Linux project page.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
First of all it's redundant to use the personal pronouns in the project
definition, since it's we who decide the project goal in anyway. Secondly
stating that the project improves the Linux kernel would sound a bit
too presumptuous. Let's define the project as fixing and extending the
Linux kernel instead. It won't change the gist but will seem softer.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
Indeed it must have been some typo or rudiment and has no any meaning with
respect to the text. Drop it for good.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Let's have a nice-looking footer with the document version, update date
and maintenance info instead of the boring Note-like list with the same
data.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Currently the links are rendered as just text. Let's convert them to being
clickable with descriptive names and proper highlight.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
It's a tough task to track changes in the long lines even with diff usage.
Let's apply the 80-char line constraints to the document at least for the
chapters body so to make diff's more readable.
Co-developed-by: Serge Semin <svsemin@unistemlab.com>
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Extend the description of the frequently used in the text specific words
and acronyms with the details in relation to the LANDAU project. Also move
the words list into a dedicated text table.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Drop it since the text above describes the process more than accessible.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Indeed it's content is basically the same as in the GIT-branches
description. Let's drop the chapter then and move the note to the later
paragraph.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
It was decided to mark the just released LANDAU Linux with EXTRAVERSION
set to 'l' which would also imply '0'. This shall make the version looking
different from the RC-stage just by absent '-rcX' suffix, but also looking
alike Linus' 'vV.P' release versioning with '.l' suffix added.
While at it fix somehow slipped in vX.Y.lZ format. It is supposed to be
unified vV.P.lZ.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
The LANDAU-linux maintenance document doesn't provide an important
information regarding the way the sub-LANDAU-Linux repositories are
supposed to be maintained. Moreover it is uncertain of how these changes
are supposed to be collected into a single LANDAU-Linux release. Let's fix
that by adding the detailed description of both of these processes into
the chapter 6 concerning the maintainers responsibilities. The text is
equipped with a mermaid gitGraph diagram visualising the GIT-flow in that
regard.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The chapter "5. LANDAU-Linux release process" is a bit lame. First of all
it constantly refers to a fixed release version v7.0.y meanwhile the
document implies an approach irrelevant to the version number. Secondly
the stages are differently described in the sub-paragraphs. Meanwhile it
can be done in the more structured way, like list of the steps, key stage
parameters and key notes. Thirdly the stages lack the details regarding
the commit creation and it' format. Finally the LTS version support is no
different from the stable release. So the current chapter 6. can be easily
merged into the paragraph 5.4.
Well ideally this should have been done in a set of the incremental
commits. But this would have taken too much effort seeing the changes are
interdependent. So let's introduce it in a refactor-like commit. This
doesn't change the gist of the release process, but extends the
description with the missing details and makes the text looking more
structured by the paragraphs style unification.
Co-developed-by: Dmitry Rokosov <rockosov@rulkc.org>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
At this moment it just states 'The Linux kernel 7.0 is released'. For the better
LANDAU-Linux release cycle understanding it would be good to provide more
details what it means from the LANDAU project point of view.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The text states that the initial condition is the Linux kernel 6.12
release. But the further example refers to the 7.0 version which is way
newer release. Fix the statement to indicate the correct version - 7.0.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
LANDAU-Linux RC stage is indicated by the version of the format 'l-rcX'.
Meanwhile the example lists them as just 'rcX', which is a bit misleading.
Fix that by adding the 'l-' prefix to the versions in the chapter 7.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The text mentions that the LANDAU Linux releases are always behind the
Linux kernel release. It's true but the lag is in one _PATCHLEVEL_ cycle
since LANDAU Linux is based on the last released Linux kernel version past
RC-cycle. Meanwhile _SUBLEVEL_ is the stable kernel update which might be
released even not once per week. Let's fix that.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
First of all the GIT-branches life-cycle block-scheme doesn't provide any
info regarding the "landau-next" branch even though it's presented in the
list of the main GIT-branches. Secondly the RC-stages is also missing in
the stages sheet. Thirdly there is no need in splitting up the
Normal(stable) and LTS branches diagram since their basic support is the
same.
Let's fix all of that by extending the GIT-branches description with the
details regarding the 'landau-next' GIT-branch and it' relation to
'landau-V.P.y'. Also provide some more insight about what 'support'
basically means in the framework of the LANDAU release cycle.
Co-developed-by: Dmitry Rokosov <rockosov@rulkc.org>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The text mostly uses the branch and repo words in reference to the GIT
versioning system. In order to reduce some level of uncertainty it's
better to add the "GIT-" prefix to these words to signify that the
messages particularly mean the GIT-branches and repositories.
Also there is no direct translation of the "Branching strategy" term.
Let's use a more correct wording in that case: "GIT-branch organization
strategy."
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The RC-stage version and tags format description is missing in the chapter
2. Meanwhile they are utilized afterwords in the chapters with the
detailed process description and in the examples. Let's add the "l-rcX"
version and "v7.0.l-rcX" tags format to have a more comprehensive Chapter
2. "Releases versioning format".
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
Since the text below uses the EOL abbreviation let's add it to the glossary
chapter. EOL means End-Of-Life - a final stage of the product life-cycle
indicating the end of the product support by means of the produce owner.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
Since the text below uses the MR abbreviation let's add it to the glossary
chapter. Basically it just means a standard git-like merge request. But in
case of the LANDAU-Linux notation (and the upstream Linux repo too) it can
be normally sent by an authorized person to be accepted.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
It's just "original repo", "source repo", "origin", etc. Use these more
correct alternatives instead or just drop if it's appropriate.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
First of all the English work "changelog" in the middle of the Russian
text looks inappropriate. It's just a literal "set of changes". Secondly
"upstream" is a literal "original repository" or just origin. Yes, in
general the "Bundle" name could be converted to something more appropriate
but there is no such need at this stage seeing it isn't utilized in the
text below.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
First of all the English work "maintenance" in the middle of the Russian
text looks inappropriate. Secondly the process described in the document
is already "official" by itself since it's presented in the repo
description. Finally let's collect the definitive nouns at the tail of the
sentence to summarize the description.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
The document describes the LANDAU Linux fork maintenance strategy.
Using just LANDAU sounds vague where the actual fork is referenced since
it might be interpreted as for any LANDAU fork. So let's explicitly use
the full fork-name in the document to avoid such ambiguity.
Signed-off-by: Serge Semin <svsemin@unistemlab.com>
|
|
Introduce the LANDAU Linux subproject under the LANDAU umbrella:
- Add landau-linux/index.md with project description, goals, and
key documents navigation
- Add landau-linux/maintenance.md with the comprehensive maintenance
manifest covering:
* Versioning scheme (VERSION.PATCHLEVEL.SUBLEVEL.lXYZ)
* Branching strategy (landau-next, landau-V.P.y)
* Release cycle and schedule
* RC testing process
* LTS support policy
* Maintainer responsibilities
* GPG signing requirements
* Squash policy with Co-developed-by attribution
These documents formalize the LANDAU Linux maintenance process and
establish the project as an upstream-first fork tracking mainline
and stable kernels.
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Replace the LANDAU Kernel-specific landing page with a broader
LANDAU umbrella project introduction. The new page presents LANDAU
as a collection of system components (Linux kernel, U-Boot, EFI,
QEMU, and more) under the Russian Linux Kernel Community (RULKC).
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
hugo requires this for some reason, otherwise refuses to render pages
on same level.
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
See original commit by Viacheslav Bocharov <v@baodeep.com>
https://github.com/adeepn/landau/commit/c694f9d9f41d0b5298fc822edcdfba61bceadb6c.
[Splitted checker into content repo site]
Signed-off-by: Nikita Shubin <nikita.shubin@maquefel.me>
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Summary changes
- Define LANDAU: Linux kernel Advanced for Next-gen Devices & Architectures
- Add Jekyll config with hacker theme
- Create main page with project vision and upcoming events
- Add Open Mic #001 page with agenda and registration
- Include RULKC contacts and Telegram channel
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
|
Signed-off-by: Dmitry Rokosov <rockosov@rulkc.org>
|
