Discuss Board Meeting

From MWStake
Jump to navigation Jump to search

Raw transcript:
Lex: That it's much

Lex: It's much better to have friends that own it.

Bryan: Yeah, totally. Always

Lex: Never buy that stuff never ever own it just have friends and you bring a bottle of wine, have a good time. And then you say bye bye

Lex: Thank you.

Lex: And then they're they're left with the whole

Lex: No, no, I'm not that gadget t

Bryan: Yeah.

Lex: As long as you can enjoy it with someone else. You don't have to own it.

Bryan: Yeah, they say that the two best days in a boat owners live from the day they buy it. And the day they sell it.

Exactly.

Lex: Well, unless you know it's your, your absolute passion or it's your, your, your business.

Yeah, then of course

Lex: So,

Bryan: So it's really jumped on the beat is on

Cindy: Hi there.

Cindy: Can you hear me.

Bryan: Yes, it's me.

Cindy: Because I'm sitting on the grass under a tree outside of Costco. Well, my tires are getting rotated unbalanced.

Lex: Oh rating the

Time.

Bryan: Cindy. How are you guys for the lockdown. Hi. It's nice. It's a beautiful day.

Cindy: It's a nice, it's a nice set. And there's even some Shea and I was able to take off my face mask, because there's nobody within six feet of me. So this nobody within 50 feet of me so

Cindy: Yeah, we're

Cindy: Think we're still considered phase two of lockdown. So, you know, people have to wear masks and you're supposed to stay home. If possible, but you're allowed to go out and do stuff like, get your tires rotated now.

Bryan: Yeah, we just got kind of a lockdown again.

Cindy: That's what I heard. How are things about. So I think it's worse near you, than it is in Northern California. Is that right,

Bryan: I don't know we're, we're, we're in kind of like a weird little zone within what we call Central California where we're kind of on the northern side better now. We didn't have anything for a while, really.

Cindy: Okay. Yeah, I think that's right, yeah. Because you're not you're not la your, your central Europe north of La

Bryan: Yeah, we're basically I'm in the middle between LA and San Francisco.

Bryan: But yeah, we've now had, you know, a serious uptick in cases so

Bryan: It's here. Yeah.

Cindy: Yeah, we've been doing relatively okay lately, but there has been in here too.

Bryan: But I want to say.

Bryan: We have like 200 and something thousand people in our county and for a while, you know, for a long while we're recording, like, you know, in the single digits low single digits for a while and every day, you know, none for a while. One, two and, more recently, were like

Bryan: 30 a day or something.

Cindy: So it's up. Yeah.

Bryan: Almost 300,000 people

Bryan: Mark, you are you able to talk

Bryan: You can talk. We can hear you.

Bryan: You can try calling in.

Mark: I just switched the microphone.

Bryan: Got that work. Yes.

Amazing.

Mark: Computers, especially Linux is so hard.

Mark: Anyway,

Mark: How's it going, Lex

Lex: Good, good, good, good.

Mark: Are you watching us Americans in shock and saying, you know, how can they be such idiots.

Lex: No, no, no, no, no. I can still be

Lex: You know, whenever, whenever someone asks me, and I think I've mentioned this on this channel already whenever someone asked me, What do you think about the states, I say, I fully rely on the British wisdom.

Lex: Want you know why I mentioned that no

Lex: Because I say about the US that the US.

Lex: Will always do the right thing, but only after they've tried everything else.

Cindy: So,

Lex: That's, that's my look. This is all it boils down to.

Lex: And

Cindy: My god, that's accurate.

Lex: So, yeah.

Bryan: Well, you know, we had a we had our Fourth of July, which they would, they would have called the colonial insurrection day but

Bryan: We celebrated it

Mark: Yeah. Wow.

Mark: Anyway, um,

Mark: So let me, let me see. Where's my little agenda thing that I have

Mark: You all should know that.

Mark: I've been working

Mark: On making sure and upgrade to 134 works. I had a question for you, Cindy about

Mark: That so don't worry always something stability.

Cindy: I'd love you to try out. They actually have they put out they cut the branch or one to 35 but I was thinking this morning. I don't remember seeing announcement that they've actually put out a release candidate yet.

Cindy: But once they do, I'd love people to try it.

Mark: So, oh yes, very the very second thing at the on the list is the brokerage flex and Brian are supposed to be working on.

Bryan: Supposed to is the key word Lex did some work art can post the link

Mark: Yeah, it's it's it there in the announcement.

Bryan: Yeah, oh actually check the announcement. I should start reading those

Yeah.

Bryan: I'll post it in the chat. Just to. Yeah.

Bryan: You do have to

Bryan: Login.

Bryan: To manage

Lex: I can share my screen if you want to. Yeah.

Bryan: Go for it. Like,

Lex: Can you see

