Hi -
On 11/16/16, 12:37 PM, "Pedro N. Rodriguez" <[email protected]> wrote: > > >Dear team, > > >As a way of learning Chapel, I have decided to create a Visual Code >Extension. Currently I have a very simple version using both the snippet >and tmLanguage files available at Github. Nonetheless, I would like to > continue working on this and hopefully add additional functionality. > > >What would work best? Should I just create a public github project and >continue working on isolation or should I "push" the extension to the >chapel project? If the extension is relatively small and amounts to syntax highlighting, I'd store it in highlight/ in our repository and then it would make it in to releases. Note that in that case you'd have to sign a contributors agreement (basically agreeing that the contributed code can be distributed under the Apache 2 license). If it's pretty big / significant, or if there's some reason you don't want to contribute it, putting it in your own GitHub repo makes sense. Either way some documentation for people unfamiliar with Visual Code is going to be critical. Cheers, -michael > > > > >However, if someone is already working on this, then probably I could >this time to create other benchmarks more financial oriented. Just let me >know. > > > > >Best, > > > >Pedro > > > > > > > > ------------------------------------------------------------------------------ _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
