Ticket #1157 (closed general: fixed)

Opened 8 months ago

Last modified 8 months ago

change the way Initial Hosting Requests are processed

Reported by: besser82 Owned by:
Priority: major Keywords: meeting
Cc: Blocked By:
Blocking:

Description

phenomenon

When a new person is interressted in getting involved within the community by creating packages, one usually needs hosting space with the capability of direct linking. In Join the package collection maintainers there's mentioned a way how to request such hosting space.

The way these requests are processed is sub-optimal.

reason

The problems here are:

  1. Those requests are processed by a single person. Everybody just has limit ressources (time). Sometimes it takes about one or two weeks until new requests are processed (nothing against you, tibbs, in person --> limited ressources).
  2. The "fedorabugs" group is "abused". It was created for some different purpose, afaik.
  3. Packager-sponsors are not able to give webspace to new people in needing it.
  4. There's even no direct human contact involved during the whole process until the review-bug is filed. The "newbie" needs to find a way to get in touch with someone helping him / answering questions.

recommendation

  1. Create an own group for this purpose, e.g. "srpm-hosting".
  2. Give packager-sponsors the possibility to sponsor requestees to this new group.
  3. Assign those "Initial Hosting Request"-tickets to packager-sponsors ml.
  4. Add another step to Join the package collection maintainers wiki page after "Create your Fedora Account" like: "Create your Initial Package Ticket" to make sure there is a "real human" contact with a packager-sponsor rather early in the whole process, being a guide until the review-bug is filed. Alter the "Upload Your Package" step.

benefits

  1. Hosting requests can be processed quicker, because handling it up to a broader audiance. This gives the volunteers a sense of higher appreciation on his willingness to contribute.
  2. We have direct contact with new sponsorees a lot earlier in the whole joining-process.
  3. The newcomer has someone "on the hand" if he has questions or gets stuck.
  4. Communication between volunteer and packager-sponsor can be handled through the trac-ticket or some other way they agree upon with oneanother.

proposal for wiki page

Create your Initial Package Ticket

You will need some hosting space to upload your SRPM and SPEC files created in further steps onto the Internet somewhere so that others can retrieve them. Please visit the sponsors trac instance and file a ticket in the "Initial package hosting request" component. After this there will be someone to get in touch with you giving you some storage at http://fedorapeople.org and helping you through the process to that point when your Review Request gets filed and answering your questions.

Upload Your Package

Upload your SRPM and SPEC files onto your storage at http://fedorapeople.org, which was given to you earlier in the process, so that others can retrieve them.

Change History

comment:1 Changed 8 months ago by kevin

  • Keywords meeting added

I don't think everyone has had enough time to look at this, but if not, we can address it at the next meeting.

comment:2 follow-up: ↓ 3 Changed 8 months ago by kevin

A few things to note:

There is not a packager-sponsors list, it's a alias for everyone in the group.

I don't know if sponsors would want to step up and start working with someone before they even knew what they were going to package/submit. It might be that they are doing java packages, but the sponsor who sees their request doesn't know java, etc.

I do like the idea of trying to open communication with the new packager early on so they don't get discouraged. This may require a re-work of how we do sponsoring though.

comment:3 in reply to: ↑ 2 Changed 8 months ago by besser82

Replying to kevin:

A few things to note:

There is not a packager-sponsors list, it's a alias for everyone in the group.

I know, but it's called something like that in Provenpackager policy.

I don't know if sponsors would want to step up and start working with someone before they even knew what they were going to package/submit. It might be that they are doing java packages, but the sponsor who sees their request doesn't know java, etc.

Directly using your Java-example here, the sponsor in first-contact could point the newbie to the Java-SIG wiki-page...
It's not meant to start working with someone; it's more meant to be a guide, helping about where to look / to ask for informations and help.

I do like the idea of trying to open communication with the new packager early on so they don't get discouraged. This may require a re-work of how we do sponsoring though.

comment:4 Changed 8 months ago by kevin

We didn't get to this this week... will discuss fully next.

comment:5 Changed 8 months ago by toshio

  • Resolution set to fixed
  • Status changed from new to closed

This was forwarded to infrastructure, fedorabugs, and package-sponsors (fesco voted +5 to let them work out a solution). Over the course of the week, and spearheaded by nirik and besser82, I think a solution was worked out with the fedorabugs sponsors being expanded and being informed more readily of who would need sponsorship.

Note: See TracTickets for help on using tickets.