Lex: Must be Cindy.

Cindy: There was a near miss right in front of me.

Cindy: I didn't see it, though, because I was looking so intently. Alexis wiki.

Cindy: I just

Lex: When you see my is that one page, you can see

Bryan: Yes, yeah.

Okay.

Lex: Yeah, so I just, this is just a story about you know how it should be initiated and the the main aspects that need to be clarified and then this step that someone would have to follow.

Lex: With clearly

Lex: A clear distinction about what MW steaks role and responsibilities and the whole thing.

Mark: There were some questions we had last time I believe about

Mark: What were the questions, there was a discussion we had about this last time.

Bryan: We popped the nose. I all I think I took was is there is Cindy had and I think there's a few

Bryan: reservations about parts of it i don't i don't think i caught what they were.

Bryan: But what

Bryan: The one thing I'd like to notice. One of the more immediate things we need to do is have a concrete and procedure laid out.

Bryan: If we are going to incorporate it into the authorize net portion of the credit card payment on the website as a form of receiving the payment, we need to have that defined like pretty soon.

Bryan: So my proposal for that.

Bryan: Till wow four variations would be something where we could provide, you know, there'd be a drop down for the normal

Bryan: Payments for membership for different rates. And then we could have a

Bryan: On our side.

Bryan: You know code that we could provide and then I'm not sure how exactly we can, we would configure it if we'd be on wiki but functioning, whatever the code is that we provide could be like the 1900 and $20 that Lux has here that's in addition

Bryan: And something that normal

Bryan: credit card payment process would pop up. So the user, you know, there'd be a blank spot for, you know, something new. If they put in something that doesn't exist, it wouldn't allow them to move forward. But if they put in the code, it would pop up with the

Bryan: For whatever note. The reason was in their pain and process it.

Bryan: I'm confused because I thought

Cindy: We were paying the 1920

Cindy: And people paid their membership dues and then we would pay 1920 towards a contractor.

Cindy: To do some work.

Bryan: Well, so, okay, sorry. Yeah, you're right. That's how it's written here, but let's pretend that we determine that.

Bryan: Yeah, you're right. That's how this is right. Okay, so there's no overage in this one, but the worry is is if their ends up being a

Bryan: You know, we look at the project and it paid for a 16 our project. And it looks like it's going to take 26 hours and we say, hey, this is a little bit more than what you know you get with your membership, the differences as to what is it 120 times

Bryan: You know, whatever. I said, The difference was there maybe eight hours.

Bryan: And so, you know, you're going to be charging an additional $1,000 to do this. Do you want to move forward. And if they say yes, we will still had all the brokerage but we need some way of accepting that that difference

Cindy: Yeah, that was the part I was uncomfortable with that was us being involved in that transaction.

Cindy: At least without clarifying what the, what the terms are

Cindy: Because what if

Cindy: Somebody does quite a bit of work and says, yeah, yeah. We'll pay will pay and you know if it's one of us. We all trust each other. We know that they'll pay, but if we're going to start this in a larger scale for

Cindy: I don't know. I'm just worried about us.

Bryan: We have

Cindy: Not

Cindy: Done until after paid for example now.

Bryan: We have a couple options. One, we can say

Bryan: You know, there needs to be a scoping portion at the very beginning where we

Bryan: Intake we decided, like is this

Bryan: Within around the 16 hour range or is this wildly off right and and so somehow we need to do without up front, and we could make the decision that

Bryan: If it's wildly off. It's not how we're going to be doing this and it gets dropped like it's not a project, you know, you need to come up with a project. The other option is we can say like

Bryan: You know, as long as the amount that we think the differences is less than, like, the whatever the total is that they're spending to be a member 5000 we can kind of use that as collateral for a bit, you know, and we can eat into that as needed and still ask them to pay for it.

Bryan: But if we don't worst cases, you know, they get a project paid through and you know we can revoke their member. I don't know how that ultimately, we have a little cushion there.

Bryan: And then the next thing we can do is say, you know, payment doesn't work doesn't start until you you use this voucher to pay on the site. This difference that you know we've identified is the difference between what

Bryan: The 16 hour project is and and what what you presented

Mark: So, um, I definitely see the

Mark: The issue that you're outlining i think i think what we may want to do is have appeared, you know, have a

Mark: Recognition of trust, you know, if it's something that we just met our niche. You know, it's someone's first project limited to that $5,000 or whatever their total, you know, spend is

Mark: Limited total spin to that. And then if you know if they if there's a few projects under their belt and they consistently, you know, follow through. Then, you know, I think we can

Mark: Ramp up and let them do more. So

Mark: But I wonder if there's a way to clarify that.

Bryan: Well, one thing would be nice, is to kind of step into it, like, you know, Lexus seemingly offering

