profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/brianclemens/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Brian Clemens brianclemens @ctrliq @resf https://resf.org Solutions Architect at Ctrl IQ / Project Manager at The Rocky Enterprise Software Foundation

hpcng/singularity 2097

Singularity: Application containers for Linux

hpcng/warewulf 31

Warewulf is a stateless and diskless container operating system provisioning system for large clusters of bare metal and/or virtual systems.

hpcng/singularity-userdocs 21

User Documentation

hpcng/singularity-admindocs 7

Admin documentation

ctrliq/warewulf-docs 2

Sphinx documentation for Warewulf

brianclemens/bitlbee-docker 1

🐝 Fully-loaded BitlBee Docker Container 🐳

brianclemens/puppetlabs-apache 0

Puppet module for the Apache httpd server, maintained by Puppet, Inc.

brianclemens/warewulf 0

Warewulf is a stateless and diskless container operating system provisioning system for large clusters of bare metal and/or virtual systems.

hpcng/hpcng.org 0

HPCng website

issue closedrocky-linux/infrastructure

[logic] why ?

Why did you choose to split this project on multiple platforms ... GITHUB of all ... and the issues on bugzilla ? if you expect people to signup on a new platform, why not choose gitlab ? IT'S FREE

closed time in 3 days

cybernet

issue commentrocky-linux/infrastructure

https://wiki.rockylinux.org/Infrastructure is not found

Please see: https://wiki.rockylinux.org/team/infrastructure

yifengyou

comment created time in 3 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 9ecf10d1fb7c1d9906879de43c65fd55fa0627bf

address ldap_attrs

view details

push time in 13 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 0ce89a2a05687a7ad1327b8f698de123334abe0d

fix name

view details

push time in 13 days

push eventShougo/shougo-s-github

Shougo Matsushita

commit sha 15fb17b9e20397adebd2997a267b61634e983a62

Update

view details

push time in 16 days

issue commentrocky-linux/infrastructure

[logic] why ?

Hi @cybernet -

Ultimately, we're still figuring out what works best, what we need, and where we can simplify. That being said, the decision regarding bugzilla came down to the following:

  • GitLab (or GitHub) can host source code in the future (it doesn't right now) and issues will be for the code
    • Think of Fedora pagure for their source code issues and they use bugzilla.redhat to deal with distribution issues.
  • Bugzilla will be the distribution tracker.
    • It did not make sense to have a distribution bug tracker in Git. The organization does not allow for that and we also don't want to open groups/projects just to field issues with the distribution. The git contributor agreement does explain this.

In summary, there should be a logical separation between source code issues (which is very little) and actual distribution issues (which will likely be higher for a long while). But, this brings up some other things:

  • We don't like the idea of having disorganization on github issues or consolidating things into a single unorganized bucket
    • Git(hub|lab) issues are great, but not for something that is complex, like a distribution and its infrastructure requirements.
  • Creating projects/groups for things that won't have code to host issues did not make logical sense
  • Release Engineering tools already hook into bugzilla and git and use them for their specific use cases.

Hopefully that gives some clarity on the use of bugzilla - where everything will "live" long term remains to be seen. We've only been at it for a few months.

If you have any follow up questions, I'd be happy to try and answer them!

cybernet

comment created time in 21 days

issue openedrocky-linux/infrastructure

[logic] why ?

Why did you choose to split this project on multiple platforms ... GITHUB of all ... and the issues on bugzilla ? if you expect people to signup on a new platform, why not choose gitlab ? IT'S FREE

created time in 21 days

issue closedrocky-linux/infrastructure

[Bug Tracker] Enable SSO on Mantis Bug Tracker

Based on the following ticket, we are looking to enable SSO with keycloak. SAML or OIDC both work and are acceptable. The plugin will have to be in PHP as the bug tracker is built with PHP (mantis bt). There are example plugins in the mantis github but they are not maintained or poorly documented.

closed time in 21 days

nazunalika

issue commentrocky-linux/infrastructure

[Bug Tracker] Enable SSO on Mantis Bug Tracker

they fixed it mate :) they chose bugzilla ...

nazunalika

comment created time in 21 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 4359de6300e140bf75691cf8f38a0ab4f1371108

update tree

view details

push time in 22 days

push eventrocky-linux/infrastructure

