Hello everyone,
since my merge requests at
https://gitorious.org/xmpp/xmpp/merge_requests got unnoticed, I was told
to use the standards ML instead.
As my mail relay is currently broken I can't use git send-mail, so
please excuse me simply adding the patches inline.
Regarding #2 roominfo_pubsub
On 1 Sep 2014, at 08:47, Florian Schmaus f...@geekplace.eu wrote:
since my merge requests at
https://gitorious.org/xmpp/xmpp/merge_requests got unnoticed, I was told
to use the standards ML instead.
The editor team are currently working on a git based workflow which should make
this sort of
Hi,
I'm currently looking at our official Wiki (https://wiki.xmpp.org/) and
there's a couple of things that need to be cleaned.
On the main page, the XMPP technologies panel :
- The Client/Server list in https://wiki.xmpp.org/web/Tech_pages/BOSH
need to be updated (last change 2010)
- Same
I'd like to also point out that the SSL certificate is not valid for
the host name wiki.xmpp.org, thus leading to browser certificate
errors.
Regards
On Mon, Sep 1, 2014 at 4:06 PM, edhelas edhe...@movim.eu wrote:
Hi,
I'm currently looking at our official Wiki (https://wiki.xmpp.org/) and
Hi,
I appreciate the idea to introduce an issue tracker for XEPs (like Jira).
Reason: I (like many others) have raised several issues on this mailing list,
most of them only minor ones like errors in XML Schemas, errors in examples,
other inconsistencies or mere typos. But afaik none of them
Mon, 1 Sep 2014 19:08:22 +0200
Christian Schudt christian.sch...@gmx.de wrote:
Hi,
I appreciate the idea to introduce an issue tracker for XEPs (like
Jira).
It would be way much easier to move XEPs to github and use the
corresponding github's bug tracker.
Yes I was just thinking of Github too.
The pull request feature is also really nice for :
- Fixing minor issues (typo, english mistake…)
- Proposing improvements for the XEP (changes that require major
version update). Then we can decide that for such request we talk about
it during the
Whilst I agree with you entirely (we could also use Travis to test patches
are valid and publish / updated the website) I believe there are some
potential legal issues that have come up previously.
I *think* the latest gitlab has public repositories but this does not allow
for the fork + pull
On 1 September 2014 20:31, edhelas edhe...@movim.eu wrote:
I didn't get exactly what legal issue we are facing here ? Like the fact
that Github will own the sourcecode ? We can, maybe, look for our own
tracker system like Gitlab yes :)
Maybe we can talk about that during the next summit ?
On 01.09.2014 19:25, Evgeny Khramtsov wrote:
Mon, 1 Sep 2014 19:08:22 +0200
Christian Schudt christian.sch...@gmx.de wrote:
Hi,
I appreciate the idea to introduce an issue tracker for XEPs (like
Jira).
It would be way much easier to move XEPs to github and use the
corresponding
Ok I understand, but there's a couple of opensource Github clones
that we can deploy on one of our servers I think, no ?
On lun., sept. 1, 2014 at 10:08 , Kurt Zeilenga
kurt.zeile...@isode.com wrote:
On Sep 1, 2014, at 12:43 PM, Dave Cridland d...@cridland.net wrote:
On 1 September 2014
Mon, 01 Sep 2014 21:57:42 +0200
Florian Schmaus f...@geekplace.eu wrote:
On 01.09.2014 19:25, Evgeny Khramtsov wrote:
Mon, 1 Sep 2014 19:08:22 +0200
Christian Schudt christian.sch...@gmx.de wrote:
Hi,
I appreciate the idea to introduce an issue tracker for XEPs (like
Jira).
Mon, 1 Sep 2014 19:03:49 +0100
Steven Lloyd Watkin ll...@evilprofessor.co.uk wrote:
Whilst I agree with you entirely (we could also use Travis to test
patches are valid and publish / updated the website) I believe there
are some potential legal issues that have come up previously.
I *think*
Mon, 1 Sep 2014 20:43:57 +0100
Dave Cridland d...@cridland.net wrote:
Not all our contributors currently will use github.
Who will not? And why?
Mon, 1 Sep 2014 22:03:43 +0100
Dave Cridland d...@cridland.net wrote:
See Kurt's comment as to one possible reason why.
I use it for both work and pleasure; I'm more in the camp of wanting
to avoid a proprietary outsourced lockin for a core concern. I don't
mind a mirror on github, but then
On 1 September 2014 22:26, Evgeny Khramtsov xramt...@gmail.com wrote:
Mon, 1 Sep 2014 22:03:43 +0100
Dave Cridland d...@cridland.net wrote:
See Kurt's comment as to one possible reason why.
I use it for both work and pleasure; I'm more in the camp of wanting
to avoid a proprietary
16 matches
Mail list logo