Bryan: Us to trial with him so

Bryan: You know, we can propose something and see how it works out with that. But yeah, there's more scope that we can kind of add when there's these

Bryan: Weird contingencies or differences and we can decide how we want to handle it, or you know we can decide we're not going to do it, but I guess it's up to us. But you know, I don't think we should have to worry about designing for the worst case weirdness right off the bat.

Bryan: Sure.

Mark: Um, I wonder if if you said you wanted to discuss this more during the meeting. I wonder if we can discuss cover these other items that are on the agenda and then come back to this.

Lex: Yeah. Yes.

Lex: Yes, and Mark I like let's get back to that after we covered the others because I have a radically maybe just came up to my I just had this idea now radically different to approach this from a different angle. But let's do that afterwards.

Mark: Alright, so the next thing on the agenda here is status of black blog and tracking blue. I can't talk status of blog and trademark issue.

Mark: And Marcus.

Mark: Said that he was able to get a response from them and they said that we couldn't use the domain. Maybe we could, if we were the matic organization. I don't know what the difference is.

Mark: I know there is a difference. I don't know exactly what the difference is routine Queenie a theme org and a user org

Mark: And Marcus responded and asked if they could own the domain and we could use it you know right to it.

Mark: I don't think he's gotten a response back on that yet.

Mark: Does anyone else note, Cindy. You, you're the most likely to know what the differences between a theme Oregon to

Cindy: You. I did not know offhand. I know that it's documented somewhere on right but I have no chance to look at it now. Sorry.

Mark: Okay, well, that's the status of that the status of credit card processing marine and I have been going back and forth, I guess, Eric Johnson out a

Mark: Thing that I unfortunately did not read because I was

Mark: Busy, busy, busy.

Mark: But day one. Read Eric John's thing can summarize it.

Bryan: I read it, but I wasn't, I didn't read it to

Bryan: reread it, or summarize it. Sorry.

Mark: I really should have read it, I apologize.

Mark: I mean,

Bryan: Be basing my take away from it was. He's got a lot of the work done. He estimates. There's like 24 hours of work with some testing.

Bryan: And

Bryan: And the big takeaway for me was, is we need to get him any changes or corrections or updates like soon.

Mark: Right. So yeah, he has been going. I'll just tell you what I know about the

Mark: Maybe I did read it because I remember all that stuff. Um,

Mark: What, uh, what marine told me, and I feel really, really good about this, is he appreciated the clarity or the the detail or whatever that I put into the specifications. So I felt good about that because that's kind of the first time I've done that for someone else. Um, so

Mark: Let's see. Yeah, I think in and I told him we would have another modification talking about the the changes you were you mentioned, Brian. So yeah, we need to go over that.

Mark: An outline how that's going to be

Mark: I think I

Mark: Think that's it about that, uh, and I guess we can. Well, the other. The other thing is, Oh, one more thing on the agenda here is where, where's my mail.

Mark: The collection extension which, you know, since since marine gave me a little boost about the credit card processing. I think I do have a little I'm a little bit more encouraged that I can work on the specification for that, um,

Mark: So yeah, going back to the I haven't started on that anything with the credit card collection extension. But yeah, if anyone has ideas about how the

Mark: Collection extension should work you know it'd be good to get to me, I think, I think we already have a model for how it should work with the collect the old collection extension.

Mark: So anyway, um,

Mark: So back to the brokerage thing he lets you have an idea that you wanted to share

Um,

Lex: Let me paste this link.

Lex: Because I can see you know there's several concerns, especially what Cindy.

Lex: just mentioned, if we broke her money then that that

Lex: Was a whole lot of potential issues, right.

Lex: Question is, whether we could just broker competency or competencies. I say that, I mean the skills and capabilities and resources and just provide that matching service. And as you can see, let me share my screen again. But I also sent you the

Lex: Link again I'm developing this, you know, this is actually about three years old when I have here, I just put it into my new wiki now.

Lex: So the problem of we, as you know, agents for performing work for customers. Sometimes we're, we don't have the time or the skills or the experience to do it and then

Lex: We can fall back to a what we call here a trusted web of colleagues and right now I'm at this

Lex: Challenge of profiling, the skills and I was, and I put this in a sort of media wiki based ontology.

Lex: And I want to try it out with regard to to knowledge and skills revolving around media wiki setup configuration integration and everything.

Lex: And this is a I could be a service in itself to just, you know, provide the network and the mechanics to actually

Lex: Distinguish these people who who know exactly what they're what they're up to. Because you know Brian and I were discussing if I asked someone. Do you know media wiki and they that person says yes, that can mean anything.

Lex: I mean, you know, we could mean I can edit the page and it can mean I can hack the core. So, or, for example, Cindy. Did you know she was, she was

