This is a super update report, thanks for sharing
CPE have activated an open source license for Gitlab to trial out some of the workflows and features. This is their top level SaaS offering which they grant to all open source projects so it has all the features we would need for testing.
Stephen (on CC) and I have admin access. I'd love to grant folks in the SIG access, if someone can ping me a list of emails that are associated with a gitlab.com account (you need to register!) I can make that happen.
Leigh
On Thu 24 Jun 2021, 10:17 Tomas Tomecek, <ttomecek@xxxxxxxxxx> wrote:
Greetings from the Fedora source-git SIG! We are planning to start
publishing reports of what we are working on so everyone can easily
pay attention and get involved if interested. If you have any ideas,
comments or requests, don’t be shy and let us know :)
Here’s a short list of things which we are working on.
## Choosing git forge to host source-git repositories
We need to find a home for all the source-git repositories. This is
actually a really hard task because we have many options (github.com,
gitlab.com, pagure.io, src.fedoraproject.org, something custom or
on-premise) and different expectations: some projects already have
repos set up on different platforms while Pagure is the primary forge
now. Since the CPE team is investigating GitLab as a forge, it's even
harder for us to figure out the primary forge. We may end up
supporting both actually: pagure.io and gitlab.com. What are your
thoughts on this topic? Would you prefer pagure.io or gitlab.com
More info:
* https://pagure.io/fedora-source-git/sig/issue/1
* https://pagure.io/fedora-source-git/sig/issue/7
## High-level workflow proposal up for review
Hunor proposed a high-level workflow linked below and I strongly
recommend reading it. We have also started discussing many details in
the process, such as getting archives: should we generate one from the
source-git repo or use the official release archive from upstream?
Another big topic in terms of workflows are rebases (= updates to the
latest upstream release, which are very common in Rawhide). Rebases
are straightforward in dist-git, but when your source-git repo has
complete upstream git history, they are no longer trivial, especially
if one wants to get a review of a rebase.
More info:
* https://pagure.io/fedora-source-git/sig/issue/2
* Workflow proposal: https://pagure.io/fedora-source-git/docs/pull-request/2
* https://pagure.io/fedora-source-git/docs/blob/main/f/resources/CommitRules.pdf
* https://pagure.io/fedora-source-git/sig/issue/8
## Tooling
Packit is the tooling which will be used to work with source-git
repos. No surprise there I assume :D
* https://packit.dev/
We've done a lot of work here lately, mainly to polish the process of
creating source-git repos and doing updates of dist-git repositories
based on the source-git content.
* https://packit.dev/docs/source-git/work-with-source-git/
* https://github.com/packit/packit/releases
## Interested?
We meet biweekly on Wednesdays via gmeet, 2:30 - 3:30 UTC, next one is
scheduled for July 7th.
* https://calendar.fedoraproject.org/SIGs/2021/7/5/#m9982
Everyone is welcome to join the SIG or provide any feedback on the
issues and PRs above.
You can always find the latest information over here:
* https://fedoraproject.org/wiki/SIGs/Source-git
* https://pagure.io/fedora-source-git/sig/issues
I'd like to thank all the SIG members for being so active, so happy to
work with all of you!
Cheers,
Tomas
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
