Forks and other sundry items
Michael Latiolais <[email protected]> Fri, 6 Jan 2006 08:48:35 -0800 (PST)
| Newsgroups | gmane.comp.graphics.y.devel |
|---|---|
| Message-ID | <[email protected]> |
--0-1398440672-1136566115=:6439 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Instead of talking about forking the codebase, might I suggest an alternative route: actually doing it. Simply talking about this gets you nowhere, and just irritates the developers(wherever they might be now...). Instead, grab a copy of the arch repository, the 0.2.1 tarball, whatever, and actually do some coding. Bring something to the table besides good intentions. If you don't have the skills or energy to hack out something significant, what makes you think that you have the drive to maintain a fork? Look at the roadmap(http://www.y-windows.org/docs_roadmap.html), decide on what you want to do, and just do it. --0-1398440672-1136566115=:6439 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit <div id="RTEContent">Instead of talking about forking the codebase, might I suggest an alternative route: actually doing it. Simply talking about this gets you nowhere, and just irritates the developers(wherever they might be now...). Instead, grab a copy of the arch repository, the 0.2.1 tarball, whatever, and actually do some coding. Bring something to the table besides good intentions. If you don't have the skills or energy to hack out something significant, what makes you think that you have the drive to maintain a fork? Look at the roadmap(http://www.y-windows.org/docs_roadmap.html), decide on what you want to do, and just do it. <br> <br></div> --0-1398440672-1136566115=:6439--