Lex: Dude, performing open heart surgery on my week. He's database with a route my SQL access which I was, you know, I was one meter away from the computer and just looking at the screen and not even daring to brave so

Lex: Yeah, I'm now in this process of trying to codify

Lex: On that, you know, we're not exaggerating but if you go too much into the details becomes really, really rigid. But if we have you know simple high level action descriptions and especially in the context of search that could be

Lex: Helpful. And we could add it on the left here we have a competence.

Lex: Of user, Bob.

Lex: With a certain task which here is the subject about the job queue.

Lex: And then we have credentials and it could actually be the collection of this these credentials.

Bryan: Help you know

Lex: Members, fine, find the right people.

Lex: But that's something I'm developing now and you can see the current

Lex: The current ontology is actually on GitHub here and here you've got the two examples which reflect the ones here because these are direct meshing their, their mission in say that mashed up from GitHub directly

Lex: And I'm testing that now.

Lex: Because I understand this financial management.

Lex: Can be a little

Mark: Scary.

Lex: Yeah, it

Lex: You know, for an organization that doesn't have a distinct department handling that it could be a little an imperial overstretch

Cindy: Yeah, there, there are legal implications and their financial implications and we, you know,

Cindy: We need good legal and financial advice if we were going to go that way. But I do love this idea of the trustee Weber colleagues and always had, and that could definitely be a service that we would provide is, you know,

Cindy: In Canada, the brokerage

Cindy: It's just that we wouldn't necessarily be involved in the financial aspect, although that begs the question, what about the

Cindy: The fact that we're

Cindy: You know, saying that will

Cindy: Be part of membership, it gives you a 16 hour whatever project. So we'd still need to figure out a way to do that if we wanted to do it but but i think that the trust and web of colleagues to, you know,

Cindy: matchmaking is a great idea.

Mark: So I liked the idea that we limit our exposure in, you know, in the membership where we say, okay, this is only a 16 hour project. And this is only an eight hour project. I like that better than the wide open brokerage thing because it does limit our exposure and risk.

Mark: But I also understand that we want to expand it to be more than that, um,

Cindy: I know that one of Lexus initial concerns also had to do with Swiss law and being able to hire people. I can't remember the details of it.

Mark: Yeah.

Cindy: The question is whether any of this would satisfy that need from your perspective, you

Lex: Know,

Bryan: One of the thing that Lexi, and I had talked about was the potential for

Bryan: Some amount of project management.

Bryan: That we either assign or do our ourselves could be in a sense, paid for and and the methodology that we had talked about was that, let's say it was

Bryan: $5,000 that their membership was. It was 1900 and $20 that the project was and it looked like it was going to be the right amount of time for their 16 hours.

Bryan: And then, you know, we would look at and election thrown out something like 4% or something like that.

Bryan: And we would take it out of the kind of the difference between the membership dues and the project amount so

Bryan: You know they don't they don't look at it like we're taking it, you know, out of the mouth of their opinion toward the project and

Bryan: I don't know if that makes any sense. And we are able to do so called paid paid for service.

Bryan: So we can do it. Um, but

Bryan: You know, do we do we think that we need somebody internal

Bryan: Beyond just the developer we assign it to to kind of manage the project.

Mark: I think that I think that whatever work we do, does need to be, you know, we have to make sure that that's compensated just because

Mark: It is it is work and it is, you know, it's something that we're committed to and if we're going to commemorate or shells to. We want to make sure it gets done. And the way to do that is to pay someone to do it.

Mark: Um, I think that that that's definitely a reasonable thing.

Mark: And I think having it is, you know, this is a I like the 5% I understand it, you know, there may be a reason for 4% but 5% is round. Oh.

Mark: Um, so yeah, I like that idea is, well, just saying this is, you know, this is the management kept basically

Bryan: Okay.

Cindy: The only part that confuses me about that.

Cindy: And it may just be because I don't have the financial brain for it. If we're saying that it comes out of the difference between that

Cindy: You know 16 hours of work and you know however much they paid for their membership. It just means we're reclassifying part of the money that we're getting from the membership, we're not actually getting any additional money we're paying for it.

Cindy: It just air marketing some of that money towards the management expense and then the rest of the money that we get from the membership.

Cindy: So if you look at what is it $5,000 that we get and 1900 and 20 of that is to pay for 16 hour contractor to do 16 hours of work for the person

Cindy: And then there's an additional 4% whatever that might met mounts to than the amount of money that we have to play with. For other projects like for example funding to work on the collection extensive tension is whatever's left over afterwards.

Cindy: And

Cindy: Not ambitious bringing in any additional money past that.

Cindy: Yeah, that right

Bryan: Yeah, but the way to think about it would be that I think is that

Bryan: They're paying a premium and found you know the MW steak is getting more money for their coffers.

