Re: [BuildStream] Cleaning up BuildStream organization on GitLab
- From: Laurence Urhegyi <laurence urhegyi codethink co uk>
- To: BuildStream <buildstream-list gnome org>
- Subject: Re: [BuildStream] Cleaning up BuildStream organization on GitLab
- Date: Fri, 02 Aug 2019 12:12:56 +0100
Hi everyone,
I've now tidied up the BuildStream repos so that the group level landing
page is less cluttered:
https://gitlab.com/BuildStream
I filtered based on when things were last updated and archived the ones
which clearly have no current activity.
This can be very easily undone so please, if there are any issues, let
me know and we can address.
If you need to view a project that is archived, you can only do so via
the url. The projects that I have archived are:
https://gitlab.com/BuildStream/gnome-test-data
https://gitlab.com/BuildStream/defs2bst
https://gitlab.com/BuildStream/jhbuild2bst
https://gitlab.com/BuildStream/gnome-modulesets-base
https://gitlab.com/BuildStream/debootstrap-ostree
https://gitlab.com/BuildStream/debsrc2bst
https://gitlab.com/BuildStream/buildstream-sysroots
https://gitlab.com/BuildStream/cargo-fetcher
https://gitlab.com/BuildStream/glade-demo
https://gitlab.com/BuildStream/buildstream-examples
https://gitlab.com/BuildStream/buildstream-integration
Thanks,
Laurence
On 2019-07-02 23:13, Laurence Urhegyi wrote:
Sorry for the late response on this one - I've been away on holiday.
Yes I'll pick this up.
Cheers,
Laurence
On 2019-06-27 09:17, Sander Striker wrote:
That sounds like a plan then. Laurence, are you picking that up?
Cheers,
Sander
On Mon, Jun 24, 2019 at 8:34 PM Laurence Urhegyi via buildstream-list
<buildstream-list gnome org> wrote:
Hi Chandan,
I think it's a good idea (we actually discussed it during the irc
meeting a few weeks back too).
One thing we could look at is archiving the projects instead of
deleting:
https://docs.gitlab.com/ee/user/project/settings/#archiving-a-project
I think we take each project on a case by case, locate the
owner/maintainer and liaise with them to shut it down. I think this
is
non controversial and we can get started on it without delay.
Cheers,
Laurence
On 2019-06-24 19:07, Chandan Singh wrote:
Hi all,
I was browsing the list of repositories under the BuildStream
organization on
GitLab [1] and we appear to have accumulated a lot of repositories
over
time.
I, for one, don't think we actually need all of them. For some of
them,
I am not
sure if the BuildStream organization is the right place.
I think there's value in ensuring that the organization page
doesn't
list
things that are outdated or unsupported.
Sorry to pick on certain projects but here are some examples of
what I
am
talking about:
* gnome-test-data [2] describes itself as "A temporary project,
this
should be removed soon". It was last updated an year ago, and
evidently
hasn't been removed :)
* bst-plugins-ostree was never used, but exists.
* I am also unsure whether the nosoftware subgroup [4] is used by
anyone or
anything.
So, I wanted to ask how others feel about this? And if people
agree,
how should
we proceed?
Cheers,
Chandan
[1]: https://gitlab.com/BuildStream
[2]: https://gitlab.com/BuildStream/gnome-test-data
[3]: https://gitlab.com/BuildStream/bst-plugins-ostree
[4]: https://gitlab.com/BuildStream/nosoftware
_______________________________________________
buildstream-list mailing list
buildstream-list gnome org
https://mail.gnome.org/mailman/listinfo/buildstream-list
_______________________________________________
buildstream-list mailing list
buildstream-list gnome org
https://mail.gnome.org/mailman/listinfo/buildstream-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]