Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do we organize this? #1

Open
capr opened this issue Jan 25, 2019 · 10 comments
Open

How do we organize this? #1

capr opened this issue Jan 25, 2019 · 10 comments

Comments

@capr
Copy link
Member

capr commented Jan 25, 2019

Do we want a separate repo for discussion or do we use this one?

@aiverson
Copy link
Collaborator

I think it depends on what kind of discussion. I feel like we should have an initial meeting about organization in real time elsewhere rather than in these issues, document the decisions from that discussion into the README, and then use issues mostly for things like "should we add this to the stdlib" and "who is getting assigned to this feature" and "there is a bug in something"

@capr
Copy link
Member Author

capr commented Jan 25, 2019

@aiverson ok, how about we have a chat on gitter?

btw @elliottslaughter, please make the org "read/write" by default so we can avoid the overhead of pull-requests.

@elliottslaughter
Copy link
Member

@capr I believe I have done this, please let me know if there's anything else.

@aiverson
Copy link
Collaborator

No, pull requests are really important here. We should do code reviews on everything in the Standard Library. These things need to be relatively bug free and secure, so having code reviews is useful. We just need to have a good process for approving pull requests and doing code reviews, and a good architecture that supports that. I can add you both as collaborators here so that you have edit access and can approve PRs. We can rough out some basics without using a full review process, but I think we need to do code reviews and PRs at some point.

@capr
Copy link
Member Author

capr commented Jan 25, 2019

@capr
Copy link
Member Author

capr commented Jan 25, 2019

FYI: I deleted the other repo and added a welcome message to this one, so I propose to just use this one for both talking and code. Lemme add a first "real" talking point.

@Qix-
Copy link

Qix- commented Feb 12, 2019

Just chiming in: I think the realtime Gitter + this repository for discussion and code is perfect. I vote to keep it as-is.

However, I'd say we should rename it to simply terra/stdlib or perhaps even terra/std. Prefixing the repository name with the organization name is redundant.

@capr
Copy link
Member Author

capr commented Mar 1, 2019

Chat moved to https://terralang.zulipchat.com

@aiverson
Copy link
Collaborator

Is the zulip chat abandoned at this point?

@elliottslaughter
Copy link
Member

I don't know about anyone else, but on my end I failed to set up email notifications... So not intentionally abandoned, no.

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

No branches or pull requests

4 participants