#DevDiscuss Archive

Tuesday December 19, 2017
9:00 PM EST
  • gatlingxyz Dec 19 @ 9:05 PM EST
    I need to get into some open-source stuff. Can't wait for tonight's #DevDiscuss!
  • ThePracticalDev Dec 19 @ 9:09 PM EST
    Time for the #DevDiscuss Twitter chat. Tonight's topic is: ⭐️⭐️⭐️ Open Source Etiquette ⭐️⭐️⭐️ All about the written and unwritten rules of open coding
  • ThePracticalDev Dec 19 @ 9:10 PM EST
    The chat will last about an hour and we use the #DevDiscuss tag. Rules: - Stay on topic - ALWAYS ALWAYS use hashtag #DevDiscuss - Be NICE/POSITIVE ❤️ - Quoting tweets for clarity is encouraged (ALWAYS use the #DevDiscuss, even on replies where appropriate 😄)
  • ajw1970 Dec 19 @ 9:10 PM EST
    I haven't started contributing yet. I'm interested in helping out a community that has helped me out so much though. #DevDiscuss
    • kylegalbraith Dec 19 @ 8:40 PM EST
      Open source etiquette is the leader for tonight's #devdiscuss chat. Where do you try and start when contributing to #opensource projects? For me I try and add test or docs first...
  • ThePracticalDev Dec 19 @ 9:12 PM EST
    What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • singhpratyush_ Dec 19 @ 9:12 PM EST
    #DevDiscuss Make sure you run tests before creating a pull request.
    In reply to @ThePracticalDev
  • mablae Dec 19 @ 9:13 PM EST
    Ask questions, discuss idea before doing actual work and submit PR #devdiscuss
  • mrskellyvaughn Dec 19 @ 9:13 PM EST
    New to contributing to open source projects? Your first step is reading the contributor guidelines and code documentation. Everyone wins when guidelines are followed. #devdiscuss
  • aunyks Dec 19 @ 9:13 PM EST
    Project owners please make it as easy as possible for new contributors to join your project. Be informative when answering issue questions, add roadmaps and checklists to READMEs, and add `new contributor friendly` badges to issues and PRs It helps build community #DevDiscuss
  • shannon_crabill Dec 19 @ 9:14 PM EST
    I think being nice (not a jerk) goes along way. Don't assume that someone coming to your project knows everything that you do. #DevDiscuss
    In reply to @ThePracticalDev
  • daveeeeeeed Dec 19 @ 9:15 PM EST
    Be nice to beginners #DevDiscuss
    In reply to @ThePracticalDev
  • mrskellyvaughn Dec 19 @ 9:16 PM EST
    Agreed - that goes both ways. If you think you have a great idea for a project but it's not the direction the maintainer wants to go, don't take it personally. #devdiscuss
    In reply to @shannon_crabill, @ThePracticalDev
  • ajw1970 Dec 19 @ 9:16 PM EST
    Yeah, I prefer people start by gaining an understanding before telling me how my code works. I'm sure I'm not alone in this. #DevDiscuss
    In reply to @mablae
  • Nick_Craver Dec 19 @ 9:18 PM EST
    Everyone: assume best intentions. Newbies: acid, probably. Experienced: realize almost everyone new has less context. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • gdavis92 Dec 19 @ 9:18 PM EST
    Before filing an issue, hit up that searchbar to see if your issue has already been opened and/or completed. Also, looking through past PRs helps contributors get an idea of the merge process. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • IgnoreIntuition Dec 19 @ 9:19 PM EST
    Don’t be intimidated. Fear is the enemy of innovation. #DevDiscuss
    In reply to @ThePracticalDev
  • sikachu Dec 19 @ 9:20 PM EST
    If you are looking for a place to start contributing, a not-so-obvious place to start is the documentation, especially if you're a beginner! It's hard for core teams or normal contributors to figure our what's currently missing for beginner. #DevDiscuss https://t.co/4dkLClGTve
    • ThePracticalDev Dec 19 @ 9:09 PM EST
      Time for the #DevDiscuss Twitter chat. Tonight's topic is: ⭐️⭐️⭐️ Open Source Etiquette ⭐️⭐️⭐️ All about the written and unwritten rules of open coding
  • ajw1970 Dec 19 @ 9:20 PM EST
    I'd say it's good to remember that the project owners aren't looking for more work. Offering a solution instead of just making problems known must go a long way. #devdiscuss
  • ThatJoeMoore Dec 19 @ 9:20 PM EST
    If you're an OSS maintainer, please don't request that someone add tests for the bug they've fixed when you haven't already at least got a simple "hello-world" level test set up. Especially don't critique their test style when you haven't established one yet. #DevDiscuss
  • ThatJoeMoore Dec 19 @ 9:21 PM EST
    If you're an OSS maintainer, please don't request that someone add tests for the bug they've fixed when you haven't already at least got a simple "hello-world" level test set up. Especially don't critique their test style when you haven't established one yet. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • vcsjones Dec 19 @ 9:21 PM EST
    Existing OSS culture should not always be used to model your own experiences with OSS. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • ajw1970 Dec 19 @ 9:23 PM EST
    Sounds like you're speaking from a bad experience. #DevDiscuss
    In reply to @ThatJoeMoore
  • shannon_crabill Dec 19 @ 9:23 PM EST
    I agree with this 100%. A lot of projects out there lacks documentation. It's off putting as a newbie / someone who wants to contribute if there is no documentation #DevDiscuss
    In reply to @sikachu
  • sikachu Dec 19 @ 9:25 PM EST
    Also, for your code patch or PR, follow the style guide or the style of the code around it. Keep it clean and makes it easy to understand. That will cut down review loops and helps out the reviewers! 🙏 #DevDiscuss https://t.co/4dkLClGTve
    • ThePracticalDev Dec 19 @ 9:09 PM EST
      Time for the #DevDiscuss Twitter chat. Tonight's topic is: ⭐️⭐️⭐️ Open Source Etiquette ⭐️⭐️⭐️ All about the written and unwritten rules of open coding
  • ajw1970 Dec 19 @ 9:26 PM EST
    Are newbies the best ones to be adding missing documentation? #DevDiscuss
    In reply to @shannon_crabill, @sikachu
  • hiPHPie Dec 19 @ 9:26 PM EST
    Try to separate the message from the tone. The first contact is often made out of an undelightful experience, and the tone might be inappropriate. Nevertheless, the message might be valuable. Be grateful for that message. Ignore the tone. #DevDiscuss
    In reply to @ThePracticalDev
  • _ropthe_ Dec 19 @ 9:27 PM EST
    @ThePracticalDev What is the proper etiquette when the original maintainer is no longer responsive? #devdiscuss
  • Nick_Craver Dec 19 @ 9:27 PM EST
    Oh and *most* people forget this sooner or later: maintainers are usually giving their time for free. Be considerate. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • gatlingxyz Dec 19 @ 9:28 PM EST
    Can we get a list of some open-source projects? I'm always down for learning some new things and getting out of my comfort zone. #DevDiscuss
  • ThatJoeMoore Dec 19 @ 9:28 PM EST
    Yup. There's a reason I haven't contributed to that project again. I still respect the lead developer - he's insanely smart - but I really don't feel the desire to contribute to his (or his employer's) projects anymore. #DevDiscuss
    In reply to @ajw1970
  • ajw1970 Dec 19 @ 9:28 PM EST
    Good advice... hard to do but goes well when practiced. #DevDiscuss
    In reply to @hiPHPie, @ThePracticalDev
  • shannon_crabill Dec 19 @ 9:28 PM EST
    Maybe not in all cases. I also meant from a mainteners standpoint. Having existing documentation (if it can be improved upon, that's another thing) may help a project to more accessible to newbie who want to contribute #DevDiscuss
    In reply to @ajw1970, @sikachu
  • _ropthe_ Dec 19 @ 9:28 PM EST
    Newbies are definitely the best ones to find gaps in the documentation. When something doesn't make sense, figuring it out and documenting it would help everyone that comes after #DevDiscuss
    In reply to @ajw1970, @shannon_crabill, @sikachu
  • ajw1970 Dec 19 @ 9:29 PM EST
    Just move forward with your own fork? #DevDiscuss
    In reply to @_ropthe_, @ThePracticalDev
  • bendhalpern Dec 19 @ 9:29 PM EST
    Here are some good resources for newbs who are not sure where to start with open source https://t.co/nOTu7ab7Ds #DevDiscuss
  • shannon_crabill Dec 19 @ 9:30 PM EST
    I was going to add something to this point too. I'd also consider catching spelling errors / typos a good way for newbies to contribute #DevDiscuss
    In reply to @_ropthe_, @ajw1970, @sikachu
  • ike__jr Dec 19 @ 9:31 PM EST
    every oss repo I've ever looked at has been overwhelming to me, but I decided to follow GitHub's opensourcefriday movement and never really got the time because of school stuff #devdiscuss
  • ajw1970 Dec 19 @ 9:32 PM EST
    Understandable. #DevDiscuss
    In reply to @ThatJoeMoore
  • _ropthe_ Dec 19 @ 9:32 PM EST
    Definitely! No PR is too small. and getting your chops wet on small things like typos is great practice of PR workflow. My first PRs were all *very* small documentation typos. #DevDiscuss
    In reply to @shannon_crabill, @ajw1970, @sikachu
  • cely717 Dec 19 @ 9:33 PM EST
    All: don't bump the version number in your PR. That's the quickest way to generate a conflict. You don't know the maintainer's plans. I've seen this happen way too often. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • ajw1970 Dec 19 @ 9:33 PM EST
    Yeah, I've done that. Or perhaps examples to expand on existing documentation after getting something to work. Go ahead and fill the holes you fall into so that others don't fall into them too. #DevDiscuss
    In reply to @shannon_crabill, @_ropthe_, @sikachu
  • ike__jr Dec 19 @ 9:34 PM EST
    anyways anybody got a oss repo concerning kotlin? I'll really love to help. started learning kotlin not long ago, looking for cool things to do with it #DevDiscuss
  • mikesusz Dec 19 @ 9:35 PM EST
    when people file issues (much like filing bugs) they assume a level of familiarity and don’t take the time to rigorously explain the problem. assume someone will take on your query who has never seen the project before. be thorough. #devdiscuss
    In reply to @ThePracticalDev
  • ThatJoeMoore Dec 19 @ 9:36 PM EST
    As a contributor, be flexible and open to making changes to your submission. Odds are, you won't be maintaining the code you just wrote, and a good maintainer will guide you to producing better code. #DevDiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • gatlingxyz Dec 19 @ 9:36 PM EST
    This seems like EXACTLY what I've been looking for. Thanks! #DevDiscuss
  • _ropthe_ Dec 19 @ 9:36 PM EST
    It took me a while to realize that maintainers are fallible too. #devdiscuss
    In reply to @IgnoreIntuition, @ThePracticalDev
  • ajw1970 Dec 19 @ 9:37 PM EST
    Great advice. #DevDiscuss
    In reply to @mikesusz, @ThePracticalDev
  • ThePracticalDev Dec 19 @ 9:39 PM EST
    What's the best part about taking part in open source? #devdiscuss
  • _ropthe_ Dec 19 @ 9:41 PM EST
    Definitely, no documentation is a death sentence for a project. How will anyone know where to start, even experts? #devdiscuss
    In reply to @shannon_crabill, @ajw1970, @sikachu
  • bendhalpern Dec 19 @ 9:41 PM EST
    - Learn a lot - Give back - Make friends/professional contacts - Improve your tools - It's a lot of fun! I haven't done a lot of open source myself, but enough to think these things are all true #DevDiscuss
  • IgnoreIntuition Dec 19 @ 9:41 PM EST
    It seems unattainable until you meet them, talk to them, work with them. Then you realize that they’re just regular folk. #DevDiscuss
    In reply to @_ropthe_, @ThePracticalDev
  • IgnoreIntuition Dec 19 @ 9:42 PM EST
    Yup. Goes both ways. #DevDiscuss
    In reply to @RobertShippey, @ThePracticalDev
  • _ropthe_ Dec 19 @ 9:42 PM EST
    Or follow them on twitter 🤣#devdiscuss
    In reply to @IgnoreIntuition, @ThePracticalDev
  • ThatJoeMoore Dec 19 @ 9:42 PM EST
    Working with a skilled project owner to improve a contribution is a great way to learn from somebody who's smarter than you are. #DevDiscuss
  • shannon_crabill Dec 19 @ 9:42 PM EST
    When your pull request gets merged #DevDiscuss
    In reply to @ThePracticalDev
  • ThatJoeMoore Dec 19 @ 9:44 PM EST
    There's no better way to make sure that a bug you've encountered in a project you love gets fixed than to help fix it yourself. #DevDiscuss
  • gdavis92 Dec 19 @ 9:44 PM EST
    Or meet them after a conference talk #DevDiscuss
    In reply to @_ropthe_, @IgnoreIntuition, @ThePracticalDev
  • IgnoreIntuition Dec 19 @ 9:44 PM EST
    Knowing that you contributed to something bigger than yourself #DevDiscuss
    In reply to @ThePracticalDev
  • Programazing Dec 19 @ 9:45 PM EST
    Check out my website/blog at https://t.co/4DAQVTUa1s #DevDiscuss
  • ajw1970 Dec 19 @ 9:45 PM EST
    The https://t.co/cPnFk73DRH Core team fixed a bug I found today and let me know it would be in the next release. I was feeling like that and I hadn't even contributed to the fix! I can't wait to get a PR merged on something I contribute. #DevDiscuss.
    In reply to @shannon_crabill, @ThePracticalDev
  • ThatJoeMoore Dec 19 @ 9:47 PM EST
    One big thing I've seen is that it has helped me learn to look beyond my specific problem and see the more general one, then solve that. That skill has especially helped while leading large, company-spanning projects. #DevDiscuss
  • ajw1970 Dec 19 @ 9:49 PM EST
    I would think being helpful to those who openly offer help to me would be the best part. I lack enough experience to even be a newbie at this point though. #DevDiscuss
  • ThatJoeMoore Dec 19 @ 9:50 PM EST
    That warm happy feeling you get when your contribution fixes a long-forgotten bug in a major project that only you and one other person have encountered. #DevDiscuss
  • Nick_Craver Dec 19 @ 9:51 PM EST
    Learning and improving yourself, from all angles. #DevDiscuss
  • M_F9i Dec 19 @ 9:52 PM EST
    -Boost your CV. -More experience. -Good start to become senior. -Making communication skills better. #DevDiscuss https://t.co/DpRVcrb1AK
  • ajw1970 Dec 19 @ 9:53 PM EST
    Gaining a particular set of skills... I WILL find bugs... I will KILL bugs. #DevDiscuss
  • ThePracticalDev Dec 19 @ 9:54 PM EST
    In the last few minutes of #DevDiscuss, anybody have any news to share, like a project or a personal win, or any other announcement?
  • ajw1970 Dec 19 @ 9:54 PM EST
    As a solo programmer for decades, that last part is a big draw for me. I want to have more interraction with other developers and contributing to open source seems like a great way to do that. #DevDiscuss
    In reply to @M_F9i
  • danstarkdevops Dec 19 @ 9:55 PM EST
    Taking an idea from conception to “production” (something others can pick up and use) is an important skill as a developer. In particular, battling your internal scope creep and providing empathic documentation are key. #DevDiscuss
    In reply to @ThePracticalDev
  • daveaglick Dec 19 @ 9:56 PM EST
    The biggest thing that I think trips people up, even the most well meaning, is occasionally forgetting that there are actual people behind that project, PR, or issue #devdiscuss
    • ThePracticalDev Dec 19 @ 9:12 PM EST
      What should people know about being a good citizen of open source? What makes newbies trip up? What do experienced OSS contributors often mess up on in terms of etiquette? #devdiscuss
  • ajw1970 Dec 19 @ 9:57 PM EST
    I've been getting familiar with @github using private repositories so that when I do find opportunities to contribute I won't be new to EVERYTHING. #DevDiscuss
    In reply to @ThePracticalDev, @github
  • gdavis92 Dec 19 @ 9:57 PM EST
    Speaking of #opensource, just released this fun utility function to help transform synchronous functions to asynchronous functions. #DevDiscuss https://t.co/Yyvf6XgK8l
    • ThePracticalDev Dec 19 @ 9:54 PM EST
      In the last few minutes of #DevDiscuss, anybody have any news to share, like a project or a personal win, or any other announcement?
  • ma_khan Dec 19 @ 9:57 PM EST
    You never gain experience of all aspects of a large framework at work. OSS is a great tool to learn from the mistakes, wins and lessons of others. #DevDiscuss
    In reply to @ThePracticalDev
  • dvdmuckle Dec 19 @ 9:57 PM EST
    When the maintainer says in an issue "I wish I knew how to do that..." and you're all like... #DevDiscuss
    In reply to @ThePracticalDev
  • downloadSteven Dec 19 @ 9:58 PM EST
    I'm glad I've had the opportunity to work in open source as an undergrad in @vj_chidambaram's course. Open source demands a level of software maturity. If you don't have it, you learn a long the way. #devdiscuss
  • yechielk Dec 19 @ 9:59 PM EST
    Just got a job offer for my first dev job last week! I start in January! #devdiscuss
    In reply to @ThePracticalDev
  • shannon_crabill Dec 19 @ 9:59 PM EST
    I'll be speaking at #Codeland in 2018 and I'll be talking about open source 😜 #DevDiscuss https://t.co/jadCVMp7bz
    In reply to @ThePracticalDev
  • _ropthe_ Dec 19 @ 9:59 PM EST
    I publicly announced a blog post for the first time and received surprisingly positive feedback! So that was exciting #devdiscuss
    In reply to @ThePracticalDev