Migrate to Gitea

Events from the world of KolibriOS and its developers
  • Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Well, finally
    It would be great to refer to previous discussions that finally led to the proposal below.

    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Why git?

    Modern
    There are more modern version control systems, e.g. pijul which is even written in Rust.
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Pull requests, commits will be checked before merging to master branch
    I am not sure a pull request is a unique feature of git. Automatic commit check and manual review is not related to git too.
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Multiple repositories, not all files will be in main repository
    I believe virtually every VCS allows several repos per host. SVN certainly does.

    So, maybe there are other reasons to use git.

    Sweetbread wrote: Sat Feb 24, 2024 5:40 pmWhy Gitea?
    What existing services do you propose to replace with gitea? How do you plan to move their contents?
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Open source
    Like all the web services we are currently using.
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Customizable
    What customizations are missing from our services that we want from gitea?
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Easy to use
    Is websvn hard to use?
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm (Almost?) same features as GitHub
    So, which features we would like to have?

    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm What is already done?

    Autobuild with Gitea Actions
    Why changing the current scheme that uses a post-commit hook? Will the autobuild via gitea actions work for direct commits to main?

    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm So, tag and offset will be used instead of revision number
    This way we will get rv0.7.7.0-1234 on the blue screen instead of r2345. Is it ok?
    Also, 'git show v0.7.7.0-1234' will not find the commit.
    Then, if the kernel logs its version as v0.7.7.0-1234, how should I find the corresponding commit?
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Is there any version specification?
    In what way version specification is connected to git or gitea?
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Filename format?
    kolibri_<tag>-<offset>-g<hash>.<ext>
    That g before <hash> breaks selection with a double click. Why is it needed?
  • dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Well, finally
    It would be great to refer to previous discussions that finally led to the proposal below.
    Migrate to GitHub
    Git or GitHub

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Why git?

    Modern
    There are more modern version control systems, e.g. pijul which is even written in Rust.
    Are that "more modern VCS" popular? Popularity means community, community means guides and tips

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Pull requests, commits will be checked before merging to master branch
    I am not sure a pull request is a unique feature of git. Automatic commit check and manual review is not related to git too.
    Git allows merging. Pull requests is just web interface for merging

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Multiple repositories, not all files will be in main repository
    I believe virtually every VCS allows several repos per host. SVN certainly does.
    Why it haven't done then? All files in one repository it's not good

    dunkaist wrote: Sun Feb 25, 2024 9:16 am So, maybe there are other reasons to use git.
    What's the reason continue using svn? Also, currently GSoC is going, why we scare the students with old websvn? Also, people wants git by results of voting

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Why Gitea?
    What existing services do you propose to replace with gitea? How do you plan to move their contents?
    Currently, websvn and bugtracker. Manualy.

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Open source
    Like all the web services we are currently using.
    But Gitea is still open source. It's not about websvn is not, it's about we can replace OSSP with OSSP

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Customizable
    What customizations are missing from our services that we want from gitea?
    Themes from community, for example

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Easy to use
    Is websvn hard to use?
    Fusty design

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm (Almost?) same features as GitHub
    So, which features we would like to have?
    1. Actions for builds
    2. Organisations for dividing main repository by many for different programming languages, programms not in builds etc.
    3. Pull requests to avoid that kind of situations
    4. Maybe, wiki in future
    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm What is already done?

    Autobuild with Gitea Actions
    Why changing the current scheme that uses a post-commit hook?
    "It's working -- don't touch" is not cool. Gitea allows, why not use it? In commit list we will see commits, that failed building/testing, then click add see where and why "without leaving the cash register".

    dunkaist wrote: Sun Feb 25, 2024 9:16 am Will the autobuild via gitea actions work for direct commits to main?
    Yep

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm So, tag and offset will be used instead of revision number
    This way we will get rv0.7.7.0-1234 on the blue screen instead of r2345. Is it ok?
    Why not?

    dunkaist wrote: Sun Feb 25, 2024 9:16 am Also, 'git show v0.7.7.0-1234' will not find the commit.
    Then, if the kernel logs its version as v0.7.7.0-1234, how should I find the corresponding commit?
    Then there will also hash

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Is there any version specification?
    In what way version specification is connected to git or gitea?
    In git there is no revision number. Then we need another way to indentificate the commit - git describe. It returns tag, offset and hash. Tag is version, then we need in version specification

    dunkaist wrote: Sun Feb 25, 2024 9:16 am
    Sweetbread wrote: Sat Feb 24, 2024 5:40 pm Filename format?
    kolibri_<tag>-<offset>-g<hash>.<ext>
    That g before <hash> breaks selection with a double click. Why is it needed?
    Ok, without g
  • Who is online

    Users browsing this forum: Ahrefs [Bot] and 8 guests