Dmitri Pisarev dimaip

I have a project idea, that is very well needed in our church, but I wonder if it would be interesting for wider circles. We often need to transcribe (i.e. turn audio into text) of sermons, interviews, conferences etc for our websites our newspapers. Usually volunteers help out with it. Current workflow is:

Convert some weird audio format into mp3
Split mp3 into, let's say, 10 minute pieces
Distribute those pieces among volunteers
Volunteers have to download some audio player that supports keyboard shortcuts, slowing down speed and setting volume to more than 100%
Track progress and then collect transcribed texts from volunteers
Stich those texts into one file and proofread it, edit it etc

You get the point... Perfect place to introduce some automation: I want all of this to be automated in an online service.

Dear Neos community!

I'm just back from the Dresden sprint, in which I was able to participate thanks to your kind help.

We managed to do quite a lot of work on the new React UI for Neos CMS, and I pesonally was able to do some focused work on replicating the dialog for creating new nodes. See my writeup on the current progress of the UI rewrite.

We don't want to loose momentum going, so we are organizing another sprint before the Inspiring Conference, 18th to 23rd of April. My employer, SFI.ru, is ready to send me there as part of my working time. I will try to find a place to stay via Couchsurfing.com, to save some team budget (though if you live in Rosenheim and want host me, I'll be more than happy), but yet again, I can't pay from personal budget for the plain tickets.

Currently I found cheap tickets from Moscow to Munich and back for only 160EUR + 30EUR for the train to Rosenheim. If your company i

Dear community,

Neos CMS team is currently in the middle of UI rewrite on top of React. This project will have immediate benefits like improved performance, correctly working media-queries and higher robustness of the UI due to the use of iframe for site content. But main aim for it is to support ambitious plans of our project (such as structured editing of content) that would require a modern foundation.

Currently we have reached an alpha phase, where almost all basic functionality is in place, but everything needs A LOT of polish. And that's where I want to ask for your support.

I have been a part of this project since its early prototype days, and was able to spend quite some time working on it, including joining 3 code sprints fully focusing on it. But right now I can not afford to work on my spare time as much as the project currently requires it. So **I'm looking for sponsors that would allow me to relocate some of my freelancing time

Here's a quick idea for a stateless PaaS on top of Github and docker swarm.

You mark Github repos that you want to deploy to your Docker swarm with a certain tag, say "my-server".
Each repo has a docker-compose.yml file defining the stack needed to run it.
You have a daemon that periodically queries Github API for repos with given tag name (and from a certain user, for security reason). For every found repo it would do docker stack deploy RepoName --compose-file "...". Stacks would be deployed according to given service's deploy policy, utilizing its healthchecks etc.

So if you need to add a new repo to the swarm, you just mark it with a tag and wait a few min. If you need to update a service, you just edit its docker-compose.yml file and wait a few min. Secrets would be managed via docker secrets.

Advantages over plain swarm cluster?

Dear Neos community,

during the last code sprint in Vienna I've spent a week coding support for selecting multiple nodes in the document and content trees and performing batch operations on all of them: copying/moving/deleting/hiding all of the selected nodes at once. I am sure editors are going to appreciate this feature very much :-)

Now the feature is already working, but I still need the time to polish the technical implementation, writing tests for it, improving the visual styling etc. Unfortunately, I will not be able to finish it in a spare time mode in the foreseeable future, so I want to ask you to support me by funding this feature. I need about 10 hours of work (at 55€/h rate) for polishing it.

If I get another 20 hours of sponsoring, I would be able to implement batch editing of any property in the inspector that is common to all of the selected nodes. E.g. imagine selecting multiple nodes in the tree and then being able to set say a starti

	/**
	* Реализация API, не изменяйте ее
	* @param {string} url
	* @param {function} callback
	*/
	function getData(url, callback) {
	var RESPONSES = {
	'/countries': [
	{name: 'Cameroon', continent: 'Africa'},
	{name :'Fiji Islands', continent: 'Oceania'},

	# Data in content repository would look like this:
	{
	nodeType: "My:Page",
	properties: {
	title: "hello world title"
	},
	children: [
	{
	nodeType: "My:Text"
	properties: {

	prototype(Sfi.Site:ImageUri) < prototype(TYPO3.TypoScript:Case) {
	image {
	condition = ${asset}
	renderer = ImageUri {
	asset = ${asset}
	width = ${width}
	height = ${height}
	maximumWidth = ${maximumWidth}
	maximumHeight = ${maximumHeight}
	allowCropping = ${allowCropping}

	prototype(Flowpack.FusionBP:RecursiveMenu) < prototype(Neos.Fusion:Array) {
	@process.tmpl = ${'<li>' + value + '</li>'}
	title = ${node.properties.title \|\| '<em>' + node.name + '</em>'}
	nextLevel = Neos.Fusion:Collection {
	@process.tmpl = ${'<ul>' + value + '</ul>'}
	@process.tmpl.@if.notEmpty = ${q(node).children().count() > 0}
	collection = ${q(node).children().get()}
	itemName = 'node'
	itemRenderer = Flowpack.FusionBP:RecursiveMenu
	}

	<div>
	Quess what's in here: {property1}
	</div>