We are currently evaluating shout as mentioned by allan.

I would not close this too fast. You proposed interesting stuff and having more feedback would be great. I know it's a bit disappointing to have this little feedback, but it is often like that when you are in charge of the more "infra" side of things in a project.

By the way, how can I quit my account here?

Because of the lack of interest, I think this topic can be closed.
Although the fact, that only two persons added a comment speaks for itself.

Closing this one, and crossing fingers :-)

Done in http://lab.apertus.org/V4

inviting backers to the lab is a very good idea, whishlist also. Polls - excellent idea, noticed only one ...

I think we should adapt the welcome panel a bit to give people options to do these things with one click:

What does lab lacks that a forum would bring?

Mailing lists suck a bit for finding information, they work better for "official" correspondence in larger projects. Often in a semi-direct manner.

@philippej: the people lost the interest in the forum. True, but what do you think, why is that? They also lost the interest in the mailing lists, why is that? And what about the lab? How many people participate here?

I dont think the forum should close, only that development should be moved out of it. The forum is nice to have when people get their devices, if its just open now it will continue to build for when its needed.

A few comments in random order :

You can post your own opinion while documenting, something like (author note : blabla), I see no problem with that.

having a problem with documenting the Discussion about sliders and rotary dials without bringing in my personal opinion, which I should not do as a documenter...
although extracting keywords would perhaps help not to go through the same discussions again and again.
extracting links would be a question of just setting up a simple script - if this could be of any use
[off topic] cannot imagine setting a camera value by using linear controls as e.g. sliders, although I appreciate faders when using a (sound)mixing console - compared to rotary knobs - on the other hand, it is very easy to distinguish about 16 different positions looking at a rotary knob ( or scale, imagine a wall clock or a compass ), whereas 10 positions are very hard to distinguish on a linear scale ( slider )
[very off topic]do we have something like user Interface from the Viewpoint of usability ( having intuitive handling in mind, and if so, which story should be behind it?)

@allan, will keep your update text for when we'll announce lab to all bakers (currently only announced to team, in order to scale as nicely as possible). Also I still need to find a way to link to open, unassigned tasks in lab.

What about some structure in/for the wiki? In the moment we have about hundred pages ( 106 to be precise ), as the numer of pages increase, it will be harder to find any information.
I propose to move e.g. ElphelVision pages to a separate namespace ( or something alike , as I am not "the MediaWiki expert" )

I cooked up this little update that can be sent out to backers:

hi, just some sort of crawled through the irc logs of the past days to look at and bookmark all ( or some of ) the URLs, like

Very interesting guys!

All good in theory, but in practice especially online its much more difficult.

The power to overthrow is at no point given away. We all have to put trust in the operators of the apertus company, because if they arent trustworthy, any and all endeavours are flawed anyway.

The problem with these kinds of responsibilities and permissions as with any online group is trust and potential for major problems down the line.

The point i was trying to make is i need admin rights to delete anything. The comment is in the edit log, atleast thats the way to do it.
my {{delete|comment}} got eaten since the template didnt exist.

@allan, please try to keep discussion in each task relevant for this task.

I would like to be website editor. I can manage the effort to simplify and improve the communication, and also help new members to do the same.

I'm more than happy to agree to not do it, and if we don't have any other feedback going in te opposite direction, we can won't fix in a week or so

I agree with Allan here, we should not try to solve a problem that isn't one for us currently.

I can help out, send me a BoM-list.

From the info I sourced on the different pages, some creative commons, share alike? license is to be used for documentation. GPLv3 for software, and cern open hardware license for the metal.

printed and cut, all done

printing now

I agree. With a lot of public interest now directed at our project, I'd like to avoid falling into any legal disputes with developers who are neither familiar with or aware of our openness.

Please check with TAG organizers and reassign to me in case I should still print them.

Might be possible to have them printed in Mexico so we dont need to fly them in.

minor last changes applied

design finished, review and ready for printing:

"A" instead of "an". We could probably just say developer's kit instead of both. That way it is more concise and easier to follow. "Developer's kit" implies that it is for an early adopter anyway.

Attached the updated version

or this :