Google Summer of Code (GSoC) is a global program run by Google where students and open source beginners get paid to contribute to open source organizations over a summer. You apply to a specific organization with a project proposal, a mentor reviews it, Google funds the selected contributors, and you spend the coding period working on real software used by real people. It's not an internship at Google — the org... - Source: dev.to / 4 months ago

Many companies that depend on OSS contribute financially so that the projects remain robust. Examples like Google and Microsoft have shown that corporate sponsorship is not only beneficial for maintainers but also for companies that rely on reliable software. The corporate sponsorship model moves away from traditional ad-based revenue generation, fostering a direct relationship between the sponsor and the... - Source: dev.to / over 1 year ago

Similarly, open source projects, which are the backbone of digital infrastructure, have long struggled to achieve sustainable funding. Crowdfunding platforms such as Kickstarter, Opencollective, and corporate sponsorships from technology giants like Google’s open source initiatives and Microsoft’s commitment to open source are now offering viable alternatives. Innovators have begun to integrate Non-Fungible Tokens... - Source: dev.to / over 1 year ago

Governments, academic institutions, and major tech companies like Microsoft and Google have recognized the importance of financial support. Funding models have evolved to include corporate sponsorships, grants (e.g., Mozilla's Open Source Support Program), and community-driven donations through platforms like GitHub Sponsors and Open Collective. - Source: dev.to / over 1 year ago

Sponsorship Programs: Platforms such as GitHub Sponsors and offerings from tech giants like Google Open Source and Microsoft Open Source provide recurring support while maintaining community values. - Source: dev.to / over 1 year ago

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