KevIt seems there is only two XEPs remaining here: http://xmpp.org/xmpp-protocols/xmpp-extensions/ Link Mauve @ 8:44
That's not many. intosi @ 8:50
It's only the index that's broken. The actual XEPs seem to work just fine. 8:53
Yeah. Link Mauve @ 8:54
stpeterdid I miss anything?
AshI don't think so, unless I missed it all too (which may well be the case!)
m&mshunting bleeding hearts
AshIs that shunting or c… ;)
stpeteryeah, my heart bleeds for the internet
m&mabout 67% of it today
KevI'm assuming everyone in this room has been running around madly for several hours because of this :)
Kevm&m: The XEP index is now allegedly broken.
m&mwell, according to the index, we only have two XEPs
stpeteroh that's a good idea, let's consolidate everything into 2 XEPs
m&myeah yeah yeah
m&mso, it looks like the table is only written by gen.py
m&mI'm not sure what's faster: writing the file by hand, or running gen.py over every XEP
stpeterisn't there all.py?
m&mit doesn't actually call gen.py
stpeterthat invokes gen.py?
m&mit calls xsltproc by hand
m&mand doesn't update the xep table
m&mI think I'll modify all.sh to call gen.py
m&mI would not be confident in my abilities to hand-create that table
m&mit looks like it was there, but commented
m&mbut first I have to delete the existing table, because it appends rather than sully sorts (-:
stpeterthe table is sullied? ;-)
m&mYes. Yes it is!
m&mindex is rebuilding
stpetertoo many XEPs!!
stpeterthank you thank you
m&mthe thirteenth-council page was never created
stpeterm&m ah hrmph
m&mcreating it now
m&mcan someone refresh my memory on how many votes the current council has gone through already?
stpeterm&m let me take a look
stpeterlooks like updates to 156 and 206, and advancement of 152
m&mok, and I'm tracking down the dates of those now, too
m&mjust found 206
stpeterI went to http://xmpp.org/xmpp-protocols/xmpp-extensions/ and ordered by date