Re: [racket-users] on-boarding new racketeers

2019-08-14 Thread Paulo Matos
On 14/08/2019 14:44, Hendrik Boom wrote: > But there's also the issue tracking. How easy is it to export that > from github and install it on another system? > > And there is an MIT-licenced alternative to github showing up > soon: gitea. They let you use your own machines instead of >

Re: [racket-users] on-boarding new racketeers

2019-08-14 Thread Stephen De Gabrielle
Hi, On Wed, Aug 14, 2019 at 9:45 PM Hendrik Boom wrote: > > But there's also the issue tracking. How easy is it to export that > from github and install it on another system? > > there is an API :) https://developer.github.com/v3/issues/ could be easily scripted in racket...or you can also

Re: [racket-users] on-boarding new racketeers

2019-08-14 Thread Hendrik Boom
On Wed, Aug 14, 2019 at 02:25:40PM +0900, Stephen De Gabrielle wrote: > I’m travelling so haven’t been able to properly read the discussion :( > > I do want to add: > > A) Keep local git repos (backups) on storage you control- this is important > as you never know when you will lose access to a

Re: [racket-users] on-boarding new racketeers

2019-08-13 Thread Stephen De Gabrielle
I’m travelling so haven’t been able to properly read the discussion :( I do want to add: A) Keep local git repos (backups) on storage you control- this is important as you never know when you will lose access to a data centre (github, gitlab, Amazon, azure, iCloud , Dropbox , etc.) B) I know

Re: [racket-users] on-boarding new racketeers

2019-08-13 Thread Hadi Moshayedi
Thanks Stephen! On Mon, Aug 12, 2019 at 7:52 AM Stephen De Gabrielle < spdegabrie...@gmail.com> wrote: > 5. Put the location of the scribble source file at the beginning of every > scribble file because it is really hard to find the location of scribble > source; > 'Quick: An Introduction to

[racket-users] on-boarding new racketeers

2019-08-12 Thread Stephen De Gabrielle
Hi, I've been thinking about small things that can be done to lower the barriers to entry to the racket community, and I've come up with some ideas! 1. Adopts the standard GitHub set of issue labels* for all active repositories, only deviating where necessary. Benefit - This would allow