xsf / xmpp.org Goto Github PK
View Code? Open in Web Editor NEWxmpp.org website (builds: https://github.com/xsf/xmpp.org/actions)
Home Page: http://xmpp.org
xmpp.org website (builds: https://github.com/xsf/xmpp.org/actions)
Home Page: http://xmpp.org
@Kev took this very very very graciously.
There should be links to projects of https://github.com/xsf/ of course ;-)
I'll write this from #15
We have XMPP uses for IOT, webrtc, im, social. But we're missing a section on realtime-web. I think @lloydwatkin and @legastero would be best placed to write two paragraphs on this.
@dwd to send a pull request
I suggest to remove the release dates in those tables.
Some of the dates are wrong right now. And it would be hard for us to maintain all this dates.
We should not give a visitor the impression that a software is outdated only because we missed updating the dates.
Presently, all page URLs end with .html
It's possible to get URLs that end without .html through changes to pelican's configuration.
Compare the present XSF configuration:
ARTICLE_PATHS = [ 'posts/blog', 'posts/learn' ]
ARTICLE_URL = 'posts/{blog_id}/{date:%Y}/{date:%b}/{date:%d}/{slug}'
ARTICLE_SAVE_AS = 'posts/{blog_id}/{date:%Y}/{date:%b}/{date:%d}/{slug}.html'
INDEX_SAVE_AS = 'posts/blog/index.html'
...
YEAR_ARCHIVE_SAVE_AS = 'posts/blog/{date:%Y}/index.html'
with my own site's pelican configuration:
PAGE_URL = '{slug}'
PAGE_SAVE_AS = '{slug}/index.html'
CATEGORY_URL = '{slug}'
CATEGORY_SAVE_AS = '{slug}/index.html'
YEAR_ARCHIVE_SAVE_AS = '{date:%Y}/index.html'
MONTH_ARCHIVE_SAVE_AS = '{date:%Y}/{date:%m}/index.html'
DAY_ARCHIVE_SAVE_AS = '{date:%Y}/{date:%m}/{date:%d}/index.html'
per issue #17 the following need to be converted:
http://xmpp.org/2015/05/eyeball-networks/
http://xmpp.org/2015/04/xsf-gsoc-students-2015/
http://xmpp.org/2015/03/board-goals-for-2015/
http://xmpp.org/2015/03/summit-17-the-presentations/
http://xmpp.org/2015/03/an-introduction-to-xmppresearch-org/
http://xmpp.org/2009/02/google-summer-of-code/
http://xmpp.org/2015/03/xmpp-in-google-summer-of-code-2015/
http://xmpp.org/2015/03/no-its-not-the-end-of-xmpp-for-google-talk/
http://xmpp.org/2015/02/thank-you-xsf-sponsors/
http://xmpp.org/2015/01/its-all-about-choices-and-control/
http://xmpp.org/2015/01/xmpp-summit-17/
http://xmpp.org/2014/05/upcoming-events/
http://xmpp.org/2014/05/happy-encrypted-network/
http://xmpp.org/2014/04/xmpp-on-the-global-internet-of-things-day/
http://xmpp.org/2014/04/security-notice-uncontrolled-resource-consumption-with-highly-compressed-xmpp-stanzas/
http://xmpp.org/2014/03/third-security-test-day/
I think you have this access @imaginator?
From #15
At the least, we need to change RFC 6122 to RFC 7622.
Also adding RFC 7395 would be good.
We need to move existing content to the new site. But before we can do that, we need some kind of plan for what goes where.
I've pulled down an exhaustive list of all URLs on the present xmpp.org site, then grouped and sorted by what I think we should do with them.
I would really like input on the "misc" sections.
Not sure what to do with these.
http://xmpp.org/about-xmpp/xsf/xsf-ipr-policy/
http://xmpp.org/about-xmpp/xsf/xsf-people/
http://xmpp.org/author/admin/
http://xmpp.org/about-xmpp/?page_id=297
http://xmpp.org/author/stpeter/
http://xmpp.org/about-xmpp/faq/?page_id=297
http://xmpp.org/internet-drafts/attic/draft-jabber-00.txt
http://xmpp.org/internet-drafts/attic/draft-jabber-00.html
http://xmpp.org/internet-drafts/attic/draft-miller-jabber-00.txt
http://xmpp.org/internet-drafts/attic/draft-miller-jabber-00.html
http://xmpp.org/about/bof-minutes.txt
http://xmpp.org/about/wg-charter.txt
http://xmpp.org/about/ipr-notice.txt
Not sure what to do with these.
http://xmpp.org/xmpp-protocols/xmpp-core/?page_id=297
http://xmpp.org/participate/become-a-member/editor-team/
http://xmpp.org/extensions/inbox/
http://xmpp.org/extensions/refs/
http://xmpp.org/xmpp-protocols/xmpp-extensions/submitting-a-xep/
Need to make some decisions about how and where these are linked to/from. @ralphm would love to have your input.
http://xmpp.org/rfcs/rfc3920.html
http://xmpp.org/rfcs/rfc3921.html
http://xmpp.org/rfcs/rfc6120.html
http://xmpp.org/rfcs/rfc6121.html
http://xmpp.org/rfcs/rfc6122.html
I'm a bit confused to see all the contents of the content
folder are HTML files instead of markdown. (https://github.com/xsf/xmpp.org/tree/master/content)
I'm hesitant to assume this was an arbitrary decision. Is there a reason it was set up this way initially?
Basic bootstrap theme
We'll want some redirects for some existing pages given the restructuring of some of the content. This issue is a placeholder for mapping 301s we'd need. (Waiting on #17)
jdev logs point at outdated: http://logs.jabber.org/[email protected]/
we need this updated to the new logs wherever they are at https://github.com/xsf/xmpp.org/blob/master/content/pages/community/chat.md
Ralph/peter: @intosi might know something about this.
From #15
http://xmpp.org/about-xmpp/xsf/meeting-minutes/
These need to be ported to markdown pages in content/pages/about/xsf/records/meeting-minutes
@lauracrossley pointed out this would be good content to add. http://wiki.xmpp.org/web/index.php?title=Myths
If I add a file to content/posts/learn
I do get the learn post properly generated, but I don't seem to get any of the indexes generated.
Much of this content can come from the original website.
These voting records (linked from here) need to be ported to markdown pages in content/pages/about/xsf/records/council-votes
For generating markdown tables, this tool is awesome.
Arguably, these could all just go into one page reverse chronologically sorted.
We need to settle on the homepage tagline / strapline. Current it reads:
"The most secure messaging standard"
Is that what we agree to use for launch?
Looks like @guilhermesgb has made some cool stuff to get menus to work nicely. (Thanks!)
I'm going to review how these work and add the info to the README—unless Guilherme beats me to it :)
From #15
From #15
http://xmpp.org/xmpp-protocols/
http://xmpp.org/xmpp-protocols/protocol-namespaces/
http://xmpp.org/xmpp-protocols/xmpp-core/
http://xmpp.org/xmpp-protocols/xmpp-extensions/
http://xmpp.org/xmpp-protocols/internet-drafts/
http://xmpp.org/xmpp-protocols/rfcs/
http://xmpp.org/xmpp-protocols/?page_id=297
http://xmpp.org/protocols/activity/
http://xmpp.org/protocols/address/
http://xmpp.org/protocols/amp/
http://xmpp.org/protocols/bookmarks/
http://xmpp.org/protocols/bytestreams/
http://xmpp.org/protocols/caps/
http://xmpp.org/protocols/chatstates/
http://xmpp.org/protocols/commands/
http://xmpp.org/protocols/compress/
http://xmpp.org/protocols/disco/
http://xmpp.org/protocols/feature-neg/
http://xmpp.org/protocols/file-transfer/
http://xmpp.org/protocols/geoloc/
http://xmpp.org/protocols/http-auth/
http://xmpp.org/protocols/httpbind/
http://xmpp.org/protocols/ibb/
http://xmpp.org/protocols/jabber_client/
http://xmpp.org/protocols/jabber_iq_last/
http://xmpp.org/protocols/jabber_iq_oob/
http://xmpp.org/protocols/jabber_iq_privacy/
http://xmpp.org/protocols/jabber_iq_register/
http://xmpp.org/protocols/jabber_iq_roster/
http://xmpp.org/protocols/jabber_iq_rpc/
http://xmpp.org/protocols/jabber_iq_version/
http://xmpp.org/protocols/jabber_server/
http://xmpp.org/protocols/jabber_server_dialback/
http://xmpp.org/protocols/jabber_x_conference/
http://xmpp.org/protocols/jabber_x_data/
http://xmpp.org/protocols/jabber_x_oob/
http://xmpp.org/protocols/jidescaping/
http://xmpp.org/protocols/linklocal/
http://xmpp.org/protocols/mood/
http://xmpp.org/protocols/muc/
http://xmpp.org/protocols/nick/
http://xmpp.org/protocols/offline/
http://xmpp.org/protocols/pep/
http://xmpp.org/protocols/pubsub/
http://xmpp.org/protocols/rc/
http://xmpp.org/protocols/rosterx/
http://xmpp.org/protocols/rsm/
http://xmpp.org/protocols/shim/
http://xmpp.org/protocols/si/
http://xmpp.org/protocols/sipub/
http://xmpp.org/protocols/soap/
http://xmpp.org/protocols/streams/
http://xmpp.org/protocols/tune/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-bind/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-e2e/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-sasl/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-session/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-stanzas/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-streams/
http://xmpp.org/protocols/urn_ietf_params_xml_ns_xmpp-tls/
http://xmpp.org/protocols/urn_xmpp_archive/
http://xmpp.org/protocols/urn_xmpp_attention/
http://xmpp.org/protocols/urn_xmpp_avatar/
http://xmpp.org/protocols/urn_xmpp_blocking/
http://xmpp.org/protocols/urn_xmpp_bob/
http://xmpp.org/protocols/urn_xmpp_captcha/
http://xmpp.org/protocols/urn_xmpp_delay/
http://xmpp.org/protocols/urn_xmpp_features_rosterver/
http://xmpp.org/protocols/urn_xmpp_jingle/
http://xmpp.org/protocols/urn_xmpp_jingle_apps_rtp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_ibb/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_ice-udp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_raw-udp/
http://xmpp.org/protocols/urn_xmpp_jingle_transports_s5b/
http://xmpp.org/protocols/urn_xmpp_langtrans/
http://xmpp.org/protocols/urn_xmpp_media-element/
http://xmpp.org/protocols/urn_xmpp_pie/
http://xmpp.org/protocols/urn_xmpp_ping/
http://xmpp.org/protocols/urn_xmpp_receipts/
http://xmpp.org/protocols/urn_xmpp_sm/
http://xmpp.org/protocols/urn_xmpp_ssn/
http://xmpp.org/protocols/urn_xmpp_time/
http://xmpp.org/protocols/urn_xmpp_xbosh/
http://xmpp.org/protocols/waitinglist/
http://xmpp.org/protocols/xdata-layout/
http://xmpp.org/protocols/xdata-validate/
http://xmpp.org/protocols/xhtml-im/
http://xmpp.org/xmpp-protocols/protocol-namespaces/?page_id=297
http://xmpp.org/protocols/jabber:client/
http://xmpp.org/protocols/jabber:server/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-session/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-bind/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-sasl/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-e2e/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-stanzas/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-streams/
http://xmpp.org/protocols/urn:ietf:params:xml:ns:xmpp-tls/
based on issue 15 - this page must be written.
Where/how does this get generated?
@dwd offered to write this.
Now that I have the site structure in my head, this is my first order of business.
I think I'll stub out the markdown files for these to begin with, then create an issue with a punch list.
http://xmpp.org/sponsor/sponsor-the-xsf/
to /community/sponsorship
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.