Going off of that previous thread ("GNUstep Public Relations"), it
sounds like there's some interest in tackling issues on the wiki first,
and using GitHub Projects to track the work.With GitHub Projects, it appears that tasks in a project are actually GitHub Issues that still need to be connected to a repo. The projects view is just a better way to organize and visualize them. Two questions on this: 1. Will one repo (gnustep/website) work for all tasks concerning the web presence, or do we need to have two separate repos (gnustep/website, gnustep/wiki)? 2. What's the process like to get the repo/s and project created on GitHub, and to be able access them? -- Luke Lollard
