Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

KR2016 The Free Software Bastard Guide

1 252 vues

Publié le

All best practices to be an asshole in the Free Software community

Publié dans : Technologie
  • Soyez le premier à commenter

KR2016 The Free Software Bastard Guide

  1. 1. @CreativeConnard the Free Software Bastard Guide Disclaimer: explicit content, do not reproduce in real life
  2. 2. ~ 2 ~@CreativeConnard HOW TO be an asshole ~ User ~ ~ Developer ~ ~ Company ~
  3. 3. ~ 3 ~@CreativeConnard ~ User ~
  4. 4. ~ 4 ~@CreativeConnard Chapter #1 [ Mailing lists ]
  5. 5. ~ 5 ~@CreativeConnard Don’t use lists Send mail directly to project leaders※ Paste stack traces on IRC channels※ Use Twitter and Facebook to ask question or report problems※ ※ Open issues in bug tracker to ask questions
  6. 6. ~ 6 ~@CreativeConnard Use the lists Never register! Let administrators take time to moderate your message. Be rude if you don’t get any answer. ※ Use a Vacation Away message to inform all people that your are not available※ Do not answer to the list but directly to sender. You want to get help, not to give it.※
  7. 7. ~ 7 ~@CreativeConnard Invite the list to all professional networks
  8. 8. ~ 8 ~@CreativeConnard Write on lists ※ Use your mother thong. Anybody can use a translation tool to read you. Answer on top, don’t include original text, use HTML, include pictures in your signature, TRY TO UPPERCASE ALL WORDS, put !!! and ??? everywhere ※ ※ FEED THE TROLL
  9. 9. ~ 9 ~@CreativeConnard Chapter #2 [ Bugs ]
  10. 10. ~ 10 ~@CreativeConnard Find bugs ※ Use prehistoric version (>2 years old) ※ Use non official patch ※ Use weird operating systems ※ Let your children use the software
  11. 11. ~ 11 ~@CreativeConnard Report bugs ※ Don’t search if the bug was already reported, try to create duplicates ※ Description “Does not work” is often enough ※ Demand a quick solution for free. Use the word “ASAP”. Never test the patch because it’s too hard
  12. 12. ~ 12 ~@CreativeConnard ~ Developer ~
  13. 13. ~ 13 ~@CreativeConnard Chapter #3 [ Documentation ]
  14. 14. ~ 14 ~@CreativeConnard Acronyms ※ RTFM (Read The Fucking Manual) ※ WITFM (Where Is The Fucking Manual) ※ TODO (Too Old DOcument) ※ RTS (Read The Source)
  15. 15. ~ 15 ~@CreativeConnard Documentation everywhere ※ Create files in project (README, INSTALL) but never update them ※ Install an open wiki (without authentication) ※ Explain a lot of things on mailing list but never put them in a documentation
  16. 16. ~ 16 ~@CreativeConnard Chapter #4 [ Quality ]
  17. 17. ~ 17 ~@CreativeConnard TESTING IS DOUBTING
  18. 18. ~ 18 ~@CreativeConnard ~ Company ~
  19. 19. ~ 19 ~@CreativeConnard Using Free Software ※ License? Let this to Bob from accounting department ※ OMG they give it for free! Idiots ;) ※ Give something back? We will that next year ※ Community? Are we doing politics here?
  20. 20. ~ 20 ~@CreativeConnard Making Free Software ※ Fork instead of contributing (Fork as a Service) ※ Keep interesting features for “enterprise” edition, because only big companies use them ※ Create a new license and pay a team of lawyer for this, because no existing license fits your needs ※ Don’t let external people contribute, they will mess up all with their dirty hands
  21. 21. ~ 21 ~@CreativeConnard @CreativeConnard Links for bastards @DonJon_Legacy http://donjonlegacy.com/

×