Bug 1974965

Summary:	Review Request: jello - Query JSON at the command line with Python syntax
Product:	[Fedora] Fedora	Reporter:	Kelly Brazil <kellyjonbrazil>
Component:	Package Review	Assignee:	Nobody's working on this, feel free to take it <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	code, eclipseo, package-review
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-02-28 15:53:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kelly Brazil 2021-06-22 20:36:41 UTC

Spec URL: https://jello-packages.s3.us-west-1.amazonaws.com/fedora/jello.spec
SRPM URL: <srpm info here>
Description: Query JSON at the command line with Python syntax
Fedora Account System Username: kellyjonbrazil

Hi team,

I am the developer of Jello (also JC) and I would like to request Jello to be packaged for Fedora. I created a src rpm spec similar to what we used for JC, so it should be pretty straightforward. I would prefer not to be the maintainer of the package.

https://github.com/kellyjonbrazil/jello

Thanks!
Kelly

Comment 1 Robert-André Mauchin 🐧 2021-07-03 13:27:47 UTC

> I would prefer not to be the maintainer of the package.

If you post a Review request here, it is to become the maintainer of the package. If you want someone to be maintainer of the package, you have to find someone willing to do it. I suggest sending a mail to the devel mailing list asking for help:

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/

Try also asking the maintainer of JC if they are interested in maintaining your package.

Comment 2 Ben Beasley 2022-02-28 15:53:19 UTC


*** This bug has been marked as a duplicate of bug 2059247 ***