Skip to content
This repository has been archived by the owner on Jul 16, 2019. It is now read-only.

Contributing guidelines #1

Open
Beanow opened this issue Jun 11, 2019 · 1 comment
Open

Contributing guidelines #1

Beanow opened this issue Jun 11, 2019 · 1 comment

Comments

@Beanow
Copy link

Beanow commented Jun 11, 2019

From sfosc/sfosc#87 and information on https://polyformproject.org/ it seems GitHub is not the primary / singular collaboration tool for polyform.

So I wonder for meta things like the webpages:

  • Where to best keep track of work?
  • With what and how one might help?
  • Things to keep in mind when you do?
@kemitchell
Copy link
Member

@Beanow, thanks for your interest!

You are right that we have used other forums to discuss and work so far. But when we announced the license draft, we transitioned here to GitHub.

Our primary project right now is focusing on the license language, so that we can release a version 1.0.0 of all of the licenses soon. The best things anyone can do for the project right now are:

  1. Reading the license terms and sending feedback.

  2. Encouraging representatives from organizations that might release or accept software on Polyform terms to read and feed back. We are especially interested in word from companies that might use Polyform terms to release software, and in word from noncommercial organizations like universities and charities that might use that software.

When we have a 1.0.0 to publish, we will also be working on a complete website to replace the single-page site that we have now.

If I'm not mistaken, you have already signed up to our mailing list. We plan to begin using that list to make specific calls for help very soon.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants