Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 83426 - Clarification of Q17 in End-Of-Mentoring Quiz
Summary: Clarification of Q17 in End-Of-Mentoring Quiz
Status: RESOLVED WONTFIX
Alias: None
Product: Community Relations
Classification: Unclassified
Component: Developer Relations (show other bugs)
Hardware: All All
: High normal
Assignee: Gentoo Community Relations Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-26 18:43 UTC by Alex Howells (RETIRED)
Modified: 2007-08-01 19:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Howells (RETIRED) gentoo-dev 2005-02-26 18:43:55 UTC
Could the end-of-mentoring quiz please be clarified slightly from question 17 and mention something along the lines of "Assume you are able to test on all of the architectures below" since that is what the question requires, instead of a reply that would include only architectures the developer can in reality test for when answering the quiz.

Thanks.
Comment 1 Donnie Berkholz (RETIRED) gentoo-dev 2005-02-26 20:20:24 UTC
Why should that assumption be made?
Comment 2 Tim Yamin (RETIRED) gentoo-dev 2005-02-26 20:33:25 UTC
Well, I believe this is what Obz intended to be the needed clarification for the question on the feedback he gave; Mike, could you please comment?
Comment 3 Mike Gardiner (RETIRED) gentoo-dev 2005-02-26 20:59:33 UTC
That wasn't quite the clarification that I was talking about.

Here's the situation:
foomatic-1.3 (KEYWORDS="x86 sparc ~mips amd64")

foomatic-1.4 depends on libfnord-1.2
libfnord-1.2 (KEYWORDS="x86 ~sparc")

Therefore,
foomatic-1.4 (KEYWORDS="~x86 ~sparc") and a test-request to the mips and amd64 teams, informing them on the situation - that is libfnord and foomatic need keywording for their architectures.

That doesn't imply that you need access to SPARC - libfnord has allready been keyworded ~sparc (we assumed it's been tested and works), and so we can keep the keyword for foomatic - assuming the change isn't so great that sparc need to re-test and keyword foomatic.

So the answer should be KEYWORDS="~x86 ~sparc"

However, my clarification, was that based on the architecture of the new dev, and how they interpret the question, you can also end up with KEYWORDS="~x86 ~sparc ~<new devs arch>".

So there are really two things here:
o)  do we assume the change isn't so great that you need to drop the ~sparc keyword and have them re-test and keyword sparc.
o)  should the dev consider their architecture in the question, or should we say "assuming you only have access to x86 hardware"
Comment 4 Donnie Berkholz (RETIRED) gentoo-dev 2005-02-26 21:16:37 UTC
So I was just talking to Mike. Staying far away from making assumptions is the best way to go here, because we care about what _this_ dev will do, not what some hypothetical dev who may or may not be on the same architecture will do. _This_ dev will break or not break the tree, and the actions of the hypothetical one have no bearing on it, so we care about teaching this one.
Comment 5 SpanKY gentoo-dev 2005-09-15 19:18:02 UTC
ok ... so are we going to update the question to contain 'assuming you only have
access to x86 hardware' ?  or just leave it as it is ?
Comment 6 Christina Gianelloni (RETIRED) gentoo-dev 2007-08-01 19:09:10 UTC
This bug is two years old and people, per recruiters, are already specifying in their responses as to which arch they're using. We agree with Donnie's response about concern about what this dev would do.
Closing bug.