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

Website should have a 'getting started' page #246

Merged
merged 3 commits into from
Feb 26, 2017
Merged

Website should have a 'getting started' page #246

merged 3 commits into from
Feb 26, 2017

Conversation

guusdk
Copy link
Contributor

@guusdk guusdk commented Jan 16, 2017

This pull request introduces a new page that guides people that are completely new to XMPP.

This pull request results from a discussion on the XSF MUC earlier today. I thought it'd be a good idea to float the idea in a tangible way. Obviously, the commit needs work: the list of clients and services needs to be completed, and the entire thing could be made a lot prettier too.

This commit adds a page that describes, to novice users, how to start using XMPP
for instant messaging.
@guusdk
Copy link
Contributor Author

guusdk commented Jan 16, 2017

Here's a screenshot of the commit: https://ibin.co/3987T3lKd72z.png

(Note that locally, I've not been able to get the menu to work right)

@guusdk guusdk changed the title Website should have a XMPP 101 page Website should have a 'getting started' page Jan 16, 2017
Adding the first two semi-popular services that accept new registrations.
Added jwchat.org and jabber.at, Gajim, Adium and Pidgin.
@bear
Copy link
Contributor

bear commented Jan 17, 2017

👍

let's get it on the site as nothing makes people update/fix/add things than seeing it on the web

@guusdk
Copy link
Contributor Author

guusdk commented Jan 17, 2017

I like the way you're thinking @bear :)

Up until now, the XSF remained neutral to a fault, where it concerns implementation or service advocacy. That changes somewhat with this PR, as it pushes forward some clients and services.

Although I believe this is acceptable (and to this degree, desirable), others have voiced concerns.

Is this PR something that we want to run by the board?

@bear
Copy link
Contributor

bear commented Jan 17, 2017

I don't think it requires that - let's ask forgiveness if someone really sees something they don't like

@Kev
Copy link
Member

Kev commented Jan 18, 2017

I hate to be a dissenting voice here, but the website is the voice of the XSF and the XSF has previously decided to be neutral. I don't think it's up to anyone here to change that. Bring it before Board. It's either a simple 'yes', in which case no harm done by asking, or it's a 'no', in which case it clearly shouldn't have been merged.

@ge0rg
Copy link
Contributor

ge0rg commented Jan 23, 2017

@Kev would it be sufficiently neutral to only link to the XSF client list and a public server list like https://xmpp.net/directory.php ?

In that case I'd argue that we make a first, neutral, version of the page and get that out, so that it's not blocked by the much needed discussion. Regarding the overall neutrality question, I think this is something that should be brought up at the summit, and be decided by the whole XSF.

@Kev
Copy link
Member

Kev commented Jan 25, 2017

Referring to third-party lists doesn't seem harmful to me, if appropriately linked.
I think we should bring this PR before Board and see if we can do it all though.

@guusdk guusdk merged commit 195fadc into xsf:master Feb 26, 2017
@guusdk
Copy link
Contributor Author

guusdk commented Feb 26, 2017

I've herded this PR for six weeks now, but little progress is made, discussion-wise. In various discussions that started, but never concluded, the general consensus appeared to be in favor of leaving strict neutrality. As far as I can tell, the last board meeting didn't discuss the neutrality topic, while the one before that bulldozered the issue ahead.

I'm merging this issue. If people care enough about this issue to disagree, I'm assuming that my merge will trigger a follow-up.

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

Successfully merging this pull request may close these issues.

4 participants