This is fixed in later commits. might be a good idea to update our install

unfortunate but it would mean forking phabricator, and we are not in the position to mess with the tool curently (or forever)

Interesting topic, a lot to read and keep up already, with unfortunately not that much time on my end to discuss deeply :-)

My only wish would be : Please don't make a complex system with complex rules, because what we currently have worked quite well for a long time already :-)

Could you continue in english so we can all follow (this highly interesting topic) ? :-) Thanks !

Etherpad has become a really nice tool imho. Does it supports a way to manage easily list of documents? Permissions?

Nice idea for the two steps system.

RAML looks nice, but probably a bit too complex in the initial brainstorming phase. We could first define what "stuff" will be read / written / created/ deleted from the camera, then write the api specs.

My current take on this, is that we should follow Laravel Lumen methodology, and first agree on writing the api documentation then implement it.

eink might not be too slow if only (small) part of the screen is refreshed. And it would be damn cool to have all the settings shown even is the camera is not powered :-)

here for example : https://apertus.org/admin/structure/types/manage/article

Technical details :

The prices, tech specs, availability would be ideally put in the store imho.

I'm not sure on what we can do
we could add some text field and ask people why they register and push it to mollom for enhanced analysis

Colorbox lib was not installed.
It's now fixed. I also made a complete update of Drupal

+1

Several options to do it. If it's the same accross all pages, I'd just use a custom block with the html in it.

• create event content type
• add a date field
• use drupal calendar module as a view renderer
• profit !

I disabled registration and limited as much as possible posting for any user.

This looks like a nice and lean alternative to symphony : http://lumen.laravel.com/docs/introduction

Having the sensor information in b/w doesn't preclude having color zebra.

agreed it all depends on personal preferences. As I understand conpherence, it could complement our existing tools and allow notifications and reply by email... Best of both worlds?

Cool page, forgot to comment on this. Is is used somewhere? Might need some update

Work document : https://docs.google.com/document/d/1PSZu3aKSy4hzZfljJDKqSUAWyHg1Ax9hhG561nNO5cI/edit#

added module and configured it

By the way @WedgeSama, welcome to the lab !

Very interesting, thanks.
For a first step, I'd like to work with a minimalistic approach. Symphony seems a bit overkill for what we want to achieve. I'd start with the smallest working prototype than build on top of that.

This might be the ultimate solution : https://github.com/mofarrell/p2pvc
:-)

I would test this, since it's not so stiff on the edges.

Like this :

Agreed on providing the two boxes options.

working here : https://lite5.framapad.org/p/eLstD0Zxif

I mean general and agree on the need for an agenda.

Work in progress on this. I installed a test drupal commerce install and so far so good. Will report when ready

we could be more inovative and provide something that can be used also for longer term transportation. Using a standard (simple) box and some foam pads to protect, ship, and transport the tools.

Polystyren is not eco friendly. Might be interesting to dig the recycled paper solutions?

drupal commerce install guide :https://www.drupal.org/node/1007434

The black shading between each frame is indeed interesting, but it would mean the sensor can capture data without "opening" the (electronic) shutter.
What does it even mean in the context of an electronic shutter?

As I understand it, scope for this is debayered data. Raw (post) processing could use any other (more clever) strategy to enhance highlights, something we don't want / can't afford to do in-camera.

Putting this up for grab by the future sysadmin.

Now just need to add some file exist check : http://irc.apertus.org/index.php?day=01&month=01&year=2020

That is exactly what I had in mind. The only thing we mus be clear with, is that we should not try to create custom business logic (custom code) since drupal and drupal commerce are a real pain to customize beside what is already available as module.

One clear rule is to always show clipping as recorded.

Is it possible (and thus easier) to see this as extreme sharpening applied to the image? On the newer red cameras it looks more like sharpening, and it's very effective to do the focusing.

Note that this should happen at a specific stage that allows to have a separate magnified version sent to one output, and the normal (not zoomed) version sent to another.

I think Sebastian meant pixel skip. (every 4 line, every 4 column or something like that)

And if at all possible, bypass the need for a "conventional" (x86) cpu and find a way to provide filesystem and sata protocol support from an fpga / arm system for lower power consumption. Pipe dream ?

In phabricator, you can subscribe to the tasks you want to follow, or subscribe to projects. In the later case, you are automatically subscribed to every new task. A great way to fill your inbox :-)

if indiegogo provides decent tool, we can already use that

mostly done here : https://apertus.org/node/359

If we use drupal commerce (yes, IF :-) )

added a full screen link that opens in another window

fine for me, hadn't seen it already

Yes, sure, but if you want to update only the remote for example, you won't like to download a 300 mb file just to upgrade a 64kb firmware.

edited slightly and added added a general 20% padding style for all <p> on this page.

you beat me to it, will try :-)

yes, forgot to mention that, the faq still needs to be edited. anyone ?

now with the toc, I'm not sure we really gain something with the indent

Note that the table of content module is a text filter, in this case configured here : https://apertus.org/admin/config/content/formats/visual_editor

I installed a table of content module that does the job for us : https://apertus.org/en/faq

Blender getting involved page is good :

I would better have an article then, else we'll all have this introductory page each time we visit the lab. We could simply link to the article instead of the lab (in the mailing and on the apertus "participate" menu), and put a big button on the article saying "Ok, I understood, bring me to the lab !"

it's an old blog about the first apertus meeting (libre software meeting) that took place in switzerland :-)

...or limit width even on big screens

I really like the idea of physical meetup, I guess it's something to consider for the not too far future.

Columns and paragraphs : no (non-ugly) solution found. I think the two column thing doesn't work terribly well in most cases. Our problem is that line length is too long if we don't use columns, and then the text becomes hard to read.

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.

we could host ourselves, but it would be quite a bit more hassle.

we'd better create a static version of this, and upload it somewhere. But first, yes it must be recovered

Closing this one, and crossing fingers :-)

I think we can consider this as fixed.

it can be done as well, let me check that

and preview is here: http://cdn.knightlab.com/libs/timeline/latest/embed/index.html?source=0AkuoL30VroS1dFpZVEtoNk4yUkpsb1pRTEN4S0w3X0E&font=Bevan-PotanoSans&maptype=toner&lang=en&height=650

Timeline work in progress here : https://docs.google.com/spreadsheet/ccc?key=0AkuoL30VroS1dFpZVEtoNk4yUkpsb1pRTEN4S0w3X0E#gid=0

a very cool tool for timelines (presented online only) is timelinejs : http://timeline.knightlab.com/

testing adding a project in cc

adding potential helpers, including myself :-)

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

I tried to download the file here, and it unpacks fine btw

I would do the other way around and put everything under a single faq page. Thoughts?