[2015-01-08 22:00:38] Hi, and welcome to this first official meeting for the Direct Connect Network Foundation. [2015-01-08 22:00:58] I am the interim supervisor of the meeting until the meeting supervisor has been elected. [2015-01-08 22:01:14] All who are here for today's meeting, please write now with your registered member name. All those who are here agrees on the by-laws. [2015-01-08 22:01:21] Fredrik Ullner / Pretorian [2015-01-08 22:01:34] cologic [2015-01-08 22:01:35] poy [2015-01-08 22:01:39] eMTee [2015-01-08 22:02:22] The first order of business is electing a meeting supervisor and a meeting secretary. Those who wishes to be the meeting supervisor or wish to nominate someone, write now a name. [2015-01-08 22:02:28] I nominate myself, Pretorian. [2015-01-08 22:02:36] Fredrik Ullner / Pretorian [2015-01-08 22:03:06] Frederisk Ullner / Pretorian [2015-01-08 22:03:17] Pretorian [2015-01-08 22:03:20] There have been one nomination, for Pretorian to be voted supervisor for this meeting. [2015-01-08 22:03:21] *Frederik Ullner [2015-01-08 22:03:27] *still wrong :P [2015-01-08 22:03:29] *Fredrik. [2015-01-08 22:03:32] There. :p [2015-01-08 22:03:38] I'll edit it out later, I guess. :p [2015-01-08 22:03:50] you mean you will "adjust". [2015-01-08 22:03:55] Quite. [2015-01-08 22:04:04] The second order of business is electing a meeting secretary. Those who wishes to be the meeting secretary or wish to nominate someone, write now a name. [2015-01-08 22:04:08] I nominate myself, Pretorian. [2015-01-08 22:04:16] Fredrik Ullner / Pretorian [2015-01-08 22:04:18] Pretorian [2015-01-08 22:04:21] Pretorian [2015-01-08 22:04:25] There have been one nomination, for Pretorian to be voted secretary for this meeting. [2015-01-08 22:04:48] The supervisor for this meeting is Pretorian. The secretary for this meeting is Pretorian. [2015-01-08 22:05:10] I have now been elected supervisor, and will continue on with the order of business as set forth by the by-laws of DCNF. [2015-01-08 22:06:12] Second item is establishing voting length in time for each type of vote during the meeting. Specify now a voting length. If all members vote the same before the time elapse, thereby shortening the time for a vote. [2015-01-08 22:06:23] I nominate 2 minutes for each vote. [2015-01-08 22:06:40] yes for 2 minutes for each vote. [2015-01-08 22:07:01] Yes [2015-01-08 22:07:01] I nominate 5 minutes for each vote. [2015-01-08 22:07:18] 3 votes for "2 minutes", 1 vote for "5 minutes". [2015-01-08 22:07:26] poy: Not yet. :P [2015-01-08 22:07:30] -_- [2015-01-08 22:07:45] But yes, 3 votes for 2 minutes. 2 minutes shall be used henceforth in this meeting. [2015-01-08 22:07:45] Presumably, one can have a 2-minute vote for a 5-minute vote. [2015-01-08 22:08:30] Item 3 in the by-laws: choosing vote counter and meeting protocol adjuster. Those who wishes to be the meeting vote counter or wish to nominate someone, write now a name. [2015-01-08 22:08:32] poy [2015-01-08 22:08:44] poy [2015-01-08 22:08:47] poy [2015-01-08 22:08:56] myself, poy. [2015-01-08 22:09:15] poy is eleected vote counter with 4 votes. poy shall for the continuation of this meeting count all votes. [2015-01-08 22:09:28] Those who wishes to be the meeting protocol adjuster or wish to nominate someone, write now a name. [2015-01-08 22:09:31] cologic [2015-01-08 22:09:35] cologic [2015-01-08 22:09:36] cologic [2015-01-08 22:09:37] cologic [2015-01-08 22:09:42] 4 votes for "cologic". [2015-01-08 22:09:53] cologic is elected meeting protocol adjuster. [2015-01-08 22:10:18] Item 4 in the by-laws: has the meeting been announced correctly and fairly? [2015-01-08 22:10:21] yes [2015-01-08 22:10:24] yes [2015-01-08 22:10:24] yes [2015-01-08 22:10:28] yes [2015-01-08 22:10:33] 4 votes for "yes". [2015-01-08 22:11:11] Item 5 in the by-laws: Meeting items shall be established here. State your intended meeting items that will discussed and possibly voted on in item 15. [2015-01-08 22:11:23] Only state the "headline" of your meeting items. [2015-01-08 22:11:33] Numbered for an easier reference: * poy-01) Content on the DCNF website * poy-02) Mailing list for the DCNF * poy-03) Activities of the DCNF (blog, "social media" presence...) * poy-04) Acceptance of supported projects (type (programs, protocols...), workflow...) * poy-05) Separation between the foundation and supported projects (legal, in particular) * poy-06) Hosting DC hub lists * poy-07) Hosting DC support hubs for supported projects * poy-08) Hosting code repositories for supported projects * poy-09) Hosting websites for supported projects * poy-10) Hosting mailing lists for supported projects * poy-11) Hosting bug trackers for supported projects * poy-12) Buying the services of a network administrator * poy-13) Using external services to proxy DCNF / supported projects data * poy-14) Legal structure to help the DCNF * poy-15) Legal structure to help supported projects * poy-16) Ways to find new members * emtee-01) Involvement of the DCNF in DC protocols * emtee-02) Buying the services of developers * emtee-03) Mobile/web-based DC-related programs * emtee-04) Contacting well-known tech bloggers * emtee-05) DC and businesses [2015-01-08 22:12:17] I will allow five minutes for additional thought, or if you wish to continue to next item, just write "continue" [2015-01-08 22:12:23] continue [2015-01-08 22:12:30] continue [2015-01-08 22:12:31] continue [2015-01-08 22:13:17] * poy-17) Hub for the DCNF [2015-01-08 22:13:19] continue [2015-01-08 22:13:29] Count please :) [2015-01-08 22:13:35] 4 votes for "continue". [2015-01-08 22:14:12] 22 items have been specified for further discussion. [2015-01-08 22:14:43] Item 6 in the by-laws: this meeting is the first established organizational meeting. Therefore, there is no proceeding year's board or financial state. This means we will continue on to the next item. [2015-01-08 22:15:08] Item 7 in the by-laws: this meeting is the first established organizational meeting. Therefore, there is no proceeding auditors or financial state. This means we will continue on to the next item. [2015-01-08 22:15:20] Item 8 in the by-laws: this meeting is the first established organizational meeting. Therefore, there is no proceeding year's board. This means we will continue on to the next item. [2015-01-08 22:16:08] Item 9 in the by-laws: We will now decide on the member fee set forth by the organization. State your proposals for amount in Euros €. We will have a vote for each nomination. If only one is nominated, it will be selected. [2015-01-08 22:16:19] 10 € per year per member. [2015-01-08 22:16:33] 10 € per year per member. [2015-01-08 22:17:05] 10 € per year per member. [2015-01-08 22:17:16] 10 € per year per member. [2015-01-08 22:17:26] 4 votes for "10 € per year per member". [2015-01-08 22:17:49] 10 € per year per person will be the member fee. If a person wishes to donate more, they can do so at their free will. [2015-01-08 22:18:47] Item 10 in the by-laws: this meeting is the first established organizational meeting. Therefore, there is no proceeding year's board to show a plan. This means we will continue on to the next item. [2015-01-08 22:19:34] Item 11 in the by-laws: those who wish to be part of the board or if you wish to nominate someone else, please write a name for nomination. Each person nominated will have their own voting period. [2015-01-08 22:19:38] Pretorian [2015-01-08 22:19:48] Just the nominations now* [2015-01-08 22:19:59] poy [2015-01-08 22:20:03] cologic [2015-01-08 22:21:46] Pretorian, poy and cologic are nominated [2015-01-08 22:21:50] If you wish for Pretorian to be elected in the board, write his name or yes or +1. If you do not, write -1 or no. [2015-01-08 22:21:53] +1 [2015-01-08 22:21:57] +1 [2015-01-08 22:21:58] +1 [2015-01-08 22:22:00] +1 [2015-01-08 22:22:09] 4 votes for Pretorian to be in the board. [2015-01-08 22:22:18] Pretorian is elected to the board. [2015-01-08 22:22:20] If you wish for cologic to be elected in the board, write his name or yes or +1. If you do not, write -1 or no. [2015-01-08 22:22:24] +1 [2015-01-08 22:22:24] +1 [2015-01-08 22:22:26] +1 [2015-01-08 22:22:38] +1 [2015-01-08 22:22:39] 4 votes for cologic to be in the board. [2015-01-08 22:22:41] cologic is elected to the board. [2015-01-08 22:22:48] If you wish for poy to be elected in the board, write his name or yes or +1. If you do not, write -1 or no. [2015-01-08 22:22:50] +1 [2015-01-08 22:22:51] +1 [2015-01-08 22:22:52] +1 [2015-01-08 22:22:53] +1 [2015-01-08 22:22:58] 4 votes for poy to be in the board. [2015-01-08 22:23:00] poy is elected to the board. [2015-01-08 22:23:14] The board is now complete and consist of Pretorian, poy and cologic. [2015-01-08 22:23:27] Item 13 in the by-laws: those who wish to be part of the stand-in board or if you wish to nominate someone else, please write a name for nomination. Each person nominated will have their own voting period. [2015-01-08 22:23:30] eMTee [2015-01-08 22:23:36] eMTee [2015-01-08 22:23:40] eMTee [2015-01-08 22:23:47] eMTee [2015-01-08 22:23:51] 4 votes for eMTee to be part of the stand-in board. [2015-01-08 22:24:05] eMTee is elected to the stand-in board. [2015-01-08 22:24:12] The stand-in board is now complete and consist of eMTee. [2015-01-08 22:24:56] Item 15 in the by-laws: I will now go over each item in the proposals set in 5 in the order they were brought up. The person that brought it up has the floor. [2015-01-08 22:25:15] poy brought up item 1: "Content on the DCNF website" [2015-01-08 22:25:37] Let's discuss what is hosted on the DCNF website. [2015-01-08 22:26:40] I shall just interject, if you wish to have an item to be an open discussion, please state as such. [2015-01-08 22:27:14] Currently the DCNF website is a forum. Presumably, the intention would be that the forum not constitute the entirety of the site, modulo archive and builds. [2015-01-08 22:27:15] (otherwise, people should wait until the person that has the word has given approval after their opening monologue/statement) [2015-01-08 22:27:23] I think it should contain a blog, a forum, a DC-related wiki, DC usage tips, an appealing section for people who don't know about DC. [2015-01-08 22:27:40] (Pretorian: ah. Had been unclear myself.) [2015-01-08 22:27:44] I approve of further discussion. [2015-01-08 22:27:50] Great. :) [2015-01-08 22:28:19] I wish this item to receive an open discussion. [2015-01-08 22:28:23] I agree with poy, although the question is a) who will be the maintainer and b) why we would need each resource. E.g., the wiki was kind of pointless since no one used it before. [2015-01-08 22:28:56] poy: how would this blog relate to dcpp.wordpress.com? The DCNF probably should not be too partisan towards a particular client, so it could not literally be the same blog, but at least from my end, much of the content I've put on the DC++ blog isn't properly about DC++ to begin with. [2015-01-08 22:29:24] The blog could be focused on activities of the DCNF itself at first. [2015-01-08 22:29:25] cologic: For what it's worth, the naming scheme was Gargoyle's doing. [2015-01-08 22:29:32] (dcpp.wordpress.com) [2015-01-08 22:29:50] poy: Do you suggest a new blog to be started (at wordpress)? [2015-01-08 22:30:04] Similarly, the wiki could host DCNF-related content at first (member list, supported projects, meeting summaries...). [2015-01-08 22:30:17] I agree that a wiki would be useful, and it, of course, used to exist. I periodically run across links to ADCPortal's wiki and similar sites with annotated, categorized lists of clients, hubs, and similar information to which it would be useful to be able to link and point people. [2015-01-08 22:30:34] I'd prefer a blog be hosted on the DCNF website (wordpress can be relatively easy self-hosted). [2015-01-08 22:30:42] relatively easily* [2015-01-08 22:30:57] poy: I think that costs money, though. (Just pointing it out. [2015-01-08 22:31:27] Pretorian: I used the wiki, occasionally, as a reference. I never ended up making for a good discussion forum, I'd acknowledge. [2015-01-08 22:31:31] We will have money. I wouldn't be asking so much if the DCNF wasn't there. [2015-01-08 22:31:46] *It never ended up [2015-01-08 22:31:50] poy: Fair enough. If so, I agree. [2015-01-08 22:32:14] I think we will need to appoint a person to be the maintainer. [2015-01-08 22:32:28] (appoint/pay a maintainer) [2015-01-08 22:33:15] That could be added into point poy-12. [2015-01-08 22:33:18] So the DCNF website should focus solely on DCNF (and projects it supports etc)? [2015-01-08 22:33:34] Or, at least primarily. [2015-01-08 22:34:21] That is why I was initially thinking of a separate domain name. But dcbase could do that at first and expand later when we fill confident enough. [2015-01-08 22:35:16] dcbase can simply grow from the ADC-centric forum to DCNF. [2015-01-08 22:35:33] (which was my initial idea with dcbase anyway) [2015-01-08 22:35:37] Any other content anyone can think could be added to the DCNF website? [2015-01-08 22:36:06] I think this is pretty clear/good: [tor:22:27:23] I think it should contain a blog, a forum, a DC-related wiki, DC usage tips, an appealing section for people who don't know about DC. [2015-01-08 22:36:46] Yes, I'd support all of those things. [2015-01-08 22:36:54] If poy feels item 1 has been addressed satisfactory, we will move on to item 2: Mailing list for the DCNF [2015-01-08 22:37:29] I feel item 1 has received a satisfactory discussion. [2015-01-08 22:37:50] I want item 2 to be an open discussion. [2015-01-08 22:38:07] What purpose does a mailing list have, compared to a forum? [2015-01-08 22:38:28] Beyond the availability of having it offline I suppose (getting content as a mail). [2015-01-08 22:38:30] None. [2015-01-08 22:38:42] Do we need a mailing list if we have a form? [2015-01-08 22:38:49] Mailing lists are thing of the past. What are its advantages to modern counterparts like forums or social media? [2015-01-08 22:39:07] I see no need for the DCNF to have a mailing list. [2015-01-08 22:39:16] I agree. [2015-01-08 22:39:18] Agreed [2015-01-08 22:39:22] Agree. [2015-01-08 22:39:28] I feel item 2 has received a satisfactory discussion. [2015-01-08 22:39:43] We will move on to item 3: Activities of the DCNF (blog, "social media" presence...) [2015-01-08 22:39:49] I want an open discussion for item 3. [2015-01-08 22:40:19] There is www.reddit.com/r/directconnect and dcbase at Twitter and youtube/directconnectnetwork. [2015-01-08 22:40:36] Should there be an additional channel/twitterpage/subreddit for DCNF? [2015-01-08 22:40:55] Good. facebook and Google+ are missing. [2015-01-08 22:41:23] First of all, I think the youtube account shall be "given" to the organization/board. It is currently in my "possession". [2015-01-08 22:41:59] Pretorian: given relative dearth of content, a separate subreddit, at least, might spread things too thinly. I don't have a strong opinion, however. [2015-01-08 22:41:59] Should we both have Facebook and G+? [2015-01-08 22:42:12] eMTee: Details on the social media activities you had in mind? [2015-01-08 22:42:31] I personally don't use G+, and I barely use Facebook. [2015-01-08 22:42:51] (I _have_ G+ since I have a Gmail but beyond that) [2015-01-08 22:42:59] In these sectors, sometimes the more the merrier, even if content is being repeated from one social media to the other. [2015-01-08 22:43:05] I don't use either. I have no position on this, as a result. [2015-01-08 22:43:11] (G+ or Facebook.) [2015-01-08 22:43:40] poy: I merely mentioned it as today's necessity. I don't use social media myself so I can't go further to propose details. [2015-01-08 22:43:54] The accounts Pretorian listed are enough by me. [2015-01-08 22:44:15] poy: So you mean Twitter/Youtube/Reddit is sufficient? [2015-01-08 22:44:18] I think if you want to effectively promote something you can't miss social media these days. [2015-01-08 22:44:45] Yes, sounds like enough. [2015-01-08 22:44:49] Activities of the DCNF might also include participation in boards / websites / social media places the DCNF itself is not in control of. Thoughts? [2015-01-08 22:44:51] the problem with G+/FB is that perhaps a few people (you guys) don't want to divulge your real names so... [2015-01-08 22:45:27] Yes, that is fine for me, assuming DCNF is correctly represented. [2015-01-08 22:45:41] Who can represent the DCNF in these places? [2015-01-08 22:45:56] At its heart, the board, I suppose. [2015-01-08 22:46:00] (and stand-in) [2015-01-08 22:46:15] That is the only "official" DCNF support/presence. [2015-01-08 22:46:16] Pretorian: my understanding is that the DCNF, as an organization, could have a page separately from any individual (non-purely-legal) person. [2015-01-08 22:46:29] I don't know the mechanics of how that functions, however. [2015-01-08 22:46:47] cologic: Yes, but you still need to link/attach yourself to that page so anyone who is part of the page can see each other. I.e., I would see you. [2015-01-08 22:47:01] But sure, if people don't link/attach themselves, that's possible. [2015-01-08 22:47:29] You just can't really post/do anything on it, unless you login with a separate "FB DCNF account". [2015-01-08 22:47:43] (similarly as the twitter page) [2015-01-08 22:48:03] I'm fine with having things on FB, I am only concerned with maintenance. [2015-01-08 22:48:25] And I'm not afraid of divulging my name, so that's kind of up to you guys. [2015-01-08 22:49:18] So we are OK with the possibility of having Facebook / Google+ / [other] accounts in the future, should the need arise. [2015-01-08 22:49:22] Yes [2015-01-08 22:49:33] I feel item 3 has been discussed enough. [2015-01-08 22:49:38] We will move on to item 4: Acceptance of supported projects (type (programs, protocols...), workflow...) [2015-01-08 22:49:44] I want an open discussion for item 4. [2015-01-08 22:49:56] What type of "acceptance" did you have in mind? [2015-01-08 22:50:43] By "workflow", I mean "process" by which an entity can submit a project to be supported by the DCNF and who / how it would be accepted. [2015-01-08 22:50:55] Also, who can submit. [2015-01-08 22:51:02] What does it mean that a project is "supported by the DCNF"? [2015-01-08 22:52:04] The project will benefit from any service provided by the DCNF to its supported projects; details are to be discussed in future points. [2015-01-08 22:52:22] Fair enough. Who shall draw up the process/workflow? [2015-01-08 22:52:43] To be discussed later on or done by the board? [2015-01-08 22:53:00] I think it should be decided here. [2015-01-08 22:53:14] Now, or at a DCNF meeting in the future? [2015-01-08 22:54:00] (and by "DCNF meeting", I don't mean the one in one year) [2015-01-08 22:54:01] I'd prefer we decided now, unless some people want time to think about it? [2015-01-08 22:54:47] I think it is soemthing to be considered, I believe it is quite complex on the steps unless they are very broad. Do you have any suggested steps/actions we/users can take otherwise? [2015-01-08 22:55:29] I say any member paying the minimum fee can submit any project he fancies. The board will then decide / vote whether said project qualifies to be supported by the DCNF. [2015-01-08 22:55:42] Fair enough, +1. [2015-01-08 22:55:47] +1 [2015-01-08 22:55:53] The specifics of how a project can qualify are more complex and can be established later on. [2015-01-08 22:56:03] Agreed [2015-01-08 22:56:18] +1 [2015-01-08 22:56:24] +1 [2015-01-08 22:56:42] 4 votes for "Any member paying the minimum fee can submit any project he fancies. The board will then decide / vote whether said project qualifies to be supported by the DCNF.". [2015-01-08 22:56:54] We will move on to item 5: Separation between the foundation and supported projects (legal, in particular) [2015-01-08 22:57:35] As I can envision some members of the DCNF will also manage DCNF-supported projects, I wanted some talk about the separation. [2015-01-08 22:58:03] Organizational separation: voting powers about one's own projects, especially when one is member of the board. [2015-01-08 22:58:45] Legal separation: making sure the DCNF has no trouble should one of its supported projects legally misbehave (or vice-versa). [2015-01-08 22:58:52] Feel free to discuss item 5. [2015-01-08 22:59:16] Organizational separation: Does a board member not have a vote if it's a project they own? [2015-01-08 22:59:42] (own/manage) [2015-01-08 23:00:06] I don't have a strong position on this, but would observe it creates weird incentive structures to disallow people from voting that way. [2015-01-08 23:00:42] I am fine with lack of vote if there is at least two members in the board that do not own or manage the project. [2015-01-08 23:01:08] It's more likely to create ties, if nothing else. [2015-01-08 23:01:23] Legal separation: Just general guess: perhaps a simple disclaimer/use notice would work. [2015-01-08 23:01:38] Terms of use [2015-01-08 23:01:43] +1 for "no right to vote when a board member is also a manager of a supported project". [2015-01-08 23:02:04] Fair enough, +1 [2015-01-08 23:02:09] Properly addressing legal separation would require actual legal knowledge, but I'm not sure under what circumstances the DCNF would acquire presumptive responsibility to start with. [2015-01-08 23:02:33] cologic: If we have simply a terms of use, then perhaps one can reference that. [2015-01-08 23:03:00] +1 as I don't object [2015-01-08 23:03:00] I am also unsure how we can provide an actual legal separation. [2015-01-08 23:03:33] A board member shall also not have a vote if the project misbehaves. [2015-01-08 23:03:45] (i.e., it applies both for inclusion and exclusion of the supported project) [2015-01-08 23:04:11] I mostly had in mind the "list of things P2P devs cannot do" (such as helping a person download a movie). Can DCNF members do that without putting DCNF-supported projects in danger? Can DCNF *board* members do that without putting DCNF-supported projects in danger? [2015-01-08 23:04:41] As long as we abide by that list by EFF, I'd say we're good. [2015-01-08 23:04:43] 3 votes for "no right to vote when a board member is also a manager of a supported project". [2015-01-08 23:04:47] poy: I suspect that's a more subtle legal question than anyone here can answer. [2015-01-08 23:04:53] Though, a good/worthwhile one. [2015-01-08 23:05:37] Side question: Can the DCNF accept projects the managers of which we suspect might have infringed on that EFF recommendation list? [2015-01-08 23:06:10] Yes, on the presumption that have fixed their errors. [2015-01-08 23:06:13] I think the secretary should compile these questions so we can submit them to more knowledgeable people. [2015-01-08 23:06:24] Subsumed into the judgements of people accepting or not each individual project, presumably. [2015-01-08 23:06:41] Though, I, personally, would be wary. [2015-01-08 23:07:05] I propose that the board should file these questions to the EFF, they have a mailing list for questions. [2015-01-08 23:07:25] This is of importance for several projects I am thinking of proposing for inclusion into the list of DCNF-supported projects. [2015-01-08 23:07:51] +1 board, -1 secretary [2015-01-08 23:08:05] +1 board [2015-01-08 23:08:25] (or, perhaps I can't do that here, since we have a mutual exclusivity. oh, well, I believe my point comes across) [2015-01-08 23:08:45] Ah, I'm not sure precisely what's +1/-1'd here? [2015-01-08 23:08:57] [tor:23:07:05] I propose that the board should file these questions to the EFF, they have a mailing list for questions. [2015-01-08 23:09:00] vs secretary [2015-01-08 23:09:03] +1 board [2015-01-08 23:09:36] 3 votes for the board to compile a list of questions related to the legal separation between the DCNF and its supported projects and send it to the EFF. [2015-01-08 23:09:46] I feel this point has been discussed enough. [2015-01-08 23:09:50] We will move on to item 6: Hosting DC hub lists [2015-01-08 23:10:17] This point also has some legal concerns (re item 5). [2015-01-08 23:10:42] I say the DCNF should host one global hub list, and possibly more later on. [2015-01-08 23:10:45] Please discuss. [2015-01-08 23:10:59] +1 relatively strongly. I view this as an existential issue for DC. [2015-01-08 23:11:15] If DCNF is responsible for a hub list, it must abide by EFF's suggestions and be prepared to filter the list [2015-01-08 23:11:39] Host it on dcbase.org or on a separate website? (the separate website could provide comments / rating, etc.) [2015-01-08 23:12:22] Pretorian: Maybe not; that's also a question to be asked to the EFF. [2015-01-08 23:12:27] I believe DCNF shall NOT be the host, the hub list shall be a supporting project. In that way, it is hopefully sufficiently separated legally and organizationally. [2015-01-08 23:12:43] +1 [2015-01-08 23:12:46] Ah, I might revise my vote in light of that possiblity. [2015-01-08 23:12:49] +1 for hub lists behing supported projects by the DCNF [2015-01-08 23:12:53] +1 [2015-01-08 23:12:59] 4 votes for hub lists behing supported projects by the DCNF. [2015-01-08 23:13:06] I feel this has been discussed enough. [2015-01-08 23:13:15] We might explore that one of the old hublist domains are free and use that. [2015-01-08 23:13:16] e will move on to item 7: Hosting DC support hubs for supported projects [2015-01-08 23:13:49] This is the first service I propose the DCNF offers to projects it supports. [2015-01-08 23:13:58] eMTee: I think we can discuss that in an additional item later on. [2015-01-08 23:14:01] Please discuss. [2015-01-08 23:14:02] absultely necessary, it's a place when users can ask for problems fastly and without registration [2015-01-08 23:14:13] +1 [2015-01-08 23:14:26] +1 [2015-01-08 23:14:34] +1 [2015-01-08 23:14:50] I think this hub should be the very first hub that users visit (in most clients, hard coded in a "go to support hub" button) [2015-01-08 23:14:54] 4 votes for the DCNF to provide support hubs to its supported projects. [2015-01-08 23:15:35] If the hubs are hosted by the DCNF, legal concerns may also appear here. Chat-only (no file transfer) hubs? [2015-01-08 23:16:03] even propose to add it as a default hub to open for clients that has possibility to open (hub) windows specified in the settings [2015-01-08 23:16:10] +1, with one note: there should be certain users that you _CAN_ download from that are bots. To show/handle connecitivty. [2015-01-08 23:16:23] +1 to chat-only btw [2015-01-08 23:16:40] +1 [2015-01-08 23:16:46] The bots should have like a single file or guide etc. [2015-01-08 23:16:47] +1 for chat-only (except connectivity testing bots) support hubs. [2015-01-08 23:17:02] +1 to chat only except testing bots. [2015-01-08 23:17:08] 4 votes for chat-only (except connectivity testing bots) support hubs. [2015-01-08 23:17:21] We will move on to item 8: Hosting code repositories for supported projects [2015-01-08 23:17:30] Please discuss. [2015-01-08 23:17:35] (Assuming poy was done with 7.) [2015-01-08 23:17:46] +1 [2015-01-08 23:17:47] I agree, allow code repositories. [2015-01-08 23:18:05] if they need it altough there are great free and reliable places on the internet to do so. [2015-01-08 23:18:18] We need to decide which type of repository git/svn and web? [2015-01-08 23:18:36] Sure, could be optional. [2015-01-08 23:19:02] I think the details of the repository type can be discussed later. [2015-01-08 23:19:07] My generic concern with , too, even though I've +1'd them, is that DC has been bad at infrastructure. I'm willing to try to have the DCNF try again, certainly. [2015-01-08 23:19:22] But, yes, ultimately code is what runs DC. +1 [2015-01-08 23:19:34] I propose that the board decides the repository details. [2015-01-08 23:19:41] That is a concern for me too but I see little point in having a foundation if it can't provide that. [2015-01-08 23:19:50] poy: I agree. [2015-01-08 23:20:09] 4 votes for code repositories. [2015-01-08 23:20:48] This has been discussed enough. [2015-01-08 23:20:54] We will move on to item 9: Hosting websites for supported projects [2015-01-08 23:21:00] +1 [2015-01-08 23:21:13] Same caveats+support as before. [2015-01-08 23:21:15] +1 [2015-01-08 23:21:23] Depends on a) the type of website and b) how this shall be maintained? [2015-01-08 23:21:42] Shall we allow a SF-style http? [2015-01-08 23:21:44] Hmm... Only static pages? [2015-01-08 23:21:54] Who can upload/maintain them? [2015-01-08 23:22:13] This won't be easy to set up. [2015-01-08 23:22:40] Exactly, that is my concern. [2015-01-08 23:22:50] A repository is easy, a website is harder. [2015-01-08 23:23:09] I will +1 with restrictions on set up/maintenance. [2015-01-08 23:24:02] I change my vote to a "no" ; to be decided later on. [2015-01-08 23:24:37] 2 votes for websites (with restrictions) ; 1 vote against. [2015-01-08 23:24:41] Let's move on. [2015-01-08 23:24:44] We will move on to item 10: Hosting mailing lists for supported projects [2015-01-08 23:24:53] -1 [2015-01-08 23:24:56] -1 [2015-01-08 23:24:57] -1 [2015-01-08 23:25:01] -1 [2015-01-08 23:25:07] 4 votes against mailing lists. [2015-01-08 23:25:13] We will move on to item 11: Hosting bug trackers for supported projects [2015-01-08 23:25:41] There are projects that provide the full package (redmine, bugzilla, iirc) - can be relatively easy to set up. [2015-01-08 23:25:42] +1 [2015-01-08 23:26:04] It's definitely a more constrained problem space than "websites" [2015-01-08 23:26:11] I am unsure, I will abstain. [2015-01-08 23:26:17] And it makes sense to go along with code repositories. [2015-01-08 23:26:37] If there are two "yes" votes, I will vote "yes" as well. [2015-01-08 23:27:07] +1 as part of package. As poy said: the code should be linked with bug trackers. [2015-01-08 23:27:13] +1 then [2015-01-08 23:27:17] no vote just like for the earlier two. I can't decide [2015-01-08 23:27:29] I'd be both/neither [2015-01-08 23:27:35] 3 votes for bug trackers. [2015-01-08 23:27:37] Yes, both/neither [2015-01-08 23:27:44] We will move on to item 12: Buying the services of a network administrator [2015-01-08 23:27:53] Discuss. [2015-01-08 23:28:19] We will definitely need one to provide what we have voted for so far. I don't know the prices. [2015-01-08 23:28:23] Unless we're lucky we won't find suitable people doing it for free. [2015-01-08 23:28:29] In principle, can't be worse than now. No idea of how this works financially, though. [2015-01-08 23:28:41] I believe the organization has other more highly prioritized items that it should spend money on, but if there is room, fincancially, yes. [2015-01-08 23:28:55] Such as? [2015-01-08 23:29:06] Yeah what are those? [2015-01-08 23:29:10] Domain, webserver for starters. [2015-01-08 23:29:59] How much do they cost, roughly? [2015-01-08 23:30:05] To a large extent, I view the DCNF as a conduit for money for exactly this sort of thing, again, in principle. Paying for and coordinating interactions with external services is one of the major weak points today. [2015-01-08 23:30:12] Roughly 200 € per year. [2015-01-08 23:30:16] I think, IIRC. [2015-01-08 23:30:44] What's happened so far is that one person has decided to do it, but then one gets debacles such as the fun with Toast. [2015-01-08 23:30:46] Domain is "just" 7.9 €. [2015-01-08 23:31:48] Those two are the primary expenses that the organization has. After that is up for discussion. [2015-01-08 23:31:59] Someone whose job is solely to do that (for many different clients) and has no interest in DC would be great. Any dev can then set up the code repository / bug tracker parts. [2015-01-08 23:32:14] We can find/ask people who provided such working administered server for us for free before if he wants to do it for money? [2015-01-08 23:32:23] eMTee: +1 [2015-01-08 23:32:25] Other problems that have come up: not keeping track of phpBB updates... [2015-01-08 23:32:53] I am decidingly _not_ a network/system administrator. [2015-01-08 23:32:54] (It wasn't a 0-day that took done one of the forum incarnations.) [2015-01-08 23:32:56] cologic, that'd be same or worse for e.g. wordpress [2015-01-08 23:33:03] *down [2015-01-08 23:33:26] +1 to eMTee. [2015-01-08 23:33:38] Yeah, I've read news items on that. Looks like it's had seriousl isues lately, including some that one had to respond to in literally hours or else one's installation was near-guaranteed exploited. [2015-01-08 23:33:47] +1 to eMTee [2015-01-08 23:34:13] 4 votes for asking previous net admins to keep doing it for money. [2015-01-08 23:34:35] (And of course, this comes after servers themselves have been paid.) [2015-01-08 23:35:00] Next item? [2015-01-08 23:35:02] We will move on to item 14: Using external services to proxy DCNF / supported projects data [2015-01-08 23:35:31] Basically, auto-sync with sourceforge / launchpad / github / etc. [2015-01-08 23:35:50] I'm not sure what has to be discussed... We'll see when the rest is done. [2015-01-08 23:36:05] Yup, +1 [2015-01-08 23:36:46] no vote, still can't decide why we should host (and not link only) things that has great free reliable place elsewhere [2015-01-08 23:37:07] eMTee: Because they could close at any time and we would be left with nothing. [2015-01-08 23:37:17] (see berlios) [2015-01-08 23:37:34] I sometimes wonder about the state of Launchpad to be honest [2015-01-08 23:37:39] Well, if proxy == mirror == backup, that's roughly what this proposes, yes? [2015-01-08 23:37:50] However we could do the reverse: Rely on external services by default but keep auto-synchronizing with mirrors we host. [2015-01-08 23:37:55] good point, though places I think of are in hands of large companies and it's unliklely they will be closed [2015-01-08 23:38:06] Yes, +1 poy autosync/backup [2015-01-08 23:38:07] eg. github or launchpad, etc... [2015-01-08 23:38:18] Pretorian: it's tied to bzr and bzr is dead. A zombie, slowly shuffling along, but dead regardless. [2015-01-08 23:38:47] eMTee: That's another issue; that companies (and governments they reside in) have their hands on these services. [2015-01-08 23:39:16] The current server for dcbase.org is not in the US which is pretty good. [2015-01-08 23:39:16] Combined with GitHub and Bitbucket as distant #2 taking over market, LP appears ever more to be something useful primarily for already-extant or internal Canonical projects. [2015-01-08 23:39:36] It's also useful for this purpose that the DCNF won't be American. [2015-01-08 23:40:03] +1 autosync/backup. -1 to internal repos as primary. [2015-01-08 23:40:16] +1 cologic [2015-01-08 23:40:21] +1 cologic [2015-01-08 23:40:22] Removes DDoS incentives too. [2015-01-08 23:41:02] +1 to external services as primary project management services, with auto-sync with DCNF servers. [2015-01-08 23:41:22] 4 votes for external services as primary project management services, with auto-sync with DCNF servers. [2015-01-08 23:41:30] (hmm, my ctrl+up got messed up...) [2015-01-08 23:41:34] We will move on to item 14 (previous item was mislabled, should've been 13): Legal structure to help the DCNF [2015-01-08 23:42:01] Discuss. [2015-01-08 23:42:16] What type of legal structure did you have in mind? [2015-01-08 23:42:24] We talked earlier about just emailing the EFF so that could be enough. [2015-01-08 23:42:31] Yes, agreed. [2015-01-08 23:42:40] I don't know; what type of legal structure do IT foundations usually have? [2015-01-08 23:42:44] DCNF is the structure, I'd thought. But yes, I'd say this follows reading if/how the EFF responds. [2015-01-08 23:43:00] It's not as if there will be a legal department. [2015-01-08 23:43:03] Yes, indeed, cologic. [2015-01-08 23:43:11] Ok, let's move on. [2015-01-08 23:43:12] DCNF will be a legal entity. [2015-01-08 23:43:20] We will move on to item 15: Legal structure to help supported projects [2015-01-08 23:43:33] Same thing there, EFF? [2015-01-08 23:43:39] What legal services is the DCNF going to provide to supported projects? [2015-01-08 23:43:41] (oops, sorry, your word poy) [2015-01-08 23:44:22] Yeah, I think legal issues, albeit important in principle, are probably beyond the DCNF's effective capacity as currently constituted. [2015-01-08 23:44:41] Moving on then. [2015-01-08 23:45:02] I believe DCNF should have a list of all questions/answers it has taken to a legal council/EFF., [2015-01-08 23:45:14] +1 [2015-01-08 23:45:15] On the aforementioned wiki/website. [2015-01-08 23:45:59] +1 [2015-01-08 23:46:17] 3 votes for the DCNF hosting legal questions / answers. [2015-01-08 23:46:24] We will move on to item 16: Ways to find new members [2015-01-08 23:46:42] Open discussion. [2015-01-08 23:47:23] I thought I'd post to reddit/r/technology, flashback.org (Sweden's largest forum) announcing the org. [2015-01-08 23:47:35] There are 2 sides to this: advertizing / letting potential members even know the DCNF exists; and motivating them (giving something back). [2015-01-08 23:48:02] I doubt I'll disagree with anything vaguely reasonable here on the advertising side, anyway. [2015-01-08 23:48:09] I considered also posting/talking to IDG.se (IT webpaper), Swedish Pirate Party and potentially torrentfreak.com (they sometimes do posts about other stuff). [2015-01-08 23:48:33] Oh, yeah, above is just advertisement. [2015-01-08 23:49:06] What about announcing the foundation on some DC forums? Or would that be too much of a nudge? [2015-01-08 23:49:10] Giving back: perhaps a t-shirt with DCNF logo? [2015-01-08 23:49:15] Yes, that would work fine. [2015-01-08 23:49:32] A DCNF badge one can include in a program. [2015-01-08 23:49:43] +1 for the t-shirt. [2015-01-08 23:49:50] But I believe we shall do all of that after members can actually sign up in a meaningful way and pay money. [2015-01-08 23:49:59] (to be discussed I suppose) [2015-01-08 23:50:04] +1 badge [2015-01-08 23:50:17] This is also the topic... How do they join & pay? [2015-01-08 23:50:48] My idea is outlined as: Paying There will a Swedish bank account set up to allow people to send money to it for membership. This account will also be used for other economic matters that pertains to the organization. A PayPal account will be set up to be attached to the bank account. Members Members should send dcnf@dcbase.org a mail indicating their name (pseudonym is possible), e-mail and possible also something unique (preferably). The unique thing is meant to be a way for us to identify people if they want to vote etc. Membership information will be stored in a database, kept in a place where the board has access to it. The board will manage adding/removal/change of membership information. [2015-01-08 23:51:01] s/economic/financial [2015-01-08 23:51:12] I don't disagree with any of this. +1 for why not, if people are interested. [2015-01-08 23:51:32] Initially just keep a simple Excel file that the board can access/modify. [2015-01-08 23:51:41] 3 votes ub favor of the various ideas in this item. [2015-01-08 23:51:45] in favor* [2015-01-08 23:51:45] This gamification stuff isn't my personal preference, but it's quite popular in the world. [2015-01-08 23:51:59] But further down the line a full fledged a simple "I join" site. [2015-01-08 23:52:30] Next? [2015-01-08 23:52:31] We will move on to item 17: Hub for the DCNF [2015-01-08 23:52:57] Could be the same as we called dev hub until now? [2015-01-08 23:53:01] The dcbase server should host a hub for the DCNF. [2015-01-08 23:53:08] I believe this is adcs://hub.dcbase.org:16591 and it should be hosted on a DCNF controlled server. [2015-01-08 23:53:24] Not as a service, but as a part of the DCNF infrastructure. [2015-01-08 23:53:54] It will inevitably receive attacks; are we ready to handle them? [2015-01-08 23:54:02] I'd be fine with that, though reliability is evidently a problem. [2015-01-08 23:54:06] Or do we wait for that network admin? [2015-01-08 23:54:14] I think OVH, our current server, can handle it. [2015-01-08 23:54:37] poy: that's my question about a lot of these infrastructure issues. I'm concerned about the DCNF making promises it has no effective capacity to keep. [2015-01-08 23:54:53] +1 for hosting the dcbase hub on the OVH server immediately. [2015-01-08 23:54:58] I'd rather it try and fail than not try, but I'm cognizant of the problem. [2015-01-08 23:55:05] Indeed, cologic [2015-01-08 23:55:14] +1 [2015-01-08 23:55:16] (could only moderately hurt to try - OVH will put the server down and relaunch it after some time.) [2015-01-08 23:55:38] 3 votes for hosting the dcbase hub on the OVH server immediately. [2015-01-08 23:55:44] The word moves from poy to eMTee. We will move on to item 18: Involvement of the DCNF in DC protocols [2015-01-08 23:55:45] On the web side, cloudflare has been very effective. [2015-01-08 23:56:19] eMTee, you now have the hand on items being discussed. [2015-01-08 23:56:28] but divulging the ip with the hub would make cloudflare ineffective, no? [2015-01-08 23:56:47] Yes, it would. Cloudflare can't do DC hubs, so the hosts need distinct IPs [2015-01-08 23:57:08] eMTee, you have the word. [2015-01-08 23:58:06] If I may start... I belive the DCNF should not directly interfere with DC protocols but that they should simply be supported projects. [2015-01-08 23:58:09] I will open up for discussion. [2015-01-08 23:58:22] Agree, +1 [2015-01-08 23:58:33] +1 [2015-01-08 23:58:39] So eMTee had good ideas but they are to be brought up with ADC managers. [2015-01-08 23:58:57] no vote then [2015-01-08 23:59:05] 3 votes for "the DCNF should not directly interfere with DC protocols but that they should simply be supported projects". [2015-01-08 23:59:08] We will move on to item 19: Buying the services of developers [2015-01-08 23:59:12] who are ADC managers, anyway? [2015-01-08 23:59:16] I am. [2015-01-08 23:59:39] and why not present it under the name of the organization? [2015-01-08 23:59:50] Developers are one of the only things around here in any numbers, vs IT admin, etc. [2015-01-09 00:00:10] eMTee was not done with item 18, continuing discussion. [2015-01-09 00:00:24] eMTee: I would say that the ADC project can be a supported project. [2015-01-09 00:00:32] That's a good question - I have no opinion. [2015-01-09 00:00:48] I am unsure what DCNF, as an organization, shall provide. [2015-01-09 00:00:55] I think it would look great and a lot more convincing that the org is behind the recommended DC protocol [2015-01-09 00:00:55] A protocol published by a well-organized foundation might have more impact. [2015-01-09 00:01:11] But I may alone with that assumption. [2015-01-09 00:01:42] I'm indifferent, largely. I do agree it probably looks more convincing. [2015-01-09 00:01:43] You make a good case. [2015-01-09 00:01:44] poy, that's what I had in mind, yeah [2015-01-09 00:01:55] Fair enough, +1 DCNF for protocols [2015-01-09 00:02:14] This is an important decision - does the DCNF take control of the ADC protocol? [2015-01-09 00:02:14] This would include changing naming etc, right? [2015-01-09 00:02:24] Also, should we ask arnetheduck about this? [2015-01-09 00:02:25] I have no problem with that. [2015-01-09 00:02:33] ADC, yes, technically. [2015-01-09 00:02:48] Not the NMDC project, I own that and I can transfer to DCNF. [2015-01-09 00:02:48] poy: arne is/would be quite the bottleneck in that case. No objections in principle, only practical concerns. [2015-01-09 00:03:14] I propose the board should talk to arne about officially moving control to DCNF. [2015-01-09 00:03:21] +1 [2015-01-09 00:03:26] +1 [2015-01-09 00:03:31] +1 [2015-01-09 00:03:38] Furthermore, +1 to DCNF controlling ADC/NMDC [2015-01-09 00:03:41] 4 votes for "the board should talk to arne about officially moving control to DCNF". [2015-01-09 00:03:59] eMTee: Are you OK with this item? [2015-01-09 00:04:37] One remark: I thought about ADC only not NMDC. But there's time to discuss it at length later. [2015-01-09 00:04:51] NMDC is similarly applicable. [2015-01-09 00:04:57] We will move on to item 19: Buying the services of developers [2015-01-09 00:05:37] "Buying" - expression is not from me. [2015-01-09 00:05:48] Please clarify/explain. [2015-01-09 00:06:08] (In your own words) [2015-01-09 00:06:24] recruit is the word I used but maybe it's bad [2015-01-09 00:06:33] convince maybe? [2015-01-09 00:06:47] I think that would be good/OK, I suppose. [2015-01-09 00:06:50] Depends how one wants to fine-tune the connotations. [2015-01-09 00:07:08] Dozens if not hundreds of words broadly might apply. [2015-01-09 00:07:08] Depends on the incentive, I guess. [2015-01-09 00:07:17] Do you have ideas to convince devs? [2015-01-09 00:07:30] I have one: Google summer of code [2015-01-09 00:07:36] great [2015-01-09 00:07:39] +1 [2015-01-09 00:07:41] +1 [2015-01-09 00:08:06] 4 votes for the DCNF using the "Google summer of code" event to lure developers into DC. [2015-01-09 00:08:10] also announcements on project sites for open developer positions to certain areas/goas to achieve [2015-01-09 00:08:18] +1, eMTee [2015-01-09 00:08:21] also in the DCNF blog [2015-01-09 00:08:29] Perhaps a more controversial one, but making DC++ less conservative, since it and its mods are the main GUI clients these days. [2015-01-09 00:09:07] I regard this notion of ignoring the widespread need/desire for functionality because mods can do it as a long-failed experiment. [2015-01-09 00:09:16] also to respond at least for devs who would do great things if they'd be allowed or encouraged [2015-01-09 00:09:44] If there are no other comments/suggestions, we will move on to item 19: Buying the services of developers [2015-01-09 00:09:47] cologic: I'm not quite getting "less conservative" - technically or in terms of letting more people contribute? [2015-01-09 00:09:57] there's at least one case that really bothers me. I don't want to mention persons, to be discussed later if anyone interested. [2015-01-09 00:10:01] Both, I guess, but I had in mind the former. [2015-01-09 00:10:24] Let's move on [2015-01-09 00:10:32] Wait [2015-01-09 00:10:36] ok [2015-01-09 00:10:58] Do you know "project sites for open developer positions"? [2015-01-09 00:11:26] The ones I can think of usually involve money. [2015-01-09 00:11:29] I thought that'd be for each respective project's main page? [2015-01-09 00:11:38] E.g., "DC++ is in need of a web master" [2015-01-09 00:11:44] Similarly to how ApexDC++ does it, I think [2015-01-09 00:11:54] Ah... Good idea. :) [2015-01-09 00:12:16] So we don't have to spend money. [2015-01-09 00:12:46] Next item? [2015-01-09 00:12:49] Next item. We will move on to item 20: Mobile/web-based DC-related programs [2015-01-09 00:13:12] eMTee? [2015-01-09 00:13:20] Pretorian's idea, I added to the list because I think it's important today. [2015-01-09 00:13:44] It was even discussed at some detail how would things done in a mobile client. [2015-01-09 00:13:53] Fair enough, I believe we should have two things: 1) A webbased client that can be used as a proxy for chat-only hubs and 2) native clients for phones [2015-01-09 00:14:05] Needs a dedicated project/developer though. [2015-01-09 00:14:28] I don't disagree that this would be useful. [2015-01-09 00:14:34] Related to the previous point then. [2015-01-09 00:14:38] 1) would allow users to connect to the DCNF hub without owning a device that can connect via normal DC protocols [2015-01-09 00:15:10] E.g., if you have a locked down computer where you can't install/run EXEs [2015-01-09 00:15:22] (but where HTTP works) [2015-01-09 00:15:40] But ultimately this requires developers, of course. [2015-01-09 00:15:55] I'm all for it - sounds like a good project to bring new devs. [2015-01-09 00:15:59] My personal solution is ncdc + any SSH-like frontend one wants. That's not a mass-market solution, of course. [2015-01-09 00:16:19] If possible, it would be great if people could convince universities to create a project (say, final thesis) [2015-01-09 00:16:24] There are 'SSH for the web' native JS terminals. [2015-01-09 00:17:12] The only problem with such a university project is the available physical place to carry out that project. Those projects are typically done at the company/org. [2015-01-09 00:17:17] (not possible for me) [2015-01-09 00:17:17] Pretorian, very good idea, relates to the points discussed above [2015-01-09 00:18:18] The persons doing the project is usually compensated somehow, at least in my experience. [2015-01-09 00:18:36] But it'd be a fun project, most likely for a university. [2015-01-09 00:18:47] And for students [2015-01-09 00:19:22] Ok, next? [2015-01-09 00:19:28] We will move on to item 21: Contacting well-known tech bloggers [2015-01-09 00:19:54] Tied in with 16, finding new members. Any suggestions for bloggers? [2015-01-09 00:20:05] Pretty much what it says. Tech bloggers are always looking for/eager to write about interesting things but before contacting them we do should looking interesting. Therefore it's not useful before we have a good website and nominated clients/hubs that's for wide usage. [2015-01-09 00:20:09] (whoops, sorry, eMTee's word) [2015-01-09 00:20:19] ok, +1 [2015-01-09 00:21:35] Yep, the blogger will just fire up a client and if it's not perfect he'll let it go. [2015-01-09 00:21:44] We need that new people like what they discovered through the recommendation of their fav blog sites. If it's average or hard to use they just move on... [2015-01-09 00:22:02] Any particular suggestions for bloggers? [2015-01-09 00:22:53] Harder security with similar possibilities that other known P2P can offer. [2015-01-09 00:23:18] +instant messaging, community features. what other P2P doesn't offer [2015-01-09 00:23:29] +1 [2015-01-09 00:23:32] Generalizing, easier to form known groups (e.g., where local bandwidth is free/cheap/abundant but the links outside aren't). [2015-01-09 00:24:22] Ok, let's move on. We will move on to item 22: DC and businesses [2015-01-09 00:25:00] I can only quote my idea from my list [2015-01-09 00:25:08] Provide a documentation of ideas of possible business/industrial usage of the DC protocol (securely sharing, transferreing documents between parties or parts of a large company without storing outside, etc...) If DC could be picked up and developed by a business for any purpose but on its own cost, that could give a boost in form of a possible upstream patches to various DC software. [2015-01-09 00:25:38] +1 for planning on publishing such a doc. [2015-01-09 00:25:42] So this is primarily documentation, targetted to businesses? [2015-01-09 00:26:07] +1 anyway [2015-01-09 00:26:25] Rather a heads up of what more can be achieved using the DC protocol. [2015-01-09 00:26:26] 3 votes for planning a business-oriented doc about DC. [2015-01-09 00:26:57] Could include other similar ideas that makes potential people thinking about it. [2015-01-09 00:27:00] also chatting... we use DC at work to chat sometimes. ;) [2015-01-09 00:27:10] sure [2015-01-09 00:27:13] +1 [2015-01-09 00:27:16] +1 [2015-01-09 00:27:31] and the hub runs at the boss' office logging all :P [2015-01-09 00:27:52] With this subitem, this concludes the item 15, with the list created in item 5. [2015-01-09 00:27:59] It's surprisingly hard to find good, reasonably mature open-source chat servers and clients. XMPP/SIP are the main competitors here. [2015-01-09 00:28:00] it's in a machine in the middle of the office. :) [2015-01-09 00:28:11] Item 16 in the by-laws: additional items and motions. [2015-01-09 00:28:35] I have two: a) copyright management for DC plugins and b) copyright management for clients/hubs [2015-01-09 00:29:02] Item a) I believe all DC Plugins shall transfer the copyright to DCNF, similarly as ADC/NMDC projects [2015-01-09 00:29:09] (where possible/applicable) [2015-01-09 00:29:12] feel free to discuss [2015-01-09 00:29:22] what is the advantage? [2015-01-09 00:29:24] Sounds harsh... why? [2015-01-09 00:29:28] What are they now? [2015-01-09 00:29:48] Allows plugins to have a signature stamp that they were created by the organization. [2015-01-09 00:30:03] Or, sanctioned, at least. [2015-01-09 00:30:27] I see - we were planning on DC++ managers to do that in the past - better have the foundation do it. [2015-01-09 00:30:35] Yes. [2015-01-09 00:30:45] Note: this item is only for plugins, I will get to clients/hubs [2015-01-09 00:30:48] So you mean "existing plugins", not "any plugin anyone develops"? [2015-01-09 00:30:52] correct [2015-01-09 00:31:17] +1 for moving current DC plugins to the DCNF. [2015-01-09 00:31:20] Basically the ones listed on [2015-01-09 00:31:26] Including the SDK project. [2015-01-09 00:32:02] +1 certainly for the "DC++ team" ones. iceman would have to comment on is. I guess poy's basically already commented regarding iFeelPowerful. [2015-01-09 00:32:10] Yes, of course, cologic. [2015-01-09 00:32:25] Since plugins is a standard like the protocols, if the latter goes under the control of DCNF then it's logical to do the same with plugins [2015-01-09 00:32:27] We cannot "steal" the copyright of those authors. [2015-01-09 00:32:35] Indeed, eMTee. [2015-01-09 00:32:36] 4 votes for moving current DC plugins to the DCNF. [2015-01-09 00:33:04] Item b) this is the same as item a) but for certain clients and hubs. Notably, DC++, in my opinion. [2015-01-09 00:33:10] 4 votes for asking current plugin authors to transfer to the DCNF.* [2015-01-09 00:33:29] This would allow us to create certificates for DC++ (et al) and have a better publishing mechanism. [2015-01-09 00:33:33] Feel free to discuss [2015-01-09 00:33:48] I'm indifferent on DC++ & ADCH++ themselves going to the DCNF - in any case, arnetheduck has the final word on that matter. [2015-01-09 00:33:58] Provided of course that we will get arne's approval. [2015-01-09 00:34:20] It would simplify legal action, if such need to be taken. [2015-01-09 00:34:21] But also it will still make DC++ look like the de facto and best client. It's not the purpose of DCNF [2015-01-09 00:34:31] Good point eMTee. [2015-01-09 00:34:43] not to say that it's not DC++ that is the best client available right now [2015-01-09 00:34:56] The idea behind the move is simply that I would like to have a certificate issued. [2015-01-09 00:35:09] That would allow users to see a "approved" installer. [2015-01-09 00:35:10] If the advantage is "certs", how would other supported projects handle certs? Maybe the DCNF could help them without requiring a copyright? [2015-01-09 00:35:13] I had been prepared to support, but yes, actually, I agree that at least at first the DCNF should maintain separation from any given client, since it already looks like it's basically just DC++ developers. [2015-01-09 00:35:34] Which is a critique I've seen in particular before on some other things regarding ADC. [2015-01-09 00:35:40] I believe the copyright owner MUST be the same as the certificate owner. [2015-01-09 00:36:13] E.g., it is "worse" to see "Jacek Sieka supplied this application". [2015-01-09 00:36:20] vs "DCNF supplied this application" [2015-01-09 00:36:30] But yes, I agree it is cumbersome for other develoeprs. [2015-01-09 00:36:33] I agree there, but regard is a lesser downside. [2015-01-09 00:37:19] ok, new proposal: DCNF should provide projects with an ability to acquire certificates (i.e., basically paying for the certificate) [2015-01-09 00:37:20] A remark: we're talking about moving copyright to DCNF, I think it's not a good idea, however to move the copyright of DC++ and ADCH++ to someone who actively working on it would be great. [2015-01-09 00:37:23] eMTee & cologic make good points - this loss of separation is dangerous. I'd prefer DC++ found another way of getting certs. [2015-01-09 00:38:24] +1 agree on separation [2015-01-09 00:38:29] +1 for the DCNF providing supported projects with a way of getting certs. [2015-01-09 00:38:30] eMTee: yes. Absolutely. I've discussed this before. Whether DCNF should 'own' DC++ (which has problems, yes), arne's increasingly a historical figure regarding DC++. [2015-01-09 00:39:19] for the record: we even forget to invite him for this meeting. sorry arne if you ever read it. [2015-01-09 00:39:26] His copyright makes sense nonetheless as he remains the main contributor, and he is probably still available by email. [2015-01-09 00:39:51] It's been a while since it's caused real problems, so the status quo, conversely, doesn't much bother me. [2015-01-09 00:39:54] We have a list of items that he needs to address, we should bring this up as well. [2015-01-09 00:40:07] (well, the board*) [2015-01-09 00:41:04] If there are no additional comments on this, I will move on. [2015-01-09 00:41:14] Next item that I just though of, that we discussed earlier: [2015-01-09 00:41:20] [tor:23:13:15] We might explore that one of the old hublist domains are free and use that. [2015-01-09 00:41:36] Perhaps we should buy old domains. [2015-01-09 00:41:57] I don't know all of them, and I don't know which are still active to this day. [2015-01-09 00:42:01] hublist.org and openhublist.org that I was referring [2015-01-09 00:42:03] Cheap + pre-existing client trust relationships. Could be useful. [2015-01-09 00:42:17] +1 for those two [2015-01-09 00:42:22] Good idea, +1. [2015-01-09 00:42:44] openhublist may had another different domain at it's start IIRC. [2015-01-09 00:42:45] 4 votes for attempting to buy "dead" hub list domain names. [2015-01-09 00:42:52] If there are no further comments on this item, I will move on. [2015-01-09 00:43:03] This concludes item 16, addiitonal items. [2015-01-09 00:43:14] This is the last item and concludes this meeting. [2015-01-09 00:43:29] I want to thank all of you for participating. [2015-01-09 00:43:37] Any last comments? [2015-01-09 00:43:54] Not from me. [2015-01-09 00:44:17] I will hereby officially close this very first meeting for the Direct Connection Network Foundation (DCNF).