Andrea Veri commented:
OK, issues and code were moved successfully. You'll find issues being created
by myself, that's totally expected. :)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_839789
You're
Andrea Veri commented:
@mcatanzaro you're welcome! waiting for @bberg to coordinate with me so we can
migrate issues and repo directly :)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_839050
You're receiving
Andrea Veri commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_839048
@bberg, mind joining #sysadmin on irc.gnome.org so we can quickly coordinate on
that one?
Thanks!
--
Reply to this email directly or view it on GitLab:
Michael Catanzaro commented:
Thanks av!
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_839049
You're receiving this email because of your account on gitlab.gnome.org.
Benjamin Berg commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_838940
Heh, I was thinking of the issue tracker primarily. git is easy enough to
simply push :)
--
Reply to this email directly or view it on GitLab:
Andrea Veri commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_838930
@bberg there you go: https://gitlab.gnome.org/GNOME/gnome-network-displays
--
Reply to this email directly or view it on GitLab:
Benjamin Berg commented on a discussion:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_838897
@averi ^ oops … typo
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_838897
You're
Benjamin Berg commented:
@avery, sorry, I should have updated the title. The repo should be
gnome-network-displays (designers suggested a rename).
Also, I would want to import everything from
https://github.com/benzea/gnome-network-displays. Is that possible or should I
create a new
Issue was closed by Andrea Veri
Issue #121: https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121
You're receiving this email because of your account on
Andrea Veri commented:
@mcatanzaro https://gitlab.gnome.org/GNOME/gnome-screencast has been finally
created :)
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/-/issues/121#note_838878
You're receiving this email because of your
Michael Catanzaro commented:
> Note: in the case of gnome-network-displays (formerly gnome-screencasts),
> this module is probably going to be a dependency of gnome-control-center. So
> it's likely going into core (or maybe core-deps) regardless. It seems very
> unlikely that any
GitLab Admin - Carlos Soriano commented:
> Note that the question here is not whether gnome-screencast is a GNOME
> project, but whether it can be uploaded to a new repository in the GNOME
> namespace. That distinction is one we started to make when moving to gitlab.
Right, didn't want to
Michael Catanzaro commented:
Note: in the case of gnome-network-displays (formerly gnome-screencasts), this
module is probably going to be a dependency of gnome-control-center. So it's
likely going into core (or maybe core-deps) regardless. It seems very unlikely
that any conceivable
Bastien Nocera commented:
> The official body that can decide what is considered a GNOME project is the
> board
Note that the question here is not whether gnome-screencast is a GNOME project,
but whether it can be uploaded to a new repository in the GNOME namespace. That
distinction is
GitLab Admin - Carlos Soriano commented:
And forgot to mention, I do understand the furstration. I also believe we
should have some interim solution, since it's taking signitifacntly longer that
I would have expected. I will have some chats around and see if we come up with
something.
--
GitLab Admin - Carlos Soriano commented:
@hadess I see, I guess a good oportunity for us to talk with daniels about this
and discuss ideas.
@mcatanzaro sorry, I didn't see your comment before. Unfortunately, what is
obvious to you might not be obvious to someone else, and it's not
Bastien Nocera commented:
> @hadess just to understand your issue, is this because fdo has a similar
> policy? Or are you saying that for some reason you are not able to create
> repositories in your personal space at GNOME gitlab and therefore need to use
> fdo personal space?
It's
GitLab Admin - Carlos Soriano commented:
@hadess just to understand your issue, is this because fdo has a similar
policy? Or are you saying that for some reason you are not able to create
repositories in your personal space at GNOME gitlab and therefore need to use
fdo personal space?
--
Bastien Nocera commented:
> @hadess, should we close this one or keep open if Carlos (or the Board) will
> come up with a process?
I'm not the OP, I was simply showing my similar frustrations.
--
Reply to this email directly or view it on GitLab:
Benjamin Berg commented:
@avery, please leave the bug open, the issue has not been resolved.
Also, I explicitly asked the board for a decision and clarification how these
cases should be handled today. So I hope that there will be news soon.
--
Reply to this email directly or view it on
Andrea Veri commented:
@hadess, should we close this one or keep open if Carlos (or the Board) will
come up with a process?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/121#note_745431
You're receiving this email
Bastien Nocera commented:
I've ended up using my own namespace on fd.o's gitlab for some stuff that's
really pretty core to the desktop experience.
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/121#note_745219
You're
Michael Catanzaro commented:
Carlos, until we have a process, can we please just put obviously-GNOME stuff
under GNOME? New core desktop components developed by Red Hat obviously belong
under GNOME/ and not under World/. What's happening currently is they're being
developed on GitHub
GitLab Admin - Carlos Soriano commented:
Sorry for the delay. The board is working on a process to make the question of
what is considered GNOME software a more straightforward decision. I think
there are two options here:
1. Move this now to the World group.
1. Wait until we finalise the
Andre Klapper commented:
@csoriano: Ping. Can you please reply?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/121#note_627565
You're receiving this email because of your account on gitlab.gnome.org.
Benjamin Berg commented:
@csoriano, what is the situation here? Is this request pending on something
else?
--
Reply to this email directly or view it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/121#note_505433
You're receiving this email because of your account
Benjamin Berg commented:
I have no idea what the status is right now (or if maybe I need to ping someone
else, e.g. the release team?), but there is a discussion from the designers to
rename to e.g. "Network Displays" which would likely also result in a rename of
the binary/repository as we
Andrea Veri commented:
@csoriano, waiting for your acknowledgement before proceeding :)
--
View it on GitLab:
https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/121#note_479827
You're receiving this email because of your account on gitlab.gnome.org.
28 matches
Mail list logo
