Meeting log: "Meeting Chat" @ Sunday 14th of May 2017

[20:05:30] <Pretorian> Welcome to DCNF monthly meeting, it is 2017-05-14.
[20:05:35] <Pretorian> For simplicity sake, I will be the chairman and Crise has agreed to act as secretary.
[20:05:41] <Pretorian> What we do need is a head count, so just state your names. 
[20:05:42] <Pretorian> Pretorian
[20:05:47] <poy> poy
[20:05:51] <Crise> Crise
[20:05:52] <cologic> cologic
[20:06:00] <Pretorian> All right
[20:06:02] <Pretorian> There's a few items from the last meeting;
[20:06:10] <Pretorian> 1) Fix Markdown file issues (Pretorian)
2) Update DCNF web pages for affiliated projects (Pretorian, Crise)
3) Propose inclusion of affiliated projects (poy)
4) Setting up new affiliate project for information on DC projects (Crise, cologic, Pretorian)
5) Tax papers
[20:06:33] <Pretorian> This is from the meeting on https://www.dcbase.org/files/meetings/2 ... g_chat.log I couldn't recall a meeting in early April
[20:06:42] <Pretorian> (i think we skipped it due to no progress/low attendance)
[20:06:53] <Crise> yeah low attendance
[20:07:01] <Crise> there was a brief discussion though
[20:07:17] <Pretorian> yeah, but I don't remember a formal meeting as such.
[20:07:31] <Pretorian> Any divergent items from above?
[20:07:40] <Pretorian> I don't have anything in my logs.
[20:07:53] <Crise> outside of rescheduling the next meeting as per emails, no
[20:07:59] <Pretorian> All right.
[20:08:00] <Pretorian> We can proceed anyway with above, I don't think things are that changed anyway.
[20:08:12] <Pretorian> Item 1 ) Markdown fix issues
[20:08:24] <Pretorian> This is not done, apologies.
[20:08:47] <Pretorian> It's unlikely I'll be able to do this before 2016-06-09 (back from travels)
[20:09:12] <Pretorian> If anyone else can do it (crise :P) then great, but otherwise I'll have to do it then.
[20:09:17] <Crise> No problem, are the latest links for the files (pastebin) if I recall still good
[20:09:34] <Pretorian> Assuming they haven't expired.
[20:09:48] <Pretorian> I can probably generate the base files (pastebin) again if need be.
[20:09:57] <Pretorian> I just can't place a lot of time on it unfortunately.
[20:10:47] <Crise> ok, I should have some time on the week before 9th of June the latest, if you could make sure I have the base files available somewhere though
[20:10:47] <Pretorian> Unless there's any comment on above, let's move on.
[20:11:07] <poy> 2016-06-09? :) (I routinely do that mistake too. ^^)
[20:11:09] <Pretorian> Yeah, sure, I have only this coming week and up until the Wednesday basically
[20:11:25] <Pretorian> poy: Ah, yeah, I invented time travel by the way :P
[20:11:46] <Pretorian> (Up until 2017!-05-24 basically)
[20:12:00] <Pretorian> So maybe we can verify that in this coming week?
[20:12:38] <Pretorian> Let's move to item 2, it's basically the same anyway...
[20:12:48] <Pretorian> Item 2 hinges on the markdown anyway.
[20:13:11] <Crise> basically yes
[20:13:32] <Pretorian> No progress from my side at least, there is some initial management with the hublist project done, but it's not really the webpages.
[20:14:00] <Crise> yeah, the subdomains should be working for the most part
[20:14:21] <Pretorian> So unless there's some further comment, we can just move on to item 3.
[20:14:32] <Pretorian> 3) Propose inclusion of affiliated projects 
[20:14:34] <Pretorian> poy?
[20:14:44] <Pretorian> This has been dragging for a few meetings :P
[20:15:07] <poy> no progress so far, sorry.
[20:15:27] <Pretorian> All right, let's move on then
[20:15:35] <Crise> well that item is basically valid for anyone to chip in though
[20:15:40] <Pretorian> Yeah, true
[20:15:53] <Crise> if nothing else we can update contribute page with any ideas
[20:15:54] <Pretorian> Should we remove it for the next meeting? As it's a generic point
[20:16:06] <Pretorian> The current page has a few ideas so yeah
[20:16:44] <poy> I do intend to write some and post on forums, so I'd like to keep this item. people won't join in if they aren't at least told they can and what the benefits are / etc.
[20:17:00] <Pretorian> Sounds good
[20:17:20] <Crise> ok, well now the forums are at least up... don't remember when exactly they came back though
[20:17:37] <Pretorian> Without massive errors, too! :P
[20:17:38] <poy> I meant the forums of individual projects I know of. ;)
[20:17:53] <Pretorian> <thumbs up>
[20:17:56] <Crise> :)
[20:18:37] <Pretorian> Let's move on? Feel like we can't say much more here at the moment
[20:18:43] <poy> basically, go nag people and track who has answered / has more questions / etc.
[20:19:02] <Pretorian> (Please stop me if you think I'm moving too fast -- I am in no particular time hurry this evening, I've set aside time for this particular meeting)
[20:19:22] <poy> let's move on. :)
[20:19:24] <cologic> (Efficiency in meetings is always good though.)
[20:19:29] <Pretorian> Item 5) Tax papers
[20:19:45] <Pretorian> Everything's filled in, I just need to physically mail the paper.
[20:20:11] <Pretorian> There's basically no differences compared to last year, just noting the amount of donations and member fees.
[20:20:14] <Pretorian> Everything else is 0
[20:20:47] <Pretorian> I'll see to it that I have it mailed this week.
[20:20:59] <Pretorian> (Deadline is last July I think)
[20:21:35] <Pretorian> Let's move on, I guess
[20:21:37] <Pretorian> That concludes all the items from the previous meeting.
[20:21:45] <Pretorian> Does anyone have any additional items that they thought of?
[20:22:11] <Pretorian> (I have none.)
[20:22:23] <cologic> I completed a version of the forum RSS to JSON scripts.
[20:22:29] <Crise> rescheduling next meeting
[20:22:50] <Pretorian> Öet
[20:22:55] <Pretorian> Let's do schedule last
[20:23:03] <Pretorian> cologic: Oh yeah?
[20:23:32] <cologic> Yeah, I mentioned it a week or two ago (with links to code, example output, etc) to Crise.
[20:23:32] <Pretorian> Published anywhere?
[20:24:06] <cologic> Well, pastebin. I haven't put in any git repo, which I should. It's now specialized enough that it should just go in a pretty purpose-specific (dcbase etc) repo.
[20:24:11] <Crise> yeah it looks as a good starting point, I am guess dufferences between individual projects file organization might cause some friction if we want 100% consistent representation though
[20:24:30] <Crise> (looks like I can't type today)
[20:24:32] <cologic> It's not broadly useful enough to be reused elsewhere with less work than just rewriting something simple.
[20:24:52] <cologic> Due to a bunch of version-parsing, etc.
[20:24:54] <Pretorian> The current dcbase repo should be sufficient in the meantime?
[20:25:00] <cologic> Yeah.
[20:25:14] <Pretorian> Is this something we can have running the current server?
[20:25:27] <cologic> Crise: I did my best to paper over those, but yes, that's an issue.
[20:25:37] <cologic> Yes.
[20:25:40] <Crise> with a cron job, or systemd monitoring it is easy
[20:25:54] <Crise> ie. monitor the adresses file for changes
[20:26:18] <Pretorian> It'd be great if we could have it a) posted here (ignoring Yorhel's bot :P), b) posted on Twitter and c) potentially some sub-site on dcbase.org.
[20:26:39] <cologic> It just outputs JSON which can be used for whatever.
[20:26:51] <Crise> I can do posting on twitter through the website in php I think
[20:27:04] <Crise> twitter should have apis for that sort of stuff I would guess
[20:27:14] <cologic> Yeah. I don't know details, but they do.
[20:27:21] <Pretorian> <https://dev.twitter.com/resources/twitter-libraries>
[20:27:51] <Pretorian> We used Webhooks, right? <https://dev.twitter.com/webhooks>
[20:28:18] <Crise> we can use them I think, but right now they are not required
[20:28:26] <cologic> I don't know, but they look reasonable.
[20:30:12] <Pretorian> So can anyone move forward with hooking them up with Twitter?
[20:31:01] <Crise> just pushing a simple tweet should be simple enough, I need to mess with it anyways for display on dcbase.org so I may as well (not sure under which url it will end up on there though)
[20:31:35] <Pretorian> Well, it'd certainly be cool to have some sort of Twitter aggregate for all DC related Twitter users. 
[20:32:12] <cologic> And, Crise, I just organized the JSON in a way that seemed useful for the use cases described, e.g., I separate in different layers date stamps from versions, because version strings don't sort nicely.
[20:32:22] <cologic> But if there's a better way, that's easy at this point.
[20:32:45] <Crise> yeah, we'll see once I actually put a page together
[20:32:48] <cologic> Thus, one can sort by "version" by sorting by date-stamp-cluster, sort of.
[20:33:04] <cologic> (Which is inferred by looking at at represention of version in the URL)
[20:34:07] <cologic> And, of course, ISO 8601 dates, being the one true date format, sort naturally.
[20:35:03] <Pretorian> Maybe you can coordinate this after the meeting?
[20:35:23] <cologic> Yeah, this is getting a little bit more detailed than this is the right time/place for, agree.
[20:35:32] <Crise> likewise
[20:35:47] <Pretorian> All right
[20:35:54] <Pretorian> Does anyone have any additional items that they thought of?
[20:36:44] <Crise> not at this time, although as a separate note I should have more time to dedicate for the organization starting in June
[20:36:53] <cologic> I have nothing else.
[20:36:57] <Pretorian> June will clear up for me as well
[20:37:02] <Pretorian> (after I get back)
[20:37:07] <Pretorian> Let's schedule next meeting
[20:37:28] <Pretorian> I will not be able to attend on July 4th
[20:37:34] <Pretorian> err
[20:37:40] <Pretorian> June 4th
[20:38:06] <Pretorian> 11th works for me but I won't have done anything of importance by that date.
[20:38:16] <cologic> Either of those works fine for me.
[20:38:49] <poy> same, both are fine here.
[20:38:55] <Crise> should work for me as well, so whatever works best for you Pretorian
[20:39:01] <Pretorian> 11th then
[20:39:07] <cologic> Sounds good.
[20:39:17] <Pretorian> All right. Same time then.
[20:39:29] <Pretorian> Next meeting items;
1) Fix Markdown file issues (Pretorian)
2) Update DCNF web pages for affiliated projects (Pretorian, Crise)
3) Propose inclusion of affiliated projects (poy)
4) Setting up new affiliate project for information on DC projects (Crise, cologic, Pretorian)
5) Tax papers
6) Publishing of RSS feeds in various places (Twitter, website etc) (cologic/Crise)
[20:39:44] <Pretorian> If there's nothing further, that concludes this meeting. Thank you all.