Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Discussion on user contributions to Gentoo: issues/proposals
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  
Author Message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 8229

PostPosted: Mon Dec 01, 2008 1:56 am    Post subject: Reply with quote

Why not just recruit bug wranglers either as staff or as developers without repository access? Once there is some practical experience with project specific bug wranglers further refinements could be put in place, if for example the staff quiz was insufficiently technical and the developer quizzes were overly technical for screening qualified bug wranglers. One advantage of using this approach is that it could be implemented now without waiting through the GLEP process.
Back to top
View user's profile Send private message
reavertm
Developer
Developer


Joined: 05 Feb 2004
Posts: 264
Location: Wrocław

PostPosted: Mon Dec 01, 2008 5:43 am    Post subject: Reply with quote

Yes, that could done this way - Gentoo Bug Wranglers Project does not specify any requirements for bug wranglers so I guess it's safe to assume that they could be (so far) recruited as staff. My proposal still would be valid - to introduce project-specified bug wranglers (it is necessary to narrow the scope thus lowering requirements). Where should I proceed to make it 'legal'?
_________________
Maciek
Back to top
View user's profile Send private message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 8229

PostPosted: Mon Dec 01, 2008 6:03 am    Post subject: Reply with quote

Ask a project lead if they want a bug wrangler, remind them that staff recruiting is valid for that role and that the recruiting process is simpler for staff. Bringing a finished quiz might help your case, just wait for them to mention it before offering it. Most of the answers are in the "Gentoo Developer Handbook", though others hide places like a GLEP or even a list of lists. If you are already involved to some extent with the project mentoring should be fairly easy to come by, and in some cases it is largely a formality even then.
Back to top
View user's profile Send private message
Rad
Guru
Guru


Joined: 11 Feb 2004
Posts: 381
Location: Berne, Switzerland

PostPosted: Sun Feb 15, 2015 1:22 am    Post subject: Reply with quote

Quote:
What could be other possibilities for people wanting to contribute, that are not currently used?

Try to adopt more of the projects of the wider ecosystem into Gentoo.

To give an impression of what I mean by that in spirit: Funtoo has patches to its Portage that may not all be irrelevant to everyone, Paludis and Pkgcore might be run in QA automated tests that run on ebuilds (even if reacting on failures might be non-binding), and maybe some of the Portage tools might become Portage functionality or at least part of a meta-package of useful tools with a snippet of documentation.

I can guess that some of these were a technical problem to get done, while others may just have been a lot of work that no one had any interest in. But I just think if the wider ecosystem has resources, and if those were tapped into, supported and maybe just plain acknowledged more, it might quite likely result in more contributions. And/or more happy situations, anyways.

Quote:
How and where could we best publicize these?

One idea: have a fancy graph / statistics sections about open bugs, ebuild requests, poor wiki articles, and so on in multiple prominent places. Especially the things that volunteers typically can most easily get involved in should be presented that way - graphs / statistics make people click, and numbers get people motivated as well.

I know that there is the bug tracker, but it's not even nearly as fancy as even p.g.o, and not really prominent or otherwise likely effective at catching average user's attention...
Back to top
View user's profile Send private message
Naib
Advocate
Advocate


Joined: 21 May 2004
Posts: 4427
Location: Removed by Neddy

PostPosted: Sun Feb 15, 2015 2:48 am    Post subject: Reply with quote

Rad wrote:


Quote:
How and where could we best publicize these?

One idea: have a fancy graph / statistics sections about open bugs, ebuild requests, poor wiki articles, and so on in multiple prominent places. Especially the things that volunteers typically can most easily get involved in should be presented that way - graphs / statistics make people click, and numbers get people motivated as well.

I know that there is the bug tracker, but it's not even nearly as fancy as even p.g.o, and not really prominent or otherwise likely effective at catching average user's attention...


Have you read the monthly newsletter? http://blogs.gentoo.org/news/2014/06/02/gentoo-monthly-newsletter-may-2014/
_________________
The best argument against democracy is a five-minute conversation with the average voter
Great Britain is a republic, with a hereditary president, while the United States is a monarchy with an elective king
Back to top
View user's profile Send private message
Rad
Guru
Guru


Joined: 11 Feb 2004
Posts: 381
Location: Berne, Switzerland

PostPosted: Mon Feb 16, 2015 2:04 pm    Post subject: Reply with quote

Naib wrote:
Have you read the monthly newsletter? http://blogs.gentoo.org/news/2014/06/02/gentoo-monthly-newsletter-may-2014/

Thanks for the reference! That's certainly a match with most of what I said. But it is not quite what I had in mind, mainly because of the intended audience. The newsletter is showing information mostly aimed at people in the core developer herds.

It's not so much about showing what work specifically needs doing by "anyone" - especially issues suitable for people not (yet?) part of a herd.

I think it would might be good to list specific things in a simple fashion: "package requests with no ebuild", "wiki pages marked as in need of more work", "wiki articles not reviewed in three years", "ebuilds that currently have no specific maintainer", "packages in need of a program patch", and so on.
Each would list individual issues linked directly to the place where you can get involved with fixing the specific issue in question, making it dead simple to pick and get started on something that you feel you probably can help with. [It might also be a good idea to add an instructive "how do I go about helping out in this category?" page that explains the formalities, maybe some terminology and where help is when you get stuck, as well as how the contributed work ties into the process the herd in question does.]
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8
Page 8 of 8

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum