Search results

#REDIRECT [[:Category:Spec_Remarks]]

#REDIRECT [[:Category:Spec_Remarks]]

=== Specification front === * Specs in last call

{{specs}}

[[Category:Spec_Remarks]]

{{specs}} ...popular method is to have users contact administrators, or some deployment-specific solution.

...client and server side. I also have an important understanding of the XMPP specs since I had to "study" them to correctly implement our server and client s ...he knowledge and experience I gained after implementing many JEPs and XMPP specs both on the server and client sides.

...cretary, Treasurer, Executive Director, etc. I also [co-]authored a lot of specs, both XEPs and RFCs. ...years I was very active in the Internet Engineering Task Force (IETF) as a spec author, working group chair, member of the Internet Engineering Steering Gr

...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.

RETIRED * Hardware specs: Dell Poweredge 1850(Dual P4 Hyperthreaded Xeon CPUs (2.8 Ghz), 4 GB mem, RETIRED * Hardware specs: Dell Poweredge 1850(Dual P4 Hyperthreaded Xeon CPUs (2.8 Ghz), 2 GB mem,

...Technical Review Team is to continuously improve the technical quality of specifications produced by the XMPP Standards Foundation. === Spec Reviews ===

{{specs}}

...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.

* Justin to update the spec to reflect IRL discussion ...lements in message/presence (Justin to write first draft of best practices spec):

* Heavily advocates XMPP's use in games and is working on a spec for out-of-band server advertising based on pubsub and MUC For the Copyleft Games Group (which PySoy is part of), I'm working on a spec for out-of-band gaming via XMPP/Jingle. I want to leverage compatibility a

...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.

{{specs}}

...cts on top of software which has real use and support in the community. We specialise in real-time communications, including IM, VOIP, video and collaborat ...dless of the underlying protocol, language or even license. As well as the spec itself, Collabora supports and develops the Jabber/XMPP backend as our main

...cretary, Treasurer, Executive Director, etc. I also [co-]authored a lot of specs, both XEPs and RFCs. ...years I was very active in the Internet Engineering Task Force (IETF) as a spec author, working group chair, member of the Internet Engineering Steering Gr

...ason to reapply for XSF membership. One of my main interests is making our specs more approachable to client (library) developers.

...one of its founding developers. I've also contributed to a variety of XMPP specs, and am mentioned in the RFCs.

This event's goal is to produce tools (specs, implementations, etc.) for public XMPP services,

...and howto documents, but since 2001 I've concentrated on writing protocol specs -- mostly [http://xmpp.org/extensions/ XEPs] and [http://xmpp.org/rfcs/ R

...mostly focused on documenting existing protocols and writing new protocol specs. As a result I edited the XMPP RFCs and have also written dozens of XMPP E * Push more specs from Draft to Final (see [http://mail.jabber.org/pipermail/standards/2007-

...h with the standardization process. One of my main interests is making our specs more approachable to (future) client (library) developers.

would like to specifically address while on the council. I suspect the answer is some mix of modifying the name of the document statuses, cre

...h with the standardization process. One of my main interests is making our specs more approachable to client (library) developers.

** Idee: Es gibt nur eines Spec -> Interoperabilität ** Hat [https://matrix.org/docs/spec/proposals Spec-Proposal-Prozess]

I think that XMPP on the mobile, especially with project's like [https://github.com/rtreffer/AsmackService AsmackS ...ing on some of the social bits in XMPP. (Eventually I'd like to see a good spec for XMPP social, I just don't think we are there yet)

...nes. Has some been Obsoleted, or simply Updated? Also learn about Friendly specs! focus on specs

...be used for United Communications. I've provided feedback about the Jingle specs directly to Peter Saint-Andre instead of posting to the public discussion

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;

...sode, I work on the M-Link XMPP server. Needless to say a lot of XMPP and spec reading are involved here :)

* both editing and writing specs * clarifying question: editorial or actually writing specs?

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;

* Clean up the publish-subscribe specifications (XEP-0060, XEP-0163, XEP-0248) * Advance the server dialback specification (XEP-0220) to Draft

...al features of stable XEPs. This gives me a unique perspective on the XMPP specifications. There are also a fair number of specifications I'd like to see progress on. These include

* improving Tigase's compatibility with XMPP specs and general interoperability,

* improving Tigase's compatibility with XMPP specs and general interoperability,

...al features of stable XEPs. This gives me a unique perspective on the XMPP specifications. I'm quite active on the standards mailing list. There are also a fair number of specifications I'd like to see progress on. These include

...I work on the M-Link XMPP server team. Needless to say a lot of XMPP and spec reading (and suggesting cleanups in them) are involved here :)

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability,

* we are very good at specifications, but only by developers for developers, we don't ask enough our u ...good and best practices already available on the market, both in terms of specs and implems <= PUSH FOR IMPLEMENS OF NEW XEPs, COLLECT FEEDBACK

* [[Sprints/2020 March Duesseldorf|March 2020 Duesseldorf Spec Sprint]]

* [http://code.google.com/soc/inkscape/about.html Inkboard Protocol Spec and Lib Conversion]

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability,

* finding and fixing bugs thus improving compatibility with XMPP specs and general interoperability;

* improving Tigase's compatibility with XMPP specs and general interoperability,

...any of the clients, servers or libraries lacking support (see the project-specific lists below). ...xperience with this method so that we can correct and advance the relevant specs, which are:

...od practices" to make things speak the same language. The interoperability spec will be a moving target with constant elaboration to enable true interopera ...nd doesn't cost a fortune to be compliant. And most importantly it is open specifications that is easy to find.

* improving Tigase's compatibility with XMPP specs and general interoperability,

* [http://code.google.com/soc/inkscape/about.html Inkboard Protocol Spec and Lib Conversion]

! Client !! Described Version !! Jingle Audio Spec !! Transport Methods !! Audio Codecs || ICE implementation || STUN/TURN dis ...freedesktop.org/wiki/ libnice] || DNS (for STUN), Google Jingle Info, user specified || Yes (via libnice) || No

...mostly focused on documenting existing protocols and writing new protocol specs. As a result I edited the XMPP RFCs and have also written dozens of JEPs.

...SF discussions and other business, I have a few goals that I would like to specifically address while on the council: ...e the legacy [https://xmpp.org/extensions/xep-0136.html Message Archiving] spec (which I will revisit once MAM has been debated).

My passion is programming, and I am specializing in the topics of low-level hardware development and post-quantum cr I have largely contributed to the recent versions of the OMEMO XEP, especially the cryptographic details.

== XMPP Specifications == ...is my reason to apply for XSF membership. My main aim would be making our specs more approachable to client (library) developers.

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

* it needs to be specified more clearly: what is packet relay? * usage of relay on XMPP network is discouraged. right now the spec says you SHOULD allow relaying (since you MAY decide not to allow it). Let'

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...even needed - no real consensus as it may be too implementation enironment specific two aspects of conferencing

...ther) discussions on the XMPP mailing lists. However, my official protocol spec contributions remain limited to the following XEPs:

=== Specs === ...tations from Joe on some of the new XEP's he would like to see worked on (especially Carbons, XEP-0280) and then we had some demos of &yet's [http://otalk.

..., multi-user chat (XEP-0045), publish-subscribe (XEP-0060), and the Jingle specs (XEPs 166, 167, 176, 234, etc.). In 2009 I co-authored "XMPP: The Definiti

== Base Specifications == This specification. Defines how provisioning, the management of

Some need specs, some need implementation/deployment. No specific conclusion/action.

...gs communicate. In order to make it happen we must work for provide robust specs in area of rather new development: ...(we are working on and RSS/Atom mobile reader and we think that there few aspects that need standardization)

...t, David Durand's Palimpsest model, some of the Tiny SVG spec and the XMPP specs. * Read documentation again, mainly other XEPs and a few old mailing lists, especially about writing the XEP.

...e constructively to protocol (and other) discussions, my official protocol spec contributions are limited to the following XEPs:

...he same DOM. Basic groups communication primitives are part of first level spec.

...mmands in Mellium to draw forms. Also we'll discuss some problems with the spec and how they could be resolved.

== Base Specifications == This specification. Defines how provisioning, the management of

...Peter, though). I've also been actively reviewing the 3920bis and 3921bis specs. I've been involved in the formation of a number of XEPs (and more are com * 198 is specced, and is starting to see use - we need to push for this.

This page lists known issues with the Publish-Subscribe specifications ([http://xmpp.org/extensions/xep-0060.html XEP-0060], [http://xmp * The section mentions that a '''body''' element can be provided and used to specify ''natural-language text regarding the affiliation change''.

...he cold north]", with sauna and crêpes, working on new groupchat bookmarks specification, file transfer interoperability issues, and a future landing page === Extensions and specifications ===

* [[:Category:Spec Remarks|Remarks about XEPs and RFCs]]

...eply within exam stuff and will remain so for several more weeks. Studying specifications of Encrypted sessions protocol, some of it's dependencies and of ...them and I found XMPP protocol even more capable and better than I first suspected. Well, XML namespace stuff is quite complicated (entire XML namespace mo

* got an open and open-minded community, can't believe it, even specs are free(speech)!

The second part is almost the opposite - in some respects, you can measure the worth of a Council member by how many times they're ...e knowledge the Council has. The last session had two server developers, a specification expert, a service developer, and a client developer. We had an exp

The spec is quite confusing either refering to XEP-0065's requester/target or Jingle If the XEP could provide a way to authenticates a specific candidate instead of the transport as a whole, that would make it possi

== Base Specifications == This specification. Defines how provisioning, the management of access privileges, et

* [[:Category:Spec Remarks|Remarks about XEPs and RFCs]]

...ses, Whatsapp uses an XMPP-derivative protocol, Google Hangouts uses some aspects of XMPP internally, and as well as end-users it's used extensively by ent ...ate this use case. However, to get real life feedback and improve our XMPP specifications, we need to experiment with working code. A consistent package of

...ike clients, servers, libraries, but also hosted/running services (because specifications don't have to be widely covered since we have one central origin: ...lish very early proof-of-concepts, this can clearly lead to new and better specs and codebases

...r the organizers nor other participants will tell you to work on something specific. ...t X, or want to implement a certain feature in your client and know that a specific developer knows a thing or two about that, you can look in the particip

...t almost inevitably, I've moved to being much more reactive - dealing with specifications as they arrive, and trying to seek out problems and issues in the The vote tallies don't really show it, but I suspect I've voted against more XEPs than any other member - I'd like to think thi

* Migration is done through presence stanzas, so only online clients get the specific payload, other get a roster push * Daniel volunteers to specify the tombstoning for IBR

...ts of channels and quickly reynchronise messages when coming back online (especially nice in a mobile environment). This project is to build a gateway so t ** Understanding of XMPP messaging, MAM, PubSub and MUC specs

* Spec bugs: ==== Request specific identity ====

...ntation on XMPP, SASL or DIGEST-MD5. If you're in doubt, read the relevant specs. This document assumes that you'll never want to use the channel integrity ...pt to authenticate into. If not present, the client should ask the user to specify a realm.

Usual way to prevent them from spamming was to inspect messages (e.g. links, message too large etc.). ...of checking message contents, we checked whether messages conformed to the spec, for example some messages had typing errors, or MUC messages were sent to

...ns should we rather not depend on it? Yes we should put new rules in a new spec.... ...that are mandatory for government bodies to adhere to when they want to do specific things.

### Specification Spec a component (or SIMS?) To expose rich HTTP links to clients (Link Purple, p

...itecture and a timeline. Rene will also be available for client and server specific code questions. Additionally there is an active buddycloud dev chat-roo ...her applications to enable searching and notifications based on content or specific changes to that content.

...rd to the mechanisms the involved protocols provide. From a pure "what the specification describes" pont-of-view, an ideal solution would possibly be to ...ultimately, the entity possibly also wants to verify if setting has been respected and became effective.

...port is a big project, it probably makes more sense to develop a specific aspect of Jingle support, such as the file transfer content type or a particular ...0136]. A SoC project could add support for message archiving to a client (especially a web client) or a server.

* '''Summary''': Implement all aspects of keeping conversation history, both local and remote. * '''Summary''': Implement social aspects in user profiles