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

Move chat to slack #376

Closed
jeromeetienne opened this Issue Jul 3, 2018 · 8 comments

Comments

Projects
None yet
3 participants
@jeromeetienne
Copy link
Owner

jeromeetienne commented Jul 3, 2018

Move chat to slack, thus we can get channel

@nicolocarpignoli

This comment has been minimized.

Copy link
Collaborator

nicolocarpignoli commented Jul 9, 2018

For anyone who wants to help to contribute to this project, please write to me or @jeromeetienne for an invite on the slack channel

@janpio

This comment has been minimized.

Copy link

janpio commented Feb 8, 2019

ping, piotrowski+slack@gmail.com (docs and readme work)

@nicolocarpignoli

This comment has been minimized.

Copy link
Collaborator

nicolocarpignoli commented Feb 11, 2019

@janpio sadly author of AR.js is not responding to chat/email for a long time. I cannot add you on github contributor so Is kinda useless :(

@janpio

This comment has been minimized.

Copy link

janpio commented Feb 11, 2019

I am fine with going the normal Pull Request route, but a way to ask what stuff is already in the works, planned etc might be valuable anyway.

@nicolocarpignoli

This comment has been minimized.

Copy link
Collaborator

nicolocarpignoli commented Feb 11, 2019

Yea, problem is actually nothing is planned. I don't see any commitment actually..

@janpio

This comment has been minimized.

Copy link

janpio commented Feb 11, 2019

Ok.

I am interested in keeping AR.js alive as I used it in a project, and the current state of the repo is not optimal for "selling" the usage of AR.js to clients. Even if there is no (big) future development, it would still make sense to get the current working software in a better environment.

There was some work started to migrate the repo to an org in the past, but if I understood correctly this was stopped because old URLs might stop working or something like that. Maybe we should just start there ("move AR.js to the org") and investigate the best way so things don't break while doing this, and then try to get @jeromeetienne to go through with the transfer - including admin rights for you.

Right direction?

@nicolocarpignoli

This comment has been minimized.

Copy link
Collaborator

nicolocarpignoli commented Feb 11, 2019

Could be the right direction. We started a slack chat. Some were invited, but then nobody has started with the commitment - if not for someone, also this is probably due to lack of 'direction', absolutely not to blame anyone.

We can start again to try to do things done this time. Otherwise the other path is to create a brand new repository and try to re-direct people from this one, that could be flagged as obsolete.

I'd like to know thoughts from people on AR.js slack, I will email them and see if they can chat here to decide something.

@janpio

This comment has been minimized.

Copy link

janpio commented Feb 11, 2019

I created #469 so this is an independent issue and we don't abuse this one about Slack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment