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

Update/Change GNU Social Repo #2106

Closed
BeaverTek opened this issue May 26, 2020 · 3 comments · Fixed by #2271
Closed

Update/Change GNU Social Repo #2106

BeaverTek opened this issue May 26, 2020 · 3 comments · Fixed by #2271
Assignees
Labels
Milestone

Comments

@BeaverTek
Copy link

The current GNU Social repo is at: https://notabug.org/diogo/gnu-social
It's under active development. V2 will be out soon and v3 is being worked on.

@SuperSandro2000
Copy link
Contributor

https://gnu.io/social/ points to https://git.gnu.io/gnu/gnu-social/-/issues which throws a 500. You know what is correct?

@BeaverTek
Copy link
Author

The original creator / lead dev of GS, mattl, abandoned the project long ago. The new Project Lead is Diogo. He, along with a few others, are mentoring students currently as part of the G. Summer of Code. Diogo's in touch with the folks at GNU.
Current Stable is v1.20.9

Official IRC
server: freenode
room: #social

Official unofficial XMPP MUC
server: conference.bka.li
room: gnusocial

Oh, I see what you mean SuperSandro.
https://git.gnu.io/gnu/gnu-social/
that's the correct link. Follow the first link on the gnu.io/social or simply take the hyphen out.

@nodiscc nodiscc added the fix label Aug 22, 2020
@nodiscc nodiscc self-assigned this Oct 8, 2020
@nodiscc nodiscc added this to the 1.0 milestone Oct 8, 2020
nodiscc added a commit that referenced this issue Oct 10, 2020
@BeaverTek
Copy link
Author

Sorry, I seem to have failed to mention that the main / currently actively maintained homepage for the site is: https://gnusocial.network

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

Successfully merging a pull request may close this issue.

3 participants