Tools like Userdoc (https://userdoc.fyi) help in a few ways, you can easily create requirements (stories, personas, journeys, test cases), but also reverse engineer existing source code into detailed docs, then ask natural language questions etc. AI helps us plan our product in Userdoc, and our devs connect via MCP to bring those requirements directly in to Cursor (full disclaimer, I work at Userdoc - but we eat... - Source: Hacker News / about 1 year ago

Userdoc has versioning of stories and acceptance criteria, aimed to at helping this exact issue https://userdoc.fyi (transparency: I’m the founder). - Source: Hacker News / over 1 year ago

I'm interested to hear how other people are using tools to help them, we've been playing with userdoc.fyi and having good success, but there are just so many AI related tools I feel like I can't keep up! Source: about 3 years ago

Great read, I spent years thinking requirements should live somewhere like Jira, and I feel for many teams this is the case. But as the author mentions, Jira contains tasks related to bugs, text changes, colour changes etc.. These are not product requirements per se. Like the author, I came to the conclusion requirements are best kept in a requirements management system, that integrates with your project... - Source: Hacker News / over 3 years ago

I built Userdoc (https://userdoc.fyi) a requirements management system for software projects. After running a development consultancy for 8 years, I wanted a dedicated system for gathering and confirming requirements, and only syncing them with project management tools like Jira when they are ready (but keeping them in Userdoc as the living documentation and source of truth. Things are going well, we have some... - Source: Hacker News / over 3 years ago

This... exists? Did they even search for it? https://github.com/open-source/sponsors. - Source: Hacker News / 8 months ago

Community-Driven Upgrades: Increased integration of real-time community feedback via platforms such as GitHub Sponsors and social media channels (e.g., Twitter (@fsf)) could drive iterative improvements in the license. - Source: dev.to / over 1 year ago

Chad has been leading the Open Source Pledge, a simple framework to get companies to fund the projects they rely on. The idea is straightforward: for every developer your company employs, allocate $2,000 per year to open source. Distribute those funds however you want—GitHub Sponsors, Open Collective, Thanks.dev, direct payments, etc. The only other ask is to publish a blog post showing what you did. - Source: dev.to / over 1 year ago

Abstract: This post dives into the evolution and global expansion of GitHub Sponsors and its impact on funding open-source projects. We examine its inception, supported countries, technical challenges, and how blockchain innovations and alternative funding models are shaping the future of open source development. From core benefits and practical use cases to potential hurdles and forward-looking trends, this... - Source: dev.to / over 1 year ago

This post explores the critical issue of sustainable funding for open source projects. We dive into historical challenges, innovative funding strategies, and future trends that aim to support the collaborative spirit of open source development. Using examples from corporate sponsorships, non-profit foundations, crowdfunding methods, subscription models, government grants, and commercialization, the article... - Source: dev.to / over 1 year ago