Re: [python-uk] Announcing the Yorkshire Inquisition

2016-12-08 Thread Edward Hartley
> On 7 Dec 2016, at 13:36, Thomas Kluyver wrote: > >> On Wed, Dec 7, 2016, at 01:20 PM, Andy Robinson wrote: >> To enforce good conduct in a suitably Pythonic manner, I hereby >> propose the foundation of the Yorkshire Inquisition, headed by Steve. > > I don't think

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Mark Lawrence via python-uk
On 08/12/2016 14:00, Andy Robinson wrote: On 8 December 2016 at 09:29, James Broadhead wrote: Personally, I'd be in favour of #2 - it allows the community to promote positions internally, but avoids recruiter-mails which seem to trigger so much ire. It seems to me

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Daniele Procida
On Thu, Dec 8, 2016, Michael wrote: >IMO, Leave it as is, and ask people just for a bit of common politeness. >The list description says "there will be job ads". it's said that for years >(decades?) Anyone who doesn't like it doesn't actually have to join. (and >if they can't

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread David Wilson
On Thu, Dec 08, 2016 at 02:20:30PM +, S Walker wrote: > Frankly if we didn't have people complaining about the job postings > each time they were made I suspect that is a rule everyone could get behind. :) > they'd be responsible for a negligible amount of list traffic. Ignoring

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Michael
Andy, Speaking as one of the few who didn't say anything - because the ad wasn't relevant to me at the time - I personally see little reason to change the policy of allowing job ads on here. A handful of people complain once or twice a year, and the upshot is more posts and traffic as a result

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread S Walker
I've read comments on here supporting there being job postings as they are of use to the community (I think all of us like being able to afford to eat, right?), and I'd tend to agree with that. Maybe a better idea would be to put guidelines for job posting (e.g. not more than x frequency,

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Ian Makgill
+1 for that. Then if you don't want job ads you can filter out content with that url. On 8 December 2016 at 15:16, Pete Graham wrote: > How about every job posting to this mailing list has to contain an > accompanying link to the full job ad on

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Pete Graham
How about every job posting to this mailing list has to contain an accompanying link to the full job ad on http://pythonjobs.github.io/? If someone forgets we can politely remind them. Pete On 8 December 2016 at 14:06, Stestagg wrote: > I agree with John > > While

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread James Broadhead
On 7 December 2016 at 21:14, John Lee wrote: > Having been on this list since 2004 I *think* I'm right in saying that > there have never been sharp words on any subject EXCEPT recruiters. > > So though I've defended recruiters here before, and posted job ads myself, > I think we

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Marcelo Elias Del Valle
It gives the impression to me that being offensive pays off. But I am new here, I don't have a strong opinion. On 8 Dec 2016 09:53, "Gilberto Gonçalves" wrote: > So though I've defended recruiters here before, and posted job ads myself, >> I think we should consider the

Re: [python-uk] 2 Principle Engineer roles in London up to £95k

2016-12-08 Thread Gilberto Gonçalves
> > So though I've defended recruiters here before, and posted job ads myself, > I think we should consider the possibility that all that's needed is to not > allow job ads (or not allow recruiters if you like -- but I think > simplicity is a virtue here). Then rogue job ads can be responded to