From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Date: Wed, 1 May 2013 09:30:22 +0000 From: mortdeus Message-ID: <72121e16-3e6a-4e96-a035-1035f95797b5@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable References: Subject: Re: [9fans] [GSOC 2013] Implement plan9 commands in Go, Goblin Topicbox-Message-UUID: 4de8598a-ead8-11e9-9d60-3106f5b1d025 Sure im always open to contributions. The only requirements for goblin are.= .. 1. The plan9 command line api may not be changed.=20 2. No import dependencies outside go's standard library except (http://godo= c.org/github.com/guelfey/flag9) due to rule 1. (maybe termbox will be allow= ed if it simplifies the implementation greatly.) 3. All tools must be implemented as cross platform if possible. If we can e= mulate plan9 behavior in userland like inferno does then thats probably the= way to go. 4. Most commands in goblin should be new implementations rather than C -> G= o ports of the plan9 commands. Lucent PL is not GPL compatible and the goal= is to not reintroduce code licensed under Lucent PL if it can be avoided. = Some code like yacc has already been ported to Go from outside the goblin p= roject and it doesnt make sense to replicate the effort in circumstances li= ke this. Other than cases like this, I will reject code that appears to be = directly derived of plan9's source.