Bryan: At the cost of, you know, 1920 which we don't seem to bat an eye at right. It's like, that's part of it. And then it's, you know, like an additional 250 bucks, which would be the 5%

Bryan: For the 5000 which presumably is you know roughly around two hours of one of our work for making sure it moves forward. So you're right. But I don't think

Bryan: I don't think if you talk to anybody there would be much of an issue with that I'm

Cindy: Trying to understand where where the money's coming and going.

Cindy: The other thing was the 1920 it was assuming that there that we find somebody at $120 an hour and that there's no other costs or taxes or fees or anything associated with that.

Cindy: Are we talking about doing that as a flat rate or, you know, what if we could get somebody for less. Or what if nobody's available for anything less than say 150 an hour.

Bryan: Yeah, well one and what that was one of the talks that lacks and I did mention, I think, to make sure that we're not

Bryan: Looked at suspiciously. We should be, you know, using i mean that the trusted web of colleagues is one of the reasons I was interested in becoming a member of

Bryan: W steak and or a board member, because that this, this type of idea is exactly what I want for me selfishly, so I can use it to figure out who I can pay for or talk to you or whatever. But there's lots of reasons, but ultimately

Bryan: We should probably be sending out if we get a project and we say, okay, it's a security something, then we say, okay, you know, maybe let's pretend Brian will still is willing to do it and

Bryan: We should probably find two other people using the you know festival colleagues database or whatever.

Bryan: And then send out and say, hey, we have you know this thing. Are you willing to do it. And can you provide like a, you know, a quick estimate and then we should, you know,

Bryan: Look at the bids and then make a decision. Right. But we shouldn't probably always be soul sourcing it because that could be kind of suspect right and we

Mark: Definitely

Bryan: We shouldn't like

Bryan: publicize what the bids word everything else that should be kept internal but we can have records of what it was. And so if we ever get asked, we can kind of say well we did

Bryan: You know, for this project. Here's the three, you know, people we reached out to. And this is the person that one it but

Bryan: Yeah, I mean, and the more we talk about all these bits of detail you know this thing ends up growing and us something that's a bit bigger, but I think it's still worthwhile.

Mark: Um, it is it is a

Mark: Week definitely should not be soul sourcing stuff if if at all possible.

Mark: I there are, you know, there are things that basically there's only going to be a sole source for

Mark: But yeah, we should definitely try and I think our tiny little section of the web here. I think it's more likely that we're more likely to run into those soul force issues.

Mark: I, I am the only expert, as far as I know. Well, no, that's what they told me I am the only expert who knows about media wiki on wiki pathways, for example, because they have so much customization there that I've helped them with

Mark: In fact, probably, I'm, I'm, that's one big reasons that they're going to move away from media wiki. So because because they

Mark: You know, don't really have anyone else to support it. So,

Bryan: Yeah, it sounds like. I mean, this is a side topic, but, uh, we should try to sell them on a more standardized approach understand what they're doing and see how we can make it.

Mark: And, you know, maybe, maybe we can bring them here and get them, give them talk to you because they were they do want to use media wiki still, they just don't want to use it the same way that they were kind of like what you're talking about it a more

Mark: standardized approach and they were looking at using more wiki data.

Mark: If you have you done anything with wiki data Brian No.

Bryan: No, I mean if if they're saying

Bryan: I was way more bummed. If it's you're going to say we go like SharePoint or something or

Mark: No, no, no, no, nothing like that. It's just

Mark: They have a lot of customization if they went to a SharePoint that would have to do just as much customization.

Bryan: I mean, if they're going to wiki data. Um,

Bryan: And we're talking about the software, not, not the company, but then they functionally are using media with he's still

Mark: They're just not using know they're talking about the

Bryan: wiki, although

Bryan: I hate it. Right. You okay, instead of having an internal something

Cindy: Anyway, so let your idea with the trust the trust and web of colleagues is your idea that if somebody were a member of the stakeholders group.

Cindy: That they would get access to a private website yet would have information.

Cindy: Or would it be a public website that anybody could use that we just maintain or would it be that we maintain it for our own uses the you know the board can get access to it but anybody else has to come and ask us, and we would then give them recommendations.

Lex: Yeah, now you're much further than I have thought until now, I can tell you where the original idea is not from a customer perspective.

Lex: But from my perspective as a very small little service because I want to be able to sleep, sometimes have a weekend and go on vacation.

Lex: Which means that if I have customer either is either. I have a large enough company so I can provide a sort of 24 hour service or and that's when the trusted web of colleagues came up

Lex: I have this web of colleagues and I can fall back to, and you can see I was coming up as a deputy service. So if I if I cannot

Lex: respond to a request that would help me resources contraction is when I don't know. For example, I always bring L Dap and Active Directory integration, I have no clue. I can hack it together, but it's not professional. So I would fall back to someone else and

