Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 194. (Read 804700 times)

**NOTE**

We now have a public repo for the Block Explorer. Please feel free to load your own and post the address here!

https://github.com/crypti/bcexplorer

I know, I just thought an answer of "No, but you can help with testing if anything" would suffice, because I was reading his posts,




And seemed like he could be fit for testing if his intetions were really about helping out.

You missed the part where he was offering his help by wanting access to the code. Hello

Anybody?

I would like to check on your development, and see if i can give you a hand on it! I’m free at the moment maybe i could come in handy!

This guy, even if he was somewhat insulting while doing so was talking about the db structure/opt issues while back and how Node was better at this, and for the record lol they were and are currently and thats reality, and now you're on that, so surely, he's offered you good advice thus far even if he did not tell you it in a sunshine and flowers kinda way because currently it isn't...... this is getting ridiculous

You shouldn't share XCR SC sure, but in it's current form it's gonna help Node, really? We've hit a hurdle too, remember?

Wake up!

If he really wants to help, get him to help you with public testing as Wulfcastle suggested because you need this help, but don't cut outsiders out like this, people expressing interest in XCR isnt even big right and what you do doesnt help this.... especially continuessly talking down on another currency, how's this doing XCR any good?

This guy, even if he was somewhat insulting while doing so was talking about the db structure/opt issues while back and how Node was better at this, and for the record lol they were and are currently and thats reality, and now you're on that, so surely, he's offered you good advice thus far even if he did not tell you it in a sunshine and flowers kinda way because currently it isn't...... this is getting ridiculous

You shouldn't share XCR SC sure, but in it's current form it's gonna help Node, really? We've hit a hurdle too, remember?

Wake up!

So you consistently come into our thread and talk about how NODE is better than us, you are an avid visitor and fan to the NODE thread and have offered to work for them, and you want our source code?

IMO one of 2 things is happening here. Either you are working for the NODE team and due to the fact that they hit a hurdle you want to see if our code can help, or you are trying to get both of our source codes to develop something of your own. You haven't been here in like a month, so I seriously question the motivation here.

Anybody?

I would like to check on your development, and see if i can give you a hand on it! I’m free at the moment maybe i could come in handy!

I'll ask this!

I'm currently on the iRC with a bunch of XCRs. Just waiting for a developer and GreXX now. Join if you got time. I'll give them the time they need to sort out their internal discussion first, and maybe then they got time for us.

I'm thinking of asking about clarifications on:

The new version
Custom Made Blockchains
Windows wallet forging
Belarus
About new developers
ETAs
The solution you brought up.


If you got anything else, or anyone got anything else and can't participate let me know. I'll probably come up with more as we go.. hoping for a constructive discussion... I'll ask the hard questions! From a market perspective, they no longer matter too much if they are negative, so maybe we can get some straight answers so we're all in the loop on what to expect now.

Let me know!

What is the status on the new version? When is it coming out?

Hey Guys, I am working with the team to find out when we might be able to work something out to do a chat. For reference, we do our weekly meetings at around 12 my time (U.S. Denver, Mountain Time) on Saturdays. They last anywhere from 2 hours to as long as 6 (the longest). Worst case, maybe I can get a few of us to stick around after the meeting or pop in during.

+1 I will be available as always on: #CryptiTalk IRC.

To be fair, GreXX made a welcome effort to be present in IRC this week. For those present (jari76, myself and the usual silent lurkers), it most certainly provided a confidence boost. I provided pastebins to those who came asking for news, but it appears there are still unanswered questions.

I've also had a few long conversations with 5000Bitcoins this week. He really has huge amounts of passion & energy. If you guys want to avoid conflict. May I suggest you find a way to channel that passion & energy into crypti rather than against it. We have a long haul ahead of us and we need all help we can get...

Peace, Karmacoma24.

Heres my Solution to the problems I outlined in my post above :

The Solution

1. Create Proper Deadlines
It's time to ditch this "It's done when it's done" crap and move to a proper release schedule. Proper realistic deadlines need to be created, and the whole team should work reaching that deadline. No more "it should be done in 3 weeks" or anything like that, we need actual dates. The "It's done when it's done" mentality simply doesn't provide any motivation to complete releases on time.

2. Bi-Weekly Updates
Currently the only time we get real updates is when we constantly have to ask for them, or when shit hits the fan. That should not be the case, we shouldn't have to ask for updates as I've mentioned before, they should be provided in a timely manner. I suggest that GreXX provides the community with 2 weekly updates, covering everything that the team has done since the previous update. I suggest the updates take place on a Wednesday and Saturday each week.

3. External Communications Auditor
Frankly, at the moment we can't trust the word of any member of the team, therefore I suggest that we nominate a member of the community, one that is not currently on the Crypti Team, to view and participate in  the internal communications channel between the Crypti Team members. The member of the community would then report back to community to verify the bi-weekly updates or to answer questions that need verification.

4. Open Testing Cycles
At the moment all testing of new Crypti releases, are being done internally, and at the moment terribly. I suggest that the Crypti Team make testing cycles open to anyone that would like to participate. The advantage of this, is that new releases are being tested across a wider variety of platforms and will be more conducive to bug finding than internal testing. The way this would be carried out, would be with BETA releases, which would be released normally, however only those who want to help with testing would download and use it. Errors could then be logged into a special BETA Repository on GitHub. None of the source code needs to lie there, the repository simply needs to exist so that issues can be logged. (The whole process should be carried out similar to the way OpenBazaar is going about their BETA releases.)


Well fellow community members, what do you think?

+1 that sounds good to me

Perhaps set up an ircmeeting with community + foundation + atleast one developer this weekend. What do you think?