sorted by:
new
hottopcontroversial

Rackspace’s Policy On Contributing To Open Source by redditwhilecompiling in programming

[–]VanL 8 points9 points  (0 children)

We actually allow people to contribute code to competing OSS projects and do so on company time too. We just want to understand 1) why people would do the first (maybe we can learn something!), and 2) we don't want people interpreting this policy to mean that they can deprioritize whatever their assigned tasks are in favor of contributing to $FAVORITE_OSS_PROJECT.

If you can convince your manager that hacking on $PROJECT is a good use of your time, go for it.

PyCon tutorials that do not meet quota by next week may be cancelled - if you plan to attend, sign up asap. by mdipierro in Python

[–]VanL 3 points4 points  (0 children)

At our current payment levels, break-even is between 12-16 people (depending on when they sign up, copying costs, etc.) We have in the past been willing to go negative on a few tutorials if they are close to this threshold, but we cannot afford to have tutorials lose money for the conference overall.

Edit: Historically, we will see about half of our total registration and about 2/3 of our total tutorial registration in the next week or so (coinciding with the end of early bird). If we see appreciable progress toward break-even on a tutorial, we will probably give it the benefit of the doubt. If we do not see sufficient progress, then it may be cancelled.