Lex: These were the two and then based on that. I was coming up with these trust levels.

Lex: Were on you know from Tier one two to five.

Lex: To one is just very simple tasks, you know, they asked for a new form and you're actually in the net Paul how King, so I just call it to one guy and or person and they will do it for me.

Lex: TL five afterwards is is strategic advisory of should we do multi server installs and should we, you know,

Lex: But this is all theoretical at the moment, but it's just that you know that my idea was for us to become more stable as a network of small

Lex: Service agents that was the original idea.

Cindy: Yeah, and I think that's a great idea.

Lex: And and and what you have here is, is this scaffolding the framework.

Lex: And also, you see, I have the problem up here, which is an overstretched challenge and and then the solution which is this term.

Lex: That that I came up with. And right now I'm I'm working on the on the interface between the tasks at hand and and the human resources available and I'm trying to formalize that but not overdo it.

Lex: So that it becomes sort of automatically manageable and of course I want to do that in a wiki and

Lex: Mostly automated as well because my search engine is now already sort of being optimized for addressing this task, but

Lex: Yeah. And then from a customer point of view. Yeah, you've got a member at the stake member looking for for for human resources for people helping him.

Lex: I guess they would, they would sort of connect. Here you see so they look for someone. Well, depends on how

Lex: How well they understand the system I let's say they say, you know, it's very slow. It doesn't update. For example, that's something

Lex: As simple end user a rookie a layman will discover they say I make changes and then I can't find them, or I make changes and they don't show up in a in a query results and then he would sort of say, well, I need help with that. And that would then affect the job queue.

Lex: So he would have the system to search would have to point him to that two people, featuring the competence to actually, as you can see here configured to run regularly configured to run on page requests. Oh I this is I forgot something here. Sorry.

Lex: That's actually another one continuously that should that should mean continuously have to change that. So you see, I'm, I'm looking for a way to formalize that that surface between the tasks at hand and the resources we could provide

Bryan: Well, one quick, just know that we're just getting back to the original question, maybe we can try to make a decision about it. I haven't thought about it too much, but

Bryan: Should the results of the trusted web of colleagues be published externally or not without really thinking too much about it. I think it would be good if it was published externally.

Lex: Sure. Sure. Okay. You see, the only. I mean, maybe this the test. You see, then I thought the credentials. Because look, actually the original was on syndicate

Lex: Here I came up with that. And these are my red links are completely messed up. I don't know exactly why, but I'm

Lex: For example,

Cindy: Yeah. The only reason I can think to not have it be public is as an incentive for membership, but that always feels good.

Bryan: Yeah yeah

Cindy: You know, I don't know.

Lex: Now that that's all about

Cindy: We're sort of all about sharing and whatever until it

Cindy: Goes to to hold that. But on the other hand, we too need incentives for membership. So no, I don't know.

Bryan: I'm very

Bryan: I still think I think we can't be selling the memberships based off of a quid pro quo basis. Like that's, I don't think that's really how memberships for this type of organization work. So if we

Bryan: You know, if we're having to sell a cookie for $1 membership we it's we've not you know

Bryan: Our, our, our model for what we're trying to do, isn't isn't correct right

Cindy: Yeah I know people should want to be members because

Cindy: There's a value in being part of the community and exchange of knowledge. Yeah.

Mark: Um, one reason that might make sense not to share this. And I just, you know, this is

Mark: A way.

Mark: I'm not sure it makes sense for for a nonprofit to do this or if it's even legal but one, one thing is that this becomes a resource that is very valuable for headhunters then um

Bryan: That's wonderful.

Mark: Well, yes it is. I'm not. I'm not. I'm not disputing that what I'm saying is we could

Mark: We can use that then to, you know, they always have, you know, we call it incentives, if you have someone who can fill this role, then we'll pay you X amount of money.

Mark: And and you know if if it's not public, or maybe even if it is. I don't know if it's not public, then you know we can

Mark: We can sell the the contacts we have, um,

Bryan: But hold on. So who grants in the actually didn't I got, I got a point.

Cindy: Well, what I was gonna say is that, you know, I always feel like it's not always recently. I'm feeling like I'm doing a lot of devil's advocate, but you know some of the issues that were going on for borderline on you know legal issues.

Cindy: And my concern is, what if somebody wants to be included in the web trust the web of colleagues.

Cindy: We don't trust them.

Cindy: What if somebody does bad work and we want to put a note on our database saying don't use them again.

Cindy: Well, that's

Bryan: And that's why it's good. Like, it's this can be you know we've talked previously about one of the functions that the NW sake does is certification right some way to certify

Bryan: Developers or, you know, consultants or something. And, and I think that's a really powerful thing. I think that's something that, you know, I would want

