I’m a co-founder of OpenSign, an open-source alternative to DocuSign. Recently, something concerning happened in our project that I believe the community should know about.
Someone has forked OpenSign and is attempting to strip all paid plan restrictions, replacing our project logos with their own. They even submitted a PR for these changes. While this technically complies with the AGPLv3 license that OpenSign is built on, it raises ethical questions about how open-source projects should operate.
OpenSign was designed to provide accessible, open-source e-signature tools while sustaining development through optional paid plans. This move doesn’t just undercut those plans—it undermines the sustainability of the project itself.
We’re committed to the open-source ethos, but forks like this create a dangerous precedent, especially when they explicitly try to hijack the original project's identity and monetization strategy.
I’d love to hear your thoughts—should open-source projects have more safeguards? Is this just "fair game" in the open-source world? How do we as a community draw ethical boundaries while respecting open-source licenses?
Here’s a quick rundown of the new features we’ve added:
1. Template-Based Document Creation: Streamline your workflow with the ability to create and share documents using pre-saved templates.
2. Enhanced Signature Customization: Now includes options to input signatures in various text formats and fonts, adding a personalized touch to your documents.
3. Improved Placeholder Management UI: A more intuitive and user-friendly interface for managing signature placeholders, including enhanced resizing capabilities.
4. Efficient Document Organization Tools: New functionalities to delete and move documents within the OpenSign™ drive for better file management.
5. Seamless Email Integration: Easily send signed documents via email directly from the platform, enhancing the document signing and sharing process.
6. Cross-Device Placeholder Compatibility: Ensures consistent placeholder experiences across both mobile and desktop platforms.
7. Customizable User Support Options: Includes a ‘don’t show again’ option for help guides and direct links for easy communication with the OpenSign team.
8. Key Bug Fixes and Performance Enhancements: Addressing various user-reported issues for a smoother, more reliable OpenSign™ experience.
These updates aim to make OpenSign™ a stronger contender in the open source digital signing space, rivalling traditional solutions like DocuSign with a community-driven, user-centric approach.
Not sure what you are trying to say. The product had been in development for a long time - around 6-7 months. How do you think the news of DocuSign exploring a sale will impact us?
Sorry, meant the post being on HN, not the project itself. The sale might be relevant to customers of DocuSign who are potentially considering migrating before the usual enshittification that happens after a sale.
Absolutely. The potential sale of DocuSign could indeed be a pivotal moment for its current customers & OpenSign™. This uncertainty might be a perfect opportunity for users to explore alternatives like OpenSign™.
OpenSign™ offers a robust and user-friendly solution that aligns with the needs of those looking for stability and consistency in their document management and e-signature processes. As an open-source platform, OpenSign™ is not only free but also constantly evolving with contributions from a community focused on reliability and innovation.
For those considering a switch, now might be an ideal time to test OpenSign™ and experience the benefits of an open-source, community-driven alternative. Plus, being part of our user community means having a say in the future developments of the tool. It's a win-win for users seeking control and quality in their e-signature solutions.
Dear hacker news community,
We would love to get your feedback on what is that one thing that you would like to change/improve in your current document signing solution?
We have recently released v1.0.6-beta version of OpenSign, the leading open source document signing solution, marking a significant step forward in the development journey. This release encapsulates numerous bug fixes and feature enhancements, highlighting our team's commitment to providing a robust and user-friendly product. In this blog post, we delve into the key changes and improvements introduced in this version.
Key Improvements and Fixes
1. Multiple Annotations in Single File: A fix has been made to address issues with handling multiple annotations in a single file, enhancing the software's efficiency in managing complex documents.
2. Document Signature and Certificate Issue Fixes: Significant fixes were made to the 'need-your-sign' report, document signature, and certificate issues, further solidifying the software's reliability in handling legal documents.
3. Mobile view Enhancements:
Adjustments were made to the location of requested signature placeholders in the mobile "Request Signatures" flow, improving user experience on mobile devices.
4. SMTP Email Integration:
The introduction of SMTP for sending emails marks a notable feature enhancement, expanding the software's capabilities in terms of communication and notifications.
5. Sanitized Output Filenames:
A critical fix has been implemented to sanitize output filenames, ensuring better security and data integrity.
6. Enhanced Modal Titles and Verification Mail Alerts:
The modal title for login now includes additional information, and the verification mail alert message has been updated for clarity.
7. UI and Security Refinements:
Various minor UI changes and security improvements were implemented, reflecting an ongoing effort to refine the user experience and bolster security measures.
OpenSign v1.0.6-beta is more than just an incremental update, it's a testament to the continuous evolution of a software dedicated to simplifying digital signatures. Each fix and feature enhancement is a step towards a more efficient, secure, robust and user-friendly digital signature process. For developers, entrepreneurs and businesses relying on digital signatures, this update offers an array of improvements that streamline operations and enhance security protocols.
As OpenSign continues to evolve, it remains a significant tool for professionals seeking a reliable and efficient open source digital signature solution. This release not only addresses immediate issues but also lays the groundwork for more innovative features and improvements in future releases.
You are right. But there are many Individuals/companies who cannot benefit from DocuSign's trust because of the price tag. We want to provide them the free/ open source option and during the process build a brand that is equally trusted if not more than DocuSign.
True. Even if one party from the signers dont trust e-sign, it wont work. But the number of people thinking an E-signature is good is only increasing day by day.
I’m a co-founder of OpenSign, an open-source alternative to DocuSign. Recently, something concerning happened in our project that I believe the community should know about.
Someone has forked OpenSign and is attempting to strip all paid plan restrictions, replacing our project logos with their own. They even submitted a PR for these changes. While this technically complies with the AGPLv3 license that OpenSign is built on, it raises ethical questions about how open-source projects should operate.
OpenSign was designed to provide accessible, open-source e-signature tools while sustaining development through optional paid plans. This move doesn’t just undercut those plans—it undermines the sustainability of the project itself.
We’re committed to the open-source ethos, but forks like this create a dangerous precedent, especially when they explicitly try to hijack the original project's identity and monetization strategy.
I’d love to hear your thoughts—should open-source projects have more safeguards? Is this just "fair game" in the open-source world? How do we as a community draw ethical boundaries while respecting open-source licenses?
Let’s discuss!