Will this project fester and die? Or can the community run with it?
I've used this project several times over the past five years and find in very useful for putting together reminder sheets of my custom keyboard layouts. I've also previously contributed to the project (the included Kinesis Advantage layout came from me). I am disappointed to find that this project is still festering in a never-never land. I would like to propose that if the _way the project is managed_ changes it could easily thrive instead of languishing. Open source projects thrive when there is interest and expertise (which this project seems to have generated) and somebody responds to and coordinates the community's efforts (which this project has not done). The original author has barely participated once or twice on the issue tracker in the last couple years, PR requests have gone unmerged with no feedback as to why, and incoming issues are not getting triaged. Furthermore I would like to propose the following to fix this situation: - [ ] **1.** Deal with #212. Pick an actual OSS license and apply it to the current code. The status quo license limbo is crazy and killing the project. Open source projects do not thrive while under proprietary licenses and if you wait until feature completion/maturity to open it up ① a single distracted author will never be able to bring in to maturity and ② there will be little wider interest in helping get it there because the effort invested seems to be poured into a black hole. - [ ] **2.** Appoint at least one maybe two other
Posted by alerque on Jan 18, 2018, 10:07 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Will this project fester and die? Or can the community run with it?
I've used this project several times over the past five years and find in very useful for putting together reminder sheets of my custom keyboard layouts. I've also previously contributed to the project (the included Kinesis Advantage layout came from me). I am disappointed to find that this project is still festering in a never-never land. I would like to propose that if the _way the project is managed_ changes it could easily thrive instead of languishing. Open source projects thrive when there is interest and expertise (which this project seems to have generated) and somebody responds to and coordinates the community's efforts (which this project has not done). The original author has barely participated once or twice on the issue tracker in the last couple years, PR requests have gone unmerged with no feedback as to why, and incoming issues are not getting triaged. Furthermore I would like to propose the following to fix this situation: - [ ] **1.** Deal with #212. Pick an actual OSS license and apply it to the current code. The status quo license limbo is crazy and killing the project. Open source projects do not thrive while under proprietary licenses and if you wait until feature completion/maturity to open it up ① a single distracted author will never be able to bring in to maturity and ② there will be little wider interest in helping get it there because the effort invested seems to be poured into a black hole. - [ ] **2.** Appoint at least one maybe two other
Comments (0)
No comments yet. Start the discussion.