Bryan: Um, but what one of the whole goals. I think about MW state is to make switching the media wiki more frictionless and easier and more, you know, have media. We can be adopted across the board and

Bryan: So if that's really one of our core troubles talking about getting money here there. I don't think it's as important as trying to make sure

Bryan: People use it. So if there's less friction, meaning that headhunter goes out and uses this list of colleagues that can do a specific task and they can find that

Bryan: Developer that can that can do it perfectly. And that ends in more and better media wiki use around the world. I think we've done our job so

Bryan: I think being open is better. Right.

Mark: I and I'm I was just, you know, I was selfishly trying to make more money for for us and have to do less fundraising, but

Bryan: What I mean like it, getting back to it. Why are we raising money right yeah we're raising money for that point. And so if this is a tool that

Bryan: We give out in a sense for free, but it does that point, it makes the use of easier. I think we've done our job.

Cindy: And we are a nonprofit. We're not trying to make money. I don't know if you can hear my mask on.

Cindy: So I might be careful.

Cindy: But yeah. We are a nonprofit. We're not trying to make money aside from just being able to sustain a day in the organization. My concern recently is more about either

Cindy: regal getting it. Yeah. Getting into legal trouble or getting into financial trouble and just make

Cindy: It.

Mark: So there are there are tons of ratings websites out there.

Mark: And, you know, people are allowed to post negative reviews, if that's the concern.

Mark: So I don't think I think when you say trusted web of colleagues that implies that you know you can say negative things because hey, if there's a reason you don't dress them. There's a reason they don't you know if they're on the list. They have a negative rating so

Bryan: I'm not trying to shoehorn it, but it sounds like

Bryan: It's not a declared list of what people say their competencies are

Bryan: The trusted web of colleague, so

Bryan: If we if we move down that

Cindy: Yeah, so if somebody were not trusted, would they just not appear on the list, or would they appear with the black mark beside their name.

Lex: Yeah, I would know. I would say they don't appear. It's like a medical doctor, I mean you have to study and you have to pass the exams and then you get it.

Mark: I mean going to show up.

Mark: If he was shorter

Mark: Than you then you don't show up on the list of boards are five doctors

Lex: Yeah, exactly, because I'm

Lex: Sure people in the world that could study medicine entirely from books and YouTube videos without ever passing exam and they're not necessarily the worst doctors around but there. They don't appear on the official lists.

Lex: Yeah, right.

Bryan: And I think that's in a sense, that's work right. So for for us to have gotten to that point where there's a list of trusted members.

Bryan: There's work that went in, but that work means that somebody else has it doesn't have to do it or doesn't have to worry about it as much, right.

Bryan: So I think there's a lot of value in the end product of this list a curated list of developers and and people that can do something that, you know, some of you might want to hire them for

Lex: Yeah, and. And the other thing is, you know, sometimes customers are concerned because okay you're 123 men or women show

Lex: But, you know, if I install this and have it run and then you get out of business, you're get run over a tram by by by car, whatever. What happens then.

Lex: Right, if I can show them look we I mean this organization that it's like in a city, you know, the doctors. They haven't

Lex: They have a sort of a schedule plan. So when they go on vacation, their patients can fall back to someone else, it's, it's more, it's that that's the main idea behind it and I have

Cindy: Yeah, and I think that's great. I think that's, I think, that's huge. Yeah.

Mark: So, okay, how can we, how can we make take action on this. We talked a lot about it. How can we take

Mark: Starting

Mark: You putting people in this

Lex: Way. Yes, I'm. Look, I would say that because I'm going over this anyway. So this was my old site old web pay or wiki page that I going to convert completely, but I was going through all these you know how you

Lex: About the especially about the credentials. So I'll come up with a with a finished idea here. Let's say covering two or three aspects of media wiki on a digestible level of abstraction, because if we go too.

Lex: Far into details, it will become very rigid and here. For example, this is a this is a concrete example. That's not a, not just something that I made up with regard to the john

Lex: Q which is a big issue for a lot of people. I mean, one of the main frustrations is when their edits are not reflected in query results.

Lex: And then you have to tell them, Oh, we have to configure that but you know hacking a cron tab or or manually running the job queue or even putting a continuously run script.

Lex: On a server is really not something that that's done by an end user. So here I identified the three actions. Either you run them regularly by bias by a cron tab you set up a script to run them continuously, you know, with a weight of let's say 10 seconds or so.

Lex: Or you configure the job run rate differently, which then requires of the wiki been used

Lex: For for a minimum amount. But you see, so this would be at this very moment my apps, my suggestion of abstraction. And then we have pointers to that subject. So, for example, anything that can that is

Bryan: Concerned your operation of media wiki.

Lex: More higher or equal to 135 that's the task and then we mapped that task to some user here and say with regard to that task.

