I think that’s far from adequate if you want Devs to get going and feed into the process, and it will take time. We’re already beyond the point where a pause should be called.
My proposal was:
renew the domain because it is bad practice to let an established domain go, let traffic go and have it pointed to a porn site or rival project
regardless of that keep the Dev forum live somewhere and I will check it everyday (as I have for years) and answer questions there while Autonomi lack the time/staff themselves. I expect other devs would join me and this was happening before we were e told it was to be shut down.
No heat. A constructive offer of help in response to Joshuef’s proposal where he said they didn’t have time to handle it internally. I tagged you about the domain and elsewhere in the proposal I made.
I think it’s entirely normal Mark. Doc Tests are amazing as they fail if the docs are not updated with the code.
I see the dev forum in whatever form as something to chat and fix each others use of an API. But for examples and documentation I think that having those in the code makes a lot of sense.
We may not agree on that, but I am not saying devs should not have some forum to use.
My point is we need both of those and something more, which it understand is not yet on your list.
We agree that the dev forum should be part of this I think, and my understanding is that some overall the team do as well - from what Joshuef said in his proposal.
So if the community devs willing take the front line on that, can we have it back?
I don’t think it’s withheld or stolen Mark at least afaik all that’s happened is the domain was let expire. I am not a fan of it as a dev tool but happy to have others push it if they are motivated to do so. I think it would be a case of asking discourse folks to point it to another domain or use their own hosted domain.
Nobody needs to steal it. The domain expired. I reported it right away.
You then have 30 days to renew before it can be re-registered by whoever gets there first.
Picking up expired domains is a business. Almost any domain that expires is grabbed, put up for resale and frequently will be used to send its traffic to a dodgy site, or if you are lucky some marketing scammy site.
On the dev forum I though you said that this was something you supported. Joshuef has said the team support a separate dev forum or at least that he was open to it because there was some recognition of my arguments, but that they didn’t have time to frequent it for now. So he proposed reviving it later.
I’ve asked if we can revive it now with community doing the support, and I think you are saying yes or at least you are agreeable. But if it is left at that I don’t think it will happen. Nor will the domain be renewed, and it may be too late already.
That’s the last I want to say on the dev forum. I have offered to keep it going with community support. It is up to Autonomi to respond to that formally or not.
It can be any domain . It’s just a pointer in the setup afaik it’s a hosted instance but I am not 100% on that.
They may accept an email from a maidsafe account and I am happy to mail them and give them a domain. It does not have to be whatever it was it can be totally new which may be best
And I said I was not wanting to be part of the dev forum debate, typical
I know all that. The point about renewal is not just about the forum. It stands on its own.
I give up on the dev forum and I’m really pissed that you’ve listened to all this and have no intention of being involved.
The reason we are talking to you is because Bux and Jim have not been listening and we don’t want to distract devs. If you are not going to get involved, it’s no different from them not listening then everything I’ve been saying in the last few days is a complete waste of my and your time.
I don’t need to be involved though Mark, I barely used the dev forum, but I am happy to ask for discourse to map it to another domain, if they will.
Our devs barely use this forum or discord and AFAIK barely used the dev forum. They are flooded with differing mediums and I am not sure they want it. I would be happy if GitHub issues etc. were looked at more, but even there we are resource constrained.
It’s not for them. None of this is about getting them out of their spaces and here or the dev forum. At times there would be questions only you, they or someone inside could handle, but for a while that would be tiny.
The dev forum was always for developers outside Autonomi. What we had a while back with the dev hub and forum together was excellent and worked well.
If you can get the forum revived on an autonomi.com subdomain or anywhere else that will do for now. But that does not look like happening without someone in Autonomi taking action as I understand it, although for all I know all it needs is someone like Dimitar to be authorised to do some stuff. I don’t know and all Jim has said is that it will be mothballed so content is not lost but effectively left to die.
Perhaps, when we have a question that needs answering stumping multiple community devs we can have some relay that is most convenient to Maidsafe devs to answer to.
I’m aware that @happybeing has been great at raising either PR’s or issues on GitHub.
Curious what would be most preferred comm for @dirvine@joshuef@benno to respond to such queries?
For bugs it should really be GitHub. I know there is a zendesk thing being setup too that would cover user issues. I am hoping the GitHub issues and conversations there get some love soon. We need that to be much slicker and lessen the feeling of folk being pushed away.
Perhaps weekly run through of issues and fixes or similar would be good. But we need to get those numbers down.
I think personally a large part of the issue is responses to issues no matter where and it’s internal as well as external, we have the same in slack where things are not read or responded to. It’s just the teams so small and working hard on their current tasks that they don’t have bandwidth and it’s causing mayhem.
Noted. That is a real bottleneck. The only thing that can fix that is a dedicated role likely or risk distraction to current devs for a day or two a week but that could wreck productivity and delay launch.
Really a time and resource allocation dependent problem.
@neo and I have access to the domain, but the forum itself has to be manually redirected by discourse support, because after the domain there expires, we can’t access the admin menu.
I wrote to Francis a few days ago to ask if he could write to them from his authorized email because we do not have access to that email. He hasn’t answered me yet.
It should be encrypted. The network cannot do this so devs should do it. We will provide a mechanism to easily use AES 256 GSM encryption based on the hash of your secret key as the seed data.
This is also why we don’t want a history here. If you decide to change your password or whatever we don’t want that hanging around. As it’s AES it is quantum proof, for whatever that buys us, but it’s the case.
That is about registers and we must keep them from being abused or used wrong. So the 100B limit is to allow links/hashes/keys etc. to be used as links or pointers to other data.
I am not sure what of the history will help, but we are in talks with discourse to see if they can point the forum to a new url. the safe dev one is gone, but that’s largely irrelevant. It should point to a community managed domain.
Some stuff like Marks recent work or the work on static sites and web links would be great to not lose as well mind you. But another thing being pushed internally is WASM to allow cross language use. That could be a big thing and one I am quite excited about as it will allow devs of all flavours to get involved.
, is off-topic for about 20 posts. Perhaps it could be moved to a more suitable place?