Blocker Review discussion tickets -- now available
by Kamil Paral
Hello everyone,
I'd like to announce a new project of the QA team and an extension of the
BlockerBugs App [1]. The blocker and freeze exception proposals can now not
only be discussed during regular blocker review meetings [2], but also at
any time through discussion tickets hosted on Pagure [3]. So even if you
don't have time to participate in the meeting, you can still participate
and vote in those discussion tickets.
This will be mostly interesting to people who participated in blocker
review meetings in the past, but we hope we can attract new participants
this way. It is also very useful for package maintainers and developers,
because they can now easily provide feedback regarding a proposed blocker
or a freeze exception without attending a meeting at a particular time or
diluting a technical discussion in Bugzilla.
To participate, open the BlockerBugs App for a particular milestone (e.g.
F33 Beta [4]) and you'll see "Vote!" and "Discuss" links for
proposed/accepted blockers and freeze exceptions. Follow the links to see
tickets where you can express your opinion (which should ideally reflect
our release criteria [5]). You can vote according to the guide present at
[3], please read it carefully. A bot is following each ticket, updating the
voting summary, and accepting certain commands. Watching the Pagure repo
[3] also gives you the option to get notified about every new proposed
blocker/freeze exception.
We've been using these discussions for a week or two now (I apologize for a
late announcement) and so far our existing practice seems to be to vote for
proposals throughout the week using these discussion tickets, close those
which we can easily get enough votes and agree on, and discuss the
remainder during the next blocker review meeting. So the regular blocker
review meeting hasn't been replaced, but we use the discussion tickets to
cut down on the meeting length. We're still trying to figure out the best
approach to take here, so nothing is set in stone. The voting functionality
itself is also still in development, we'll try to provide new features and
improve the experience based on your feedback.
I'll be happy to answer questions, if there are any.
Thanks,
Kamil
Fedora QA
PS: Development credits go to Lukas Brabec, Frantisek Zatloukal, Tim Flink,
Josef Skladanka and Adam Williamson.
[1] https://qa.fedoraproject.org/blockerbugs/
[2] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[3] https://pagure.io/fedora-qa/blocker-review
[4] https://qa.fedoraproject.org/blockerbugs/milestone/33/beta/buglist
[5] https://fedoraproject.org/wiki/Fedora_Release_Criteria
3 years, 7 months
- 1
- 0
Orphaned packages looking for new maintainers
by Miro Hrončok
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2020-09-07.txt
grep it for your FAS username and follow the dependency chain.
For human readable dependency chains, see https://packager.fedorainfracloud.org/
For all orphaned packages, see https://packager.fedorainfracloud.org/orphan
Package (co)maintainers Status Change
================================================================================
apache-commons-dbcp mizdebsk, orphan 3 weeks ago
container-exception-logger abrt-sig, ekulik, mmarusak, 2 weeks ago
msuchy, orphan
dbus-java orphan 4 weeks ago
emacs-magit orphan, petersen 0 weeks ago
fedora-icon-theme orphan 0 weeks ago
freight orphan 0 weeks ago
fst orphan 4 weeks ago
geronimo-parent-poms jjelen, mizdebsk, orphan 2 weeks ago
golang-github-mholt- orphan 1 weeks ago
certmagic-0.9
joda-time mizdebsk, orphan 3 weeks ago
js-jquery-iframe-transport orphan 4 weeks ago
js-jquery-knob orphan 4 weeks ago
js-jquery-qrcode orphan 4 weeks ago
js-tag-it orphan 4 weeks ago
jvnet-parent mizdebsk, orphan 2 weeks ago
libmatthew-java orphan 4 weeks ago
liquibase awood, orphan 4 weeks ago
man-pages-de orphan, romal 4 weeks ago
marble-widget orphan, rdieter 1 weeks ago
mozilla-iot-gateway-addon-node orphan 4 weeks ago
mozilla-iot-gateway-addon- orphan 4 weeks ago
python
nodejs-babel-code-frame orphan 0 weeks ago
nodejs-base orphan 0 weeks ago
nodejs-bcrypt nodejs-sig, orphan 0 weeks ago
nodejs-body-parser orphan 0 weeks ago
nodejs-bufferutil nodejs-sig, orphan 0 weeks ago
nodejs-cache-base orphan 0 weeks ago
nodejs-call-matcher orphan 0 weeks ago
nodejs-core-util-is nodejs-sig, orphan 5 weeks ago
nodejs-cross-spawn nodejs-sig, orphan 0 weeks ago
nodejs-cross-spawn-async nodejs-sig, orphan 0 weeks ago
nodejs-css-stringify nodejs-sig, orphan, patches 2 weeks ago
nodejs-css-tree orphan 2 weeks ago
nodejs-doctrine galileo, nodejs-sig, orphan, 0 weeks ago
vjancik
nodejs-duplexer nodejs-sig, orphan 5 weeks ago
nodejs-duplexify nodejs-sig, orphan 5 weeks ago
nodejs-end-of-stream nodejs-sig, orphan 5 weeks ago
nodejs-espower-location- orphan 2 weeks ago
detector
nodejs-esrecurse nodejs-sig, orphan 0 weeks ago
nodejs-faucet orphan 0 weeks ago
nodejs-from nodejs-sig, orphan 5 weeks ago
nodejs-fs-dot-notify orphan 0 weeks ago
nodejs-gauge nodejs-sig, orphan 0 weeks ago
nodejs-global-prefix nodejs-sig, orphan 0 weeks ago
nodejs-grunt nodejs-sig, orphan, patches, 2 weeks ago
piotrp
nodejs-grunt-legacy-util nodejs-sig, orphan, patches, 0 weeks ago
piotrp
nodejs-http-signature nodejs-sig, orphan, patches 0 weeks ago
nodejs-jsonm nodejs-sig, orphan 0 weeks ago
nodejs-jsonstream nodejs-sig, orphan 0 weeks ago
nodejs-markdown-it-testgen nodejs-sig, orphan 0 weeks ago
nodejs-node-static nodejs-sig, orphan, tdawson 0 weeks ago
nodejs-nopt nodejs-sig, orphan, patches 0 weeks ago
nodejs-option-cache orphan 0 weeks ago
nodejs-raw-body nodejs-sig, orphan, patches 0 weeks ago
nodejs-readable-stream jsmith, nodejs-sig, orphan 5 weeks ago
nodejs-rechoir nodejs-sig, orphan 0 weeks ago
nodejs-require-yaml nodejs-sig, orphan 0 weeks ago
nodejs-rfile orphan 0 weeks ago
nodejs-rollup-plugin-commonjs orphan 0 weeks ago
nodejs-rollup-plugin-node- orphan 0 weeks ago
resolve
nodejs-snapdragon orphan 2 weeks ago
nodejs-socket-dot-io-parser orphan 0 weeks ago
nodejs-tap-mocha-reporter nodejs-sig, orphan 0 weeks ago
nodejs-tap-parser nodejs-sig, orphan 0 weeks ago
plexus-ant-factory mizdebsk, orphan 1 weeks ago
plexus-component-factories-pom mizdebsk, orphan 1 weeks ago
python-kaptan bowlofeggs, jcline, orphan 2 weeks ago
python-libtmux orphan 2 weeks ago
python-nnpy orphan 4 weeks ago
python-zope-configuration infra-sig, orphan, tdabasin 0 weeks ago
qrcode-generator orphan 4 weeks ago
relaxngDatatype dbhole, mizdebsk, orphan 1 weeks ago
relaxngcc orphan 1 weeks ago
rmic-maven-plugin mizdebsk, orphan 3 weeks ago
ruby-ldap orphan 5 weeks ago
rubygem-Ascii85 orphan, ruby-packagers-sig 0 weeks ago
rubygem-delayed_job orphan 2 weeks ago
rubygem- orphan 2 weeks ago
delayed_job_active_record
rubygem-elasticsearch orphan 5 weeks ago
rubygem-elasticsearch-api orphan 5 weeks ago
rubygem-fast_gettext brandfbb, orphan 5 weeks ago
rubygem-jgrep lkundrak, orphan, stevetraylen 0 weeks ago
rubygem-org-ruby orphan 2 weeks ago
rubygem-paint orphan 0 weeks ago
rubygem-rkerberos orphan 0 weeks ago
rubygem-ruby-rc4 orphan, ruby-packagers-sig 0 weeks ago
rubygem-rubypants orphan 2 weeks ago
rubygem-sigdump orphan 2 weeks ago
rubygem-wikicloth orphan 4 weeks ago
rubygem-wirb orphan 0 weeks ago
satyr abrt-sig, ekulik, mgrabovs, 2 weeks ago
mmarusak, msuchy, orphan
sonatype-oss-parent mizdebsk, orphan 2 weeks ago
umlgraph orphan 0 weeks ago
unboundid-ldapsdk orphan 5 weeks ago
unison213 gemi, orphan, rjones 5 weeks ago
unison227 brummbq, gemi, orphan, rjones, 5 weeks ago
timj
unison240 brummbq, orphan, rjones 5 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2020-09-07.txt
See dependency chains of your packages at https://packager.fedorainfracloud.org/
See all orphaned packages at https://packager.fedorainfracloud.org/orphan
Affected (co)maintainers (either directly or via packages' dependencies):
abompard: python-zope-configuration
abradshaw: rubygem-Ascii85, rubygem-ruby-rc4
abrt-sig: satyr, container-exception-logger
abrt-team: satyr, container-exception-logger
acaringi: sonatype-oss-parent
akurtakov: sonatype-oss-parent
amahdal: rubygem-Ascii85, rubygem-ruby-rc4
anishpatil: nodejs-css-stringify
anoopcs: rubygem-Ascii85, rubygem-ruby-rc4
asrob: rubygem-Ascii85, rubygem-ruby-rc4
athoscr: rubygem-Ascii85, rubygem-ruby-rc4
awood: liquibase
besser82: rubygem-Ascii85, rubygem-ruby-rc4
bowlofeggs: python-kaptan
brandfbb: rubygem-Ascii85, rubygem-fast_gettext, rubygem-ruby-rc4
brummbq: unison240, unison227
cfeist: rubygem-Ascii85, rubygem-ruby-rc4
chrisw: rubygem-Ascii85, rubygem-ruby-rc4
churchyard: rubygem-Ascii85, rubygem-ruby-rc4
cicku: rubygem-Ascii85, rubygem-ruby-rc4
ckyriakidou: rubygem-Ascii85, rubygem-ruby-rc4
clime: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
coolsvap: geronimo-parent-poms
copr-sig: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
cottsay: rubygem-Ascii85, rubygem-ruby-rc4
cquad: sonatype-oss-parent
dbhole: relaxngDatatype
dcallagh: nodejs-css-stringify
decathorpe: rubygem-Ascii85, rubygem-ruby-rc4
devos: rubygem-Ascii85, rubygem-ruby-rc4
dfateyev: rubygem-Ascii85, rubygem-ruby-rc4
djbw: rubygem-Ascii85, rubygem-ruby-rc4
dturecek: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
ebaron: sonatype-oss-parent
eclipse-sig: sonatype-oss-parent
ekulik: satyr, container-exception-logger
evgeni: rubygem-Ascii85, rubygem-ruby-rc4
fab: rubygem-Ascii85, nodejs-rechoir, nodejs-css-stringify, rubygem-ruby-rc4
fale: rubygem-Ascii85, rubygem-ruby-rc4
frostyx: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
galileo: sonatype-oss-parent, nodejs-doctrine
gchamoul: rubygem-Ascii85, rubygem-ruby-rc4
gemi: unison227, unison213
germano: rubygem-Ascii85, rubygem-ruby-rc4
gil: geronimo-parent-poms
hguemar: rubygem-Ascii85, rubygem-ruby-rc4
hhorak: sonatype-oss-parent
hobbes1069: rubygem-Ascii85, rubygem-ruby-rc4
honzaf: rubygem-Ascii85, rubygem-ruby-rc4
idevat: rubygem-Ascii85, rubygem-ruby-rc4
ignatenkobrain: rubygem-Ascii85, python-kaptan, python-libtmux, rubygem-ruby-rc4
infra-sig: python-zope-configuration
irina: rubygem-Ascii85, rubygem-ruby-rc4
jaruga: rubygem-Ascii85, rubygem-ruby-rc4
jcline: python-kaptan
jdeluyck: nodejs-rechoir
jerboaa: sonatype-oss-parent
jfilak: satyr, container-exception-logger
jhli: rubygem-Ascii85, rubygem-ruby-rc4
jhrozek: rubygem-Ascii85, rubygem-ruby-rc4
jjames: jvnet-parent
jjelen: geronimo-parent-poms, jvnet-parent, sonatype-oss-parent, apache-commons-dbcp
jjohnstn: sonatype-oss-parent
jpokorny: relaxngDatatype, rubygem-Ascii85, rubygem-ruby-rc4
jskarvad: rubygem-Ascii85, rubygem-ruby-rc4
jsmith: nodejs-cross-spawn, nodejs-css-tree, nodejs-css-stringify,
nodejs-end-of-stream, nodejs-grunt, nodejs-nopt,
nodejs-rollup-plugin-node-resolve, nodejs-readable-stream,
nodejs-grunt-legacy-util, nodejs-snapdragon, nodejs-rechoir,
nodejs-core-util-is, nodejs-cross-spawn-async, nodejs-cache-base,
nodejs-global-prefix, nodejs-base, nodejs-duplexify
jstanek: rubygem-Ascii85, rubygem-ruby-rc4
jsteffan: rubygem-Ascii85, rubygem-ruby-rc4
jstribny: rubygem-Ascii85, rubygem-ruby-rc4
jussilehtola: rubygem-Ascii85, rubygem-ruby-rc4
jvanek: sonatype-oss-parent
kanarip: rubygem-Ascii85, rubygem-ruby-rc4
kdaniel: sonatype-oss-parent
keitellf: rubygem-Ascii85, rubygem-ruby-rc4
kkeithle: rubygem-Ascii85, rubygem-ruby-rc4
lef: jvnet-parent, sonatype-oss-parent
lkundrak: rubygem-jgrep
luya: nodejs-css-tree
m4rtink: satyr
maha: rubygem-Ascii85, rubygem-ruby-rc4
mbooth: sonatype-oss-parent
mef: sonatype-oss-parent
mgrabovs: satyr, container-exception-logger
mizdebsk: geronimo-parent-poms, jvnet-parent, sonatype-oss-parent,
apache-commons-dbcp, relaxngDatatype, plexus-ant-factory,
plexus-component-factories-pom, rmic-maven-plugin, joda-time
mlisik: rubygem-Ascii85, rubygem-ruby-rc4
mmarusak: satyr, container-exception-logger
mmorsi: rubygem-Ascii85, joda-time, sonatype-oss-parent, rubygem-ruby-rc4
moceap: geronimo-parent-poms
mojavelinux: rubygem-Ascii85, rubygem-ruby-rc4
mso: fedora-icon-theme
msuchy: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util, satyr,
container-exception-logger
ngompa: rubygem-Ascii85, rubygem-ruby-rc4
niveusluna: rubygem-Ascii85, rubygem-ruby-rc4
nodejs-sig: nodejs-bufferutil, nodejs-css-stringify, nodejs-duplexer,
nodejs-nopt, nodejs-tap-parser, nodejs-markdown-it-testgen, nodejs-core-util-is,
nodejs-cross-spawn-async, nodejs-from, nodejs-end-of-stream, nodejs-grunt,
nodejs-jsonm, nodejs-rechoir, nodejs-esrecurse, nodejs-node-static,
nodejs-cross-spawn, nodejs-css-tree, nodejs-doctrine, nodejs-bcrypt,
nodejs-grunt-legacy-util, nodejs-http-signature, nodejs-readable-stream,
nodejs-jsonstream, nodejs-tap-mocha-reporter, nodejs-global-prefix,
nodejs-raw-body, nodejs-duplexify, nodejs-snapdragon, nodejs-require-yaml,
nodejs-gauge
nonamedotc: rubygem-Ascii85, rubygem-ruby-rc4
olysonek: rubygem-Ascii85, rubygem-ruby-rc4
omular: rubygem-Ascii85, rubygem-ruby-rc4
patches: nodejs-css-stringify, nodejs-grunt, nodejs-nopt,
nodejs-readable-stream, nodejs-grunt-legacy-util, nodejs-http-signature,
nodejs-rechoir, nodejs-core-util-is, nodejs-raw-body
pbrobinson: rubygem-Ascii85, rubygem-ruby-rc4
pcahyna: rubygem-Ascii85, rubygem-ruby-rc4
petersen: emacs-magit
piotrp: nodejs-css-stringify, nodejs-grunt, nodejs-nopt,
nodejs-grunt-legacy-util, nodejs-jsonstream
pknirsch: rubygem-Ascii85, rubygem-ruby-rc4
ppisar: rubygem-Ascii85, rubygem-ruby-rc4
praiskup: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
pstodulk: rubygem-Ascii85, rubygem-ruby-rc4
pvalena: rubygem-Ascii85, rubygem-ruby-rc4
raphgro: sonatype-oss-parent
rdieter: marble-widget
rgrunber: sonatype-oss-parent
rjones: unison240, unison227, unison213
romal: man-pages-de
ruby-packagers-sig: rubygem-Ascii85, rubygem-ruby-rc4
rust-sig: rubygem-Ascii85, rubygem-ruby-rc4
sagitter: nodejs-rechoir
salimma: rubygem-Ascii85, rubygem-ruby-rc4
sandeen: rubygem-Ascii85, rubygem-ruby-rc4
sdgathman: sonatype-oss-parent, nodejs-nopt
sdyroff: rubygem-Ascii85, rubygem-ruby-rc4
sergiomb: js-jquery-iframe-transport, nodejs-css-stringify
simo: rubygem-Ascii85, rubygem-ruby-rc4
skisela: rubygem-Ascii85, rubygem-ruby-rc4
snecker: rubygem-Ascii85, rubygem-ruby-rc4
spike: geronimo-parent-poms
spontsle: rubygem-Ascii85, rubygem-ruby-rc4
stevetraylen: rubygem-jgrep
stingray: rubygem-Ascii85, rubygem-ruby-rc4
tc01: jvnet-parent, nodejs-css-stringify, nodejs-bufferutil, nodejs-grunt,
nodejs-nopt, relaxngDatatype, nodejs-readable-stream, nodejs-grunt-legacy-util,
nodejs-core-util-is, nodejs-raw-body, nodejs-body-parser
tdabasin: python-zope-configuration
tdawson: nodejs-readable-stream, nodejs-core-util-is, nodejs-node-static
thias: rubygem-Ascii85, rubygem-ruby-rc4
thm: rubygem-Ascii85, rubygem-ruby-rc4
timj: unison227
tmz: rubygem-Ascii85, rubygem-ruby-rc4
tojeline: rubygem-Ascii85, rubygem-ruby-rc4
tross: rubygem-Ascii85, rubygem-ruby-rc4
valtri: rubygem-Ascii85, rubygem-ruby-rc4
vishalv: rubygem-Ascii85, rubygem-ruby-rc4
vjancik: nodejs-readable-stream, nodejs-core-util-is, nodejs-doctrine,
nodejs-css-stringify
vondruch: rubygem-Ascii85, rubygem-ruby-rc4
vtrefny: satyr
xavierb: nodejs-grunt, nodejs-nopt, nodejs-grunt-legacy-util
xenithorb: rubygem-Ascii85, rubygem-ruby-rc4
zbyszek: sonatype-oss-parent
zvetlik: nodejs-readable-stream, nodejs-core-util-is, nodejs-css-stringify
zzambers: sonatype-oss-parent
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py
3 years, 7 months
- 1
- 0
Gitlab Ask Me Anything - Sept 10th, 13:30 UTC
by Aoife Moloney
Good Morning folks,
As you likely remember, a little while ago now, was announced the decision to
move dist-git to a gitlab instance. This decision was the results of different
factors which included a wish for Red Hat to have a consistent tooling and
experience across the different distribution it works on or with, meaning:
RHEL, CentOS-Stream, CentOS Linux and Fedora.
Since then, a number of technical requirements needed to use gitlab in Fedora,
were gathered and a ticket was opened at gitlab to track them [1] but up until
now the progress on the Fedora side has been fairly slow. This is mostly due to
the feedback from Fedora that followed this decision, leading to a focus on the
first two distributions in the list above.
However, in order to progress the evaluation of gitlab, we have organized an
"Ask Me Anything" (AMA) session with the gitlab folks on Thursday September 10th
2020, at 13:30 UTC on #fedora-meeting-1 on irc.freenode.net.
The idea is to have an open floor for anyone in the community to discuss with
GitLab the technical merits that GitLab has, as well as the requirements we, the
Fedora community, have.
In order for this session to be productive, we believe that it may be wise to
start gathering questions to GitLab early on, so they can also look into them
and prepare their answers (I'm sure we all prefer to have actual answers rather
than: "hm, I don't know, let me check and I'll get back to you on this"). Of
course, we will still be able to ask question at the last minute or even during
the session.
Gathering them as early as possible is just a way for GitLab to see what
interests us, who may be the right persons to attend this session and overall to
make this hour as productive as possible.
So there are two ways for you to submit your questions to the GitLab folks on a
potential deployment of GitLab as a front-end to our dist-git (ie:
src.fedoraproject.org):
- A public hackmd document:
https://hackmd.io/RW8HahOeR7OJPON1dwuo3w#
Underneath each questions you will also be able to vote (simply add a ``+1`` to
the ``Votes:`` line), the most popular questions will be asked first.
Since this document is public, please be mindful of what previous
people entered.
- A discussion on forum.gitlab.com at:
https://forum.gitlab.com/t/fedora-migration-to-gitlab-ask-me-anything-ama...
The questions that we will not have time for, or cant be answered during the
session, will be answered afterward. The AMA minutes will be sent in the CPE
weekly mail, the hackmd will be updated and and summary published on
the community
blog.
Looking forward to the discussion,
Aoife
[1] https://gitlab.com/gitlab-org/gitlab/-/issues/217350
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
3 years, 7 months
- 1
- 0
About the Future of Communishift
by Aoife Moloney
Good Morning Everyone,
I wanted to share with you some information regarding the current
state and future of Communishift. The infrastructure team presented on
this project back in 2019 during Nest [1] [2], and since then, we have
deployed it, started using it and had to shut it down for
the colo-move.
As a number of people have noted, it has not come back up yet, and
during Nest this year, we had hinted that communishift is not going to
come back alive looking
the same as when we shut it down, and that is unfortunately true.
The idea for communishift was to give to anyone in the community a place where
they could run any application they wish to provide to the community.
This was a proper place where Joe and Jane could offer the service foo to the
foo SIG without engaging the infrastructure's team responsibility to keep the
service up and running. The infrastructure team would have been able to say:
"well the openshift cluster is running, so if the app isn't, talk to the
application maintainer, there is nothing we can do about it".
Basically, it gave a place where we could experiment with new apps
without adding too
much work to the infrastructure team.
However, the General Data Protection Regulation (GDPR) [3] and the California
Consumer Privacy Act (CCPA) [4] basically makes the Fedora Infrastructure team
(and thus Red Hat) responsible for the content hosted by any services running in
our infrastructure. In other words, the Fedora Infrastructure team would be
responsible to answer all GDPR/CCPA related requests and requirements for any
and all services running in communishift (services that the team has 0 knowledge
about, that's the whole goal of communishift).
For these reasons communishift is not going to come back to life in the same way
it was shut down for the colo move.
We have not given up on the original idea though (ie: providing a place where
community members can deploy applications without adding work on the
infrastructure team), however, as with anything involving legal, this is going
to be a slow process. We will share any information as soon as we are able.
We're sorry for the inconvenience this causes, we really would like the
situation to be different but we also appreciate these regulations for what they
are (protecting our personal information) so we want to respect them.
Hoping this clarifies the situation around communishift a bit.
Aoife, Kevin & Pingou
- On behalf of the Fedora Infrastructure team
[1] https://fedoraproject.org/wiki/Infrastructue/Communishift
[2] https://www.youtube.com/watch?v=phCHilTEQb4&list=PL0x39xti0_64C75dRUuwlXl...
[3] https://gdpr-info.eu/
[4] https://www.oag.ca.gov/privacy/ccpa
[4] https://www.oag.ca.gov/privacy/ccpa
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
3 years, 7 months
- 1
- 0