Lex: He possesses he or she possesses the competence to do that. And then we collect the credentials.

Lex: And the credentials have several types. It can be, you know, having holding a talk at a conference about job queue optimization here, you know, receiving a testimonial may be administering for extensions that deal with that and so on and so forth.

Lex: Yeah, you see that

Mark: So is that, is that something that two weeks from now if we can meet again in two weeks. Can we can we start slotting people into this

Lex: Hey look, if I'm the main worker on this task. No, because I'm now more or less than vacation for two weeks. The first two weeks is with two boys and they're going to be super keeping me busy, but I'm

Lex: You know, two children that I take for for a couple

Lex: But I can, I will certainly come up with more of these examples here and I let I wonder where we should install the system for the time being, probably will put it on manage

Mark: My time sense. Yeah.

Lex: And then I also going to connect it to my search engine. And we can we can go through that.

Mark: Okay, so the next two weeks are off off then

Mark: Yeah, so

Mark: What if

Mark: Since we have fewer people this time. And I don't know, we have any action items so that what if we say in a month, we can meet again and then you think you'd have time to get

Mark: Yeah, me know

Lex: In a month is fine.

Lex: And a monster. I mean,

Lex: I might look i can i can update you

Lex: Whenever you'll receive a cow will receive all the updates on this.

Mark: Okay, yeah, um, because yeah I we've talked about this for a while and now we actually have a use for it. And I think it'd be good to actually implement some of these things.

Mark: And if it sounds like we're that you are almost ready to do that so

Lex: No, I'm it's just

Lex: The challenge here is the level of abstraction, because it these things sound great in theory, and once you run them, you come across all sorts of obstacles. But, you know, we have to try it.

Mark: So I'm I'm going over the list of actions for this meeting and I see that I still need to get with

Mark: Brian about this credit card processing thing.

Mark: And then give Miranda an update on that.

Bryan: Oh. Well, while we're talking about that just really quick. Um, does it seem to make sense to allow for

Bryan: An arbitrary amount of money to be collected on the platform. I mean, yes, the catch all for a brokerage or, you know, some weird something

Bryan: That okay

Mark: Yeah, I absolutely think that's that makes a ton of sense, especially that we don't have hard coded amounts in there.

Mark: Are at least that we have hard coded amounts and also another one.

Mark: Yeah, I mean,

Mark: totally makes sense. Um,

Mark: So we talked about this web of colleagues, I guess that's the what we're. That was the second point with the brokerage plan to talk about yeah okay so

Mark: Um okay yeah we covered everything that we're supposed to cover

Bryan: One. One more question. Looking forward, um, if we wanted to.

Bryan: You know, if we were able to do a conference next year.

Bryan: tittering collecting conference dues. The same process.

Mark: I so

Mark: Let's spec that out. Let's see, you know, I think that's possible. I think it's, you know, I think it's possible to say no, just have an empty field, but then also without too much trouble just say, Okay, let's put a line items that you're paying for here.

Mark: But let's I think we need to respect that out and we need you, that you know offline here.

Mark: And actually,

Mark: If you have time this afternoon.

Mark: It would be good talk about that today.

Mark: Because I do need to get back from her in on this. Okay. Um, do we want to aim for meeting again in a month. And then, and then if we meet again in a month. We don't have to decide right now.

Mark: I don't think that will do it, but

Cindy: Sounds good to me.

Mark: Is that, is that right, Brian. Am I wrong on that I Think

Bryan: I think we have to make a decision about whether

Bryan: I guess it's just what

Bryan: We're having a meeting. I'm not sure. I mean, we're a small enough group. So I think we can play a little bit loose until

Bryan: But are you saying that we're going to try to meet in about a month, but we just don't have a date yet to vote on

Mark: That that was my thinking. Yeah.

Mark: I will

Mark: Yeah, let's do that because I don't you know I like the I need that we've been meeting regularly and getting some Things done making progress.

Mark: But

Mark: I also don't want to, you know, rushes too much so.

Bryan: Let's just do the one part official. And how about you call a vote for having a meeting in a month.

Mark: Yeah okay so let's vote on having a medium mountain. And if we can all give an audible. You know, yeah, your name. So, all those in favor of having a meeting in a month. Yeah.

Mark: That's too. Yeah.

Mark: Oh,

Mark: There was another one. I heard, I heard for. So, okay. Yay. Um, thank you. Um, and I guess that's it.

Bryan: Okay.

Bryan: Well,

Bryan: Have a good day, everybody. Thank you.

Cindy: Right now, so probably not going to be end to end the meeting of like

Cindy: Where you're

Mark: At now so yeah

Cindy: Yeah, I'm just saying I won't be able to hang up. So the recording is going to be a little bit longer.

Lex: Okay.

Cindy: You take care bye Bye.