https://linen.dev logo
Join Slack
Powered by
Hi Team, I would like to report an issue regarding...
# infisical-contributing
a
Hi Team, I would like to report an issue regarding contribution ethics. There is a contributor, @jaydeep-pipaliya, who repeatedly submits PRs for issues that have already been raised by someone else. This has happened to me three times now. In the latest case, I created the issue and was waiting for the maintainers to respond before proceeding. Instead of checking whether the issue was already being discussed or asking if someone was already working on it, @jaydeep-pipaliya directly opened a PR for the same issue. Even if issues are not formally assigned, I believe it is good open-source etiquette to respect the person who identified and reported the issue. At the very least, contributors should check for existing discussions or ask before starting work on an issue that has just been reported by someone else. I have noticed @*jaydeep-pipaliya doing* the same behavior in several other issues as well, where PRs are opened without considering whether the original reporter is already working on a fix. I kindly request the maintainers to review this situation and, if appropriate, clarify the project's expectations around contribution etiquette so that everyone has a fair opportunity to contribute. Thankyou Looking forward to have aa positive response !! cc @Akhil Mohan @Jake (Infisical) @Carlos Monastyrski @Vlad (Infisical) Please team a very humble request to have a look on this
Finding and reporting a genuine issue often takes hours of investigation and effort. When someone else immediately opens a PR for that issue without communicating with the person who reported it, it discourages contributors and undermines the collaborative spirit of open source. Even if there is no formal ownership of an issue, respecting the effort of the person who identified and reported it is important. Taking their work without any discussion can negatively impact their confidence and motivation to continue contributing or reporting issues in the future. This isn't just about a single PR , It's about fostering a community where contributors respect each other's time, effort, and good-faith contributions.
🙌 1
Looking forward to hear from the team Thankyou
j
Hey Abdul! Thanks for flagging this. Taking a look now!
✅ 1
Hey @abdulmoiz3140, thanks for the thorough writeup and for caring about the community here. On this issue Jaydeep already closed that duplicate PR and apologized, so that specific one is resolved. On the bigger point, you're right that contributors should check for existing work before starting on an issue. Our contributing guide infisical.com/docs/contributing/getting-started/overview already asks people to comment on an issue and wait for a maintainer before picking it up, and we're going to make that more visible and add a note about checking for open PRs too. That should help everyone avoid stepping on each other going forward. Appreciate you raising this.
a
Thankyou so much @Jake (Infisical) means alot
Also, If possible, could you also take a look at my open PRs when you get a chance? It's been a little over a week now, and I currently have around six PRs waiting for review. I believe they contain genuine fixes and improvements, including one for the Ruby SDK. I completely understand that the team is busy building and improving the core security platform. I truly appreciate all the work you're doing. I just wanted to mention that I'd be happy to help in any way I can. If you ever need someone to contribute more actively to the open source project or help engage with the community, I'd love to be involved. Thanks again, and I look forward to hearing from you whenever you have the time.
Hi @Jake (Infisical) , I hope you're doing great . Just i case it got burried Can you please look into these : github.com/Infisical/infisical/pulls/… ?
Open in Slack
PreviousNext
Powered by