Announcement

Collapse
No announcement yet.

Intel Survey Finds Maintainer Burnout & Documentation Top Open-Source Challenges

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • plonoma
    replied
    Originally posted by coder View Post
    Not to take sides, but I guess the equivalent would be if you file a bug and include pseudocode for a suggested solution.

    More often than not, I'd guess the response you'd get (if any) would be like: "sounds good. Please submit a PR and we'll review."
    I second this!

    Leave a comment:


  • coder
    replied
    Originally posted by uid313 View Post
    Most of the projects are on GitHub today and email isn't really used today (well outside of the Linux kernel community).
    Not to take sides, but I guess the equivalent would be if you file a bug and include pseudocode for a suggested solution.

    More often than not, I'd guess the response you'd get (if any) would be like: "sounds good. Please submit a PR and we'll review."

    Leave a comment:


  • uid313
    replied
    Originally posted by plonoma View Post

    What if you email your contribution in the form of a message describing the problem and fix (including where in the source files to modify things) without including code, only pseudocode clearly marked as pseudocode. Would that be a practical approach for that type of contributions?
    Most of the projects are on GitHub today and email isn't really used today (well outside of the Linux kernel community).

    Leave a comment:


  • plonoma
    replied
    Maintenance burdens or when almost: Everybody wants to start a cool new hip project but nobody wants to maintain existing projects.
    All those software projects. Who's going to maintain them? The chickens come home to roost.

    Leave a comment:


  • plonoma
    replied
    Originally posted by uid313 View Post

    I didn't want to be a core maintainer who stays around and maintains it forever. I just wanted to do a one time contribution, a bug fix or a feature and then leave.
    What if you email your contribution in the form of a message describing the problem and fix (including where in the source files to modify things) without including code, only pseudocode clearly marked as pseudocode. Would that be a practical approach for that type of contributions?

    Leave a comment:


  • bug77
    replied
    Originally posted by guglovich View Post
    Strange that there's no QA and UI/UX.
    QA is mentioned towards the middle of the second table in the article.

    Leave a comment:


  • guglovich
    replied
    Strange that there's no QA and UI/UX.

    Leave a comment:


  • uid313
    replied
    Originally posted by bug77 View Post

    Almost as fun as having to sign up with 100 web sites just to be able to report issues. I see where you're coming from. And yes, sharing personal info is not for everyone. Especially in this day and age.
    Oh, yeah that is another one. I prefer to report issues on GitHub where I already have an account. Sometimes I am expected to sign up for an account on some private Gerrit instance just report an issue, I don't like that.

    Leave a comment:


  • bug77
    replied
    Originally posted by uid313 View Post
    Yeah, I see how CLA can be useful, but it also a burden to have to sign it, and its not funny have to surrender personal information. There are some obstacles that make someone not want to contribute to open source. That make it not fun, that make it a chore, that make it dreadful.
    Almost as fun as having to sign up with 100 web sites just to be able to report issues. I see where you're coming from. And yes, sharing personal info is not for everyone. Especially in this day and age.

    Leave a comment:


  • uid313
    replied
    Originally posted by bug77 View Post

    Yes, you want to contribute and then leave. But without a CLA in place, you can't just "leave". You retain ownership of that code and maintainers must get a hold of you if they want to relicense or something. You see how not signing a CLA puts other people involved in the project in a tight spot?
    If you truly wanted to be helpful, you'd have no problem signing over ownership of your code.

    Just to be clear, I'm not saying that everyone should give their code away all the time. Just that in some (many?) cases, a CLA makes sense. Especially if you consider some contributors will eventually fall of the edge of the world.
    Yeah, I see how CLA can be useful, but it also a burden to have to sign it, and its not funny have to surrender personal information. There are some obstacles that make someone not want to contribute to open source. That make it not fun, that make it a chore, that make it dreadful.

    Leave a comment:

Working...
X