[03:27] <youngbin_> Fallen ilvipero Hello, Sorry for pinging you guys while you might be busy. Just wonder if there any updates on UbuCon Asia sponsorship and merchandises.
[07:26] <Fallen> youngbin: yes, emailing today. I have a draft email waiting for me to complete.
[07:46] <youngbin_> <Fallen> "youngbin: yes, emailing today. I..." <- Thanks a lot for your work, will wait for your mail. :)
[10:45] <Fallen> <arraybolt3> "Fallen: Hey, sorry to be gone so..." <- Hey, I've been swamped lately myself due to some team changes, so no worries. I was just thinking of you yesterday, great coincidence. I have spoken to Daniele, our docs director, and he was saying that the best way to deal with non-community documentation right now is to not touch it. He is building up the capacity to put some structure into it, but this needs some dedicated folks
[10:45] <Fallen> working on it.
[10:46] <Fallen> He also mentioned that having an issue tracker might actually be counter-productive, as it would end up being yet another treasure trove of issues for someone new coming in to triage, and that it would likely make more sense to work on issues piece by piece.
[10:48] <Fallen> Based on that, I think we could also skip the tracker, but instead have a regularly curated list of things to work on. The scope would indeed be documentation about community, so likely from the pages in the appendix of the doc we've been working on.
[10:49] <Fallen> If you have capacity to push forward on this, I think a good next step would be drafting an announcement to bring people to #ubuntu-doc, the mailing list, and get them involved in a few simple tasks.
[14:02] <Fallen> DiogoConstantino: are you here?
[14:08] <Fallen> arraybolt3: The other thing of interest, which I believe we chatted about briefly, was a high level structure for the sidebar of the docs page. This might be a matter of going through the appendix pages and picking out a few relevant pages, categorizing them loosely by their Diataxis group, and figuring out how they connect. From that you can create a bullet point list on what the main structure might look like. 2-3 levels of hierarchy
[14:08] <Fallen> should be sufficient, don't need to get too detailed.
[16:04] <DiogoConstantino> I'm now
[16:05] <DiogoConstantino> just finished work
[16:55] <Fallen> DiogoConstantino: thanks! I emailed instead, if you could check.
[17:55] <DiogoConstantino> I just notived
[17:55] <DiogoConstantino> I just noticed
[17:56] <DiogoConstantino> response sent
[17:59] <DiogoConstantino> too many things happening
[18:44] <Fallen> All good, glad we were able to clear it up :)