Louis Abel

commit sha e5c57418d54d661a471b218697f7fcde4cce1d82

Merge pull request #14989 from rocky-linux/develop Develop

view details

push time in 22 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 8fdb68fddeafe32ee0fc65c566e36169f26dd054

forgot one perl module

view details

nazunalika

commit sha 9924afd0994c4aed217699ffbe748e5df00cb388

add one more module

view details

Louis Abel

commit sha e5c57418d54d661a471b218697f7fcde4cce1d82

Merge pull request #14989 from rocky-linux/develop Develop

view details

push time in 22 days

PR merged rocky-linux/infrastructure

Develop
+3 -1

0 comment

1 changed file

nazunalika

pr closed time in 22 days

PR opened rocky-linux/infrastructure

Develop
+3 -1

0 comment

1 changed file

pr created time in 22 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 9924afd0994c4aed217699ffbe748e5df00cb388

add one more module

view details

push time in 22 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 8fdb68fddeafe32ee0fc65c566e36169f26dd054

forgot one perl module

view details

push time in 24 days

push eventrocky-linux/infrastructure

Louis Abel

commit sha 5d8f09f683fd545a49ecf95d24825b0fcaa5d29f

Merge pull request #14988 from rocky-linux/develop fix lint

view details

push time in 24 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 2b5141255cd699fcd2375e5a71128724eaa45160

fix lint

view details

Louis Abel

commit sha 5d8f09f683fd545a49ecf95d24825b0fcaa5d29f

Merge pull request #14988 from rocky-linux/develop fix lint

view details

push time in 24 days

PR merged rocky-linux/infrastructure

fix lint
+7 -4

0 comment

1 changed file

nazunalika

pr closed time in 24 days

PR opened rocky-linux/infrastructure

fix lint
+7 -4

0 comment

1 changed file

pr created time in 24 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 2b5141255cd699fcd2375e5a71128724eaa45160

fix lint

view details

push time in 24 days

push eventrocky-linux/infrastructure

Louis Abel

commit sha ff9d39342ac15a3d6f5b0776667f912bc04d349f

Merge pull request #14987 from rocky-linux/develop Bugzilla

view details

push time in 24 days

push eventrocky-linux/infrastructure

nazunalika

commit sha 81aa7faa26a74d34d6c3de0e02a9575e4283ed34

add gitlab runner

view details

nazunalika

commit sha f05ade9fe40b89516b05d2d8a88894c89e67d55b

add PDR disable

view details

nazunalika

commit sha 46fa4fab255b78e6d579a13a23e5c81f1fbf51cf

update PDR

view details

nazunalika

commit sha 3d32fa1988685a7b5dc0cab2f3a9c6ec5718a33d

add gitlab adhocs

view details

nazunalika

commit sha d532f6a28dca1682e6c8555981e1220e49d1e809

bugzilla

view details

nazunalika

commit sha ff44b35cc86ca880801beee0639e419e2010919d

bugzilla

view details

Louis Abel

commit sha ff9d39342ac15a3d6f5b0776667f912bc04d349f

Merge pull request #14987 from rocky-linux/develop Bugzilla

view details

push time in 24 days

PR merged rocky-linux/infrastructure

Bugzilla
+618 -4

0 comment

16 changed files

nazunalika

pr closed time in 24 days

PR opened rocky-linux/infrastructure

Bugzilla
+618 -4

0 comment

16 changed files

pr created time in 24 days

push eventrocky-linux/infrastructure

nazunalika

commit sha d532f6a28dca1682e6c8555981e1220e49d1e809

bugzilla

view details

nazunalika

commit sha ff44b35cc86ca880801beee0639e419e2010919d

bugzilla

view details

push time in 24 days

push eventShougo/shougo-s-github

Shougo Matsushita

commit sha 9b63c114dc6b0dbd390c9f23bc2d82b260c0a344

Update

view details

push time in a month

issue openedrocky-linux/infrastructure

[Bug Tracker] Enable SSO on Mantis Bug Tracker

Based on the following ticket, we are looking to enable SSO with keycloak. SAML or OIDC both work and are acceptable. The plugin will have to be in PHP as the bug tracker is built with PHP (mantis bt). There are example plugins in the mantis github but they are not maintained or poorly documented.

created time in a month