SoylentNews is people
SoylentNews
Well, it's been a bit of time since the last time I posted, and well, I had to think a fair bit on the comments I received. It's become very clear that while I'm still willing to at least help in technical matters, the effort to reforge SN is much higher than I expected. In addition, given the, shall we say, lukewarm response I got to my posts and journal entries, well, I'm clearly not the right person for the job.
I think at this point, it's time to figure out who is going to lead SN going forward. After my de facto stepping down in 2020, the site has, for want of a better word, been a bit listless. At the moment, no one on staff really has the cycles to take that position on. A few people have expressed interest in the position, and I've talked with Matt, who is co-owner of the site about this. By and large, whoever fills the seat will have to figure out what, if anything, needs to change in regards to moderation policy, content, and more.
If you're interested in potentially fulfilling the role, drop me an email at michael -at- casadevall.pro, with the subject of "SN Project Leader", and include the following:
- Who you are
- What you want to do with the site
- How you intend to do it
- Why do you want to get involved
I'll leave this call for candidates open until December 14th, at which point Matt and I will go through, and figure out our short list, I'll talk to editors, and solicit more comments from the community. I'm hoping to announce a successor in early January, and formalize the transition sometime in February, which will be the site's 9th anniversary.
(Score: 1) by shrewdsheep on Monday December 05, @06:51PM (4 children)
My suggestion is to put the configuration (best as CMS scripts like ansible)/dockerfile online to spin up an instance of soylentnews on github/lab etc. Then you don't have to do the work yourself.
(Score: 3, Informative) by janrinok on Monday December 05, @07:48PM
Containerisation is exactly what NCommander is intending to do.
(Score: 4, Insightful) by janrinok on Monday December 05, @07:58PM (2 children)
Of course, we cannot provide docker containers with all the personal database data already inside them. That would hardly be way of keeping everybody's personal data private, now would it? There is also a series of privileges that need to be allocated to specific users depending on their role or function.
However, generating fake data is possible - we do it on the development system so that we can create reproducible data for testing. It is quite time consuming for the first time though. But it gives anyone a chance to spin up a system and debug/play with the code.
(Score: 2) by fliptop on Monday December 05, @09:54PM (1 child)
Maybe I'm misunderstanding, but can you not include the data in the container? Just the code and DB schema that runs the site, spin that up, then load the data from backup?
To be oneself, and unafraid whether right or wrong, is more admirable than the easy cowardice of surrender to conformity
(Score: 2) by janrinok on Tuesday December 06, @01:08AM
Yes - WE can. That is the whole point of doing this. But we are not going to provide the docker package complete with personal data to other people.
One of the benefits of the container is that is can be transferred elsewhere and run. If someone thinks that they are going to be able to simply ask for a docker installation and it will arrive complete with data then that is incorrect. They could have the container without any data so that they do not have to build a new system complete with all the same versions of software in order to test or debug software - which is what we have to do today. Several people have tried this path, including myself, and simply found the the effort was not justified.
However, I will happily take the docker container and create my own fake data in order to do bug squashing or testing changes to the Perl code.
At least that is my understanding of it.