Bug 145318 – Add information about the process from bugzilla to portage

• Product: [OLD] Docs on www.gentoo.org
• Status: RESOLVED WONTFIX

[Description Chris Carlin 2006-08-28 00:37:25 UTC]

The "Contributing Ebuilds" document explains how users are to upload ebuilds to bugzilla, but then stops. It seems like a good idea to tell contributors what the process is from there on out.

Are users supposed to do anything else to help see their contribution through? I actually don't know and haven't run across the policy in the documentation.

In any case, it seems like something volunteers should know to keep them from being frustrated and keep them volunteering.

[Comment 1 Łukasz Damentko (RETIRED) 2006-09-02 06:53:38 UTC]

What can they do expect waiting patiently?

[Comment 2 Chris Carlin 2006-09-02 14:56:28 UTC]

Well I'm not sure. That's why I'm suggesting this addition in the first place :)

But seriously, currently a first-time ebuild author would be all excited. He's getting his program in portage! He's contributing to Gentoo! He's working out how it all works, probably spending a lot of time researching the issue, crafting the file, finally posting to bugzilla and hopefully getting feedback.

He's finally answered all criticisms and his ebuild is done! Hurray! And now on to portage.... right? Wait, why is his package sitting there at maintainer-wanted? The first time contributor is now confused and frightened. Is he supposed to do something else? Did he do something wrong?

It's pretty disillusioning to see all of this momentum just stop without warning. If the documentation said that the contributor would have to wait patiently for a developer then that would be fine. At least he would know that the next step is out of his hands. Better documentation might mention IRC and overlays.

I'm being humorous and dramatic here, but I hope you get the point. A new contributor probably expects his package to end up in portage, but the docs stop before that point.

[Comment 3 Łukasz Damentko (RETIRED) 2006-09-04 00:04:35 UTC]

There's not much a user can do except waiting. He can annoy the community, ask different devs in priv, spam our mailing lists, none of which we like or appreciate. Thanks for reporting but i have to mark it as wontfix.

[Comment 4 Chris Carlin 2006-09-04 05:12:02 UTC]

That's the point! To avoid having a user bugging the devs or having his feelings hurt the docs should indicate that now the user should wait patiently and that the process might take a while.